The FreeType Project - Bugs: bug #43380, Add flag to make FT_Load_Glyph...
You are not allowed to post comments on this tracker with your current authentication level.
bug #43380: Add flag to make FT_Load_Glyph obey gasp table data
Submitter: | Werner LEMBERG <wl> | ||
Submitted: | Wed 08 Oct 2014 06:50:52 AM UTC | ||
Severity: | 3 - Normal | Item Group: | Wishlist |
Status: | Postponed | Privacy: | Public |
Assigned to: | None | Open/Closed: | Open |
Planned Release: | None |
Sun 09 Aug 2020 08:20:00 AM UTC, comment #1: |
- <_194785> |
Wed 08 Oct 2014 06:50:52 AM UTC, original submission:
This has been requested on the list a few times, and it should actually be the default for native hinting of TrueType fonts. |
Werner LEMBERG <wl>![]() |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
Carbon-Copy List
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.
Follows 1 latest change.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2014-10-08 | wl | Item Group | None | ![]() |
Wishlist |
This is quite important. No Microsoft standard TrueType renderer will anti-alias a font that specifies bilevel rendering, and no Microsoft ClearType renderer will do vertical anti-aliasing on a font that specifies no anti-aliasing vertically. I see many cringe renders from applications using FreeType incorrectly. And v38 should be permanently disabled until the subpixel renderer with no vertical anti-aliasing is finished.