Default UPM for OTFs is 1000.
Custom Unicode values are a pro feature. I’ll add that to the Glyphs Mini page. Anything else you feel should be noted there?
How’s it a pro feature if it works in Glyphs Mini? Or do you mean to say “Custom Unicode values with custom meaningful glyph names”? Because just assigning “uniE123” works correctly as expected in Glyphs Mini, so saying that it’s a pro feature would misinform potential users.
You can upgrade to the full version and get the Mini price as a discount.
Thank you, I’ll keep this in mind. While you make fine software that in its full version has been a pleasure to use, I can’t afford 300 bucks for a rather niche piece of software. If Glyphs Mini didn’t exist, I’d look for other alternatives, or (sadly) revert to having icons as images.
You can send me the file if you want me to tell what’s wrong.
Thank you kindly, will take you up on this offer if my manual reconstruction of everything in Glyphs Mini still ends up with problems.
The grey info box does show the Unicode value if the glyph in question has one. The glyph name “iconClockThreeThirty” is not linked to a Unicode value, that’s why it doesn’t show, but standard glyph names are.
(removed part of the original reply; I misread mekkablue’s response)
The glyph in question does have a unicode value, because I set it, verified it, and am using the resulting font.
I also did verify that calling a glyph “uniE123” in Glyphs Mini correctly displays E123 in the top-right corner of grey box, and subsequently renaming the glyph to “iconFooBar” removes that value. This is not how things worked in the trial version of Glyphs. So it sounds like there’s incompatibility between the two versions, both in terms of features and in terms of the .glyphs file format.
I did some more debugging, and now understand exactly what’s happening. Putting all the details here in case somebody else gets into similar trouble.
you’re building an icon font, possibly because you read this article: http://blog.fogcreek.com/trello-uses-an-icon-font-and-so-can-you/
you have a .glyphs file generated by the free trial version of Glyphs
you have a bunch of glyphs in the private use area of the Unicode space, with meaningful names assigned to each glyph after you’ve set their unicode values
your font worked just fine, perhaps you used fontsquirrel to convert to the web-usable formats, but…
… your trial expired and you decided to buy Glyphs Mini
you open your .glyphs file in Glyphs Mini, export as .otf, try to upload to fontsquirrel, and get a message saying “The font ‘your-font.otf’ is corrupt and cannot be converted”
Due to (I imagine) incompatibility between Glyphs and Glyphs Mini, unicode values set by naming a glyph “uniE123” and then naming it “iconSomeMeaningfulName” do not carry through to Glyphs Mini. So you’re effectively exporting an empty font, and fontsquirrel unhelpfully tells you that it’s corrupt.
As a simple test, either rename one of your existing glyphs to “uniE000” or add a new glyph and name it that. Export .otf and upload to fontsquirrel again. The error message will not appear. Go through the steps, download your webfontkit archive, and open your-font-demo.html. Go to the “Glyphs & Languages” tab, and you’ll see your lonely new/renamed glyph there.
So, your unicode assignments are gone. Recreate them by naming all your glyphs “uniXXXX”, and you’re back in business. And no, I suspect you won’t be able to have custom glyph names and unicode assignment at the same time in Glyphs Mini. According to the thread above, it almost sounds that it works in Glyphs by fluke rather than by design.
Thanks for your help with figuring this out, mekkablue.