[etoys-dev] Etoys: GetText-Richo.9.mcz
richi.moran at gmail.com
Fri May 28 10:02:57 EDT 2010
Most of the phrases in the english locale are empty, so they will fall into
the "no translation found" case all the time. Maybe we should just fill the
english po file. I haven't tested in a XO but I think iterating through all
domains is fast enough if the cases are few.
On Fri, May 28, 2010 at 5:42 AM, Bert Freudenberg <bert at freudenbergs.de>wrote:
> On 28.05.2010, at 06:01, Ricardo Moran wrote:
> > Yes, I found a couple of strings in english po that have different
> translations. I guess I should find a different way of telling if a
> translation wasn't found. Maybe if we make NaturalLanguageTranslator return
> nil when a translation is not found? I just don't want to break any existing
> This is why I suggested to use == instead of =. If a translation is found
> but identical, it will be = but not ==, so no further lookup would happen.
> I'd suggest we simply optimize the "no translation found" case because that
> is very common in the "en" locale. The simplest optimization I can think of
> is a dictionary with all phrases from all domains, instead of iterating
> through all domains.
> - Bert -
> etoys-dev mailing list
> etoys-dev at squeakland.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the etoys-dev