LanguagePacks
|
Size: 1296
Comment:
|
Size: 3663
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| <<Include(TranslatingUbuntu/Header)>> | ## page was copied from TranslatingUbuntu/LanguagePacks <<Include(Translations/Header)>> |
| Line 3: | Line 4: |
| 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 6: |
| 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 8: |
| You can check the latest language packaged (.mo files) from [[https://launchpad.net/~ubuntu-langpack/+archive || Language Pack PPA ]]. | The complete lifecycle of translations (import, maintenance, export, and language pack structure) is '''described on TranslationLifecycle'''. |
| Line 16: | Line 10: |
| 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 check the latest language packaged (.mo files) from the [[https://launchpad.net/~ubuntu-langpack/+archive || Language Pack PPA ]]. |
| Line 18: | Line 12: |
| == Translations in Rosetta but not included in lang-packs == | You can get the source language packs (.po files) from [[https://translations.edge.launchpad.net/ubuntu/jaunty/+language-packs | Language packs for Jaunty ]]. |
| Line 20: | Line 14: |
| * Ubuntu / Kubuntu / Xubuntu /Edubunu Docs - The are manualy extracted from Rosetta and converted to xml my Matthew East * Firefox / xulrunner - Manualy extracted by Alexander Sack * Ubuntu Start Page - Manualy extracted and sent to Ubuntu sysadmin. Contact Matthew Nuzum or AdiRoiban * OpenOffice |
== 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: == Translations in Rosetta but not included in language packs == There are a couple of exceptions for translations done using Rosetta but not included or updated via language pack. Those translations are Ubuntu Documentation, Ubuntu Start Page and other tools only available on the Live CD or install media. Please see the following list: || '''Name''' || '''Contact''' || '''Update notes''' || || ubuntu-docs || MatthewEast or AdiRoiban || The are manualy extracted from Rosetta and converted to xml by Matthew East <<BR>> Usually there are 2 updates per cycle and before an export there is an announcement on the ubuntu-translators mailing list || || kubuntu-docs || [[nixternal|Richard A. Johnson]] || || || xubuntu-docs || [[j1mc|Jim Campbell]] || || || edubunu-docs || JordanMantha || || || installation-guide || ColinWatson || currently not updated || || Ubuntu Start Page || MatthewNuzum or AdiRoiban || Sparse updates, there is an announcement on the ubuntu-translators mailing list before an export || || Debian Installer and other install tools || Colin Watson || || || OpenOffice.org || ChrisCheney || || || ubuntu-wallpapers || || || ## || Firefox / xulrunner || AlexanderSack || || ## Firefox is included in language packs, but if there is problem with the Firefox language extension generation, Alexander can be contacted More is listed on the [[NonLanguagePackTranslationDeadline]] page. == 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.edge.launchpad.net/ubuntu/jaunty/+language-packs|language pack packages]] ---- 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.
The complete lifecycle of translations (import, maintenance, export, and language pack structure) is described on TranslationLifecycle.
You can check the latest language packaged (.mo files) from the https://launchpad.net/~ubuntu-langpack/+archive.
You can get the source language packs (.po files) from Language packs for Jaunty.
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:
Translations in Rosetta but not included in language packs
There are a couple of exceptions for translations done using Rosetta but not included or updated via language pack.
Those translations are Ubuntu Documentation, Ubuntu Start Page and other tools only available on the Live CD or install media. Please see the following list:
Name
Contact
Update notes
ubuntu-docs
The are manualy extracted from Rosetta and converted to xml by Matthew East
Usually there are 2 updates per cycle and before an export there is an announcement on the ubuntu-translators mailing listkubuntu-docs
xubuntu-docs
edubunu-docs
installation-guide
currently not updated
Ubuntu Start Page
Sparse updates, there is an announcement on the ubuntu-translators mailing list before an export
Debian Installer and other install tools
Colin Watson
OpenOffice.org
ubuntu-wallpapers
More is listed on the NonLanguagePackTranslationDeadline page.
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
Translations/LanguagePacks (last edited 2011-10-07 02:42:10 by jbicha)