Thanks, I'll look into that. Yes, FOP does print a # with the Trunk, at least as it was last I compiled it. FOP prints a square with the 2611, which could be some sort of default invalid? Windows apps (Notepad, Wordpad?) print squares whenever they load a file with an unrecgnized character. I'll have to see what that unicode is all about. If it's supposed to load those chars listed on that unicode.org website, and they're supposed to be in the font file, I may need to load in another font file to get those. I'm still working on installing that font editor to see if it says the font contains those glyphs.
-----Original Message----- From: J.Pietschmann [mailto:[email protected]] Sent: Saturday, July 17, 2010 11:20 AM To: [email protected] Subject: Re: Font Glyph? On 15.07.2010 22:44, Eric Douglas wrote: > Then I pass a text value of "☑" in my XML. When the > transformer uses FOP to translate the XML into output, this prints a square. Have a look at http://www.unicode.org/charts/charindex.html U2611 is "BALLOT BOX WITH CHECK", i.e. not a square (U2610 should be a square, are you sure about the entity?) If FOP couldn't find the glyph, it would have printed a # instead. You could use one of the font editors to check whether your font actually has a glyph for the U2611 character (try http://fontforge.sourceforge.net/) > I tried replacing my fop.jar with one that I compiled from the Trunk, > and instead of printing the square it printed an error message to the > Java Console that the font doesn't contain the specified glyph. That's mildly odd, I'd guess your method for telling FOP about your font doesn't work as in Trunk. J.Pietschmann
