<URL: http://bugs.freeciv.org/Ticket/Display.html?id=39642 >
On 9/5/07, Egor Vyscrebentsov <[EMAIL PROTECTED]> wrote:
> <URL: http://bugs.freeciv.org/Ticket/Display.html?id=39642 >
> On Mon, 3 Sep 2007 06:30:59 -0700 Egor Vyscrebentsov wrote:
> > One moment/problem: original string is shown if untranslated for _any_
> > translation...
> > [JT]
> > Rather than moratoring changing, it is better (IMHO) to
> > create good mechanism to tell a translator what was changed (in i18n/l10n)
> > between two versions (or, even better, since last .po modify date.)
> > [/JT]
> Still think so.
> > I'm not against en_US.po, but I don't see much perspective...
> OK, I take back last sentence. Right now I see that en_US may help in
> translations like for the req_source_type_names (where text in code and
> text, displayed to user, may [not necessary should] differ.)
> Thanks, evyscr
Any misinformation or fatal mistakes that could affect the accuracy of
the localizations should naturally be corrected in source on stable
en_US would only cover typos that don't affect the meaning of a
string. Or at least that's how I interpret it.
Freeciv-dev mailing list