Replace pdf.ttf with sharp2.ttf, keep name the same #220
Conversation
As discussed at length in issue tesseract-ocr#182, the existing pdf.ttf causes difficulties for certain PDF viewers, in part because the old file had zero advance width. With testing, sharp2.ttf seems to be the best available compromise, although it's not perfect and causes some visual difficulties in Evince. It does seem to fix Kindle and OS X Preview.
|
Did someone test that there is no regression in pdf output with Adobe Acrobat |
|
I have checked: Acrobat XI, Google Chrome PDF Viewer, OS X Preview, Safari PDF viewer; all on El Capitan. |
|
See #182 for other tests people did with sharp2.ttf |
|
Chromium and Adobe Reader on Linux are fine. I have reports that Ghostscipt and friends are okay. I should probably double check Android right now. |
|
Latest stock Android (Marshmallow) is fine. |
|
Okay, but I think you should also test this with an image that has more than two words... |
Replace pdf.ttf with sharp2.ttf, keep name the same
|
Using
|
|
I've been tracking the Firefox offset problem in mozilla/pdf.js#6509 and it looks like it has gotten a little worse with this change. (I take that back; your screenshot is worse but mine looks the same. Maybe you are using a different zoom level in Firefox or something) |
Replace pdf.ttf with sharp2.ttf, keep name the same
Replace pdf.ttf with sharp2.ttf, keep name the same
Replace pdf.ttf with sharp2.ttf, keep name the same
Replace pdf.ttf with sharp2.ttf, keep name the same
As discussed at length in issue #182, the existing pdf.ttf causes difficulties
for certain PDF viewers, in part because the old file had zero advance width.
With testing, sharp2.ttf seems to be the best available compromise, although
it's not perfect and causes some visual difficulties in Evince. It does
seem to fix Kindle and OS X Preview.