On Wednesday, 6 July 2005 at 13:27:42 +0200, Bruno Haible wrote: > Greg Lehey wrote: >>> b) Recognize the encoding according to a note in the first line >>> '\" -*- coding: EUC-JP -*- >>> groff will then emit errors when it is fed input that is non-ASCII >>> and without coding: marker, so that man page maintainers are notified >>> that they need to add the coding: marker. >> >> 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. >> wouldn't it be more appropriate to make it into a groff request? > > Yes, I'm talking about planned changes to groff. 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. Greg -- The virus contained in this message was detected by LEMIS anti-virus. For further details see http://www.lemis.com/grog/lemis-virus.html Finger [EMAIL PROTECTED] for PGP public key. See complete headers for address and phone numbers.
pgpBoqOAtyerk.pgp
Description: PGP signature
