[Etoys] Localization guidelines for a developer

[Korakurider]

Hi, Ben.

On Feb 10, 2008 1:35 PM, Ben Goetter <goetter at mazama.net> wrote:
> Folks,
>
> As an eToys/Squeak project developer, what should I be doing to ensure
> that my project is easily localizable?  Do we have a set of conventions
> that I can follow?
>
> I gather that eToys doesn't use NaturalLanguageTranslator, so I suppose
> that (e.g.)
>     'Syntax error on line {1}' translate format: { linenumber }.
> isn't what I want.
>
> How does gettext work from the Squeak perspective?

NLS in old version is squeak is basically a dictionary with preloaded
translation data.
The new engine "GetTextTranslator" use gettext emulation object "MOFile"
that dynamically read translation data from MO into internal dictionary.
>From user 's perspective those are very similar.  Actually, in current
version of Etoys both GetTextTranslator and InternalTranslator
(refactored from legacy NLS) inherit common abstract class
NaturalLanguageTranslator and share some interfaces.
You could review these in Etoys source code.

So the code:
 'Syntax error on line {1}' translated format: { linenumber }.
will work with both gettext based translation and legacy NLS.

What has not been built yet is the facility to translate user objects
in project (*.pr) ,
translate text of Morph instances for example.

I might not be able to understand what you are worrying very well.
So please ask again with more detail if you want...

Cheers,
/Korakurider