User:Mstone/Notes/Localization 1: Difference between revisions

From OLPC
Jump to navigation Jump to search
mNo edit summary
mNo edit summary
 
(3 intermediate revisions by the same user not shown)
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.

; Locales of Present Interest

en_US (English: America)

es_PE? (Spanish: Peru, Uruguay, Mexico, Colombia?, Argentina?, Panama?, Equitorial Guinea?)
es_UY
es_ME

mn_MN? (???: Mongolia)

fr_RW? (French: Rwanda, Senegal?)
fr_???

ar_IQ (Arabic: Palestine, Iraq, Egypt?)
ar_LB

ht_HT (Kreyol: Haiti)
am_ET (Amharic: Ethiopia)
kh_CA? (Khmer: Cambodia)
fa_AF (Dari: Afghanistan) (prs_AF)
??? (???: Thailand)
hi_HI (Hindi: India)
pt_BR (Portuguese: Brazil)
??? (Oceania)
it_IT? (Italian: Italy)
??? (Turkey)

http://en.wikipedia.org/wiki/List_of_ISO_639-2_codes

Latest revision as of 00:03, 24 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.

Locales of Present Interest
   en_US    (English: America)
   es_PE?   (Spanish: Peru, Uruguay, Mexico, Colombia?, Argentina?, Panama?, Equitorial Guinea?)
   es_UY
   es_ME
   mn_MN?   (???: Mongolia)
   fr_RW?   (French: Rwanda, Senegal?)
   fr_???
   ar_IQ    (Arabic: Palestine, Iraq, Egypt?)
   ar_LB
   ht_HT    (Kreyol: Haiti)
   am_ET    (Amharic: Ethiopia)
   kh_CA?   (Khmer: Cambodia)
   fa_AF    (Dari: Afghanistan)   (prs_AF)
   ???      (???: Thailand)
   hi_HI    (Hindi: India)
   pt_BR    (Portuguese: Brazil)
   ???      (Oceania)
   it_IT?   (Italian: Italy)
   ???      (Turkey)

http://en.wikipedia.org/wiki/List_of_ISO_639-2_codes