On 27 Jan 2019, at 4:53 am, Reinhard Kotucha <reinhard.kotucha@web.de> wrote:

On 2019-01-26 at 10:04:30 -0700, Karl Berry wrote:

> I gather the PDF/A-1 standard is not available online. -k

See

https://github.com/veraPDF/veraPDF-validation-profiles/wiki

It provides at least section 6 (Technical Requirements).

Statements in sections "Requirement" are from the ISO specs.

Thanks for this link, and also Phil’s message.

I’ll add this into the Bibliography of pdfx.pdf .

Looking at:

https://github.com/veraPDF/veraPDF-validation-profiles/wiki/PDFA-Part-1-rules#error-details-58

Rule 6.3.5-2 for PDF/A-1

https://github.com/veraPDF/veraPDF-validation-profiles/wiki/PDFA-Parts-2-and-3-rules#error-details-70

Rule 6.2.11.4-3 for PDF/A-2 and PDF/A-3

it becomes clear that

• PDF/A-1 requires a CharSet entry to exist, but places no requirement on its accuracy

• PDF/A-2,3 relaxes this to being optional, but if present the CharSet must be accurate.

So when the new primitive becomes available I’ll adjust coding in pdfx.sty to:

* include the CharSet when building PDF/A-1b

* omit the CharSet when building PDF/A-2b or PDF/A-3b (and u flavours)

That should satisfy these rules.

It then must be documented that if validation due to an incomplete CharSet occurs with PDF/A-1

the author should upgrade to PDF/A-2 to avoid having the bad CharSet.

But that error should not occur, unless the validator is being more picky than required.

All I need is the name of the new primitive, and which values will correspond to include/exclude,

to be able to write this new (La)TeX coding, by testing for the csname .

This will allow pdfx.sty to support this for TeXLive 2019.

Regards,
Reinhard

--
------------------------------------------------------------------
Reinhard Kotucha Phone: +49-511-3373112
Marschnerstr. 25
D-30167 Hannover mailto:reinhard.kotucha@web.de
—————————————————————————————————