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,
Pablo
--
http://www.ousia.tk
--- mkiv/lpdf-fmt.lua 2017-10-19 13:54:58.000000000 +0200
+++ lpdf-fmt.lua 2017-10-23 18:18:10.528400281 +0200
@@ -355,7 +355,7 @@
pdf_version = 1.7,
format_name = "pdf/a-2a",
xmp_file = "lpdf-pda.xml",
- gts_flag = "GTS_PDFA2",
+ gts_flag = "GTS_PDFA1",
gray_scale = true,
cmyk_colors = true,
rgb_colors = true,
@@ -379,7 +379,7 @@
pdf_version = 1.7,
format_name = "pdf/a-3a",
xmp_file = "lpdf-pda.xml",
- gts_flag = "GTS_PDFA3",
+ gts_flag = "GTS_PDFA1",
gray_scale = true,
cmyk_colors = true,
rgb_colors = true,
_______________________________________________
dev-context mailing list
[email protected]
https://mailman.ntg.nl/mailman/listinfo/dev-context
