All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: gettext in build system
Date: Tue, 17 Nov 2009 11:49:17 +0100	[thread overview]
Message-ID: <20091117104917.GA18850@thorin> (raw)
In-Reply-To: <20091116223252.GA21513@nubol.oskuro.net>

On Mon, Nov 16, 2009 at 11:32:52PM +0100, Jordi Mallach wrote:
> On Mon, Nov 16, 2009 at 08:56:06PM +0100, Robert Millan wrote:
> > > > > +#define _(str) gettext(str)
> > > > And I'm not sure if this is the right place to define _.  Isn't there
> > > > a system-wide definition?
> > > This, and others, sometimes go in a common .h to avoid duplication. Many
> > > grub utilities are going to add this kind of stuff.
> > I wonder where would we put this.  Is there any convention?
> 
> I'm not aware of any convention, not even for GNU packages. nls.h, i18n.h,
> grub-i18n.h. You name it. :)

Ok.  <grub/i18n.h> then.

> > > I haven't tested this patch yet, but I'm not sure if a bindtextdomain()
> > > call is needed here too.
> > This requires LOCALEDIR.  Should we add po.m4 in order to get this, or
> > just define it ourselves?
> 
> *shrug*, I think just assuming the usual $(datadir)/locale is ok. po.m4
> does provide checks for the gettext tools iirc, though, so that might
> be useful in its own right.

I enabled AM_GNU_GETTEXT() which drags that in, as well as a few of the
other declarations we needed.

Thanks!

-- 
Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."



  reply	other threads:[~2009-11-17 10:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-15 23:13 gettext in build system Robert Millan
2009-11-15 23:59 ` Robert Millan
2009-11-16  0:23   ` Colin Watson
2009-11-16 19:15     ` Robert Millan
2009-11-16 19:09   ` Jordi Mallach
2009-11-16 19:56     ` Robert Millan
2009-11-16 20:24       ` Robert Millan
2009-11-16 22:34         ` Jordi Mallach
2009-11-16 22:32       ` Jordi Mallach
2009-11-17 10:49         ` Robert Millan [this message]
2009-11-17 12:22           ` Robert Millan

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=20091117104917.GA18850@thorin \
    --to=rmh@aybabtu.com \
    --cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.