UPDATE: There’s an even newer version, 5714, released 9 Oct 2015.
We have just published FontLab Studio 5 for Mac and Windows
release candidate builds 5672. They have an updated mechanism for generating OTF fonts and many bugfixes. Please read the release candidate notes and download!
Free BitFonter 126.96.36.1995 (http://bit.ly/1Njr6tk) and ScanFont 188.8.131.525 (http://bit.ly/1HjtWxN) updates for Mac OS X available!
2015-01-27: Updated builds 2015-01-23 available (segmentation fault 11 bug fixed; better handling of guidelines and composites, TTH bug fixed)
FontLab vfb2ufo is a two-way command-line converter for Mac OS X and Windows. It’s available free of charge from FontLab.
vfb2ufo converts between development font formats: VFB and UFO (including the compressed variant UFOZ). It converts both ways: from VFB to UFO (or UFOZ) and from UFO (or UFOZ) to VFB. If you supply it with a VFB, it will output a UFO (or UFOZ if you use the -z option). If you supply it with a UFO or a UFOZ, it will output a VFB. It converts one VFB or UFO or UFOZ at a time, but you can write batch scripts to facilitate conversion of multiple files at once.
This document describes an example process of generating hinted fonts with PostScript or TrueType outlines using automatic and/or simple manual steps in FontLab Studio 5.
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 SFNT
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.
It’s been long overdue… I wasn’t really happy about what the various blog templates looked like, so I have been putting away the creation of our own. But finally, this year, responsive web techniques have become easy to use, the proliferation of web fonts has made it possible to create a page that’s easy to read continuously, so we’ve prototyped a new look, and — well — launched it (semi-officially).
We have a long line of content articles that shall be appearing here in the coming months. So, don’t bite your fingernails while waiting for revelations here in the next weeks, but feel free to visit us from time to time.
(Also, please bear with us for the time being — there are some design and functional glitches here and there which we’re planning to fix.)
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.