Pages '09, Pages 5.0, and More Practical Typography

A few days ago, I wrote about Practical Typography and how it caused me to change a few style issues on TheOverAnalyzed.[1] After spending more time with Matthew Butterick’s masterpiece,[2] I stumbled upon his page explaining OpenType features. In it, Butterick shows how to implement OpenType features on the web via CSS.[3]

What caught my attention was Butterick’s blurb on OpenType implementation across the various word processors.

In particular:

Pages ’09 on the Mac is the word proces­sor with the best Open­Type fea­ture sup­port. (The 2013 up­date of Pages, how­ever, sup­ports no Open­Type fea­tures at all.) [emphasis added]

That last part troubled me. It’s common knowledge that new versions of software can sometimes remove features instead of adding them. This is especially true in the first-party Apple app ecosystem.[4] But could an update to really have removed crucial features?

Apparently so.

Taking Butterick’s word for it, I quickly scoured the internet for a scant copy of iWork '09, something I recall deleting a year ago after thinking to myself, "Oh, I’ll never need this—it’s tied to my App Store purchases now. Delete"

After a bit of searching, I found a working .dmg for “iWork '09 Trial.” Great. All I needed after that was a working serial number. Somewhat perplexingly, I found one rather quickly and easily, perhaps because it had been 5+ years since iWork '09 was released.

And so, there I was with two versions of Pages in my /Applications folder.

Just look at that icon 👌🏾
Just look at that icon 👌🏾

Boy did I feel like a real rabble-rouser. I had a vintage pirated copy of an application that a typography master said was better than every other schmuck’s copy of the current version.[5]

I existed in this state of cognitive bliss for several days, until a thought occurred to me: perhaps Butterick was wrong?

After all, Practical Typography was released mid-2013. Maybe subsequent versions of fixed the lack of OpenType features present in the initial 5.0 release?

At first glance, it certainly seems like the newest version of Pages has decent ligature support.[6] I reached out to Butterick to confirm as much, but haven’t yet heard back.

As best as I can tell, while the newer version of Pages does have proper ligature support, it doesn’t appear to have any of the other OpenType features supported by the older version.

Ideal Sans comes with several alternate versions of characters, but as you can see from the screenshots below, the special “G” character (without the horizontal crossbar) does not seem to be available in the newer version of Pages.

Pages 4.4.3 without OpenType Pages 5.5.3 OpenType
Pages 4.4.3 with OpenType support and Pages 5.5.3 without much OpenType support at all

So Butterick was right. Still, even without full support of OpenType features, the newest version of is clearly more at home on 10.11+ systems than the older version. The iconography and pretty much everything else about the newer version is more inline with “iWork’s” iOS counterparts. And because of this, I can’t help but recommend that most users migrate to the newer versions of Pages.

Indeed, even the application icon has now incorporated the Yosemite and El Capitan design ethos:

The "flat" application icon for 5.0+
The "flat" application icon for 5.0+

Louie Mantia agrees:

@ToniWonKanobi sure but this one suits Yosemite better.

— Louie (@mantia) August 31, 2015

It seems like Pages was never sure whether it wanted to be a layout/design application, or just a word processor. Version 5.0 of Pages solidified its place in the latter camp. And there’s nothing particularly heinous about that, unless you’re one of those prosumers not savvy enough for Illustrator, but too smart for Word. If you’re one of those people, the new Pages is not what it used to be. I feel sorry for you, because I am one of you.

  1. Why typography matters

  2. At least I think it’s his masterpiece.

  3. font-fea­ture-set­tings

  4. Final Cut Pro X, anyone?

  5. Poor, poor fools.

  6. Throughout this piece, I’ve been assuming that ligature support means full OpenType support, but that isn’t necessarily the case. And ultimately, I cannot truly confirm full OpenType support without being a typography expert.