Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

Publishing linked FM files to WebHelp in RH - horrible results

Community Beginner ,
Mar 21, 2012 Mar 21, 2012

We are using FrameMaker 10 and RoboHelp 9 in a Windows 7 environment.

We have a FrameMaker book that contains the following, all of which are linked chapter files to two other books:

  • TOC
  • Home page (made just for the WebHelp content)
  • Chapter 1
  • Chapter 2
  • Chapter 3
  • Chapter 4
  • Chapter 5
  • Chapter 6
  • Glossary
  • Index

We perform the following steps:

  1. Open RoboHelp, and notice the empty Starter tab.
  2. On the Green opening RoboHelp menu, click Create New > Blank Project.  The New Project Wizard window appears.
  3. Enter the project name and specify the location, then click Finish.
  4. Select File > Project Settings, and verify all settings are correct. (Point to the ISF file we want.)
  5. When the new blank project loads, select File > Link > FrameMaker document.  The Open window appears.
  6. Navigate to the FrameMaker book file, and click Open. The linked book files appear under Project Files in the Project Manager pod. In the linked FrameMaker files, we see the Glossary chapter and the Index chapter.
  7. Delete the "First Topic" file that RoboHelp created in step 3.
  8. Right-click on the book file in the Project Manager pod, and select Update > Generate. We think this step generates HTML topics based on the pagination/topic levels specificed in the ISF file.
  9. After generating html topics from the linked FramMaker book files, right-click on the book file in the Project Manager pod and select Properties.
  10. On the Contents tab of the “FrameMaker Document Settings” panel, check all 3 boxes to “convert FrameMaker” TOC, Glossary, and Index files.  For the TOC, navigate to the FrameMaker TOC file of the book.
  11. Select the radio buttons to “Create new associated” TOC, Glossary, and Index.
  12. RH insists that you name them, so name them Contents, Glossary, and Index.
  13. Click OK to close the window.
  14. Back to the Project Manager pod, right-click the new TOC, Glossary, and Index files (one at a time) and select the option to set these as the Default ones.
  15. With the book file selected, select File > Generate > Primary Layout (WebHelp).  The WebHelp Settings window appears.
  16. Verify that <Default TOC>, <Default Index>, and <Default Glossary> are selected under Content Categories / Content <Default>.
  17. Click Save and Generate.  RoboHelp generates the WebHelp.  A dialog window appears that says: Result: WebHelp has built successfully.
  18. Click, "View Result."

The above steps produce an empty set of help files. No TOC, no content, no nothing.  So we do the following:

  1. In Project Manager pod, select book.
  2. Right-click, Update > Update All.
  3. Select File > Generate > Primary Layout (WebHelp).

At this point we get 95% of what we expected.

These are the issues we see in the WebHelp output:

  1. The WebHelp merged chapter 2 into chapter 1, by appending the chapter 2 content onto the end of chapter 1.  Why?
  2. There is a Glossary document icon at the bottom of the WebHelp TOC, and Glossary icon in the toolbar.  Both are empty. (The Glossary chapter in the FM book contains several dozen terms.)  How can we get the glossary terms/definitions to show up in WebHelp?
  3. There is an Index document icon at the bottom of the WebHelp TOC, and an Index icon in the toolbar.  The Index document icon in the TOC is empty, but the Index icon in the toolbar contains the information we want. We want to get rid of the Index document icon in the WebHelp TOC.  How?
  4. The home page, which shows up as the first document in the Project Manager pod in RH, does not show up in the WebHelp TOC (although when you launch the WebHelp, it is the default opening content).  How do we make the home page show up at the top of the WebHelp TOC?

We have spent at least 50 resource hours trying to troubleshoot this, so any help would be appreciated.

Tim

873
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Mar 21, 2012 Mar 21, 2012

We have resolved issue #1.  We had a Heading 1 style that was obsolete, and was not replaced at the beginning of chapter 2.  When we updated the paragraph style with the current Heading 1, the FM file became its own chapter.


We still have not resolved issues 2, 3, and 4.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Mar 22, 2012 Mar 22, 2012
LATEST

#2 & #3 are probably caused by not selecting the conversion of the glossary & index before creating the RH topics

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Resources
RoboHelp Documentation
Download Adobe RoboHelp