bug-groff
[Top][All Lists]
Advanced

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

[bug #55300] URW fonts issues in Groff 1.22.4


From: Eli Zaretskii
Subject: [bug #55300] URW fonts issues in Groff 1.22.4
Date: Thu, 27 Dec 2018 12:21:28 -0500 (EST)
User-agent: Mozilla/5.0 (Windows NT 5.1; rv:52.0) Gecko/20100101 Firefox/52.0

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

                 Summary: URW fonts issues in Groff 1.22.4
                 Project: GNU troff
            Submitted by: eliz
            Submitted on: Thu 27 Dec 2018 07:21:26 PM IST
                Category: Core
                Severity: 3 - Normal
              Item Group: Build/Installation
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
         Planned Release: None

    _______________________________________________________

Details:

If one doesn't have URW fonts installed, the Groff configure script emits the
following message:

     configure:
       No URW fonts in .pfb format were found on your system, URW fonts
       generation for 'devpdf' will not work properly.  These fonts can be
       downloaded here:

        http://downloads.ghostscript.com/public/fonts/urw-base35-v1.10.zip

       By default groff will search these fonts in the paths given by `gs
       -h' and in these 2 default directories:
       '/usr/share/fonts/type1/gsfonts/' and
       '/opt/local/share/fonts/urw-fonts/' (paths used by
       font/devpdf/Foundry.in).  You can also pass the option
       '--with-urw-fonts-dir=DIR' to 'configure' to set a custom path.  You
       would need to re-run the 'configure' script after installing these
       fonts.

First, the URL is outdated: it yields 404.

More importantly, the configure script insists on using GhostScript, even if
one finds and installs the fonts, and then invokes the configure script with
'--with-urw-fonts-dir=DIR'.  If GhostScript is indeed required, it should be
mentioned in the above text.





    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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