Wed Oct 23 10:04:11 2019 apache2@netcasters.com - Ticket created [Reply] [Forward]
Subject: Problem with particular PDF
Date: Wed, 23 Oct 2019 09:25:01 -0400
To: bug-pdf-api2@rt.cpan.org
From: apache2 <apache2@netcasters.com>
Hi,
I have a particular pdf (actually there are a few of them), that when written to via PDF::API2, Adobe cannot render the file. This is via Internet Explorer, Edge and Firefox. Chrome renders the file fine.
I did a simple offline test:
- Call ghostscript to make a copy of the file. SUCCESS
- Add "Hello World" text to file. SUCCESS
- Save file SUCCCESS
- Call ghostscript to make a copy of the file. ERROR
So, in this case ghostscript has an issue with the file. Maybe the issue is with ghostscript and Adobe.
Seems like you need to see the pdf and possible my test code, but I'd rather not make it public since it is a client file. What can we do to resolve?
Let me know if you need any further information.
Thank you very much
Ted
Thu Oct 24 11:11:10 2019 PMPERRY@cpan.org - Correspondence added
Well, yes, we ARE going to need an example PDF that shows this problem. If I understand your explanation, you have a working PDF, modify it with GS, and then Adobe doesn't like it? Was this PDF originally produced with PDF::API2? Which "Adobe" are you talking about -- Reader, Acrobat, or something else? First of all, PDF::API2 produces PDF 1.4, which while old, should work OK with GS or Adobe. If GS takes a working PDF (that Reader doesn't ask to SAVE after displaying), and breaks it, that sounds like a problem with GS. Without seeing an example, though, it's hard to say for sure whether there was something odd about the original PDF.
If the PDF was produced with PDF::API2, please supply the Perl code for PDF::API2, rather than just the PDF output. Cut down the code to the minimum that shows the problem, while removing proprietary information. Just for giggles, you might try it with PDF::Builder too, and see if the same problem shows up. Note that if Adobe Reader asks to save a PDF when exiting, that means it had to fix up a defective PDF when it loaded it.
Thu Oct 24 11:11:10 2019 The RT System itself - Status changed from 'new' to 'open'