| 2010-03-22 23:07:16 |
Duncan Lock |
description |
Binary package hint: pdftk
Since upgrading to 9.10 (Karmic), I've been getting an error processing some pdf files with pdftk.
I get the error trying to process pdf files which have been printed from OpenOffice Writer - but the same document 'exported' as a pdf file from OO Writer (via File -> Export as PDF...) - rather than being printed - works fine with pdftk.
I'm using the version of OpenOffice that comes with Karmic (Openoffice.org 3.1.1 OOO310m19 Build:4920, synaptic says openoffice.org-writer 1:3.1.1-5ubuntu1.1). I think this is the same version of office that I was using in Jaunty before upgrading, as I was using this PPA with Jaunty (https://launchpad.net/~openoffice-pkgs/+archive/ppa), so I'm guessing this might be something to do with the newer version of CUPS-PDF that comes with Karmic?
My two test case pdf files is just a completely blank OO Writer document either exported or printed to pdf - one works with pdftk, the other doesn't. I've attached them to this bug.
I get this error when I try to process the printed one:
duncan@duncan-desktop:~/test$ pdftk blank_pdf_printed_settings_default.pdf output printed_output.pdf
Unhandled Java Exception:
java.lang.ClassCastException: com.lowagie.text.pdf.PdfDictionary cannot be cast to com.lowagie.text.pdf.PRIndirectReference
at com.lowagie.text.pdf.PdfStamperImp.close(itext-2.1.5.jar.so)
This command also produces a zero length file called printed_output.pdf. Doing the same thing with the exported pdf produces no error:
duncan@duncan-desktop:~/test$ pdftk blank_pdf_exported_settings_default.pdf output export_output.pdf
and creates the export_output.pdf, as expected. All three pdf files appear to work fine in evince.
This bug is a problem because the 'Export as PDF' feature in open office doesn't produce faithful pdf's in all cases - printing to PDF seems to work better - but now pdftk doesn't like my printed pdf's, thus messing up my workflow. If there's any more information that I can provide that would help debug this issue, please just let me know. |
Binary package hint: pdftk
Since upgrading to 9.10 (Karmic), I've been getting an error processing some pdf files with pdftk.
I get the error trying to process pdf files which have been printed from OpenOffice Writer - but the same document 'exported' as a pdf file from OO Writer (via File -> Export as PDF...) - rather than being printed - works fine with pdftk.
I'm using the version of OpenOffice that comes with Karmic (Openoffice.org 3.1.1 OOO310m19 Build:4920, synaptic says openoffice.org-writer 1:3.1.1-5ubuntu1.1). I think this is the same version of office that I was using in Jaunty before upgrading, as I was using this PPA with Jaunty (https://launchpad.net/~openoffice-pkgs/+archive/ppa), so I'm guessing this might be something to do with the newer version of CUPS-PDF that comes with Karmic?
My two test case pdf files were created by from a completely blank OO Writer document both exported then printed to pdf - one works with pdftk, the other doesn't. I've attached them to this bug.
I get this error when I try to process the printed one:
duncan@duncan-desktop:~/test$ pdftk blank_pdf_printed_settings_default.pdf output printed_output.pdf
Unhandled Java Exception:
java.lang.ClassCastException: com.lowagie.text.pdf.PdfDictionary cannot be cast to com.lowagie.text.pdf.PRIndirectReference
at com.lowagie.text.pdf.PdfStamperImp.close(itext-2.1.5.jar.so)
This command also produces a zero length file called printed_output.pdf. Doing the same thing with the exported pdf produces no error:
duncan@duncan-desktop:~/test$ pdftk blank_pdf_exported_settings_default.pdf output export_output.pdf
and creates the export_output.pdf, as expected. All three pdf files appear to work fine in evince.
This bug is a problem because the 'Export as PDF' feature in open office doesn't produce faithful pdf's in all cases - printing to PDF seems to work better - but now pdftk doesn't like my printed pdf's, thus messing up my workflow. If there's any more information that I can provide that would help debug this issue, please just let me know.
|
|
