On 06.08.2008 13:12:28 lmhelp wrote: > > Thank you Jeremias. > > Hi everyone, > > So, I've upgraded to fop-0.95. > > I've added the following line to the ../fop-0.95/conf/fop.xconf file: > <directory>C:/Program Files/fop-0.95/fonts_lea/</directory> > (Maybe this is not the right file to update... ?) > > ============================================ > Here is the whole configuration file (fop.xconf) as it is now: > ============================================ <snip/>
Config file looks good without having actually using it. > The C:/Program Files/fop-0.95/fonts_lea/ directory contains the TTF file > verdana.ttf > which I copied from C:/WINDOWS/Fonts. > > (Tell me if I am wrong:) > if your TTF file's name is "fontname.ttf" then the font name you have to use > in the xsl-fo file is "fontname" (for example: <fo:block > font-family="fontname">) > to get it work. No, the font-family is not derived from the filename. The font itself contains the font family name that is to be used. In the case of verdana.ttf that would be "Verdana" (case-sensitive!). > Once having done that, I launched the following command: > # fop -c "C:\Program Files\fop-0.95\conf\fop.xconf" -xml projectteam.xml \ > -xsl projectteam2fo.xsl -pdf projectteam.pdf > and it worked. > But I had to put the -c option above... Yes, sure, otherwise you only have a default font configuration, not your custom one. > See you. > -- > View this message in context: > http://www.nabble.com/FOP---FONTS---expl.-verdana-tp18836748p18849018.html > Sent from the FOP - Users mailing list archive at Nabble.com. Jeremias Maerki --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
