The FreeType Project - Bugs: bug #56580, Type 1: Problem with (badly...
You are not allowed to post comments on this tracker with your current authentication level.
bug #56580: Type 1: Problem with (badly formed) SEAC glyph
Submitter: | Chris Liddell <chrisl> | ||
Submitted: | Thu 04 Jul 2019 11:14:18 AM UTC | ||
Severity: | 3 - Normal | Item Group: | None |
Status: | Fixed | Privacy: | Public |
Assigned to: | wl | Open/Closed: | Closed |
Planned Release: | 2.10.2 |
Thu 04 Jul 2019 12:31:14 PM UTC, comment #1: |
Werner LEMBERG <wl> |
Thu 04 Jul 2019 11:14:18 AM UTC, original submission:
The attached Type 1 font has a ligature glyph ('fl', character code 175 in the included encoding) formed by using a SEAC glyph (obviously contrary to the intent of SEACs!). According to spec, the (h)sbw values in the "accented character" must be the same as the base glyph, but clearly other consumers give priority to the accented char values over the base char (whilst freetype currently does the opposite).
|
Chris Liddell <chrisl> |
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 5 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2019-07-04 | wl | Status | None | Fixed | |
Assigned to | None | wl | |||
Open/Closed | Open | Closed | |||
Planned Release | None | 2.10.2 | |||
2019-07-04 | chrisl | Attached File | - | Added FuturaBQ-Light.pfa, #47158 |
Powered by Savane 3.13-d3ae.
Corresponding source code
Patch applied, thanks!