Werner LEMBERG writes:
> The planned groff 2.0 will use the same syntax as Emacs to define the
> input character set, i.e. the first line contains
>
> -*- coding: foo -*-
>
> in a comment. This info will then be forwarded to a preprocessor
> which converts the man page to UTF-8.
Will "foo" be a standard IANA encoding name, or will it be an Emacs
name?
Already now, the Emacs names are nonstandard:
- For US-ASCII, Emacs wants "undecided".
- For GB2312, Emacs wants "euc-cn".
- For TIS-620, Eamcs wants "th-tis620".
It is foreseeable that this list will grow in the future.
Furthermore Emacs doesn't support many encodings, like ISO-8859-6,
ISO-8859-13, ISO-8859-15, KOI8-U, EUC-TW, BIG5HKSCS, GBK, GB18030.
Will these encodings be allowed for manpages?
> \# -*- coding: utf8 -*-
>
> as the first line.
The Emacs21 and Emacs20+MuleUCS name is "utf-8", not "utf8".
Bruno
-
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/lists/
