Really what is needed here are people fluent in two languages. The problem is that this approach imposes aadditional limitations, such as that they must be familiar with subversion, and not intimidated by things like java property files.
If you could find a way that non-devs could *easily* contribute translation files, I suspect this would be a much faster process. Ian. On 3/31/07, Florent Daigni?re (NextGen$) <nextgens at freenetproject.org> wrote: > Hi, > Today I've commited what will be our "base framework" for > internationalization... Review/comments are welcome. > > Help too :p > > In a first time we probably want to translate only what is visible > on fproxy; even if we limit us to that, it's still a fair amount of > work. > > All the framework stands in > https://emu.freenetproject.org/svn/trunk/freenet/src/freenet/l10n/ > Translations files will be UTF-8 encoded and kept in java > properties files... > > The first task is to externalize strings... is there a special > naming convention for keys ? I mean does ClassName.whatever fits > the purpose or should we look for something a bit more evolved ? > > NextGen$ > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.6 (GNU/Linux) > > iD8DBQFGDvkbU/Z/dHFfxtcRAh6gAKC2vjZV/qS1Yn5q9jKPitGIJ1iKOACgqsjO > rSJl6LlawnTOezfB62wuOl0= > =AUKB > -----END PGP SIGNATURE----- > > _______________________________________________ > Devl mailing list > Devl at freenetproject.org > http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl > -- Founder and CEO, Thoof Inc Email: ian at thoof.com Office: +1 512 524 8934 x 100 Cell: +1 512 422 3588 AIM: ian.clarke at mac.com Skype: sanity
