Re: [PATCH] Unicode Lisp reader escapes

[Eli Zaretskii]

> From: Kenichi Handa <address@hidden>
> CC: address@hidden, address@hidden
> Date: Wed, 03 May 2006 11:59:52 +0900
> 
> > 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.

Sorry, I meant utf-fragment-on-decoding, which decodes Cyrillic and
Greek into ISO 8859.  (I always get confused and lost in the maze of
those twisted *-on-decoding passages, all alike.)

> > 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.

Right, but what about Cyrillic and Greek?  The merits and demerits of
depending on utf-fragment-on-decoding are not clear when the Lisp
reader is involved.