To elaborate a little bit on why you'd get this strange behavior, Windows encodes line endings as CR/LF, that is a carriage-return (return to the beginning of the line) followed by a linefeed (advance to the next line). So if you strip off just the linefeed, you end up with this in your string:

FORM<CR> is the symbol<LF>
[download]

That tells your terminal to print FORM, then return the cursor to the beginning of the line and print is the symbol---which is now right on top of FORM---and finally advance to the next line.

If you pipe this through less, od, or hexdump, you should be able to see this is what's going on.