bug-groff
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #62676] better document PDF generation


From: Dave
Subject: [bug #62676] better document PDF generation
Date: Mon, 27 Jun 2022 01:53:09 -0400 (EDT)

URL:
  <https://savannah.gnu.org/bugs/?62676>

                 Summary: better document PDF generation
                 Project: GNU troff
               Submitter: barx
               Submitted: Mon 27 Jun 2022 12:53:08 AM CDT
                Category: Device gropdf
                Severity: 1 - Wish
              Item Group: Documentation
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
         Planned Release: None


    _______________________________________________________

Follow-up Comments:


-------------------------------------------------------
Date: Mon 27 Jun 2022 12:53:08 AM CDT By: Dave <barx>
See this thread for discussion of some of the shortcomings of gropdf
documentation: http://lists.gnu.org/r/groff/2022-01/msg00052.html

Select points from this thread:

"Pdfmark.pdf... is the best resource we have for producing pdfs with groff,
and details the macros and how to use them."  However, the gropdf man page
mentions pdfmark.pdf "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... 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'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)."

(Related: bug #60927 covers pdfmark documentation and the pdfroff man page.)







    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?62676>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]