All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: Jordi Mallach <jordi@gnu.org>
Cc: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: gettextizing
Date: Mon, 23 Nov 2009 17:41:41 +0100	[thread overview]
Message-ID: <20091123164141.GA1378@thorin> (raw)
In-Reply-To: <20091123162851.GA4462@nubol.oskuro.net>

On Mon, Nov 23, 2009 at 05:28:51PM +0100, Jordi Mallach wrote:
> > > -  grub_printf ("\nPress any key to continue...");
> > > +  grub_printf (_("\nPress any key to continue..."));
> > 
> > I'm not sure if the spaces and newlines here would be a problem.  Jordi,
> > any comment?
> 
> Not a big issue in this case. However, it makes it difficult to reuse these
> strings, ie we can end up having 3 different strings:
>  - \nPress any key to continue...
>  - Press any key to continue...
>  - Press any key to continue...\n
> 
> which makes it easy to make different translations for the same string if the
> translator isn't careful.

Thanks Jordi.  This made me think, it also makes GCC allocate the string
3 times.  So one more reason to handle those!

-- 
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-23 16:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-22 22:28 gettextizing Carles Pina i Estany
2009-11-23 11:56 ` gettextizing Robert Millan
2009-11-23 16:28   ` gettextizing Jordi Mallach
2009-11-23 16:41     ` Robert Millan [this message]

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=20091123164141.GA1378@thorin \
    --to=rmh@aybabtu.com \
    --cc=grub-devel@gnu.org \
    --cc=jordi@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.