View Single Post
Old 09-18-2013, 01:52 AM   #569
kim1406
Connoisseur
kim1406 can load mercury with a pitchforkkim1406 can load mercury with a pitchforkkim1406 can load mercury with a pitchforkkim1406 can load mercury with a pitchforkkim1406 can load mercury with a pitchforkkim1406 can load mercury with a pitchforkkim1406 can load mercury with a pitchforkkim1406 can load mercury with a pitchforkkim1406 can load mercury with a pitchforkkim1406 can load mercury with a pitchforkkim1406 can load mercury with a pitchfork
 
Posts: 59
Karma: 48000
Join Date: Oct 2012
Device: kindle paperwhite
Quote:
Originally Posted by willus View Post
Okay--first off, the converted file should display correctly if you convert using native mode. I'm guessing you didn't actually get native mode turned on because you had text re-flow or OCR turned on (these disable native-mode conversions). Secondly, I didn't understand why k2pdfopt would not render your font (Simplified Arabic) and Sumatra would when they are both based on the MuPDF library, so I did some investigating. It turns out that there are modifications to the MuPDF library specifically for Sumatra that enable it to correctly render MS Windows system fonts when they are not already embedded in the PDF file (the MuPDF library, as downloaded from the MuPDF site, does not do this). So I have incorporated those Sumatra mods into my version of the MuPDF library, and the next release of k2pdfopt will correctly render this font (or any other MS Windows system font which is not directly embedded in the PDF file).
I re-checked again and found out that, when using the gui mode, enabling native pdf, re-flow and OCR turned off, k2pdfopt will output a file without the correct font, but, when using the commands mode (no gui), the output file with be fine with the Arabic font.
kim1406 is offline   Reply With Quote