> Now, for just random PDFs, this is a bit more tricky, but you can do so > with ghostscript. Now, this sadly doesn't have such a great guide, but > something like this should do the trick, though that's only PDF/A-1 for all > I can tell. If your contractor needs a different version, you'll have to > adapt it: > > gs -dQUIET -dUseCIEColor -sProcessColorModel=DeviceCMYK -sDEVICE=pdfwrite > -dPDFACompatibilityPolicy=1 -dCompressFonts=true -dSubsetFonts=true > -sFONTPATH=/usr/share/fonts/ -o <file name of output> <file name of input>
This does not seem to work. For example: $cd /tmp $wget -O old.pdf https://arxiv.org/pdf/2406.18499 $gs -dQUIET -dUseCIEColor -sProcessColorModel=DeviceCMYK -sDEVICE=pdfwrite -dPDFACompatibilityPolicy=1 -dCompressFonts=true -dSubsetFonts=true -sFONTPATH=/usr/share/fonts/ -o new.pdf old.pdf [Gives warnings: GPL Ghostscript 10.00.0: Use of -dUseCIEColor detected! Since the release of version 9.11 of Ghostscript we recommend you do not set -dUseCIEColor with the pdfwrite/ps2write device family.] Uploading new.pdf to https://www.pdfforge.org/online/en/validate-pdfa produces report "The file is not a valid PDF/A document" with these details: ISO 19005-1:2005 6.1.8 The object number and generation number shall be separated by a single white-space character. The generation number and obj keyword shall be separated by a single white-space character. The object number and endobj keyword shall each be preceded by an EOL marker. The obj and endobj keywords shall each be followed by an EOL marker. ISO 19005-1:2005 6.1.7 The stream keyword shall be followed either by a CARRIAGE RETURN (0Dh) and LINE FEED (0Ah) character sequence or by a single LINE FEED character. The endstream keyword shall be preceded by an EOL marker Repeating with the flag -dUseCIEColor removed prevents the Ghostscript warnings but doesn't change the PDF/A validation result. Best regards, Greg Marks
signature.asc
Description: PGP signature
