Re: [PATCH] Unicode Lisp reader escapes

[Kenichi Handa]

In article <address@hidden>, Eli Zaretskii <address@hidden> writes:

>> From: Kenichi Handa <address@hidden>
>> Date: Tue, 02 May 2006 15:43:16 +0900
>> Cc: address@hidden
>> 
>> > +  lisp_char = call2(intern("decode-char"), intern("ucs"),
>> > +                    make_number(i));
>> > +
>> 
>> First of all, is it safe to call Lisp program in
>> read_escape?

> Whether it is safe or not, I think it's certainly better to implement
> the guts of decode-char in C, if it's gonna be called from
> read_escape.  All those guts do is simple arithmetics, which will be
> much faster in C.

I agree.

> Moreover, I think the fact that decode-char uses translation tables to
> support unify-8859-on-*coding-mode (and thus might produce characters
> other than mule-unicode-*) could even be a misfeature:

Decode-char doesn't support unify-8859-on-*coding-mode but
supports utf-fragment-on-decoding and
utf-translate-cjk-mode.

> do we really want read_escape to produce Unicode or
> non-Unicode characters when it sees \uNNNN, depending on
> the current user settings?

I think, at least, CJK characters should be decoded into one
of CJK charsets because there's no other charsets.

---
Kenichi Handa
address@hidden