Re: Font path issue

2022-08-22 Thread Deri
On Sunday, 21 August 2022 17:26:55 BST G. Branden Robinson wrote: > Hi Deri, > > At 2022-08-21T01:12:07+0100, Deri wrote: > > Gropdf is different, it takes into account all download files found, > > so there is no need to duplicate entries into the site-font download > > file. You could organise y

Re: Font path issue

2022-08-21 Thread Peter Schaffter
Deri -- Talk about diving down a rabbit hole and taking a wrong turn at Albuquerque! > If you look at gropdf around line 55, you should see something > like:- > $cfg{GROFF_VERSION}='1.22.4'; > $cfg{GROFF_FONT_PATH}='/usr/share/groff/site-font:/usr/share/groff/1.22.4/ > font:/usr/lib/font'; I lo

Re: Font path issue

2022-08-21 Thread G. Branden Robinson
Hi Ralph, At 2022-08-21T17:43:03+0100, Ralph Corderoy wrote: > How about making %download be a hash of lists and appending to the end > of the relevant list without checking anything. Then run along the > relevant list when the file is actually needed to find the first, if > any, which opens. If

Re: Font path issue

2022-08-21 Thread Ralph Corderoy
Hi Branden, > $download{"$foundry $name"}=$file; ... > I think it _might_ be better to (a) perform that check (with the `-r` > operator, I reckon), only adding $file to the hash if that succeeds > and (b) skipping the validity check and hash update if the key > ("$foundry $name") is al

Re: Font path issue

2022-08-21 Thread G. Branden Robinson
Hi Deri, At 2022-08-21T01:12:07+0100, Deri wrote: > Gropdf is different, it takes into account all download files found, > so there is no need to duplicate entries into the site-font download > file. You could organise your fonts into separate families, each with > its own separate download file j

Re: Font path issue

2022-08-21 Thread Deri
On Sunday, 21 August 2022 15:17:01 BST Robert Goulding wrote: > If Deri says it looks for *all* the download files, then that must be > correct! But is the manpage out of date then? > > Robert. Hi Robert, I have corrected it on git. Cheers Deri commit 5b357550d90f59f4d37ae9f2ce3a562d97b78a01

Re: Font path issue

2022-08-21 Thread Robert Goulding
> > > All works fine here. I believe what hit Robert is that grops stops looking > when it finds the first download file (which would be the one in site-font > if > it exists) which means that if there are any entries in the system > download > they would not be found. This is why copying those en

Re: Font path issue

2022-08-20 Thread Deri
On Saturday, 20 August 2022 01:05:02 BST Peter Schaffter wrote: > In this post, "system" means groff/current/font/ and "local" means > /groff/site-font. Hi Peter, "current" should be a symlink to a numbered version in the groff directory. Where does it point on your system? > After implementing