On Mon, 11 Mar 2013 00:11:59 +0100, Kevin Israel pleasestand@live.com wrote:
If "Whatever the JSON encoder we use does" means that one day, the daemon starts sending UTF-8 encoded characters, it is quite possible that existing clients will break because of previously unnoticed encoding bugs. So I would like to see some formal documentation of the protocol.
It's 2013. If something still doesn't support receiving UTF-8 data and sending it back without corrupting the text, it should be chucked out of the window like now.
And I don't mean things like properly determining the length of a string etc., as these are not UTF-8 specific, and *are* hard to get right; I mean not breaking binary data.