2 Replies Latest reply on Apr 20, 2010 4:11 PM by LAN_INTL

    RoboHelp 8.02.208 Conversion Problems


      We have a large body

      of  documentation in RH5 and we have successfully converted several projects in our initial test. So far there do not

      seem to be any issues with style. However, conversion of a RH7 project to

      RH8 has me completely baffled. I verified that the correct style sheet was select

      ed, but the interline spacing, alignment of bullets, and in some cases the conditional tags are a nightmare. Everything looks fine in the files until I go to generate the help file. The resulting file is not acceptable. I'm assuming part of this problem is due to the way RH8 handles multi-level lists. Why the conversion from RH5 has been less problematic has me scratching my head. So what do I need to do to get a large RH7 project properly converted?

        • 1. Re: RoboHelp 8.02.208 Conversion Problems
          Peter Grainge Adobe Community Professional (Moderator)

          Each forum has a Sticky Topic, Before You Post. http://forums.adobe.com/thread/467760


          Please start each thread with the edition and version of RoboHelp that you are using. I am assuming you are using RH HTML.


          The code changed in RH7 and again in RH8 so I'm guessing the problem is related to the upgrade from 7 to 8, although that does really help us. It just maybe explains the difference.


          The problem with lists is that many people have set up paragraph styles as list instead of using the LI tag. There are many posts on the forums about this. Also you might like to look at Willam van Weelden's pages at http://www.wvanweelden.eu/robohelp/lists/lists.php


          Tags and spacing have not been an issue though. Try creating a new layout pointing to a new folder.


          See www.grainge.org for RoboHelp and Authoring tips



          • 2. Re: RoboHelp 8.02.208 Conversion Problems
            LAN_INTL Level 1

            Thanks for your reply. Most of the formatting and spacing issues were resolved when the trouble was traced to Internet Explorer 8. Setting IE 8 to Display all webites in Compatibility View resolved most of the issues. The other issue was a complex topic with numerous conditional tags that could not be resolved except by starting all over again and redesigning the topic. I essentially created two topics and applied conditions at the topic level to solve the problem.