From: "Владимир Мартьянов" <vilgeforce@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
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 08:42:00 -0000 [thread overview]
Message-ID: <CAL5iTPJr_-WxFcCSFdq_CEoBHuq22FVr55aA1WQisO9DPiEv2w@mail.gmail.com> (raw)
In-Reply-To: <83ef6qjdbb.fsf@gnu.org>
Just try to use gettext with FormatMessage. I don't have idea how to
do it, could you please give me a code sample?
пт, 29 мар. 2019 г. в 11:27, Eli Zaretskii <eliz@gnu.org>:
>
> > From: Владимир Мартьянов <vilgeforce@gmail.com>
> > Date: Thu, 28 Mar 2019 23:36:05 +0300
> > Cc: gdb-patches@sourceware.org
> >
> > сб, 23 мар. 2019 г. в 16:11, Eli Zaretskii <eliz@gnu.org>:
> > > Thanks, but isn't this a step backward? Would it make sense to have
> > > the hard-coded messages be translated instead? Or is that impossible
> > > for some reason?
> >
> > There is _nl_locale_name function in intl/localename.c, it could be
> > used to retrieve current locale name, which, in turn, could be used to
> > translate messages in FormatMessage. But when I include gettextP.h in
> > win32-low.c I got an error:
> > In file included from win32-low.c:38:0:
> > ../../intl/gettextP.h:71:8: error: inline variables are only available
> > with -std=c++1z or -std=gnu++1z [-Werror]
>
> Can you tell why you needed to retrieve the current locale's name?
>
> If gdbserver supports NLS and gettext, all you need is to wrap the
> untranslated messages in _().
next prev parent reply other threads:[~2019-03-29 8:42 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 ` Владимир Мартьянов [this message]
2019-03-29 9:29 ` Eli Zaretskii
2019-03-29 9:39 ` Владимир Мартьянов
2019-03-29 12:32 ` Eli Zaretskii
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=CAL5iTPJr_-WxFcCSFdq_CEoBHuq22FVr55aA1WQisO9DPiEv2w@mail.gmail.com \
--to=vilgeforce@gmail.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.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