The other week a customer who builds their Sunday newspaper advertising insert with InDesign asked me if they could use use the Contact Sheet Script to make an InDesign contact sheet out of individual INDD files. I thought it was a great idea, and didn’t see why it shouldn’t be possible, considering that IDCS3 can now place INDD files.
I tried the script on it’s own, but it doesn’t recognize INDD files without a bit of tweaking. Here’s the solution:
- Locate the file called “WasScriptLibrary.jsx” on your hard drive and open it with the ExtendScript Toolkit application or your favorite script editor.
- Locate this string in line 755:
WasLib.fileFilters.putValue( “Contact Sheet”,”PNG,JPG,JPEG,TIF,TIFF,GIF,AI,PSD,PDF,EPS,EPSF” );
- Change the string to:
WasLib.fileFilters.putValue( “Contact Sheet”,”PNG,JPG,JPEG,TIF,TIFF,GIF,AI,PSD,PDF,EPS,EPSF,INDD” );
This allows INDD files to be included in InDesign contact sheets. Note that it places different file sizes at the same dimensions and always places the first page of the INDD file. Hope that helps!
I don’t know how common this is, but a customer recently asked me how to migrate a tracked PDF review in Acrobat from one computer to another. Scenarios include upgrading from Acrobat 7 to Acrobat 8, upgrading to a new computer, or tracking reviews from a laptop if you travel. If this sounds interesting, here’s the solution:
- Copy the file "Workflows" from this location on the old Mac HD/users/username/Library/Preferences/Acrobat/(version number)/Collab/Workflows to the same location on the new machine. The file path on Windows should be similar under the "Documents and Settings" folder.
- Relaunch Acrobat.
- Now copy the tracked PDFs from the old machine to the new machine. If the PDFs have the exact same file path on the new machine as they did on the old machine, then you’re done. If they don’t have the same file path, then just click their filename in the Tracker window and Acrobat will prompt you to tell it the new file path.
That should take care of it!
As a follow-up to my recent post about new tools to help you migrated from GoLive to Dreamweaver (if you want to) I wanted to offer an extra tip that will hopefully help some of you. I recently learned that the GL2DW extension assumes (for better or worse) that your GoLive site is in good working order and using the new site folder organization scheme that’s been in use for the last few versions.
If that’s not the case, the GL2DW extension can hiccup in the conversion process. To tidy things up before running the extension, open your site in GoLive and choose Site>Convert Site to New Structure. If the menu command is grayed out you’re in the clear. If it’s available, you should let ‘er rip.
GoLive is not dead (you’ll be seeing a new version layer this year) and you don’t have to switch if you don’t want to, but if you’re thinking about migrating from GoLive to Dreamweaver, then there are some good resources you need to know about. Click on over to http://www.adobe.com/products/dreamweaver/switch/ and check out the goods, including a 17-page migration guide written by me (Adam) and my long-time writing partner and GoLive expert, Lynn Grillo. The migration guide supports a new extension that is included with Dreamweaver CS3 that helps convert your GoLive sites to be Dreamweaver-ready. Please let us know if these resources are helpful.
If you’re using GoLive and don’t plan to switch to Dreamweaver, we also want to hear from you! Is it emotional? A specific couple of features? A certain workflow? Let us know!