Closed
Bug 28854
Opened 26 years ago
Closed 26 years ago
clean up intl values in all.js
Categories
(Core :: Internationalization, defect, P3)
Tracking
()
VERIFIED
FIXED
M15
People
(Reporter: bobj, Assigned: nhottanscp)
References
Details
Please remove these obsolete prefs from all.js:
In http://lxr.mozilla.org/seamonkey/source/modules/libpref/src/init/all.js
254 pref("intl.character_set", 2); // CS_LATIN1
255 pref("intl.font_encoding", 6); // CS_MAC_ROMAN
...
253 pref("intl.auto_detect_encoding", true);
(nhotta, I gave you this because you already have to edit all.jp for bug 28751.)
| Assignee | ||
Updated•26 years ago
|
Target Milestone: M15
| Assignee | ||
Updated•26 years ago
|
Status: NEW → ASSIGNED
| Assignee | ||
Comment 2•26 years ago
|
||
remove intl.mailcharset.cyrillic also
Do we need to do anything with obsolete 4.x prefs when doing the profile
migrations?
| Assignee | ||
Comment 4•26 years ago
|
||
Asking this to sspitzer, that's a generic pref migration issue.
Comment 5•26 years ago
|
||
there are two parts to this.
1) remove default 4.x pref values from the default pref files (like all.js) if
they are no longer used by 5.0
2) migrate 4.x prefs to 5.x values, and then remove the 4.x prefs.
which issue is this?
I have a bug on me (#10672 ) to clear the old 4.x mailnews prefs after we
migrate them to 5.0 pref values.
| Assignee | ||
Comment 6•26 years ago
|
||
This bug is for 1).
The issue bobj mentioned is 2) which is a dup of 10672.
Please also remove four intl prefs in migration when you do 10672.
intl.character_set
intl.font_encoding
intl.auto_detect_encoding
intl.mailcharset.cyrillic
Comment 7•26 years ago
|
||
who is migrating these prefs?
intl.character_set
intl.font_encoding
intl.auto_detect_encoding
intl.mailcharset.cyrillic
using lxr, I didn't see any code to migrate them.
| Assignee | ||
Comment 8•26 years ago
|
||
Those prefs are not going to be migrated to mozilla.
We want those pref not to appear in the migrated pref.
Are they automatically done?
| Assignee | ||
Comment 9•26 years ago
|
||
checked in
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•