Hi,
when using LyX 1.1.6fix3 with localized X keyboard (no LyX's kmap
is used) everything works fine except for one character: \'o
(/oacute in PostScript terminology). When pressing the particular
keys (dead key for acute and o), the result is \'n (/nacute).
Fortunately, the letter is pretty rare in Czech documents, so
that I can easily owercome the problem by copying it from another
X applications through clipboard.
What is even more surprising is that \'O (/Oacute) which is even
more rare, works quite well.
Of course, everything is OK when plain X applications (xedit) are
used.
See exceprt from xev output when the particular key was used.
KeyPress event, serial 21, synthetic NO, window 0x3800001,
root 0x25, subw 0x0, time 1201421911, (164,12),
root:(776,181),
state 0x10, keycode 21 (keysym 0xfe51, dead_acute),
same_screen YES,
XLookupString gives 1 characters: "´"
KeyRelease event, serial 22, synthetic NO, window 0x3800001,
root 0x25, subw 0x0, time 1201421995, (164,12),
root:(776,181),
state 0x10, keycode 21 (keysym 0xfe51, dead_acute),
same_screen YES,
XLookupString gives 1 characters: "´"
KeyPress event, serial 24, synthetic NO, window 0x3800001,
root 0x25, subw 0x0, time 1201422288, (164,12),
root:(776,181),
state 0x10, keycode 32 (keysym 0x6f, o), same_screen YES,
XLookupString gives 1 characters: "o"
KeyRelease event, serial 24, synthetic NO, window 0x3800001,
root 0x25, subw 0x0, time 1201422366, (164,12),
root:(776,181),
state 0x10, keycode 32 (keysym 0x6f, o), same_screen YES,
XLookupString gives 1 characters: "o"
Does anybody know the reason for this beahvior and some solution
to it?
Thanks a lot
Matej
--
Matej Cepl, [EMAIL PROTECTED]
138 Highland Ave. #10, Somerville, Ma 02143, (617) 623-1488
Economics is the only discipline where two people can win a Nobel
Prize for saying exactly the opposite thing!
-- Eamonn Butler of Adam Smith Institute
on Nobel Prize awards for year 2001
