All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carles Pina i Estany <carles@pina.cat>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: keyboard layouts
Date: Tue, 12 Jan 2010 23:29:59 +0000	[thread overview]
Message-ID: <20100112232959.GA6071@pina.cat> (raw)
In-Reply-To: <20100112225354.GL5847@riva.ucam.org>


Hi,

On Jan/12/2010, Colin Watson wrote:
> On Tue, Jan 12, 2010 at 09:47:43PM +0000, Carles Pina i Estany wrote:
> > Plan:

> > * Approach 2
> > Small program (I guess that you prefer C, Python would be nice too) that
> > when Grub is installed would process the /usr/share/X11/xkb/symbols
> > files and generates the files that Grub will read. Code to read this
> > files would be much easier than before.
> > 
> > This way, the layout tables could stay in /boot/grub/layouts . These
> > files would look like keycode - symbol pairs. Everything already in
> > binary, and only for the things that differ from English.
> > 
> > So, if a layout has 40 different keycode-symbol pairs compared with
> > English, this would be 80 bytes per layout. Probably will be more, but
> > it should be of this order of magnitude.
> 
> I can't remember whether I mentioned this before, but have a look at

I haven't read about it previously.

> the gfxboot-theme-ubuntu package in Ubuntu, specifically the
> scrape-console-setup script.  It makes use of console-setup to process
> XKB keymaps into a form that can then be run through loadkeys and
> reformatted so that gfxboot can use them.  A similar approach might be
> feasible in GRUB.

Legal question: gfxboot-theme-ubuntu is licensed under GPL 2. I
understand that this means that we cannot share code. In the other hand,
I think that you are the author, so you could give the copyright of this
code to the FSF if needed. Is it possible?

Integration question: some of that code is done using Perl. Actually are
quite small scripts (373 lines the longer one). I don't know if we want
to add Perl as a Grub dependency :-/, or if it's worth. We can redo the
script in C.

Ok, the process of scrape-console-setup (I have not been able to test it
yet) is to use ckbcomp to convert from XKB keymaps to the "loadkeys"
keymaps, and then does some process on this second keymaps.

My approach was avoiding ckbcomp (actually I didn't know it :-) ). The
loadkeys keymaps are easier to parse, so for me looks fine to use. In
the other hand adds a new dependency, only for the laziness of
processing the XKB layouts.

Can you write in two lines the format of the layout that gfxboot use?
(else I will try to generate it soon...)

Thanks,

-- 
Carles Pina i Estany
	http://pinux.info



  reply	other threads:[~2010-01-12 23:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-12 21:47 keyboard layouts Carles Pina i Estany
2010-01-12 22:53 ` Colin Watson
2010-01-12 23:29   ` Carles Pina i Estany [this message]
2010-01-12 23:51     ` Colin Watson
2010-01-13  9:24 ` Yves Blusseau
2010-01-13 16:23   ` Vladimir 'φ-coder/phcoder' Serbinenko
  -- strict thread matches above, loose matches on Subject: below --
2010-02-09 23:23 Carles Pina i Estany
2010-03-19 23:45 Carles Pina i Estany
2011-04-22 22:34 Keyboard layouts (was Re: GRUB 1.99~rc2 released) Vladimir 'φ-coder/phcoder' Serbinenko
2011-05-23 13:22 ` Keyboard layouts Treutwein Bernhard

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=20100112232959.GA6071@pina.cat \
    --to=carles@pina.cat \
    --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.