Closed Bug 33403 Opened 25 years ago Closed 25 years ago

Charset related defaults need to be set for JA build

Categories

(Core :: Internationalization: Localization, defect, P3)

x86
Windows NT
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: momoi, Assigned: fergus)

Details

** Observed with 3/23/2000 Win32 build ** The charset and charset menu defaults are currently using the ones for the US build. These should be changed to reflect the localization. Here's what we should set: pref("intl.charset_menu.static","iso-2022-jp, shift_jis,euc-jp,iso-8859-1"); pref("intl.charset.detector","japsm"); There is one other item, of which I'm not sure. Cata, should there be any setting for this? if so, what value? pref("intl.charset_menu.cache", ""); The first 2 are definitely needed for jabeta1. The 3rd, we will wait for an answer from cata.
A couple of things about the charset menu defaults. 1. I'm recommding setting defaults for both Auo-detection and JA charsets. If the auto-detection is on, the 3 menus are not needed, but I think we should have them in case the user turns off auto-detection. 2. I'm including iso-8859-1 because that would be one other charset people might be using.
Needed for beta 1.
Keywords: jab1
Note that charset names are case-sensitive and must be in lowercase.
Target Milestone: --- → M14
Fergus, I reassign the bug to you. Please talk to Kat regarding the Prefs update.
Assignee: rchen → fergus
We're excluding UTF-8 here, right?
Status: NEW → ASSIGNED
Yes, you're right. There will be no UTF-8 on the static menu.
Unlike the charset names to be used for conversion, the names used for menu seem to be case-sensitive. So, please use exact values I suggested above.
Fixed in 0328 build
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
I verified this in 2000032417a JA build.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.