In article <address@hidden>, Richard Stallman <address@hidden> writes:
>> ;; xxx.el -- Do XXX. -*- coding: latin-1!; -*-
> Such a notation is not self-evident. What about
> ;; xxx.el -- Do XXX. -*- coding: latin-1; translation: no -*-
> It would be useful to support the latter as well,
> but I think we want something terse for this.
I've just installed these changes.
(1) Accept something like "latin-1!" as value of coding: in
header and local variables section.
(2) Accept "char-trans: VAL" in header and local variables section.
I think "translation: VAL" is too ambiguous.
(3) Accept "enable-character-translation: VAL" in local
variables section.
In which NEWS section, that information should go?
Previously we simply had "* Changes in Emacs XX.YY", but now
we have these sections:
* Installation Changes in Emacs 22.1
* Startup Changes in Emacs 22.1
* Incompatible Editing Changes in Emacs 22.1
* Editing Changes in Emacs 22.1
* New Modes and Packages in Emacs 22.1
* Changes in Specialized Modes and Packages in Emacs 22.1
* Changes in Emacs 22.1 on non-free operating systems
* Incompatible Lisp Changes in Emacs 22.1
* Lisp Changes in Emacs 22.1
* New Packages for Lisp Programming in Emacs 22.1
It seems that this change is "Editing Changes", but I'm not
sure we can declare it incompatible or not. Perviously, if
a file has "coding: latin-1!", it is treated as an invalid
coding specification. In that sense, this change is
incompatible, but...
---
Kenichi Handa
address@hidden