A new work flow and documentation for i18n and l10n of applications
Provide a new work flow and documentation for developers to assure that new Ubuntu applications are fully internationalized and "localizable".
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Milo Casagrande
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Discussion
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
Whiteboard
--- gobby doc ---
Facts:
- two new applications were inserted in intrepid
- one of this application is installed by default
- none of them were translatable before the release
Find a way to interact with developers and translators.
Propose a i18n blocker to developers: all the end-users application that get into main
should be i18n compliant. (it should be already, but looks like it's not documented anywhere)
Propose:
- create a document that help developers know i18n and l10n differences
- problem with upstream documents
- collect on the wiki links that detail how to do i18n for applications
allow only i18n GUI applications in main
- if the apps has no i18n support add a bug and push for i18n support upstream or in the ubuntu community
- be careful with exceptions !!!!
l10n general guide-
- written in english
- translated in each language
- available in rosetta
- assigned to Launchpad Translation Standard
- containing common infos and policies
- push people to trandlate upstream
- link to another page for each languages specific topic
- available in a central place - wiki.ubuntu.com or create a new page in an l10n porta
l10n guide team specific
- outsourced