Bug with International Characters Really Fixed
Ok, I admit we did inadequate testing on the last internationalization bugfix. We fixed sending international characters from the operator to the website client, but not the other way around. Hab.la should now fully support any character that you can encode in UTF-8. We have not tested it with UTF-16, because I am unaware of jabber clients that support UTF-16 encoding, please let me know if you need UTF-16 encoding (i.e. if the current release of Hab.la does not work for your browser/language/charset).
I also made some tweaks to the Javascript to make it smarter about the way it reconnects to the server when we are deploying new versions of our software. I.e. it is currently very easy to update the RPC server, without needing the javascript clients to reload their webpages etc.
In other news, I have begun to implement a WIKI for Hab.la’s API documentation, so maybe they’ll be some API docs coming soon :-)

Comments [0]