Hi Bonekrusher,
The <font-triplet> element has to be contained in the <font> element- see
http://xmlgraphics.apache.org/fop/0.95/fonts.html for the configuration
documentation.

You may need to include file:///C:/Program Files(x86)/fop-0.95/fonts in the
base-uri attribute, or in the <base> element of your fop.xconf

Pete


On Thu, Apr 15, 2010 at 2:02 PM, bonekrusher <[email protected]> wrote:

>
> Hi,
>
> I am using the following in my fop.xconf to embed fonts. Everything works
> on
> my PC, but when I run on a different machine, the fonts are not found:
>
> fop.xconf
>
> <fonts>
>
>                <font-triplet name="Arial" style="normal" weight="normal"/>
>                <font-triplet name="Arial" style="normal" weight="400"/>
>                <font-triplet name="Arial" style="normal" weight="700"/>
>                <font-triplet name="ArialMT" style="normal"
> weight="normal"/>
>
>
>                <font-triplet name="Arial" style="normal" weight="bold"/>
>                <font-triplet name="Arial" style="normal" weight="normal"/>
>                <font-triplet name="Arial" style="normal" weight="400"/>
>                <font-triplet name="Arial" style="normal" weight="700"/>
>                <font-triplet name="ArialMT" style="normal" weight="bold"/>
>
> </fonts>
>
> I have converted the font matrix with org.apache.fop.fonts.apps.TTFReader
> to
> xml and placed them in a folder "file:///C:/Program Files
> (x86)/fop-0.95/fonts"
>
> FOP reports:
>
> Apr 13, 2010 2:05:47 PM org.apache.fop.fonts.FontInfo notifyFontReplacement
> WARNING: Font 'Arial,normal,700' not found. Substituting with
> 'any,normal,700'.
>
> The file structure is the same on both machines...
>
> Any thoughts?
>
> Thanks,
>
>
> --
> View this message in context:
> http://old.nabble.com/Help-embeding-fonts-tp28254961p28254961.html
> Sent from the FOP - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to