The current Language/Region lists currently installed language packs. We can enhance that list or create another list to show more languages. That allows the user to set up international related preferences at once instead of changing them manually (note that there are several prefs has to be set, auto-detection, default charset, accept language, etc...). We also need a backend i18n support to take xp-locale and set preferences for that locale.

-> jbetak The current list only displays installed packs. Enhancing the functionality to locale-related pref switching sounds like a good idea, but it might be quite challenging to convey those two separate functions in the UI. Same goes for a separate list. I will try to work on this, but currently I's tend to think that designing a dynamically built list (based on language packs available online from an FTP source directory) might be something worth looking at. Selecting an item in this list, would download and install the pack and switch locale-specific preferences.

Hi, Naoki: All the i18n prefs settings mentioned here are in the language packs. How's this request different from downloading and installing the required language pack and then selecting it as the locale provider?

This is for languages which do not have lang pack available. And for the users who just want to set several intl defaults at once but not want to download and use localized UI.

i18n triage team: nsbeta1-

reassigning

MASS-CHANGE: This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614

MASS-CHANGE: This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago. Because of this, we're resolving the bug as EXPIRED. If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component. Query tag for this change: EXPIRED-20100420