Created attachment 113098 [details] Fix bug font wrong codepage In MS specification TTF in https://www.microsoft.com/typography/tt/ttf_spec/ttch02.doc clean write: table 'hmtx(horizontal metrics)' is required. And in https://www.microsoft.com/typography/tt/ttf_spec/ttch03.doc this required too. But font without hmtx exist (mostly as embedded font in pdf). I have that example pdf - on Windows they open without any problems but in linux - font is adsent. I create bug in "FreeType Project" https://savannah.nongnu.org/bugs/index.php?44169 , but after (if it will be fixed) pdf anyway not opening correct. With that simply patch (and patched freetype2 from https://savannah.nongnu.org/bugs/index.php?44169) pdf be opening correctly and font visible and readable. Thet bug with buggy pdf exist in MuPDF http://bugs.ghostscript.com/show_bug.cgi?id=695690
Please attach such a pdf file
Created attachment 113133 [details] bug pdf with wrong font
The needed freetype commit has still not happened right? Can you ping us in this bug once freetype can render that font?
Yes, ofcourse, but fix in freetype for render font without problem very simple - only 1 string comment and 1 string add. That ready patch attached to bug https://savannah.nongnu.org/bugs/index.php?44169
In freetype bug reopened from https://savannah.nongnu.org/bugs/?44169 to whishlist https://savannah.nongnu.org/bugs/?44184
Freetype commit for fix that happened (and bee in 2.6.0 version of reetype): http://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/?id=92359bd8851448ba40167affdf5663659a7b28f0 with that patch fonts is visible, but codepage is wrong. With attached patch for "Fix bug font wrong codepage" all displayed OK. And if i copy wrong displayed chars and words in clipboard and past to another place - i view readable text.
That freetype commit fix problem in mupdf http://bugs.ghostscript.com/show_bug.cgi?id=695690 In poppler font viewed, but displayed codepage wrong.
Pushed
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.