<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Simplifying Complexity &#187; Tools</title>
	<atom:link href="http://www.vanarsdall-infodesign.com/category/tools/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.vanarsdall-infodesign.com</link>
	<description>Technical Communication Services and Resources from VanArsdall InfoDesign</description>
	<lastBuildDate>Tue, 07 Sep 2010 03:39:24 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>MadCap Flare Tip: Setting Up Concept Links in FrameMaker Files</title>
		<link>http://www.vanarsdall-infodesign.com/2010/04/25/madcap-flare-tip-setting-up-see-also-links-in-framemaker/</link>
		<comments>http://www.vanarsdall-infodesign.com/2010/04/25/madcap-flare-tip-setting-up-see-also-links-in-framemaker/#comments</comments>
		<pubDate>Sun, 25 Apr 2010 15:46:42 +0000</pubDate>
		<dc:creator>Eddie</dc:creator>
				<category><![CDATA[Help Development]]></category>
		<category><![CDATA[Information Development]]></category>
		<category><![CDATA[MadCap Software]]></category>
		<category><![CDATA[Online Publishing]]></category>
		<category><![CDATA[Single Sourcing]]></category>
		<category><![CDATA[Technical Writing]]></category>
		<category><![CDATA[Tools]]></category>
		<category><![CDATA[XML]]></category>
		<category><![CDATA[adobe framemaker]]></category>
		<category><![CDATA[content development]]></category>
		<category><![CDATA[flare]]></category>
		<category><![CDATA[framemaker]]></category>
		<category><![CDATA[help development]]></category>
		<category><![CDATA[import]]></category>
		<category><![CDATA[web content]]></category>

		<guid isPermaLink="false">http://www.vanarsdall-infodesign.com/?p=3514</guid>
		<description><![CDATA[In my last post, I discussed ways that you can build lists of related links in your MadCap Flare projects. I expressed a preference for concept links. If you share my enthusiasm for concept links and are importing FrameMaker content into Flare, you may want to pre-configure your source FrameMaker files to include Passthrough markers [...]]]></description>
			<content:encoded><![CDATA[<p></p><a name="top"></a>
<p>In my last post, I discussed ways that you can build lists of related links in your MadCap Flare projects. I expressed a preference for <em>concept links</em>.</p>
<p>If you share my enthusiasm for concept links and are importing FrameMaker content into Flare, you may want to pre-configure your source FrameMaker files to include <em>Passthrough</em> markers with special strings. When you import the marked FrameMaker content into Flare, the Passthrough markers convert to <em>concept</em> markers in the equivalent Flare topics. </p>
<p>You can then insert a concept link help control in each topic that contains the same marker and build a dynamic list of related topics. I described this process in the following post:</p>
<p><a href="http://www.vanarsdall-infodesign.com/2010/04/11/madcap-flare-tip-helping-users-find-related-information/" title="Link to post about Flare help controls" target="_self">MadCap Flare Tip: Helping Users Find Related Information</a></p>
<p>When preparing your FrameMaker files to include Passthrough markers, follow these steps:</p>
<ol>
<li>Add a custom Passthrough marker to each FrameMaker file. If you&#8217;re not sure how to set up markers in FrameMaker files, read this post:
<p><a href="http://www.vanarsdall-infodesign.com/2010/04/02/preparing-framemaker-files-for-importing-into-madcap-flare/" title="Link to post about FrameMaker file preparation" target="_self">Preparing FrameMaker Files for Importing into MadCap Flare</a></li>
<li>Insert a Passthrough marker in the heading of each topic that is related to the same concept.</li>
<li>Add the following string to the Passthrough marker definition:
<p><span class="tag">&#60;MadCap:concept term=&#8221;term&#8221; /&#62</span></li>
<li>Substitute &#8220;term&#8221; with <em>your</em> concept term, keeping the quotes (&#8220;&#8221;). Make sure that &#8220;MadCap&#8221; has an uppercase M and uppercase C.</li>
</ol>
<div class="note"><span class="notetext">Example:</span> If you want Flare to build a dynamic list of topics about <em>search tips</em>, add a Passthrough marker to the heading of each topic that&#8217;s related to search tips. Define each marker using this string:</p>
<p><span class="tag">&#60;MadCap:concept term=&#8221;search tips&#8221; /&#62</span></div>
<p>To ensure that the markers convert properly, enable the following Flare import settings. If you&#8217;re using an import file in your project, you&#8217;ll find these settings on the <strong>Options</strong> tab:</p>
<ul>
<li><strong>Enable &#8216;Passthrough&#8217; Markers</strong> = <strong>Checked</strong></li>
<li><strong>Passthrough Marker Format</strong> = <strong>XML</strong></li>
</ul>
<p><p><a href="#top">Back to top</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.vanarsdall-infodesign.com/2010/04/25/madcap-flare-tip-setting-up-see-also-links-in-framemaker/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Learn Flare Single Sourcing in Arlington, VA</title>
		<link>http://www.vanarsdall-infodesign.com/2009/05/10/advanced-flare-single-sourcing-class-coming-to-arlington-va/</link>
		<comments>http://www.vanarsdall-infodesign.com/2009/05/10/advanced-flare-single-sourcing-class-coming-to-arlington-va/#comments</comments>
		<pubDate>Sun, 10 May 2009 21:49:27 +0000</pubDate>
		<dc:creator>Eddie</dc:creator>
				<category><![CDATA[Help Development]]></category>
		<category><![CDATA[MadCap Software]]></category>
		<category><![CDATA[Online Publishing]]></category>
		<category><![CDATA[Print Publishing]]></category>
		<category><![CDATA[Single Sourcing]]></category>
		<category><![CDATA[Tools]]></category>
		<category><![CDATA[Training]]></category>
		<category><![CDATA[madcap flare]]></category>

		<guid isPermaLink="false">http://www.vanarsdall-infodesign.com/?p=2268</guid>
		<description><![CDATA[Though I teach most MadCap Flare classes online these days, I am scheduled to teach a live Flare Single Sourcing class on June 3, 2009, in Arlington, VA. About the single sourcing class The single sourcing class is a one-day, hands-on session that uses a scenario-based model to teach you how to single source your [...]]]></description>
			<content:encoded><![CDATA[<p></p><p>Though I teach most MadCap Flare classes online these days, I am scheduled to teach a live Flare Single Sourcing class on June 3, 2009, in Arlington, VA.</p>
<h2>About the single sourcing class</h2>
<p>The single sourcing class is a one-day, hands-on session that uses a scenario-based model to teach you how to single source your content with Flare. The course includes an overview of single sourcing for those who are new to the concept. It also includes advanced tips and best practices for experienced information developers.</p>
<p>In the course scenario, One Source Hotels is expanding to open two resort hotels: one in the US and another in Canada. The company needs to develop policies and procedures for the new hotels. They need to single source one set of content to account for differences between the customs and the legal requirements of the two countries. They need to publish to HTML and PDF.</p>
<h3>Course prerequisites</h3>
<p><em>If you are a beginning Flare user and are unfamiliar with the Flare work environment, I recommend that you take the <a href="http://www.madcapsoftware.com/training/flaretraining.aspx" title="Link to MadCap Training page" target="_blank">Flare Basic/Intermediate class</a> before attempting the single sourcing class.</em>  Unfortunately, we simply cannot cover the work environment in detail. If you have no formal Flare training but are comfortable working with the product, then you will will probably do well in the single sourcing class.</p>
<h3>Course highlights</h3>
<p>The single sourcing course covers many powerful Flare features, including</p>
<ul>
<li>re-using content</li>
<li>maintaining a linked workflow where contributors are writing in Word and FrameMaker and publishing in Flare</li>
<li>creating <em>ad hoc</em> tables of content for different outputs</li>
<li>using Flare page layouts for printed output</li>
<li>using snippets to reuse content with embedded conditions</li>
<li>using variables in topics and in a TOC</li>
<li>running builds from the command line and automating builds with batch files</li>
<li>creating multiple targets (one online and one print target for each hotel)
</li>
<p>sharing content and resources using Global Project Linking.
</ul>
<h2>Details for the upcoming session</h2>
<ul>
<li><strong>When:</strong> Wednesday, June 3, 2009, from 9 am to 5 pm</li>
<li><strong>Where:</strong> 2001 Jefferson Davis Highway, Suite 610,<br />Arlington, VA 22202 (Crystal City, accessible by Metro)</li>
<li><strong>Price:</strong> $599 per student</li>
<li><strong>What to Bring:</strong> Laptop with Flare 4.2.1 installed.  If you need to use a trial version, MadCap will provide a temporary key.</li>
</ul>
<h2>Questions and registration</h2>
<p>Contact <span class="leadin">Jennifer Morse</span>, Senior Territory Manager, MadCap Software:</p>
<ul>
<li><strong>Direct:</strong> +1.858.320.0387&#215;212</li>
<li><strong>Toll Free:</strong> 1.888.623.2271&#215;212</li>
<li><strong>Fax:</strong> 858.320.0338</li>
<li><strong>Email:</strong> <a href="mailto:jmorse@madcapsoftware.com" title="Jennifer's email address">jmorse@madcapsoftware.com</a></li>
<li><strong>Curriculum outline:</strong> <a href="http://tiny.cc/YcylK">http://tiny.cc/YcylK</a></li>
</ul>
<p>Even if you don&#8217;t live in the Washington, DC, area but live within a reasonable travel distance, I hope that you will join us.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.vanarsdall-infodesign.com/2009/05/10/advanced-flare-single-sourcing-class-coming-to-arlington-va/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>STC WDC Chapter Sponsors Flare&#160;Single Sourcing Demo</title>
		<link>http://www.vanarsdall-infodesign.com/2009/04/13/upcoming-presentation-for-stc%c2%a0washington-dc/</link>
		<comments>http://www.vanarsdall-infodesign.com/2009/04/13/upcoming-presentation-for-stc%c2%a0washington-dc/#comments</comments>
		<pubDate>Mon, 13 Apr 2009 11:06:48 +0000</pubDate>
		<dc:creator>Eddie</dc:creator>
				<category><![CDATA[Help Development]]></category>
		<category><![CDATA[MadCap Software]]></category>
		<category><![CDATA[Online Publishing]]></category>
		<category><![CDATA[Print Publishing]]></category>
		<category><![CDATA[Single Sourcing]]></category>
		<category><![CDATA[Tools]]></category>
		<category><![CDATA[madcap flare]]></category>

		<guid isPermaLink="false">http://www.vanarsdall-infodesign.com/?p=2076</guid>
		<description><![CDATA[I am presenting at an upcoming STC Washington, DC (STC WDC) chapter meeting. I will demonstrate and discuss many of the outstanding single-sourcing features that MadCap Flare offers. Here are some basic details: Date: Tuesday, April 21, 2009 Time: 6:30 &#8211; 8:30 p.m., US EST Place: Silver Spring Library If you are in the Washington, [...]]]></description>
			<content:encoded><![CDATA[<p></p><p>I am presenting at an upcoming <a href="http://www.stcwdc.org" title="Link to STC WDC site" target="_blank">STC Washington, DC (STC WDC) chapter</a> meeting. I will demonstrate and discuss many of the outstanding single-sourcing features that MadCap Flare offers. </p>
<p>Here are some basic details:<br />
<strong>Date:</strong> Tuesday, April 21, 2009<br />
<strong>Time:</strong> 6:30 &#8211; 8:30 p.m., US EST<br />
<strong>Place:</strong> Silver Spring Library</p>
<p>If you are in the Washington, DC, area, I hope to see you there!</p>
<p><a href="http://guest.cvent.com/EVENTS/Info/Summary.aspx?e=e30b9e01-d8c3-45ba-868e-162db4633b36" title="Link to STC WDC event registration page" target="_blank">Visit the event page and register for the event</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.vanarsdall-infodesign.com/2009/04/13/upcoming-presentation-for-stc%c2%a0washington-dc/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Flare Print Publishing, Stage 6: Building&#160;a&#160;Print&#160;Target</title>
		<link>http://www.vanarsdall-infodesign.com/2009/02/15/stage-6-building-a-print-target/</link>
		<comments>http://www.vanarsdall-infodesign.com/2009/02/15/stage-6-building-a-print-target/#comments</comments>
		<pubDate>Sun, 15 Feb 2009 17:04:54 +0000</pubDate>
		<dc:creator>Eddie</dc:creator>
				<category><![CDATA[MadCap Software]]></category>
		<category><![CDATA[Print Publishing]]></category>
		<category><![CDATA[Tools]]></category>
		<category><![CDATA[madcap flare]]></category>

		<guid isPermaLink="false">http://www.vanarsdall-infodesign.com/?p=1501</guid>
		<description><![CDATA[This is the sixth and final installment in a series of articles outlining my suggestions for developing a Flare 4 print publishing strategy. Each article represents a stage in the process. This article provides suggestions, tips, and key points for successful print publishing with Flare. It is not a replacement for Flare&#8217;s comprehensive online help [...]]]></description>
			<content:encoded><![CDATA[<p></p><p><em><a name="top" id="top"></a>This is the sixth and final installment in a series of articles outlining my suggestions for developing a Flare 4 print publishing strategy. Each article represents a stage in the process. This article provides suggestions, tips, and key points for successful print publishing with Flare. It is not a replacement for Flare&#8217;s comprehensive online help and how-to guides.</em></p>
<p><strong>Recommended prerequisite reading:</strong></p>
<ul>
<li><a title="Link to Stage 1: Laying the Foundation" href="http://www.vanarsdall-infodesign.com/2008/12/05/flare-print-preparation/" target="_self">Stage 1: Laying the Foundation</a></li>
<li><a title="Link to Stage 2: Defining Styles" href="http://www.vanarsdall-infodesign.com/2008/12/15/flare-print-styles/" target="_self">Stage 2: Defining Styles</a></li>
<li><a title="Link to Stage 3: Creating a Book Structure" href="http://www.vanarsdall-infodesign.com/2009/01/03/flare-print-bookstructure/" target="_self">Stage 3: Creating a Book Structure</a></li>
<li><a title="Link to Stage 4: Designing a Book Layout" href="http://www.vanarsdall-infodesign.com/2009/01/22/flare-print-booklayout/" target="_self">Stage 4: Designing a Book Layout</a></li>
<li><a title="Link to Stage 5: Assembling a Book" href="http://www.vanarsdall-infodesign.com/2009/02/11/flare-print-assemblingbook/" target="_self">Stage 5: Assembling a Book</a></li>
</ul>
<p>Here&#8217;s where all of your hard work in setting up a Flare print publishing infrastructure pays off. All you have to do is configure a target for printed output, generate the build, and then publish the deliverable.</p>
<p>If you require more than one print target, add as many as you need (<strong>Project</strong> > <strong>Add Target</strong>). For example, if you need to publish to both Word and PDF, you can create a target for each.</p>
<p><strong>Goal of this stage:</strong> Configure, build, and publish.</p>
<p><span id="more-1501"></span></p>
<h2>Step 1: Configure the target file.</h2>
<p>The following tables list target settings that are specific to printed output.</p>
<h3>Basic tab settings</h3>
<table border="0">
<colgroup>
<col class="setting"></col>
<col class="description"></col>
</colgroup>
<tbody>
<tr>
<th>Setting</th>
<th>Description</th>
</tr>
<tr>
<td>Output Type</td>
<td>Specifies the format of the printed output (for example, PDF or Word). Select the desired type.</td>
</tr>
<tr>
<td>Master TOC</td>
<td>Specifies the TOC to use in the printed output. Select your print-only TOC from the drop-down list.</td>
</tr>
<tr>
<td>Master Page Layout</td>
<td>Specifies the page layout to be used in the printed output. If you are using only one page layout, select it from the drop-down list. If you are using multiple page layouts for multiple book sections, leave this set to <strong>default</strong>.</td>
</tr>
<tr>
<td>Master Stylesheet</td>
<td>Specifies the style sheet to be used in the printed output. Select a style sheet from the drop-down list.</td>
</tr>
</tbody>
</table>
<h3>Conditional Text tab settings</h3>
<table border="0">
<colgroup>
<col class="setting"></col>
<col class="description"></col>
</colgroup>
<tbody>
<tr>
<th>Setting</th>
<th>Description</th>
</tr>
<tr>
<td>Tags</td>
<td>Specifies content to be included or excluded from the output. Check the appropriate columns.</td>
</tr>
</tbody>
</table>
<h3>Variables tab settings</h3>
<table border="0">
<colgroup>
<col class="setting"></col>
<col class="description"></col>
</colgroup>
<tbody>
<tr>
<th>Setting</th>
<th>Description</th>
</tr>
<tr>
<td>Variable Sets</td>
<td>Specifies the values of variables for the current target. This tab enables you to change variable values on a target-by-target basis. For example, if you have print targets for several products, you can use one <span class="leadin">ProductName</span> variable but change its value in each target file.</td>
</tr>
</tbody>
</table>
<h3>Advanced tab settings</h3>
<table border="0">
<colgroup>
<col class="setting"></col>
<col class="description"></col>
</colgroup>
<tbody>
<tr>
<th>Setting</th>
<th>Description</th>
</tr>
<tr>
<td>Stylesheet Medium</td>
<td>Specifies the medium (default, non-print, print, or custom) to apply to the output. For printed output, select the <strong>print</strong> medium.</td>
</tr>
</tbody>
</table>
<h3>Printed Output tab settings</h3>
<table border="0">
<colgroup>
<col class="setting"></col>
<col class="description"></col>
</colgroup>
<tbody>
<tr>
<th>Setting</th>
<th>Description</th>
</tr>
<tr>
<td>Expanding Text</td>
<td>Determines how expanding text is handled in print. You can convert it to footnotes, include it as body text, or remove it.</td>
</tr>
<tr>
<td>Text Popup Effects</td>
<td>Determines how popup text is handled in print. You can convert it to footnotes, include it as body text, or remove it.</td>
</tr>
<tr>
<td>Generated TOC</td>
<td>
<ul>
<li>
<p><strong>Use TOC depth for heading levels:</strong> Uses your print-only TOC to determine levels in the printed output, overriding any TOC levels that you have applied using the <strong>PrintSupport</strong> &gt; <strong>mc-heading-level</strong> property in your style sheet. </p>
<p>For example, let&#8217;s say that in online output you are using <span class="leadin">h1</span> for each of your main topic headings and using <span class="leadin">h2</span> and <span class="leadin">h3</span> for subheadings. In printed output you are using a <span class="leadin">ChapterTitle</span> style and have added it to organizational topics using conditional text. In your style sheet, the mc-heading-level property for both <span class="leadin">h1</span> and <span class="leadin">ChapterTitle</span> is set to 1.</p>
<p>If you enable the TOC depth setting in the target file, Flare uses the <span class="leadin">ChapterTitle</span> style as the first level in your TOC, but it demotes <span class="leadin">h1</span> and <span class="leadin">h2</span> down one level. This doesn&#8217;t affect the way your printed topics look. It mainly adjusts the heading levels in the TOC of all print output types. The same adjustments are applied to the bookmark structure in the left pane of a PDF document.</p>
</li>
<li><strong>Inject headings for unlinked books in TOC:</strong> Ensures that a heading appears for every book in the print-only TOC, regardless of whether the book is linked to anything.</li>
<li><strong>Remove images from paragraphs with heading levels:</strong> Prevents any images included in heading text from appearing in the TOC.
</li>
</ul>
</td>
</tr>
<tr>
<td>Multi-Document Native XPS/PDF Output</td>
<td>Used to generate separate documents for each chapter in printed output. Enable this setting if your output is XPS or PDF and you have configured your print-only TOC to use a separate, named file for each chapter.</td>
</tr>
<tr>
<td>FrameMaker and MS Word Output</td>
<td>
<p>Lists various settings that are specific to FrameMaker and Word output only. Some settings have specific installation requirements and/or require Word 2007. If your target is set to any output type other than FrameMaker or Word, you cannot select these settings.</p>
<p>For more information about each setting, click the <strong>quick help</strong> link that appears to the right of that setting.</p>
</td>
</tr>
</tbody>
</table>
<h2>Step 2: Build the target.</h2>
<p>Once you have selected all of the desired settings, save and build the target. Examine the output and make any necessary adjustments.</p>
<h2>Step 3: Publish the target.</h2>
<p>Just as you publish online output to make it available for your users, you also need to publish your printed documents and books. For more information about publishing, <a title="Link to article about Flare publishing destinations" href="http://www.vanarsdall-infodesign.com/2009/01/11/publishing-with-flare-destinations/" target="_self">see my article covering Flare publishing destinations</a>.</p>
<h2>Conclusion</h2>
<p>Wow, the epic is finished! To my Flare students who asked for this information months ago, I hope it was worth the wait. I have juggled the writing with a busy schedule and other responsibilities, so publishing these articles took longer than I had anticipated. I hope that you find the information helpful.</p>
<p>Please visit this site often for more frequent Flare tips.</p>
<p><a href="#top" target="_self">Back to top</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.vanarsdall-infodesign.com/2009/02/15/stage-6-building-a-print-target/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Flare Print Publishing, Stage 5: Assembling&#160;a&#160;Book</title>
		<link>http://www.vanarsdall-infodesign.com/2009/02/11/flare-print-assemblingbook/</link>
		<comments>http://www.vanarsdall-infodesign.com/2009/02/11/flare-print-assemblingbook/#comments</comments>
		<pubDate>Wed, 11 Feb 2009 20:43:52 +0000</pubDate>
		<dc:creator>Eddie</dc:creator>
				<category><![CDATA[MadCap Software]]></category>
		<category><![CDATA[Print Publishing]]></category>
		<category><![CDATA[Tools]]></category>
		<category><![CDATA[madcap flare]]></category>

		<guid isPermaLink="false">http://www.vanarsdall-infodesign.com/?p=1360</guid>
		<description><![CDATA[This is the fifth installment in a series of articles outlining my suggestions for developing a Flare 4 print publishing strategy. Each article represents a stage in the process. This article provides suggestions, tips, and key points for successful print publishing with Flare. It is not a replacement for Flare&#8217;s comprehensive online help and how-to [...]]]></description>
			<content:encoded><![CDATA[<p></p><p><em><a name="top" id="top"></a>This is the fifth installment in a series of articles outlining my suggestions for developing a Flare 4 print publishing strategy. Each article represents a stage in the process. This article provides suggestions, tips, and key points for successful print publishing with Flare. It is not a replacement for Flare&#8217;s comprehensive online help and how-to guides.</em></p>
<p><strong>Recommended prerequisite reading:</strong></p>
<ul>
<li><a title="Link to Stage 1: Laying the Foundation" href="http://www.vanarsdall-infodesign.com/2008/12/05/flare-print-preparation/" target="_self">Stage 1: Laying the Foundation</a></li>
<li><a title="Link to Stage 2: Defining Styles" href="http://www.vanarsdall-infodesign.com/2008/12/15/flare-print-styles/" target="_self">Stage 2: Defining Styles</a></li>
<li><a title="Link to Stage 3: Creating a Book Structure" href="http://www.vanarsdall-infodesign.com/2009/01/03/flare-print-bookstructure/" target="_self">Stage 3: Creating a Book Structure</a></li>
<li><a title="Link to Stage 4: Designing a Book Layout" href="http://www.vanarsdall-infodesign.com/2009/01/22/flare-print-booklayout/" target="_self">Stage 4: Designing a Book Layout</a></li>
</ul>
<p>Once you have set up a book structure and designed the book layout, you&#8217;re ready to assemble the book. Don&#8217;t confuse this with <em>generating</em> a book. You&#8217;ll do that in the final stage by setting up and building a print target.</p>
<p><strong>Goal of this stage:</strong> To assemble a book using  a print-only table of contents to specify the book sections.</p>
<p><span id="more-1360"></span></p>
<h2>Step 1: Create a print-only TOC.</h2>
<p>When you create a new Flare project, Flare includes one Master TOC (.fltoc) file. You are not restricted to using only the Master file. In fact, you can add as many TOCs as you need and use them for various targets. You can also designate any TOC as the Master TOC by right-clicking its name and selecting <strong>Make Master TOC</strong> from the shortcut menu.</p>
<p>For this stage of the print publishing process, you need to add a print-only TOC to your project. You will use the new TOC to assemble the sections of your printed book. The following procedures explain two different ways to add the TOC.</p>
<h3>Adding a TOC using the Project menu</h3>
<p>To add a TOC using the Project menu, follow these steps:</p>
<ol>
<li>Select the following menu command:<br />
<strong>Project</strong> &gt; <strong>Add Table of Contents</strong></li>
<li>In the Add TOC window, do one of the following:
<ul>
<li>Click the button to the right of the <strong>Source File</strong> field and browse for a saved TOC template; or</li>
<li>Type a file name that expresses the intent of the new TOC (for example, <em>PrintOnly</em>).</li>
</ul>
</li>
<li>Click <strong>Add</strong>.</li>
<li>Click <strong>OK</strong> to confirm that you want to copy the file to the project. Flare adds the new TOC to the <strong>TOCs</strong> folder in the Project Organizer.</li>
</ol>
<h3>(Alternate) Adding a TOC by copying another TOC file</h3>
<p>If you want to re-use content from an existing TOC, copy it and use its hierarchy as a starting point for your print TOC. To copy an existing TOC file, follow these steps:</p>
<ol>
<li>Right-click the existing TOC, then select <strong>Copy</strong> from the shortcut menu.</li>
<li>Right-click anywhere in the Project Organizer pane, then select <strong>Paste</strong> from the shortcut menu. Flare adds the new TOC to the <strong>TOCs</strong> folder in the Project Organizer. The new TOC is named <em>Copy of &lt;original file name&gt;</em> (for example, <em>Copy of Master</em>).</li>
<li>Rename the new file using a name that expresses the intent of the new TOC (for example, <em>PrintOnly</em>).</li>
</ol>
<h2>Step 2: Assemble the hierarchy for the new book.</h2>
<p>If you cloned the Master TOC, you may want to add or remove specific books and topics. Regardless, add TOC entries for the print-only topics that you created in Stage 3 of the print publishing process. For example, if you created topics for a cover page, TOC section, lists of figures and tables, glossary, and index, add TOC pages for those topics and link the pages to the topics.</p>
<div class="note"><span class="notetext">Note:</span> For more information about print-only topics, <a title="Link to Stage 3: Creating a Book Structure" href="http://www.vanarsdall-infodesign.com/2009/01/03/flare-print-bookstructure/" target="_self">see the article on creating a book structure</a>.</div>
<p>A simple way to simultaneously add TOC pages and link them to topics is to drag the topics into the TOC from the Content Explorer. To do this,  follow these steps:</p>
<ol>
<li>Open the print-only TOC.</li>
<li>Display the <strong>Content Explorer</strong>.</li>
<li>Locate your print-only topics. I recommend storing all of them in the same subfolder.</li>
<li>Drag each topic to a specific location in the TOC. This step creates a TOC page and links it to the topic.</li>
<li>Save the TOC file.</li>
</ol>
<p>The following image shows an example of a completed print-only TOC hierarchy. The standalone pages in the TOC are linked to print-only topics, and the books are linked to content topics.</p>
<div class="clearright"><img class="aligncenter size-full wp-image-1411" title="Print-only TOC hierarchy" src="http://www.vanarsdall-infodesign.com/wp-content/uploads/2009/02/winprinttoc.png" alt="Print-only TOC hierarchy" width="294" height="248" /></div>
<h2>Step 3: Map TOC pages to book sections.</h2>
<p>The standalone pages that you created in Step 2 now represent book sections. You can specify the layout for each section by mapping the TOC page properties to specific page layouts.</p>
<div class="note"><span class="notetext">Note:</span> The following procedure assumes that you are using Flare 4 and generating printed output using page layouts. If you are using Flare 3 or below, or if for some reason you are using a print master page with Flare 4,  refer to the following help topic: <span class="helplink"><a title="Link to information about section breaks and print master pages" href="http://www.madcapsoftware.com/support/webhelp/flare/Content/Output/Printed_Output/More_About_Printed_Output/Specifying_Section_Breaks_and_Master_Pages_for_Printed_Output.htm" target="_blank">Specifying Section Breaks and Master Pages for Printed Output</a></span>. If you are a Flare 4 user, I urge you to take advantage of page layouts.</div>
<p>To map TOC pages to book sections, follow these steps:</p>
<ol>
<li>Open the print-only TOC.</li>
<li>Do either of the following to access the Properties window for a TOC page:
<ul>
<li>Double-click the TOC page;<br />
or</li>
<li>Right-click the TOC page, then select <strong>Properties</strong> from the shortcut menu.</li>
</ul>
</li>
<li>Complete the following tasks.</li>
</ol>
<h3>Setting Chapter Break properties</h3>
<p>In the Properties window, follow these steps:</p>
<ol>
<li>Click the <strong>Printed Output</strong> tab.</li>
<li>Check the box labeled <strong>Start a new chapter document</strong>.<br />
This step enables the rest of the options in the Chapter Break section.</li>
<li>Under <strong>Configure chapter using this Page Layout</strong>, select a page layout. For example, if you have a page layout called <em>Front</em> that includes a cover page and copyright page, you might select <em>Front</em>.</li>
<li>Select a <strong>Page Type</strong> from the drop-down list. The available types come from the page layout that you selected in the previous step. For example, if the <em>Front</em> page layout is set up for a double-sided book, you would most likely select the <em>First</em> page type to start a new section.</li>
<li>If you want new chapters to automatically start on right (odd) pages, set the <strong>Auto-end on &#8216;left&#8217; page</strong> property to <strong>Enabled</strong>. </li>
<li>Leave <strong>Chapter File Name</strong> set to default if you plan to use one file for the printed book. If you plan to use multiple files for the chapters, you can use a target setting to break chapters into multiple files and specify names for each file. For more information, see the help topic titled <span class="helplink"><a title="Link to information about chapter breaks and page layouts" href="http://www.madcapsoftware.com/support/webhelp/flare/Content/Output/Printed_Output/More_About_Printed_Output/Specifying_Chapter_Breaks_for_Printed_Output.htm" target="_blank">Specifying Chapter Breaks and Page Layouts</a>.</span></li>
</ol>
<h3>Setting Page Number properties</h3>
<p>To establish a page number format for the current section, follow these steps:</p>
<ol>
<li>Ensure that the <strong>Printed Output</strong> tab is still visible.</li>
<li>In the Page Number section, select settings according to what you want to do:
<ol>
<li>To start page numbering at a specific number, enter the starting number in the box.</li>
<li>To control the page number format for the current section, select a format from the <strong>Format</strong> drop-down list.</li>
<li>To continue page numbering and retain the number format from the previous section, select the <strong>Continue from previous</strong> option.</li>
</ol>
</li>
<li>Click <strong>OK</strong> to close the Properties window.</li>
</ol>
<h3>Specifying  Section, Chapter, or Volume Numbering</h3>
<p>The Properties window for a TOC item includes settings for section, chapter, and volume numbers. For example, even if you have set up an auto-numbered style for appendices (such as <span class="leadin">Appendix {chapnum}</span>), you use TOC settings to ensure that uppercase alpha headings (such as <span class="leadin">Appendix A</span>) show in printed output.</p>
<p>To specify section, chapter, or volume numbering, follow these steps:</p>
<ol>
<li>In the Properties window, click the <strong>Auto-numbers</strong> tab.</li>
<li>Specify settings as needed in the Section, Chapter, and Volume areas of the tab:
<ol>
<li>To start numbering at a specific number, enter the starting number in the box.</li>
<li>To control the number format for the current section, select a format from the <strong>Format</strong> drop-down list.</li>
<li>To start at the same number as the previous section, select <strong>Same as previous</strong>.</li>
<li>To number consecutively from the previous section, select <strong>Continue from previous</strong>.</li>
</ol>
</li>
<li>Click <strong>OK</strong> to close the Properties window.</li>
</ol>
<h2>What&#8217;s next?</h2>
<p>You have completed all of the most time-intensive stages of the Flare print publishing process. There&#8217;s only one more thing to do: <a title="Link to article about configuring and building a print target" href="http://www.vanarsdall-infodesign.com/2009/02/15/stage-6-building-a-print-target/" target="_self">configure and build your print target</a>.</p>
<p><a href="#top" target="_self">Back to top</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.vanarsdall-infodesign.com/2009/02/11/flare-print-assemblingbook/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>
