Manuel Mall wrote:
On Friday 19 January 2007 14:08, Daniel Noll wrote:
Hi all...
Daniel,
could you try and use a font name not including spaces, e.g.
ArialUnicodeMS. I am suspicious that the font family name property
parser may take 'Arial Unicode MS' as a specification of 3 font
alternatives and not as a single font name.
Ah... that does fix it. :-)
The XSL-FO spec says that commas are required between alternative fonts,
so I guess it's a bug in FOP. Might not be too hard for me to fix
myself, though, if it's just a string splitting or regex issue.
Daniel
--
Daniel Noll
Nuix Pty Ltd
Suite 79, 89 Jones St, Ultimo NSW 2007, Australia Ph: +61 2 9280 0699
Web: http://nuix.com/ Fax: +61 2 9212 6902
This message is intended only for the named recipient. If you are not
the intended recipient you are notified that disclosing, copying,
distributing or taking any action in reliance on the contents of this
message or attachment is strictly prohibited.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
