That sounds good!
Anyway, a friend of mine kindly offered me his spare time to help about translation stuff. Which part is good to start? He understands both Squeak programming and gettext architecture. I think separating the translations into chunks is what we have to try at first (I myself haven't read gettext documentation in detail yet though).
Cheers, - Takashi
Hilaire Fernandes wrote:
That would be really great !!
Hilaire
2007/7/4, Bert Freudenberg bert@freudenbergs.de:
Yes, that's what I meant. So for a string in a method of a class in category "Foo-Bar" we would look at "Foo.mo". Or, for even more sophistication, look for "Foo-Bar.mo" first, and if that does not exist look in "Foo.mo".
On Jul 2, 2007, at 13:37 , Michael Rueger wrote:
Bert and I just had a chat about this :-)
Our thoughts were:
- separate the translations into chunks by SystemCategory
- generate an initial set of gettext files from the current language
editor files
- use the comments in gettext to add class>>selector>>line nr
- on a new release write out a new set of templates
- then use gettext tools, diff etc to maintain the translation files