From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: SOC - SGD based on grub2 - Menu and scripting status
Date: Mon, 24 Apr 2006 20:10:29 +0200 [thread overview]
Message-ID: <200604242010.29290.okuji@enbug.org> (raw)
In-Reply-To: <87mzeac40c.fsf@xs4all.nl>
On Monday 24 April 2006 18:49, Marco Gerards wrote:
> > 4) What is the best way for dealing with languages and translations
> > when developing?
>
> We are thinking about i18n support. This is something about this on
> the wiki, I think.
I don't think this part is described well in the wiki. So I describe my idea
here:
- GRUB needs to have a locale variable to determine a language.
- GRUB needs to have gettext or something similar to translate messages.
- GRUB needs to be able to generate .po files compatible with gettext.
- GRUB needs to support message translations by scripting as well as by C
code.
These are not implemented at all yet, but not difficult. I expect that this
would take 2 weeks, if one works in full time.
Okuji
next prev parent reply other threads:[~2006-04-24 18:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-24 10:48 SOC - SGD based on grub2 - Menu and scripting status adrian15
2006-04-24 16:49 ` Marco Gerards
2006-04-24 18:10 ` Yoshinori K. Okuji [this message]
2006-04-24 18:36 ` Marco Gerards
2006-04-24 18:44 ` Yoshinori K. Okuji
2006-04-25 20:40 ` Vesa Jääskeläinen
2006-04-25 20:46 ` Marco Gerards
[not found] <200604251605.k3PG58Ax008963@dell01.dinaserver.com>
2006-04-28 11:42 ` adrian15
2006-05-01 18:57 ` Marco Gerards
2006-04-28 11:48 ` adrian15
[not found] <200605011855.k41ItvdZ029423@dell01.dinaserver.com>
2006-05-02 16:18 ` adrian15
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=200604242010.29290.okuji@enbug.org \
--to=okuji@enbug.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.