Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: teawater <teawater@gmail.com>, Eli Zaretskii <eliz@gnu.org>,
		"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [RFA] Add _() to query
Date: Tue, 24 Feb 2009 14:57:00 -0000	[thread overview]
Message-ID: <20090224144826.GA5387@caradoc.them.org> (raw)
In-Reply-To: <20090224133929.GA30561@host0.dyn.jankratochvil.net>

On Tue, Feb 24, 2009 at 02:39:29PM +0100, Jan Kratochvil wrote:
> On Tue, 24 Feb 2009 14:32:55 +0100, Daniel Jacobowitz wrote:
> > On Tue, Feb 24, 2009 at 03:10:51PM +0800, teawater wrote:
> > > I remember you told me that you want to add _() to all query.
> > > I make a patch for it. Do you think it's OK?
> > 
> > Before this goes in, could someone see if we could use xgettext
> > --keyword instead?  That would let us translate messages in
> > one place instead of all over.
> 
> The standard for localized messages is _().  Making the localization more
> magic makes the GDB project less viable for possible development newcomers.

I have trouble believing that.

I got this idea from GCC, which has used it for as long as I can
remember.  If you pass --keyword=query, and use N_() inside the body
of query, xgettext will localize all arguments to query in the entire
program.

This is better for code size and for readability.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2009-02-24 14:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-24 10:52 teawater
2009-02-24 14:33 ` Daniel Jacobowitz
2009-02-24 14:38   ` Jan Kratochvil
2009-02-24 14:57     ` Daniel Jacobowitz [this message]
2009-02-24 15:32       ` Jan Kratochvil
2009-02-24 19:46 ` Eli Zaretskii
2009-02-25  7:18   ` teawater

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=20090224144826.GA5387@caradoc.them.org \
    --to=drow@false.org \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --cc=teawater@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