<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Creating an Advertiser Index (or other difficult TOC)</title>
	<atom:link href="http://indesignsecrets.com/creating-and-advertiser-index-or-other-difficult-toc.php/rss2" rel="self" type="application/rss+xml" />
	<link>http://indesignsecrets.com/creating-and-advertiser-index-or-other-difficult-toc.php</link>
	<description>InDesignSecrets Blog and Podcast</description>
	<pubDate>Thu, 04 Dec 2008 20:26:12 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Molly</title>
		<link>http://indesignsecrets.com/creating-and-advertiser-index-or-other-difficult-toc.php#comment-470164</link>
		<dc:creator>Molly</dc:creator>
		<pubDate>Wed, 12 Nov 2008 21:37:03 +0000</pubDate>
		<guid isPermaLink="false">http://indesignsecrets.com/creating-and-advertiser-index-or-other-difficult-toc.php#comment-470164</guid>
		<description>Barbara, I've found that if the second heading text  starts further on the left than the top text, the second (bottom) appears before the first (top) in the TOC. I've had to do some fussing with text wrap to get it correct in the TOC. Hope this helps.
Molly</description>
		<content:encoded><![CDATA[<p>Barbara, I&#8217;ve found that if the second heading text  starts further on the left than the top text, the second (bottom) appears before the first (top) in the TOC. I&#8217;ve had to do some fussing with text wrap to get it correct in the TOC. Hope this helps.<br />
Molly</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BarbaraW</title>
		<link>http://indesignsecrets.com/creating-and-advertiser-index-or-other-difficult-toc.php#comment-469002</link>
		<dc:creator>BarbaraW</dc:creator>
		<pubDate>Wed, 08 Oct 2008 00:04:58 +0000</pubDate>
		<guid isPermaLink="false">http://indesignsecrets.com/creating-and-advertiser-index-or-other-difficult-toc.php#comment-469002</guid>
		<description>I am having problems the with TOC in CS2. It generates the correct page numbers but no matter what I have tried, switching heading levels by drag and drop or at the level option, when I update the TOC the second heading is above the first heading. Any ideas?
Thanks in advance</description>
		<content:encoded><![CDATA[<p>I am having problems the with TOC in CS2. It generates the correct page numbers but no matter what I have tried, switching heading levels by drag and drop or at the level option, when I update the TOC the second heading is above the first heading. Any ideas?<br />
Thanks in advance</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SueC</title>
		<link>http://indesignsecrets.com/creating-and-advertiser-index-or-other-difficult-toc.php#comment-158324</link>
		<dc:creator>SueC</dc:creator>
		<pubDate>Fri, 19 Oct 2007 17:10:10 +0000</pubDate>
		<guid isPermaLink="false">http://indesignsecrets.com/creating-and-advertiser-index-or-other-difficult-toc.php#comment-158324</guid>
		<description>The indexing problem in CS3 has me scared. I do lots of books and often need to do indexes. Has the problem been addressed? Should I stick with CS2 for now? 

Here's my question about indexes, if I have the editor tag the index words in the text with a character style (that would be the same style visually as my body text in my doc), can I then use that style to generate the index tags I need to make an index? I am trying to avoid having to the tag all the words myself!</description>
		<content:encoded><![CDATA[<p>The indexing problem in CS3 has me scared. I do lots of books and often need to do indexes. Has the problem been addressed? Should I stick with CS2 for now? </p>
<p>Here&#8217;s my question about indexes, if I have the editor tag the index words in the text with a character style (that would be the same style visually as my body text in my doc), can I then use that style to generate the index tags I need to make an index? I am trying to avoid having to the tag all the words myself!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SueC</title>
		<link>http://indesignsecrets.com/creating-and-advertiser-index-or-other-difficult-toc.php#comment-158323</link>
		<dc:creator>SueC</dc:creator>
		<pubDate>Fri, 19 Oct 2007 17:05:56 +0000</pubDate>
		<guid isPermaLink="false">http://indesignsecrets.com/creating-and-advertiser-index-or-other-difficult-toc.php#comment-158323</guid>
		<description>This may need a new thread... I need to generate a "picture credits" list in the backmatter of a book. I would like the information to come from the file info fields on the photos. This is where we record it. I have just cut and pasted manually from the fields after clicking on "get file info" in the links palette. Too time consuming. Is there some way to do this automatically or with a script? (I have never used scripts and sure can't write one!) And related to this, is there a way to get captions recorded in file info into a document without cut and paste?</description>
		<content:encoded><![CDATA[<p>This may need a new thread&#8230; I need to generate a &#8220;picture credits&#8221; list in the backmatter of a book. I would like the information to come from the file info fields on the photos. This is where we record it. I have just cut and pasted manually from the fields after clicking on &#8220;get file info&#8221; in the links palette. Too time consuming. Is there some way to do this automatically or with a script? (I have never used scripts and sure can&#8217;t write one!) And related to this, is there a way to get captions recorded in file info into a document without cut and paste?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Blatner</title>
		<link>http://indesignsecrets.com/creating-and-advertiser-index-or-other-difficult-toc.php#comment-111869</link>
		<dc:creator>David Blatner</dc:creator>
		<pubDate>Wed, 29 Aug 2007 22:09:54 +0000</pubDate>
		<guid isPermaLink="false">http://indesignsecrets.com/creating-and-advertiser-index-or-other-difficult-toc.php#comment-111869</guid>
		<description>Yes, I have heard of a lot of people having troubles with creating indexes in CS3... particularly when indexing a whole book (multiple docs in a book panel). Indexing a single document seems to work better for some folks.</description>
		<content:encoded><![CDATA[<p>Yes, I have heard of a lot of people having troubles with creating indexes in CS3&#8230; particularly when indexing a whole book (multiple docs in a book panel). Indexing a single document seems to work better for some folks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Minh</title>
		<link>http://indesignsecrets.com/creating-and-advertiser-index-or-other-difficult-toc.php#comment-111167</link>
		<dc:creator>Minh</dc:creator>
		<pubDate>Tue, 28 Aug 2007 23:58:56 +0000</pubDate>
		<guid isPermaLink="false">http://indesignsecrets.com/creating-and-advertiser-index-or-other-difficult-toc.php#comment-111167</guid>
		<description>My company spent a lot of money upgrading from CS2 to CS3. Unfortunately we started our catalog in CS2 and finished it in CS3 which, from what I read, is where the issue lies. I too am having HUGE problems indexing with CS3. Topics are not showing up, page numbers are wrong and  appear in the wrong order. 

However, I do have a workaround I'd like to suggest. You have to export all your CS3 files to Adobe's 'Interchange" format (.inx), then open each .inx file with CS2, and then do a "Save As" to a CS2 file. The file will lose any  templates or styles that are new in CS3, but it should keep all the text and index tags intact. Recreate your book in CS2 and bring in all your newly saved CS2 files. The process was a pain in the *ss, but it worked. All the topics appear and the page numbers are intact and read in the correct order. Once you create your index you can add it back in to your final CS3 book for printing.

Adobe, you'd better fix this issue soon!</description>
		<content:encoded><![CDATA[<p>My company spent a lot of money upgrading from CS2 to CS3. Unfortunately we started our catalog in CS2 and finished it in CS3 which, from what I read, is where the issue lies. I too am having HUGE problems indexing with CS3. Topics are not showing up, page numbers are wrong and  appear in the wrong order. </p>
<p>However, I do have a workaround I&#8217;d like to suggest. You have to export all your CS3 files to Adobe&#8217;s &#8216;Interchange&#8221; format (.inx), then open each .inx file with CS2, and then do a &#8220;Save As&#8221; to a CS2 file. The file will lose any  templates or styles that are new in CS3, but it should keep all the text and index tags intact. Recreate your book in CS2 and bring in all your newly saved CS2 files. The process was a pain in the *ss, but it worked. All the topics appear and the page numbers are intact and read in the correct order. Once you create your index you can add it back in to your final CS3 book for printing.</p>
<p>Adobe, you&#8217;d better fix this issue soon!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anne-Marie</title>
		<link>http://indesignsecrets.com/creating-and-advertiser-index-or-other-difficult-toc.php#comment-88174</link>
		<dc:creator>Anne-Marie</dc:creator>
		<pubDate>Wed, 18 Jul 2007 18:46:02 +0000</pubDate>
		<guid isPermaLink="false">http://indesignsecrets.com/creating-and-advertiser-index-or-other-difficult-toc.php#comment-88174</guid>
		<description>Hi Kevin, sorry, have not been following that issue in the forums. Is it a problem with ID CS2 book files that have been converted to CS3, or *any* CS3 book files?

In general I'd recommend that people finish projects in the same version of the software they started with, if at all possible. But if CS3 is having problems with indexing even new CS3 docs, that advice wouldn't help either.</description>
		<content:encoded><![CDATA[<p>Hi Kevin, sorry, have not been following that issue in the forums. Is it a problem with ID CS2 book files that have been converted to CS3, or *any* CS3 book files?</p>
<p>In general I&#8217;d recommend that people finish projects in the same version of the software they started with, if at all possible. But if CS3 is having problems with indexing even new CS3 docs, that advice wouldn&#8217;t help either.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Shilts</title>
		<link>http://indesignsecrets.com/creating-and-advertiser-index-or-other-difficult-toc.php#comment-88136</link>
		<dc:creator>Kevin Shilts</dc:creator>
		<pubDate>Wed, 18 Jul 2007 17:10:15 +0000</pubDate>
		<guid isPermaLink="false">http://indesignsecrets.com/creating-and-advertiser-index-or-other-difficult-toc.php#comment-88136</guid>
		<description>I am surprise no one is reporting the huge problems with Indexing and TOC generation with CS2 Books brought over the CS3. Lots of comments on Adobe's InDesign discussion board but no workaround yet. In my case, Indexing is not working at all. When you generate it, it leaves out lots of entries from the Index pallette and gives other the wrong page numbers. I have not experienced the TOC generation problems that others have reported, but I understand similar things are happening there. This is a big problem for Adobe, it makes CS3 useless for the production of publications with indexes.

Has anyone heard of when this will be fixed or what work-arounds are available, I have a 368-page catalog going to press Aug 20 and a worthless index.</description>
		<content:encoded><![CDATA[<p>I am surprise no one is reporting the huge problems with Indexing and TOC generation with CS2 Books brought over the CS3. Lots of comments on Adobe&#8217;s InDesign discussion board but no workaround yet. In my case, Indexing is not working at all. When you generate it, it leaves out lots of entries from the Index pallette and gives other the wrong page numbers. I have not experienced the TOC generation problems that others have reported, but I understand similar things are happening there. This is a big problem for Adobe, it makes CS3 useless for the production of publications with indexes.</p>
<p>Has anyone heard of when this will be fixed or what work-arounds are available, I have a 368-page catalog going to press Aug 20 and a worthless index.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Blatner</title>
		<link>http://indesignsecrets.com/creating-and-advertiser-index-or-other-difficult-toc.php#comment-25527</link>
		<dc:creator>David Blatner</dc:creator>
		<pubDate>Thu, 15 Feb 2007 15:14:52 +0000</pubDate>
		<guid isPermaLink="false">http://indesignsecrets.com/creating-and-advertiser-index-or-other-difficult-toc.php#comment-25527</guid>
		<description>Owen, I'm not sure what you mean. You &lt;em&gt;can&lt;/em&gt; take the text from any paragraph that is tagged with a paragraph style. My tip has to do with tagging things like pictures that don't have any styled paragraph you can "grab."</description>
		<content:encoded><![CDATA[<p>Owen, I&#8217;m not sure what you mean. You <em>can</em> take the text from any paragraph that is tagged with a paragraph style. My tip has to do with tagging things like pictures that don&#8217;t have any styled paragraph you can &#8220;grab.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Owen</title>
		<link>http://indesignsecrets.com/creating-and-advertiser-index-or-other-difficult-toc.php#comment-25510</link>
		<dc:creator>Owen</dc:creator>
		<pubDate>Thu, 15 Feb 2007 13:34:44 +0000</pubDate>
		<guid isPermaLink="false">http://indesignsecrets.com/creating-and-advertiser-index-or-other-difficult-toc.php#comment-25510</guid>
		<description>Ye, sure, but you should be able to take the text in a section title and include it automatically in TOC.  The only workaround is (as above) to make non printing text box with the title in it.  This is double work, particularly on long docs...</description>
		<content:encoded><![CDATA[<p>Ye, sure, but you should be able to take the text in a section title and include it automatically in TOC.  The only workaround is (as above) to make non printing text box with the title in it.  This is double work, particularly on long docs&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
