[Freeciv-Dev] (PR#39642) en_US.po
http://bugs.freeciv.org/Ticket/Display.html?id=39642 > Changing translatable strings in stable branch is bad. So we don't do it for minor things like typofixes. We can't help those typos etc appearing when gettext is not used, or there is no translation in used language. But we could at least provide typofixed 'translation' as en_US.po. That po would need translation only to those couple of strings we don't want to use in their current default form. I would add that file to S2_1 only - in trunk default texts should be fixed. Also, when S2_2 is created, new en_US.po should be created instead of getting one from S2_1, as everything in S2_1 version is obsoleted by trunk fixes. Opinions? - ML ___ Freeciv-dev mailing list Freeciv-dev@gna.org https://mail.gna.org/listinfo/freeciv-dev
Re: [Freeciv-Dev] (PR#39642) en_US.po
http://bugs.freeciv.org/Ticket/Display.html?id=39642 > On 8/31/07, Marko Lindqvist <[EMAIL PROTECTED]> wrote: > > http://bugs.freeciv.org/Ticket/Display.html?id=39642 > > > Changing translatable strings in stable branch is bad. So we don't do > it for minor things like typofixes. > We can't help those typos etc appearing when gettext is not used, or > there is no translation in used language. But we could at least > provide typofixed 'translation' as en_US.po. > That po would need translation only to those couple of strings we > don't want to use in their current default form. > I would add that file to S2_1 only - in trunk default texts should be > fixed. Also, when S2_2 is created, new en_US.po should be created > instead of getting one from S2_1, as everything in S2_1 version is > obsoleted by trunk fixes. > Opinions? > > > - ML > Excellent idea. I've been contemplating how to deal with typos in stable branches recently myself... ~Daniel ___ Freeciv-dev mailing list Freeciv-dev@gna.org https://mail.gna.org/listinfo/freeciv-dev
Re: [Freeciv-Dev] (PR#39642) en_US.po
http://bugs.freeciv.org/Ticket/Display.html?id=39642 > On Fri, 31 Aug 2007 Marko Lindqvist wrote: > Changing translatable strings in stable branch is bad. So we don't do > it for minor things like typofixes. > We can't help those typos etc appearing when gettext is not used, or > there is no translation in used language. But we could at least > provide typofixed 'translation' as en_US.po. > That po would need translation only to those couple of strings we > don't want to use in their current default form. ... > Opinions? One moment/problem: original string is shown if untranslated for _any_ translation... [JT] Keeping strings unchangeable should never become a target in itself. We're afraid that people will not correct translation after release? But what is current statistics on .po-files? Only several full translated files... 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] I'm not against en_US.po, but I don't see much perspective... -- Thanks, evyscr ___ Freeciv-dev mailing list Freeciv-dev@gna.org https://mail.gna.org/listinfo/freeciv-dev
Re: [Freeciv-Dev] (PR#39642) en_US.po
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 ___ Freeciv-dev mailing list Freeciv-dev@gna.org https://mail.gna.org/listinfo/freeciv-dev
Re: [Freeciv-Dev] (PR#39642) en_US.po
http://bugs.freeciv.org/Ticket/Display.html?id=39642 > On 9/5/07, Egor Vyscrebentsov <[EMAIL PROTECTED]> wrote: > > 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 branches too. en_US would only cover typos that don't affect the meaning of a string. Or at least that's how I interpret it. ~Daniel ___ Freeciv-dev mailing list Freeciv-dev@gna.org https://mail.gna.org/listinfo/freeciv-dev
Re: [Freeciv-Dev] (PR#39642) en_US.po
http://bugs.freeciv.org/Ticket/Display.html?id=39642 > Marko Lindqvist wrote on Aug 31, 02:26 (-0700): > Changing translatable strings in stable branch is bad. So we don't do > it for minor things like typofixes. > Opinions? What bugs me harder is the absence of a timeline for the 2_1 release. I wonder whether the recent code changes are all bug fixes? Without a code freeze and a strings freeze (clearly communicated) it will be hard to find all (new) bugs in the betas before the release. This applies as well for the strings. For the rest, I'm with evyscr. After a strings freeze, translators should be granted several weeks to come up with translations, during which the testing can continue. Important text bugs after strings freeze can be fixed and announced on the i18n list. The remaining typos in english can be fixed in en_US.po, but I wonder whether it will be worth doing that. Christian -- Christian Knoke* * *http://cknoke.de * * * * * * * * * Ceterum censeo Microsoft esse dividendum. ___ Freeciv-dev mailing list Freeciv-dev@gna.org https://mail.gna.org/listinfo/freeciv-dev
Re: [Freeciv-Dev] (PR#39642) en_US.po
http://bugs.freeciv.org/Ticket/Display.html?id=39642 > I strongly disagree with the creation of en_US.po Strings that exist, and need trivial fixing for grammar (not content), should be updated in both the code source and *all* the translation *.po keys. It's easy to do, and there's no effort needed by translators That's how I've been handling it already. Surely, we all have sed, or its GUI equivalent?!?! Strings that change in content and semantics have to be vetted by translators anyway, having en_US.po doesn't help! ___ Freeciv-dev mailing list Freeciv-dev@gna.org https://mail.gna.org/listinfo/freeciv-dev
Re: [Freeciv-Dev] (PR#39642) en_US.po
http://bugs.freeciv.org/Ticket/Display.html?id=39642 >
On Mon, 10 Sep 2007 06:01:34 -0700 William Allen Simpson wrote:
> I strongly disagree with the creation of en_US.po
>
> Strings that exist, and need trivial fixing for grammar (not content),
> should be updated in both the code source and *all* the translation *.po
> keys.
I'm agree that en_US.po is not a silver bullet. But I think neither you
nor me nor somebody else can't fix all translation changes. Simple
fix in english may become very untrivial task in other language.
('%2s %1s' for [quite easy] example)
> It's easy to do, and there's no effort needed by translators
>
> That's how I've been handling it already. Surely, we all have sed, or
> its GUI equivalent?!?!
Erm, is it right that "it's easy"? I'm sure that I *never* placed 'msgid'
twice in one line. But once I've fixed that. See also Marko's fixes
of fuzzies. And sed never was a translation tool! Marking string
as fuzzy is more fair thing that to change it manually (or automatically
not by 'make update-po' [*]) without giving translator a notice.
[*] And update-po changes only msgids, marking string as fuzzy.
But this is not about en_US.po.
> Strings that change in content and semantics have to be vetted by
> translators anyway, having en_US.po doesn't help!
Agree.
But you may look to my second answer in this ticket.
And you may find sentences in archive of the list that english is
not the ideal language for freeciv, but we have no better.
--
Thanks, evyscr
___
Freeciv-dev mailing list
Freeciv-dev@gna.org
https://mail.gna.org/listinfo/freeciv-dev
