Hello, I have just commited some changes to CVS that should improve the problems people have had with encodings. We now set the correct flag for the encoding we use so the other side can properly decode the message. There are 3 flags, ASCII, UTF16, and Other. The other flag will be used if the otherside doesn't support UTF16. That means you will have to find the right encoding to get it to work with them.
For example, if I send a japanese message from Licq to a windows computer, i have to select SJIS encoding. But if I send a japanese message to a gaim user (which also supports UTF16) I would select UTF-8 (the daemon converts it to UTF16 now). Please test this out and give me any feedback. This was one of the largest bugs that I wanted to get fixed before 1.3.2. Jon ------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_idt12&alloc_id344&op=click _______________________________________________ Licq-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/licq-devel
