From: "Vesa Jääskeläinen" <chaac@nic.fi>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: SOC - SGD based on grub2 - Menu and scripting status
Date: Tue, 25 Apr 2006 23:40:38 +0300 [thread overview]
Message-ID: <444E8946.9000206@nic.fi> (raw)
In-Reply-To: <878xpubz36.fsf@xs4all.nl>
Marco Gerards wrote:
> "Yoshinori K. Okuji" <okuji@enbug.org> writes:
>
>> 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.
>
> Will this mean Adrian can use it for menu entries as well? I think
> that is what he wants to do.
I think this is one of the possibilities. Giving support to script in
form like this:
menuentry $gettext("My menu entry text") {
}
Though gettext is not perfect in all places, but could be enough for us.
I am still wondering what are the features of the scripting language.
Marco could you write some summary of your ideas somewhere and some
syntaxical examples?
Thanks,
Vesa Jääskeläinen
next prev parent reply other threads:[~2006-04-25 20:40 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
2006-04-24 18:36 ` Marco Gerards
2006-04-24 18:44 ` Yoshinori K. Okuji
2006-04-25 20:40 ` Vesa Jääskeläinen [this message]
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=444E8946.9000206@nic.fi \
--to=chaac@nic.fi \
--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.