bug-groff
[Top][All Lists]
Advanced

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

[bug #62572] [gropdf] would like complaint if embedding need but downloa


From: G. Branden Robinson
Subject: [bug #62572] [gropdf] would like complaint if embedding need but download file useless
Date: Thu, 2 Jun 2022 22:45:10 -0400 (EDT)

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

                 Summary: [gropdf] would like complaint if embedding need but
download file useless
                 Project: GNU troff
               Submitter: gbranden
               Submitted: Fri 03 Jun 2022 02:45:08 AM UTC
                Category: Device gropdf
                Severity: 1 - Wish
              Item Group: Warning/Suspicious behaviour
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
         Planned Release: None


    _______________________________________________________

Follow-up Comments:


-------------------------------------------------------
Date: Fri 03 Jun 2022 02:45:08 AM UTC By: G. Branden Robinson <gbranden>
I made a bonehead move with commit 6e62be835d
<https://git.savannah.gnu.org/cgit/groff.git/commit/?id=6e62be835d08239dd1a08dde98ccff6e328e3bf3>
 back on 2 May that managed to break the "download" file for PDF output--it
was empty except for a comment.

Around the same time, I noticed that the Courier font in groff-generated PDF
files got replaced with an ugly Helvetica on the Evil non-free PDF viewer on
my tablet.

It turns out that was not a coincidence.  Now I know why--with the download
file practically empty, the fonts weren't getting embedded after all despite
the '-e' option.

I would like gropdf to warn about this.  If a font the document needs is not
found in the download file, it should warn, alerting the user to the
possibility of suboptimal output.

I've fixed the problem I caused; it is pending in my local checkout.







    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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