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 them custom names!
There is now a large “Glyph Range Chooser” that lets you explore all the code blocks in Unicode, and easily add them to your project:
The Glyph Range Chooser can be launched from Font Settings, or from the Glyph Chooser panel which shows up lots of places.
Speaking of Font Settings, here is what the new “Additional Glyph Ranges” looks like:
Even after you add ranges from the Glyph Range Chooser, you can edit their names… or even their beginning and ending values. These ranges are very open ended, and up to you to do what you’d like.
I couldn’t quite decide if this was a bug fix or a new feature… but anyway, there is also new functionality where only these “active” glyph ranges will be exported to OTF or SVG fonts (as opposed to every glyph designed in the project).
Below is the granular list of updates. There you have it!
A huge Unicode Code Block range chooser – easily preview and add any Unicode code block to your project!
Glyph Ranges now support custom range names.
Glyph Ranges can now be edited.
Font Exports and Imports now only export/import “active” glyph ranges… this may be more like a bug fix 🙂
It is now possible to disable the Basic Latin glyph range.
Global Action: Re-size all glyphs – now has an additional option to update the Glyph Width (advance width) property.
Ligatures for HTML comment strings now work, like <!–
Ligatures 0x 0X u+ U+ now work – they previously were treated as
invalid Unicode / Hex inputs, but they are valid 2 character ligatures.
This is a very exciting release. One of the very first issues filed on GitHub was to enable Ligatures. Basically forever, we’ve had to rely on a workaround: Export to SVG then convert to OTF for Ligatures and Kerning. Starting now, Ligatures will be exported directly to OTF! Hopefully we’ll be able to work out saving Kern information at some point 🙂
Ligatures export directly to OTF files!
Ligatures that also have a single Unicode code point will be exported accordingly.
A few small Ligature improvements around adding common ligatures, and displaying thumbnails.
Fixed a bug around handling glyphs that use multiple Component Instances with the same Root Component.
Correctly handle / draw side bearings equal to zero.
Allow / disallow correct characters when exporting metadata to SVG Fonts.
Fixed an export bug involving locked points and glyphs with left side bearings.
Context Glyphs – type a few glyphs to show before and/or after the glyph you are currently editing on the edit canvas. Easily navigate to any of those displayed glyphs by clicking on that glyphs name on the Edit Canvas.
Notes on the Ligature and Kerning pages describing how to export to OTF font files via SVG Fonts.
Better slider controls for transparency settings (grids and guides) around the whole tool.
Contribute link now works in the Desktop client.
Show a toast notification when Undo-ing spans many glyphs, and requires navigating to a different glyph.
Test Drive re-factored, including some very small updates.
When inserting a new Component Instance, or using the ‘Get Shapes’ command to paste all the shapes from one glyph to another, there are new options to also copy Glyph Attributes like Width and Side Bearings. This is very useful if you use these copy commands for diacritical marks, where the new glyph should have both the shapes and the glyph dimensions of the root glyph.
Little notation on the splash screen and on the About page that indicates if Glyphr Studio has been updated in the past week.
Removed glyphs 0x0080 through 0x009F from the chooser panel. In Unicode, these are printing control glyphs that have no visual associated with them. But, browsers tend to replace these with ANSI glyphs, so the glyph chooser was erroneously showing previews, causing confusion.
Fixed a bug where ‘Bulk transform shapes’ also transformed shapes in other glyphs.
Added support for SVG number notation, where numbers like ‘22.214.171.124’ are interpreted as ‘123.45, 0.67, 0.89’.
Fixed a bug to only export SVG glyphs if that glyph has a valid hexadecimal key value.
Fixed a bug where you weren’t able to set a shape’s x/y coordinate to zero.
Fixed a bug on Mac where releasing the command key did not exit multi-select mode. (Releasing the key should work, but if not, clicking either the Arrow or Pen tool again will now forcefully exit multi-select mode)
Glyph Range in the Chooser panel is remembered when the panel is switched.
Fixed a bug where editing shape width/height via Attributes Panel was not honoring Lock Aspect Ratio.
Well – boolean actions are here, and the first one is Combine. That’s the big update for 1.04, but you may notice something else before that – we slipped in new icons for actions in one of the previous patch updates:
Like before, these actions are contextually shown or hidden, based on a variety of things. The icon in the lower right is the Combine action, and it shows up if you have two shapes selected. (BTW, you can multi-select shapes by using the pointer tool and Ctrl+Click’ing)
Combine Shapes is going to be kind of a progressive feature. It works for the most part, but we’re still encountering edge cases where it fails. That’s where you come in! Please try out the combine feature, and if you repeatably run into an issue combining two shapes, please email us (email@example.com) your Glyphr Studio Project File (.txt) and tell us which two shapes you’re combining. We are also going to continue to thoroughly test the feature, and fix any edge cases we find.
Going forward, once the Combine algorithm is more solid, we’ll be implementing some related features:
Combine more than two shapes at once.
On the back end, combine shapes and make them semi-transparent for overlapping glyphs in Kern Groups.
Provide an option to combine shapes within a glyph on export – to simplify and minimize font data.
All this stuff will be happening over the 1.04.x milestone, so stay tuned!
So, I know we were going on and on about Boolean Combine… I was having a nice discussion with a Glyphr Studio user over at GitHub about Rotation, and I got to a point where I realized I could actually do the rotate feature in less time than it was taking to talk about it. So here it is!
It also works for Component Instances… but due to how adjustments are applied to Root Components, there could be some wonky results. It boils down to this: there is an extra property on Component Instances called “Rotate First”. If you want to rotate, flip, and adjust the size of a Component Instance, try to do the rotate as the very first action, or the very last action.
If you are curious, it has to do with rotating shapes about their center point. If you do a Resize-Rotate action, it will create a different shape than a Rotate-Resize action. Wierd!
So, we took a little time off over the summer, but v1.02 is here – multiselect Path Points! When the Pen tool is selected, just press the Ctrl key, and all the points for all paths will be shown. While holding the Ctrl key, clicking more points will multiselect them. That’s right – select many points from one path, or many points from across different paths, and edit them together!
Mostly this is useful for moving a couple points at the same time, but any action you can do on one point can also be done on many: Nudge, Insert, Delete, or Reset.
Go try out the new feature and let us know if you find any bugs! We have some performance improvements that we’re also working on. And v1.03 will probably be Boolean Combine (which sounds like an event at the Nerd Olympics).