The FreeType Project - Bugs: bug #44241, Font with overlaping paths...
You are not allowed to post comments on this tracker with your current authentication level.
bug #44241: Font with overlaping paths autohinted into nothing.
Submitter: | bungeman <bungeman> | ||
Submitted: | Fri 13 Feb 2015 08:28:03 PM UTC | ||
Severity: | 3 - Normal | Item Group: | None |
Status: | Fixed | Privacy: | Public |
Assigned to: | wl | Open/Closed: | Closed |
Planned Release: | 2.6.0 |
Tue 03 Mar 2015 10:26:02 AM UTC, comment #2: |
Werner LEMBERG <wl> |
Fri 20 Feb 2015 06:51:53 PM UTC, comment #1: I think I know what is happening now. I went and fixed the issues with the font outlines overlapping, and generally fixed things up, but the issue persisted. That's when I noticed that this font is being subset by some means which, instead of removing characters and glyphs, is instead setting unused glyphs to trivial paths. So in this font A-Z and b-z and a number of others are all 'empty glyphs', where by empty I mean 'have two points, one on top of the other'.
|
bungeman <bungeman> |
Fri 13 Feb 2015 08:28:03 PM UTC, original submission:
This was an issue originally reported against Chromium, see https://crbug.com/394373 . The webfont in question there can currently be found at http://www.ebooksystem.net/downloads/tuned/Tuned/Fonts/NumbersRedbird.ttf .
|
bungeman <bungeman> |
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 4 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2015-03-03 | wl | Status | None | Fixed | |
Assigned to | None | wl | |||
Open/Closed | Open | Closed | |||
Planned Release | None | 2.6.0 |
Powered by Savane 3.13-02a9.
Corresponding source code
Thanks for the report; this is now fixed in git.
This font lies, as you've correctly noted, but it was easy to work around this very problem by rejecting glyphs that have less than three points.