Robohelp 2019 - Import Word Document - Do Not Want Topics To Import Alphabetically

I just found the RoboHelp 2019 project I set up explaining how numbered topics work. I think that by using the CSS there, you should be able to get numbered headings post import.

See the Contact page on my site and email me. I will send you the project.

www.grainge.org

I hit the multiple bookmarks problem when doing some testing. Go back to you Word document and go to Insert > Bookmarks. Tick Show Hidden Bookmarks. I think you will then see a whole lot more bookmarks than you thought were there.

You can either clean up there or fix the unwanted bookmarks in RoboHelp.

I believe there is another thread about the numbered headings.

www.grainge.org

I don't know if this was taken care of in version 10. I'm using RH2019 version 10. I imported a word doc with numbered headings and the RoboHelp project did create the topics in the same order as the word doc. However, how do I number the headings in the RoboHelp project? After importing, the project removed the numbering from the headings and I see a lot of bookmark symbols in the Heading. Is that because the word document had a TOC with hyperlinks? Even if that was the case, why multiple bookmarks? Please advice!

An option would be to use numbered headers in the Word document, as the imported files are named like the header they origin from. However, with update 8 it was not possible to import a Word document with numbered headers. I don't know if this works with update 9.

I would like the order of the topics that result from importing a Word file to match their original order in the Word file.

In our current development process SMEs are providing content in Word files, and the order of the topics (Header 1s) in the Word files should be reproduced in the output.

The current design, alphabetizing the resulting imported topics

• makes editing and QC of the file more difficult
• adds to the effort of using Auto TOC or negates the value of Auto TOC entirely, since the resulting topic sequence will always be wrong
• adds to the effort of producing browse sequences

Thanks for sharing feedback on the same. We will look into this improvement and add as part of our roadmap.

thanks

Amitoj Singh