|
| From: | Alan Zheng |
| Subject: | Re: Grub-devel Digest, Vol 58, Issue 8 |
| Date: | Tue, 9 Dec 2008 11:26:13 +0800 |
Send Grub-devel mailing list submissions to
address@hidden
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.gnu.org/mailman/listinfo/grub-devel
or, via email, send a message with subject or body 'help' to
address@hidden
You can reach the person managing the list at
address@hidden
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Grub-devel digest..."
Today's Topics:
1. Re: localization of Grub (Carles Pina i Estany)
2. configure fail for grub (Alan Zheng)
3. RE: configure fail for grub (James Shewey)
4. Re: localization of Grub (Carles Pina i Estany)
----------------------------------------------------------------------
Message: 1
Date: Mon, 8 Dec 2008 00:33:08 +0100
From: Carles Pina i Estany <address@hidden>
Subject: Re: localization of Grub
To: The development of GRUB 2 <address@hidden>
Message-ID: <address@hidden>
Content-Type: text/plain; charset=us-ascii
Hello again,
Let me to re-open this thread, where we were discussing about
localization and translation:
On Sep/28/2008, Robert Millan wrote:
> 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.
Do you mean the strings that are generated in standard Linux user-space
and written to grub.cfg?
What do you (everybody in the list) think about the text help that
appears here and there (output of Grub -usually shell- commands?)
Needed? Or these texts are good enough in English (like commands in the
programming languages)
> - 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 _()).
This part is more clear (at least theoretically, of course :-) )
I understand that all error messages, messages, etc. that Grub prints
while Grub is executing should be translated.
My understanding is that we should have some module to handle some
function (eg. _()), that would read some variable to choose to which
language, if available, translate some string. Like gettext, as you
said.
> I'd also recommend making the user interface similar to posix locales, for
> consistency's sake (which you know I hold dearly ;-)).
I agree
I'm not familiar in the .mo internals, I will take a look. I understand
that this gives us quite much flexibility, if we would implement
everything (like argument orders, etc.)
> 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.
As I said before by mail, grub.cfg don't have lot of UI strings.
Some, but not a lot.
I understand that we/I should adapt some scripts using, for example, this
guideline?:
http://www.gnu.org/software/automake/manual/gettext/Preparing-Shell-Scripts.html
(I haven't tested now, I think that some years ago I did some tests with
Bash and gettext)
--
Carles Pina i Estany GPG id: 0x17756391
http://pinux.info
------------------------------
Message: 2
Date: Mon, 8 Dec 2008 16:50:31 +0800
From: "Alan Zheng" <address@hidden>
Subject: configure fail for grub
To: address@hidden
Message-ID:
<address@hidden>
Content-Type: text/plain; charset="iso-8859-1"
Hello All:
When I configure grub-1.96, I got following error message:
configure: error: neither start nor _start is defined
Could anybody give me some ideas for it?
--
Best Regards
Alan Zheng
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.gnu.org/pipermail/grub-devel/attachments/20081208/75530ae2/attachment.html
------------------------------
Message: 3
Date: Mon, 8 Dec 2008 07:39:13 -0500
From: James Shewey <address@hidden>
Subject: RE: configure fail for grub
To: The development of GRUB 2 <address@hidden>
Message-ID: <address@hidden>
Content-Type: text/plain; charset="iso-8859-1"
Grub will not currently compile on 64 bit distros. Try compiling with a 32 bit live cd or a 32 bit VM (you can try virtualbox.org for this) and then copying the requisite files to the 64 bit OS.
-----Original Message-----
From: Alan Zheng <address@hidden>
Sent: Monday, December 08, 2008 3:50 AM
To: address@hidden
Subject: configure fail for grub
Hello All:
When I configure grub-1.96, I got following error message:
configure: error: neither start nor _start is defined
Could anybody give me some ideas for it?
--
Best Regards
Alan Zheng
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.gnu.org/pipermail/grub-devel/attachments/20081208/ebcd4533/attachment.html
------------------------------
Message: 4
Date: Mon, 8 Dec 2008 15:33:49 +0100
From: Carles Pina i Estany <address@hidden>
Subject: Re: localization of Grub
To: The development of GRUB 2 <address@hidden>
Message-ID: <address@hidden>
Content-Type: text/plain; charset=us-ascii
Hello,
On Dec/08/2008, Carles Pina i Estany wrote:
> I understand that we/I should adapt some scripts using, for example, this
> guideline?:
> http://www.gnu.org/software/automake/manual/gettext/Preparing-Shell-Scripts.html
>
> (I haven't tested now, I think that some years ago I did some tests with
They use gettext.sh file, in my Debian is in:
/usr/bin/gettext.sh, in package gettext-base . Do you think that this is
the best way? Do we assume that gettext.sh it's there, or we provide
backfail mechanism? (for example I don't think that this file comes with
cygwin...)
I can translate in two ways:
----
echo $(gettext "hello world")
eval_gettext "hello world";echo
----
so, with eval_gettext (comes from gettext.sh) or from gettext binary
straight.
eval_gettext helps a bit substituing shell variables:
# eval_gettext MSGID
# looks up the translation of MSGID and substitutes shell variables in the
# result.
eval_gettext () {
gettext "$1" | (export PATH `envsubst --variables "$1"`; envsubst
"$1")
}
But we could do it without gettext.sh
Which method do you think that we should use?
With failback option?
Thanks,
--
Carles Pina i Estany GPG id: 0x17756391
http://pinux.info
------------------------------
_______________________________________________
Grub-devel mailing list
address@hidden
http://lists.gnu.org/mailman/listinfo/grub-devel
End of Grub-devel Digest, Vol 58, Issue 8
*****************************************
| [Prev in Thread] | Current Thread | [Next in Thread] |