msgfmt freaks out when it sees a message that ends with a straight newline in original but not in translation, something that I've seen creep into translations a number of times.
Error messages look like this:
locale/cs/LC_MESSAGES/statusnet.po:5904: `msgid' and `msgstr' entries do not both end with '\n' locale/ka/LC_MESSAGES/statusnet.po:5443: `msgid' and `msgstr' entries do not both end with '\n' locale/ka/LC_MESSAGES/statusnet.po:5568: `msgid' and `msgstr' entries do not both end with '\n' locale/ka/LC_MESSAGES/statusnet.po:5606: `msgid' and `msgstr' entries do not both end with '\n' locale/ka/LC_MESSAGES/statusnet.po:5649: `msgid' and `msgstr' entries do not both end with '\n'
Siebrand thinks this may be due to extra whitespace inserted by the JS code, so you end up with " \" instead of "\" for the final line.
They can be manually cleaned up once noticed, but there's a few things that could help prevent them:
- during editing, see if we can avoid the extra space insertion
- at save time, see if we can detect the mismatch and throw a warning for the translator to fix it
- at .po export time, see if we can detect the mismatch and either throw a warning or silently fix it in the output
Version: unspecified
Severity: enhancement