opengraphica

Much of the existing logic in these components relies on the `parsedValue` prop changing, which can only be updated on emit. It was necessary in order to keep the selection...

First screenshot is using HTML + CSS in Firefox. Second screenshot is using opentype.js glyph draw function and offsetting the Y for each glyph by offsetHeight. I would like to...

> Nobody contributing or reviewing has really drained my motivation to provide more of my time. Usually maintainers on a project do code reviews. Are you expecting community members to...

After inspecting the code, it seems the vmtx/vhea table is not parsed, and thus this feature is not supported. If it's easy enough I'll open a PR for it.

Master branch works the same, like I said parsing vmtx/vhea will be the solution to this problem.

> We'll look into it, probably for version 2.1.0 as we need to get 2.0.0 out quick. This is a very simple change; parse some tables, expose a few variables....

Did 1.3.4 not support variable fonts? To be honest, I do not like this API. The user always retrieves a glyph from a font object, so logically the glyph should...

Additionally, font is considered optional in `getPath()`, which is the function that retrieves the variation in the first place, no? The API is inconsistent. https://github.com/opentypejs/opentype.js/blob/ab95cea6560b9a8ba20f6290603e7e6e8f4bd02b/src/glyph.mjs#L148 https://github.com/opentypejs/opentype.js/blob/ab95cea6560b9a8ba20f6290603e7e6e8f4bd02b/src/glyph.mjs#L157

> PS: Genereally instead of "a && a.b" .. i'd just do "a?.b" I agree, just following the existing code convention. > Glyph objects do not have a reference back...

Ok, but at the same time the library doesn't currently support writing to the hvar table anyways. Even if two fonts share the same glyph, can't make use of that...