Re: Possible (side) effects of using dPDFACompatibilityPolicy=1

Ken Sharp <[email protected]>
Newsgroups gmane.comp.printing.ghostscript.devel
Message-ID <[email protected]>
At 08:35 27/01/2016 +0000, Simon Stratmann wrote:


>GPL Ghostscript 9.18: Annotation set to non-printing,
>  not permitted in PDF/A, annotation will not be present in output file
>GPL Ghostscript 9.18: PDFA doesn't allow images with Interpolate true.
>
>The link text is kept but the links don't work. The images seem to be 
>still there, so I don't know what Ghostscript could've left out?

I presume, but cannot say for certain without investigating the file, that 
it left out the link annotation (the *text* is not the same thing as the 
link) and it emitted the image without the /Interpolate flag being set.


>For comparison I converted the same PDF with 3-Heights PDF/A converter and 
>it would keep the links intact - so the links itself aren't the problem 
>and could be left in.

Not if they are set to non-printing. We could instead change them to 
'printing' but that isn't what Policy=1 does, it drops anything which is 
invalid.


>The point is, with PDFs which usually only contain text and images, could 
>I lose actual content or just metadata and stuff like links (if they were 
>in the PDF).

And I'm not going to guarantee you anything. Check the spec, anything which 
is  not permitted in a given level of PDF/A will be dropped from the output 
if you set the Policy to 1 (exception; we render transparency to an image 
for PDF/A-1).

Its up to you to decide whether that is acceptable to you.



                     Ken
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.