All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: localization of Grub
Date: Sun, 14 Dec 2008 02:02:17 +0100	[thread overview]
Message-ID: <20081214010217.GA25952@thorin> (raw)
In-Reply-To: <20081207233308.GA15844@pina.cat>

On Mon, Dec 08, 2008 at 12:33:08AM +0100, Carles Pina i Estany wrote:
> >   - gettextise the util tools, so they can be translated as normal programs.
> 
> Do you mean the strings that are generated in standard Linux user-space
> and written to grub.cfg?

I mean every command produced out of util/.  grub-mkconfig, grub-probe,
grub-setup, etc.

> What do you (everybody in the list) think about the text help that
> appears here and there (output of Grub -usually shell- commands?)
> Needed? Or these texts are good enough in English (like commands in the
> programming languages)

I think in long-term it would probably be a good thing to gettextize
everything; but short-term we should focus on the util/ part IMHO.

> This part is more clear (at least theoretically, of course :-) )
> I understand that all error messages, messages, etc. that Grub prints
> while Grub is executing should be translated.
> 
> My understanding is that we should have some module to handle some
> function (eg. _()), that would read some variable to choose to which
> language, if available, translate some string. Like gettext, as you
> said.

Yep, something like that.  Also, it needs to be registered in a function
pointer, so that kernel won't need it unconditionally.

> I understand that we/I should adapt some scripts using, for example, this
> guideline?:
> http://www.gnu.org/software/automake/manual/gettext/Preparing-Shell-Scripts.html

Probably.  I'm afraid I'm no l10n expert :-(

-- 
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."



      parent reply	other threads:[~2008-12-14  1:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-26  8:16 localization of Grub Carles Pina i Estany
2008-09-26  8:34 ` Carles Pina i Estany
2008-09-26 11:13   ` Felix Zielcke
2008-09-26 12:19     ` Carles Pina i Estany
2008-09-28 13:39       ` Robert Millan
2008-09-28 21:49         ` Carles Pina i Estany
2008-09-29 14:59           ` Robert Millan
2008-09-29 18:48             ` Vesa Jääskeläinen
2008-09-29 21:47               ` Javier Martín
2008-09-29 23:14               ` Carles Pina i Estany
2008-09-29 22:55             ` Carles Pina i Estany
2008-12-07 23:33         ` Carles Pina i Estany
2008-12-08 14:33           ` Carles Pina i Estany
2008-12-14  1:03             ` Robert Millan
2009-01-04 11:36               ` Carles Pina i Estany
2008-12-14  1:02           ` 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=20081214010217.GA25952@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.