[Pkg-kbd-devel] Re: Ubuntu keyboard/installer plans

[Denis Barbier]

On Tue, Oct 03, 2006 at 04:51:12PM +0300, Anton Zinoviev wrote:
> I tested the new xkb files with console-setup.  This is the result for
> the mac variants:
> 
> ./kbdcompiler macintosh_old MyKeyboardNames.pl /usr/share/X11/xkb >macintosh_old.ekmap
> Compiling compact keymaps for macintosh_old...
> WARNING: Can not found "dvorak" in "macintosh_vndr/se".
> WARNING: Unknown X keysym "Eurosign"
> WARNING: Unknown X keysym "reserved"
[...]
> Computing differential matrix for macintosh_old...
> Reducing the keymaps for macintosh_old...
> Dumping the encoded keymaps for macintosh_old...
> gzip -9 <macintosh_old.ekmap >macintosh_old.ekmap.gz
> 
> I am not sure about the meaning of "reserved" and I suppose "Eurosign"
> should be replaced by "EuroSign" or "Euro".

Hey, it finds spelling mistakes in XKB files, that's great!
   Current    Fixed keysym
  Eurosign ---> EuroSign
  equals   ---> equal
  reserved ---> VoidSymbol  ('reserved' appears in bt, I guess that
          this is a placeholder to insert characters which are not
	  yet in Unicode)

Hangul is a valid keysym though.

On Tue, Oct 03, 2006 at 05:02:44PM +0300, Anton Zinoviev wrote:
> On Tue, Oct 03, 2006 at 04:51:12PM +0300, Anton Zinoviev wrote:
> > 
> > I looked at rules/base and I saw that macintosh is included in $macs.
> > Because of that the macintosh keycodes are used even with the new
> > powermacs.  With the old version the macintosh keycodes were used only
> > with "macintosh_old", wasn't this correct?
> 
> Ops, I didn't saw that keycodes/macintosh is also changed.. :-)
> 
> But this also means that the current console-setup is incompatible
> with the new xkeyboard-config.  There seams to be no relation between
> the X keycodes and the keycodes of the kernel.  Because of that
> ckbcomp has to use hardwired translation tables and to guess the
> architecture from the keyboard model.  Up to now keycodes/macintosh
> implied the old macintosh keycodes but now this depends on the model..

This also depends on kernel; old macintosh keycodes are generated by
kernel < 2.4.x (I do not remember the value of x); for etch, we can
assume that new macintosh keycodes are used.  They are similar to
PC keycodes.

I wanted to say in my previous mail that symbols/* now contain mac
variants, which are similar to symbols/macintosh_vndr/*.
It would be nice to find a solution so that $macs models look for
symbols in symbols/* without breaking current settings, but I failed,
so they will still look for symbols in symbols/macintosh_vndr.
But one can instead select a pc105 model and a mac variant, the same
symbols will then be obtained.
Can you get rid of symbols/macintosh_vndr in console-setup, and only
consider mac variants?  (and of course mac_nodeadkeys, fr_mac, etc)

Denis