[NTG-context] PDF/A no longer compliant?
hello at lnikki.la
Sat Nov 3 13:57:13 CET 2018
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
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
I think the second error was due to the BOM.
On Sat, 3 Nov 2018 at 13:11, luigi scarso <luigi.scarso at gmail.com> wrote:
> On Fri, Nov 2, 2018 at 9:03 PM Leo Nikkilä <hello at lnikki.la> 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.
> Thank you for the patch. Which validator are you referring to?
> If your question is of interest to others as well, please add an entry to
> the Wiki!
> maillist : ntg-context at ntg.nl /
> webpage : http://www.pragma-ade.nl / http://context.aanhet.net
> archive : https://bitbucket.org/phg/context-mirror/commits/
> wiki : http://contextgarden.net
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the ntg-context