Sarah Groß

> seems related to: #486 That PR only adds parsing support, writing support is a different story and I just added #561 so we can keep track of this.

Was this ever resolved? Should we look at this or not?

@brawer seeing you were recently active - any update on this?

See https://github.com/opentypejs/opentype.js/issues/627#issuecomment-1773311283

Closing this after 3 years of inactivity

We are meanwhile supporting format 14 (via #581) as well as format/encoding 0 for platform 1 (via #634), which the issue was originally about. The provided example `BRUSHSTP.ttf` will load...

Format 13 will be supported via #647, which will close this issue. As discussed before, it's not worth the time to support obscure formats that will probably never be encountered...

> Are there still plans to implement this fix? This bug caused a lot of confusion until I found out about this issue. It took only 5 years, but I...

Variable font rendering has been implemented via #699, so this is now possible. See the new `font.variation` API description in the [README](https://github.com/opentypejs/opentype.js?tab=readme-ov-file#the-fontvariation-object-variationmanager), especially [Font.variation.getTransform()](https://github.com/opentypejs/opentype.js?tab=readme-ov-file#fontvariationprocessgettransform#:~:text=Font.variation.process.getTransform()) if you want the outlines of...

@ILOVEPIE I only resolved merge conflicts in .js.map files that will be re-generated anyway, but therefore my review does not count towards allowing the merge because I'm technically the last...