Comment author: @damiendoligez

Arguably, your HTML renderer is also broken: it shouldn't take a single \r as an end-of-line.

Comment author: @dra27

Well, possibly, but by HTML renderer you're referring to Internet Explorer 11, Chrome 37 and Firefox 27 (I know that's out-of-date - I don't use it very often!). Interestingly, as I also have a not-updated Ubuntu 12.4 virtual machine, Firefox 27 appears to ignore the extra \r on Linux, but not on Windows.
Technically (http://www.w3.org/TR/html401/struct/text.html#line-breaks), both are behaving correctly - \r\r\n is two line breaks (or three, depending on how you read it!) and a pre element's rendering of whitespace is all covered by "may"! What SGML parsing has to say about mixed line break use, I don't know, because it's of course an ISO standard and I'm not wealthy enough to be able to consult it!

Comment author: @damiendoligez

OK, so it's HTML itself that is broken. I'm not surprised.

FTR, now that MacOS 9 has disappeared, the correct way to handle this CR/LF nonsense is to consider that LF is a newline, and CR is utterly ignored in all contexts. That works with both Unix and Windows.

I've committed a fix to trunk (rev 15815), but I still need to test it for real under Windows.

Comment author: @damiendoligez

tested under Windows