On Sat, 24 Nov 2007 06:58:01 +0900 Jon Keating <[EMAIL PROTECTED]> wrote:
> > what encoding icq uses for sending messages with non ASCII text? > > Is there some standard, say, UTF-8? For example, when encoding > > in licq is UTF-8, I can send and receive non ASCII messages with > > gaim, gaim is able with miranda, but licq with miranda doesn't work. > > There are a few standards in the ICQ protocol. One is to let the client send > whatever it wants. The other is UTF-16. UTF-16 support was added later on, so > Licq mainly uses the whatever option, but is able to hand UTF-16 support as > well. Perhaps you can send over a packet capture of when you send a message > to a Miranda user? Make sure to include the encoding you manually set, and > what the contents of the message are. I tried to set Unicode-16 in licq, but then incomplete message was sent (w/o accent letters at all), and received message was displayed in hieroglyphs. So it seems it is something wrong with UTF-16 support. So I used UTF-8 when testing. I found an older thread about this problem - http://www.mail-archive.com/[email protected]/msg00066.html After reading it I understand that there are 2 problems with licq UTF-8 support: 1. licq doesn't send CAP_UTF8 (but it is needed for receiving UTF-8 messages only, see below). 2. http://www.mail-archive.com/[email protected]/msg00077.html : ________________ > wrong? Seems to me, that setting CAP_UTF8 is not enough since miranda > and micq understand each other without problems or even codepage > overrides. I promised to quote this from micq mailing list and it prooves what I said above: > The capability is needed so that other clients know that the client > can receive unicode messages. For sending messages, they just have > to be tagged accordingly. Unacknowledged messages (type-1) get the > encoding field (an int) set accordingly, and the message will be in > UCS-2BE. For acknowledged messages, the message will be in UTF-8, and > the capability as a GUID needs to be in the message. ________________ So my proposal is: CAP_UTF8 should be added (or http://trac.licq.org/attachment/ticket/1445/newdiff.patch?format=raw applied), as otherwise licq cannot receive UTF-8 messages from some clients (Miranda for example). Sending messages have to be tagged accordingly. Regards, Nerijus
