Nerijus Baliunas wrote:
> > I think the correct solution is a redefinition of a portion of latin
> > map with desired keys (as in li) which should be put in a separate section
> > of li symbol map. Then the user could ask for described behaviour as:
> > 
> > XkbSymbols "us+li(us_li_accented),li"
> 
> Should it be XkbSymbols or XkbLayout?

  XkbLayout of course.

> I tried  Option "XkbSymbols" "pc/lt+pc/lt(lt_us)", but then it does not
> work correctly (Enter key doesn't work for example).

  You can use the setxkbmap program with a verbose option to see how the list
of layouts should be converted to the XkbSymbols argument.
  For example
setxkbmap -v 10 -layout "lt,lt(lt_us)"
shows something like
.....
Trying to build keymap using the following components:
keycodes:   xfree86+aliases(qwerty)
types:      complete
compat:     complete
symbols:    pc/pc(pc104)+pc/lt+pc/lt(lt_us):2

  BTW 'pc/pc(pc...)' is responsible for the Enter key and other non-alphabetic
keys.

> If I use
> Option "XkbLayout"  "lt,lt(lt_us)", it works, but only if I remove
> include "pc/latin" from xkb_symbols "lt_us" {}. Otherwise I get
> 
> xkbcomp reports:
> Error: Map "pc/latin(basic)" included more than once
> Later inclusion ignored
> Abandoning symbols file "lt_us"
> Abandoning symbols file "default"

  Oops. It is a bug.  I will try to fix it.

-- 
 Ivan U. Pascal         |   e-mail: [EMAIL PROTECTED]
   Administrator of     |   Tomsk State University
     University Network |       Tomsk, Russia
_______________________________________________
I18n mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/i18n

Reply via email to