[EMAIL PROTECTED] wrote on 2000-08-07 19:04 UTC:
> > I would hope that all that has to be done in "man" is to test for whether
> > we are in a UTF-8 locale as described on
> > http://www.cl.cam.ac.uk/~mgk25/unicode.html#activate
> > and then pass the -Tutf8 option on to groff and friends accordingly.
>
> Hmm. The present setup uses a config file, say /etc/man.conf
> or /usr/share/man.config or so. It has pathnames and options
> for the programs to call. E.g.
>
> TROFF /usr/local/bin/groff -Tps -mandoc
> NROFF /usr/local/bin/groff -Tlatin1 -mandoc
> EQN /usr/bin/geqn -Tps
> NEQN /usr/bin/geqn -Tlatin1
> TBL /usr/bin/gtbl
> # COL /usr/bin/col
> REFER /usr/local/bin/refer
> PIC /usr/bin/gpic
> VGRIND
> GRAP
> PAGER /usr/bin/less -is
> CAT
>
> So, it is not entirely obvious what to do.
One quite neat solution would be to write in the config file something
like
NROFF /usr/local/bin/groff -T${charset} -mandoc
and make ${charset} a locale-dependent best-guess for what should come
after -T. If you write %s instead of ${charset}, it's probably slightly
easier to implement.
Another option would be to change groff such that we can write
NROFF /usr/local/bin/groff -Tlocale -mandoc
and then groff would have to do the check for UTF-8 locale (as described
on the above URL) and output in the appropriate encoding, or even better
NROFF /usr/local/bin/groff -Twlocale -mandoc
would cause groff to output everything using glibc 2.2's wide character
functions. The latter solution would automatically support not only
UTF-8 but any multibyte encoding and transliteration, but might involve
a bit more implementation work.
Markus
--
Markus G. Kuhn, Computer Laboratory, University of Cambridge, UK
Email: mkuhn at acm.org, WWW: <http://www.cl.cam.ac.uk/~mgk25/>
-
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/lists/
