Hi Mike, body.font.family and symbol.font.family are docbook specific parameters. FOP does only handle XSL-FO, i.e. what is output by docbook XSLT.
That said, FOP 0.93 is quite old today, and font handling had been strongly improved since that version: FOP 1.0 implements a basic font-selection-strategy (only "auto" is assumed, see [1]). That means that if you set font-family with a font list, then FOP will "choose" the better font to render the text, so I guess that cited parameters should help. In addition, according to [1], you'll probably have to "isolate" special characters groups within 2 ZWSP (​) in order to help FOP to render them in appropriate alternate font. [1] http://xmlgraphics.apache.org/fop/1.0/fonts.html#selection Le 20/09/2011 12:36, mike 675 a écrit : >> There have been a lot of changes between 0.20.5 and 1.0, although > Unicode characters should be displayed properly, provided FOP can > find a font containing a glyph for the character. > Did you get an error or warning message? What does "not rendered" > mean precisely: is there a blank instead of the arrow, another > character, or is it completely omitted? < > I get a #character. > >> >Does your Helvetica font > contain a glyph for the U+2192 (check with a font viewer or font > editor, if in doubt), or did you override the font locally (with > something other than font="Symbol")< > > I am using Linux. I think Sans is used for Helvetica. > Sans includes U+2192. > >> >I also notice that you use DocBook, it may be necessary to adjust > some parameters to tell the style sheets you are using FOP 1.0 now.< > I am using the fop1.extensions parameter. > > Question: Does FOP 1.0 support the XSL body.font.family and > symbol.font.family parameters? > This page suggests it does not, as from 0.93: > > http://www.sagehill.net/docbookxsl/SpecialChars.html#MissingChars -- Pascal --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
