In non-Unicode settings, I believe Windows' multi-line edit controls internally use "\x0D\x0A" bytes for hard line breaks, and "\x0D\x0D\x0A" for word wraps.

If you have to deal with a certain platform's byte sequences for line breaks, don't just use the semantic names "\n" or "\r", but get specific with hex or octal codes. "\n" should be read as "whatever newline this platform *usually* likes."

--
[ e d @ h a l l e y . c c ]