Using the Target Editor, you can edit properties for any of your targets.
- In the Project Organizer, expand the Targets folder and double-click the target that you want to edit.
You can use the tabs in the Target Editor to perform various tasks, depending on the output type associated with the target (i.e., some tasks can be performed only in certain targets).List of Tasks
- Accessibility Warnings Read more… You can use the Target Editor to indicate whether you want to receive compiler warnings when your output fails to include information that makes it accessible. By default the warnings are set to be enabled, but you can set any of them to be ignored if you want. See About Accessibility and Ignoring Warnings When Building Output.
- ALT Text (Empty) Read more… You can add an empty "alt" (alternate text) attribute to images, QR codes, and equations that do not have one. The attribute gets added to the output when the target is generated. See Applying Empty Alt Text.
- Browse Sequence (Associate) Read more… If you have created only one browse sequence for your project, you do not need to associate it with a target. It will display automatically after you build the target. However, if you have added more browse sequences, you need to specify which one will serve as the "master browse sequence." This is the browse sequence that will be displayed in the output. The additional browse sequences will also be displayed if you have linked to them from the master browse sequence. You can use the Target Editor to associate a master browse sequence with a target. See Associating a Browse Sequence with a Target.
- Build Events (Create) Read more… You can use the Target Editor to create pre- and post-build events. This lets you run command line events before or after the target is generated. See Creating Pre- and Post-Build Events.
- Build (Generate) Output Read more… You can use the Target Editor to build a target in your project that is not designated as your primary target. See Building and Publishing a Single Target.
- Condition Tags (Associate) Read more… After you create and apply condition tags to content, you need to tell Flare what your target should do with the condition tags that you have created and applied. Should content with a particular condition tag be included in or excluded from that target?
See Associating Conditions with Targets.
- Context-sensitive Help—Alias File (Associate) Read more… An alias file is used to populate a header file with the information necessary for producing context-sensitive Help (CSH). If you have added more than one alias file for your project, you need to associate the appropriate alias file with the target that you plan to build. If you do not specify an alias file in a target, Flare uses the first alias file listed in the Project Organizer. See Associating an Alias File with a Target.
- DOCTYPE Declaration (Add) Read more… You can add the DOCTYPE declaration to topic files when you generate online output. This allows browsers to render the topics in strict mode. If you do not select this option, generated topics will not have this declaration and will be rendered by browsers in quirks mode. Quirks mode and strict mode have to do with the evolution of web browsers and the rules they use to interpret styles in cascading stylesheets (CSS). Quirks mode follows the old rules, and strict mode follows the new rules. If you are not concerned about which mode is used for your online output, you do not need to add the DOCTYPE declaration to topics. However, if you want to ensure that your output is interpreted and displayed using the newer strict mode, you should use this option. See Adding the DOCTYPE Declaration to Generated Topics.
- Eclipse Help Output—Options (Specify) Read more… If you are sending output to the Eclipse Help format, you can access Eclipse options in the Target Editor. See Specifying Eclipse Options.
- Empty Pages—(Inject) Read more… For PDF output, this check box is used in conjunction with empty page types to automatically include empty pages in the output when necessary. See Using Empty Pages.
- EPUB Output—Options (Specify) Read more… If you are sending output to EPUB, you can access EPUB options in the Target Editor. These options let you provide metadata, select a cover image, validate output, generate MOBI output, enable MathML to PNG conversion, embed fonts, and enable dynamic content. See Specifying EPUB Options.
- Equation Styles (Convert) Read more… When you build a target, equations may be converted to another format. This, however, depends on the output type of the target you are building. See Converted Output Formats for Equations.
- External URLs—(Prevent) Read more… In Flare's web targets, you can prevent people from loading an external website in the topic pane by appending a foreign URL at the end of your output's URL. You might use this feature to prevent someone from appending a malicious website to the end of your normal URL. See Preventing External URLs.
- Feedback (Enable) Read more… If you purchase the MadCap Feedback Service in order to track user activity on your online output, a separate license is required for each target that you want to associate with Feedback. After obtaining the necessary Feedback license(s), you need to enable the Feedback functionality in Flare. This is done on the Community tab in the targets. See Enabling Feedback in Flare and About MadCap Feedback.
- Glossaries (Associate) Read more… If you are including one or more glossaries in your output, you need to associate them with the target. After you build the target, the glossary will be incorporated into the output
and terms will be converted to links in individual topics (if you have selected one of the term conversion options in the Target Editor). See Associating Glossaries with Targets.
- Glossaries (Auto-generate) Read more… You can select an option to let Flare auto-generate a glossary for you in print-based output. See Auto-generating Glossaries for Print.
- HTML Help—Jump Buttons (Specify) Read more… You can specify the destination (URL) for the Jump1, Jump2, and Home buttons that can be included in Microsoft HTML Help output. You can also set these destinations in the Skin Editor (HTML Help Setup tab) and associate that skin with the target (on the General tab of the Target Editor). The reason this option is available in both the Skin Editor and Target Editor is this: If you want multiple targets to use one skin, with each target using the same destinations for the jump buttons, you should set the jump button URLs in the Skin Editor. If you want multiple targets to use the same skin, but you want them to use different URLs for the jump buttons, set the URLs in the Target Editor. If URLs are set in both the Skin Editor and the Target Editor, Flare uses the settings from the Skin Editor. See Specifying Buttons for HTML Help Output.
- HTML Help—Merged Output (Display Navigation) Read more… If you want the merged navigation (table of contents, index, search) to be displayed in any of the CHM files, even child targets, you can enable an option on the Advanced tab of the Target Editor. However, the parent CHM must be present when you open a navigation element in a child CHM (i.e., it must be in the same folder as the child CHM). See Displaying Merged Navigation in HTML Help Child Outputs.
- HTML Help—Stylesheet and Image Links (Patch) Read more… If you generate Microsoft HTML Help output, some topics may not look as intended when they are printed from the CHM file, due to stylesheet-related problems. You can use this feature to "patch" those problems, ensuring the printed topics will look as intended. Why would you not use this option? The only reason not to use this option is when you plan to rename the generated CHM file. If this option is enabled and you rename the CHM file, styles in the output are broken. This happens because, when the option is enabled, the file name of the CHM is hardcoded into the CHM itself. See Patching Stylesheets and Image Links for HTML Help.
- HTML5—Server-based Output (Enable) Read more… You can create HTML5 output in its regular state, or you can select an option in the Publishing tab of the Target Editor to enable server-based functionality. This allows you to accomplish the same results as WebHelp Plus output—searching of non-XHTML content, faster server-side search, and automatic runtime merging. See Enabling HTML5 Server-based Output.
- Images—Microsoft Word Output (Embed) Read more… An option on the Advanced tab of the Target Editor lets you ensure that images are embedded in Microsoft Word output. This option is enabled by default.
See Embedding Images in Word Output.
- Images—Objects (Auto-size) Read more… If you have inserted MadCap Capture images that contain objects with text, you can auto-size those objects automatically when the output is generated. This can be done by selecting an option in the Advanced tab of the Target Editor. The original image file and its associated properties (.props) file remain unchanged. Only the output image is affected. See Auto-sizing Capture Image Objects to Fit Text.
- Images—Resized Scaled Images (Generate) Read more… When you use Flare's resizing features to scale images, you can specify whether you want Flare to pre-compile the resized images.
You can do this for the online outputs (HTML5, Clean XHTML, DotNet Help, Eclipse Help, Microsoft HTML Help, WebHelp, WebHelp Mobile, WebHelp Plus), as well as for Microsoft Word and Adobe FrameMaker output.What does this mean? It means that Flare will create new copies of images wherever you have specified resizing, rather than relying on the browser to render the new size from the original. This means better quality images, but it also means more image files in the output. It is recommended that you leave the default pre-compile setting as it is (enabled). However, if you want to disable it, you can open the Target Editor, select the Advanced tab, and select Generate resized copies of scaled images to remove the check mark. (For Adobe PDF and XHTML Book output, the resized images will always be pre-compiled, whether this option is enabled or not.)
- Images—Web-safe Images (Generate) Read more… If you have used non–web-safe image formats (e.g., WMF, EMF, BMP, TIF, TIFF) in your project, you can convert those images to web-safe formats (e.g., GIF, JPEG, PNG) when you generate online output ( HTML5, Clean XHTML, DotNet Help, Eclipse Help, Microsoft HTML Help, WebHelp, WebHelp Mobile, WebHelp Plus). For print-based output types (Adobe FrameMaker, Adobe PDF, Microsoft Word, XHTML Book), the original image file formats will be used when you generate output. See Generating Web-Safe Images.
- Importing—Auto-sync (Disable) Read more… Let's say you have imported Microsoft Word, Adobe FrameMaker, or Flare files from another project, and when doing so, you selected the "Easy Sync" option to automatically re-import the files when you generate output. You can use this feature to override that Easy Sync setting for a specific target. Therefore, if you want to re-import any of the files, you will need to do so manually. You might decide to use this option, for example, if you are testing the generation of output and do not want to wait the extra time for the files to be imported. After you finish your testing, you can deselect this option to return to the automatic imports of the files.
See Disabling Auto-Sync of Import Files.
- Index (Auto-generate) Read more… You can select an option to let Flare auto-generate an index for you in print-based output. See Auto-generating Indexes for Print.
- Index—Search (Excluding) Read more… If you insert index markers in your project, those markers by default are included in searches that users perform in your output. If you want to exclude index entries from searches, you can do so. See Excluding Index Entries From Search.
- Language—(Select) Read more… You need to tell Flare which language you are working with so that it knows which skin to use in the output. This can be done when you are first creating the project or later by using the Project Properties option. You can also override the project language and set it for the individual targets or topics. If out want to create a multilingual target output, you can select multiple languages and link Lingo projects or additional Flare projects to your current (master) project. The generated output will include each selected language. In addition, if you set a right-to-left (RTL) language on the target, there are multiple options selected by default. These options are used to automatically invert language-related style rules locally or in the stylesheet, as well as to invert image callouts and page layout settings. See How to Select Languages for a Specific Target.
- MadCap Styles (Remove) Read more… Due to an issue with Google Chrome, content within the body of topics inherits the hover color of MadCap styles (e.g., MadCap|xref:hover). To prevent this situation, Flare will automatically add a @namespace rule at the beginning of the CSS files in your output. However, you can select an option in the Target Editor for web-based outputs if you do not want this rule to be added to your stylesheets. See Removing MadCap Styles.
- Mark of the Web (Add) Read more… Mark of the Web (MOTW) is a comment added to the HTML markup for a web page. When users open the web page from their local machine, Internet Explorer references this comment to determine the security zone in which it should run the page. This means you can deliver WebHelp outputs without your online Help initially being blocked on the user's machine with a security message. See Adding Mark of the Web.
- Master Page (Associate) Read more… If you want a master page to be applied to all topics in the output, you would associate that master page with the target that you are building. This is useful, for example, if you want to create breadcrumbs, a mini-TOC, header content, or footer content for your online outputs (e.g., HTML5, DotNet Help, Eclipse Help, Microsoft HTML Help, WebHelp, WebHelp Mobile, WebHelp Plus). See Associating Master Pages with Targets.
- Master Pages (Disable) Read more… Let's say you have used master pages in earlier versions of Flare when creating Word or FrameMaker output, but now you decide to use the newer page layouts instead. You can manually remove all links to master pages in your target and table of contents. However, another alternative is to click this option instead. By selecting this option, Flare will ignore all links to master pages when you generate the Word or FrameMaker target. It will instead use links that you provide to any page layouts. See Disabling the Use of Master Pages.
- Meta Tags (Add) Read more… For online outputs, you can add custom meta tags in the Advanced tab of the Target Editor. These are added between the <head> and </head> tags in your content when you generate output. See Adding Custom Meta Tags.
- Navigation Elements (Synchronize With TOC Entries) Read more… If you generate HTML5 output, links to the TOC (e.g., menu items, breadcrumbs, mini-TOCs) are dynamically generated when a particular topic is opened. This allows you to keep these navigation elements in sync with your TOC. This is particularly important if the same topic is linked to multiple entries in your TOC; otherwise, menu items and other navigation elements might display for one instance of that topic in the TOC when another instance is preferred. For HTML5 Tripane output, navigation elements will always remain in sync with your TOC entries. However, for HTML5 Side Navigation, Top Navigation, and skinless outputs, you must enable a feature in your target to synchronize navigation elements with TOC entries. See Synchronizing Navigation Elements with TOC Entries.
- Output File and Folder (Specify) Read more… When you build the output for a target in your project, Flare sends the output files to the Output folder where your project is located. It also uses a default name for the main entry file in the default output type. However, you can specify a different location and main entry file name for a target's output files. For Word and FrameMaker output, you can also specify a different output file type than the default (e.g., add .pdf to the end of the file name, instead of .xml).
See Specifying the Output File and Folder in a Target.
- Output Files—Characters and Spaces (Replace With Underscores) Read more… If you have spaces or unusual characters in your file names or folders, you can covert these spaces and characters to underscores in the output. This feature is primarily useful for individuals working in a UNIX environment. In addition to spaces, the characters that are converted to underscores include: ()&;,!'. See Replacing Characters and Spaces with Underscores.
- Output Files—Custom Extensions (Specify) Read more… You can use specific file extensions for topics for WebHelp output types. If you do not use this feature, the output topic files will have an .htm extension. The most common alternative extensions are .html and .aspx. To use this option, click the appropriate check box on the Advanced tab of the Target Editor. Then type the file extension that you want to use in the text field. Do not type the period, but rather the characters only. See Using Custom File Extensions.
- Output Files (Exclude Content not Linked) Read more… One way to completely exclude content from online output is to place condition tags on the topic files and include or exclude them from the targets (see About Conditions). Another method is to use an option in the Target Editor to include only content files that are directly or indirectly referenced from the target. This means that if the target is using particular files such as a table of contents (TOCs), master page, and so on, other files linked directly or indirectly from them will be part of the output. See Excluding Content not Linked Directly or Indirectly from Targets.
- Output Files—Lowercase Names (Convert) Read more… You can convert online output file names and folders to all lowercase letters, even if the corresponding file names and folders in the project are not all lowercase. This option is useful, for example, if you are working in a UNIX environment, which is case-sensitive. See Converting Output File Names and Folders to Lowercase.
- Output Folder—Content (Omit) Read more… The Content subfolder in a project is normally used to hold all of your content files. If you do not want this subfolder to be created when you generate online output, you can omit it. When you use this option and build output, the content files will be placed at the root of the output folder instead, rather than within the Content subfolder. See Omitting the Content Folder from Output.
- Output Type (Change) Read more… Each target in your project is based on one of the output types available in Flare (Adobe FrameMaker, Adobe PDF, Clean XHTML, DITA, DotNet Help, Eclipse Help, EPUB, Microsoft HTML Help, HTML5, Microsoft Word, WebHelp, WebHelp Mobile, WebHelp Plus). You can use the Target Editor to switch the output type for a particular target. You can also add an internal comment to describe the output. See Changing the Output Type for a Target.
- Page Layout—Master (Associate) Read more… After you create a page layout and configure its frames and settings as necessary, you need to associate the page layout with the appropriate content. In most cases, you will probably want to associate different page layouts with various entries in your outline TOC (so that different page layouts can be used for different parts or chapters in a manual)
—see Specifying Chapter and Page Layout Breaks. Otherwise, you would associate a single "master" page layout with an entire target or project; in that case, the same page layout will be applied to all topics in that target or project. You can associate a page layout with an outline TOC entry with or without creating a chapter break at the same time. In the Target Editor, you can associate a master page layout with a target. See Associating Master Page Layouts with Targets.
- PDF Output—Multiple Documents (Create) Read more… If you are generating PDF output directly (rather than going through FrameMaker or Microsoft Word to produce it), you can split the generated output into multiple documents, rather than using the default, which results in only one document. To create multiple PDF documents, you must also specify chapter breaks at the appropriate places in the TOC (not the TOC that displays in the PDF output, but in the "outline TOC" used to determine the printed manual content and structure). This can be done on the Printed Output tab of the TOC Properties dialog. By specifying chapter breaks, you are letting Flare know where you want to split the output into new PDF documents. Then in the Advanced tab of the Target Editor, select the "Generate multiple documents for native PDF output" option.
- PDF Output—Options (Specify) Read more… If you are sending output directly to Adobe PDF, you can access PDF options in the Target Editor. These options let you specify the way that images, document properties, PDF tagging, and the initial view are handled in the output. See Specifying PDF Options.
- PDF Output (Specify) Read more… If you are building either Microsoft Word or Adobe FrameMaker targets, you can send the output to Adobe's Portable Document Format (PDF) as well. When you use this feature, Flare generates the native Word or FrameMaker documents, in addition to a PDF file. See Specifying PDF Output Via Word or FrameMaker.
- PDF Output—Top Margins (Collapse) Read more… You can collapse the top margin for all elements occurring at the top of a new page or column. See Collapsing Top Margins.
- Performance (Improve) Read more… You can improve the processing performance of your online output in several ways. See Improving the Processing Performance of the Target.
- Printed Output—Online Features (Convert) Read more… Some online features in your project are automatically handled in one way or another when you produce printed output. However, there are some features (expanding text and popup effects) where you can specify how you would like them to be treated in the printed output. See Specifying How Online Features are Converted in Printed Output.
- Publish Output Read more… After you build a target, you can publish the output to any destinations that you have created. See About Building and Publishing Output.
- Publishing Destinations (Associate) Read more… A publishing destination is used to tell Flare where to send a copy of your output files. After you create a publishing destination, you need to associate it with a target that you plan to build. You can associate the same publishing destination with as many targets as you want. See Associating Publishing Destinations with Targets.
- Pulse (Enable) Read more… To integrate Pulse with your Flare output, you need to enable the Pulse functionality in a Flare target. You also need to create or select a community for the target. A community is simply the entity for a collection of Pulse data. You can perform these tasks on the Community tab in the Target Editor. See Integrating Flare and Pulse and About MadCap Pulse.
- Redacted Text (Set) Read more… For each PDF document that needs to include redacted content, you can open the target. Then you can use the Advanced tab to specify how the content marked as "redacted" should be treated in the output. See Setting Redacted Text on Targets.
- Relationship Tables (Associate) Read more… If you have created relationship tables in your project, you need to tell Flare which tables to use for which targets.
See Associating Relationship Tables with Targets.
- Search—Filter Set (Associate) Read more… A filter can be included in the search feature to let users narrow their search based on "concepts" that you have inserted into topics. Concepts are simply markers that you insert into topics that have some kind of relationship with each other. After you add a search filter set, you need to associate it with the target that you want to build. See Associating a Search Filter Set with a Target.
Search—Engine (Set Up) Read more… For HTML5 targets, you can choose the type of search engine you want people to use—MadCap Search, Google Search, or Elasticsearch (for Side Navigation, Top Navigation, or skinless output). There are additional steps that you can follow to set up each of these engines. For MadCap Search, this includes setting the search result importance, including glossary terms in the results, setting the number of results per page, and setting the abstract character limit. For Google Search, this includes creating a new search engine, verifying the URL, adding a sitemap, submitting the site for indexing, excluding the TOC from indexing, customizing the appearance of the results, and reviewing the indexing status. For Elasticsearch, there are several search results and auto-complete results you can configure for your search engine. See Setting Up a Search Engine.
- Search—Partial Word Searching Read more… For some online outputs, you can provide partial-word searching. This lets users type part of a word, press Enter, and see search results matching those characters. See Enabling Partial-Word Search.
- Search—Include Stop-Words in Search Read more… Flare has a hard-coded stop words list that works behind the scenes to filter out common structure-class words (i.e., function words) from search operations. This means the Flare search engine excludes words (e.g., "an," "for," "of, and "the") by default. However, if you want the search engine to search for queries with these words, you can include the stop words list in search.
See Including Stop Words in Search.
Search-Include SQL Search Database Read more… For DotNet Help you can create an SQL database when generating the output. This results in faster searches. It also allows people to use asterisk wildcards when performing searches. For example, if you type Mad* in the Search field, Flare will list all topics with words that have "Mad" followed by any other letters (e.g., MadCap, Madagascar, madness, Madrid).
- Sitemap/Search Engine Optimization Read more… For web-based targets, you can generate a sitemap when compiling your output. This helps with search engine optimization (SEO), making it easier for search indexing services (i.e., spiders, crawlers, or bots) to find your output. Therefore, the entire output is indexed and search engine results are improved. See Generating Sitemaps for Search Engine Optimization.
- Skin (Associate) Read more… A skin is a file that contains information about the appearance of the output window. After you add a skin to your project and edit the settings, you can associate it with a target. When you build the target, the output will be displayed in the skin. You can also tell Flare not to use any skin at all. See Associating Skins with Targets.
- Skin Components (Associate) Read more… In addition to or instead of full skins, you can use smaller skin components for features such as search, menus, and toolbars. If you add multiple skin components of the same type to your project, you can associate one with a target. See Associating Skin Components with Targets.
- Skin—Favicons (Add) Read more… Short for “favorite icons,” favicons are supported in Flare for HTML5 output. A favicon is the image that you sometimes see in a browser tab, address bar, bookmark, Windows tiles, etc. See Adding Favicons.
- Skin—Responsive Output (Set) Read more… For HTML5 skins, you can override the responsive output settings from the Skin Editor for Tripane skins. Top Navigation skins automatically have responsive output enabled, so you can use the fields in the Target Editor to control the widths for the different mediums. In addition, you can choose to use device width media queries, which means the output will be responsive based on the actual device rather than merely on the width of the screen. See About Responsive Web Design and Responsive Skins.
- Skins (Generate All) Read more… An option on the Advanced tab of the Target Editor controls whether every skin in the project or just the selected skin in the target (which is set on the Skin tab for HTML5 targets and the General tab for other targets) will be generated for the output. This option is enabled by default. One reason to keep this option enabled is if you need the ability to make context-sensitive Help (CSH) calls to different skins. In this case, each of those skins must be generated so that they are available in the output for the CSH calls. If you are not using multiple skins for CSH calls, you might want to disable this option. If you disable it, the size of the entire output will be minimized because unnecessary skins will be excluded. Another reason to enable this option is to use runtime skins for HTML5 outputs, where end users are able to choose the skin to display the output. See Setting All Skins to be Generated.
- Source Control (Get Files Automatically) Read more… If you have bound your project to a source control program, you can use a setting in the Target Editor to automatically get the latest version of all files prior to generating the target. You might use this option if you are working with a team of authors and want to make sure that you include the latest changes from other writers in the output (without having to manually get those files).
See Updating or Getting the Latest Version of Source Control Files.
- Startup Topic (Specify) Read more… You can specify which topic in your project is the first one that users see when they open the online output. If you have written a welcome or introduction topic, you will likely want this to be the "startup" topic in your output. See Specifying the Startup Topic in a Target.
- Stylesheet (Convert to Inline Styles) Read more… For Clean XHTML targets, you have the option to keep your stylesheet styles or to convert them to inline styles. See Converting Stylesheet Styles to Inline.
- Stylesheet—Master (Associate) Read more… When you want to use styles in your content, the stylesheet needs to be made available for the content in question. In Flare, you can associate regular stylesheets with individual files
(see Associating Stylesheets Locally with Specific Files). However, you also have the option of using a regular stylesheet as a "master," applying it at either the project or target level, or both. In the Target Editor, you can associate a master stylesheet with a target. See Associating Master Stylesheets with All Files.
- Stylesheet—Medium (Associate) Read more… A medium is an alternative group of settings in a stylesheet and can be very useful when you are generating multiple kinds of outputs.
Unless you tell Flare otherwise, default style settings will be used for the different outputs you generate. But there may be times when you want to override a default style setting for a particular output; that's why you would use a medium. You need to explicitly tell Flare which medium you want a particular target to use. This is done from the Advanced tab of the Stylesheet Editor.You can use the Target Editor to associate a medium with a particular target. See Associating a Medium with a Target.
- TOC—Master (Associate) Read more… In most situations, you will have one TOC that you use for a particular output (target). In that case, you simply associate the appropriate TOC with the target. If you have multiple TOCs that you want to include in the same project or output target, the TOC that you associate with the project or target serves as the "master" TOC. In your master TOC, you have the option of creating links to the other TOC that you want to include in the output. If you do not select a TOC, Flare will use the first one in the project (if there is more than one). If you have specified a master TOC at the project level and another at a target level, the TOC at the target will take precedence. See Associating a Master Table of Contents with a Target.
- TOC—Print-based Output (Auto-generate) Read more… You can select an option to let Flare auto-generate a TOC for you in print-based output. See Auto-generating TOCs for Print.
TOC—Print-based Output (Heading Levels, Unlinked Books, Remove Images) Read more… There are a few settings in the Target Editor that let you control how a generated TOC is produced in print-based output.settings
- Heading Levels Read more… You can select an option to base the heading levels of your generated TOC on the structure of the outline TOC. When you generate print-based output (Adobe FrameMaker, Adobe PDF, Microsoft Word, XHTML Book) with a topic containing a TOC proxy, a TOC is generated and included in the output. Unless you specify otherwise, the levels of the headings in the generated TOC are based on the h1 through h6 styles in your project (or other styles where you've entered a value for the mc-heading-level property). However, this option allows you to use an alternative method, basing the generated TOC on the exact structure that you create in the "outline TOC." See Determining Heading Levels for a Print TOC.
- Unlinked Books Read more… You can select an option to create headings in a generated TOC for books that are not linked in your outline TOC. See Creating Headings for Unlinked Books in a Generated TOC.
- Remove Images Read more… You can select an option to remove images from a generated TOC if you have inserted them into the headings in your topics. See Removing Images from Headings in a Generated TOC.
- Tracked Changes (Preserve) Read more… If you have tracked changes in Flare, you can preserve the changes so they are visible when you generate Word output.If you have tracked changes in Flare, you can preserve the changes so they are visible when you generate PDF output.If you have tracked changes in Flare, you can preserve the changes so they are visible when you generate PDF or Word output. See Preserving Tracked Changes in PDF or Word Output.
- Variables (Override) Read more… The variables that you create and define in the Variable Set Editor are available to your entire project. However, if you want the definition for a variable to be different in a particular target, you can override the project-level definition for that target in the Target Editor.
See Overriding Variable Definitions in Targets.
- View Output Read more… After you generate a target, you can view the output for it. See Viewing Output.
- WebHelp Plus (Enable) Read more… You can specify in the Target Editor the catalog that you are using for the output. In most cases, this will be Web, which is the default value. However, if you or someone in your company (e.g., network administrator) creates a custom catalog, you need to enter that name in the field. See Enabling WebHelp Plus Output.
- Word Output—Review Mode (Enable) Read more… If you want to automatically track any changes made to the Word document after you open it, you can enable review mode in the Word output. This will automatically enable the Track Changes feature in Word. See Enabling Review Mode in Word Output.
- Word Output—Mirror Margins (Enable) Read more… Let’s say you create a page layout with mirror margins on pages (e.g., the odd pages are set up to have a left margin of 2 inches and a right margin of 1 inch, whereas the even pages are set up to have a left margin of 1 inch and a right margin of 2 inches). In such a case, Microsoft Word is unable to display the correct margins without a little help. Therefore, you need to enable mirror margins by selecting a single check box in the Target Editor. When you generate Word output, you will then see the appropriate margins on each page. See Enabling Mirror Margins in Word Output.
- Word Output—Multiple Documents (Create) Read more… If you are generating Word output, you can split the generated output into multiple documents, rather than using the default, which results in only one document. To create multiple Word documents, you must also specify chapter breaks at the appropriate places in the TOC (not the TOC that displays in the Word output, but in the outline TOC used to determine the printed manual content and structure). This can be done on the Printed Output tab of the TOC Properties dialog. By specifying chapter breaks, you are letting Flare know where you want to split the output into new Word documents.
- XPS Output (Specify) Read more… Microsoft's XML Paper Specification (XPS) is a document format with a markup language that is a subset of XAML for Windows Presentation Foundation. XPS is an alternative to Adobe's Portable Document Format (PDF). By installing a free add-in download from Microsoft, you can generate output via Microsoft Word to the XPS format.
SeeSpecifying XPS Output Via Microsoft Word .
- Click to save your work.