Arial is everywhere. If you don’t know what it is, you don’t use a modern personal computer. Arial is a font that is familiar to anyone who uses Microsoft products, whether on a PC or a Mac. It has spread like a virus through the typographic landscape and illustrates the pervasiveness of Microsoft’s influence in the world.
Arial’s ubiquity is not due to its beauty. It’s actually rather homely. Not that homeliness is necessarily a bad thing for a typeface. With typefaces, character and history are just as important. Arial, however, has a rather dubious history and not much character. In fact, Arial is little more than a shameless impostor.
Throughout the latter half of the twentieth century, one of the most popular typefaces in the western world was Helvetica. It was developed by the Haas Foundry of Switzerland in the 1950s. Later, Haas merged with Linotype and Helvetica was heavily promoted. More weights were added and it really began to catch on.
An icon of the Swiss school of typography, Helvetica swept through the design world in the ’60s and became synonymous with modern, progressive, cosmopolitan attitudes. With its friendly, cheerful appearance and clean lines, it was universally embraced for a time by both the corporate and design worlds as a nearly perfect typeface to be used for anything and everything. “When in doubt, use Helvetica” was a common rule.
As it spread into the mainstream in the ’70s, many designers tired of it and moved on to other typographic fashions, but by then it had become a staple of everyday design and printing. So in the early ’80s when Adobe developed the PostScript page description language, it was no surprise that they chose Helvetica as one of the basic four fonts to be included with every PostScript interpreter they licensed (along with Times, Courier, and Symbol). Adobe licensed its fonts from the original foundries, demonstrating their respect and appreciation for the integrity of type, type foundries and designers. They perhaps realized that if they had used knock-offs of popular typefaces, the professional graphic arts industry—a key market—would not accept them.
By the late eighties, the desktop publishing phenomenon was in full swing. Led by the Macintosh and programs like PageMaker, and made possible by Adobe’s PostScript page description language, anyone could do near professional-quality typesetting on relatively inexpensive personal computers.
But there was a problem. There were two kinds of PostScript fonts: Type 1 and Type 3. Type 1 fonts included “hints” that improved the quality of output dramatically over Type 3 fonts. Adobe provided information on making Type 3 fonts, but kept the secrets of the superior Type 1 font technology to itself. If you wanted Type 1 fonts, Adobe was the only source. Anyone else who wanted to make or sell fonts had to settle for the inferior Type 3 format. Adobe wanted the high end of the market all to itself.
By 1989, a number of companies were hard at work trying to crack the Type 1 format or devise alternatives. Apple and Microsoft signed a cross-licensing agreement to create an alternative to Adobe’s technology. While Microsoft worked on TrueImage, a page description language, Apple developed the TrueType format. TrueType was a more open format and was compatible with—but not dependent on—PostScript. This effectively forced Adobe’s hand, causing them to release the secrets of the Type 1 format to save themselves from irrelevancy.
Around the same time, PostScript “clones” were being developed to compete with Adobe. These PostScript “work-alikes” were usually bundled with “look-alike” fonts, since the originals were owned by Adobe’s business partners. One PostScript clone, sold by Birmy, featured a Helvetica substitute developed by Monotype called Arial.
Arial appears to be a loose adaptation of Monotype’s venerable Grotesque series, redrawn to match the proportions and weight of Helvetica. At a glance, it looks like Helvetica, but up close it’s different in dozens of seemingly arbitrary ways. Because it matched Helvetica’s proportions, it was possible to automatically substitute Arial when Helvetica was specified in a document printed on a PostScript clone output device. To the untrained eye, the difference was hard to spot. (See “How to Spot Arial”) After all, most people would have trouble telling the difference between a serif and a sans serif typeface. But to an experienced designer, it was like asking for Jimmy Stewart and getting Rich Little.
... continue reading