All of lore.kernel.org
 help / color / mirror / Atom feed
From: adrian15 <adrian15@raulete.net>
To: grub-devel@gnu.org
Subject: Re: SOC - SGD based on grub2 - Menu and scripting status
Date: Fri, 28 Apr 2006 13:48:03 +0200	[thread overview]
Message-ID: <445200F3.5060602@raulete.net> (raw)
In-Reply-To: <200604251605.k3PG58Ax008963@dell01.dinaserver.com>

> On Monday 24 April 2006 20:36, Marco Gerards wrote:
> 
>>Will this mean Adrian can use it for menu entries as well?  I think
>>that is what he wants to do.
> 
> 
> In my idea, yes. I can say anything before implementing. ;)
> 
> Okuji

Yes... The thing that when meaning translation I was thinking about SGD, 
which is kind of a GUI for Grub so... I did not think about Grub 
messages but to menu entries as Marco suggested.

However you're right Grub messages could also be translated.

Currently I have SGD (only menu entries) translated to various languages 
with a three-level structure... one for algorithm... one for "kind of 
universal language" and one for the actual languages. It's implemented 
with bash variables and uses sed and other unix tools and it is not 
perfect...

I know there was this gettext thing and in the first place I didn't get 
to work it with bash (I think I needed to recompile it) so I discarded 
the idea.

Maybe I will take a look at gettext again for SG2D.

adrian15



  parent reply	other threads:[~2006-04-28 11:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200604251605.k3PG58Ax008963@dell01.dinaserver.com>
2006-04-28 11:42 ` SOC - SGD based on grub2 - Menu and scripting status adrian15
2006-05-01 18:57   ` Marco Gerards
2006-04-28 11:48 ` adrian15 [this message]
     [not found] <200605011855.k41ItvdZ029423@dell01.dinaserver.com>
2006-05-02 16:18 ` adrian15
2006-04-24 10:48 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
2006-04-25 20:46         ` Marco Gerards

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=445200F3.5060602@raulete.net \
    --to=adrian15@raulete.net \
    --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.