Best Pratice: Flare 1 – Reporting

The first of our mini-series of tips for Flare, here we consider how to leverage that old RoboHelp licence to squeeze some extra information out on your Flare HTMLHelps. 

It is advisable to ensure the following checks towards the end of a help project:

1. Technical correctness check by Designer
2. Help integrity checks by Technical Author
3. Grammatical check by Proof Reader
4. Accessibility check by the Tester
    

The second stage here requires a high degree of reporting information. To aid us with this we need to leverage functionality in RoboHelp until the reporting in Flare is updated. The following process enables you to gain a whole host of additional information about your Flare HTMLHelp project. Perhaps you CAN have your cake and eat it:

1. Towards the end of your help project in flare.
2. Generate output and save a log of the issue as a report.
3. Run through this report, correcting the errors.
4. Generate output again.
5. Take a copy of the temporary output from:
   1. PROJECT\Output\USER\Temporary\Microsoft HTML Help\Content.
6. Open the _Temp.hhp in your legacy copy of RoboHelp.
7. Work through the topics in the RoboHelp Broken links section to fix links back in flare.
8. Select the TOC in Robohelp, check through the list for topics not included in the TOC. Add these items into the TOC back in Flare as appropriate.
9. Select Tools | Report in RoboHelp and use any additional reports to check content.