Hi Daniel,
Daniel Noll a écrit :
> On Wednesday 30 May 2007 16:55:36 Vincent Hennebert wrote:
>> Or if you are sure that the Lucida font contains all the characters you
>> need, you can directly specify this font for the whole FO document:
>>
>> <fo:page-sequence font-family="Lucida"...
>>
>> for each page-sequence, plus you setup the Lucida font as usual in your
>> config file:
>> http://xmlgraphics.apache.org/fop/0.93/fonts.html#custom
>>
>> That way every character will appear in Lucida, you have both a
>> consistent and working result.
>> Is that what you need?
>
> I'm not sure that will solve the problem because there may be an element
> further in with font-family="something" that sets it back to some other font
> which may not have that character. And since our FO file tends to indirectly
> come from HTML+CSS, it's highly likely that there are custom fonts somewhere.
Ah, I see your problem. Then you can redefine the fallback font to
Lucida in the config file. For example:
<renderer mime="application/pdf">
<fonts>
<font kerning="yes" metrics-url="Lucida.xml"
embed-url="Ludica.ttf">
<font-triplet name="any" style="normal" weight="normal"/>
</font>
...
and do the same for the various combinations of bold and italic. That
way if some non-configured fonts appear in the FO file the Lucida one
will be used as a fallback.
> I guess I could do per-character substitution using a custom XML filter of
> some sort to mangle the FO input.
Yes, if you want a finer-grain control (only some characters not
available in a font, as Jeremias wrote).
HTH,
Vincent
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
