Follow-up Comment #5, bug #67911 (group groff): [comment #2 comment #2:] > I am not too sure what to do about this! I did point out to Branden that the > pdfmark.pdf documents a lot of what gropdf can do, so I wrote a short > document intended as a replacement (file #57766), but it relies on ms > features which will not be included in 1.24 (see bug #67665). Suggestions > about what is the best thing to do are most welcome. I could change gropdf.1 > to reference pdfmark.pdf on Keith's git or host the new pdf on my chuzzlewit > server and add that link to the man page. > > Written before comment #1.
My plan for bug #66453 was simply to read through your short document (file
#57766) and sift out material appropriate to the _gropdf_(1) man page where
not already present, which would not be wasted effort since it needs to
document those features anyway, for as long the output driver supports them
(likely indefinitely).
Reviewing that file while preparing _this_ comment, I see some buglets we'll
want to clear up (a footnote gets misnumbered, section numbers in the headings
get repeated, there's apparently a syntax glitch affecting the cover page, and
there's no legend for the meanings of the box colors).
But overall it looks like a pretty sweet set of additions to our _ms_ package
and I'd definitely like to see this stuff in a shipping release sooner than
later. Hold me to my July 2026 game plan for _groff_ 1.25!
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?67911>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
