m.rueger at acm.org
Mon Jul 2 07:37:53 EDT 2007
Takashi Yamamiya wrote:
> Hilaire Fernandes wrote:
>> The problem using Gettext with Squeak, is that Gettext is not its
>> native system for translation. When using Gettext with GNU application
>> you benefice from the its tool suite: when messages are updated, it is
>> able to mark changed messages as fuzzy and/or to propose a closer
>> match. I don't know if it is applicable to Squeak, and what is
>> necessary to do to make the best use of the whole gettext tool suite.
> That's interesting. We should have those feature.
>> Regarding translation, another stuff it will be nice is language
>> catalogue per Squeak Application. It is not unrealistic
>> people/organisation/vendor will develop Squeak application (applet,
>> extension or whatever it should be nammed) for the OLPC.
>> In this case this organisation will also need to ship language
>> catalogue with their Squeak Application. It is also what Gettext
> That's a good idea. What's your definition of Squeak Application? I
> think a .pr whould be a good unit.
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
- 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
(Bert please correct/add where necessary)
This is a pretty well defined chunk of work, that could be handed off to
More information about the Etoys