<?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: Building an Index Using Character Styles or External Word List</title>
	<atom:link href="http://indesignsecrets.com/building-an-index-using-character-styles-or-external-word-list.php/rss2" rel="self" type="application/rss+xml" />
	<link>http://indesignsecrets.com/building-an-index-using-character-styles-or-external-word-list.php</link>
	<description>InDesignSecrets Blog and Podcast</description>
	<pubDate>Thu, 04 Dec 2008 20:55:28 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Damian</title>
		<link>http://indesignsecrets.com/building-an-index-using-character-styles-or-external-word-list.php#comment-470088</link>
		<dc:creator>Damian</dc:creator>
		<pubDate>Mon, 10 Nov 2008 12:28:46 +0000</pubDate>
		<guid isPermaLink="false">http://indesignsecrets.com/?p=1811#comment-470088</guid>
		<description>Just used this most helpful script but struggled initially. The character styles I wanted to use for the index were grouped in a sub folder in my character styles palette and the script kicked out an error. Moved the styles to the root level of the palette and viola! Magnifique!

Damian</description>
		<content:encoded><![CDATA[<p>Just used this most helpful script but struggled initially. The character styles I wanted to use for the index were grouped in a sub folder in my character styles palette and the script kicked out an error. Moved the styles to the root level of the palette and viola! Magnifique!</p>
<p>Damian</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roland</title>
		<link>http://indesignsecrets.com/building-an-index-using-character-styles-or-external-word-list.php#comment-468753</link>
		<dc:creator>Roland</dc:creator>
		<pubDate>Thu, 25 Sep 2008 10:02:23 +0000</pubDate>
		<guid isPermaLink="false">http://indesignsecrets.com/?p=1811#comment-468753</guid>
		<description>I need to make an index (first ever for me) and this script seems to be just the thing I need, but I have two questions:
Can the script search for multi-word keywords (example: radiator coupling) and create multi-word index-words without having to do a find &#38; replace on the word list my customer will have to supply?

And, is it preferable to have words that have multiple spellings or abbreviations mentioned once using the &#62; operator, or to simply mention every spelling?</description>
		<content:encoded><![CDATA[<p>I need to make an index (first ever for me) and this script seems to be just the thing I need, but I have two questions:<br />
Can the script search for multi-word keywords (example: radiator coupling) and create multi-word index-words without having to do a find &amp; replace on the word list my customer will have to supply?</p>
<p>And, is it preferable to have words that have multiple spellings or abbreviations mentioned once using the &gt; operator, or to simply mention every spelling?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JT</title>
		<link>http://indesignsecrets.com/building-an-index-using-character-styles-or-external-word-list.php#comment-467214</link>
		<dc:creator>JT</dc:creator>
		<pubDate>Fri, 01 Aug 2008 19:29:39 +0000</pubDate>
		<guid isPermaLink="false">http://indesignsecrets.com/?p=1811#comment-467214</guid>
		<description>I solved my problem by using a GREP search and the IndexMatic script. Here's how, in case anyone reading this post has the same problem:

Again, the format is:

Doctor Name [tab] City, ST [tab] Phone Number

For the index, I care only about the name. The names are already formatted as I need them, I just need to get them into an index.

I do a GREP find-and-replace with the following search string:
&lt;code&gt;^[(backslash)l(backslash)u(backslash)d, (backslash).-"'(backslash)((backslash))]+&lt;/code&gt;

(Sorry, but my backslash characters get munged when I post.)

This finds strings starting at the beginning of a paragraph, and consisting of upper- and lowercase letters, commas, spaces, periods, hyphens, single- and double quotes, parentheses, and digits (for the heck of it): characters that appear in people's names in Roman-based languages. When InDesign encounters the tab character, it stops the match. I restrict this search to text with the paragraph style I applied to all the listings.

I replace this string with a special character style. I include a special color with this character style so it will be easy to see what has been matched and what hasn't. Then I run the IndexMatic script on this character style.

It only took a few seconds for InDesign to apply this character style to 6200+ names, and about 10 minutes for IndexMatic to crank out the index. Compare that to hours doing it by hand or even with a keystroke-saving macro.

I couldn't have done it without stuff I learned from this site, so… thanks! :)</description>
		<content:encoded><![CDATA[<p>I solved my problem by using a GREP search and the IndexMatic script. Here&#8217;s how, in case anyone reading this post has the same problem:</p>
<p>Again, the format is:</p>
<p>Doctor Name [tab] City, ST [tab] Phone Number</p>
<p>For the index, I care only about the name. The names are already formatted as I need them, I just need to get them into an index.</p>
<p>I do a GREP find-and-replace with the following search string:<br />
<code>^[(backslash)l(backslash)u(backslash)d, (backslash).-"'(backslash)((backslash))]+</code></p>
<p>(Sorry, but my backslash characters get munged when I post.)</p>
<p>This finds strings starting at the beginning of a paragraph, and consisting of upper- and lowercase letters, commas, spaces, periods, hyphens, single- and double quotes, parentheses, and digits (for the heck of it): characters that appear in people&#8217;s names in Roman-based languages. When InDesign encounters the tab character, it stops the match. I restrict this search to text with the paragraph style I applied to all the listings.</p>
<p>I replace this string with a special character style. I include a special color with this character style so it will be easy to see what has been matched and what hasn&#8217;t. Then I run the IndexMatic script on this character style.</p>
<p>It only took a few seconds for InDesign to apply this character style to 6200+ names, and about 10 minutes for IndexMatic to crank out the index. Compare that to hours doing it by hand or even with a keystroke-saving macro.</p>
<p>I couldn&#8217;t have done it without stuff I learned from this site, so… thanks! <img src='http://indesignsecrets.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Blatner</title>
		<link>http://indesignsecrets.com/building-an-index-using-character-styles-or-external-word-list.php#comment-466609</link>
		<dc:creator>David Blatner</dc:creator>
		<pubDate>Wed, 16 Jul 2008 14:49:05 +0000</pubDate>
		<guid isPermaLink="false">http://indesignsecrets.com/?p=1811#comment-466609</guid>
		<description>Robert: Also, make sure you are choosing "longest string" from the Search For pop-up menu. If you apply the character style to "silly rabbit" and use "alphabetic words," then you will get two entries ("silly" and "rabbit"). But if you choose "longest string" then you get one entry.</description>
		<content:encoded><![CDATA[<p>Robert: Also, make sure you are choosing &#8220;longest string&#8221; from the Search For pop-up menu. If you apply the character style to &#8220;silly rabbit&#8221; and use &#8220;alphabetic words,&#8221; then you will get two entries (&#8221;silly&#8221; and &#8220;rabbit&#8221;). But if you choose &#8220;longest string&#8221; then you get one entry.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marc</title>
		<link>http://indesignsecrets.com/building-an-index-using-character-styles-or-external-word-list.php#comment-466599</link>
		<dc:creator>Marc</dc:creator>
		<pubDate>Wed, 16 Jul 2008 08:32:58 +0000</pubDate>
		<guid isPermaLink="false">http://indesignsecrets.com/?p=1811#comment-466599</guid>
		<description>Robert said: &lt;em&gt;&lt;strong&gt;Would it be possible to respect nonbreaking hyphens and nonbreaking spaces to solve this?  A second thing: words containing a descretionary hyphen do not appear at all in the index.&lt;/strong&gt;&lt;/em&gt;

Good point. I've to add some extra parameters in the dialog to let users extend the GREP search scope.

That's easy, but I need some time to analyse the different cases.</description>
		<content:encoded><![CDATA[<p>Robert said: <em><strong>Would it be possible to respect nonbreaking hyphens and nonbreaking spaces to solve this?  A second thing: words containing a descretionary hyphen do not appear at all in the index.</strong></em></p>
<p>Good point. I&#8217;ve to add some extra parameters in the dialog to let users extend the GREP search scope.</p>
<p>That&#8217;s easy, but I need some time to analyse the different cases.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marc</title>
		<link>http://indesignsecrets.com/building-an-index-using-character-styles-or-external-word-list.php#comment-466598</link>
		<dc:creator>Marc</dc:creator>
		<pubDate>Wed, 16 Jul 2008 08:24:11 +0000</pubDate>
		<guid isPermaLink="false">http://indesignsecrets.com/?p=1811#comment-466598</guid>
		<description>Robert said: &lt;em&gt;&lt;strong&gt;I tried the two GREP-searches you suggested on “Meißner” and in both cases it finds “Mei” and “ner” but not the sharp s.&lt;/strong&gt;&lt;/em&gt;

OK, here we have the culprit !! On Mac OS, it seems that InDesign DOES NOT recognize &lt;strong&gt;ß&lt;/strong&gt; or other extra-Ascii latin characters AS a word letter!

If other Mac users confirm that point, that's a InDesign bug, because the GREP &lt;strong&gt;[[:alpha:]]&lt;/strong&gt; (Posix) and &lt;strong&gt;&lt;em&gt;antislash&lt;/em&gt; w&lt;/strong&gt;  are supposed to match any alphabetic/word letter.

So, I've to rewrite the GREP command to get round the bug...</description>
		<content:encoded><![CDATA[<p>Robert said: <em><strong>I tried the two GREP-searches you suggested on “Meißner” and in both cases it finds “Mei” and “ner” but not the sharp s.</strong></em></p>
<p>OK, here we have the culprit !! On Mac OS, it seems that InDesign DOES NOT recognize <strong>ß</strong> or other extra-Ascii latin characters AS a word letter!</p>
<p>If other Mac users confirm that point, that&#8217;s a InDesign bug, because the GREP <strong>[[:alpha:]]</strong> (Posix) and <strong><em>antislash</em> w</strong>  are supposed to match any alphabetic/word letter.</p>
<p>So, I&#8217;ve to rewrite the GREP command to get round the bug&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eugene Tyson</title>
		<link>http://indesignsecrets.com/building-an-index-using-character-styles-or-external-word-list.php#comment-466597</link>
		<dc:creator>Eugene Tyson</dc:creator>
		<pubDate>Wed, 16 Jul 2008 07:52:36 +0000</pubDate>
		<guid isPermaLink="false">http://indesignsecrets.com/?p=1811#comment-466597</guid>
		<description>Well, I missed loads of this and I caught up this morning. Seems like the preservelocalformatting thing might work after all. 

Nested styles need a general rule to be applied don't they? So if it was the first word of a sentence or a em space text em space that would apply the nested style. I'm guessing it's for body text, but the nested style has to have some trigger.

Is it not possible to GREP search the triggers and then apply a character style. You can find in between em spaces for example and you could apply a style to the text that you find. It wouldn't affect the nested style either.

It's just a matter of searching your text using the criteria you set up in the nested styles.

You could then technically use the FindChangebyList that ships with CS3 to find all the nested styles and apply the style that you want, in one big swoop.

Does any of that sound doable?</description>
		<content:encoded><![CDATA[<p>Well, I missed loads of this and I caught up this morning. Seems like the preservelocalformatting thing might work after all. </p>
<p>Nested styles need a general rule to be applied don&#8217;t they? So if it was the first word of a sentence or a em space text em space that would apply the nested style. I&#8217;m guessing it&#8217;s for body text, but the nested style has to have some trigger.</p>
<p>Is it not possible to GREP search the triggers and then apply a character style. You can find in between em spaces for example and you could apply a style to the text that you find. It wouldn&#8217;t affect the nested style either.</p>
<p>It&#8217;s just a matter of searching your text using the criteria you set up in the nested styles.</p>
<p>You could then technically use the FindChangebyList that ships with CS3 to find all the nested styles and apply the style that you want, in one big swoop.</p>
<p>Does any of that sound doable?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert</title>
		<link>http://indesignsecrets.com/building-an-index-using-character-styles-or-external-word-list.php#comment-466596</link>
		<dc:creator>Robert</dc:creator>
		<pubDate>Wed, 16 Jul 2008 06:48:08 +0000</pubDate>
		<guid isPermaLink="false">http://indesignsecrets.com/?p=1811#comment-466596</guid>
		<description>Did some more testing with the names and found that there is no way to get two (or more) words into one line in the index. Especially in Germany compound names (like Leutheusser-Schnarrenberger) are very common and it is not possible to keep them together. Would it be possible to respect nonbreaking hyphens and nonbreaking spaces to solve this? 

A second thing: words containing a descretionary hyphen do not appear at all in the index.

Robert</description>
		<content:encoded><![CDATA[<p>Did some more testing with the names and found that there is no way to get two (or more) words into one line in the index. Especially in Germany compound names (like Leutheusser-Schnarrenberger) are very common and it is not possible to keep them together. Would it be possible to respect nonbreaking hyphens and nonbreaking spaces to solve this? </p>
<p>A second thing: words containing a descretionary hyphen do not appear at all in the index.</p>
<p>Robert</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert</title>
		<link>http://indesignsecrets.com/building-an-index-using-character-styles-or-external-word-list.php#comment-466592</link>
		<dc:creator>Robert</dc:creator>
		<pubDate>Wed, 16 Jul 2008 05:49:41 +0000</pubDate>
		<guid isPermaLink="false">http://indesignsecrets.com/?p=1811#comment-466592</guid>
		<description>David,
sorry, in my hurry to test the script I ignored the case formating thing.

Marc,
I tried the two GREP-searches you suggested on "Meißner" and in both cases it finds "Mei" and "ner" but not the sharp s.

Robert</description>
		<content:encoded><![CDATA[<p>David,<br />
sorry, in my hurry to test the script I ignored the case formating thing.</p>
<p>Marc,<br />
I tried the two GREP-searches you suggested on &#8220;Meißner&#8221; and in both cases it finds &#8220;Mei&#8221; and &#8220;ner&#8221; but not the sharp s.</p>
<p>Robert</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marc</title>
		<link>http://indesignsecrets.com/building-an-index-using-character-styles-or-external-word-list.php#comment-466583</link>
		<dc:creator>Marc</dc:creator>
		<pubDate>Tue, 15 Jul 2008 22:20:15 +0000</pubDate>
		<guid isPermaLink="false">http://indesignsecrets.com/?p=1811#comment-466583</guid>
		<description>Dave and David, thank you for your suggestions.

The first method -- checking the  &lt;strong&gt;appliedNestedStyle&lt;/strong&gt; Text property on each character -- could be a solution for short documents. But that's so frustrating!

The second method, based on a temporary "conversion" of the nested style into something that Find could see, is a genious idea.

Hmmm, I've to think about it...</description>
		<content:encoded><![CDATA[<p>Dave and David, thank you for your suggestions.</p>
<p>The first method &#8212; checking the  <strong>appliedNestedStyle</strong> Text property on each character &#8212; could be a solution for short documents. But that&#8217;s so frustrating!</p>
<p>The second method, based on a temporary &#8220;conversion&#8221; of the nested style into something that Find could see, is a genious idea.</p>
<p>Hmmm, I&#8217;ve to think about it&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
