[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-trivial] [Qemu-devel] [PATCH] misc: Avoid UTF-8 in error messa
From: |
Thomas Huth |
Subject: |
Re: [Qemu-trivial] [Qemu-devel] [PATCH] misc: Avoid UTF-8 in error messages |
Date: |
Wed, 21 Nov 2018 07:03:44 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 |
On 2018-11-20 21:36, Eric Blake wrote:
> While most developers are now using UTF-8 environments, it's
> harder to guarantee that error messages will be output to
> a multibyte locale. Rather than risking error messages that
> get corrupted into mojibake when the user runs qemu in a
> non-multibyte locale, let's stick to straight ASCII error
> messages, rather than assuming that our use of UTF-8 in source
> code string constants will work unchanged in other locales.
>
> Reported-by: Markus Armbruster <address@hidden>
> Signed-off-by: Eric Blake <address@hidden>
> ---
> hw/misc/tmp105.c | 2 +-
> hw/misc/tmp421.c | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/hw/misc/tmp105.c b/hw/misc/tmp105.c
> index 0918f3a6ea2..f6d7163273a 100644
> --- a/hw/misc/tmp105.c
> +++ b/hw/misc/tmp105.c
> @@ -79,7 +79,7 @@ static void tmp105_set_temperature(Object *obj, Visitor *v,
> const char *name,
> return;
> }
> if (temp >= 128000 || temp < -128000) {
> - error_setg(errp, "value %" PRId64 ".%03" PRIu64 " °C is out of
> range",
> + error_setg(errp, "value %" PRId64 ".%03" PRIu64 " C is out of range",
> temp / 1000, temp % 1000);
> return;
> }
> diff --git a/hw/misc/tmp421.c b/hw/misc/tmp421.c
> index c234044305d..eeb11000f0f 100644
> --- a/hw/misc/tmp421.c
> +++ b/hw/misc/tmp421.c
> @@ -153,7 +153,7 @@ static void tmp421_set_temperature(Object *obj, Visitor
> *v, const char *name,
> }
>
> if (temp >= maxs[ext_range] || temp < mins[ext_range]) {
> - error_setg(errp, "value %" PRId64 ".%03" PRIu64 " °C is out of
> range",
> + error_setg(errp, "value %" PRId64 ".%03" PRIu64 " C is out of range",
> temp / 1000, temp % 1000);
> return;
> }
>
Reviewed-by: Thomas Huth <address@hidden>