Pascal Sancho wrote:
Hi,
The XSL-FO REC 1.0 says: "Font family names containing whitespace
should be quoted. If quoting is omitted, any whitespace characters
before and after the font name are ignored and any sequence of
whitespace characters inside the font name is converted to a single
space."
Hi,
The XSL-FO REC 1.0 says:
"Font family names containing whitespace should be quoted. If quoting is
omitted, any whitespace characters before and after the font name are ignored
and any sequence of whitespace characters inside the font name is converted to
a single space."
IIRC, in this cas
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 M
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
alternati
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 sin
Hi all...
After upgrading to FOP 0.93 I'm having issues getting custom fonts
working. I've properly updated my configuration to the new schema for
the config file:
The b
