On Production.
by Pablo Defendini
I came of age, career-wise, in the late 90′s, as an art director at J. Walter Thompson, a multinational advertising agency. The 1990′s were an interesting time to be in an art department. The desktop publishing revolution was changing the way art directors and designers went about their work: x-acto knives, paste-ups, and letraset lettering were being displaced by Macs running Adobe Photoshop, Macromedia Freehand (nowadays Adobe Illustrator, sadly. Freehand kicked ass) and Quark Xpress (these days it’s InDesign, thankfully. Quark Xpress is a piece of trash and should be put out of its misery with a bullet or twenty. But I digress). Many old-school designers and art directors were being forced to completely upend their usual modus operandi. During my tenure at JWT and other agencies, I saw art directors mostly take one of three tacks to attack the problem of their suddenly impending obsolescence:
a) hire a bright young thing to translate their hand-crafted comps into electronic desktop publishing files,
b) hunker down, learn the new tools of the trade, and become proficient in the new lingua franca of creative production, or
c) sit back with their head in the sand, coast on their reputations (and their sometimes exorbitant paychecks), complain loudly about how computers were destroying their livelihood, or how they were just a fad or trend, and would soon pass.
I remember being one of those bright young things from a), and I learned a lot from my mentors, who would—in exchange for some relatively minor Photoshop jockeying—help me hone my conceptualization and design skills: you know, the kinds of abilities that no amount of Photoshop-fu can magically instill in you; I still keep in touch with some of my former colleagues who embraced solution b); and had absolutely no patience for the old-guard who decided to take tack c). I’ve no idea what’s become of those poor fools—they are certainly not professionally active in any substantial sense anymore, as far as I can tell.
As time went on, my career and interests expanded into film-making and web design, and I saw the same effect in these sectors. The advent of Apple’s Final Cut film-editing software in the early 2000′s, for example, allowed me to put together a very lean television production team, hiring out producers and creatives like directors, DPs and editors directly, and creating TV spots which enabled me to not have to depend on outsourcing production to film-based studios, thereby (legitimately) undercutting competitors on price and speed-to-air. The debut of software like Dreamweaver and other WYSIWYG code editors allowed me to learn to code HTML in a way that was much more accessible to me than having to learn a programming language blind, and let me put together a nascent interactive department.
It absolutely boggles my mind that, at this late stage in the game, publishers still consider themselves somehow exempt from the repercussions of the digital revolution.
As publishing makes its unfashionably late entrance into the digital realm, the people working in publishing production are facing similar challenges. Unfortunately, the prevalence of attitude c) is legion, especially among the big six legacy publishers. It amazes me that, despite being run by what seems to be a bunch of genuinely intelligent people, and despite the fact that, within all the big publishing houses, there are incredibly smart and competent and observant people (usually our age and pay grade) who are acutely aware of what needs to be done, legacy publishing is stubbornly determined to make the same mistakes that others have made before them.
There is a saying that my mother is very fond of, and it’s one that I’ve been saying to myself over and over, like a mantra, over the past couple of years: Si las barbas de tu vecino se están quemando, pon las tuyas en remojo. Or, for the monolingual among you: “If your neighbour’s beard is on fire, you should go soak yours in water.” So let’s take a look at what a hypothetical publisher with some cojones could stick in their bucket of water, shall we?
You know that author who swears by their 1965 IBM Selectric, the one they bought at a garage sale when they were fifteen and still use to this day, because “the only way I can write is by clacking away at my Selectric in my special writing corner of my special writing cabin in the middle of my special woods”? Well, that’s adorable, really. Very quaint, and I’m sure it makes for a wonderful quip while on tour and trying to aggrandize the author’s romantic mystique. Unfortunately, it’s also fucking retarded. You know what? Grow a goatee, or wear a beret, but use a modern word processor, or even better, an XML editor. Like it or not, authors who produce creative work for big publishers are not fine artists, they are commercial artists, like illustrators, designers, session musicians, etc. If you’re writing a book of poetry for yourself, or as a purely artistic endeavour, then go ahead and break out the chisel and chip away at your stone tablets. But if you’re a commercially published author, who depends on a production team in order to get your work published, you’re damn well served making your support team’s life easier. Musicians don’t hand in a box full of reel-to-reel tapes to their record companies; they’re rocking ProTools files.
Editors, same deal: learn to author XML. Learn to love versioning tools. That way you’ll have full control over the master edition of your work: the one that gets distributed to all the different formats: print, ebook, web, smoke signals, what have you. Looking for typos and errors in galleys of the printed book before it goes to press is too late in the game (not that it shouldn’t be done, of course). By the time something hits the production department, it should be good to go. That kind of print-centric approach is soon to be very inadequate anyway, as ebook production gets rolled into the main line of a book’s production cycle, which in turn becomes much less linear.
Hey typesetters, compositors, and producers in general: you know how I’m hectoring authors and editors about XML? Well, that goes quadruple for you. Learn how to cleanly import XML into InDesign for your print edition (hint: it’s not quite as simple as mousing over to File>Import); learn how to create a proper, well-crafted, compliant and appropriate ePub file from that XML document (which is also not quite as simple as hitting File>Export to Digital Editions—go listen to what Liza Daly has to say. Listen to that woman—make her your bible, your fucking virgin mary); learn how to automate these processes so that you’re always working from the original manuscript (which is now an XML file), as opposed to making ad-hoc, in-line corrections on the fly which don’t propagate to subsequent editions.
Wait a minute… it’s kind of quiet in here. Where did everybody go? Oh shit, big publishers outsource a large part of these services, don’t they? They’ve found that cutting out expensive production departments and hiring out the services of middlepeople, who also handle distribution and sometimes even retail fulfillment, saves on people power (read: health insurance and pensions), hassle, and extra load on their IT departments. Well, guess what one of the cardinal rules of the digital revolution is: digital production eliminates the need for most middlepeople. Bring this all back in-house, make it a lean operation. Settle on nothing less than a standards-compliant workflow, but please, build it from the ground up, as opposed to tacking it onto your existing production setup as an afterthought. I’m a rip-the-band-aid-off-quickly kind of guy, so it should come as no surprise that I’m advocating the scorched-earth approach here, but scorched-earth is the right approach here, I think; things are moving too quickly around you for it to not be.
I know it’s an enormous outlay of capital at the beginning, and it requires re-thinking many of your core business relationships and practices, and that we’re in a recession, and that you don’t want to lay off or re-train half your workforce. It’s gonna be hard. Real hard. Old habits, and all that. But you know, it’s going to have to happen sooner or later, like it or not. Why not get a jump on things—be proactive, take advantage of the fact that we’re in a recession, and people are out of work, and looking for gigs. Steve Jobs once said, during the dot-com bust of the early ’00s: “We decided to innovate our way through this downturn, so that we would be further ahead of our competitors when things turn up“. That’s worked out rather well for Apple, don’t you think? Take a page from Uncle Steve’s playbook.
Otherwise, smaller and more agile shops are coming in to eat your lunch. They don’t have the large amounts of capital from the latest Dan Brown/Stephen King.J.K. Rowling/Stephanie Myers/Janet Evanovich, but they also don’t have the overhead, the legacy, or the inbred, grandfathered attitudes so prevalent at legacy publishing houses.











Comments
Fuck. Stop making me feel like a moron. Or maybe I should stop doing that to myself? Bandaid, quick, rip, yeah. But inspiring.
I came of age, career-wise, in the early 90s and was also one of those so-called “bright, young things.” So I’m with you on most of your points.
One picky thing, though: Until InDesign gets something resembling Kerning Table Edit, I will still retain some love for Quark (even though I choose not to use it anymore).
Tina @2:
Heh, good catch; I actually thought about kerning tables when I was writing out that line. But well-made Opentype Fonts mostly eliminate the need for editing kerning tables!
Marry me?
“I’ve no idea what’s become of those poor fools—they are certainly not professionally active in any substantial sense anymore, as far as I can tell.”
I believe they all wound up at Y&R.
@ India:
Aw, shucks.
@ Jim HInes
Oh snap!
(yes, I am my own peanut gallery!)
I agree with most of what you say here, except for the authors switching to a new format for composing and delivering their work. Authors write how they write, it’s up the publisher to get it into working order. If Paul Auster wants to send me cassettes with dictation, fine. People don’t pay money for my production skills, they pay to read his work.
What happens if an author has several publishers, each at their own station along the XML express? Or, more frustrating, what’s the shelf life on XML versus the next, better code five years from now? Your own post addresses these issues (Quark to Indesign to…?)
But XML is not software; it’s a markup language. XML files are plain text. Shelf life is indefinite—and certainly much longer than a Word doc.
@Ryan:
Aside from what India says above, I think we’re talking about two different things here.
I’m talking about the tools an author should use in order to make the lives of the production team at their publisher easier.
You’re talking about publishers coddling their authors, and not expecting them to conform to standard production practices.
If an author hands a publisher a cassette with dictation on it, then it’s up to the publisher to decide whether they want to humor that author and find the time and resources to transcribe it into something that the production department can actually use. Fair enough. Sometimes they will, and sometimes they won’t.
Personally, I’m firmly in the camp of not allowing that kind of behaviour: I think that, along with deadlines, acceptable formats for delivery should be part of any contract. If I were a publisher, and I got a cassette tape from an author, I’d be all like: “Hey, get your head out of your ass and either hire an assistant to do this for you, or come correct with a text file”. But that’s just me.
If a musician, a designer, or hell, a carpenter is expected to stay current and proficient on the tools of their trade, I don’t see why authors should be exempt from that. Remember: they’re commercial artists. There is a state of the art for their trade, and as commercial artists, it’s their responsibility to stay current on it.
Also: people do pay money for your production skills. Otherwise, authors would simply publish a manuscript, with no regard to editing, proofreading, copyediting, typography, packaging, etc.
I think you nailed it with the “commercial artists” line. I’m thinking more of the literary writers. It isn’t about the money for them, often advances and royalties are secondary incomes. This is of course a small percentage of all of publishing, but it is the one I work for. O’Reilly should go with XML. Sterling should go with XML. But our novelists who submit a book once every 7-10 years? I can’t see it.
I think we’ll have to agree to disagree here. I get where you’re coming from, but I consider any author writing for a commercial publishing house with the intention of producing a book for commercial consumption (read: for sale to the public) to be a commercial artist, regardless of the specific content of their work.
hey, i’m just starting out working towards working in digital publishing. going to university this fall to study dig pub and currently just reading everything i can about everything going on! i want to start myself off learning as much as i can on my own about platforms and mark up languages before university begins. so since this blog seems like a safe haven for dig pub newbies, thought i’d ask… can anyone point me in the right direction in terms of which XML editor and resource would be good for a beginner, also any books i can study on basic HTML and CSS as well as on InDesign? thanks a lot and please ignore/forgive if this was the wrong forum to post this!
@ Tanushri
Hm. One of the reasons I didn’t link to a particular XML editor is because I’m still learning myself—I’m not prepared to endorse one over the other, and the tools are still in the early days, at least as they pertain to authors and editors. But the first piece of software I’m looking into is going to be Oxygen XML Author.
As for InDesign, HTML, CSS, and XML in general, there are plenty of great resources out there, particularly from places like Peachpit Press or the great tutorials at Lynda.com.
I work for a legal and regulatory publisher. We actually made the switch to SGML before XML was even an option. The reporters and editors of our periodicals work in SGML in a highly customized environment. But of course, our books division relies entirely on outside authors and was allowed to outsource their production, Now, of course, we’re suffering the limitations of that decision– very few books in our electronic libraries– and are only now bringing them into the SGML fold.
It’s been very frustrating as an ebook reader to suffer the weird formatting errors (like funky hyphen- ation) and
know exactly how they got there. Single source is the way to go!
I especially like your point about bringing a lot of it back in-house. Hm, must ponder this further….
hey, thanks a lot! will definitely check those out and hopefully make sense of all this!
Righteous! I was just asking Hartwell about source control and versioning the other week. As with most questions about production at big old publishing companies, I was left with my jaw on the floor wondering why the small mammals haven’t already eaten up all the publisher’s eggs.
Personally, I’d recommend authors do their writing in one of the low-complexity ASCII markup languages like Markdown or reStructuredText. Those make it easy to re-read without getting poked in the eye by angle brackets. And a simple Perl or Python script outputs HTML or XML.
[...] On Sleekness — Pablo Defendini (of Tor.com fame) on production techniques, creative destruction, and professional sleekness. Fascinating stuff. [...]
Pablo, that all sounds good in principle — or maybe I’m just smug because I’ve been doing DTP since I was in high school in the 80s — but I get to the XML part and I have no idea what you’re talking about. And I say that as somebody who’s been writing software around XML since the mid-90s.
Every time I’ve used XML I’ve used it for something different: catalog records for Cambridge University Press, machining process plans for Boeing, biochemical metadata for Amgen and Genentech. And every time we’ve made up our own, task-specific dialect.
So should I be using ODF? DocBook? MS Office Open XML? Whatever it is that Apple’s Pages puts out? (Doesn’t play well with version control, Pages, sadly.)
Saying “use XML”, from here that’s like saying “use the internal combustion engine.” Okay, but should it run on tracks? Or should it float? Should it have wings? Propellers? Maybe it should have legs?
DocBook, or even better, DTBook, I should think (certainly not whatever crap markup Office or Pages spews forth). But that’s way beyond the scope of this post, really. It’s up to production departments to do their homework and figure this stuff out.
Great, great post.
@Ryan Chapman: if I may build a bit on Pablo’s comment, people will pay money for your production skills if that means that your production skills let them have the best possible reading experience for their favourite reading device (be it a paperback, a kindle, an iPhone, a next-big-thing, …), and XML simplifies this a lot.
…although I must agree that it will not be easy to have authors shift to XML.
Having copyedited hundreds of now-published manuscripts in virtually every trade genre, there is no way I would trust authors to produce a standards-compliant XML file. These people generally don’t know how to use a semicolon correctly
There’s no reason XML markup can’t be combined with copyediting. Let the authors create. Leave the technical details to the technical people = better results all around.
Most authors don’t seem to know how to use MS Word properly, either, yet they do keep trying . . .
It seems like there’s an opportunity here for someone to make an idiot-proof word processor that makes semantic markup easy to understand and apply, discourages unhelpful wysiwyg styling, has built-in version control with a change-tracking and commenting interface for editors, robust citation management (with Zotero integration) so that editing notes and bibliographies becomes less of a nightmare, and outputs clean XML. Lightweight, suitable to run on a netbook or iPad. Designed for long-document production, not for creating miscellaneous office documents.
So, uh, could you get on that, you programmer people?
[...] (if somewhat snarky) post this week by Pablo Defendini, producer and blogger at Tor.com, at The New Sleekness: [B]ig publishers outsource a large part of these services… They’ve found that cutting out [...]
There’s a middle ground between manual typewriter in a cabin in the woods and authors originating mss. in standards-compliant XML. I’m with Rebecca on the inability of authors to write a parseable English sentence without outside assistance, let alone conceptualizing their pearls in terms of how they fit into a markup language’s conceits. But what they do seem to be able to do a half-assed job of is using a Word template furnished by the publisher. Once the copyeditor is done, the now rules-compliant ms. can be the input to an XML-based processing chain, and all is well with the world.
I edit for one major publisher who has standardized on this process, and I have to say it works pretty well. Authors are shielded from markup languages; editors are shielded from the chaos of unformatted mss.
[...] great post by Pablo Defendini spaked some thoughts on the production in publishing and the changes it will (well, should) [...]
I spent most of the ’90s trying to convince authors to use SGML, then XML…finally gave up. I was thinking too much like a programmer/systems analyst at the time. Most authors are not going to use XML (unless they write for a niche publisher in a technical field). Forget about it. Choose the right battle to fight. Better to focus on the in-house workflow, which is manageable. I like the concept of a Word template that translates well to XML for in-house use.
[...] Andrew Malkin at Publishing Perspectives, the other from Tor.com’s Pablo Defendini at The New Sleekness. Despite a good 15 years, give or take, separating the three of us (I’m declaring Andrew the [...]
[...] at The New Sleakness there is a good overview of the changes in production at major houses. This holds true at every [...]