[Localization] Localization: What works and what does not (Sayamindu Dasgupta)

Carlo Falciola cfalciola at yahoo.it
Wed Dec 16 12:55:28 EST 2009


My 1/2 cent:
1. Context: many times is difficult to get the right term because the original one is out of context and the original language term has multiple translations with different meanings depending on context, so 
 
1.1 adding context information, if is possible, ease, accelerate, and reduce errors.  (es. "play" in english has several reasonable translation in italian: as noun "gioco", "opera teatrale", ...;  as verb. "giocare", "suonare", "eseguire", "recitare"....)
1.2 avoid big chunks of strings: it takes time to figure out from where any string belongs, many time could happen the same same strings get repeated in the software and it should belong to different translations because of the contexts..(es. etoys has 1 file, 27454 words 4412 strings)  

2. on the process side it would be useful to have back information on when the strings (or .po file granularuty) actually landed in releases.
(where they should be in GIT would be an intermediate useful information too)

3. probably the translator nirvana would be to be able to have the option to translate "in place" the strings that has more heavy space constrains in the GUI.

ciao carlo 


      



More information about the Localization mailing list