Re: ICQ charsets.

On 5 Jun, 2005, at 03:45, Encoding values:
> 0x0000 means ASCII (really ISO-Latin-1)
> 0x0002 means ICS-2BE (UTF-16 Big Endian)
> 0x0003 means custom character set (anything)

Where did 1 go? Or is this another case of version number syndrome?

> On the message with encoding 0x0003, Adium sent a message containing 
> 0xFEFF (unicode byte order marker) and no message text at all.

No, this is me sending a message with "UTF-16". Something interprets it 
as a C-string and truncates at the null char. Theoretically, it would 
actually send something if I sent characters outside iso-latin-1.

> Now, version 2.0 (currently in development) has a revamped service 
> architecture, including using the AIM library for ICQ.  It works in my 
> limited tests, and you are welcome to check-out the code and run it.  
> Instructions are found here:
> http://fire.sourceforge.net/development/developer.php
>
> When using the AIM library for ICQ, it does not use HTML, because that 
> is not part of ICQ.  It uses HTML (not really HTML but close) on AIM 
> because that is part of AIM.  If you don't like HTML on AIM, blame 
> AOL, not the AIM implementation we use.

Except it annoyingly sends HTML for text where I'd much rather send 
plaintext. I especially don't like the font tags, but that's me 
("default" should be a valid outgoing color, and a valid font, and...).

- Purr



-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.  How far can you shotput
a projector? How fast can you ride your desk chair down the office luge track?
If you want to score the big prize, get to know the little guy.  
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20