Saving Time With Quark's Synchronized Text

With QuarkXPress 6 or 6.5, making changes to text that repeats across a page or even multiple, disparate layouts is a matter of doing it just once with Synchronized Text.

QuarkXPress 6 intro­duced the con­cept of mul­ti­ple print and/or web lay­outs in a sin­gle doc­u­ment. The idea, of course, is to keep relat­ed lay­outs in a project togeth­er in a sin­gle doc­u­ment as opposed to the typ­i­cal way of mak­ing sep­a­rate doc­u­ments for each.

At first, many design­ers were con­fused by the need for Quark’s mul­ti­ple lay­outs. Why not just keep doing it the way we’ve always done it—multiple files? Afterall, decades of doing it that way have taught cre­atives how to orga­nize and man­age their files to reduce con­fu­sion, clut­ter, and file misplacement.

Screenshot of QuarkXPress with Synchronized Text palette
The Synchronized Text palette with a sychro­nized text box, indi­cat­ed by the light­ning bolts in the resize han­dles. [Screenshot from QuarkParticles]

Many design­ers are still doing it that way, even in Quark 6 and 6.5—creating a new XPress doc­u­ment for each new lay­out, regard­less of how close­ly they are relat­ed or much infor­ma­tion the lay­outs have in common.

There are, of course, draw­backs to putting all your lay­outs in one doc­u­ment. As with any­thing else, putting all your eggs in one bas­ket means if some­thing hap­pens to the basket—file cor­rup­tion jumps to mind immediately—you’ve lost the entire project instead of just one seg­ment. But, there are also dis­tinct advantages.

Quark R&D rec­og­nized that a large por­tion of its cre­ative and pro­duc­tion users typ­i­cal­ly work on mul­ti­ple, close­ly relat­ed doc­u­ments. Corporate iden­ti­ty mate­r­i­al is the best exam­ple. Though they are laid out very dif­fer­ent­ly, the infor­ma­tion and basic style of busi­ness cards, let­ter­head, envelopes, and oth­er iden­ti­ty mate­r­i­al are vir­tu­al­ly iden­ti­cal. So why require a design­er to type and change mul­ti­ple copies of the same infor­ma­tion or style?

If Quark had left the multiple-layout func­tion­al­i­ty at just that, then its only val­ue would be orga­ni­za­tion, reduc­ing the file-management tasks for the project. But they didn’t leave it at that. They built in pro­duc­tion func­tion­al­i­ty that takes advan­tage of mul­ti­ple lay­outs in a sin­gle document.

Using the Synchronized Text fea­ture, redun­dant infor­ma­tion like address, phone num­ber, web­site URI, and oth­er bits of text com­mon to mul­ti­ple design projects like an iden­ti­ty pack­age, only has to be typed once. Now, typ­ing short bits of infor­ma­tion a cou­ple of times—or copy­ing and pasting—isn’t that much of a chore. But how often do typos occur? How many times have you trans­posed two dig­its in a phone number?

Consider designs for prod­uct pack­ag­ing, brochures, oth­er pro­mo­tion, and point-of-sale. How much infor­ma­tion is redun­dant between those types of projects? Chunks of the copy is often repeat­ed, ver­ba­tim, among at least some of them. The prod­uct name, tagline, and major copy points are invari­ably repli­cat­ed from one design to anoth­er. Now con­sid­er how often the client comes back with copy changes to one or all por­tions of such projects?

Even a sim­ple copy change across mul­ti­ple lay­outs can be time-consuming and tedious. Sometimes the tedi­um itself leads to typos. Wouldn’t it be nice to change all the copy, across all relat­ed designs, in a sin­gle shot?

That’s what Quark was after when they built into XPress 6 mul­ti­ple layouts.

If all relat­ed lay­outs are stored in a sin­gle QXD file, each in its own lay­out, text blocks can be typed only once—and updat­ed only once—and then the changes are syn­chro­nized across the entire project. And it works for mul­ti­ple instances inside the same document—think of busi­ness cards laid 6‑up on a page. Changing the phone num­ber or e‑mail address doesn’t have to be change once, then copy and paste five times.

While writ­ing this arti­cle (5 January 2005) QuarkParticles, Quark’s online newslet­ter, appeared in my inbox with a tuto­r­i­al on–guess what?–Synchronize Text.

So, rather than pub­lish effec­tive­ly the same infor­ma­tion in two dif­fer­ent lay­outs, I will, after giv­ing you the why, refer you to QuarkParticles for the how.