Sarah Groß comments

Results 253 comments of


                                            Sarah Groß

trafficstars

Error parsing some cut font files using 'opentype. parse(...)'

What I can say so far is that `font_13_13.otf` is that it is an old Adobe Type 1 (PostScript) font. Even Adobe itself as [dropped support for those in their...

Error parsing some cut font files using 'opentype. parse(...)'

You can check out this work-in-progress branch for a more forgiving handling of incomplete font files: https://github.com/Connum/opentype.js/tree/WIP/validation-error-handling ![image](https://github.com/opentypejs/opentype.js/assets/13076806/c10f3935-023f-49e8-a44a-13bec13b8a1d) ![image](https://github.com/opentypejs/opentype.js/assets/13076806/b85a773b-60e0-4558-8de0-84f30b79d65b) ![image](https://github.com/opentypejs/opentype.js/assets/13076806/1d5dff9e-171e-4a2f-9fdf-a337a8578d73)

Error parsing some cut font files using 'opentype. parse(...)'

There are probably too many cases of what can go wrong with a font, but with each example provided we can address more places in the code that prevent incomplete...

Error parsing some cut font files using 'opentype. parse(...)'

font_14 seems to be a raw CFF table, but I'm not entirely sure yet. While fontforge manages to open even that, I'm not sure if opentype.js should really support that......

Error parsing some cut font files using 'opentype. parse(...)'

With the latest update to the branch, CFF Type1 will load. It might not be complete, but should be enough to get the glyph paths and some basic meta data....

Error parsing some cut font files using 'opentype. parse(...)'

So I hacked together a solution for loading the PostScript Type1 fonts, here's a proof of concept: ![image](https://github.com/opentypejs/opentype.js/assets/13076806/62beb3ea-1198-4582-a897-21456cadbaa1) However this is not viable as a solution to be integrated into...