On Tue, Oct 31, 2006 at 11:11:25AM -0600, Richard Laager wrote: > Regarding one of our web servers, a co-worker of mine filed an internal > bug with this text: > > > ImageMagick fonts don't get properly configured -- this seems like it > > may be a package bug to me, though I'm not sure. > > Basically /usr/lib/ImageMagick-6.2.4/config/type.xml, as installed, > > refers to type-ghostscript.xml, which refers to fonts that are not > > installed (we don't have any Type 1 fonts installed).
ImageMagick indirectly suggests to install the gsfonts package. (It suggests to install gs which depends on gs-gpl which recommends gsfonts.) That's probably too weak a link, and we should add an explicit Recommends or Suggests on gsfonts to libmagick9. > > The ImageMagick > > examples page ( http://www.cit.gu.edu.au/~anthony/graphics/imagick6/ ) > > suggests using a script to enumerate fonts: > > http://www.cit.gu.edu.au/~anthony/graphics/imagick6/scripts/imagick_type_gen > > (this produces a replacement for type.xml). I did that and it seems to > > work fine. The proper way would probably involve having every installed > > font package add a file to be included in type.xml. (Well, ideally, there > > would be a type.d directory, I suppose :) ) > > Our needing to edit a configuration file which is stored > in /usr/lib/ImageMagick-6.2.4/config makes me nervous. It's going to get > overwritten on upgrades, since it's not a conffile, right? You can use environment variable MAGICK_CONFIGURE_PATH to add a directory containing local tweaks to ImageMagick's search path without modifying the packaged defaults. Regards, Daniel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]