On Sun, 20 Jan 2002 14:55:17 +0000 Markus Kuhn <[EMAIL PROTECTED]> wrote: > > What you could do is either prefix each release with some release > indicator symbol, or add for instance 0x200000 to a Unicode character to > turn it into a release code. Both approaches allow you to use a normal > UTF-8 decoder at the receiver's end.
Sounds like a good idea but unfortunately Xutf8LookupString, XmbLookupString, and XwcLookupString are not supposed to be used with XKeyReleasedEvents. Apparently it messes up the input context. I've resorted to simple XLookupString and writing post-modifier KeySyms as 4 byte integers. Works for now but I'd like to also provide transparent support for the Linux console and Putty. If I'm going to normalize on something I should at least use unicode to avoid table lookups in the end user code. Ideas would be appreciated. > > There is no standard for what you want to do, as this is getting very > far away from the classic VT100 / ISO 6429 terminal semantics. No matter > what you do, it will be your private encoding that isn't compatible with > anything else. > > Make sure that the ESC sequence that you use to activate this private > mark/break mode is as long and obscure as possible (at least 10 bytes, > but still within the ECMA-48 syntax for ESC sequences!), to minimize > that it can ever be sent by accident to the terminal. With a hint from of Mr. Dickey, I believe the private \E[?1515h and \E[?1515l sequences are appropriate. > > http://www.ecma.ch/ecma1/STAND/ECMA-048.HTM This looks important :~) Thanks, Mike -- May The Source be with you. -- Linux-UTF8: i18n of Linux on all levels Archive: http://mail.nl.linux.org/linux-utf8/
