To merge output means to connect multiple projects in such a way that the source files are combined into a single online output. The merging is based on the table of contents (or browse sequence) in one master project, where links point to one or more child projects.
- Runtime Merging Flare Projects Using Targets (Recommended) Use this merging method if you have access to all of the Flare project files to be merged. You can merge projects together by linking targets with the same output type (e.g., linking Microsoft HTML Help to Microsoft HTML Help, linking WebHelp to WebHelp). This is one of the easiest method to use for merging projects.
See Runtime Merging Flare Projects Using Targets.
Runtime Merging Output from Microsoft HTML Help Projects Use this merging method if you are developing Microsoft HTML Help (a CHM file) and you want to merge your output with another CHM file. This method is useful, for example, if another author is working on the external Microsoft HTML Help project to which you are linking and you only have access to the other CHM file (not the project files).
See Runtime Merging Output from HTML Help Projects (CHM Files).
Note: You can also link to CHM files from the TOC in all web-based outputs (HTML5, WebHelp, WebHelp Plus). However, linking to a specific topic within the CHM is not supported in these outputs.
See Linking to CHM Files.
- Runtime Merging Output From Flare WebHelp Projects Use this merging method if you are developing HTML5, WebHelp, or WebHelp Plus and you want to merge the output files from your parent project with the web output files from an external Flare project. This method is useful, for example, if another author is working on the external web project to which you are linking and you only have access to the output files (not the project files).
See Runtime Merging Output from Flare WebHelp Projects.
- Runtime Merging Output Using Server-Based HTML5 or WebHelp Plus Use this merging method if you are developing HTML5 or WebHelp Plus and you are hosting the output files on a web server running Microsoft IIS. This is an easy way to merge the output from multiple
WebHelp Plus or HTML5 server-basedFlare targets into one Help system. These targets can be originated from the same Flare project or from different Flare projects. You simply place the output files in the correct location on the server (i.e., within your master project's AutoMerge folder). Flare then automatically merges the output from all of the targets when users access the Help. From the end user's perspective, the results are seamless, appearing as one large Help system. All of the TOCs, browse sequences, indexes, glossaries, and search capabilities for the projects are merged. See Runtime Merging Server-based HTML5 Output and Runtime Merging Output Using WebHelp Plus.
Note: If you are working with HTML Help and import a RoboHelp project that has been merged with other CHM files, the linked CHM files are placed in a special subfolder in the Content Explorer (Resources > CHMSupport).
Note: If you want to create navigation links from content in one project to content in another project, see Inserting Links to External Files—HTML, PDF, Microsoft Office.
Note: If you have previously merged Flare projects with WebHelp outputs and then decide to generate WebHelp Plus output from the master project instead, you must make sure that the child projects linked to the master contain at least one WebHelp Plus target each. Even if you keep the link from the master project to a WebHelp target in the child, the child project must also have a WebHelp Plus target.
Note: If you merge projects, synonym files will remain separate in each project. For example, if you create synonyms in Project A but not in project B, only the topics from Project A will use the synonyms when users perform searches in the output.
Note: You can stitch existing PDFs into your output by adding links to them in a table of contents (TOC). This is supported in PDF output and all of the online targets.
Note: Flare's HTML5 Side and Top Navigation skins do not support runtime project merging.