Is very hard for a common user to understand what you decide in the "Language/Region Selection" dialog. There needs to be a way better description of what is going on, and how the user fx changes this to something else in the future.

*** Bug 44069 has been marked as a duplicate of this bug. ***

Comment from bug 44069: The button is called "Region Selection...". The title of the dialog is called "Language/Region Selection" and the text says "Select UI Language and Region Content". No wonder the user gets confused...

Ok let's get this fixed. I definitely agree that the text in this dialog is perfect, and can lead to confusion. I had to translate this for the French localization of Mozilla, and honestly I had a hard time finding something that would reflect perfectly what this dialog is for. So far, the locales are mostly translations, I don't think any locale package includes any region setting (or am I wrong), so why not use "Local settings" or "Lang packages" "Region Selection" for the button in the profilemanager is silly because mainly it's about language, not region. Since most end-users do not know what a UI is, I suggest changing UI to "User Interface" or to a more basic "The selected language will be used for the User Interface" Tell me what you think, it would be cool to have a great dialog here. Mainly for foreign users. Fabian.

Nominating for 0.9, or failing that, 1.0.

Nominating for nsbeta1. After a Recommended install, the following 2 choices appear for selecting UI Language and Regional Content: English (US) US Region A user is not going to know what to do with these choices; most would probably interpret this as a selection between a language and region, not between languages or regions. This obviously needs to be split up so as to not confuse the user. Bug 65253 seems related.

John - The seperation of the language UI from the content packs should address this issue, and close it. User should be able to "Set Language" or "Set Content" separately.

I'm marking this one as dependent on Bug 65241; also adding Asa to the cc: list. What is clear is that the current UI is very confusing. In Profile Manager, the user is given the option to change Region Selection. As I wrote earlier, a Recommended Install provides the options of English (US) and US Region. We also have the same options when going to View>Set Language/Region. Here are some scenarios I see for resolving this issue: 1) In View menu, have only a "Set Region" option; in Profile Manager, have only a "Set Language" option. As we have a "Download More" option for the current "Set Language/Region" selection, we would have to figure out how to split this up as well. 2) Have "Set Region" and "Set Language" options in both Profile Manager and the View menu. I can see a lot of arguments for and against this. 3) Have a "Set Region" and "Set Language" option in the View menu; have only "Set Region" in the Profile Manager (as is currently the case)--it appears to me that the current debate in Bug 65241 is focused only on this idea. 4) Have a "Set Region" and "Set Language" option in the View menu; have only "Set Language" in the Profile Manager. Other ideas? The main thing I want to convey is that having (for example) English (US) and US Region together in one place is much too confusing, and must be split up.

nav triage team: Reassigning to mcarlson to figure who can work on this since navigator team is overloaded.

Our team doesn't do UI work. We only translate the product. Not sure who to reassign this to. Does anyone have any ideas who this should be reassigned to?

Assigning to German. German - Pls upload your UI spec for review, and see if it works for this issue.

Latest Ui designs are published at http://www.mozilla.org/projects/ui/communicator/framework/langcontentui/ bug 65241 I believe describes the motivation/background

reassigning.

this bug is still valid. Where do the profile manager get the "(us)" from?

ups wrong bug. sorry...

Mass reassign of my non-Firefox bugs to ben_seamonkey@hotmail.com

"Region Selection" has been obsoleted by bug 325473 now, as content packs are history on trunk now. This also means that this bug is fixed, finally.