write specification for ISO10646-C properties, write sample implementations of the mapping routines, and add these to xterm, GTK, and other applications and libraries. Any volunteers?
• Keysyms: The keysyms defined at the moment cover only a tiny repertoire of Unicode. Markus Kuhn has suggested (and implemented in xterm) that any UCS character in the range U-00000000 to U-00FFFFFF can be represented by a keysym value in the range 0x01000000 to 0x01ffffff. This admittedly does not cover the entire 31-bit space of UCS, but it does cover all the characters up to U-0010FFFF, which can be represented by UTF-16, and more, and it is very unlikely that higher UCS codes will ever be assigned by ISO (in fact there are proposals to remove the code space above U-0010FFFF from ISO 10646 in the future). So to get Unicode character U+ABCD you can directly use keysym 0x0100abcd. See also the file keysym2ucs.c in the xterm source code for a suggested conversion table between the classical keysyms and UCS, something which should also go into the X11 standard. Markus also wrote a proposed draft revision of the X protocol standard Appendix A: KEYSYM Encoding (PDF) that adds a UCS cross
Related Questions
- write specification for ISO10646-C properties, write sample implementations of the mapping routines, and add these to xterm, GTK, and other applications and libraries. Any volunteers?
- I am a mechanical engineer and would like to specify FlexFlow Elbow on all of my future projects. Do you have a sample specification and detail drawings?
- What could be a sample mapping specification for modeling above?
