Re: [PATCH] Unicode Lisp reader escapes

[Kenichi Handa]

In article <address@hidden>, Richard Stallman <address@hidden> writes:

>       (set-language-environment "Latin-1")
>       (byte-compile-file "~/test1.el")
>       (set-language-environment "Japanese")
>       (byte-compile-file "~/test2.el"))

>     Although the source files are exactly the same, the
>     resulting test1.elc contains a string of two Latin-1
>     characters whereas the test2.elc contains a string of single
>     Japanese character.

> Is the difference due solely to the choice of coding system for
> decoding the file?

Yes, in the above example.

> That heuristic choice of coding system depends on
> lots of things, but Lisp files can prevent variation by specifying
> -*-coding-system:...;-*-.

> When the file does that, does eliminate the problem?

Yes, in the above example.

> Anyway, is the specific problem I asked you to look at a matter of
> choice of coding system?  (I don't know the details, since I don't
> know what that variable does--I just know it relates to Mule.)

"A matter of choice of coding system" is just one of the
problems.  Even if a coding system is deterministically
chosen, there are several options that controls the decoding
of utf-*.  And, binding all of them to the default values
while byte-compiling leads to another problem as I wrote in
the previsou mail.

---
Kenichi Handa
address@hidden