Re: Latin 9 characters cropping up from XKB usage

Hrvoje> Eek. That is amazingly evil. Hrvoje, calm down. It is _not_ evil. That file is loaded only on explicit user request (at least, that's why I put it in the packages) and if those keysyms have associated characters, they will not be overridden. The bug is that they don't get assigned to Latin 2 characters in a Latin 2 locale; let's fix that bug. What more could you reasonably ask for? I would guess that what needs to be done in principle is to extend the code in keymap.c to do all the ISO 8859 keysyms, but that's probably not in the cards for 21.4 and should be done very differently for 21.5 (which is not going to have Mule charsets internally in the near future if I read the runes correctly). So the thing to do is to have a similar file for Latin 2 (etc), and have the language environment code invoke it. This isn't ideal in this case (it does seem unlikely that very many people are using direct entry of Scaron and friends in Latin 9) but I would guess that there are other cases where hardcoding at dump time would cause annoying shadows. Hrvoje> The former is t. How did that happen? If we did that behind your back, it's an XEmacs bug; that support was designed to be loaded on request by people who need Latin 9 support as their primary environment---little thought has been put into making it loadable by default, and none in combination with non-Latin-9 environments. If you did it, I'd like to know why so I can figure out how to ensure that you can fixup keysym translations before the latin9 support gets loaded. Hrvoje> I still think it makes sense not to force scaron and Hrvoje> zcaron into Latin 9, where they clearly don't belong. The ISO disagrees. Please, let's find a solution that allows us to support _both_ coded character sets as defined in the standard. Hrvoje> Even if it worked, it wouldn't be a good workaround. Hrvoje> People *do* switch keyboards, and switching keyboards Hrvoje> can't be expected to break things. "The X Window System. Live the horror." Switching keyboards has always broken things for me. The most recent Debian upgrades to X broke my keyboard out from under me. And of course XKB in XFree86 and possibly other X11 distros is deliberately backward incompatible with XEmacs and other apps that handle legacy keyboards in a sophisticated way. This stuff is a nightmare, and it will only get worse if we deliberately write code that doesn't conform to the existing standards. -- School of Systems and Information Engineering http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Ask not how you can "do" free software business; ask what your business can "do for" free software.