[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [Groff] Re: groff: radical re-implementation

> > Note that such an encoding request has to determine the encoding *and*
> > character set of a document (similar to Emacs).
> (snip)
> > Examples:
> >   .\" -*- charset: JIS-X-0208; encoding: EUC -*-
> >   .\" -*- charset: JIS-X-0208; encoding: ISO-2022 -*-
> No.  only specifying 'encoding' is sufficient.  This is because
> 'encoding' includes information on which charset to be used.

This is not true.  Encoding does *not* imply the character set.
You are talking about charset/encoding tags.

> Thus, when I specify encoding is ISO-2022-JP, it automatically says
> that charsets are US-ASCII, JIS X 0201 (LeftHalf), JIS X 0208-1978,
> and JIS X 0208-1983.  When I specify encoding is EUC-KR, it
> automatically says that charsets are US-ASCII and KS X 1001.

Again, EUC-KR and friends are charset/encoding tags.  ISO 2022 is not
limited to this, as you certainly know (and as Emacs proves).  You
can, for example, have a character set in the GL or in the GR area.
You can have 7bit ISO 2022 and 8bit ISO 2022, etc.


Reply to: