> > > after upgrading to Debian 3.0r0 (from 2.2r7), several applications had > > problems with the compose key, which allows me to enter characters like > > £ or ¥ etc. > > > > In the "gnome-terminal", I had to disable "Enable multi-byte mode" in > > the preferences, and it worked again. So I can use most programs now, > > except Lyx, where the compose key has no effect. > > This is the second report we've had of this ... compose works fine for > me. What xforms version are you using ? > > Can you run the program "fdesign" and compose in that ? > Yes, fdesign works fine with compose. libforms is version 0.89.0, Lyx is version 1.2.0.
The debug output is: -- $ lyx -dbg key Setting debug level to key Debugging `key' (Keyboard events handling) InitLyXLookup: creating an input context. InitLyXLookup: X locale modifiers are `' XFilterEvent WorkArea: Key is `' [0] WorkArea: Keysym is `' [0] Empty kdb action (probably composing) XLookupBoth " WorkArea: Key is `quotedbl' [34] WorkArea: Keysym is `quotedbl' [34] Workarea Diff: 4072797324 KeySym is quotedbl[34] State is [1] action first set to [-1] meta_fake_bit is [0] action now set to [-1] Key [action=-1][S-quotedbl] Removing modifiers... Action now set to [69] XLookupBoth u WorkArea: Key is `u' [117] WorkArea: Keysym is `u' [117] Workarea Diff: 351 KeySym is u[117] State is [0] action first set to [90] meta_fake_bit is [0] action now set to [90] Key [action=90][u] Cannot decode: u SelfInsert arg[`u'] TextCache: BufferView::buffer CloseLyXLookup: destroying input context -- In this scenario, the compose key sequence produced "u rather than ü. -- Regards, Cyrille Artho - http://artho.com/ - Tel. +41 - [0]1 - 632 09 88 There is no surer way to ruin a good discussion than to contaminate it with the facts. -- Cecil Adams
