LocalesThatDontSuck
789
Comment: Mention BreezyFirefoxStartPageTranslation
|
1885
Provide more details
|
Deletions are marked like this. | Additions are marked like this. |
Line 19: | Line 19: |
In order to server our user communities better, we need to be more responsive and proactive with localisation updates. There are two solutions proposed here: 1) Switch to using the belochs locales packages. 2) Use the belochs locales packages to seed Rosetta, and generate all localisation information from Rosetta. |
|
Line 20: | Line 26: |
Getting locale changes into upstream glibc is unnecessarily hard. The glibc maintainer (correctly) requires proof of the correctness of a change before it's included, but the onus of demonstrating that change falls to the glibc package maintainers. The package maintainers are frequently not qualified to provide this proof, and cannot answer upstreams questions to the needed degree of satisfaction. The glibc upstream maintainer also has a well deserved reputation for being difficult to approach with changes. |
|
Line 23: | Line 33: |
* Agloolik lives in Iqaluit, Nunavut, Canada and has been using Rosetta to do translations, but wants his gnome calendar to correctly use Sunday as the first day of the week. |
|
Line 24: | Line 36: |
* Locales / Belocs-locales packaging * Langpacks * Rosetta |
Created: Date(2005-09-26T18:35:38Z) by JeffBailey
Priority: NeedsPriority
People: JeffBailey, JordiMallach
Contributors: JeffBailey
Interested: MartinPitt
Status: UbzSpecification, BrainDump (then DraftSpecification then EditedSpecification then ApprovedSpecification), DistroSpecification
- Branch:
- Malone bug:
- Packages affected: locales, langpacks
- Depends:
- Dependents:
- BoF sessions: none yet
Summary
In order to server our user communities better, we need to be more responsive and proactive with localisation updates. There are two solutions proposed here:
1) Switch to using the belochs locales packages.
2) Use the belochs locales packages to seed Rosetta, and generate all localisation information from Rosetta.
Rationale
Getting locale changes into upstream glibc is unnecessarily hard. The glibc maintainer (correctly) requires proof of the correctness of a change before it's included, but the onus of demonstrating that change falls to the glibc package maintainers. The package maintainers are frequently not qualified to provide this proof, and cannot answer upstreams questions to the needed degree of satisfaction. The glibc upstream maintainer also has a well deserved reputation for being difficult to approach with changes.
Use cases
* Agloolik lives in Iqaluit, Nunavut, Canada and has been using Rosetta to do translations, but wants his gnome calendar to correctly use Sunday as the first day of the week.
Scope
* Locales / Belocs-locales packaging
* Langpacks
* Rosetta
Design
See also BreezyFirefoxStartPageTranslation.
Implementation
Code
Data preservation and migration
Outstanding issues
BoF agenda and discussion
LocalesThatDontSuck (last edited 2008-08-06 16:38:19 by localhost)