[Konversation-devel] [Bug 109750] Annoying behavior of special characters in nicknames

[Eli MacKenzie]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=109750         
argonel sympatico ca changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX



------- Additional Comments From argonel sympatico ca  2005-07-29 17:20 -------
Sorry, but this is not something we can nor should fix. 0x000A is a linefeed, and has been used in this role since at least 1963. Please see RFC#20, dated October 16,1969, page 7. <http://www.ietf.org/rfc/rfc20.txt>

Unix-style operating systems (now including MacOs) use LF as the primary message seperator. This practise is still valid with Unicode. Since there are *lots* of available characters in Unicode, there is no need to redefine the use of 0x000A. 

Please also note that both RFC1459 and RFC2812 reserve the use of LF as a message terminator. Any IRCD that does accept only CR (or indeed only LF) for message termination is tolerant, not normative.

I suggest that you file a bug report with those that have modified the behavior of the IRCD.