Re: [NTG-context] PDF/A no longer compliant?

I’m afraid I don’t remember exactly which validator that was. I tried a few such as veraPDF and Adobe Acrobat’s preflight verifier. I found one of the preflight output files from Acrobat (but not the input document unfortunately) and these were the errors when validated against PDF/A-3a: 1. Device process color used but no PDF/A OutputIntent (101 matches on 1 page) - 1 2. Syntax problem: String object invalid (odd number of hexadecimal characters) I think the second error was due to the BOM. -- Leo On Sat, 3 Nov 2018 at 13:11, luigi scarso wrote:

On Fri, Nov 2, 2018 at 9:03 PM Leo Nikkilä wrote:

...

I tried PDF/A a while back and noticed the XMP header has an extra byte order mark which validators flagged as “??”.

I’ve attached the patch I used to remove it, however I’m still on an old version of ConTeXt so this might not apply cleanly to yours.

You might need to open the patch in a hex editor to see the difference in the two lines as most text editors will not show the BOM.

-- Leo

Thank you for the patch. Which validator are you referring to?

-- luigi

___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net

___________________________________________________________________________________