Skip to content

Metrics View should just use HarfBuzz #4158

@ctrlcctrlv

Description

@ctrlcctrlv

“My font works in the Metrics View but then looks different in Chrome” is such a common type of bug report. Sometimes the reverse is also complained about.

HarfBuzz is the new Uniscribe. It is the most common shaper out there. I am tired of always having to explain to people...“no, the Metrics View is just an interpretation by one possible shaper...not one anyone actually uses, just fontforge...it is perfectly possible to make fonts in fontforge which fontforge's own shaper cannot interpret, and in fact some of my own fonts fit this bill.”

This would close #3837 if implemented, and probably more issues.

What do you all think? Is it worth taking the time to do this?

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions