[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-i18n-doc
Subject:    Re: [typo] cantor.po
From:       Māris Nartišs <maris.kde () gmail ! com>
Date:       2012-07-12 8:18:00
Message-ID: CAB7F8C7QxXV_Nrom5s_Noc=HCTwz6Rb8MPaJhLD25gReCx4VvQ () mail ! gmail ! com
[Download RAW message or body]

Hello,
You are missing the point - even just a single letter spelling fix
will make string fuzzy in all existing translations. Translator teams
might not notice it or have time to check for this new fuzzy message
before release and thus release might have one more untranslated
string in a perfectly translated application. "an" -> "a" isn't a case
where it might cause totally wrong translation and thus be better to
have untranslated than wrongly translated string.

Just FYI :)
Maris.

PS. Formation of volcanic chains is a slow process and usually takes
thousands if not millions of years and thus have nothing common with
chain reaction You witnessed in this ML ;)

2012/7/12 Laszlo Papp <lpapp@kde.org>:
> On Wed, Jul 11, 2012 at 10:23 PM, Nicol=C3=A1s Alvarez
> <nicolas.alvarez@gmail.com> wrote:
>> We're in message freeze. You need to get the i18n language teams to agre=
e
>> *before* you push string changes.
>
> Wow! Such a super simple change can cause volcanic chain... I would
> understand, if the meaning of a word is changed, or anything gets
> rephrased, but this is just "an" -> "a" change where the translations
> should remain the same anyway.
>
> At any rate, I am sorry for not guessing this. I sincerely apologize.
>
> Best Regards,
> Laszlo Papp
[prev in list] [next in list] [prev in thread] [next in thread]