On 9/23/06, Joachim Staib <[EMAIL PROTECTED]> wrote:
decide which character set to use). Interestingly, when the user sends the Supports-UTF-8-Flag the correct encoding doesn't seem to be "UTF-8" but "UCS-2BE". The problem with this encoding is that it can contain bytewise zeros (I think) - and this is the point where of course things like strdup or strlen stop working.
We do a little bit with the UCS-2BE encoding automatically, but only for direct messages. Grep the source for UTF16 to see the exact places. The current method is not complete, it was mainly done to test the UTF16 support in ICQ. But, it does work for direct messages, so it may be nice to move it throughout the daemon.
I'd like to start with such a work in the backend if this doesn't interfere with some plans you have :)
Sure, go ahead! Let me know if you have any questions. As I said, grep for "UTF16" to see the existing code. Jon -- ________________________________________________________ Jon Keating ICQ: 16325723 [EMAIL PROTECTED] MSN: [EMAIL PROTECTED] http://www.licq.org GPG: 2290A71F http://www.thejon.org HOME: Minamiashigara, Japan
