From: Pavel Roskin <proski@gnu.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Fw: gettext support
Date: Thu, 25 Jun 2009 23:09:02 -0400 [thread overview]
Message-ID: <1245985742.23442.249.camel@mj> (raw)
In-Reply-To: <20090625212047.GA27921@pina.cat>
On Thu, 2009-06-25 at 22:20 +0100, Carles Pina i Estany wrote:
> IMHO: b1 looks more professional/nicer and complete than b2, that looks
> like a quick-patch, no? But both has similar results.
I realize now that the comparison with the kernel was wrong. The kernel
output can be hidden from the user. But GRUB is interactive by design.
My main concern is the size of the files we install in /boot/grub. It's
approaching one megabyte already, without the localization. That's why
I'm trying to avoid a large number of *.mo files in /boot/grub.
On the other hand, incorporating a dictionary into grub.cfg would be
equivalent to having just one set of strings under /boot/grub. But we
can achieve the same by having one *.mo file in /boot/grub.
I agree, using gettext is a more solid approach technically.
But installing all *.mo files to /boot/grub would be an overkill in many
cases. I think copying the file for the current language should be
enough. The same language should be specified in grub.cfg when it's
generated.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2009-06-26 3:09 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
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 [this message]
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=1245985742.23442.249.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.