Re: [PATCH] Unicode Lisp reader escapes

[Kenichi Handa]

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

>     As I've just installed a fix, it doesn't fail now .  So, the
>     remaining problem is whether or not we should allow the
>     short name "char-trans" for it.  I tend to agree with Juri
>     that we don't need it because we can use "CODING!" notation.

>     If you agree with deleting it too, I'll install a proper
>     change soon.

> Ok.

I've just installed a change for not handling the short-name
"char-trans".

address@hidden (Kim F. Storm) writes:

> The change is not incompatible in the sense that it breaks
> existing _valid_ coding specs.

> The section

> ** Multilingual Environment (Mule) changes:

> seems appropriate??

Ok, I've just added this in that section.

*** You can disable character translation for a file using the -*-
construct.  Include `enable-character-translation: nil' inside the
-*-...-*- to disable any character translation that may happen by
various global and per-coding-system translation tables.  You can also
specify it in a local variable list at the end of the file.  For
shortcut, instead of using this long variable name, you can append the
character "!" at the end of coding-system name specified in -*-
construct or in a local variable list.

---
Kenichi Handa
address@hidden