Apache OpenOffice (AOO) Bugzilla – Issue 7218
OOo 1.0.1 Writer: Printing-to-PDF problem
Last modified: 2003-03-11 17:57:50 UTC
I am using OOo 1.0.1. under RedHat Linux 7.3. I was trying to print a document (with lots of EPS pictures) to PDF (using standard GhostScript's PDF writer, and ADISTILL printer driver). My question is this: - Acrobat Reader 5.0 (both Win and Linux) complains: "The font 'Times-Bold~26' contains a bad /BBox." Why is this? - I checked the PDF produced (i.e. take a look at the PDF binary), it is level 1.3. I downgraded that to 1.2., the message still appears - the PDF produced by this has some strange font names, like Times-Bold~26, Times-Bold~3a, and so on. I have never seen these in other PDFs produced by Acrobat Distiller (Under Win2000). - When all the EPS images were removed from the file, and I printed again, there was no such "Times-Bold~26" thing. All are just Times-Bold as usual. Why is this? Could you point out what's wrong? I am using GhostScript version 6.52 in the Linux box. Wirawan
Created attachment 2586 [details] The writer's file with EPS pictures in it
Created attachment 2587 [details] The PDF produced from tbh-results-2.sxw (level 1.2)
Created attachment 2588 [details] The EPS source files
Created attachment 2589 [details] The writer's file *without* EPS pictures in it
reassigned
adusting project
basically around the EPS files inside the resulting PostScript document there should be a %%BeginDocument/%%EndDocument pair; if these are missing ghostscript gets confused. You can workaround this by putting these lines around the embedded EPS files; which is quite arduous in case of many EPS files. Alternatively you can probably produce EPS files by putting "%%BeginDocument: none" at their beginning and %%EndDocument at their end. This will be fixed in OOo 1.1 *** This issue has been marked as a duplicate of 4529 ***
As mentioned on the qa dev list on March 5th I will close all resolved duplicate issues. Please see this posting for details. First step in IssueZilla is unfortunately to set them to verified.
As mentioned on the qa dev list on March 5th I will close all resolved duplicate issues. Please see this posting for details.