On 02/17/2011 07:59 AM, Peter Maydell wrote:
On 17 February 2011 13:37, Anthony Liguori<anth...@codemonkey.ws> wrote:
An application has to explicitly support an encoding. It is not
transparent. UCS2/UTF-16 means that strings are not 'const char *'s but
'const wchar_t *' where typedef unsigned short wchar_t;.
QEMU assumes, in lots of places that strings are single-byte NUL terminated.
Basically, any use of snprintf, printf, strcpy, strlen, etc. pretty much
tie you to ASCII/UTF-8.
Er, no, it limits you to those encodings where you can treat strings
as "bag of NUL-terminated bytes". Oddly enough just about all the
common legacy ones (iso-8859-*, iso-2022-jp, etc) fit in that category
because otherwise they'd break really badly.
I wasn't even considering those because I think the entire world has
moved to unicode/utf*
Those functions limit you to UTF-8 which was my original point.
Regards,
Anthony Liguori
As it is, generally
things Just Work for programs which treat filenames as "an opaque
string".
-- PMM
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
