> I've spent some time looking into it all, and figured out what went
> wrong eventually. The .pot import went through fine, but all of the .po
> files failed silently. I've opened an answer ticket at LP about this
> problem (and others,
> https://answers.launchpad.net/rosetta/+question/36031). They've filled a
> couple of bug reports (one of them the missing mail with the reason of
> import failure).
> Anyway, that guy was kind enough to find the import error in the logs:
> "Original text (u'Revision: %ld\nURL: %s\r\nAuthor: %s\r\nDate:
> %s\r\n\r\nLogmessage:\r\n%s') mixes different newline markers
> So looks like a header was edited partly on a Windows system and partly
> on a non-Windows system, and then copied to a lot of translations, with
> mixed line ending codes."
That depends: is the error message due to mixed eols in the file itself
or in the string? As you can see in the string, there are both \r and \n
chars there, and those are required.
If it's due to inconsistend line endings in the file itself: I've fixed
four po files which had not set the svn:eol-style property set yet
(ca_ES, eo, id and ro).
> The question is then: Is the mix of line endings intended or not? If it
> is, I'll report back to the LP guys and ask them to accept it anyway. If
> not, can we fix that string?
As I said above, the string requires the \r\n line ending sequence.
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
Received on 2008-06-12 17:50:33 CEST