Category: Publishing & media (Page 46 of 53)

On May 9, I was one of several speakers at an Innodata-Isogen event, “Future Tense – Emerging Trends in Publishing Workflow Management.” They have now posted the presentations and accompanying podcasts. Registration is required, but there are a number of interesting presentations and case studies, including ones from The New Yorker, Houghton Mifflin, Time Out New York, and Harvard Business School Publishing.

(Full disclosure: I’ve consulted many times with Quark and with Adobe, and was specifically hired by Quark to prepare a brochure called QuarkXPress 7 for Output Service Providers.)

I think that QuarkXPress 7 is an important release for Quark, its customers, Adobe and the publishing industry. We’re well past the days of “feature wars,” so, for example, the addition of OpenType support, something first offered in InDesign 1.5 five years ago, is not shaking my world. There is also new support for transparency, improved color management and PDF support, and various other goodies that you’d expect to find in your Christmas stocking, but none of these are anything much more than “overdue.”

What’s most important from my perspective is Quark’s forward strides in supporting improved publishing workflows, the last frontier for the electronic publishing industry. Two new features stand out in this respect. One is “Job Jackets” and the other is JDF (Job Definition Format) support.

According to CIP4 (www.cip4.org) the non-profit industry association pushing JDF, “JDF is a comprehensive XML-based file format and proposed industry standard for end-to-end job ticket specifications combined with a message description standard and message interchange protocol.” Along with its earlier incarnations, JDF has been in the making for more than 15 years now. It has very broad industry support – hundreds of vendors have added JDF functionality to hundreds of hardware and software products. That being said, it’s still a challenge to find a robust JDF-based publishing installation in the field. The main reasons for this are the complexity of the standard and the need for all of the players in a broad publishing workflow to be in the game – if one key component lacks support the JDF flow grinds to a halt.

Adobe have added JDF support to Acrobat, which is to some extent accessible from InDesign, but Quark has moved ahead of Adobe by building JDF support directly into the page layout application, independently from PDF. No doubt Adobe will follow suit in the next version of InDesign, expected early next year, so the issue is not so much who got there first. But having what is still the mostly widely-used page layout application in the world throw its support behind JDF is of key importance at this time when broad-based JDF adoption by the publishing industry is still in question.

Quark uses JDF also in its Job Jackets feature. A Quark Job Jackets file contains all of the rules and specifications necessary to describe a QuarkXPress project. A Quark Job Jackets file can include specifications for colors, style sheets, trapping, and color management as well as picture color space, format, and resolution. The file can also include information such as the page size, number of pages, and contact information for the people involved with a job. And the file can include rules that specify configurations for font sizes, line thicknesses, box backgrounds, and other project elements. Workgroups can obtain consistent output by using Quark Job Jackets to share specifications across workstations.

For me the most intriguing benefit of Quark Job Jackets is that it re-invents the concept of preflighting. Preflighting has always been a post-process step: create your file, and then find out where you screwed up. With Job Jackets users can ensure that a print job adheres to its specifications from the moment it’s created, and that it continues to adhere to those specifications all the way through the production process until it rolls off the press. I’ve long maintained that page designers would not be able to perfect their process until it was possible to prevent errors, rather than to correct them after the fact. I’m certain this approach will fast become the production norm.

It’s interesting to me that searching through Google News the day after the Quark 7.0 launch in New York, there’s nary a mention in the mainstream press. Neither the New York Times nor the Wall Street Journal seem to have found it worthy of coverage. To me this reflects the new prevailing “wisdom”: Adobe has won the page-layout wars (and every other war for that matter), so Quark’s announcement isn’t newsworthy. I think they are underestimating the importance of QuarkXPress 7.0. Only time will tell.

Our news includes some details about the launch of QuarkXPress 7.0, but I have to ask if this is at all significant to the desktop publishing world at this point. Most–maybe even all–publishers I work with have made the move to Adobe InDesign. Some publishers are holding on to a few licenses of QuarkXPress for older books and products that might need to be updated, but all new products are being done using InDesign. Moreover, Adobe Creative Suite, which combines InDesign, Illustrator, PhotoShop, and other products, is simply too attractive an offering with very attractive pricing. Quark has nothing comparable to counter with.
For larger publishers, there are also very viable workgroup options with InDesign, which wasn’t true a few years ago. The combination of InDesign with InCopy for writers and editors is gaining traction, and there solutions such as K4 from Managing Editor and Smart Connection Enterprise from Woodwing for larger groups. These systems are often replacing Quark’s QPS solution as the publishers drop QuarkXPress for InDesign.
Quark 6.0 took forever to come out. Quark 7.0 took forever to come out. In the meantime, InDesign has really taken hold. So I have my doubts that Quark can overcome this.
Finally, there is a cautionary tale in all of this. Quark was famously arrogant in its heyday, and did a lot to alienate customers. When I wrote about the movement to InDesign for The Seybold Report in December 2004 (subscription required), industry maven Kate Binder said, “Never discount people’s absolute, bitter hatred of Quark the company. It’s genuinely a factor.”

I couldn’t resist buying an Intel iMac and installing Windows on it. It really was incredibly simple to add Windows. I’m not sure how I will actually use both OSs yet, but it occurred to me that in the often heavily mixed Mac and PC creative and publishing environments, a few Macs running both operating systems could be very useful for smoothing out some workflows in potentially non-disruptive ways. I’ll let others figure out if this is the case, but one issue they will need to think through is whether to format their Windows partition with NTFS (more secure and reliable) or FAT (more compatible).

Frank does a great job of filtering the news and getting it out to our readers. We get several press releases a day, and on busy days it can be a dozen or more. When one of our conferences or a trade show like AIIM is coming up, the flood of news can be pretty overwhelming. To make it more challenging, most of the news ends up in our email in-boxes–along with dozens of other legitimate email and, some days, hundreds of spam. I have pretty good spam filtering, but sometimes it overflags, and a vendor email will end up in my junk mail folder. Every week or so, I go through the spam and flag these email addresses for my white list.
So I have a proposal for vendors. Come up with an RSS feed for your news, and I will subscribe to it. A few of you already do this, and I have subscribed, but most of you don’t. So add an RSS feed for your press releases and let us know–by email of course. 😉
While you are thinking about it, you could consider a more general RSS feed for other elements of your Web site–events, new documents, and so forth. I am sure your customers would appreciate it too.