Re: encoding issues with micq

> 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.

Greets
Alex