Venkat Reddy wrote:
Hi Chris,
Hi Venkat, <snip/>
Parsing font... Reading C:\windows\fonts\msmincho.ttc... This is a TrueType collection file with 2 fonts Containing the following fonts: MS Mincho <-- selected MS PMincho Font Family: [MS Mincho, ?? ??] Creating xml font file... Creating CID encoded metrics... Writing xml font file msminch.xml... This font contains no embedding license restrictions. I have given sub-font="MS Mincho" and got the same result as "#####".
So the end result was the same, but that doesn't mean the route taken to get there was the same. Changing to use sub-font attribute should have eliminated font not found warnings from FOP. Can you confirm the log output from FOP with this configuration?
If the Font is indeed correctly configured now and you still see # in the output then that indicates the MS Mincho font you are using does not contain the glyphs you are trying to use in your XSL-FO. If that is the case then I would expect to see glyph not found warnings in the FOP log.
I have no idea, why this configuration is not working?
<snip/> Chris --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
