Skip to content

Fix issue with PDF parser throwing unexpected token errors

Nathanael Krauße requested to merge tanolino/cairo:tanolino-master-patch-40383 into master

Text formed after /FontName /%s+%s created names like /FontName /59?><4+Arial-BoldMT some of those are considered invalid character. It also seem to only happen in combination with images and URI. I tested with MSCV 14 (2015 Express) and MSVC 14.2 (2019).

Invalid character seem to not work with Adobe Reader or qpdf but other reader like the Firefox built in reader can tolerate such issues.

Also I don't think this is an elegant solution but it works for those who encounter the issue.

Merge request reports