> Here's what I've worked up. [...]
>
> Comments? Unless someone convinces me that I've gone round the
> bend, something like this will probably be in my next push.
Looks good, thanks.
Werner
On Friday, 7 October 2022 10:35:55 BST G. Branden Robinson wrote:
> One thing I don't understand is why "(gs)" (which, IIRC, means,
> "whatever Ghostscript's font search path reported in 'gs -h' is) comes
> right after the URW fonts directory when searching for Adobe or generic
> fonts but all the
Hi Deri,
At 2022-10-07T13:23:06+0100, Deri wrote:
> On Friday, 7 October 2022 10:35:55 BST G. Branden Robinson wrote:
> > One thing I don't understand is why "(gs)" (which, IIRC, means,
> > "whatever Ghostscript's font search path reported in 'gs -h' is)
> > comes right after the URW fonts directo
At 2022-10-07T03:25:05-0500, G. Branden Robinson wrote:
> I don't have enough information to solve this, but I do have two ideas
> that I think may help flush it out.
>
> 1. Add the purportedly successful URW font location path to the
> configuration report.
> 2. Have gropdf report more cont
At 2022-10-07T07:14:35+, Werner LEMBERG wrote:
>
> >> This inconsistency of gs on my GNU/Linux is of no importance, but
> >> it clearly shows that there is a bug while compiling groff: It uses
> >> `gropdf` from my system instead of using the just compiled
> >> `gropdf`!
> >
> > Are you sure?
