Article View: adobe.incopy.windows
Article #194InDesign/InCopy Workflow Issue
From: Bobbie_Hartzler
Date: Thu, 14 Sep 2006 13:22
Date: Thu, 14 Sep 2006 13:22
13 lines
1724 bytes
1724 bytes
It appears that the InDesign/InCopy workflow was designed for content to be entered by InCopy users and the Graphics/Final Formatting to be handled by InDesign users. In our situation the InDesign users create the graphics/templates etc. We then send them in Word all of the content which they then flow into InDesign. We then use InCopy to make final edits. We are then responsible for the final printed document, which means if we notice issues from the InDesign side we have to work with the InDesign staff to make those changes. We are having alot of frustration with this setup as there are times where we cannot see headers/footers etc. from the InCopy side, so have to go back to the InDesign staff to see the headers/footers. My question is this -- are we trying to use InDesign/InCopy in a way it was never designed to handle? It seems that in most cases the staff using InDesign are also responsible for the final production... and in our case it is the InCopy users who are responsible for the final production which I am thinking is the basis for alot of the frustration we are feeling> Any thoughts? Thanks, Bobbie
Technical Details
Message-ID:
<3bc19de7.-1@webcrossing.la2eafNXanI>Path:
arc1-ca.pugleaf.net!g2news2.google.com!news3.google.com!news4.google.com!news.glorb.com!news.buerger.net!open-news-network.org!news.isoc.lu!webcrossingShow Full Headers
Complete Article Headers
X-Google-Thread: 1efea4,f23a182439761ca9 X-Google-Attributes: gid1efea4,public X-Google-Language: ENGLISH,ASCII-7-bit From: Bobbie_Hartzler@adobeforums.com Path: arc1-ca.pugleaf.net!g2news2.google.com!news3.google.com!news4.google.com!news.glorb.com!news.buerger.net!open-news-network.org!news.isoc.lu!webcrossing Newsgroups: adobe.incopy.windows Subject: InDesign/InCopy Workflow Issue Message-ID: <3bc19de7.-1@webcrossing.la2eafNXanI> Date: Thu, 14 Sep 2006 06:22:16 -0700 Lines: 27 MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit