| Summary: | PDF Text hinting does not work for embedded otf fonts (CID Type 0C), does work for truetype. | ||
|---|---|---|---|
| Product: | [Applications] okular | Reporter: | Jerome <ce0c5679c447a438> |
| Component: | PDF backend | Assignee: | Okular developers <okular-devel> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | normal | CC: | aacid, simonandric5 |
| Priority: | NOR | ||
| Version First Reported In: | 0.18.5 | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
repro pdf
screenshot of rendering issue |
||
|
Description
Jerome
2014-05-20 01:42:01 UTC
Created attachment 86720 [details]
repro pdf
Created attachment 86721 [details]
screenshot of rendering issue
We don't do rendering of pdf, poppler does, pelase report this upstream at https://bugs.freedesktop.org/ Just updating the developers, that the poppler developers pointed out an issue in freetype's use of a new font hinting engine contributed by Adobe which has a feature called "stem darkening". It appears it's on by default and that the default values interact badly with how poppler does rendering (In a way I do no understand). The freetype developers have confirmed the issue. There is a runtime option for freetype that allows you to turn off stem darkening, and by using it in poppler I was able to eliminate (practically) the problem. I'd like to suggest that the okular developers track this, and would be glad to see it handled in a coming release by whatever form the solution takes. |