I was afraid that there was no better way. I have created an addition for the utf8 Compose files that allows <Multi_Key><u><hex><hex><hex><hex> for each of the BMP possibilities.
The next time I reboot I'll see how it works. (Including one comment line, octal escaping for 0x0..0x1f and \ escaping for \, it comes to 3504097 octets. A bzip2(1)ed copy (only 189085 octets) can be found at: http://cloos.sixbit.org/xfree86/UTF8-hex-entry-compose-additions.bz2 A better fix would be to either do what gtk+ 2.0 does at the client toolkit level or to modify the keyboard handling to create a keysym that is is equivalent of what <Multi_Key> <u> becomes with the above file added to ..../Compose. -JimC _______________________________________________ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
