Re: [sup-talk] i18n?

From: Fabio Riga <usul@aruba.it>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] i18n?
Date: Fri, 23 Oct 2009 13:23:06 +0200	[thread overview]
Message-ID: <1256295847-sup-9437@viajero> (raw)
In-Reply-To: <1256280223-sup-736@tilus.net>

Excerpts from Tero Tilus's message of ven ott 23 09:00:21 +0200 2009:
> Excerpts from 's message of pe loka 02 15:52:47 +0300 2009:
> > Please tell me what you think.
> 
> Why not default to the english strings as translation keys and
> fallback to key itself in case of missing translation?  This has imo
> several advantages.  You can go grep the source using what you see in
> sup UI (instead of first greping language yaml).

Well, I finally read the code and I agree with Tero. I also think that the
use of gettext will be simpler for both developer and translator. In
this way, every time a developer add a new string he need to write it
twice, or another developer has to hack it. Instead with gettext the
developer write his string, surrounded with _() or n_() and he's done
(tell me, if I'm wrong).

Furthermore people used to .po files (like me) will know what to do and
are already provided with tools for that purpose (i.e. Vim :-) ).

Can anyone explain me where and why a translated string in the UI should be
searchable with a regular expression? (Maybe this question is due to the
fact that I still don't understand sup internals...)

Cheers,
Fabio
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk