Re: [PATCH] Unicode Lisp reader escapes

[Kenichi Handa <handa@m17n.org>]

In article <E1FgCyb-0001Uq-Pk@fencepost.gnu.org>, Richard Stallman <rms@gnu.org> writes:

>     I agree, in principle. IIRC, I was the first one here to suggest to
>     just document the issue and be done with it. But documenting it would
>     be a good idea. Something along the lines: "When using non-ASCII
>     characters in Emacs Lisp source files, beware that compilation
>     "freezes" some of your current settings for character unification
>     and/or fragmentation.

> I want to fix this bug, not document it.

I'm confused.  You wrote:

> Handa says that telling people "don't use utf-8" solves the problem.
> If that is a good solution, I think the problem is solved.
> Does everyone agree that that solution works?

So, I thought you accepted such kind of solution;
i.e. documenting the potential problem about decoding and
the way to avoid the ambiguity if one has a problematic *.el
file.  There are two ways to avoid it.

(1) use emacs-mule coding system
(2) use one of iso-2022 based coding systems (they include
iso-8859-X) with setting enable-character-translation to nil
in "Local Variables:" section.

(1) works now.  (2) doens't work now but easy to make it
work as I wrote in the previous mail.

Do you want something more?

---
Kenichi Handa
handa@m17n.org