Hi Ted,
> One approach might be to have a Preamble (or perhaps an auxiliary
> macro package) in the groff source document which tests \*[.T] and
> then defines various things appropriately, e.g.
>
> .char \[lq] "
>
> etc. if \*[T] is "ascii".
There's no need to do this particular .char because -Tascii uses " for
\(lq and \(rq.
$ echo '\(lq,\(rq,\(ga,\(aa,",'\'',`' | groff -Tascii | cat -s
",",`,',",',`
$ echo '\(lq,\(rq,\(ga,\(aa,",'\'',`' | groff -Tascii | cat -s | hexdump -C
00000000 22 2c 22 2c 60 2c 27 2c 22 2c 27 2c 60 0a
$ echo '\(lq,\(rq,\(ga,\(aa,",'\'',`' | groff -Tutf8 | cat -sA
[EMAIL PROTECTED],[EMAIL PROTECTED],`,M-BM-4,",[EMAIL PROTECTED],[EMAIL
PROTECTED]
$
With -Tascii they all get mapped onto ["'`]. It's the common
introduction of UTF-8 terminals now which gives problems with -Tutf8;
all map onto non-ASCII characters except \(ga -> ` and " -> ".
Cheers,
Ralph.
