Hi,
At Wed, 11 Apr 2001 22:45:43 +0200 (CEST),
Werner LEMBERG <[EMAIL PROTECTED]> wrote:
>> 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.
Seconded. Not only GNU Emacs but also XEmacs.
Please note Emacs name may have a postfix to specify line-breaking
code ("-unix" for LF, "-dos" for CRLF, and "-mac" for CR). Thus,
Emacs name will be IANA-NAME + LINE-BREAKING SPECIFIER). One more
note is that Emacs supports many encodings which don't have exact
IANA names - for example, "compound-text", "iso-2022-7bit", and
"iso-2022-8bit". Some encoding names are not familiar to me - for
example, "lao", "utf-8-ws", and "chinese-iso-8bit-with-esc".
> 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.
Good idea! I will implement this.
---
Tomohiro KUBOTA <[EMAIL PROTECTED]>
http://surfchem0.riken.go.jp/~kubota/
"Introduction to I18N"
http://www.debian.org/doc/manuals/intro-i18n/
-
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/lists/
