From: Pavel Roskin <proski@gnu.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Fw: gettext support
Date: Sun, 21 Jun 2009 15:14:59 -0400 [thread overview]
Message-ID: <1245611699.4250.19.camel@mj> (raw)
In-Reply-To: <20090621184230.GA21495@thorin>
On Sun, 2009-06-21 at 20:42 +0200, Robert Millan wrote:
> On Sun, Jun 21, 2009 at 06:22:36PM +0100, Carles Pina i Estany wrote:
> > > > It's not a problem. We need two locations anyway: one where make install
> > > > copies them and the other one where ./grub-install copies them. Would it be
> > > > possible to use /usr/share/grub/locale/$LANG.mo rather than
> > > > /usr/share/locale/$LANG/LC_MESSAGES/grub.mo? It would make grub-install
> > > > easier
> > >
> > > No, for system locales we need to use standard locations, or the userland
> > > gettext won't find them.
> >
> > No, for example:
>
> Uhm, okay. But I'd really prefer if we could stick to the standard paths
> anyway :-)
Do we really need to localize the bootloader? I think localization of
the tools should be sufficient.
Even Linux kernel is not localized, and it's more likely to tell the
user something important than the bootloader. Besides, how would you
ask the user about the preferred language at the boot time? If anything
goes wrong, it's likely that the translations won't be available, and if
everything is fine, the user would just pick an item from the menu, and
the menu can be localized when it's generated.
As for the tools localization, we should follow the standards.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2009-06-21 19:15 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-16 21:47 Fw: gettext support Carles Pina i Estany
2009-06-16 22:37 ` Vladimir 'phcoder' Serbinenko
2009-06-17 11:37 ` Vladimir 'phcoder' Serbinenko
2009-06-17 20:29 ` Carles Pina i Estany
2009-06-18 13:38 ` Robert Millan
2009-06-18 14:45 ` Vladimir 'phcoder' Serbinenko
2009-06-18 21:07 ` Carles Pina i Estany
2009-06-19 17:22 ` Vladimir 'phcoder' Serbinenko
2009-06-19 23:13 ` Carles Pina i Estany
2009-06-20 0:17 ` Vladimir 'phcoder' Serbinenko
2009-06-19 10:32 ` Robert Millan
2009-06-18 19:30 ` Carles Pina i Estany
2009-06-18 20:56 ` Carles Pina i Estany
2009-06-19 10:37 ` Robert Millan
2009-06-19 10:42 ` Vladimir 'phcoder' Serbinenko
2009-06-21 11:07 ` Robert Millan
2009-06-21 17:22 ` Carles Pina i Estany
2009-06-21 18:42 ` Robert Millan
2009-06-21 19:14 ` Pavel Roskin [this message]
2009-06-21 21:09 ` Carles Pina i Estany
2009-06-21 21:18 ` Robert Millan
2009-06-21 21:28 ` Carles Pina i Estany
2009-06-21 22:03 ` Vladimir 'phcoder' Serbinenko
2009-06-21 22:31 ` Carles Pina i Estany
2009-06-21 22:47 ` Robert Millan
2009-06-21 22:56 ` Colin Watson
2009-06-22 19:03 ` Jordi Mallach
2009-06-22 19:42 ` Javier Martín
2009-06-23 10:05 ` Jordi Mallach
2009-06-23 10:45 ` Javier Martín
2009-06-24 9:17 ` Jordi Mallach
2009-06-21 21:20 ` Vladimir 'phcoder' Serbinenko
2009-06-21 23:42 ` Pavel Roskin
2009-06-22 9:39 ` Robert Millan
2009-06-22 10:16 ` Colin Watson
2009-06-21 21:14 ` Robert Millan
2009-06-25 21:20 ` Carles Pina i Estany
2009-06-26 3:09 ` Pavel Roskin
2009-06-26 12:47 ` Robert Millan
2009-06-26 15:31 ` Pavel Roskin
2009-06-26 23:42 ` Carles Pina i Estany
2009-06-19 13:55 ` Jordi Mallach
2009-06-19 14:32 ` Vladimir 'phcoder' Serbinenko
2009-06-21 11:17 ` Robert Millan
2009-06-19 23:08 ` Carles Pina i Estany
2009-06-21 11:09 ` 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=1245611699.4250.19.camel@mj \
--to=proski@gnu.org \
--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.