Re: non-ascii chars in the Lisp source files

[Katsumi Yamaoka <yamaoka@jpl.org>]

>>>>> In <v9wucpj4br.fsf@marauder.physik.uni-ulm.de>
>>>>>	Reiner Steib <4.uce.03.r.s@nurfuerspam.de> wrote:

>>> Doesn't XEmacs allow the cookie in the local variables section?

>> Unfortunately, it probably be so. :(

> This seems to be a bug (see also [1]) in XEmacs 21.4 then, as (info
> "(XEmacs)Recognize Coding") in XEmacs 21.4.12 mentions local
> variables:

> ,----[ (info "(XEmacs)Recognize Coding") ]
>|    You can specify the coding system for a particular file using the
>| `-*-...-*-' construct at the beginning of a file, or a local variables
>| list at the end (*note File Variables::).

[...]

> [1]
> <URL:http://news.gmane.org/onethread.php?group=gmane.emacs.xemacs.beta
&root=%3C20020506193719.30420.qmail%40ypy.tky.hut.fi%3E>

Thanks.  I've confirmed both the latest XEmacs 21.4 and 21.5
don't handle the coding cookie at the end of a file yet.  So,
all files needing the coding cookie should contain the
"-*-...-*-" form at the beginning.  Although it's easy to modify
deuglify.el, gnus-delay.el, ..., gnus.texi so that they contain
the cookie at the beginning, there's no room to have it within
80-column.  In addition, we cannot do so in the ChangeLog files.
It's a distress.  I was increasingly disillusioned with XEmacs.
-- 
Katsumi Yamaoka <yamaoka@jpl.org>