Follow-up Comment #13, bug #63018 (group groff):
[comment #12 comment #12:]
> [comment #11 comment #11:]
> > It might help if we said so in the comment. We could
> > furthermore include in that comment the presence/values of
> > command-line options that affect the generated contents.
>
> If you're talking about modifying afmtodit to include that information in
its output, that seems like a good idea but well outside this ticket's scope.
Sure, just noting it so I don't forget. It can become a separate ticket, as
can comment #7. In fact I see two issues springing thence. So, to
summarize.
1. Make comment headers of font description files we generate with tools more
informative. Could affect _afmtodit_, _hpftodit_, _tfmtodit_, _addftinfo_,
and _xtotroff_.
2. Add "maintainer-font-descriptions" _make_(1) targets for _afmtodit_ and
maybe _hpdftodit_ and _tfmtodit_. (This might depend on what source material
we already have in the tree. If such material is missing (or so stale we
should toss it out), we might need to document further maintainer-mode build
dependencies in "INSTALL.REPO".)
3. Update the procedure documented in "FOR-RELEASE" to include the effects of
item 2 above.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?63018>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
