So You're Using Miranda and Feeling Like Everything Is Against You
It is not just you. I have been working with fonts for over a decade and I deal with this daily. Most people start with a simple idea: I need to tweak a glyph here, adjust a kerning pair there, maybe build a small typeface for a client. What they find when they open Miranda instead is an editor that behaves like it was built in 2006 and never quite updated its attitude about modern workflows. It works. It has worked for years. But it also has a number of rough edges that will make you question your sanity on a regular basis.
Miranda Is It Just Me
The frustration is universal enough that I hear it constantly from other type designers. You export something, it looks wrong. A path reverses itself without warning. Your carefully set up kerning table vanishes when you save in a format you do not expect. You open a file you created three days ago and somehow your master interpolation is broken. This is normal. Not correct, but normal. Here is how you deal with it.
What Miranda Actually Is
Miranda is a free font editor for macOS developed by James Burnham and later maintained by the open source community. It reads and writes OpenType fonts. It handles TrueType outlines. It supports multiple masters for interpolation. It does not have a modern interface, it does not have a font preview pane that renders text accurately in all contexts, and it will not save your life if you make a mistake with a contour direction. That last point matters more than you think. When I first tried using Miranda to build a simple Latin typeface, I spent four hours debugging a glyph that looked fine on screen but broke the entire kerning pair table when exported. The problem was a single reversed subpath inside the D glyph. Miranda showed the path as black and seemingly correct. FontForge and RoboFont both caught the error immediately. Miranda did not. That is an honest limitation of the tool. It simply does not flag every kind of contour anomaly the way commercial editors do.
Get the Full Details
The Workflow That Actually Works
Start by keeping your source file open in Miranda at all times, but do not do all your work there. Use it as an intermediate step, not your primary editing environment. I draw my glyphs in a program that validates contours properly. Then I bring them into Miranda for interpolation setup, kerning tables, and final OTF export. This two-step approach saves me roughly three to four hours per project compared to trying to do everything inside Miranda alone. Here is the part most tutorials miss: always export your font in TT format first and run it through a validator before exporting as OTF. Miranda sometimes builds valid TT fonts that contain hidden issues when converted to OpenType CFF outlines. The GPOS table can get mangled during that conversion. I learned this the hard way when a client received a font that rendered correctly on screen but had non-functional ligatures in print production software. Re-exporting from TT and checking the GPOS table explicitly fixed it. Takes about ten minutes and prevents two days of back-and-forth.
Kerning Without Losing Your Mind
Kerning in Miranda is functional but not intuitive. The kerning pairs editor shows you a list of pairs with numeric values. There is no visual preview of how those pairs actually render side by side at different sizes. What I do instead is export the font at various sizes, open it in a simple text editor, and visually inspect the pairs that matter most. It is slower than it sounds like it should be, but it catches errors that the built-in editor misses. A common pitfall: Miranda will sometimes auto-generate kerning pairs when you load a font with an existing kerning table, and it does not always do it consistently. If you import a font and your kerning values look completely off, check whether Miranda has duplicated or shifted pair assignments. Export the kerning data as a text file, compare it against what you expect, and rebuild the table manually if needed. This happened to me with a borrowed font where the original author used unconventional pair ordering. Miranda tried to reorganize it and produced about forty wrong pairs out of roughly six hundred.
Interpolation Quirks You Need to Know
If you are building a variable font or a multi-master family, Miranda handles the math but not always the geometry. When you create a master with a slightly different glyph structure than another master, Miranda will interpolate the differences. Sometimes it produces ugly artifacts. Sometimes it produces correct results. There is no reliable visual indicator of which will happen until you actually render the intermediate masters. The workaround is to keep your master designs geometrically aligned wherever possible. Same number of points. Same contour order. Same anchor placement. If you must have different structures between masters, build those intermediates manually instead of relying on automatic interpolation. I have found that spending thirty minutes setting up clean intermediate masters manually produces significantly better results than letting Miranda figure it out automatically, which usually takes longer overall because of the cleanup required afterward.
Export Settings That Actually Produce Working Fonts
When you export from Miranda, go to Edit > Preferences > Export and make sure the following are set explicitly: Keep the TT instruction set enabled. Disable synthetic bold and italic generation unless you specifically need it. Turn on automatic kerning pair optimization only after you have manually verified your pairs. Set the font format to TrueType if you are distributing for general use, or OpenType CFF only if you specifically need the smaller file size and have validated the output. I have seen fonts from Miranda fail to load in some browser-based type viewers when the CFF export had subtle hinting issues. Switching to TT and running the font through a free validator like FontValidator from the Apple Developer tools fixed every reported issue. Takes about five minutes and is worth doing before any distribution.
When Miranda Is the Wrong Tool
If you need automated error checking, a modern visual interface, proper variable font axis editing, or reliable cross-platform export validation, Miranda will frustrate you. It is free and it works for straightforward tasks. It is not a replacement for FontForge when you need batch processing, and it is nowhere near RoboFont when you need precision workflow control. I use it when I need a quick second opinion on a glyph or when I am doing light interpolation work on a simple project. I do not use it for production fonts going to commercial clients unless I plan to do extensive post-export validation in another tool. The bottom line is that Miranda is functional software with real limitations. Understanding those limitations and building a workflow around them is what separates people who give up on it from people who use it effectively. The issues are well-documented among people who stick with it long enough to learn the patterns. You are not imagining things. It is just the tool, and it can be made to work.
