[mule] xemacs doesn't recognize some symbols

[Aidan Kehoe]

 Ar an t-ocht? l? is fiche de m? Deireadh F?mhair, scr?obh stephen at xemacs.org: 

 > Aidan Kehoe writes:
 > 
 >  >  > Don't some iso8859 charsets have them ?
 >  > 
 >  > No. In non-East-Asian practice yes, since the Microsoft extensions of the
 >  > ISO character sets included them between 0x80 and 0xA0.
 > 
 > *Please* be careful.  The Microsoft coded character sets are *not*
 > extensions according to any of the relevant standards except as
 > subsets of Unicode.  

Agreed. But Andriy?s not from East Asia, and only East Asia cares about
those standards, especially ISO 2022. Non-ISO 2022 Cyrillic-alphabet and
Roman-alphabet standards are mundane, and useful software in these regions
needs to be able to deal with them.

 > [...] Aidan, are your patches #ifdef'able? If so, maybe it's time some
 > other interested parties got a look at them, ready for prime time or not.

I was being pessimistic; as the patch in question currently stands, its
behaviour is not any worse than what?s in the source tree. I intend
committing it tomorrow, after some further confirmation that its defaults
are okay.

 >  > (If it?s falling back, it?s to the US layout, yes.)
 > 
 > IIRC, XEmacs has no concept of keyboard layout (at least in X11).  It
 > just accepts keysyms from the server.

My committed support for the Russian-C-x problem understanding of the US
keyboard layout into the editor. 

 >  > (unless (>= 5 emacs-minor-version)
 >  >   (require 'un-define))
 > 
 >     (unless (emacs-version>= 21 5 6) (require 'un-define))
 > 
 > is a much better idea.

Indeed it is. 

-- 
Santa Maradona, priez pour moi!