Alternative to opentype.js

[photopea]

This is not a forum to advertise alternative projects.

[Jolg42]

Hi!

Nice :) I just added it to the awesome-typography list (You can check this list for OpenType related libraries!).

If you want to check other alternatives to OpenType.js:

• https://github.com/devongovett/fontkit An advanced font engine for Node and the browser
• https://github.com/bramstein/opentype An OpenType, TrueType, WOFF, and WOFF2 parser in JavaScript

Both are OpenType parsers (not writers).

I searched for your issues, but maybe you used another account for them (I can't find any)?

By the way if you have a .zip with fonts working / not working it would be helpful for testing! 😉

[fdb]

Hi @photopea, always good to see some alternative implementations! As @Jolg42 mentioned, there are some other high-quality implementations as well. I'll look at your implementation to see if there are any speed gains we can port over to OpenType.js as well.

If there are specific issues you'd like to see solved, please take them up with me (again). I've been completing my PhD in the last year(s) so OpenType.js was not always my nr 1 priority 😉

[photopea]

The most important problem was this one: #117 . I was waiting more than a year, but nobody fixed it.
Here you can see the same 100 glyphs rendered with opentype and Typr

[photopea]

I was testin Typr.js with fontsquirrel fonts, which I accessed through their API: https://www.fontsquirrel.com/blog/2010/12/the-font-squirrel-api

[fdb]

Looking at that issue, could you pinpoint what your parser is doing differently? I'd love to fix this.

Thanks for the link to the fontsquirrel API. Didn't know about that one.

[photopea]

When there is a CFF operator 14 (endchar) and stack length is 4, the "seac" (standard encoding accented character) command should be performed. Opentype does nothing. See http://wwwimages.adobe.com/content/dam/Adobe/en/devnet/font/pdfs/5177.Type2.pdf page 35.

[fdb]

Thanks! I saw that was an issue with e.g. character index 202, which has the code [98, 146, 154, 236, 247, 89, 14] which sets up a stack with five numbers but then only does endchar. I was scratching my head on what that should do.

[Jolg42]

I just did a dump from the API, all fonts are available here https://github.com/Jolg42/FontSquirrel-Fonts

[photopea]

Nice :) but I think it will be outdated like tomorrow :D

[Jolg42]

Maybe…! But I don't think that the fonts are updated on regular basis.
They add more new fonts than they update the old ones no?
Having a dump is just easier for testing (even if outdated).

[behdad]

Thanks! I saw that was an issue with e.g. character index 202, which has the code [98, 146, 154, 236, 247, 89, 14] which sets up a stack with five numbers but then only does endchar. I was scratching my head on what that should do.

What was the solution that worked? Early termination?

[fdb]

@behdad As @photopea mentioned, it should be interpreted as seac. We don't have code for this, I'll look into it.

[photopea]

Can you please also make sure, that you can render the glyph 190 in this font? I am having problems with it. https://ufile.io/0a748 BTW it really helped me when I looked at the code of FreeType library.

[ivarref]

Hi.

I wrote opentype.clj, a small wrapper for a subset of opentype.js. It runs on the Java Virtual Machine (JVM) and should be easy to interface using the Clojure programming language. Hope it's of good use to someone!

[Jolg42]

Hi @photopea It's been a while since your last message and it looks like your ufile.io/0a748 is 404. Do you still have it somewhere?
The best would be to upload it with GitHub (See https://help.github.com/articles/file-attachments-on-issues-and-pull-requests/ basically just Drag & Drop)

[Jolg42]

By the way @ivarref good job!
I'll add it to https://github.com/Jolg42/awesome-typography soon and also adding to OpenType.js' README would make sense.

[photopea]

@Jolg42 I don't remember what was that file. Why do you still need it?

[Jolg42]

@photopea I just wanted to try it again :)
By the way, I don't remember exactly but when you created Typr.js it was partly because of an issue with the parsing of some glyphs I think. Do you know if this issue was fixed in OpenType.js?

[photopea]

@Jolg42 Yes, I did it because some issues here were not fixed. It seemed to me like the author made opentype.js just for fun and did not plan to do updates.

I am the kind of programmer that prefers writing his own code instead of deciphering foreign code :D If I find a bug in Typr.js now, I can fix it right away myself. I made it because I actually need it in practice at www.Photopea.com . It is used by thousands of people every day and bugs have been found and fixed very quickly. In general, I trust Typr.js much more than opentype.js now . It is much more advanced, e.g. it even supports Color Fonts :) https://blog.photopea.com/color-fonts-in-photopea.html while being much smaller, faster and RAM-friendlier than opentype.js

[Connum]

The issue discussed above was fixed via #633. Closing.

[CNV1018]

hi, can I check if it supports TTC file? can it display all characters in TTC files? Currently, I'm using opentype.js. It works well with TTF and OTF, but it doesn't support TTC file. I'm currently looking for other alternatives.

[photopea]

This is not a forum to advertise alternative projects.

[CNV1018]

That's great!! I'm working on a .NET Core project with React for the front end. Can this tool be implemented into the project?