The FreeType Project - Bugs: bug #52098, Certain SFNT fonts can no longer...
You are not allowed to post comments on this tracker with your current authentication level.
bug #52098: Certain SFNT fonts can no longer be opened by FreeType 2.8.1
Submitter: | kinodont <kinodont> | ||
Submitted: | Sat 23 Sep 2017 09:07:30 AM UTC | ||
Severity: | 3 - Normal | Item Group: | Incorrect behaviour |
Status: | Invalid | Privacy: | Public |
Assigned to: | wl | Open/Closed: | Closed |
Planned Release: | None |
Sat 23 Sep 2017 12:10:03 PM UTC, comment #1: |
Werner LEMBERG <wl> |
Sat 23 Sep 2017 09:07:30 AM UTC, original submission:
The commit
|
kinodont <kinodont> |
No files currently attached
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 3 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2017-09-23 | wl | Status | None | Invalid | |
Assigned to | None | wl | |||
Open/Closed | Open | Closed |
Powered by Savane 3.13-4b48.
Corresponding source code
The font in question is invalid – it is a bitmap-only font (containing a 13ppem strike) that incorrectly sets the font's upem value to 13 also; I've added a quickly fixed font version to the original wine bug report.