We try to keep the type1 code in sync between dvips and pdftex, so it's
sad that the results differ. Clearly something is awry :(. --thanks, karl.
Yes, but the font inclusion is done by Ghostscript surely?
So we need to be up-to-date with what those guys are doing.
BTW, Ghostscript v.9.19 has a good new /Ext_Metadata pdfmark construction,
which I���m exploiting to get valid PDF/As with complex metadata packets.
So far it only works with ascii-encode text in the extra metadata fields.
This needs to be fixed to match what pdfx can do when using pdfTeX as engine.
Reinhard said:
"sufficient to type \char 32 somewhere in your document and the /space
should appear within the font subset.���
It does indeed with the DavidCLM font, but that���s not enough for PDF/A validation
of my test document. It still needs /quotesingle .
And it doesn���t explain why Ghostscript has included /space with no extra effort
from the document author. I suggest that pdfTeX do this too!!!