LanguagePacks
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 https://launchpad.net/~ubuntu-langpack/+archive.
You can get the source langauge 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 main repository are included in lang-packs.
Package maintainer notes
The package maintainer will only need to check if, at compile time, the package generates .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.
Translations in Rosetta but not included in lang-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 / Kubuntu / Xubuntu /Edubunu Docs
Matthew East or AdiRoiban
The are manualy extracted from Rosetta and converted to xml by Matthew East
Usualy there are 2 updates per cycle and before an export there is an announcement on the ubuntu-translators mailing listFirefox / xulrunner
Alexander Sack
Ubuntu Start Page
Matthew Nuzum 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
Chris Cheney
Package maintainer notes
Those packages that are imported in Rosetta but does not generated .mo files in a standard location will have to be manualy exported by the package maintainer.
Subpages |