We don't care, we handle all.
We have experiences with Fontra (Olli helped Just van Rossum developing Fontra for more than a year) and we enjoy working with Glyphs app (Olli helped Georg Seifert writing unittests for Glyphs app).
We make sure that the vertical metrics matches current industry-standards and work best for your environment.
The interpolation issues are the most fun issues. It's almost arty how they look. Of cause we don't want them in our final fonts, but we do enjoy finding them—so we can fix it.
Of cause we check the settings of the alignment-zone, but we even check very small details and make sure that extrem points are within zones.
Often it's a question of: Was it made intentionally or unintentionally?
Is it an intentional inconsistency, or in other words, a feature or design decision, or is it actually a bug? We don't hesitate to ask if it's unclear: is this glyph missing or is that anchors at the right position, etc.
The correct order of shapes is critical. A wrong order makes the glyph incompatible or causes interpolation issues.
We make sure that the fonts look good on screens, with the best value for money.
Are there any inconsistencies between variable and static fonts or do you need help with the proper STAT table? We have produced may fonts with a variable first approach.
Sometimes you get even errors like this, when you have done everything right. When you export TTF, your nice Bézier curves need to be converted to TrueType outlines. During this conversion it might happen that glyphs are not compatible anymore, even though it is compatible within the font-editor.
If your font contains an error that you are not able to understand or fix yourself, don't hesitat to get in contact with us.
Sometimes, during the design process, people may change spacing or sidebearings—and sometimes people forget to check the components which are not auto-aligned. We do care about these issues and are happy to find and fix them for you.
It's fun to see accents like in the example on the left—totally off. We make sure to go through all glyphs (also the composite glyphs) and check if everything is in the right position.
PowerPoint does not support GPOS kerning, but can handle an old-school kern table. We can help you creating a kern table and make kerning work—even for PowerPoint.
Sometimes fonts have issues, which are practically not possible—but they happen anyway. Believe it or not but we enjoy finding them, so we can fix it.
Are there some anchors missing? Is the position correct? Does FontSpector reports any issues related to accents? Such details make a big difference for many languages.
You hate kerning/spacing? We can help you.
Often it's not enough to fix the source data (GlyphsApp files or Designspace/UFOs) – then we create custom made post-production-scripts to fix issues in the binary font files. For example: We often add a proper handmade STAT table into variable fonts via python scripts.
Font-engineerings is a synonym for font-mastering and vice versa.
Type is a great example where design meets technology. Every font from nowadays is a piece of software, with unicode mappings, axis locations, style-linking, font embedding, hinting information, glyph substitutions and also with glyphs (or in other words: points with x and y coordinates). This font software will be installed on a digital devices like computers, smartphones, cars, dryers, printing machines or any other device which requires text to be rendered – which is almost every device in the world.
And that's why it's important to care about the technical settings within a font software as well – we make sure, that fonts simply work.
If you have ever struggled with: 'my font doesn’t work in Word', 'kerning does not work in PowerPoint', 'glyph interpolation issues' or even more complex issues like 'how do I build a proper STAT table for my variable font', 'complex OpenType features' or 'why is there a vhea table in my latin fonts?' or you wanted to fix the vertical metrics, but you don't know how? – then:
