https://bugzilla.redhat.com/show_bug.cgi?id=858801
--- Comment #31 from Steve Tyler <stephent98(a)hotmail.com> ---
(In reply to comment #29)
the zh_HK locale already exists. your example doesn't. they are
different
cases.
Doing an F17 test install, I noticed that we used to just list 'Chinese
(Traditional)' and 'Chinese (Simplified)' (and the Chinese translations of
each), without referring specifically to a country for either. I'm assuming
these resulted in zh_TW and zh_CN respectively. Somewhere between F17 and
F18 we decided to list the associated country name for them. So that makes
it more obvious that SG and HK are missing.
anaconda-17.29-1 uses a language table that has these entries:[1]
Chinese(Simplified) zh_CN False zh_CN.UTF-8 us Asia/Shanghai
Chinese(Traditional) zh_TW False zh_TW.UTF-8 us Asia/Taipei
With F18, the language table was removed, and that functionality is now
provided by python-babel[2], in part. python-babel provides an interface to the
Unicode CLDR locale data.[3] With python-babel, applications can retrieve
various display names for a language:
>> import babel
>> babel.Locale('zh', 'CN').english_name
u'Chinese
(China)'
>> babel.Locale('zh', 'TW').english_name
u'Chinese (Taiwan)'
>> babel.Locale('zh', 'HK').english_name
u'Chinese (Hong Kong SAR China)'
>> babel.Locale('zh', 'SG').english_name
u'Chinese (Singapore)'
[1]
http://git.fedorahosted.org/cgit/anaconda.git/tree/data/lang-table?id=ana...
[2]
http://babel.edgewall.org/
[3]
http://cldr.unicode.org/
$ rpm -ql python-babel | grep localedata
--
You are receiving this mail because:
You are on the CC list for the bug.