L10n:Multi-Locale Installs: Difference between revisions
(Setting up a playground for multiple locale installations) |
m (that spelling error was a little too prominent :)) |
||
| Line 1: | Line 1: | ||
This page should eventually move over to a Firefox page, once the corresponding tasks have been cornered and triaged. | This page should eventually move over to a Firefox page, once the corresponding tasks have been cornered and triaged. | ||
== | == Scenarios == | ||
In a international environment, system administrators would want to install Firefox or other Mozilla products in several languages, and the actual language used by each user should be either | In a international environment, system administrators would want to install Firefox or other Mozilla products in several languages, and the actual language used by each user should be either | ||
* taken from the OS or | * taken from the OS or | ||
* bootstrapped from the OS. | * bootstrapped from the OS. | ||
An alternative | An alternative scenario would be extension developers, who would like to easily test localizations of their extension. Hopefully, this should work reliably without having each localization as standalone install. A mere option to call the Profile Manager with a -UILocale should be enough to create according testing profiles. | ||
== TODOs == | == TODOs == | ||
| Line 14: | Line 14: | ||
=== Language selection === | === Language selection === | ||
I don't see locale switching as the main usage | I don't see locale switching as the main usage scenario here. If it has to be, we should be able to just bootstrap our locale selection by currently selected locale in the OS, and if that is not available, default to the locale of the installer. | ||
Comments? | Comments? | ||
Latest revision as of 19:38, 9 August 2005
This page should eventually move over to a Firefox page, once the corresponding tasks have been cornered and triaged.
Scenarios
In a international environment, system administrators would want to install Firefox or other Mozilla products in several languages, and the actual language used by each user should be either
- taken from the OS or
- bootstrapped from the OS.
An alternative scenario would be extension developers, who would like to easily test localizations of their extension. Hopefully, this should work reliably without having each localization as standalone install. A mere option to call the Profile Manager with a -UILocale should be enough to create according testing profiles.
TODOs
Installation
Installation should be easy. This may, some day, lead to goodness for the installer, too, requiring CDs to only hold one of them, and enable us to ship more locales for less. Anyway, installing a langpack should be as easy as to drop it in the build, at the right place.
Language selection
I don't see locale switching as the main usage scenario here. If it has to be, we should be able to just bootstrap our locale selection by currently selected locale in the OS, and if that is not available, default to the locale of the installer.
Comments?