The first step in
Following are the steps for creating a project by importing a RoboHelp project.
Note: For additional information, you can download the Transition from RoboHelp Guide:
madcapsoftware.com/support/files/documentation/FlareV4/FlareTransitionRHGuide.pdf
You can also work through the video tutorial
Flare Compared with RoboHelp.
How to import a RoboHelp project
Select File>Import Project>Import (Non-Flare) Project.
The Import Project Wizard opens.
to browse for and select the RoboHelp project file (MPJ or XPJ file) to be imported.
to browse for and select a folder.(Optional) Select Convert all topics at once if you want Flare to immediately convert all of your topic files to XHTML.
If you remove the check mark from the box, Flare imports the topic files as they are. When you try to open an imported topic in Flare, a message asks if you want to convert it to XML. Also, if this option is not selected, Flare will not import index keywords from the source files.
(Optional) Select Convert inline formatting to CSS styles if you want Flare to create new styles based on any "local" formatting that exists in the RoboHelp project files.
example
If you have applied bold and italic formatting to some text (without using a style), Flare will create a new style based on that formatting.
Note: This may result in dozens of new style classes being generated in your project.
Note: If you create more than one Flare project and need to share some of the same files or content in those projects, it is useful to import linked files from a global project. This is called "Global Project Linking."
Best Practice: Use Global Project Linking.
The project is imported and a new Flare project is created. Now you can move on to any of the other basic steps:
Note: You do not necessarily need to follow all of the above steps (and their substeps) in the exact order given. For example, as you add topics to a project (Step 2), you may want to start applying styles and formatting to them right away (Step 3), before adding other "stuff" to the project, such as a glossary (Step 2). However, the above sequence probably makes the most overall logical sense. For example, you must start a project before adding "stuff" (topics, content, cross-references, etc.) to it. And of course, you cannot distribute output to your end users (Step 6) until you build the final output (Step 5).