User:Mstone/Notes/Localization 1: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
mNo edit summary |
||
| Line 1: | Line 1: | ||
In order to qualify a release for a locale, we must ''consider'' whether we "have |
In order to qualify a release for a locale, we must '''consider''' whether we "have |
||
correct <noun>" or / "can correctly <verb>" each of: |
correct <noun>" or / "can correctly <verb>" each of: |
||
| Line 27: | Line 27: | ||
* ??? |
* ??? |
||
A separate issue which must be agreed upon by all of us is which of these items are ''necessary'' to qualify a build and keyboard for deployment at scale XXX. |
A separate issue which must be agreed upon by all of us is which of these items are '''necessary''' to qualify a build and keyboard for deployment at scale XXX. |
||
Revision as of 23:51, 23 July 2008
In order to qualify a release for a locale, we must consider whether we "have correct <noun>" or / "can correctly <verb>" each of:
- (hw)
- power adapters
- certifications
- keyboard silkscreening
- ???
- (software)
- keyboard maps for X + the Linux virtual terminals
- locale/collation data
- render text in the correct direction
- layout complex orthography
- free fonts
- input methods
- multi-language configuration
- translations of the UI and important pieces of content
- dictionaries + spellchecking
- 'sensitivity' checks for offensive words/concepts
- QA resources sufficient to maintain these items according to our software support policies for the release.
- (misc)
- deployment guide
- issue escalation path
- country-provided rollout plan??
- ???
A separate issue which must be agreed upon by all of us is which of these items are necessary to qualify a build and keyboard for deployment at scale XXX.