CSH after imported RoboHelp project and HHP file

[uwem]

One programmer based the CSH logic for the CHMs for the applications in the RHelp-Project on the HHP file. It was taken to read the names of the files in the [ALIAS] and [MAP] sections. The HHP file is as far as I can see no longer existent in Madcape 7. Is it somewhere hidden or is there a way that can it be created?

[i-tietz]

Alias file. Together with the .h files you will find it Project Organizer | Advanced.

[uwem]

Is the ALIAS file the file with the suffix flali ? Is it correct that the hhp file does not exist anymore compared to RoboHelp ?

[i-tietz]

"Yes." and "Yes." ...

[LTinker68]

Is the ALIAS file the file with the suffix flali ?

That's the extension in the authoring environment. When you build the output, I believe the file is converted to a .xml file.

EDIT: Oops, sorry, didn't realize we were in the HTML Help forum. The file conversion I was referring to is what happens when you build WebHelp output.

[RamonS]

When building CHMs the .hhp file should be in the temporary folder. Flare first crafts a project that can be used by HTML Workshop and then pulls that through Microsoft's CHM compiler. There should be a temp folder in the output folder unless MadCap puts that now somewhere else.

[Andrew]

RamonS is correct -- you can find the _Temp.hhp file inside your output folder, in Temporary Files for your target.

[uwem]

The answers are all deeply appreciated. We found the temp HHP file. T H A N K S! it is of great help !
2 additional questions:
1. In the FLALI file the path to the topic.htm is with "Content"
Example : <Map Name="English" Link="/Content/languageswitch/English.htm" />
In the CHM file, we looked into it with editor, then "Content" is not present. We assume to call the topic without the \Content\, right?
2. Is there a standard tool/function in Microsoft c++ for extracting the html-topic names from the xml-code in the flali-file ?

Uwe

[RamonS]

Now that you found the .hhp file then why not use the procedure that you used before? As far as processing the flali file, i doubt that Microsoft has routines for processing each and every proprietary XML format. If you want to go the XML route you need to parse the file and write a wrapper that picks up what you need, then spits it out in the format desired. Trying out how to get the correct parts is more work than coding the converter.