We need this pref to be able to sort correctly on linux. For 6.0, this is put in all.js in Japanese linux build.
Yes, it has to be moved to .property file and need to change the related .cpp file.
Status: NEW → ASSIGNED
Is it navigator.properties, then?
>Is it navigator.properties, then? yes
intl -> l12y
Keywords: intl → l12y
OS: Linux → All
Priority: P3 → P2
Hardware: Other → All
"intl.collationKeyAsCodePoint" is a bool pref. There is no getLocalizedBoolPref() in nsIPref. Tao, do you think we should create getLocalizedBoolPref()? For this bug, I can change "intl.collationKeyAsCodePoint" to a char pref instead of bool.
Alecf owns the getLocalizedXX() api. IMO, your proposal will work. No need to add another api just for this particular bug.
Mass change of QA contact to ji for the bugs filed by her.
QA Contact: momoi → ji
r=tao if the default value of this pref is null in navigator.properties
How about a slightly better wording, for understandability: mKeyAsCodePoint -> mUseCodePointOrder collationKeyAsCodePoint -> useCodePointOrder Also, expand the comment in the property file to: valid collation options are: <empty string> or useCodePointOrder sr=erik
Status: ASSIGNED → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → FIXED
With 04/10 build, in the file of .../locale/en-US/navigator/navigator.properties I saw the pref of "intl.collationOption" Naoki, did you change it to a char pref or bool pref?
That's a char pref, the possible value are listed as in the file. 29 # valid collation options are: <empty string> or useCodePointOrder
Thanks. Verified as fixed. Added Ying and Ray to cc list. We need this pref set to useCodePointOrder for Japanese linux build.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.