#### 16.1.1 Considering Help-system features

For HTML-based Help systems, DITA2Go can produce any specialized form of HTML you need, including those that work with proprietary DLLs.

If you have the eHelp (RoboHelp) license that permits you to redistribute the appropriate eHelp DLL, you can use DITA2Go to produce WinHelp 2000. You generate WinHelp, then add the eHelp data to the WinHelp project file before you compile; see §17.2.8 Integrating WinHelp from RoboHelp. Also, you can generate HTML Help as a precursor to using RoboHelp to generate WebHelp; see §16.1.4 Evaluating WebHelp.

If you need something similar to WebHelp or Web Works Help, try generating OmniHelp; see §16.1.5 Evaluating OmniHelp. Otherwise you would have to roll your own, which you could do with DITA2Go frameset support; see §22.12 Using framesets. OmniHelp provides a simpler and faster solution.

If you need Microsoft Help Viewer 1.x (the successor to Microsoft Help 2), you can generate HTML Help with DITA2Go and then use mshcMigrate (part of the Helpware FAR tool set) to convert the resulting .chm file:

mshcMigrate | http://mshcmigrate.helpmvp.com/home
FAR | http://www.helpware.net/FAR/index.html

Microsoft Help Viewer 1.x is the local Help that ships with Visual Studio 2010 and its associated MSDN Library; see:

http://www.helpware.net/mshelp3/

See also §16.5.2 Preparing index entries for Microsoft Help Viewer.

To produce electronic books and content for mobile devices, see §22.1 Deciding which type of output to produce.

Previous Topic: 16.1 Weighing Help-system alternatives

Next Topic: 16.1.2 Evaluating Microsoft Windows Help (WinHelp)

Parent Topic: 16.1 Weighing Help-system alternatives

Sibling Topics:

16.1.2 Evaluating Microsoft Windows Help (WinHelp)

16.1.3 Evaluating Microsoft HTML Help

16.1.4 Evaluating WebHelp

16.1.5 Evaluating OmniHelp

16.1.6 Evaluating JavaHelp and Oracle Help for Java

16.1.7 Evaluating Eclipse Help