[zh-TW] Overwrite zh-CN font setting in zh-TW Windows Firefox

RESOLVED FIXED

Status

()

defect
RESOLVED FIXED
9 years ago
Last year

People

(Reporter: timdream, Assigned: timdream)

Tracking

(Blocks 1 bug)

Firefox Tracking Flags

(Not tracked)

Details

zh-CN fonts has different style of glyphs, but we sharing the same CJK Unihan block. Some websites (e.g. Facebook) sets <html lang="zh"> for their zh-TW site, results zh-TW content being rendered in zh-CN fonts.

The proposed change will only applies to Windows users who installed zh-TW Firefox by localized installer. Yes, zh-CN website will be look different, however we need to make sure zh-TW content is always rendered using the right font.

The behavior is in parity with Google Chrome. Chrome hard-coded the choice of font in binary, and switches zh(|-CN|-TW) defaults according to interface language.

IMO, <html lang="zh"> is not semantically wrong, it's just not precise enough for browser to figure out the content is in Traditional or Simplified Chinese.
This is due to the design flaw of ISO language code standard and trade-offs of Unicode Unihan unification rule.
http://hg.mozilla.org/l10n-central/zh-TW/rev/eac97260bfd1
Pushed. Marked as RESOLVED FIXED.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
VERIFIED on latest win32 nightly.
Status: RESOLVED → VERIFIED
I'm not convinced this is the right solution to the problem.

Simon, could you weigh in?

Reopening and moving to Core Intl.
Assignee: timdream → smontagu
Status: VERIFIED → REOPENED
Component: zh-TW / Chinese (Traditional) → Internationalization
Product: Mozilla Localizations → Core
QA Contact: timdream → i18n
Resolution: FIXED → ---
Other than evangelism, I suppose the right fix is to special case "zh" in nsLanguageAtomService.cpp, using a localizable pref.
It would be great if "zh" could map to "zh-TW" or "zh-CN" or even "zh-HK" based on current localization. Before that the overwrite could serve as the workaround.
Blocks: 1085335
No longer blocks: 1085335
Blocks: 1358900
The workaround here should be superseded by bug 677919 if it ever gets implemented.

I am restoring the bug status here given we should file new bugs for any follow-ups.
Assignee: smontagu → timdream
Status: REOPENED → RESOLVED
Closed: 9 years agoLast year
Resolution: --- → FIXED
See Also: → 677919
You need to log in before you can comment on or make changes to this bug.