From: Anthony Liguori <anthony@codemonkey.ws>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Chris Wright <chrisw@redhat.com>, Avi Kivity <avi@redhat.com>,
kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] KVM call minutes for Feb 15
Date: Thu, 17 Feb 2011 08:01:55 -0600 [thread overview]
Message-ID: <4D5D2A53.30607@codemonkey.ws> (raw)
In-Reply-To: <AANLkTi=8zm4jcBM1sh16JQScOAOYhwcf0TkFp=tg_6bE@mail.gmail.com>
On 02/17/2011 07:59 AM, Peter Maydell wrote:
> On 17 February 2011 13:37, Anthony Liguori<anthony@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
>
>
next prev parent reply other threads:[~2011-02-17 14:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-15 16:26 [Qemu-devel] KVM call minutes for Feb 15 Chris Wright
2011-02-15 23:13 ` Anthony Liguori
2011-02-16 10:24 ` Avi Kivity
2011-02-16 13:34 ` Anthony Liguori
2011-02-17 9:26 ` Avi Kivity
2011-02-17 12:12 ` Anthony Liguori
2011-02-17 12:23 ` Avi Kivity
2011-02-17 13:10 ` Anthony Liguori
2011-02-17 13:25 ` Avi Kivity
2011-02-17 13:37 ` Anthony Liguori
2011-02-17 13:59 ` Peter Maydell
2011-02-17 14:01 ` Anthony Liguori [this message]
2011-02-17 14:06 ` Avi Kivity
2011-02-17 13:37 ` Anthony Liguori
2011-02-16 14:39 ` Amit Shah
2011-02-16 14:41 ` Anthony Liguori
2011-02-17 12:42 ` Amit Shah
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D5D2A53.30607@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=chrisw@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).