[Etoys] How do we want to translate project?

[Korakurider]

--- Bert Freudenberg <bert at freudenbergs.de> wrote:
> We don't need to split I think (unless translators
> want us to), but
> we will have additional pots (for projects,
> quickguides, add-on apps
> like BotsInc, DrGeo2 etc)
  I am confused here:  You implemented so that TextMorph can have
translated labels as properties and user can edit them, right?  I have
been assuming the functionality will be used for translating project
by communities and for preloaded contents.  So what problem do we want
to solve by implementing another one, and what road map are you
thinking?

And I am not sure whether gettext-based translator is good for base of
contents translation:
+ Gettext looks up translation by original text and "context" where
the text is used in code.
   The context is actually class category or method category and both
don't fit well for
   Morph instances in project.
+ I think translation for contents should be able to be dynamically
and easily modified by users.  Your tweak on TextMorph is great for
this.  Compiled MO format seems too static and rigid.

/Korakurider