>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
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
--
View this message in context:
http://old.nabble.com/Extended-characters-not-rendered-using-FOP-1.0-tp32494019p32501055.html
Sent from the FOP - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
