Harbs - thanks for the reply. But actually, what I'm asking is the other way around --

I want to work in InDesign CS5 and have the editor open the .indd file in InCopy 5.5 on a continuing basis. This is a magazine and we will be both working on the file concurrently / off and on via dropbox.

So, it's not something I would just save down using IDML or convert once . . . it's an ongoing back & forth. But her InCopy app is higher level than the Indesign file version, not the other way around.

Does anyone know if Adobe has an official position on this?

Thanks Bob - will test and let you know for future ref.

Horst,

I decided not to try using CS 5.5 and CS5 together for InCopy. Instead, we use a dropbox network. We have a shared folder on Dropbox and the InDesign file is in there so the client can open the file using InCopy.

It sounds like there would be problems because technically, we're each accessing a separate copy of the file on our own machines and then dropbox is syncing the file to the cloud and back to each other's machines every few minutes. But, it works because the client is only changing the .icml links and when they're done I have to just update my links and it all works.

The drawback is that the InDesign file is available so the client can open it in InDesign if they wish. But I made my client promise not to do that and so far they haven't. You have to decide whether you can trust your client to leave the file alone.

It's also important that you have a backup of your dropbox folder, such as a time machine backup. Otherwise the client can inadvertently delete the project files and they will be gone from your computer also. But if you have a local backup you're protected against this.

I hope this helps! Let me know how it goes.

Matt

I have both CS5.5 and CS5 for InDesign. But my client has InCopy CS 5.5.

I use InDesign CS 5.0 for this client because the other designer and client don't have 5.5. But the editors use InCopy 5.5 on my CS 5.0 .indd files.

Again, this is with the dropbox workflow, which simulates a local server-based workflow.

I have successfully used the email package workflow in the past but we were all on CS4. The editor never bought InCopy CS5 until after 5.5 came out so they couldn't buy 5.0.

As I understand it everybody needs to be on the same version and probably platform (Mac) as well. Any changes to your file names or locations has a disastrous effect on the ability to re-link the edited package files, so make sure you know where you want the files and what they will be called. You can't rename them R1, R2 etc. while you're using the Incopy package workflow.

I'll have to ask my client to participate, so it may be a couple of days. But, we will try and see what happens.