Daniel Noll a écrit : > 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.
Some precisions: FOP does not exactly follow the spec here, as it should read Arial Unicode MS as a single font family. But this works when you quote font families which contain whitespace characters, as recommended by the spec, (<fo:block font-family="'Arial Unicode MS'">... mind the single quotes!). All that said, removing whitespaces from font family names certainly is the simplest solution ;-) Vincent --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
