On a multiuser install i have to install the en-US application version to have en-US and so all other users would have en-US as default locale. Existing profiles could be fixed by installing the other locales as global extension, but for new profiles i have to manipulate the default settings for a new profile. Especially for computers which are used by the public and employees, having multiple language packs including en-US without side-effects for other users. Please provide again en-US language packs. cf_: because they were evil and would break installs cf_: because they had a whole lot more stuff in them than just the en-US strings

FWIW, the language packs are currently created during the l10n repackaging process. We should probably teach the main build to produce the en-US language pack.

It would be nice if this can be done for all Mozilla products with language packs (or at least everything 1.0+ which is recommended for production, so including Thunderbird).

Is it complicated to fix ?

To underline what a mess this is, here is a description of the only work-around that I am aware about: 1. Install the en-US version of Fx. If a localized version was already installed, you have to install it over the existing version. Any existing profiles will keep their locale, but new ones will default to en-US. 2. Install a localized version of Fx over the previous en-US install. You cannot just install a language pack, because that will not change the default profile language. So if a localized version was already there, or you accidentally installed a localized version, you end up with THREE full installs over eachother. Some of the (potential) problems: - What could have been solved with one small download for an en-US language pack, now has to be done with one or two (depending on your starting situation) additional full downloads of Fx. This can be a major problem if you don't master the foreign language, since the full install is also localized. - I do now know what the user-right requirements are for installing a language pack versus a full install, but I can image a full install requires more rights than installing a language pack. - What happens when there are updates to the en-US language resources? Again I have no experience here, but a language pack might give an alert that an update is available, but you will not get any alert for an en-US update that has been overwritten by a localized install. - I would speculate (again) that doing full installs, especially over an existing localized install, has far more potential of messing things up than just installing a language pack.

Back to the future.