2013/8/2 Carlos E. R. <carlos.e.r@opensuse.org>:
What I know is that the translation tools will not detect the double slash, and will not flag as an error if a single slash is used. What will happen if we (translators) fail to use them?
If I remember correctly, \\ is the escape sequence to have the character '\' in the resulting string, as \n is the escape sequence for the new line. So, having \\n in the original string should correspond to have the two characters '\n' in the resulting string. So, if we keep \n instead of \\n in the translation, than the tool should complain for the different number of new lines; if we use \\n, probably the user will see the characters '\n' in the string instead of the new line.
Can our tools be modified so that those errors be flagged?
No idea, also because '\\' has a meaning, it is not an error.
Why has that double slash got to be used? :-?
It seems to be a problem with the string extraction tool (from a mail sent to yast-devel only): On 08/02/2013 08:36 AM, Ladislav Slezak wrote:
Dne 1.8.2013 18:59, Andrea Turrini napsal(a):
As a result, the msgid strings now contain "\\n" instead of "\n" to denote the new line inside the same msgid.
For instance, in printer.pot, the current string is
msgid "Started the CUPS daemon.\\nWaiting half a minute for the CUPS daemon to get ready to operate...\\n"
Yeah, I haven't noticed that, thanks for reporting this!
Now, the question is: is this change expected and wanted?
This was caused by switching from YCP to Ruby which needs using Ruby gettext (rxgettext) instead of GNU gettext (xgettext).
For me it looks like a bug, I'll investigate further.
Moreover many comments are missing, this is another incompatibility in rxgettext and needs to be solved.
For now ignore the new translations, and I think the last changes could be even reverted to not cause confusions for translators...
Best, Andrea -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org