Developer education on localization
Creation of a central resource for developers to learn how to get their applications and packages localized, where both general information on internationaliz
Blueprint information
- Status:
- Complete
- Approver:
- Jono Bacon
- Priority:
- Medium
- Drafter:
- David Planella
- Direction:
- Approved
- Assignee:
- David Planella
- Definition:
- Approved
- Series goal:
- Accepted for maverick
- Implementation:
-
Implemented
- Milestone target:
-
ubuntu-10.10
- Started by
- David Planella
- Completed by
- David Planella
Whiteboard
Work items for maverick-alpha-2:
[henninge] Define best practices in setting up a project for translation in Launchpad: DONE
[dpm] Integrate the documentation on recommended practices on setting up a project for translation in Launchpad in dev.launchpad.net or on the i18n guide: DONE
[adiroiban] Investigate the new "build to branch" process and see how it will affect translations: DONE
[adiroiban] Document the new "build to branch" process: DONE
[dpm] Talk to dholbach about how developers generally expect documentation or learning material (docs, code samples, etc): DONE
Work items for maverick-alpha-3:
[knitzsche] Work with henninge and review and write the documentation on recommended practices on setting up a project for translation in Launchpad: DONE
[knitzsche] Look a the C and Python section examples in the coding section of the i18n guide, provide links to upstream documentation: DONE
Work items for ubuntu-10.10-beta:
[dpm] Review and complete https:/
[dpm] Gather feedback from developers on the structure and content: POSTPONED
[dpm] Provide recipes for the most common internationaliz
[dpm] Provide code snippets for the most common internationaliz
[dpm] Ensure that application framework tools such as quickly follow these practices and allow seamless creation of internationalized applications. Translations should "just work": POSTPONED
Status:
* Best practices document by henninge at https:/
* knitzsche: Internationaliz
Session notes:
* Translations from a technical point of view are documented in a very scattered way
* Easy point of entry that covers the basics and then point to the general documentation
* Recipes:
* Build from branch, a branch is pushed, a package is built and a template is automatically generated
* Links to already set projects: hello-world
* Create a ubuntu-hello-world
* Examples:
* A ubuntu-hello-world project with several branches, each with each type of build infrastructure. Concentrate only on the most common ones.
* New sections or sections to document:
* Internationaliz
