Khaled Hosny
Khaled Hosny
AFDKO’s tx can convert CFF2 to CFF, may be try it to see what it is doing in these situations?
I use `tx` also to generate a CFF table, then I graft it back to the TTFont. It works, but I don’t know what magic is happening behind the scenes.
By default anchor data are written to font features (because FontForge offers more control to anchor lookups that possible with UFO anchors), but if you don’t care about lookups and...
`fontmake` already has `--flatten-components` option.
The font’s `cmap` table maps PUA code points to alternate glyphs. This is an outdated, and IMO wrong, practice. Some PDF producers like XeTeX here will use the `cmap` mappings...
Seeing https://github.com/rsms/inter/issues/541, it is seems unlikely that PUA mappings are going away.
The proper code points are already mapped to the default glyphs, and it is not possible to map the same code point to different glyphs in `cmap`.
It should be just the same order as in the feature file, isn’t it?
> but I expect that in future it may be that text engines ignore the notdef glyphs in fonts to get better uniformity. That is already the case in Firefox...
My analysis in the above Microsoft Typography issue, which was conformed by Peter Constable, is that Microsoft implementation is swapping `displayOperatorMinHeight` and `delimitedSubFormulaMinHeight`. This seems to be affecting Cambria Math...