> >>> This looks like it would conflict with Emacs usage.
> >>
> >> Where is the conflict? This is precisely the syntax for declaring
> >> an encoding to Emacs, and by now Emacs also recognizes standard
> >> encoding names like "GB2312" and "UTF-8".
> >
> > It's also the method to describe a minor mode to Emacs. For
> > example, all my documents start with:
> >
> > .\" This file is in -*- nroff-fill -*- mode
> >
> > More importantly though, you intend this to talk to groff, not to
> > Emacs.
The syntax needs the `coding:' tag; everything else is ignored. I
don't see a problem here.
> > groff defines the term 'request' specially: it refers to the
> > commands that start at the beginning of the line with . or '. I
> > was thinking more like:
> >
> > .Character-Encoding EUC-JP
> >
> > This would incidentally also allow changing the character set in
> > mid-stream, at least syntactically. I suspect there may be
> > reasons that make it impractical.
Exactly. Basically, the encoding of a file is a meta information and
should stayed fixed for the whole document.
Werner
--
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/linux-utf8/
