pdfjs-dist

8877 Commits

1 Branch

1804 Tags

126 MiB

Commit Graph

Author	SHA1	Message	Date
Jonas Jenwald	c9b6de3b16	Prevent adding invalid values in `CFFDict_setByKey` (bug 1068432) In the font in question, there are a couple of `topDict` entries that have invalid values (`0xF 0xF`, i.e. just eof markers without any actual numbers). This causes the `parseFloatOperand` function, inside `CFFParser_parseDict`, to return `NaN`. Currently we pass this broken font onto the browser, which OTS unsurprisingly rejects. Fixes https://bugzilla.mozilla.org/show_bug.cgi?id=1068432.	9 years ago
Jonas Jenwald	29c4a604af	Split the font_spec.js unit-tests into cff_parser_spec.js and type1_parser_spec.js Re: issue 7261. Given the we have `gulp fonttest`, which tests the `fonts.js` functionality at a higher level, and that we have a lot of font specific reference tests, I'm not convinced that we also need unit-tests for it.	9 years ago

Author

SHA1

Message

Date

Jonas Jenwald

c9b6de3b16

Prevent adding invalid values in `CFFDict_setByKey` (bug 1068432)

In the font in question, there are a couple of `topDict` entries that have invalid values (`0xF 0xF`, i.e. just eof markers without any actual numbers).
This causes the `parseFloatOperand` function, inside `CFFParser_parseDict`, to return `NaN`. Currently we pass this broken font onto the browser, which OTS unsurprisingly rejects.

Fixes https://bugzilla.mozilla.org/show_bug.cgi?id=1068432.

Jonas Jenwald

29c4a604af

Split the font_spec.js unit-tests into cff_parser_spec.js and type1_parser_spec.js

Re: issue 7261.

Given the we have `gulp fonttest`, which tests the `fonts.js` functionality at a higher level, and that we have *a lot* of font specific reference tests, I'm not convinced that we *also* need unit-tests for it.

2 Commits (0be8e72d6fe45a38f49a2b4bcfd12e981d0a3ecc)