The example file in the wiki (at https://wiki.contextgarden.net/PDF/A) no longer verifies as compliant PDF/A. VeraPDF rejects it, and https://www.pdf-online.com/osa/validate.aspx complains: x107.pdf Compliance pdfa-1b Result Document does not conform to PDF/A. Details Validating file "x107.pdf" for conformance level pdfa-1b Invalid content of XMP packet header attribute 'begin': '??'. The property 'pdfx:ConTeXt.Support' is not defined in schema 'PDF/X ID Schema'. The property 'pdfx:TeX.Support' is not defined in schema 'PDF/X ID Schema'. The property 'pdfx:LuaTeX.Version' is not defined in schema 'PDF/X ID Schema'. The property 'pdfx:LuaTeX.Functionality' is not defined in schema 'PDF/X ID Schema'. The property 'pdfx:LuaTeX.LuaVersion' is not defined in schema 'PDF/X ID Schema'. The property 'pdfx:LuaTeX.Platform' is not defined in schema 'PDF/X ID Schema'. The document does not conform to the requested standard. The document's meta data is either missing or inconsistent or corrupt. The document does not conform to the PDF/A-1b standard. Done.
Il giorno ven 2 nov 2018, 19:06 Rik Kabel
The example file in the wiki (at https://wiki.contextgarden.net/PDF/A) no longer verifies as compliant PDF/A. VeraPDF rejects it, and https://www.pdf-online.com/osa/validate.aspx complains:
x107.pdf Compliance pdfa-1b Result Document does not conform to PDF/A. Details
Validating file "x107.pdf" for conformance level pdfa-1b
Invalid content of XMP packet header attribute 'begin': '??'.
The property 'pdfx:ConTeXt.Support' is not defined in schema 'PDF/X ID Schema'.
The property 'pdfx:TeX.Support' is not defined in schema 'PDF/X ID Schema'.
The property 'pdfx:LuaTeX.Version' is not defined in schema 'PDF/X ID Schema'.
The property 'pdfx:LuaTeX.Functionality' is not defined in schema 'PDF/X ID Schema'.
The property 'pdfx:LuaTeX.LuaVersion' is not defined in schema 'PDF/X ID Schema'.
The property 'pdfx:LuaTeX.Platform' is not defined in schema 'PDF/X ID Schema'.
The document does not conform to the requested standard.
The document's meta data is either missing or inconsistent or corrupt.
The document does not conform to the PDF/A-1b standard.
Done.
___________________________________________________________________________________ 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
___________________________________________________________________________________
I will check it asap
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
On Fri, 2 Nov 2018 at 20:12, luigi scarso
Il giorno ven 2 nov 2018, 19:06 Rik Kabel
ha scritto: The example file in the wiki (at https://wiki.contextgarden.net/PDF/A) no longer verifies as compliant PDF/A. VeraPDF rejects it, and https://www.pdf-online.com/osa/validate.aspx complains:
x107.pdf Compliance pdfa-1b Result Document does not conform to PDF/A. Details
Validating file "x107.pdf" for conformance level pdfa-1b
Invalid content of XMP packet header attribute 'begin': '??'.
The property 'pdfx:ConTeXt.Support' is not defined in schema 'PDF/X ID Schema'.
The property 'pdfx:TeX.Support' is not defined in schema 'PDF/X ID Schema'.
The property 'pdfx:LuaTeX.Version' is not defined in schema 'PDF/X ID Schema'.
The property 'pdfx:LuaTeX.Functionality' is not defined in schema 'PDF/X ID Schema'.
The property 'pdfx:LuaTeX.LuaVersion' is not defined in schema 'PDF/X ID Schema'.
The property 'pdfx:LuaTeX.Platform' is not defined in schema 'PDF/X ID Schema'.
The document does not conform to the requested standard.
The document's meta data is either missing or inconsistent or corrupt.
The document does not conform to the PDF/A-1b standard.
Done.
___________________________________________________________________________________ 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
___________________________________________________________________________________
I will check it asap
___________________________________________________________________________________ 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
___________________________________________________________________________________
On Fri, Nov 2, 2018 at 9:03 PM Leo Nikkilä
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
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
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
___________________________________________________________________________________
On Sat, Nov 3, 2018 at 1:58 PM Leo Nikkilä
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.
ok, thank you very much. -- luigi
On Fri, Nov 2, 2018 at 7:06 PM Rik Kabel
The example file in the wiki (at https://wiki.contextgarden.net/PDF/A) no longer verifies as compliant PDF/A. VeraPDF rejects it, and https://www.pdf-online.com/osa/validate.aspx complains:
x107.pdf Compliance pdfa-1b Result Document does not conform to PDF/A. Details
Validating file "x107.pdf" for conformance level pdfa-1b
Invalid content of XMP packet header attribute 'begin': '??'.
The property 'pdfx:ConTeXt.Support' is not defined in schema 'PDF/X ID Schema'.
The property 'pdfx:TeX.Support' is not defined in schema 'PDF/X ID Schema'.
The property 'pdfx:LuaTeX.Version' is not defined in schema 'PDF/X ID Schema'.
The property 'pdfx:LuaTeX.Functionality' is not defined in schema 'PDF/X ID Schema'.
The property 'pdfx:LuaTeX.LuaVersion' is not defined in schema 'PDF/X ID Schema'.
The property 'pdfx:LuaTeX.Platform' is not defined in schema 'PDF/X ID Schema'.
The document does not conform to the requested standard.
The document's meta data is either missing or inconsistent or corrupt.
The document does not conform to the PDF/A-1b standard.
Done.
it should be fixed in the next beta. -- luigi
On 11/4/2018 07:27, luigi scarso wrote:
On Fri, Nov 2, 2018 at 7:06 PM Rik Kabel
mailto:context@rik.users.panix.com> wrote: it should be fixed in the next beta.
I am afraid it is not fixed. The compilation of the wiki example now fails with: lua error > lua error on line 12 in file c://Users/micro/Projects/TeX/ConTeXt/pdfa.tex: ...ce0dde776fb1556f32e\formats\luajittex/lpdf-ini-macro.lua:236: attempt to call global 'pdfsetomitcidset' (a nil value) and in a larger file, I also see: system > lua > fatal error 1 in file 'C:/ConTeXt/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/fonts/otl/antykwatorunskacond-bold.tma' I have deleted the lua cache and regenerated and so no different result. I am running, per my log: ConTeXt was updated from version 2018.10.18 00:07 to version 2018.11.29 19:46. LuaTeX was updated from version 1.09.0 6980 to version 1.09.0 6998. -- Rik
On Fri, Nov 30, 2018 at 2:28 AM Rik Kabel
On 11/4/2018 07:27, luigi scarso wrote:
On Fri, Nov 2, 2018 at 7:06 PM Rik Kabel
wrote: it should be fixed in the next beta.
I am afraid it is not fixed. The compilation of the wiki example now fails with:
lua error > lua error on line 12 in file c://Users/micro/Projects/TeX/ConTeXt/pdfa.tex: ...ce0dde776fb1556f32e\formats\luajittex/lpdf-ini-macro.lua:236: attempt to call global 'pdfsetomitcidset' (a nil value)
typo
$ diff -u lpdf-ini.lua.orig lpdf-ini.lua --- lpdf-ini.lua.orig 2018-11-30 07:13:21.120218873 +0100 +++ lpdf-ini.lua 2018-11-30 07:13:37.459920498 +0100 @@ -233,7 +233,7 @@ end function lpdf.setomitcidset(v) - return pdfsetomitcidset(v) + return pdf.setomitcidset(v) end do -- luigi
On Fri, Nov 30, 2018 at 7:17 AM luigi scarso
On Fri, Nov 30, 2018 at 2:28 AM Rik Kabel
wrote: On 11/4/2018 07:27, luigi scarso wrote:
On Fri, Nov 2, 2018 at 7:06 PM Rik Kabel
wrote: it should be fixed in the next beta.
I am afraid it is not fixed. The compilation of the wiki example now fails with:
lua error > lua error on line 12 in file c://Users/micro/Projects/TeX/ConTeXt/pdfa.tex: ...ce0dde776fb1556f32e\formats\luajittex/lpdf-ini-macro.lua:236: attempt to call global 'pdfsetomitcidset' (a nil value)
typo
$ diff -u lpdf-ini.lua.orig lpdf-ini.lua --- lpdf-ini.lua.orig 2018-11-30 07:13:21.120218873 +0100 +++ lpdf-ini.lua 2018-11-30 07:13:37.459920498 +0100 @@ -233,7 +233,7 @@ end
function lpdf.setomitcidset(v) - return pdfsetomitcidset(v) + return pdf.setomitcidset(v) end
do
-- luigi
better $ diff -u lpdf-ini.lua.orig lpdf-ini.lua --- lpdf-ini.lua.orig 2018-11-30 07:13:21.120218873 +0100 +++ lpdf-ini.lua 2018-11-30 10:02:57.250980666 +0100 @@ -233,7 +233,7 @@ end function lpdf.setomitcidset(v) - return pdfsetomitcidset(v) + return setomitcidset(v) end do -- luigi
participants (3)
-
Leo Nikkilä
-
luigi scarso
-
Rik Kabel