I think the earlier Q commit is really the culprit here. The bisected
change modified the error returned by the other modules when rejecting
data, so I think that change just allowed the code to get this far.
Looking into getting the fuzzer going with MemorySanitizer to catch this
sort of issue, b
On Mon, Dec 13, 2021 at 12:17 PM Chris Liddell
wrote:
> In the case of a font with CFF outlines, the "glyph index" should still
be mapped through the CFF Charset.
The native CFF charset as well as the sfnt cmap's are supposed to be
listed in FT_Face->charmapS. Do you want to activate the native o
Hello Werner and all,
We've encountered a problem with our use of Freetype in mupdf.
We have a PDF with an embedded OTTO/CFF font that is used as a CIDFont
in the PDF.
Now, the way CIDFonts work in PDF is that the character code is mapped
through the PDF CMap, to get a "glyph index".
In the cas
