
What's covered?Sometimes you only have the output files for webhelp or a compiled chm file and nobody can locate the source files. This topic covers how to recover from that situation. I would like to thank Pete Lees who reviewed the first version of this topic and made some very useful comments, not least the advice you will find under Loss Prevention. |
The first step must be a very thorough search for the source files. It is definitely worth the effort. If you have Copernic Desktop Search or Google Desktop Search installed, make sure they point to the network locations you use and try to track the files that are in every project. Enlist the help of IT in looking through backups. These instructions are for when you really have exhausted all avenues.
This one is very easy for me to cover. Rick Stone has an excellent topic on his RoboWizard site! Click here.
When you have recovered your project, come back here and see the section below on Loss Prevention. Some of the suggestions there are just as relevant when recovering webhelp.
The basics have been covered across a number of posts on various forums. What I have done here is explain them a bit more fully and provide some options.
It is important with these methods that where you have to define the name of the CHM file, you use the name of the file you are decompiling exactly as it is. Do not, for example change myhelp.chm to myhelp2.chm. If change the name of the CHM file during the process, the glossary and browse sequence files will also be renamed. The necessary files will be in your folder but they will not appear in the project and the glossary and browse sequences will not show in your project.
See What's Lost for information about context sensitive help and conditional tags. Any index words that were contained in the source html files and any Stop words will be lost.
If you have a copy of FAR, then you have the tools you need.
Pete Lees posted details of a free tool that decompiles the CHM file and creates the HHP file in one process. Click here to download it.
HTML Studio can be found on the Tools tab or RoboHelp and the method is described on the Adobe site. Click here. You can either point HTML Help Studio to the CHM or you can right click the CHM and select Convert to Source.
You will also need to download the HHP builder. Click here.
No pretty interface. Just enter this into a command prompt window, amended as necessary.
hh.exe -decompile <target_directory> <path>\<filename>.chm
I have not tried this method but if Pete Lees says it works, it works.
Conditional Build Tags will be lost but any text that had a conditional build tag applied will, surprisingly, still be in the topics although not displayed. Use a multi file find and replace tool and search on condition: to find the names of the tags. Then create new tags with exactly the same names as those you find. Right click them and you will see the associated topics listed.
My thanks to Rick Stone for this one.
Before you undertake that work though, check with your developers. They should have a copy of the file that they can give you.
Any index words that were contained in the source html files and any Stop words will also be lost.
If you followed the instructions above but have still lost the index and table of contents, all is not lost. That is what I exactly what I found with a file that had been created using AuthorIt. Pete Lees identified the reason and recovering them is quite straightforward.
This section came about thanks to a brilliant suggestion from Pete Lees.
The previous section covers what most people will lose if they have to recover their source files from a CHM output. If you've been through that loss, then you may want to be better protected if the situation arises again.
I have listed below the various things that will be lost and the file that contains that information in a RoboHelp project. Pete's suggestion is that those files are added to baggage so that the procedures above will recover them. It's beautiful!
Data |
How to protect yourself |
| Stop List | Add yourproject.stp to the baggage files. |
| Map IDs / HHP file | If you add the .h file(s) to the baggage files that may cause them to show up in the results of a full-text search. You could make copies of the .h files and change the file name extensions to something else (say, .xh), and then add these copies to the project baggage or you could zip up the files and add the .zip file to the baggage. However that is a manual task so it is prone to error. |
| KLink and ALink keywords (that is, keywords embedded in the HTML source of topics) | KLink and ALink keywords are keywords that you have embedded in the HTML source of topics, rather than in the hhk file. The way to protect yourself against losing these keywords is not to use them! It's a trade off between the reason for using these keywords (they are automatically included in any project to which you may copy these topics) and the downside if the source files are lost. That's a choice you have to make. |
![]()
Date |
Changes to this page |
| 02 Dec 2007 | Reference to Convert to Source added to Method 3. |
| 09 Sep 2006 | Topic extensively revised to cover how Glossary, Browse Sequences, Conditional Tags, and Map IDs can be recovered. |
| 12 Feb 2005 | HHP file added to Map IDs row in table under Loss Prevention. |
04 Oct 2005 |
Method 4 added. What Will Be Lost? revised Loss Prevention added. |
03 Oct 2005 |
New topic. |