[bug #62860] [gropdf] trying to access URW fonts from wrong directory

[G. Branden Robinson]

Update of bug #62860 (project groff):

                  Status:             In Progress => Need Info              

    _______________________________________________________

Follow-up Comment #7:

John, can you let me know if the following changes resolve your URW font
location problem?

I would count it as "resolved" if you need to pass a --with-urw-fonts-dir=
flag to the configure script to clue in the build...as long as _gropdf_ works
afterward.  It would require a lot of machinery for _groff_ to enumerate
multiple installations of URW fonts and select a "best" set itself.


commit 57cf998eae20fe7c886ec2fbda24248dcafa8209
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
Date:   Sun Oct 9 21:27:01 2022 -0500

    [m4]: Try to make URW font search deterministic.
    
    * m4/groff.m4: Try to make gropdf's search for URW font files more
      deterministic.  To disambiguate cases where multiple--not necessarily
      identical--copies may be found on the system, search _only_ in the
      directory given to the `--with-urw-fonts-dir` configure option, if
      present.  This populates the "Foundry" file generated by the build,
      causing gropdf to search there first.
    
      (GROFF_URW_FONTS_PATH): Stop `AC_SUBST`ing `urwfontsdir` here.
    
      (GROFF_URW_FONTS_CHECK): `AC_REQUIRE` `GROFF_URW_FONTS_CHECK` to be
      run first.  If `urwfontsdir` is not null, search only there for URW
      fonts.  Assign `urwfontsdir` the value of the directory in which the
      fonts are found.  Assign it an empty value if none are found.  Either
      way, `AC_SUBST` the variable.
    
    Attempts to fix <https://savannah.gnu.org/bugs/?62860> (1/2).

commit 0b93f550d8d686326cf6701953bb0f5f590beb1a
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
Date:   Sun Oct 9 21:29:09 2022 -0500

    configure.ac: Report where URW fonts were located.
    
    * configure.ac: If URW fonts were located, add the directory where they
      were found to the configuration report.
    
    Attempts to fix <https://savannah.gnu.org/bugs/?62860> (2/2).



    _______________________________________________________

Reply to this item at:

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

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