Ok, then lulu.com doesn't respect the PDF standard. I haven't tried but maybe you could work around that (really strange) problem by changing the font-name value in the XML font metrics file to a different name, like "MyTimes-Roman" instead of "Times". In your FO document and in the userconfig.xml you'll have to do the same. That way you should be able to embed the standard Type 1 font without running into a problem because it's part of the Base 14 set. But I can't test it beforehand because I don't have the original base 14 font set here to test. So, no guarantees.
I hope that helps. On 16.12.2005 16:40:47 Paul wrote: > On 12/16/05, Jeremias Maerki <[EMAIL PROTECTED]> wrote: > > You don't need to embed Times-Roman because that font is covered by the > > Base-14 font package that is perscribed by the PDF standard. The fonts > > "Times", "Helvetica", "Courier", "ZapfDingbats" and "Symbol" can always > > be considered present in PDF and PostScript. Of course, "Times-Roman" > > Regardless of the PDF standard, lulu.com unfortunatley requires that > these fonts be embedded. > > Example: the following error from their server > Your document could not be created: Font "Times-Roman" is not embedded. > Font "Times-Italic" is not embedded. > Font "Times-Bold" is not embedded. > > Now, I removed those entries in my userconfig (I had initially placed > the entries there in an attempt to get those fonts embeded) but now we > have type1 fonts that aren't embeded. > > It seems that no matter which truetype or type1 you embed, times-roman > (type1) is always in the font list for the PDF and is not embeded in > the document. > > Any other suggestions? > Paul Jeremias Maerki --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
