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

[G. Branden Robinson]

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

[comment #14 comment #14:]
> 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 

I am uncertain of the wisdom of using GROFF_FONT_PATH, whose semantics are a
search path for groff device and font _description_ files, also as a search
path for Type 1 or other font files.

But I'm not in a hurry to burn it with my puritanical fire quite yet...see
below.

> it looks in site-font.
> Currently gropdf uses the last entry when a duplicate discovered.

Right, I recall this discussion from August now.

> A recent change to install-fonts.sh now copies entries from the system
download to the site download.

Hmmmm.

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

Yes, that is indeed the convention and historical practice.
 
> 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.

Oops.

> 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,

Can you proceed with this?

> 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.

I reckon it's not the worst thing in the world if people can use
GROFF_FONT_PATH as a crutch to tide them over while we sort out
grops/gropdf/install-font.sh font file resolution ordering.

I do point out that the _groff_ project does not have control of
install-font.sh--that's Peter Schaffter's baby, though I gather he'd prefer
someone else adopted it.
 
> 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.

Let's get gropdf fixed and see if I have sufficient wits about me to ape the
fix in grops.

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

John, can you follow up to Deri's query, please?

Deri, it sounds like bug #62950, which I filed, is yet another duplicate of
this.  Do you agree?


    _______________________________________________________

Reply to this item at:

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

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