LanguagePacks
|
Size: 1382
Comment:
|
← 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 1: | Line 1: |
| <<Include(TranslatingUbuntu/Header)>> | <<Include(Translations/Header)>> |
| Line 3: | Line 3: |
| 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. |
||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<TableOfContents>>|| |
| Line 11: | Line 5: |
| The complete lifecycle of translations (import, maintenance, export, and language pack structure) is '''described on TranslationLifecycle'''. |
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. |
| Line 14: | Line 7: |
| You can check the latest language packaged (.mo files) from [[https://launchpad.net/~ubuntu-langpack/+archive || Language Pack PPA ]]. | * You can check the latest language packaged (.mo files) from the [[https://launchpad.net/~ubuntu-langpack/+archive |Language Pack PPA ]]. |
| Line 16: | Line 9: |
| You can get the source langauge packs (.po files) from [[https://translations.edge.launchpad.net/ubuntu/jaunty/+language-packs | Language packs for Jaunty ]] | * You can get the source language packs (.po files) from the [[https://translations.launchpad.net/ubuntu/oneiric/+language-packs | Oneiric language pack tarballs ]]. |
| Line 18: | Line 11: |
| == Translations in Rosetta but not included in lang-packs == | ||<tablestyle="width:100%;" style="width: 40px; background-color: #565248;text-align: center;">{{attachment:Translations/info.png}}||<style=" text-align: left;" >The complete lifecycle of translations (import, maintenance, export, and language pack structure) is described on '''TranslationLifecycle'''|| |
| Line 20: | Line 13: |
| || '''Name''' || '''Contact''' || '''Notes''' || || Ubuntu / Kubuntu / Xubuntu /Edubunu Docs || Matthew East || The are manualy extracted from Rosetta and converted to xml by Matthew East || || Firefox / xulrunner || Alexander Sack || || || Ubuntu Start Page || Matthew Nuzum or AdiRoiban || || || Debian Installer || Colin Watson || || || OpenOffice.org || Chris Cheney || || |
== 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 * [[https://dev.launchpad.net/Translations/LanguagePackSchedule|Export schedule]] * 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]] * Some templates are not included in language packs. More is listed on the [[NonLanguagePackTranslationDeadline]] page. ---- CategoryTranslations |
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)