From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: gettext order
Date: Mon, 23 Nov 2009 13:18:20 +0100 [thread overview]
Message-ID: <4B0A7D8C.6000104@gmail.com> (raw)
In-Reply-To: <20091123115833.GC25009@thorin>
[-- Attachment #1: Type: text/plain, Size: 1351 bytes --]
Robert Millan wrote:
> On Mon, Nov 23, 2009 at 01:18:18AM +0100, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
>
>> Carles Pina i Estany wrote:
>>
>>> Hello,
>>>
>>> Tomorrow Monday I will probably gettextize the help of the all
>>> grub_register_command.
>>>
>>> Is it all right?
>>>
>>> In general, I would translate mainly all grub_printf that has user
>>> messages. I will do it in a different patch set than the
>>> grub_register_command.
>>>
>>>
>>>
>> If you see a good spot where all messages should be translated avoid
>> adding _ to it. Function calls are expensive.
>>
>
> Uhm I agree, but I'm not sure if grub_register_command() would be such
> spot. Are we sure we want to translate _all_ of its messages?
>
>
We don't have to translate all of arguments. All depends on how we
declare gettext keywords
> --
> 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."
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
>
>
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 293 bytes --]
next prev parent reply other threads:[~2009-11-23 12:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-23 0:15 gettext order Carles Pina i Estany
2009-11-23 0:18 ` Vladimir 'φ-coder/phcoder' Serbinenko
2009-11-23 11:58 ` Robert Millan
2009-11-23 12:18 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2009-11-23 11:59 ` 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=4B0A7D8C.6000104@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.