qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>,
	Markus Armbruster <armbru@redhat.com>
Cc: Alberto Garcia <berto@igalia.com>,
	qemu-devel@nongnu.org, Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] QEMU produces invalid JSON due to locale-dependent code
Date: Mon, 24 Aug 2015 14:27:57 -0600	[thread overview]
Message-ID: <55DB7E4D.7080306@redhat.com> (raw)
In-Reply-To: <20150824175648.GV22295@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1411 bytes --]

On 08/24/2015 11:56 AM, Daniel P. Berrange wrote:

>> (C) Run in a mixed locale
>>
>>     Whenever something breaks, we switch another LC_ to the C locale.
>>
>>     Can partially break GTK's internationalization.
>>
>> I happily concede that (A) would be best.  Until the manpower to pull it
>> off appears, I recommend (B), because it's safer than (C), and avoids
>> inconsistent localization, such as German messages combined with
>> non-German number formatting.
> 
> It seems the only thing that we really care about being localized is
> the messages catalogue, so the GTK UI gets internationalization in
> its menus / dialogs / etc. As such I think that we should do the
> opposite of (C). ie run every LC_* in the C locale, except for
> LC_MESSAGES which we allow to be localized.
> 
> This avoids any unpredictable functional consequences (like number
> formatting) while still giving user decent localization in the UI

Except that the LC_MESSAGES catalog may include messages such as "blah
%d blah" that get translated for use as a printf argument, and the lack
of matching LC_NUMERIC will make the translation look wrong.
Translators often assume that their translation is being used with
everything else about the locale matching the locale of the translation.

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]

  reply	other threads:[~2015-08-24 20:28 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-18 23:57 [Qemu-devel] QEMU produces invalid JSON due to locale-dependent code Alberto Garcia
2015-08-24  8:58 ` Daniel P. Berrange
2015-08-24 10:05 ` Markus Armbruster
2015-08-24 10:29   ` Alberto Garcia
2015-08-24 17:07     ` Markus Armbruster
2015-08-24 17:18       ` Eric Blake
2015-08-25  7:54         ` Markus Armbruster
2015-08-25  8:15           ` Alberto Garcia
2015-08-25 12:51             ` Markus Armbruster
2015-08-26  9:13           ` Alberto Garcia
2015-08-26  9:22             ` Daniel P. Berrange
2015-08-26  9:47               ` Markus Armbruster
2015-08-24 17:56       ` Daniel P. Berrange
2015-08-24 20:27         ` Eric Blake [this message]
2015-08-26  6:46           ` Gerd Hoffmann
2015-08-26  9:57             ` Daniel P. Berrange
2015-08-26 12:04               ` 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=55DB7E4D.7080306@redhat.com \
    --to=eblake@redhat.com \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=berto@igalia.com \
    --cc=kraxel@redhat.com \
    --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).