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, 28 Sep 2008 15:39:07 +0200	[thread overview]
Message-ID: <20080928133907.GC23805@thorin> (raw)
In-Reply-To: <20080926121909.GB9530@pina.cat>

On Fri, Sep 26, 2008 at 02:19:09PM +0200, Carles Pina i Estany wrote:
> > 
> > This is wanted but nobody did work on this yet afaik.
> > It would be good if there would be multiple keyboard layouts too I
> > think.
> 
> I think that different keyboard layouts it's even more important than
> different languages...
> 
> Do we have any plan? Maybe I will take a look (but during 20 days in
> october I will not have lot of time :-( so not sure if I will do it
> after October or not, I will see...)
> 
> Any suggestion for the implementation? How user would change the
> keyboard layout? Or maybe at beginning some setting (variable) at
> grub.cfg?

Hi,

It's very nice you want to work on localisation.  This is a very welcome
feature (and I think it's been discussed before).

(I assume we're talking about a gettext equivalent rather than keyboard
layouts, which is a separate -but also nice- feature)

My recommendation for a roadmap (please comment/discuss/challenge/etc!) would
be:

  - gettextise the util tools, so they can be translated as normal programs.

  - add support to grub (a gettext module or so) so that it can load our .mo
    files and obtain strings from it, by implementing gettext() (aka _()).

I'd also recommend making the user interface similar to posix locales, for
consistency's sake (which you know I hold dearly ;-)).

Even if you only have time/interest to implement the first part, this is
already a significant benefit.  Keep in mind that grub.cfg generation is done
by update-grub which happens entirely on userland, so we get translated menu
entries that way.

-- 
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:[~2008-09-28 13:41 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 [this message]
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

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=20080928133907.GC23805@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.