From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.0rc1) Gecko/20020417 BuildID: 2002041711 The "Add Languages" dialog (communicator/pref/pref-languages.dtd) does not list the languages(/country) in the correct order when dealing with accented letters (correct order for most european countries... : the one used in the adress-book, for example) Reproducible: Always Steps to Reproduce: 1. Use the de-AS language pack 2. Do Edit/Preferences (Bearbeiten / Einstellungen / Navigator / Sprachen / Hinzufügen...) 3. Go to the "Arabisch/*" Actual Results: The order is "Algerien < Yemen < Ägypten" Expected Results: "Ägypten < Algerien < Yemen"
Reporter: can you confirm this, hopefully with a screenshot, on a modern build?
Summary: Wrong string order in Add Language dialog (when there are accented letters) → Wrong string order in Add Language dialog (when there are accented letters)
Created attachment 125350 [details] Screenshot for 1.4 beta This is our bug on 1.4 beta, with the de-AT (german) language-pack. You see it twice, for Dänisch and Österreich.
Don't see any dupes on this one.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Though it may be related to 54746
Created attachment 172963 [details] [diff] [review] Sort using localeCompare. Small problem: localeCompare is very slow. This might cause a noticeable delay on older machines.
Attachment #172963 - Flags: review?(smontagu)
*** Bug 163140 has been marked as a duplicate of this bug. ***
Attachment #172963 - Flags: review?(smontagu) → review+
Attachment #172963 - Flags: superreview?(neil.parkwaycc.co.uk)
Attachment #172963 - Flags: superreview?(neil.parkwaycc.co.uk) → superreview+
Comment on attachment 172963 [details] [diff] [review] Sort using localeCompare. mozilla/xpfe/components/prefwindow/resources/content/pref-languages.js 1.35
Assignee: bugs → jerfa
Fixed. I'll file a new bug with a suggestion to speed up the Add Languages dialog when it's ready.
Status: NEW → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → FIXED
Hello. I have filled bug 300759, which seems to be a regression of this one in Firefox 1.1. Can anyone confirm this? If it's a regression, how must we do? Mark a dependency between bugs or mark mine as duplicate and reopen this one?
(In reply to comment #9) > Hello. I have filled bug 300759, which seems to be a regression of this one in > Firefox 1.1. It's a separte bug. Apparently, Ben didn't incorporate the fix for this bug when he mass-landed his ff 1.1 work as happended in several other cases.
You need to log in before you can comment on or make changes to this bug.