I have a question about the % codes and order.
| Ben Reser said:
|
| Right now as far as I'm concerned this rule means as long as you don't
| touch a .c or .h file you're fine. Because you can't go changing the %
| codes without chaing the .c or .h files. Now I suppose someone could
| use a %d interchangeable with a %ld on some platforms. But this all
| should be easy to review. If the % codes on the msgid don't match the
| msgstr then there is probably something very wrong with the change and
| it won't be allowed anyway. If the msgid doesn't match what we have in
| the code then well, the msgstr won't ever be used so there's no harm
| as far as stability, though the translation will suffer.
|
| The only circumstance I really see coming up in practice is adding
| strings that weren't previously translatable because they weren't
| wrapped with _(). Those things require voting. So I'd modify the rules
| to read as follows to be more clear:
|
| Without voting:
| - Changes to message translations in .po files where the % codes in the
| msgstr are exactly the same (including order) as the % codes in the
| msgid and that do not add new msgids that did not previously exist.
|
| With voting:
| - Changes to message translations in .po files that add a msgid (not
| used in another existing translation) or alter the % codes in an
| existing msgid.
Given this discussion, would it be fair to say that the rearrangement of the
% codes, even after using the msgfmt rearragement syntax (for example,
"Error %s return val %ld" ==> "Return val %2$ld error %1$s" ) is not
supported in Subversion build process?
Reference: info "(gettext)c-format Flag" (I can't get a more comprehensive
explaination than this)
Regards,
Clifford Caoile
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Jul 31 04:59:21 2004