Re: pdf inclusion bug
Hartmut Henkel <[email protected]> Sat, 30 Mar 2019 00:18:07 +0100 (CET)
| Newsgroups | gmane.comp.tex.pdftex |
|---|---|
| Message-ID | <[email protected]> |
On Fri, 29 Mar 2019, Ross Moore wrote: > Hi again, > just adding an extra comment. > > On 30 Mar 2019, at 8:51 am, Ross Moore <[email protected]> wrote: > > > and only the "C" will be visible in b.pdf. And if you look > into b.pdf, the included font contains "/CharSet (//A /B > /C)", which is obviously wrong. > > > It’s actually a bit worse than this. > The font subset’s Encoding vector has been rewritten: > > /Encoding 256 array > 0 1 255 {1 index exch /.notdef put} for > dup 67 /C put > readonly def > > which is why only the C is found. > > > If the new primitive is used: \pdfomitcharset=1 > the suspect /CharSet is no longer written, > but the problem remains that /A and /B are not found. when a.pdf is edited so that (/A/B/C) are compact without spaces, all seems to be fine. And (/A/B/C ) gives an error with letter C. Seems it's a poppler issue, called from pdftoepdf.cc, might happen in line 434: ...fontdesc->dictLookup("CharSet", &charset)... Regards, Hartmut