[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Groff] make fails creating U-<fontname>

From: Deri James
Subject: Re: [Groff] make fails creating U-<fontname>
Date: Sat, 26 May 2012 12:25:43 +0100
User-agent: KMail/1.13.7 (Linux/; KDE/4.6.5; x86_64; ; )

On Saturday 26 May 2012 10:02:22 Denis M. Wilson wrote:
> On Fri, 25 May 2012 23:41:32 -0400
> Peter Schaffter <address@hidden> wrote:
> > Building groff from the latest sources, 'make' terminates with
> > Error 2 after multiple warnings of the sort
> > 
> >   Warning: line 78: Failed to create groff font 'U-AB' by running
> > 
> > afmtodit
> > 
> > I don't recall seeing this before.  What's
> > up?
> In the file groff-current/font/devpdf You need to replace line 68 or so
> with your own path to the URW font directory, eg I used:
> foundry|U|(gs):/usr/share/fonts/type1/gsfonts
> rerun configure, and you should be fine.  This should ideally be done
> by configure itself.
> Denis

The "(gs)" runs "gs -h", and then the search paths shown are searched for the 
fonts. On my system the command gives:-

Search path:
   /home/derij/.fonts : %rom%Resource/Init/ : %rom%lib/ :
   /usr/share/ghostscript/9.04/Resource/Init :
   /usr/share/ghostscript/9.04/lib :
   /usr/share/ghostscript/9.04/Resource/Font :
   /usr/share/ghostscript/fonts : /usr/share/fonts/default/ghostscript :
   /usr/share/fonts/default/type1 : /usr/share/ghostscript/fonts :
   /usr/share/ghostscript/9.04/Resource : /usr/share/ghostscript/Resource :
   /usr/share/ghostscript/CIDFont : /usr/share/fonts/ttf :
   /usr/share/fonts/type1 : /usr/share/fonts/default/Type1
Initialization files are compiled into the executable.

and if I look for one of the fonts I see:-

-rw-r--r-- 1 root  root  69965 Jan 17  2011 
lrwxrwxrwx 1 root  root     15 Jun  3  2011 
/usr/share/fonts/default/Type1/adobestd35/a010015l.pfb -> ../a010015l.pfb

So in my case the font would be found automatically (by the last path in 
Search Path).

The problem occurs if the search paths yielded by "gs -h" don't actually 
include the standard fonts! Which is why you can add custom paths as well. The 
question arises, "How does ghostscript find the fonts if they are not on its 
own search path?", and I think the clue is in the message "Initialization 
files are compiled into the executable" which I think means the fonts are 
compiled into the executable. If someone has a better way of trying to find 
the fonts please give me a clue. :-)

Peter, what does "gs -h" yield on your system and where are the fonts actually 



reply via email to

[Prev in Thread] Current Thread [Next in Thread]