I spent the night trying to figure out the character problems we've been having with non latin characters in Meshly.
Turns out AIM sometimes encodes text as latin1 and sometimes as utf16-be, so the bot needs to make a guess as to what it's getting. Google Talk via iChat seems to encode everything utf8 so it works fine, though the java client seemed to be garbling non-latin characters (nothing I can do about that). I haven't had a chance to test MSN and sort out what it might be doing.
So, long story short: you can post in non-latin text with iChat/AIM and Google Talk and it will come out correct on the website. Some of the text the bot spits back in its confirmation is still garbled, but that's a bug for another day.
Submitted by jason - 2007-04-24 01:44:07
Channels - meshlydev
Tags - debug
unicode
aim
oscar
jabber
1 comment