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

[Deri James]

Follow-up Comment #14, bug #62860 (project groff):

What we know:-

The filepaths in the built download file are correct.
So gropdf must be reading a different download.
The locations to search for the download file are hard-coded in line 59.
After the path in GROFF_FONTPATH it looks in site-font.
Currently gropdf uses the last entry when a duplicate discovered.
A recent change to install-fonts.sh now copies entries from the system
download to the site download. 

This is a mistake since the site font directory is intended for added fonts.

I did suggest changing gropdf behaviour to use the first found entry but this
simple change 
got caught up in discussions about what grops should do, so I did nothing.

So my diagnosis is that the download file in site-font contains the stale
fontpaths (which were correct 
at the time install-fonts.sh was run, but are now stale). This diagnosis can
be confirmed by looking 
in the site-font download file to see if it contains the stale entries.

Changing the behaviour of gropdf as described above would solve the build
issue, but once the built groff 
was installed in the system directory, and GROFF_FONTPATH is unset, the stale
entries in the site-font 
directory would be used first.

The change in install-fonts.sh was to paper over a deficiency in grops which
stops looking when it has 
found the first download file, but logically the system fonts should only
appear there if you are 
purposely over-riding a system font.

Please check your copy of download in the site-font directory to see if it
contains the stale paths.


    _______________________________________________________

Reply to this item at:

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

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