Dekel Tsur <[EMAIL PROTECTED]> writes:
| > The whole keymap-stuff was never very good supported by LyX, and IMHO
| > it really has nothing to do in LyX. It belongs in the desktop.
| >
| > I'd vote for removing it completely.
| > (and before 1.2.0)
| >
| > The solution for users the:
| > - to use a desktop with support for changing/different
| > keyboard layouts
| > - use several .xmodmaps and load/unload them as needed.
| >
| > Then it will also work for all applications, not just for LyX.
|
| I don't know if this is a good idea:
|
| 1. Setting the X keymap might not be easy in some cases. Furthermore, in many
| distributions there are no keymaps for some languages (e.g. Hebrew, Arabic).
Right... but this is not _reall_ LyX' problem. (unfortunately since we
now have kmap it is... _but_ we could provide the modmap files (crated
from the kmap files))
When is it hard to set the xmodmap?
| 2. To do it correctly, it should be done after we changed to 32bit text
| representation.
why?
| 3. What happen when the user needs two or more keymaps (e.g latin keymap and
| Hebrew keymap) ?
| Is it easy to do ?
For the Desktop? Yes.
| Does the application (lyx) know when the keymap has changed ?
Yes, X (in this case) takes care of that.
| Can the application change the keymap ?
yes... (but we do not want it to if the application is lyx)
| 4. There are several method than can be used: setxkbmap, xmodmap, and gui
| programs like kikbd(in KDE1). Is there a difference between them, and do
| the answer to (3) depends on which method you use ?
I do not think so. On X they all end up doing the same: modifying the
xmodmap/xkbd.
| 5. What about ports to OS's which don't support keymaps ?
They usually support something "better", take the keyboard support in
WinX f.ex. I can think of a single modern desktom that does not
support this.
--
Lgb
