It's going to be about a week before I can review it, but I'll apply
it in my working copies (Mac OS X/PPC and Linux).
So this isn't an objection per se, rather a request for an additional
ping if you change your mind and decide there's reason to commit
>>>> "Aidan" == Aidan Kehoe
Aidan> Stephen, this adds support for the ISO-IR 196 UTF-8 escape
Aidan> syntax in ISO 2022-oriented coding systems, as Sun used a
Aidan> few years ago for transferring Unicode in X11 selections,
Aidan> and as you and Markus Kuhn objected to back then.
It wasn't just Sun, it was XFree86. And XFree86 particularly pissed
me off because they had just revised their version of the standard, so
they were well-aware that the syntax they added was explicitly
prohibited by the standard.
Note that I have zero objection to XEmacs using it where we have no
alternative that preserves content and as long as it's properly
Aidan> Given the issues my C code has provoked recently, I’d love
Aidan> testing from other people before committing.
Hey, I resemble that remark! I saw your bug and then suggested a
patch that didn't fix it at all! :-)
Aidan> NB; with this patch committed, XEmacs supports the whole
Aidan> basic multilingual plane of Unicode, and doesn’t trash any
Aidan> characters in this space.
If you're looking for suggestions :-), any hack to directly use
Unicode in Xft frames would be desirable, I think.
Have you made any progress on Unicode Inside?
School of Systems and Information Engineering http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Ask not how you can "do" free software business;
ask what your business can "do for" free software.