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: gettext util
Date: Sun, 28 Mar 2010 14:48:49 +0200	[thread overview]
Message-ID: <4BAF5031.7050807@gmail.com> (raw)
In-Reply-To: <20100327214237.GA19079@pina.cat>

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

Carles Pina i Estany wrote:
> So my concerns:
> a) It change a common practise (even when it's not the best one).
> Translators expects the way that it has been done until now, and I would
> like that somebody that it's not Grub (small i18n project) starts the
> change
>
>   
Jordi and Collin said that they are fed up with this "common practice"
> b) Makes the alignment more difficult
>   
Why not just do like

"  -h, --help                %s\n"
"  -V, --version             %s\n"
"  -v, --verbose             %s\n", _("display this message and exit"), _ ("print version information and exit"), _("print verbose messages")

We won't translate --help anyway.
> c) Makes the code a bit less clear
>   
Not if you use printf/sprintf templates
> Comment: sadly our grub.po already has someo of these long messages.
> Would you change it and "force" the translators to change? Or have the
> Grub domain with some long strings as short strings?
>   
Another possibility is to change them to short strings when we'll change
this string next time.
> Maybe Colin has things to say too.
>
> If next messages goes to the same direction (splitting) I'll propose a
> way to split some non-gettexted message in Grub and then apply the same
> to the other ones.
>
> (Mmm... a nice start would be to split the very-repeated:
> "  -h, --help                display this message and exit\n"
> "  -V, --version             print version information and exit\n"
> "  -v, --verbose             print verbose messages\n"
> "\n"
> "Report bugs to <%s>.\n"
>
> In different sentences for all messsages.
> )
>
> Cheers,
>
>   


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



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

  parent reply	other threads:[~2010-03-28 12:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-19 23:56 gettext util Carles Pina i Estany
2010-03-26 16:00 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-03-27  0:54   ` Carles Pina i Estany
2010-03-27  0:59     ` Carles Pina i Estany
2010-03-27 11:29     ` Jordi Mallach
2010-03-27 21:42       ` Carles Pina i Estany
2010-03-27 22:20         ` Colin Watson
2010-03-27 22:36           ` Carles Pina i Estany
2010-03-27 23:16             ` Colin Watson
2010-03-28 12:48         ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2010-03-28 22:05           ` 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=4BAF5031.7050807@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.