[Etoys] Missing Strings for Localization?
korakurider at gmail.com
Tue Mar 11 12:02:25 EDT 2008
On Wed, Mar 12, 2008 at 12:07 AM, Gerhard Steiner <gd.steiner at gmx.at> wrote:
> > > Is there something I should have checked before sending these message?
> > > Maybe I have missed something and just didn't get these strings
> > > into my system?
> > German PO seems to have a few strings marked as fuzzy. Fuzzy string
> doesn't appear in compiled MOs.
> > So you should review and finalize them (e.g. clear fuzzy)
> The etoys.mo has been compiled from an actual etoys.po from Pootle (3660
> strings all without "fuzzy").
Really? Right now Pootle shows German PO including 1138 fuzzy words.
> The resulting etoys.mo has been copied
> into the german lang- directory in my local etoy-directory.
> I can see the translation strings from pootle in an running etoy-image.
> The squeak/etoy language-editor for says: "4526 phrases 2371 translated
> 2155 untranslated". The translation strings from pootle doesn't show up
> in the internal language-editor. The translation strings from the
> internal language-editor doesn't show up on pootle.
Current Etoys implementation has two translation engines.
+ newly implmented one with gettext emulation called "GetTextTranslator".
the engine dynamically load translation data from MO.
+ legacy one called "InternalTranslator" (that have been named
"NaturalLanguageTranslator" in older version of Squeak). translation
data is managed in image persistently.
Etoys dynamically choose translation engine/dictionary on run time:
If MO is installed for some language etoys use gettext for the langauge.
If you want to verify how some phrase will be translated,
open Workspace in Etoys and evaluate:
The LanguageEditor in Squeak work only with InternalTranslator. So
you can't see translations from MO there.
> What's the best way to merge these translations into one single german
> How to resolve conflicts between these "versions" and bring them back up
> to pootle?
Our thought was Etoys will use only gettext based translation (in
typical usage at least).
Our translation effort for Etoys will be only toward to gettext
based engine and on Pootle. Though we still keep translation data
in-image for InternalTranslator, I don't think we will do significant
maintenance for that. We export all of translations in
InternalTranslator and load to Pootle when we started work there.
So I don't think you would need to care about in-image translations.
(note that I am speaking only for Etoys, not for squeak3.9 and
following versions that are still with legacy translation engine)
> >> In theory, Pootle will merge newer etoys.pot to all of PO.
> >> But it hasn't been executed for several months because
> >> etoys.pot/po are too big for Pootle to process.
> >> Admins are working to fix it, so stay tuned...
> When will that happen?
Let me check...
More information about the etoys-dev