Well we had a lengthy discussion about Unicode during the development of GMCP. Since I believe the data is sent in JSON format, consider:
http://www.json.org/fatfree.html
Quote:
The character encoding of JSON text is always Unicode. UTF-8 is the only encoding that makes sense on the wire ...
I don't recall what the end specification for GMCP was, but I do recall that a very lengthy and somewhat, er, robust debate occurred on the point of whether or not everything was UTF8.
I would suggest that, based on the above, and since you have Unicode set to "true" in the plugin, you should be assuming that the strings are UTF8. Therefore the server should be encoding any string data as UTF8. In particular, anything above 0x7F would need to be properly encoded, like the quote sign you showed.
I seem to recall that Zugg was very emphatic that the JSON would be Unicode, so one presumes and hopes that CMud would correctly handle the UTF8-encoded data, if the server was changed to send it. However it is interesting that, I guess, you haven't had any complaints from CMud users so far about this particular problem.
See this page for confirmation that the GMCP (ATCP2) data should be UTF8-encoded:
http://www.mudstandards.org/forum/viewtopic.php?f=7&t=107
(Keep reading all 9 pages, Unicode gets a mention from time to time).
|