[4 mod] Technical: reverse-mapped 'μΔfifl' (detected by warning in FontForge)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Font Family |
Incomplete
|
Medium
|
Unassigned | ||
fontforge (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
The following warnings are shown when opening the individual font .ttf files in FontForge (see screenshot):
The following table(s) in the font have been ignored by FontForge
Ignoring 'LTSH' linear threshold table
Ignoring 'VDMX' vertical device metrics table
Ignoring 'hdmx' horizontal device metrics table
This font contains both a 'kern' table and a 'GPOS' table.
The 'kern' table will only be read if there is no 'kern' feature in 'GPOS'.
The glyph named mu is mapped to U+00B5.
But its name indicates it should be mapped to U+03BC.
The glyph named Delta is mapped to U+2206.
But its name indicates it should be mapped to U+0394.
The glyph named fi is mapped to U+F001.
But its name indicates it should be mapped to U+FB01.
The glyph named fl is mapped to U+F002.
But its name indicates it should be mapped to U+FB02.
description: | updated |
Changed in ubuntu-font-family: | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in ubuntu-font-family: | |
milestone: | none → 0.69 |
summary: |
- Technical: 'μΔfifl' aliasing highlighted as warning in FontForge + Technical: reverse-mapped 'μΔfifl' (detected by warning in FontForge) |
Changed in ubuntu-font-family: | |
status: | Triaged → Confirmed |
importance: | Medium → Low |
Changed in ubuntu-font-family: | |
importance: | Low → Medium |
Changed in ubuntu-font-family: | |
status: | Confirmed → Triaged |
milestone: | 0.69 → 1.00 |
summary: |
- Technical: reverse-mapped 'μΔfifl' (detected by warning in FontForge) + [4 mod] Technical: reverse-mapped 'μΔfifl' (detected by warning in + FontForge) |
Breaking those down:
(1)-(3) are about tables that Fontforge does not yet handle.
(4) is I presumed duplicated for compatibility; we should file this separately and look into it
(5)-(8) are coherency sanity checks, and we should probably investigate those