Need help converting modular chm files

Tagged: 

  • pcarbonn 3 years, 3 months ago

    I’m struggling to import a modular set of HTML help files in D2H. What is the best procedure to import them, and what is the target directory structure ? Couldn’t find documentation in the Modular Help chapter of the D2H user’s guide about this.

    Here are some hints :

    idisp.hhp contains:
    [MERGE FILES]
    CADcmdline.chm
    tblparm.chm

    the other hhp don’t have merged files

    Topics in idisp.chm contains links to command lines and related topics in the merged files, for example:

    I can’t get this to work in the chm files generated by D2H after conversion. Any help welcome.

  • 2p
    Brad Keller2p 3 years, 3 months ago

    Did you create this Modular CHM file using Doc-To-Help? Or did you create it using HTML Help Workshop? Or perhaps a different tool, such as RoboHelp?

    There may be an easier way to convert it rather than trying to convert the CHM file.

  • pcarbonn 3 years, 3 months ago

    This legacy help file was created with HTML Help Workshop and FAR HTML Help. Hence the need for conversion.

    To test the conversion, I build idisp.chm from the converted files. Normally, I should not lose any content or functionality, but unfortunately, links to command lines and related topics don’t work anymore.

  • -1p
    Nicky Bleiel-1p 3 years, 3 months ago

    A modular html help project must have a hub project that ties all of the child projects together. All projects must be at the same level in the directory structure.

    If you had links between your child projects, they will need to be adjusted, because links between modular projects are set up differently than links within a project.

    This section of the online Help explains more: http://helpcentral.componentone.com/nethelp/d2h2011/WordDocuments/creatingamodularhelpsystem.htm

    The topic on "File Organization" explains the directory setup. "Creating a Hub Project" explains how to setup a hub project, and the topic on "Creating a Child Project" explains how to setup the children and links between them.

    I’m not sure about the links to command lines; that would need to be looked at separately.

  • pcarbonn 3 years, 3 months ago

    Thank you Nicky.

    One problem is : how do I come to the File organisation explained in your online help, when I’m starting from legacy chm files generated in other tools. May I import/convert idisp.chm as a standalone file, and then set the "is a modular help project" flag to make it a hub project ? Then, how do I import/convert the other chm files as child of that project ? Or should I create an empty hub project, and import/convert all chm files as child of that project ? How ?

  • -1p
    Nicky Bleiel-1p 3 years, 3 months ago

    I would not use an existing file as the hub, because the hub project is the one that pulls everything together. I would set up all of the children in the proper structure, build them, then create and build the hub (this project would be flagged as "is modular hub project".

    Once that is done, then you can create the links from the hub to the children, then fix the links within the children.

    If you need to convert the children, you should open D2H and use the Getting Started Wizard to start your conversion. Save the converted projects to the appropriate place in the directory structure.

  • pcarbonn 3 years, 3 months ago

    Thanks. I’ll try that. Hopefully, fixing the cross-project links to command lines will be easy.

Viewing 7 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic.