is now part of CreativePro.com!

*** From the Archives ***

This article is from June 4, 2006, and is no longer current.

Smart Export All to InCopy Scripts

7

The problem: InCopy users can’t edit any text in an InDesign layout until the designer has explicitly selected the text frames the editors need to work on and exported them to InCopy format. But InDesign’s “Export All Stories to InCopy” (seems like a logical choice, no?) exports every text frame on the master pages as well as the document pages to InCopy format. Which means that every folio, every header, every footer, etc. becomes an entry in the Assignments palette. And editors sometimes inadvertently edit master page text frames in InCopy. Not good.

So at the start of every project, designers have to manually export the frames (Export Selection to InCopy) they do want, one spread at a time. Oy!

Rick Johnson, a full-time illustrator and part-time AppleScript guru at Kalmbach Publishing in Wisconsin, has written a couple of in-house AppleScripts (links at the end) for the company’s designers that work around this problem. Rick and I are likethis, see, (Kalmbach is a training client of mine) so after a little of my arm-twisting and sweet-talking, and after getting permission from his employer, he has tweaked the scripts for general use and allowed us to post them on our site for downloading. Thank you, Rick and Kalmbach! Live long and prosper!

Before I describe the scripts, a couple notes of caution: First, these are AppleScripts (for InDesign CS2), so they’re Mac-only. Second, Rick is not a full-time AppleScript developer who can provide tech support for these. He’s got a full-time normal job! (If you’ve seen Kalmbach’s Model Railroader magazine, those lovely, intricate track diagrams and train renderings are his. He’s even written some Illustrator plug-ins to help create these.)

So if the scripts aren’t working right or you need something customized about them, you’re on your own. You could try posting a comment here with your question to see if a kind-hearted AppleScripter responds, but you’ll probably get a faster response if you post your question to the scripting forums for InDesign or InCopy on Adobe’s web site, where all the kind-hearted scripting geniuses hang out.

What the Scripts Do

The two Export All to InCopy scripts we’ve linked to below are essentially the same – I’ll explain their minor difference in a minute. They don’t come with ReadMe’s (just a lengthy tool tip) so read on!

In plain English, you tell the script which frames it shouldn’t touch – such as the ones on the master pages – and the script exports all the other text frames in the layout – every spread -in one operation. You prevent frames from being included in the ride by selecting them and giving them a Script Label of “Folio” or “no export.” Just type either phrase right into the Script Label palette while a frame(s) is selected. (David and I talked about the Script Label palette in Podcast #21.) It’s a lot faster to select and label a few master page text frames to exclude and then run the script to export the rest, than it is to do the manual export dance described above!

If you add more frames later on and want to export those too, running the same script exports just those new frames to InCopy format. Neither script exports image frames; you’ll have to do that manually or tweak the script.

Both scripts put all the InCopy story files into a “stories” folder at the same level as the .indd (InDesign layout) file, though it’s easy for even a non-scripter to edit the script to change the name of the folder or tell it to save the folder one or two levels “up” from the layout file. It names each InCopy file uniquely (layout name followed by the internal frame ID number) so you don’t have to worry about overwriting.

The difference: The only difference between the two scripts is what format they save the InCopy story in. Most CS2 users will want the stories exported as InCopy CS2 Documents (.incx), especially if their stories contain uniquely CS2 things like anchored objects or footnotes. They should use the “export stories to incx.scpt” script.

However, some CS2 users prefer to export their stories in the older InCopy CS Story format (.incd), since they’ve had file corruption problems with the .incx format and their InCopy CS2-using editors can still edit the older .incd files from within the CS2 layout. They lose the ability to retain footnotes in the stories and have trouble with some other CS2 text features, but they’ve tested it and it’s best for their workflow. So if you’re in that camp, you should use the “export stories to incd.scpt” script.

If you’re not sure how to install or run a script, it’s easy! Here’s our how-to.

Rick Johnson’s Export All to InCopy scripts:
Export_to_ICCS2.zip (contains the export stories to incx.scpt)
Export_to_ICCS1.zip (contains the export stories to incd.scpt)

Anne-Marie “Her Geekness” Concepción is the co-founder (with David Blatner) and CEO of Creative Publishing Network, which produces InDesignSecrets, InDesign Magazine, and other resources for creative professionals. Through her cross-media design studio, Seneca Design & Training, Anne-Marie develops ebooks and trains and consults with companies who want to master the tools and workflows of digital publishing. She has authored over 20 courses on lynda.com on these topics and others. Keep up with Anne-Marie by subscribing to her ezine, HerGeekness Gazette, and contact her by email at [email protected] or on Twitter @amarie
  • José Ramos says:

    Beautiful!!! It worked like a charm. Actually better, ‘cuz charms never work.
    Now, if I only had a script to unlink all stories in a given document, I’d be set. How hard can that be, right?

  • Don Ayer says:

    Just a word on that incx vs. incd issue. “CS2 features” are not the only things to avoid when using incd files in CS2.

    In CS1, text objects pasted inline with other text were exported as unique incd files.

    In CS2, text objects pasted inline with other text are exported as part of the main incx file.

    It seems CS2 does not recognize this important difference. When incd files are edited in CS2, these inline objects appear to be editable but CS2 does not know to save the changes to the objects’ own incd files. The changes are lost (with no error message) when the document is closed.

    The ID4.0.3 update claims to have fixed the incx corruption problem. Let’s hope so, because incd files are not the solution.

  • Pethr says:

    I´m using InCopy layer to export articles for InCopy. It requires some getting used to but if you have 3+ layers for various objects you´ll be up to speed pretty fast and you have absolute controll over what gets exported. Of course you also forget to export something from time to time because it is in different layer by mistake…

  • Bryan says:

    Worked great! It would be nice if there was a way to name the files, instead of just numberingn them after the original file name. Hard to identify them individually. I know you can click on the link and say go to content, but it’s not quite what I was looking for. But, i would highly recommend it! We will be switching to CS3 soon, and I hope it works there as well?

  • Bryan says:

    Has anyone found a solution for the script to work in CS3? I keep getting an error message. It’s a great script to have, and we have gotten spoiled with it in CS2, but now that we have switched to CS3 it is back to tedious ways of having to export each text box one at a time…. ARGGGG! Any clue on how to fix the script for CS3?

  • Its a shame that it doesn’t work in CS3! It looks like a huge time saver! Any info if it will be released for CS3?

  • Shamsky says:

    An alternative to this “Mac only” script is a Mac/Win product called CrossTalk. With Crosstalk and InCopy installed, the InCopy user can open the shared InDesign file and perform the necessary edits and saves. Check in and check out hassles are eliminated.

    I have been supporting 5 Crosstalk (& InCopy) licenses for my end users since InDesign CS. My technical copywriters make their edits directly to the InDesign master file using Crosstalk/InCopy for the various manuals that we maintain. No more time wasted importing and exporting between Word and InDesign.

    The makers of CrossTalk (CTRL-PS) supports all of the newer InCopy releases (up to CS4 as of this posting). They also provide technical support.

    The software company “Ctrl-ps” is based in Sweden, so you will need to contact them for payment arrangements. Their contact information is listed on their site.

    Sincerely,
    Shamsky

  • >