On Wed, Apr 14, 2010 at 9:25 PM, brian m. carlson <[email protected]> wrote:
On Tue, Apr 13, 2010 at 09:32:07AM +0200, Mathieu Malaterre wrote:1. Use full path for `embed-url` in your fop.xconf: <font kerning="yes" metrics-url="file:///etc/fop/fonts/times-roman.xml" embed-url="times.ttf">Yes, that does seem to fix the problem. Nevertheless, this is a regression. This basically forces me to specify every TTF file on the system in fop.xconf, even though Debian has standard locations for them.
BTW did you know since fop 0.95 that all this mess is not required anymore. See for instance: http://www.mail-archive.com/[email protected]/msg11702.html ... Note that starting from FOP 0.95 (and unofficially from FOP 0.94) this is no longer required to generate XML metrics files for fonts. You can rely on the font discovery mechanism described in the section “Basic font configuration” at the following link: http://xmlgraphics.apache.org/fop/0.95/fonts.html#basics and that should be just it. ... Here is my fop.xconf (We are using DevaVu and OpenSymbol): <?xml version="1.0"?> <fop version="1.0"> <renderers> <renderer mime="application/pdf"> <filterList> <!-- provides compression using zlib flate (default is on) --> <value>flate</value> </filterList> <fonts> <auto-detect/> <!-- IMPORTANT --> </fonts> </renderer> </renderers> </fop> Since all my fonts are in /usr/share/fonts (*), it works out of the box
2. Send the output of `fop -d`. So we can check if your local fonts dir is properly inspectedOkay, but due to #575411, all you're going to get from fop is a complaint about log4j. lakeview ok % fop -d -c /etc/fop/fop.xconf -fo crypto-primer.fo -pdf crypto-primer.pdf log4j:WARN No appenders could be found for logger (org.apache.fop.util.ContentHandlerFactoryRegistry). log4j:WARN Please initialize the log4j system properly.
ok, sorry :( -- Mathieu (*)http://xmlgraphics.apache.org/fop/0.95/fonts.html#register
signature.asc
Description: OpenPGP digital signature
