> > > > -*- coding: foo -*-
> >
> > > Will "foo" be a standard IANA encoding name, or will it be an
> > > Emacs name?
> >
> > Both, as far as possible. My implementation has Emacs name ->
> > IANA name conversion table. It will also need IANA name ->
> > iconv() name conversion table (sensible to platform).
>
> Good. But in those cases where Emacs doesn't know the IANA name,
> users will be forced to use the Emacs name, right? So they will end
> up using the Emacs name in some cases and the standard name in
> others.
I suggest you write something to emacs-bug so that the Emacs guys fix
this.
My idea was that the `coding:' line is already used by Emacs, and
there is no need to invent something new. Additionally, such files
can be easily edited by Emacs without setting the encoding manually.
Using
\# Content-Type: text/plain; charset=...
is an alternative, of course. Maybe the preprocessor should support
both notations.
Werner
-
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/lists/
