dot-font: Putting OpenType Through its Paces

5

dot-font was a collection of short articles written by editor and typographer John D. Barry (the former editor and publisher of the typographic journal U&lc) for CreativePro.  If you’d like to read more from this series, click here.

Eventually, John gathered a selection of these articles into two books, dot-font: Talking About Design and dot-font: Talking About Fonts, which are available free to download here.  You can find more from John at his website, https://johndberry.com.

So what’s it like actually using OpenType fonts in your work? Is it easier? Harder? Does it make a difference?

OpenType, in case you lost track of the latest type technology, is a cross-platform font format co-developed by Adobe and Microsoft that offers the potential for extended character sets and other typographic niceties built into the core font. Not all OpenType fonts have extra refinements built in, but those that do (Adobe markets these as “Pro” fonts) can make life much simpler for the type user. Instead of needing to load a separate font to access old-style figures, for example, you can just choose the appropriate character in your application (providing the application is OpenType savvy).

I’ve recently started putting an OpenType font family to work, in the most pragmatic environment possible: the production of a book. Not only am I using OpenType fonts, but I made the decision to switch to the OpenType version of the typeface in the middle of production, after having created the first set of galleys for the book in a non-OpenType version. Despite the extra work and the risk of changing font formats in midstream, I thought that production would end up being easier, and that the book’s files would have a longer life for potential future editions, if I used the new, rather than the old, font format. So far, I haven’t been disappointed.

Minion Pro

The typeface was Minion, Robert Slimbach’s workhorse old-style type family, which looks a bit like an updated and more dynamic version of Bembo. Minion was inspired by a number of different roman and italic types from the Renaissance; the design grew out of Slimbach’s researches in the Plantin-Moretus Museum while he was going back to original sources to develop the Adobe Garamond family. Minion, however, despite its suggestions of Bembo, is not based on any specific 16th-century types; it’s Slimbach’s interpretation of that style of typeface.

Minion has been available for about a dozen years now, and it has gone through three distinct phases. It was first issued by Adobe in 1990, as one of the early Adobe Originals, in a type family that consisted of three weights in roman and italic, with all the typographic refinements necessary for a book text face: small caps, old-style figures, accents, a full set of f-ligatures, and a handful of nicely drawn ornaments. Several years later, when Adobe was promoting “multiple master” technology as the next big thing in type, Slimbach turned Minion into a family of multiple master fonts with three axes: weight, width, and optical size. (Minion was, as I recall, the first typeface to come out with an optical size axis—meaning that the details of the letter design changed subtly from the 6-point master, at one end of the axis, to the 72-point master at the other end. Each master design was fine-tuned to look best at a specific size.) Now that Adobe has turned away from multiple master technology and embraced OpenType as the wave of the future, the refinements of Minion multiple master have been adapted to the huge potential character set of OpenType, and the Minion family has been expanded into Minion Pro, which includes both Greek and Cyrillic alphabets in the same OpenType fonts as the Latin-alphabet designs.

(Any typeface can be turned into an OpenType font, and many have simply been directly converted, by Adobe and other font vendors. But Adobe came up with the “Pro” name for fonts that make use of OpenType’s potential for including a wide range of typographic refinements in a single digital font—refinements like extended sets of accented characters, expanded sets of ligatures and alternate characters, and complementary designs for multiple scripts.)

Setting Text Type by the Pound

The book I’ve been working on is a very large book of poetry, the Complete Poems of Kenneth Rexroth (to be published this fall by Copper Canyon Press). I designed both the cover and the interior, and I’m handling the production of the pages—the typesetting, in other words. (There is no art, except on the cover.) Since I have used Minion quite a bit in designs for Copper Canyon—including an earlier, much smaller volume of Rexroth’s love poems—I settled on Minion for this book. For several years, I have been using Minion multiple master, because it was so easy to make specific versions suitable for particular uses. I had previously created a specific “instance” for use in 11-point text: an optical size that was actually slightly smaller (because I wanted the letters to appear a little sturdier than the 11-point master), a width very slightly wider than the regular width, and a normal weight. I used this instance for the text of the new book.

Although all the typographic refinements were present in the Minion type family, it took a certain amount of manipulation to use them. I would do a search-and-replace for numerals, for instance, changing all the 0’s, 1’s, 2’s, etc. from the lining (cap-height) numerals of the main font to the old-style (lowercase) numerals of the Expert font. Similarly, I had to search for the combinations that ought to use f-ligatures—and I had to do it in a logical order (search for ffi and ffl first, before searching for ff, fi, or fl; and don’t forget to check the “match case” box!). I had set up paragraph styles and character styles using these fonts, and I applied them throughout what turned into a nearly 800-page book.

I was doing both design and production in InDesign 1.5. One of the current advantages of InDesign over QuarkXPress is that InDesign has support for OpenType fonts built in. All you have to do is check an option on a menu, for instance, and InDesign applies ligatures to your text, if the font has them. In an ordinary Type 1 font with an Adobe-standard character set, the only ligatures that will appear are the fi and fl ligatures; in a Pro font, however, all the f-ligatures will be used, and possibly others as well. (InDesign 2.0 gives you several levels of ligatures to choose from—and some of the Pro fonts have quite a collection of alternate and joined characters.) Changing all the numerals to old-style figures is also just a matter of checking an option, as is switching from lowercase to small caps.

The book was so huge that in the first galleys I had left most of the numerals unconverted and the ligatures unchanged, to be dealt with in the second round of production. Between the first and the second galleys, however, I realized that if I were using Minion Pro, I wouldn’t have to do all that searching and replacing: I could just build options like using ligatures and old-style figures into my styles, and automate the whole process. And the newly standard text version of Minion looked very good on the page. (The Minion Pro Opticals package includes four different optical sizes, from “caption” through “display”—not quite the infinitely fluid range of Minion multiple master, but a very useful selection nonetheless.)

So I switched. I bought the Minion Pro fonts, and as I made the corrections and changes from the proofread first galleys, I converted all the fonts from the multiple master version to the OpenType version of Minion. The most tedious part of this was editing my styles, replacing the multiple master fonts I had specified with OpenType fonts instead. (Since I had based most of my styles on a few core styles, most of my changes could simply ripple through. But there are always a few hand-done refinements that need to be changed by hand.) Because of the new way OpenType handles small caps, I found that sometimes I’d end up with a few places where InDesign was trying to find a Small Caps & Old-Style Figures font within the Minion Pro font family—and of course it didn’t exist. When I opened the files again, InDesign would tell me that there were fonts specified that it couldn’t find; luckily, it was easy to convert them globally to the right fonts. The time spent doing this was substantially less than the time I would have spent applying ligatures and old-style figures, even with an efficiently organized search-and-replace procedure.

That Would Be a “Yes”

So far, as I said, I’ve had no complaint, and I’ve found that using the OpenType fonts—at least in InDesign—speeds up my production work, by making it possible to automatic the kind of typographic refinements that used to require extra time and effort. (Because I’m the sort of designer I am, I always go to this trouble. But not everyone does. Anything that automates quality in typesetting for the wider world of production will mean better, more readable type—especially in text—and an easier, more pleasing experience for the ultimate users: the readers.)

It seems to me that the fonts take less time to download, too, when I’m printing laser proofs, although I haven’t actually measured this. The only technical glitch I’ve run across is that my system didn’t seem to like having both the multiple master and the OpenType versions of Minion active at the same time; this wasn’t a big problem when I was converting from one to the other, but if I had to be working simultaneously in files that used both versions, it would be a limitation. (There may be a way around this that I simply haven’t noticed.)

But I’m not really trying to do a lab test here, with benchmarks and quantifiable results. I’m just reporting on a single real-world example of OpenType fonts in action.

So far, I’d say, so good.

John D. Berry is a typographer, book designer, design writer, editor, and typographic consultant. He is a former President of ATypI, and he is the founder and director of the Scripta Typographic Institute.
  • anonymous says:

    It’s apparent that almost every article published here lately, including Berry’s stuff, is an ego trip written on Adobe’s behalf. I can only guess why that is, but it’s none of my business. However, this Open Type affair seems to me as yet another pipe dream that is unlikely, untimely, and ignorant of how market share is divided among DTP applications. InDesign has yet to break 3% of market share, while Xpress is very nicely covering about 90%. Xpress does not support Open Type, nor has it any reason to do so. The majority of designers – those who are Macintosh-based – may remember something called GX, not at all unlike Open Type – much better in fact – which was another pipe dream that went the way of the lemming.

    And puh-LEEZ!! MinionMM didn’t magically transform itself into a better typeface in Minion Pro. With MinionMM I can choose a weight that is exactly 4 units thinner or heavier than Minion Bold. How do you propose I go about doing that with Minion Pro?

  • anonymous says:

    You know, if this site was nothing more than an Adobe ego trip, then I wonder why we’ve posted glowing reviews of Flash MX and are running weekly tips on QuarkXPress. I don’t disagree that we do post a lot of information about Adobe products — they are the biggest player in this market, after all. But at least give us credit for covering other products, because we do.

    Also, John is writing about OpenType which was co-developed with Microsoft. In this case, InDesign is only a vehicle for the fonts.

    Thanks,
    Pamela Pfiffner, eic

  • anonymous says:

    In the review of Opentype, the author wrote “…Not only am I using OpenType fonts, but I made the decision to switch to the OpenType version of the typeface in the middle of production…”
    As a Production Manager, I cringe when I hear things like this. I hope that the author has fully researched the ability of his prepress vendor to handle OpenType with their system. I have recently run into some issues with AGFA workflow systems in place that do not currently support OpenType.

  • anonymous says:

    OpenType is a much better way to handle special and language-specific characters than these expert collections. I did a similar job and OT fonts helped me so much on this. I love to have automactic options to change oldstyle/lining numerals or swash initials/endings.

    It’s really suprising there is no others apps with OT support by now. Just InDesign and, in a minor scale, Photoshop. Even Illustrator 10 don’t know what OT fonts are, a real failure for Adobe. But I’m sure this will change in 1-2 years.

    Besides this, the Adobe-ego-trip question makes no sense since the article is about a format developed by Adobe and MS. If someone try the new TT Microsoft fonts, will see they are actually OT fonts with Cyrillic, Greek, Arabic and Hebrew characters. It’s not an Adobe exclusivity, of course.

    The problem is not Adobe but the other software producers: why not to adopt OpenType? Translators and DTP professionals will be happy to have OT features in Word, XPress and even CorelDraw. But just Adobe give us some solution until these days.

    For the reader who asked about the precision gave by MM fonts, the solution is just one by now: to build your own OT version with FontLab 4.0, the only font editor available that handles OT format. Not an easy way.

  • anonymous says:

    Though my use of fonts and font families is
    limited to in-house manuals, technical
    documentation and the like, I strongly
    approve of the Adobe/Microsoft move
    towards Open Type, and would encourage other
    software graphics programmers to adopt the
    technology. There is nothing more
    frustrating than to have to manually create
    ligature styles, or to search for a
    complementary-but-not-identical symbol or
    special character which is necessary for the
    current project but not included in the
    current font set.

    As Mr. Berry notes, taking care benefits
    the reader. I’ve always held that when I’m
    trying to get one last thing as right as
    possible, I’m not doing it for those who
    WON’T notice. It seems to me that Open
    Type is a step in the direction of
    providing an appropriate document — book,
    memo, manual or on-line web page — not
    for those who won’t notice, but for those
    who will.

  • >