Marnen Laibow-Koser

Any chance of releasing this?

@SuperSandro2000 I don’t understand the issue here or what you’d like me to do about it. Can you be a little clearer?

What makes it hard to update this way? How would putting the file under assets help? (I hardly ever use package managers for fonts, so I don’t understand the problem...

I believe those instructions are what got me to put the files where they are today. I’ll look again, though.

There were not two places to put files the last time I made a release. Perhaps this has changed.

Cool, thanks! Let me see how these look and see about getting the OpenType features in there.

Also, please make sure to write a description for future pull requests.

BTW, if you want to merge the feature file yourself, you'd do it with the File | Merge Feature Info command in FontForge. Then you can update the pull request...

Also, it looks like while FontForge did a decent job, it created characters (at least in the bold weight) with some self-intersecting paths. @charJe Do you want to fix those...

@charJe: > I wouldn't know how to detect which are the problematic characters Did you try Element | Validation? FontForge can even run this automatically when you try to export...