>> Both files `groff.man' as `groff.1n' and `groff.7n' as source and as
>> `groff.1' and `groff.7' after compiling.
> 
> The "compiling" is the substitution of `@g@', for example?  Why not
> groff.1.in, echoing Makefile.in and friends that also under go
> simple substitution, producing groff.1?

... and I like this even more, since it is natural within the
autotools infrastructure :-) Anyways, an issue in the tracker would be
good.


    Werner

Reply via email to