Skip to main content
R
RoboHelper42
Participant
August 23, 2006
Question

Document's topics seem invisible

  • August 23, 2006
  • 2 replies
  • 370 views
I opened an existing project created and maintained in RoboHelp for Word X5.0.1 - and one of the files seems corrupted:
- In the Project view, the file can't be expanded to show topics inside it
- TOC is showing broken links
- Map Ids are there, all accompanying files are there - .ghc, .hh, .prs, .rbh and of course .rtf and .doc
- When I open the file using Edit from Project view, the topics are all there, seemingly nothing wrong with them (all RoboHelp markers are there)
- In the help file compiled few months ago, the topics and links to this problematic file are OK
- the problematic file didn't change since the last compilation, I was just about to edit it today when I realised I can't open it.
- I can't "re-attach" broken links in TOC because it doesn't see any topics from this file

Any ideas what went wrong - or what am I doing wrong?
This topic has been closed for replies.

2 replies

S
South_Coast_Surfer
Participating Frequently
August 24, 2006
I suppose it may be a corrupt Word file - try adding a new document to the project, then cut-and-paste a topic from the old to the new document. [If you can't open the old document in RH, try copying the rtf version to another location and open it directly using Word.] Can you then see that topic in the topic list? If so, try pasting all the topics. If the new document then exhibits the same problem as the old document then the corruption is within the text - hopefully just in one place. Trial-and-error will let you find exactly where.

Simon
S
South_Coast_Surfer
Participating Frequently
August 24, 2006
I suppose it may be a corrupt Word file - try adding a new document to the project, then cut-and-paste a topic from the old to the new document. Can you then see that topic in the topic list? If so, try pasting all the topics. If the new document then exhibits the same problem as the old document then the corruption is within the text - hopefully just in one place. Trial-and-error will let you find exactly where.

Simon
Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices