Re: install-font script (was: groff 1.23.0.rc2 readiness)

[Deri]

On Monday, 6 June 2022 19:08:23 BST Deri wrote:
> As I suggested it would be helpful if you are able to run gs -h on a windows
> box under cygwin and natively, the output would help us.

I have now managed to run gs -h under a VM of windows 10 with latest 
ghostscript, and you are 
correct that it needs to take account of path separator because the output 
looks like this:-

Search path:
   C:\Program Files\gs\gs9.56.1\bin ; C:\Program Files\gs\gs9.56.1\lib ;
   C:\Program Files\gs\gs9.56.1\fonts ; %rom%Resource/Init/ ; %rom%lib/ ;
   c:/gs/gs9.56.1/Resource/Init ; c:/gs/gs9.56.1/lib ;
   c:/gs/gs9.56.1/Resource/Font ; c:/gs/fonts
Initialization files are compiled into the executable.
For more information, see c:/gs/gs9.56.1/doc/Use.htm.

So I will change BuildFoundry so that paths are held in an array rather than a 
long string with a 
separator character. This means that when parsing gs -h for paths I can split 
on the given path 
separator (’;' for windows) and still use ':' for parsing Foundry.in whatever 
O/S it is running under.

I have also slightly refactored BuildFoundry to search path within file rather 
than the opposite. 
This is an attempt to source different versions of the URW fonts for the "U" 
foundry. This probably 
has no real affect, but previously I discovered that the URW fonts that came 
with ghostscript 
contained fewer glyphs than the versions which were available as a separate 
download. Currently 
they appear to have the same number of glyphs, but ghostscript claims a version 
1.00 against 
1.06 for the alternative.

Cheers 

Deri