> That I believe maps to the high keysyms mentioned in the Unicode FAQ:
> "any UCS character in the range U-00000000 to U-00FFFFFF can be
> represented by a keysym value in the range 0x01000000 to 0x01ffffff".
> The question is, if I represent a character which already has a keysym
> in X (ike hebrew or european characters) with UXXXX, will applications
> understand it?
As long as they look at the characters produced rather than the keysyms,
why shouldn't they? The keysyms for "shift", "f10", "home" etc. that
don't
correspond to any characters obviously don't have any corresponding
"UXXXX"
keysyms. (Though for return, backspace, delete, tab, esc you may have
a point.)
> > That's really key AE00 and often generates some other character than
> > TILDE, e.g.:
> >
> AE00 means first raw, first key? That's not bad.
Row E, key 00 in that row. The numbering is slightly odd, key 80 (e.g.)
is to the left of key 00). Row A is where you have the space bar.
...
> > No, not at all. While some of the key names used in XKB layout files
> > are ill-chosen, many of them "come from" ISO 9995; and that's good.
> >
> Didn't know about this standard. Is it availible online?
As most ISO standards (with a too small number of exceptions), no.
Or, yes, as PDFs, but they are not free of charge (which I guess is what
you meant).
/kent k
--
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/linux-utf8/
