I would try rebuilding preferences, and also repairing permissions on your OS X (via Utilities > Disk Repair).

It just sounds like InDesign doesn't know which app should open which image type. Since it pulls that from your computer's OS, solving it may require work on both ends.

FWIW I have not seen this same issue on my Macs/PCs.

AM

Yay! Glad it's working for you now.

AM

Right! For the benefit of lurkers … you'll see that appear on a selected object when you've applied some sort of animation to the object. 

Starting in version CS3, you can make InCopy Packages that are expressly designed for remote editors. Much neater than trying to find the files yourself and zipping them up and making sure no one edits them while the outside editor has the stories. When the editor returns it (as an InDesign Package), the layout automatically updates w/their changes and checks in their stories.

Another solution is Dropbox (https://dropbox.com), a free program that adds a “My Dropbox” folder to your local hard drive. If you put your ID projects in there, and your editors also installed Dropbox, then the folder acts just like a server. It's really cool. I demo'd it working with ID and IC at the Print & ePublishing Conference last month. And I have three or four publishers using this solution after some training from me, even for in-house use (when local server connection is spotty or slow).

AM

Yes. Try exporting your INDD file to INX or IDML, then opening that INX or IDML file back up in the same version of ID. It'll open as an Untitled document. Save it with a new name.

Also try exporting just a spread's worth of stories. You may have a corrupt story file somewhere.

It's always possible that the document is healthy but just constructed very poorly. (I've seen some nightmares.) For example, every line or paragraph is in its own text frame. Or someone accidentally Pasted in Place 50+ times. Other than document corruption, that's the only think I could imagine that would make exporting all stories take so long. Even for long, complex documents, the export shouldn't take longer than a couple minutes, max.

AM

Is this a new thing … you used to be able to export a lot of stories in a normal amount of time, now it's very slow? Or is this the first time you're using InCopy? Or something in between?

What happens if you export just a page worth of stories? Does that take a long time too?

What happens if you create a new document, add a few different text frames, and choose Export All Stories … long time? Or not so long.

The trick is diagnosing if it's the document or the program or your computer.

AM

Weird … I've taught hundreds of IC/ID users, and a few months down the line, after they've done a project or three, they're like, “you'll take my copy of InCopy out of my cold dead hands …” LOL. They can't imagine going back to paper markup or whatever.

Eugene, that's the first time I've heard of InCopy users really not getting check-in/check-out. I know you've moved on, but for lurkers, you should know that it's a trivial little task (that allows multiple users to edit the same file at the same time, so it's powerful feature!) You just do a Check Out All when opening the file, and then that's all you have to worry about. When you close the doc, InCopy checks all stories back in for you automatically.

Funny … David hatest check-in/check-out too. On the other hand, he doesn't believe in working off the server either. While very few of my publisher clients would allow users (editors especially) to work on files locally.

I should mention that if you don't need the ability for two or more people (designer and editor, or 2, or 5, etc.) to work on the same INDD file concurrently, you could just equip your InCopy users with Ctrl-Publishing's CtrlCross-Talk https://www.ctrlpublishing.com/…..  That lets IC users open INDD files and start editing, no check-out/check-in required.

AM