Re: [NTG-pdftex] Incomplete CharSet causes failure with PDF/A validation

Hi Karl,

On 28 Jan 2019, at 9:35 am, Karl Berry wrote:

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

\pdfincludecharset=0 (default) -> no /CharSet \pdfincludecharset=1 -> /CharSet included

Just now committed to pdftex and TL repos.

Great. Thanks for this.

Hope it works out. -k

The only thing is that you might want to consider swapping the default, for backwards compatibility reasons - nothing to do with PDF/A. Building CharSets has been the norm for many years. My email from earlier today gives a reason why CharSets can be useful. It’s only when building specifically PDF/A-2, 3 that the validation issue has emerged, and only with some documents and fonts. Now that we have the means to cope, we are unlikely to get complaints. On the other hand, we the developers know that sometimes we could be building PDFs that contain a small defect; with fixing it a task for the future. Opinions? Cheers Ross