Re: [PATCH] Unicode Lisp reader escapes

[Oliver Scholz]

Richard Stallman <address@hidden> writes:

>     I guess, you have a similar problem when the source file is encoded in
>     either ISO 8859-5 or ISO 8859-7 (btw., what about Hewbrew, Arabic and
>     Thai?). Unless I am much mistaken, the encoding of the characters in
>     the .elc file would also depend on the value of
>     `utf-fragment-on-decoding'.

[Note the correction in a follow-up of mine: I made a mistake in
phrasing that paragraph. I am actually talking about Elisp source
files encoded in UTF-8 (or another UCS encoding) that contain
characters from the repertoire of ISO 8859-5 or ISO 8859-7.

There's a similar case with source files encoded in some of the ISO
8859 encodings and `unify-8859-on-decoding-mode', though.]

> Are you talking about how the compiler would write the .elc file?
> Or are you talking about how the .elc file would be interpreted?

It's the former. Meanwhile I have tested it. After some more thought I
think that the case of an UTF-8 encoded source files containing
characters from the Greek or Cyrillic repertoires is in fact entirely
analogous to what would happen with \u.

In other words: that particular bug is already there.


    Oliver, who still thinks that \u and \U is really ugly.
-- 
17 Floréal an 214 de la Révolution
Liberté, Egalité, Fraternité!