Article View: adobe.indesign.featurerequests
Article #1820Re: Automatic Numbering
From: jack_zucker
Date: Thu, 04 Aug 2005 19:29
Date: Thu, 04 Aug 2005 19:29
5 lines
1398 bytes
1398 bytes
By the way, as I started working on my new instructional book, it became obvious that the workflow just does *NOT* support using MSWord for references and numbering. The problem is all the 1200 DPI PDF Files that are embedded as musical references. The only way the suggested MSWord workflow would work would be to completely finish the entire book text in Winword with placeholders for the graphics, then import it into indesign and add the graphics - A completely unrealistic workflow. I also downloaded the trial version of Virginia Systems InSeq to see if that would work. It's somewhat annoying because it forces you to type in a unique label for each destination reference which is part of what the software should do for you. Additionally, it didn't work correctly across chapters. Oh well.
Technical Details
Message-ID:
<2cd03ec9.49@webx.la2eafNXanI>Path:
arc1-ca.pugleaf.net!g2news1.google.com!news4.google.com!news.glorb.com!nntp.waia.asn.au!202.72.130.18.MISMATCH!quokka.wn.com.au!webxReferences:
<2cd03ec9.-1@webx.la2eafNXanI>Show Full Headers
Complete Article Headers
X-Google-Thread: 1efe7f,da8c03a4ee647133 X-Google-Attributes: gid1efe7f,public X-Google-Language: ENGLISH,ASCII-7-bit From: jack_zucker@adobeforums.com Newsgroups: adobe.indesign.featurerequests Subject: Re: Automatic Numbering Message-ID: <2cd03ec9.49@webx.la2eafNXanI> Date: Thu, 4 Aug 2005 12:29:27 -0700 References: <2cd03ec9.-1@webx.la2eafNXanI> Lines: 15 MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit Path: arc1-ca.pugleaf.net!g2news1.google.com!news4.google.com!news.glorb.com!nntp.waia.asn.au!202.72.130.18.MISMATCH!quokka.wn.com.au!webx