Plumin is a light wrapper around paper.js [1] and my opentype.js library[2], which can parse and write OpenType fonts in pure JavaScript.<p>Plumin is nice to build fonts from scratch. If you're interested in taking an <i>existing</i> font and manipulating its shape or metrics, consider using opentype.js directly.<p>[1] <a href="http://paperjs.org/" rel="nofollow">http://paperjs.org/</a><p>[2] <a href="https://github.com/nodebox/opentype.js" rel="nofollow">https://github.com/nodebox/opentype.js</a>
What is the use case for something like this? I think it's really, really cool that this is possible, but I'm having trouble coming up with a scenario in which I'd actually want to do this.
Here is the introduction blog post: <a href="https://www.kickstarter.com/projects/599698621/prototypo-streamlining-font-creation/posts/1132615" rel="nofollow">https://www.kickstarter.com/projects/599698621/prototypo-str...</a>
Web Font licensing is such a completely painful mess that I would wish/hope/love if this software came with a license that constrains the terms of use on any fonts produced with it to Creative Commons, or (what the hell) GPL.