Authoring - WinHelp projects

Existing WinHelp projects can be converted to a HelpServer application folder. You can drag and drop the hpj file on the ‘Applications’ root folder or on the ‘Contents’ root folder or one of its dependent folders and HelpServer will convert the content. You can also select the hpj file on HelpServer’s Import window.

WinHelp projects are converted according to the same working principles as when converting RoboHelp projects.

The next example explains the steps to import a simple WinHelp sample project.

Importing a WinHelp project

Popup the menu of the folder under which you want to import the content and select ’Import > WinHelp project’.

Selecting the file

Select the hpj file on the ‘File chooser’ and click ‘OK’ to continue.

Starting the import

Click ‘Start’ to start the import process.

Should the content to convert contain any files (images, audio, video, …) then the import process should be able to add these to the correct project gallery folders. That’s why the ‘Project gallery selection’ window will open. On this window you can see and change the different gallery folders. To enable you to convert content in the mass, this window will always open prior to the actual convert process.

The project gallery folders

Just click ‘Add now’ to continue. The purpose of the ‘Add later’ and the ‘Browse’ buttons on this window is explained in the section ‘Importing an entire tree with files’ of the chapter ‘Importing files and folders’.

If the option ‘Let me select the classes’ on the ‘Import window’ is selected then you will be prompted to select the class structure step by step. If that option is not selected, the default class structure is used. Since the default class structure is not always applicable, we advise you to choose the classes manually as shown in the next examples.

Assigning the main folder class

Topic class and topic type selection

In case the option ‘Let me select the language’ on the ‘Import window’ was checked then you will be prompted to select the language. Else the default working language will be used.

Language selection

Entering the project name

If you have selected a project folder class then you need to enter a unique project name.

And if files are involved all the files will be loaded.

Next you can continue by transforming the styles.

Mapping editor styles

Use the two lists in the upper part of the window to map new incoming styles to styles that already exist in the HelpServer environment.

If you have the required privileges you can also select the missing styles in the lower list. These will then be added to the active HelpServer editor style set. Click ‘OK’ to continue.

If not all styles are mapped or added the following message box will popup.

Message about missing styles

If you click ‘No’, you can review the mapping. If you click ‘Yes’, the convert will continue.

Eventually a message will inform you that not all styles are converted.

Message about inactive styles

The administrator can always reorganize the styles later. The next image shows the converted RoboHelp project in the Workbench.

A converted WinHelp project

All map ID are converted to pointers and resource IDs.


 About HelpServer
 Starting up and logging on
 The basic working principles
 Using the content in help and documentation systems
 Formatting the content
 Searching and replacing text
 Reusing content with shares
 Navigating with hyperlinks
 Navigating with pointerpaths
 Using bookmarks and jumps
 Duplicating content with clones
 Using tables
 Including media files
 Navigating to web pages
 Using embedded chunks
 Including html code
 Navigating with menus
 Using snippets
 Spelling checking
 Using the view mode
 Creating an index
 Creating a FAQ
 Creating a glossary
 Team authoring
 Working with projects
 Setting up structured authoring
 Generating file based output
 Creating printed output
 Importing files and folders
 Loading files in the project gallery
 Converting legacy content
 Word documents
 RoboHelp projects
 WinHelp projects
 WinHelp header files
 AuthorIT XML
 FrameMaker projects and pdf files
 Dita maps
 HelpServer XML
 Including legacy content in real time
 Transferring objects between installations
 Customizing the look and feel
 User accounts
 Working with templates
 Working with metadata
 Workflow management
 Using event exits
 Appendix A: The URL parameters
 Appendix B: The object indicators
 Appendix C: Play Javascript