Bug 30762 - zh-Hant: new locale
Summary: zh-Hant: new locale
Status: RESOLVED DUPLICATE of bug 30761
Alias: None
Product: glibc
Classification: Unclassified
Component: localedata (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-08-15 02:03 UTC by taozuhong
Modified: 2023-08-21 08:43 UTC (History)
3 users (show)

See Also:
Host:
Target:
Build:
Last reconfirmed:
fweimer: security-


Attachments
zh-Hant locale data (1.48 KB, text/plain)
2023-08-15 02:03 UTC, taozuhong
Details

Note You need to log in before you can comment on or make changes to this bug.
Description taozuhong 2023-08-15 02:03:32 UTC
Created attachment 15056 [details]
zh-Hant locale data

Dear maintainers,

Chinese has two scripts/variants: Simplified Chinese and Traditional Chinese, and the two variants are supported in different countries:
Simplified: zh-CN (Mainland), zh-SG (Singapore), zh-MY (Malaysia), zh-ID (Indonesia)
Traditional: zh-TW (Taiwan), zh-HK (Hong Kong), zh-MO (Macau) 、....

Question
The locales in used can't cover all Chinese users, especial the users outside the mainland of China, Hong Kong and Taiwan; the App developers will cost more time to support them.

Chinese support solution
Since Windows Vista and later, RFC 4646 has been chosen as the locale tag, W3C also support them, the language identification format is:
<Language>-<Script>-<Region>

The corresponding language codes are as follows:
Simplified: zh-Hans-CN / zh-Hans-SG / zh-Hans-MY / zh-Hans-ID / ...
Traditional: zh-Hant-CN / zh-Hant-HK / zh-Hant-TW / zh-Hant-MO / ...

if GLibc could support Chinese language encoding: zh-Hans/zh-Hant, Chinese translation will cover all of Chinese users, and just maintain two po files.

To simplify and improve the Chinese support, please support the Chinese language encoding zh-Hans/zh-Hant. 

Please find attached the locale definition for zh-Hant to be considered for inclusion in glibc.

Thanks!
Comment 1 Florian Weimer 2023-08-21 08:43:58 UTC
Relevant discussion is on the other bug.

*** This bug has been marked as a duplicate of bug 30761 ***