All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: Build failures on Ubuntu due to gettext
Date: Tue, 08 Dec 2009 00:59:28 +0100	[thread overview]
Message-ID: <4B1D96E0.1020004@gmail.com> (raw)
In-Reply-To: <20091207233836.GA10791@riva.ucam.org>

[-- Attachment #1: Type: text/plain, Size: 1374 bytes --]

Colin Watson wrote:
> Furthermore, the style I suggested is used in many other GNU projects.
> Here are just a few examples:
>
>   coreutils/src/du.c:994:       error (0, 0, "%s", _("invalid zero-length file name"));
>   diffutils/src/sdiff.c:853:  fprintf (stderr, "%s", _("\
>   diffutils/src/sdiff.c-854-ed:\tEdit then use both versions, each decorated with a header.\n\
>   glibc/inet/rcmd.c:178:                              __fxprintf(NULL, "%s", _("\
>   glibc/inet/rcmd.c-179-rcmd: socket: All ports in use\n"));
>   gnulib/lib/xalloc-die.c:34:  error (exit_failure, 0, "%s", _("memory exhausted"));
>
>   
I have nothing against defining grub_putl_ (str); equivalent to
grub_printf ("%s\n", str); (defined as function if it's used extensively
for space reasons).
Just from your previous mails it seemed that you proposed to transform
strings like
grub_printf (_("Moving file %s to %s."), f1, f2); to grub_printf ("%s %s
%s %s.", _("Moving file"), f1, _("to"), f2);
to avoid translating format-strings which would be completely
untranslatable.
> Indeed, here's a commit from the gettext author using this style:
>
>   http://git.savannah.gnu.org/cgit/gettext.git/commit/?id=d5d1ae3b3c3ae2f837740e5f5d65326197ccdb98
>
> (Look for close_stdout_status in lib/closeout.c.)
>
>   


-- 
Regards
Vladimir 'φ-coder/phcoder' Serbinenko



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 293 bytes --]

  reply	other threads:[~2009-12-07 23:59 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-07 14:09 Build failures on Ubuntu due to gettext Colin Watson
2009-12-07 20:14 ` Carles Pina i Estany
2009-12-07 20:54   ` Colin Watson
2009-12-07 22:46     ` Carles Pina i Estany
2009-12-07 23:25       ` Vladimir 'φ-coder/phcoder' Serbinenko
2009-12-07 23:57         ` Colin Watson
2009-12-07 23:38       ` Carles Pina i Estany
2009-12-07 23:59         ` Colin Watson
2009-12-08  0:00       ` Colin Watson
2009-12-08  0:14         ` Carles Pina i Estany
2009-12-07 22:04 ` Vladimir 'φ-coder/phcoder' Serbinenko
2009-12-07 23:12   ` Colin Watson
2009-12-07 23:38     ` Colin Watson
2009-12-07 23:59       ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2009-12-08  0:10         ` Colin Watson
2009-12-08  0:15           ` Vladimir 'φ-coder/phcoder' Serbinenko
2009-12-09 23:57             ` Carles Pina i Estany
2009-12-10  0:07               ` Carles Pina i Estany
2009-12-10  0:38                 ` Carles Pina i Estany
2009-12-10  1:10           ` Robert Millan
2009-12-11  0:04             ` Carles Pina i Estany
2009-12-07 23:18   ` Carles Pina i Estany

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=4B1D96E0.1020004@gmail.com \
    --to=phcoder@gmail.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.