ntg-pdftex

Download

ntg-pdftex@ntg.nl

May 2018

4 participants
2 discussions

Incomplete CharSet causes failure with PDF/A validation
by Ross Moore 29 Jan '19

29 Jan '19

Hi all. I believe there is a problem with the way pdfTeX constructs the CharSet for a subsetted font. Not all fonts are affected, and it only shows up when attempting to validate for PDF/A. I’ve mentioned the problem to Thanh and others, but as there’s been nothing done, I’ll bring it up here, with an example that cannot be worked-around. Attached are two PDF/A documents, using Hebrew text. The main font is the “David” style font from the culmus package: DavidCLM-Medium hebart-david.pdf — produced by pdfTeX hebart-gs.pdf — produced using dvips+GS hebart-david fails PDF/A validation in one aspect only (see image): “CharSet in subset font is incomplete (font contains glyphs that are not listed)"

8 43

\expanded
by Joseph Wright 17 May '18

17 May '18

Hello all, As recently raised on the TeX Live mailing list, the LaTeX team feel that the \expanded primitive, suggested for pdfTeX 1.50 around 10 years ago, would be a useful addition to TeX engines. (It is present in LuaTeX.) Attached is a patch which provides the primitive itself (based on the LuaTeX version), an entry for the pdfTeX manual, and some tests. (This is based on the version in https://github.com/josephwright/texlive-source/tree/expanded, slightly adjusted as the tests there also cover other primitives to support XeTeX additions.) I have chosen the pdfTeX manual as the 'home' for documenting behaviour as the idea comes from pdfTeX and as this is usually where 'utility' primitives have been documented. A similar request has been made for XeTeX (for the code part), whilst the (u)pTeX developers already have a Git branch which would add this functionality. We (the team) do hope that general agreement can be reached to make this available in the main engines (pdfTeX, XeTeX, LuaTeX, e-pTeX, e-upTeX) for TL'19. Regards, Joseph

4 17