Re: RFC: (set-xkb-cyrillic-charset "koi8-r") for non-Mule XEmacs

MB> keysymdef.h has been around for eons. I.e. before X11R6. By the way, while we're at it, probably you know: what is the proper function to get X keysym-code (0x6ff) from the string like "XK_Cyrillic_HARDSIGN"? If I'm going to implement (x-set-keysym-translation), I'll need that one.. MB> Probably Koi8 is the dominant encoding in Russia, and it would be MB> more useful for xemacs to conform to that. But most of the MB> computers I have acccess to have iso-8859-5 fonts. If that was Solaris, then it's ok, because they know only of ISO standards and not about actual situation :) Most Linux installations use koi8-r (and have to support 8859-5 for reasons that I'm trying to fix :) MB> Unfortunately, although it shouldn't matter what internal MB> representation is used for characters internally, xemacs prefers MB> to have the fonts it uses match the encoding in the internal MB> representation. MB> When designed properly, there should only be one internal MB> representation for a given character - i.e. we should not have MB> iso8859-5 and koi8 represented separately internally. This means MB> that the event-Xt.c code should not know anything about koi8. MB> Mule is hard. Good luck. I am not speaking of Mule here :) Mule works mostly ok (see parallel thread). I need to somehow cover simplest cases of non-Mule one-byte encodings and with straightforward internal representations. MB> Alexey, I encourage you to try to be the Russian maintainer for MB> XEmacs. I do not know about full-size maintenance, but I'll surely try to fix once and for all every subsystem I use (gnus, vm, ispell, psgml) if need be (sometimes it is). :) --alexm