Hi Alexey Nezhdanov,

Thanks. I think you are right. 

Our patches were made againist 1.1.4 originally. After we see the 1.1.7 patch, we re-apply our patches to 1.1.7, so we have overlooked that 1.1.7 already supported receiving unicode messages.

A lot of transport administrators are still running 1.1.6 or below, so I think it's time for them to upgrade.

For the sending strategy, the patched JIT transport will first attempt to send in ASCII mode, if the message contains only ASCII characters. Otherwise it will attempt to send in UCS2. This works with most modern ICQ clients and we don't see any significant drawback in doing so. 

You are very welcomed to look at our patches and send us feedback. And thank you very much for your JIT 1.1.7 patch!

Thank you!

Best Regards,
Tony Cheung

On 27 Nov 2005, at 2:00 AM, [EMAIL PROTECTED] wrote:

Hi,


I am glad to release a unicode patch to the popular JIT (Jabber ICQ

Gateway).


Previously, the JIT does not support sending/receiving Unicode

messages.

Nope, it's supported receiving unicode messages (version 1.1.7). I didn't 

added _sending_ unicode messages because considered this as strategically 

bad. Usually users blame clients that fails to correctly _display_ message. 

So in this case _ICQ_ clients will be blamed :)


-- 

Respectfully

Alexey Nezhdanov


Reply via email to