On 1/28/22, Deri <d...@chuzzlewit.myzen.co.uk> wrote:
> If you are using -T pdf you
> don't need to include -mpdfmark, this is documented in the gropdf man page
> and the pdfmark.pdf is referenced.
True, but just barely. It's mentioned in one entry in the list of \X
escapes. This is down in a level of detail that a lot of gropdf users
won't necessarily need, whereas at least the .pdfinfo macro under
discussion is a document-level control knob. But users won't know it
exists unless they read every entry of the \X list *and* follow the
pointer to pdfmark.pdf.
And even for those users who do find it, the list item in question is
less helpful than it could be:
* It directs users to pdfmark.pdf but gives no hint where to find this file.
* It's vague about which pdfmark facilities are available by default
in -Tpdf ("a subset" covering "most functionality," with no
elaboration about what's included or excluded).
I feel like the tie between gropdf and pdfmark should be mentioned
near the top of the Usage section. If the man page doesn't list all
the macros available, it should at least mention two or three
important ones and what they do, so users have some idea of the
functionality available to know they should move along to a separate
PDF file (which is often a couple more steps than just looking at
another man page, so it's worth giving some incentive).
That part could arguably come under the umbrella of
http://savannah.gnu.org/bugs/?61958.
