Re: Simplified or traditional for each Chinese macrolanguage

On Wed, Jul 27, 2016, at 04:43 PM, Xidorn Quan wrote:
> On Wed, Jul 27, 2016, at 04:07 PM, Koji Ishii wrote:
>> 2016-07-27 12:34 GMT+09:00 Xidorn Quan <me@upsuper.org>:
>>> On Wed, Jul 27, 2016, at 12:13 PM, Koji Ishii wrote:
>>>> So Literary Chinese and Mandarin are hard to determine? I checked
>>>> Windows region/locale/language settings but it doesn't seem to have
>>>> these in the list.
>>>
>>> Mandarin is just what we generally refer to by saying "Chinese".
>>> Literary is a historic language of Chinese, which is not used in
>>> daily life nowadays.
>>>
>>>> Maybe we should handle them as "unknown", so that browsers fallback
>>>> to use the system setting?
>>>
>>> What should zh (without anthing else) do, actually? What happens to
>>> that should probably be what we do for Mandarin and Literary.
>>
>> Blink and WebKit uses Simplified for "zh", I guess other
>> browsers too?
>
> Yes, we do this as well. I think I tend to make Literary Chinese map
> to Traditional Chinese by default, as that should be closer to how the
> text were written initially... But not sure whether it should be zh-TW
> or zh-HK... Oh, BTW, Yue should be zh-HK, and Min Nan and Hakka should
> be zh-TW.
>
> FWIW, I noticed something interesting that, we currently map zh-min-
> nan to x-western, which also matches how Min Nan Wikipedia presents.
> According to pages in Chinese wikipedia [1], Min Nan Chinese has two
> major writing system in Taiwan, one is with Chinese characters, and
> the other is using romanized characters, and sometimes people mix them
> together.
>
> Since it is unlikely that western fonts can handle Chinese characters
> properly, I guess we probably still want it to be mapped to
> Traditional Chinese by default rather than x-western.
 
Errr... zh-min-nan is not a valid language tag at all... Not sure why we
have that. Let me try to remove it :) And x-western is a Gecko-internal
tag for general western languages.
 
- Xidorn