Re: 'man groff' reports end of file while defining macro `TP'

[Paul Eggert]

> Date: Thu, 19 Jun 2003 13:22:45 +0200 (CEST)
> From: Werner LEMBERG <address@hidden>
> 
> > I just tried 'make install tmac_wrap=""' and it didn't fix the
> > problem:
> 
> Have you uninstalled groff before?  There is a high chance that there
> is a conflict due to the priority of the search path for groff macro
> files.

I have installed groff before, but I doubt whether that's the issue here.
I trussed "man groff" and found that it read the following tmac files,
in the following order:

/opt/reb/share/groff/1.19/tmac/troffrc
/opt/reb/share/groff/1.19/tmac/tty.tmac
/opt/reb/share/groff/1.19/tmac/hyphen.us
/opt/reb/share/groff/1.19/tmac/hyphenex.us
/opt/reb/share/groff/1.19/tmac/composite.tmac
/opt/reb/share/groff/1.19/tmac/papersize.tmac
/opt/reb/share/groff/1.19/tmac/tty-char.tmac
/opt/reb/share/groff/1.19/tmac/latin1.tmac
/opt/reb/lib/groff/site-tmac/an.tmac
/opt/reb/share/groff/1.19/tmac/andoc.tmac
/usr/share/lib/tmac/an
/opt/reb/share/groff/1.19/tmac/troffrc-end

These all are from groff 1.19, except for /usr/share/lib/tmac/an which
is from Solaris 9.  "man gtroff" (which works), has the same include
pattern as "man groff" (which doesn't work).

I suspect that the problem is that groff.1 uses long definitions
like ".de TP+" but these are being interpreted in compatibility mode
so they screw up.  Does this sound plausible to you?

A similar problem occurs with groffer.1.  "man groffer" outputs this:

Reformatting page.  Please Wait.../opt/reb/share/man/man1/groffer.1:82: 
warning: numeric expression expected (got a space)
/opt/reb/share/man/man1/groffer.1:85: warning: numeric expression expected (got 
`o')
/opt/reb/share/man/man1/groffer.1:96: warning: numeric expression expected (got 
`o')
/opt/reb/share/man/man1/groffer.1:100: warning: numeric expression expected 
(got `o')
/opt/reb/share/man/man1/groffer.1:147: error: end of file while defining macro 
`Er'
 done

groffer.1 has problematic definitions like ".de Error" that will be
misinterpreted in compatibility mode.




> > fixmacros.sed makes a few changes, but they're all wrong.  For
> > example, it replaces "\fBsolaris\&.role\&.assign\fR" with
> > "\fBsolaris\&.role\&.assi gn\fR".
> 
> Please send me a list of the wrong decisions so that I can correct
> fixmacros.sed.

Perhaps this was a false alarm.  I applied fixmacros to the man pages,
not to the macros.  It mishandles some man pages but it wasn't
designed for them so it's not a big deal.