-
Check out bug fixes for v1.13.10 and .11
-
Happy April Fools day, everyone! I have re-started work on Glyphr Studio v2, which is exciting (and no joke 😄). But, I also continue to fix bugs for v1… and I will for a while. Here is a quick summary of the bug fixes from the past few releases.
-
One of the most common feature requests I get is to be able to merge two fonts together. v1.13.06 introduced a small feature that may help with merging fonts – even though it’s not a nice workflow or tool that is custom built to merge fonts.
-
Howdy! It’s been a couple months… I’ve been fixing up a few bugs, and adding a few new features. Neat!
-
Okay, so I know there are a few new ‘features’ sprinkled around in here… and I know the last blog post was all about how Version 1 was ‘done’. Ha! The big thing that I’ve realized since v1.13 is that there were a few small features that are still missing that help with the final…
-
A little update to fix some bugs. Also added two updates to help with identifying and fixing path point x/y values that have decimals (for the detail-oriented among us).
-
The bar to get from Beta to Version 1 for Glyphr Studio was simple: design a font and export an OTF file. Of course this could be a huge amount of features, or something pretty basic. What actually shipped as V1 was somewhere in the middle, and V1 has come a long way since then…
-
This version was a fair amount of back-end work. But the improvements you’ll see, dear user, are all around being able to easily preview and add additional Unicode code blocks (or Glyph Ranges, as we call them) to your project. There are also some enhancements to existing Custom Glyph Ranges, like being able to give…