330
USING ROBOHELP HTML 9
Generating Help and printed documents
Last updated 12/14/2011
•
RoboHelp Style Mapping.dot template
•
A Word default template
Add new styles to the template
Analyze project styles to see how they map to Word. Create new styles as necessary. Consider the following:
Missing styles
After conversion, drop-down and expanding text appears as inline text, for example.
Character styles
Styles can be mapped only to template styles of the same type. Create a matching character style
before generating. Mapping is easier when template and project style names match. For example, create Word
character styles.
Conditional text
Define conditional build expressions to exclude topics or topic content from printed documentation. Excluded topics
are denoted with a gray question mark icon
in the Print Document Content dialog box.
More Help topics
“
Define conditional build tag expressions
” on page 223
Single-source layouts
Use with conditional build tags to customize output and save the settings.
Share style mappings from a printed documentation layout with other authors to ensure consistency. Import style
mappings (ZPL file) into the project, or export mappings to another location.
Mapping styles
Mapped styles
Non-mapped styles are formatted as they appear in the Design Editor. Style maps are saved in a ZPL file.
Heading styles
For heading mapping to occur, a standard HTML heading style must be applied to topic titles. If custom heading styles
aren’t named in the format Heading <number>, they are not treated as headings.
Heading styles are automatically mapped to Word heading styles. To disable automatic mapping, select Maintain
HTML Heading Levels in the Print Document Content dialog box. Heading style levels are retained, regardless of their
position in the Print Document Content dialog box.
RoboHelp considers the RoboHelp project style applied to the heading and the placement of the topic in the printed
TOC hierarchy.
Generating a printed document TOC exactly like the project TOC creates Word documents with identical heading
styles and an identical TOC hierarchy. When the hierarchy of the TOC changes, the automatic process takes over and
assigns heading levels.
•
Books and pages at the root level are always Heading 1. If the project heading style is lower (such as a Heading 2),
it is adjusted up.
•
Books and pages with Headings 2 – 6 are adjusted according to their level in the printed document structure and
their project heading style. Different project heading styles are adjusted as needed.
•
Books and pages with Headings 7 – 9 are automatically mapped to Word Headings 7 – 9 styles.