Re: [dev-context] fix output intent subtype

On 10/23/2017 11:14 PM, Peter Rolf wrote:

Am 23.10.2017 um 19:14 schrieb Hans Hagen:

...

On 10/23/2017 7:01 PM, luigi scarso wrote:

...

...

Hans,

according to Boris Doubrov (one of the developers of the veraPDF parser for PDF/A validation) the subtype of the /OutputIntent dictionary for all PDF/A intents should be GTS_PDFA1 (no GTS_PDFA2 or GTS_PDFA3).

Here is his reply for reference: https://github.com/veraPDF/veraPDF-parser/issues/317#issuecomment-338613962.

The attached patch fixes the issue. I have tried it myself and it solves the problems with color space profiles.

Could you apply it to ConTeXt?

Many thanks for your help, sure, but it's better if we have an example that fails --- I mean, the source code,  the version of the parser , the command

On Mon, Oct 23, 2017 at 6:25 PM, Pablo Rodriguez wrote: line used. It could be that other parts are also not ok. i also want to check with Peter

No objections, the 'gts_flag' is also fix for the PDF/X variants.

So all variants get GTS_PDFA1 ?

I think I have tested all variants at that time (around Oct 2015) and 'veraPDF' didn't throw an error. Looks like they have improved their parser on that part.

Well, for me it means that all that validation esp of keys like this are rather useless (creating work) because docs validated in the past and archived now are suddenly no longer valid. Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl -----------------------------------------------------------------