You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 28, 2019. It is now read-only.
Other PDF viewers can open the file correctly, so this may be a problem with muPDF. On the other hand, muPDF has also been fine with opening other PDFs with embedded fonts in the past, so I think the problem is not with only muPDF. I suspect that there is some protocol that this library is not following entirely and that other PDF viewers have managed to correct for these errors in a way that muPDF hasn't.
The text was updated successfully, but these errors were encountered:
This may be the same issue as #44, but it's worth pointing out that in my cases the problem is specific to muPDF and does not happen using evince or inkscape, etc.
I haven't solved this problem--for now, I've only avoided it by not using custom fonts, but that's not a solution at all, only running away from the problem...
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When an external font is embedded in the PDF, it cannot be opened in muPDF correctly:


Expected output:
muPDF also logs the following:
The code to embed the fonts is as follows:
Here is the PDF in question:
hyperschedule-color.pdf
Other PDF viewers can open the file correctly, so this may be a problem with muPDF. On the other hand, muPDF has also been fine with opening other PDFs with embedded fonts in the past, so I think the problem is not with only muPDF. I suspect that there is some protocol that this library is not following entirely and that other PDF viewers have managed to correct for these errors in a way that muPDF hasn't.
The text was updated successfully, but these errors were encountered: