Re: Patch for bison/po/es.po

[Akim Demaille]

>>>>> "Martin" == Martin v Loewis <address@hidden> writes:

>> I don't get it!  I kept on repairing and repairing this file.  How
>> could it escape!

Martin> As Santiago explains: this string is marked fuzzy, meaning
Martin> that the translator has not completed translation. There is no
Martin> need to do anything about this - the translator will
Martin> eventually get to it and update the translation.

No.  As I tried to explain, this string was not marked fuzzy.  I kept
on repairing it on my copy, but since the TP uses 0.11, it seems that
the string is *now* marked as fuzzy.


>> This translation is obviously wrong:
>> 
>> @@ -300,17 +300,17 @@
>> 
>> #: src/lex.c:438 msgid "use \"...\" for multi-character literal
>> tokens" -msgstr "utilisez \"...\" pour les terminaux litéraux de
>> plusieurs caractères" +msgstr "utilisez «...» pour les terminaux
>> litéraux de plusieurs caractères"
>> 
>> as I'm referring exactly to ".

Martin> Did you mean the patch in the reverse direction?

I mean the newest translation is +, the old was -, and the new one is
wrong.

Martin> In any case, please try not to interfere with the translators
Martin> work. 

Then consider I'm not a Bison maintainer, I'm someone who reports
translation problems.

Martin> If there are bugs, it is normally best to include the catalog
Martin> anyway. Many catalogs will have grammatical and contextual
Martin> errors in them - there is no way you could find these
Martin> errors. 

I don't really care about these.  I care about those that are wrong,
not bad.  I care about Bison asking for English quotes, and not
demandant pour des guillemets français :).

Martin> Instead, users of your package will find them. 

I'm a user!

Martin> Don't be upset when they report them - just forward them to
Martin> the respective translator (it clearly is nor your fault, after
Martin> all).

I'm sorry if I was harsh.  I did not mean it, nor did I realize I was.