Stephen J. Turnbull wrote:
>>>>>"Ben" == Ben Wing <ben(a)666.com>
writes:
>>>>>
>>>>>
Ben> well, basically i want some api that says "convert a charset
Ben> and codepoints into a Lisp char" and vice-versa "get a
Ben> charset and codepoints from a Lisp char". keep in mind that
Ben> we will be running both unicode-internal and old-mule for
Ben> awhile,
FWIW, IMO nobody's going to be running with unicode-internal if
neither font-handling nor language support is in, except for the sake
of testing unicode-internal. So, we only need to support legacy Mule
stuff for applications testers are using, on request from the testers.
well, it won't mangle arbitrary unicode characters, like currently.
also, there's already hackish font handling for arbitrary unicode chars
under windows, so this will display them correctly [more or less].
I cannot think of a single use case (excluding legacy Mule
compatibility) for the charset-oriented functions.
well, the functions are already in my workspace, and i'm not gonna
delete them. someone will surely find them useful.
also, charsets are used explicitly in the `mbcs' coding system, which
allows you to combine multiple charsets into a simple mbcs encoding.
Start with the core code. There is no use of `split-char' and
exactly
one use of `make-char' in 21.5/lisp. There are a few of each in
21.5/lisp/mule. The majority of uses are those in about.el,
european.el, greek.el, and hebrew.el. Those reflect what is just a
long-standing bug: the lack of a proper facility for reading non-ASCII
characters in LISP code, which will obviously be fixed by
standardizing on Unicode (presumably UTF-8) for source code in XEmacs.
I also added \uXXXX and \UXXXXXXXX escape codes for Unicode, as per
various other languages.
21.5/lisp/mule/cyrillic.el: (split (split-char ch)))
21.5/lisp/mule/cyrillic.el: (split (split-char ch)))
BTW these have already disappeared.
What am I missing?
we shall see; the check is still in the mail.
ben