pdf.js/issue6692.pdf.link at 5feb2a253fc432a817b71c2f9cd5a7051b64e255 - pdf.js - Gitea on kemo

Sakurai/pdf.js

Jonas Jenwald 995e1a45b8 Ensure that Lexer_getName does not fail if a Name contains in invalid usage of the NUMBER SIGN (#) (issue 6692)

*This is a regression from PR 3424.*

The PDF file in the referenced issue is using `Type3` fonts. In one of those, the `/CharProcs` dictionary contains an entry with the name `/#`. Before the changes to `Lexer_getName` in PR 3424, we were allowing certain invalid `Name` patterns containing the NUMBER SIGN (#).

It's unfortunate that this has been broken for close to two and a half years before the bug surfaced, but it should at least indicate that this is not a widespread issue.

Fixes 6692.

2015-11-28 11:59:09 +01:00

2 lines

93 B

SYSTEMD

Raw Blame History

http://web.archive.org/web/20151126121615/http://www.inf.ufg.br/~hugoribeiro/OSPs/osp-im.pdf