Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Владимир Мартьянов" <vilgeforce@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH][PR server/24377] Fix mixing English and system default languages in error messages on Windows
Date: Fri, 29 Mar 2019 12:32:00 -0000	[thread overview]
Message-ID: <837echkgjo.fsf@gnu.org> (raw)
In-Reply-To: <CAL5iTPJD77ML8=2uM_dc63QCSHtKrgQTZe2MQbPUoo=veAYJ3A@mail.gmail.com>	(message from =?utf-8?B?0JLQu9Cw0LTQuNC80LjRgCDQnNCw0YDRgtGM0Y/QvdC+0LI=?= on Fri, 29 Mar 2019 12:38:50 +0300)

> From: Владимир Мартьянов <vilgeforce@gmail.com>
> Date: Fri, 29 Mar 2019 12:38:50 +0300
> Cc: gdb-patches@sourceware.org
> 
> Using system default locale is not a good idea, user must have a way
> to change message language. If somebody have to debug on chinese
> Windows, he'll get Chinese messages. And this way mustn't affect any
> other applications or the system itself. LC_ALL and other env.
> variables will affect only gettext, not FormatMessage in the current
> implementation.

That completes the full circle and gets us right back to square one.
Where you wanted to force FormatMessage to use the English language
and I asked whether this isn't a step backward.

Anyway, since we have reviewed the various ways of fixing this, I
think you now have all the information you need to produce a patch.
Telling FormatMessage to use English is simple, and letting users
choose a different locale is only meaningful if the other messages,
those which aren't output via FormatMessage, can also be translated to
other languages, which requires to use _() and Gettext.


  reply	other threads:[~2019-03-29 12:32 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-23 11:59 Владимир Мартьянов
2019-03-23 13:11 ` Eli Zaretskii
2019-03-28 20:36   ` Владимир Мартьянов
2019-03-29  8:27     ` Eli Zaretskii
2019-03-29  8:42       ` Владимир Мартьянов
2019-03-29  9:29         ` Eli Zaretskii
2019-03-29  9:39           ` Владимир Мартьянов
2019-03-29 12:32             ` Eli Zaretskii [this message]
2019-03-30 21:26               ` Владимир Мартьянов
2019-03-31 14:45                 ` Eli Zaretskii
2019-03-31 19:39                   ` Владимир Мартьянов
2019-04-01  4:47                     ` Eli Zaretskii
2019-04-02 20:08                       ` Владимир Мартьянов
2019-04-03  4:30                         ` Eli Zaretskii
2019-04-01 22:08                     ` Jon Turney
2019-04-02 20:57                       ` Владимир Мартьянов
2019-04-02 21:10                         ` Jon Turney
2019-04-02 21:18                           ` Владимир Мартьянов
2019-04-03  4:48                         ` Eli Zaretskii
2019-04-03  4:58                           ` LRN
2019-04-03  7:37                             ` Eli Zaretskii
2019-04-03 11:32                               ` LRN
2019-04-03 12:04                                 ` Eli Zaretskii

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=837echkgjo.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=vilgeforce@gmail.com \
    /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