LanguagePacks
Size: 2463
Comment: Added info note
|
← Revision 30 as of 2011-10-07 02:42:10 ⇥
Size: 2456
Comment: point to oneiric instead of karmic
|
Deletions are marked like this. | Additions are marked like this. |
Line 9: | Line 9: |
* You can get the source language packs (.po files) from the [[https://translations.edge.launchpad.net/ubuntu/karmic/+language-packs | Karmic language pack tarballs ]]. | * You can get the source language packs (.po files) from the [[https://translations.launchpad.net/ubuntu/oneiric/+language-packs | Oneiric language pack tarballs ]]. |
Line 27: | Line 27: |
* They are used as a basis for [[https://launchpad.net/langpack-o-matic|langpack-o-matic]] to generate the [[https://translations.edge.launchpad.net/ubuntu/karmic/+language-packs|language pack packages]] | * They are used as a basis for [[https://launchpad.net/langpack-o-matic|langpack-o-matic]] to generate the [[https://translations.launchpad.net/ubuntu/oneiric/+language-packs|language pack packages]] |
Unlike other distributions we do not ship upstream translations from source packages directly in binary application packages in main and restricted, since this does not allow us any flexibility in editing them on a central place (Launchpad), update them independently from the applications, and update them post release. That is why we separate packages and their translations in Ubuntu and maintain/package them independently.
You can check the latest language packaged (.mo files) from the Language Pack PPA.
You can get the source language packs (.po files) from the Oneiric language pack tarballs.
The complete lifecycle of translations (import, maintenance, export, and language pack structure) is described on TranslationLifecycle |
Inclusion conditions
- All packages that generate .mo files in a compile time configurable location ($LOCALEDIR) will be included in lang-packs.
- Only packages from the 'main' repository are included in language packs.
Package maintainer notes
The package maintainer will only need to check if, at compile time, the package generates a .mo file in a preconfigurable location. He will upload the package just like a normal one, and the language pack script will take care of everything else.
Those packages which are imported in Rosetta but do not generate .mo files in a standard location will have to be manually exported by the package maintainer. Examples:
Generation
- Language pack tarballs get periodically exported from Launchpad
They are used as a basis for langpack-o-matic to generate the language pack packages
Some templates are not included in language packs. More is listed on the NonLanguagePackTranslationDeadline page.
Translations/LanguagePacks (last edited 2011-10-07 02:42:10 by jbicha)