Hi Ask,
> But what if by accident I change it to %pA? In between the thousands
> of messages and dozens of languages, the probability of this happening
> approaches one (Murphy's law). I mischievously typed "%pA" instead,
> and it produced no error.
Hmm, well mistakes can always happen, and I
Dear Nick and other developers,
Returning to this old issue (e.g.
https://www.mail-archive.com/bug-binutils@gnu.org/msg26950.html),
2016-10-15 18:51 GMT+02:00 Ask Hjorth Larsen :
> Dear developers
>
> In the translation template for bfd [1], very few strings have the
> c-format tag which makes ge
Hi Ask,
> Should I ask the translators for each language to individually submit
> the updates to their language?
Yes please.
> I assume the fixes should be applied to both the old and the new
> version. Correct?
Correct - thanks very much.
Cheers
Nick
_
Hi Nick,
A new version of the template has appeared on TP.
Should I ask the translators for each language to individually submit
the updates to their language?
I assume the fixes should be applied to both the old and the new
version. Correct?
Best regards
Ask
2018-01-10 16:37 GMT+01:00 Ask Hj
Hi Ask,
> Meanwhile, do we disable the strings that have translation errors?
> There are currently 6 affected languages, and we need only mark the
> relevant strings as 'fuzzy' in each po-file. It would be bad to let
> the errors remain in a version that is to be shipped soon.
I think that that
Hi Nick,
2018-01-09 16:46 GMT+01:00 Nick Clifton :
> Hi Ask,
>
>> To solve this problem, BFD should either use only the formatting codes
>> of printf (translation errors will be detected automatically) or avoid
>> exposing any strings with %A and %B to translators.
>
> I just wanted to let you kno
Hi Ask,
> To solve this problem, BFD should either use only the formatting codes
> of printf (translation errors will be detected automatically) or avoid
> exposing any strings with %A and %B to translators.
I just wanted to let you know that your email has not been ignored.
I do have a plan to
Hi,
I reported this issue a year ago, but I think it was unfortunately
never resolved. Please allow me to recap:
Some strings in bfd contain format substitution codes like %A and %B.
Translators will translate these messages and expect gettext to
produce errors if any syntax error is made. But
This is the number of errors I find:
Summary
===
da.po: 0 warnings / 1480 messages
es.po: 1 warnings / 1461 messages
fi.po: 1 warnings / 1478 messages
fr.po: 2 warnings / 1347 messages
id.po: 0 warnings / 880 messages
ja.po: 2 warnings / 1017 messages
ro.po: 0 warnings / 605 messages
ru.po: 2
Hi Nick
I just tested a message like this:
#: coff-sh.c:2780 cofflink.c:2964
#, c-format
msgid "%B: illegal symbol index %ld in relocs"
msgstr "%A: advarsel: illegalt symbolindeks %ld i relokeringerne"
Note how the translation contains an erroneous %A instead of the correct %B.
This is accepted
Hi Ask,
> Do you know when the translation
> templates on translationproject.org will be updated?
On translationproject.org - no. But I have just updated the
bfd.pot template in the binutils source repository (which I
forgot to do yesterday, sorry).
Cheers
Nick
_
Hi Nick
Thank you. I thought the c-format flag was always automatic and thus
I wonder if perhaps the format checker is not aware of the codes like
%A and %B - but this I cannot say. Do you know when the translation
templates on translationproject.org will be updated?
Best regards
Ask
2016-10-1
Hi Ask,
> In the translation template for bfd [1], very few strings have the
> c-format tag which makes gettext able to tell if placeholders (%s, %d,
> ...) are mistranslated. This typically affects the substitution codes
> %B and %A.
>
> It is very unlikely that any translator can translate all
Dear developers
In the translation template for bfd [1], very few strings have the
c-format tag which makes gettext able to tell if placeholders (%s, %d,
...) are mistranslated. This typically affects the substitution codes
%B and %A.
It is very unlikely that any translator can translate all 140
14 matches
Mail list logo
