Windows telnet certainly is a contraption of Satan, noone will dispute that. However often the problem is as simple as coders using just "\n" rather than "\n\r" when they make the strings for new char creation. This sounds stupid but I have encountered it more than once. The result on Windows Telnet? Consider the string "A\nB\nC"...
on a normal client it will appear
A
B
C
on windows Telnet it will appear
A
B
C
Adding the \r will fix the problem on Windows telnet with no adverse affect to the other clients whatsoever. Anyway, I assure you that I remain,
your faithful and obedient servant,
Erdos