Le 08/09/2010 07:56, Antti Karanta a écrit : > On Mon, 30 Aug 2010 18:31:18 +0300, Pascal Sancho > <[email protected]> wrote: >> '#' indicates that the glyph is not available in any font used by FOP. >> Note that SVG uses the fonts installed in the system, while FOP needs > ?? I think you mean the AWT renderer gets its fonts from the os and the > pdf renderer needs special font configuration? That's the impression I got > from http://xmlgraphics.apache.org/fop/1.0/output.html#general-fonts Partially correct: for PDF output, you need to configure used fonts for the PDF renderer, while Batik (SVG engine) uses fonts from OS. So, you have to check the 2 places when rendering XSL-FO+SVG to PDF.
>> that used fonts are set in config file (if you use a non standard font). > Like I said in my post, I have > > <fonts> > <auto-detect/> > </fonts> > > in my fop.xconf. Is this not sufficient? > > > Anyhow, the thing that made me wonder is that special characters are > working also in fop generated pdfs if they are outside svg images - it's > only the ones in the svg images that are failing. > > I changed the font family reference in the svg files from > font-family:Swiss,Helvetica,sans-serif; to > font-family:Swiss,Helvetica,sans-serif,Tahoma,Verdana; and now the special > characters are ok. From this it seems to me that this was simply an issue > of the font families originally listed not containing the necessary glyphs. > So not really a FOP issue at all, sorry for the noise. I've not played with multiple font-family setting in SVG, but I guess this is the issue origin. Note that font-selection is implemented in FOP since the latest version (1.0), so you should check in that direction. > > > ::Antti:: Pascal --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
