On 02/17/2011 06:23 AM, Avi Kivity wrote:
On 02/17/2011 02:12 PM, Anthony Liguori wrote:
(btw what happens in a non-UTF-8 locale? I guess we should just
reject unencodable strings).
While QEMU is mostly ASCII internally, for the purposes of the JSON
parser, we always encode and decode UTF-8. We reject invalid UTF-8
sequences. But since JSON is string-encoded unicode, we can always
decode a JSON string to valid UTF-8 as long as the string is well
formed.
That is wrong. If the user passes a Unicode filename it is expected
to be translated to the current locale encoding for the purpose of,
say, filename lookup.
QEMU does not support anything but UTF-8.
That's pretty common with Unix software. I don't think any modern Unix
platform actually uses UCS2 or UTF-16. It's either ascii or UTF-8.
The only place it even matters is Windows and Windows has ASCII and
UTF-16 versions of their APIs. So on Windows, non-ASCII characters
won't be handled correctly (yet another one of the many issues with
Windows support in QEMU). UTF-8 is self-recovering though so it
degrades gracefully.
Regards,
Anthony Liguori
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
