Chris, I read the section you quote. However, the problem was that I didn't want any base fonts.
The base fonts kept sneaking in no matter what I did! But putting the font family in the fo:page-sequence solved the problem completely. It never occured to me to think of FOP having a fo:object (like java) and then act accordingly. This has really helped. Thanks! -Mike ----- Original Message ---- From: Chris Bowditch <[EMAIL PROTECTED]> To: [email protected] Sent: Tuesday, August 19, 2008 4:03:28 AM Subject: Re: config file embedding issues Mike Ferrando wrote: Hi Mike, > Pascal, > fo:page-sequence does not have a "font-family" or "font-size" attribute? > > Can you give me a code example? Any FO can have any property set on it. This is because XSL-FO supports inheritance of properties. So just because font-family doesn't apply to fo:page-sequence doesn't mean you can't set it there. Setting the font-family on fo:page-sequence will ensure that the property is propogated down to all the child elements. Reading your original post I don't think Pascal's answer will help you. On the help page for PDF/A-1b it says: <quote> Make sure all (!) fonts are embedded. If you use base 14 fonts (like Helvetica) you need to obtain a license for them and embed them like any other font. </quote> So if your XSL-FO uses Helvetica (as indicated by the error you receive) then you will need to acquire the Type1 Font Files (*afm and *.pfb) Then add entries to your fop.xconf configuration file to tell FOP to embed these fonts. <snip/> Chris --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
