** Observed with 7/12/2000 Win32 build ** In Edit | Prefs | Languages | Character Coding list, we currently see both: 1. static list of charsets 2. Cached charsets We should not include item #2 on this list. If you have just the Western Charset and then a cached item, e.g. KOI8-R, and if you choose KOI8-R, then the next time you start Mozilla and look in the default charset pref, you won't see KOI8-R because currently the cache list is not saved from session to session. Aside from this, it is simply not correct to show cached list items here. We want a (semi-)permanent list. Otherwise users would be confused. We have not had an explicit discussion of this yet but I think it would be better to show the entir echarset list here rather than the limited "static" list. This last point may be debatable and so let's hear some opinions.
Reassign jbetak's bug to ftang.
Assignee: nhotta → ftang
reassign to cata
Assignee: ftang → cata
Status: ASSIGNED → NEW
Mark as nsbeta3+
Target Milestone: --- → M18
Mark it as P4.
Priority: P3 → P4
*** Bug 44062 has been marked as a duplicate of this bug. ***
The work for this bug can be splitted in two: 1) Create an RDF data source branch holding all the decoders 2) Use that data source in XUL dialogs
Whiteboard: [nsbeta3+] → [nsbeta3+] ETA:9/7
2) is easy simply change The value of rdf in http://lxr.mozilla.org/seamonkey/source/xpfe/components/prefwindow/resources/con tent/pref-languages.xul 82 <menulist id="DefaultCharsetList" ref="NC:MaileditCharsetMenuRoot" datasources="rdf:charset-menu" from "NC:MaileditCharsetMenuRoot" to the new RDF root value that you creat
Failed to check in yesterday, sorry. I am almost done, I need review and then I'll check in today.
Frank, you're right. But I wonder if there would be any other place where we could use this new RDF datasource branch?
And all is done and checked in.
Status: ASSIGNED → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → FIXED
Verified in 2000-09-11-08 Win32, Linux, and Mac build.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.