Moments ago, at the ATypI conference in Warsaw, representatives from Google, Microsoft, Apple and Adobe unveiled version 1.8 of the OpenType specification, featuring a surprise in the form of variable fonts (a.k.a. OpenType Variations). This is an extension and updating of the 1990s GX Variations technology invented by Apple, and a functional superset of Adobe’s Multiple Master technology.
Links which should all be live shortly if they are not already:
The variable fonts enabled by this technology will offer more freedom to type designers and font users, and smaller file sizes for packaging font families. Type designers can enable one or more axes of variation, such as weight, width, or optical size. These can be done with true typographic finesse — we’re not talking artificial stretching and automatic algorithms.
FontLab has already recently begun work on integrating support for variable OpenType fonts in FontLab VI. Indeed, sharp-eyed users of the most recent FontLab VI Public Preview builds may note that they already contain a “Variations” panel, which already features some of the key flexibilities allowed by variable fonts but not in, say, Multiple Master: masters at any point in the design space, and potentially many more design axes. FontLab VI will ship with some degree of OpenType Variations support, and we will continue work on OpenType Variations afterwards, both for FontLab VI and other products.
Variations panel prototype from FontLab VI (build 6101)
Long-time type industry watchers might be aware that FontLab was the first font editor to offer designers a full visual environment for working with Adobe’s Multiple Master technology. I did my own Master’s thesis in this area, and FontLab’s Adam Twardoch has been suggesting for several years, to anyone who would listen, how it wouldn’t be hard to add GX Variations to OpenType.
So needless to say, the FontLab team is very excited to see the unveiling of this new technology, and is fully supportive of this announcement. I have already written an article for Communication Arts magazine about OpenType Variations and what it means for designers, and next week I will be talking about it at the WebVisions conference in Chicago. You can already see the seeds in our latest FontLab VI Public Preview, and there is more to come!
The 70-minute tutorial Basics of Python scripting in FontLab Studio 5 has beed recorded in February 2015 by Adam Twardoch. The tutorial is primarily intended for users who have never written any Python code before, although some tips and tricks for more advanced users are given. Topics include: basics of Python, scripting-related user interface elements of FontLab Studio, installing Python, RoboFab and FontLab Python macros, writing simple scripts that modify a font and speed up the type design process. See below for additional resources.
Multi-color fonts are still bleeding edge technology, so no one format is universally (or even widely) supported. But they do work today in a number of places, especially if you can make a font that supports several of the competing would-be standards! This YouTube video by our own Adam Twardoch shows how to create multi-color fonts across multiple color formats, with existing FontLab apps.
There are a host of utilities that can make the font making and editing experience easier and faster. Some work directly in FontLab Studio via the Python scripting language, and others are separate items. Here is how to install Python-related tools, and the many scripts and things they enable, to work with FontLab Studio 5.1+ on Mac OS and Windows. (If you are using earlier versions, please upgrade to 5.1.x Mac and 5.2.x Windows. Upgrades from 5.0 and higher are free!)
You do not have to be a programmer to make use of these tools! While folks who are at least moderately geeky and technical will get more out of most of these tools, almost anybody who can use FontLab Studio will find value in tools such as TTX, and benefit from some scripts they can run “out of the box.” Once you get this stuff set up, you can install more macros/scripts just by dragging them to the FontLab macros folder, and restarting FontLab Studio.
OpenType Layout features allow for orthographically correct display of complex scripts such as Arabic and Indic and provide a mechanism for the user to apply advanced typographic formatting to text. They are used in the SFNTGSUB and GPOS tables.
This document contains a useful classification of OpenType Layout feature tags. It is based on the OpenType spec version 1.6, with some additional entries about removed features and Microsoft-only Math features related to the MATH OpenType table.
This document is very technical in nature, and is primarily aimed at software developers who wish to implement user interfaces for applying OpenType Layout features in applications.
Although Fontlab Ltd. debuted the Photofont technology some 8 years ago, the typographic community did not show much interest for multi-color fonts or typography. In 2013, it changed. Actually, this started a few years ago with Apple introducing the color emoji font into iOS, and then Mac OS X 10.7. Now, all major industry players (Apple, Adobe, Mozilla, Google and Microsoft) have proposed their formats, which aim to extend the OpenType font format by the ability of including color glyph information. The proposals differ in many aspects. Below is a discussion of the proposals along with some personal comments.
This article is very technical. No completeness or correctness of the information presented below, and all views are personal.
The video tutorial by Adam Twardoch accompanies this article by providing a more practical take on color font creation issues.
Theoretically, OpenType PS (.otf) supports fractional coordinates, but there are some technical caveats associated with it. In principle, we could say that the final font formats only support integer coordinates but during the work process, having fractional coordinates would be helpful.
For example, if you have drawn your glyphs on an integer grid, but then you’d like to make some adjustments such as: make it slightly more narrow, then slightly wider, then perhaps slant it by a few degrees and then slant it back, or make some tiny rotations, or maybe scale the glyph down and then up again — on an integer grid, the result will have accumulated the rounding errors from every one of these operations. On a fractional grid, all your shapes (the positions of the BCPs, the angles, the stem thicknesses etc.) will always remain just as in the original design.
Therefore, a hardwired integer grid such as the one in FontLab Studio does impose a certain limitation onto the type designer. A fractional grid such as the one in Fontographer allows you to avoid those rounding errors. But of course, at the very end, when you decide to generate or ship the font, you’ll need to align your points to an integer grid, or the software will do this for you.