Hi Andreas Thanks for your rapid response.
I was expecting that FOP would do substitution when it encounters a glyph for which it has no font. There's a note about that at http://xmlgraphics.apache.org/fop/trunk/fonts.html#substitution that implied to me that FOP will try to choose the correct font automatically based on the content of the word that it is rendering. I dug a bit deeper and found the following: http://www.w3.org/TR/xsl/#font-family """ To deal with the problem that a single font may not contain glyphs to display all the characters in a document, or that not all fonts are available on all systems, this property allows authors to specify a list of fonts, all of the same style and size, that are tried in sequence to see if they contain a glyph for a certain character. """ On Sat, 2008-08-30 at 15:08 +0200, Andreas Delmelle wrote: > Can you show us the FO? How exactly are you inserting the character? > > Something like > > <fo:block font-family="Symbol">∀</fo:block> > > works nicely on my end. I cooked up the following test case: <?xml version='1.0' encoding='utf-8'?> <root xmlns='http://www.w3.org/1999/XSL/Format'> <layout-master-set> <simple-page-master master-name='master' page-width='5cm' page-height='2cm'> <region-body/> </simple-page-master> </layout-master-set> <page-sequence master-reference='master'> <flow flow-name='xsl-region-body'> <block font-family='serif'> some text with ∀ a symbol. </block> <block font-family='Symbol'> some text with ∀ a symbol. </block> <block font-family='serif,Symbol'> some text with ∀ a symbol. </block> </flow> </page-sequence> </root> On my FOP (0.95 binary directly from the site) I get the following output: some text with # a symbol. #### #### #### ∀ # ######. some text with # a symbol. The first two lines make perfect sense, but I would expect the last line to contain all the characters properly rendered. It might be that I'm misreading/misunderstanding FO since I'm quite new to all of this but the (real) output that (originally) triggered the problem is actually from the Docbook XSL stylesheets. There's a note there, too: http://docbook.sourceforge.net/release/xsl/current/doc/fo/symbol.font.family.html """ A typical body or title font does not contain all the character glyphs that DocBook supports. This parameter specifies additional fonts that should be searched for special characters not in the normal font. These symbol font names are automatically appended to the body or title font family name when fonts are specified in a font-family property in the FO output. """ This results in all of my blocks being marked with font-family='serif,Symbol,ZapfDingbats' which, just like the small test case given above, fails to work. Any additional insight is definitely appreciated. :) Thanks again --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
