Hello,
> The "Error loading new keyboard description" is suspicious. I followed
> Ivan Pascal's example from late July and put the following text in a file:
>
> xkb_keymap {
> xkb_keycodes { include "xfree86+aliases(qwerty)" };
> xkb_types { include "complete" };
> xkb_compat { include "complete" };
> xkb_symbols { include
> "pc/pc(pc104)+pc/us_intl+pc/us:2+group(win_switch)" };
> xkb_geometry { include "pc(pc104)" };
> };
Good investigation. But 'us_intl' map can't be combined with other layouts
(at least now). It is the reason why setxkbmap can't load such configuration.
On the other hand 'us_intl' has all symbols from 'us' map. Use just
Option "XkbLayout" "us_intl"
Option "XkbOptions" "grp:win_switch"
and Win keys become AltGr key which allow you get quotas (and some other
symbols).
Regarding 'dead keys problem' I can say that ...
If they work in KDE and Gnome applications it means that the keyboard map
is right. The thing is those toolkits have own module that composes a symbol
from dead_key+key sequences. But other applications rely on Xlib's compose
mechanism and it seems that the problem is there.
Xlib gets all needed data from Compose file which should be found using
X11R6/lib/X11/locale/compose.dir 'registry' file. As I see your locale
is 'C' (the default locale). Look into this registry file and find a string
<some dir>/Compose: C
There "some dir" means a directory in X11R6/lib/X11/locale/ .
Check the Compose file in this directory. I suspect it absents or is empty.
BTW, could you say a couple of words about your OS and distribution ?
--
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
