Closed Bug 382843 Opened 17 years ago Closed 11 years ago

In chinese version, default charset in Font preference not set correctly

Categories

(Mozilla Localizations :: zh-CN / Chinese (Simplified), defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: soflare, Assigned: shaohua.wen)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; zh-CN; rv:1.8.1.4) Gecko/20070515 Firefox/2.0.0.4 XPCOMViewer/0.9.5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; zh-CN; rv:1.8.1.4) Gecko/20070515 Firefox/2.0.0.4

In chinese firefox version, the default charset is wrong.

Reproducible: Always

Steps to Reproduce:
1. Open preference dialog
2. Choose Content Tab and Click Font

Actual Results:  
In default charset group, It show nothing or UTF-16

Expected Results:  
Should be GB2312
This is a localization bug. I think it cause by the file chrome://global-platform/locale/intl.properties. In this file, the intl.charset.default is set to "gb2312", I think it should be "GB2312".
And it still has gb2312 in http://mxr.mozilla.org/l10n/source/zh-CN/toolkit/chrome/global-platform/win/intl.properties
I wonder is it possible to detect illegal charsets in l10n with some tool somehow.
Assignee: nobody → shaohua.wen
Component: Preferences → zh-CN / Chinese (Simplified)
Product: Toolkit → Mozilla Localizations
QA Contact: preferences → shaohua.wen
There is no l10n notes found in this intl.properties file.
In many places the case of the charset are not case sensitive.
why here it's case sensitive?
anyway ,fixed for firfox 3.5beta and trunk:
1.9.1 :

changeset:  89:44aeeb4ae471
user/date:  shaohua.wen@gmail.com	2009-04-15 09:38:20 +0800
parent:     88:da4975f29664 accesskey fixes.
tags:       tip

trunk:
changeset:  84:373bff0130e1
user/date:  shaohua.wen@gmail.com	2009-04-15 09:39:13 +0800
parent:     83:f2f3f3405a37 accesskey fixes.
tags:       tip

for firefox 3.0x I'll create patch for review.
I filed bug 488433 to get that cleaned up.
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.