MeshWriter 1.1.1 is out, with more complete glyph coverage and (bonus!) no file size increase. The glyphs are now enumerated for MeshWriter; see the README.
The selection is extensive in both Comic and Helvetica. More limited in Jura and HirukoPro but still a complete ASCII set.
The file “meshwriter.min.js” is still under 120K.
I may fill in some corners but I don’t plan to do any large expansions.
Yeah, seems legit to me to put var in front of the variables.
I have no clue how it was working, but before further investigations, question is: should no var tag been allowed in the first place ? @Deltakosh
@temrysh, sorry for your difficulty. Can you provide more detail. What precisely are you doing and what step is not yielding the desired results?
Background: Font file formats vary. It is possible that there is some incompatibility between the font file you are trying to convert and the MeshWriter utility. Nonetheless, let’s start at the basics.
Thank you for getting back that fast and for supporting your great tool.
So I have followed the steps described in meshwriter-font with my custom .ttf font and stumbled upon issue that was already opened on github. The output only cover the numbers 0123456789.
To narrate for other readers: ‘config.js’ (from the github repo) must be included in the source directory for complete font conversion. It holds the glyph conversion lists, by font name. If it is absent, the utility only converts the numerals, mystifying programmers.
Yes. Thank you for bringing that to my attention. I built all that stuff around a program I abandoned years ago, but that’s where I hosted the code modules. I left that server running for the sole reason of hosting MeshWriter code but I guess the cert finally expired.
I believe the code modules can be hosted directly on github. Old playground pointers must all change though.