2011/5/20 mart <[email protected]> > not sure if this applies, but just in case... > > years ago (i think 12, so this may be outdated), i worked in a > localization team, (although it was a purely windows shop where words > like dll was all that anyone talked about). Anyways, we adopted a > method for 1) re-using translations (from translation tool kits (aka. > TTKs) 2) standardizing on commonly accepted strings (i.e. there aren't > too many ways to translate a yes/no button ;)) & 3) the language > specific string tables would grow over time and served the task very > well considering... (we only had 4 or 5 languages ;) english, swedish, > japanese, simplified chinese, and french (fr_ca was deemed unworthy at > the time ;)) > > anyways, the moral is, that all strings going to UI were ripped out of > the code and replaced with IDs where the users language selection > would force load the language specific "satellite dll" @ run time - > was just a dll with the resource strings in it. > > perhaps adopting something similar (but no dll's ;) ) would be > beneficial? > > Mart :) > > > Hi Mart,
Thank you for sharing this experience. I guess you had the professional resources to do all the translations. If we use a common dictionary for web2py, we need all the translations for the languages we support for all the words before doing a new release. Do we have to resources to do that? I have some doubts. -- A+ ------------- Pierre My blog and profile (http://pierrethibault.posterous.com)<http://pierrethibault.posterous.com> YouTube page (http://www.youtube.com/user/tubetib)<http://www.youtube.com/user/tubetib> Twitter (http://twitter.com/pierreth2) <http://twitter.com/pierreth2>
