On Tue, 2007-06-05 at 23:12 -0600, Frank Cox wrote: > On Wed, 06 Jun 2007 13:03:55 +0800 > Gavin Chester <[EMAIL PROTECTED]> wrote: > > > Scenario: > > A document, containing ONLY text of around 20-50k typically blows out to > > 300-600k when exported as pdf in OO.o 2.0.4.17 OpenSuse version. How can > > I overcome this? > > > 3/ I can post-process the resulting pdf file using ghostscript and the > > file comes down to very close to the original OO.o file size - sometimes > > less depending on the document(s), but I don't want to have to do this > > two-step technique > > As you've already seen, ps2pdf (and friends) can give you a much smaller PDF > file than OpenOffice.org natively. > > The best solution that I can offer would be to script it. > > Any time I send someone a pdf from OpenOffice.org, I always print-to-file and > use ps2pdf to create the final product for posting or emailing or whatever. > You can easily write a little bash script to convert everything in a directory > to pdf so you could print-to-file a bunch of documents and then create the > pdf's in one blast at the end. > > A one-line command like this should work to convert all .ps files in a > directory to pdf files: > > for i in *.ps; do ps2pdf $i; done
Thanks for your prompt and useful reply. I already use that function to save web pages as pdf (ie, print to ps and then ps2pdf - cups can be configured to do the same but I haven't got that sorted). The problem is I didn't imagine having to do it with OO.o when that "export" feature is there. Basically, you're saying that export to pdf is broken in version 2.0.4 because it didn't have this behaviour in earlier 2.x versions. That is, we enjoy greater control with newer OO.o pdf creation, but it seems to have broken something. I wish there was more control over font embedding, for example :-( Gavin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
