>>>> "Nickolay" == Nickolay Pakoulin
<npak(a)ispras.ru> writes:
Nickolay> XEmacs maps codepoints that correspond to the mentioned
Nickolay> chars into chinese and japanese charsets. I don't have
Nickolay> ISO-2022 on my hands, but I am pretty sure that the
Nickolay> standard positions those chars in Far East charsets.
Ugly, ain't it?
This has always been true. Nobody in a position to help with testing
has ever pushed it before (I think the usual practice is to simply use
an 8-bit XEmacs with a KOI8-R font, which gives pleasant results with
no fuss).
First, check to see if GNU Emacs has this right. We should be able to
synch to their implementation for 21.4.
If not, I think the right way to deal with it in 21.4 is your #2,
assuming you have KOI8-R fonts. (Caveat, as I said before I don't
know how to do this on Windows.)
Create a private 96 charset for each non-ISO encoding that uses C1 to
represent graphic characters. Eg, KOI8-R, create symbol-koi8-r (as
you did in the recent post). The registry should be "koi8-r" (if
there are variants, regexpify that to handle them all). Change the
registry for the cyrillic-iso8859-5 charset to "koi8-r". Change the
current KOI8-R CCL codecs to simply map graphic C1 characters to
symbol-koi8-r code point + 32 - 128, and back. Use these codecs both
for fileio and redisplay.
That's the theory, I don't know if there's anybody left who has done
this in practice.
For 21.5, you'll have to ask Ben.
Nickolay> 3. Wait until full Unicodizing internals and hope the
Nickolay> problem will disappear.
Nope. This will require work, and help from you (or some Cyrillic
users, anyway) for testing and sanity checking on X (where we can't
yet count on Unicode fonts) and maybe on Windows (I suspect we
probably need a KOI8 detector).
Nickolay> Current implementation of Unicode support maps box
Nickolay> drawing and friends to Far East charsets.
This can and should be fixed in 21.5 by changing charset precedence.
I don't know if 21.5's mechanism is flexible enough to do it right
yet; again, Ben's the guy to ask.
In 21.4, Unicode is not supported. Yes, we do some autodetection, and
we provide the Mule-UCS package. But it's orphaned by upstream, and
nobody understands it. In principle you should be able to change
Mule-UCS mappings to use KOI8-R or whatever.
--
Institute of Policy and Planning Sciences
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.