reassign 709253 libpoppler19 retitle 709253 make unparseable glyph names a slient warning and not error thanks
On Mi, 04 Sep 2013, Vincent Lefevre wrote: > On 2013-09-04 16:24:57 +0900, Norbert Preining wrote: > > No, I still disagree. It is not a PDF syntax error. iT is a mistreatment > > of poppler. Only because it cannot parse a charname does not mean that > > it is invalid, I guess. > > I've searched with Google, and > > https://www.allegro.cc/forums/thread/597719/771190#target > > seems to confirm that this is not against the PDF spec. I suggest to > reassign the bug to libpoppler19. Done so. > If this is really a PDF syntax error, I think that this should be > explained in the poppler source (with a reference to the section > of the PDF spec forbidding this). I don't think that this is a PDF syntax error. Glyph names can have arbitrary names, in principle. > Otherwise, an error shouldn't be issued by default (informative output > would be OK, but only in some form of debug mode). Agreed. Norbert ------------------------------------------------------------------------ PREINING, Norbert http://www.preining.info JAIST, Japan TeX Live & Debian Developer DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 ------------------------------------------------------------------------ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
