The FreeType Project - Bugs: bug #38662, True Type hinting issue probably...
You are not allowed to post comments on this tracker with your current authentication level.
bug #38662: True Type hinting issue probably introduced in 2.4.x (it's fine in 2.3.11)
Submitter: | None | ||
Submitted: | Thu 04 Apr 2013 06:46:15 PM UTC | ||
Severity: | 3 - Normal | Item Group: | Incorrect behaviour |
Status: | Invalid | Privacy: | Public |
Assigned to: | wl | Open/Closed: | Closed |
Planned Release: | None |
Jump to the original submission
Wed 15 May 2013 10:28:45 AM UTC, comment #6: |
Werner LEMBERG <wl> |
Tue 09 Apr 2013 07:07:01 AM UTC, comment #5: Your Win XP snapshot confuses me a lot since the B/W rendering result completely differs from what FreeType produces; normally the differences are just a few pixels, if at all. My first thought was that probably the new subpixel hinting code is the culprit, but even older FreeType versions produce completely different renderings. I have absolutely no idea what's going on.
|
Werner LEMBERG <wl> |
Mon 08 Apr 2013 06:16:00 PM UTC, comment #4: Hi Werner!
|
Anonymous |
Sat 06 Apr 2013 07:44:33 AM UTC, comment #3: OK, you have compiled FreeType without subpixel support. However, the Windows rendering results in your images are certainly with subpixel rendering. Try to activate subpixel rendering in FreeType, and you get much improved results. But this is something different...
|
Werner LEMBERG <wl> |
Fri 05 Apr 2013 08:24:01 PM UTC, comment #2: Hi Werner,
|
Anonymous |
Thu 04 Apr 2013 08:11:35 PM UTC, comment #1: Please retry with the current git version of FreeType. I don't see the artifacts marked in the image. |
Werner LEMBERG <wl> |
Thu 04 Apr 2013 06:46:15 PM UTC, original submission:
When I upgraded from FreeType 2.3.11 to 2.4.8 and later to 2.4.11 I noticed a significant decrease of font rendering quality. Some fonts are less affected then the others. I think the issue has to do with the hinting algorithms.
|
Anonymous |
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 10 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2013-05-15 | wl | Status | Confirmed | Invalid | |
Open/Closed | Open | Closed | |||
2013-04-09 | wl | Status | Need Info | Confirmed | |
2013-04-08 | None | Attached File | - | Added Microgramma-WinXP-NoSmoothing.png, #27811 | |
2013-04-05 | None | Attached File | - | Added Freetype - current version - git.sv.nongnu.org.png, #27781 | |
2013-04-04 | wl | Status | None | Need Info | |
Assigned to | None | wl | |||
2013-04-04 | None | Attached File | - | Added Freetype - 2.3 vs 2.4.png, #27772 | |
Attached File | - | Added microgme.ttf, #27773 | |||
Attached File | - | Added Freetype - 2.4 - Microgramma Issue.png, #27774 |
Powered by Savane 3.13-f8d8.
Corresponding source code
I've now re-examined the `Freetype - 2.3 vs 2.4.png' image. This image shows the rendering of the auto-hinter! 2.3.11 and the current git version of FreeType yield exactly the same rendering results if native hinting (without subpixel support) is used. (There are spacing differences, however, which are unrelated to the very problem.)
I'm closing this issue as invalid. Feel free to add further comments if necessary.