All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, Bandan Das <bsd@redhat.com>,
	Gerd Hoffmann <kraxel@redhat.com>,
	qemu-devel@nongnu.org,
	Samuel Thibault <samuel.thibault@ens-lyon.org>
Subject: Re: [Qemu-devel] [PATCH v2] vl: set LC_CTYPE early in main() for all code
Date: Tue, 16 Apr 2019 21:19:42 +0200	[thread overview]
Message-ID: <87sguh3ghd.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <20190416160927.GT31311@redhat.com> ("Daniel P. =?utf-8?Q?Ber?= =?utf-8?Q?rang=C3=A9=22's?= message of "Tue, 16 Apr 2019 17:09:27 +0100")

Daniel P. Berrangé <berrange@redhat.com> writes:

[...]
> I think that's fundamentally the wrong way around. Most stuff *should*
> be locale dependant, otherwise any interaction with the host OS is
> likely to use incorrect localization. It isn't practical to put a
> uselocale() call around every place that opens a filename. There are
> a few places where QEMU should be locale indepandant such as the QMP
> and guest OS ABI sensitive things, which should take account of it.

All right, you convinced me.  The problem is even bigger than I thought.
That means the return on investment in this area is even poorer than I
thought.

I don't think we should try to support anything but ASCII and UTF-8.

WARNING: multiple messages have this Message-ID (diff)
From: Markus Armbruster <armbru@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, Bandan Das <bsd@redhat.com>,
	Gerd Hoffmann <kraxel@redhat.com>,
	Samuel Thibault <samuel.thibault@ens-lyon.org>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] vl: set LC_CTYPE early in main() for all code
Date: Tue, 16 Apr 2019 21:19:42 +0200	[thread overview]
Message-ID: <87sguh3ghd.fsf@dusky.pond.sub.org> (raw)
Message-ID: <20190416191942.5LkGKeWbRhLcs88kz2T2n5yxwnMyDfWka9Kqk2oMCTQ@z> (raw)
In-Reply-To: <20190416160927.GT31311@redhat.com> ("Daniel P. =?utf-8?Q?Ber?= =?utf-8?Q?rang=C3=A9=22's?= message of "Tue, 16 Apr 2019 17:09:27 +0100")

Daniel P. Berrangé <berrange@redhat.com> writes:

[...]
> I think that's fundamentally the wrong way around. Most stuff *should*
> be locale dependant, otherwise any interaction with the host OS is
> likely to use incorrect localization. It isn't practical to put a
> uselocale() call around every place that opens a filename. There are
> a few places where QEMU should be locale indepandant such as the QMP
> and guest OS ABI sensitive things, which should take account of it.

All right, you convinced me.  The problem is even bigger than I thought.
That means the return on investment in this area is even poorer than I
thought.

I don't think we should try to support anything but ASCII and UTF-8.


  reply	other threads:[~2019-04-16 19:19 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-15 14:15 [Qemu-devel] [PATCH v2] vl: set LC_CTYPE early in main() for all code Daniel P. Berrangé
2019-04-15 14:15 ` Daniel P. Berrangé
2019-04-15 14:25 ` Peter Maydell
2019-04-15 14:25   ` Peter Maydell
2019-04-15 15:25   ` Eric Blake
2019-04-15 15:25     ` Eric Blake
2019-04-15 15:46     ` Peter Maydell
2019-04-15 15:46       ` Peter Maydell
2019-04-15 15:51     ` Daniel P. Berrangé
2019-04-15 15:51       ` Daniel P. Berrangé
2019-04-16  7:49 ` Markus Armbruster
2019-04-16  7:49   ` Markus Armbruster
2019-04-16  9:03   ` Daniel P. Berrangé
2019-04-16  9:03     ` Daniel P. Berrangé
2019-04-16 16:01     ` Markus Armbruster
2019-04-16 16:01       ` Markus Armbruster
2019-04-16 16:09       ` Daniel P. Berrangé
2019-04-16 16:09         ` Daniel P. Berrangé
2019-04-16 19:19         ` Markus Armbruster [this message]
2019-04-16 19:19           ` Markus Armbruster

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=87sguh3ghd.fsf@dusky.pond.sub.org \
    --to=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=bsd@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=samuel.thibault@ens-lyon.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.