Adobe Using Adobe® RoboHelp® HTML 8 Robo Help 8.0 Instructions For Robohtml En

User Manual: adobe RoboHelp HTML - 8.0 - Instructions for Using Free User Guide for Adobe RoboHelp Software, Manual

Open the PDF directly: View PDF .
Page Count: 374

Download
Open PDF In Browser	View PDF

Using

ADOBE ROBOHELP HTML 8
®

Last updated 3/1/2010

Using Adobe® RoboHelp® HTML 8 for Windows®
If this guide is distributed with software that includes an end user agreement, this guide, as well as the software described in it, is furnished under license and
may be used or copied only in accordance with the terms of such license. Except as permitted by any such license, no part of this guide may be reproduced, stored
in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, recording, or otherwise, without the prior written permission of Adobe
Systems Incorporated. Please note that the content in this guide is protected under copyright law even if it is not distributed with software that includes an end
user license agreement.
The content of this guide is furnished for informational use only, is subject to change without notice, and should not be construed as a commitment by Adobe
Systems Incorporated. Adobe Systems Incorporated assumes no responsibility or liability for any errors or inaccuracies that may appear in the informational
content contained in this guide.
Please remember that existing artwork or images that you may want to include in your project may be protected under copyright law. The unauthorized
incorporation of such material into your new work could be a violation of the rights of the copyright owner. Please be sure to obtain any permission required
from the copyright owner.
Any references to company names in sample templates are for demonstration purposes only and are not intended to refer to any actual organization.
This work is licensed under the Creative Commons Attribution Non-Commercial 3.0 License. To view a copy of this license, visit
http://creativecommons.org/licenses/by-nc/3.0/us/
Adobe, the Adobe logo, Adobe AIR, Adobe Captivate, Acrobat, Dreamweaver, ExtendScript Toolkit, FlashHelp, FrameMaker, Reader, RoboHelp are either
registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries.
Microsoft, Windows, Windows Vista, and ActiveX are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other
countries. Apple and Mac OS are trademarks of Apple Inc., registered in the United States and other countries. Java and Sun Microsystems are trademarks or
registered trademarks of Sun Microsystems, Inc. in the Unites States and/or other countries. Linux is the registered trademark of Linus Torvalds in the United
States and other countries. UNIX is a registered trademark of The Open Group in the United States and other countries. Arial is a trademark of The Monotype
Corporation registered in the U.S. Patent and Trademark Office and certain other jurisdictions.All other trademarks are the property of their respective owners.
Portions of this product utilize technology created by Gilles Vollant.
This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (http://www.openssl.org/).
This product includes cryptographic software written by Eric Young (eay@cryptsoft.com).
This product includes software developed by The Independent JPEG Group.
This product contains either BESAFE and/or TIPEM software by RSA Data Security, Inc.
Portions utilize RSA Data Security, Inc. MD5 Message-Digest Algorithm.
Portions utilize Windows Media Technologies. Copyright©1994-2002 Microsoft Corporation. All Rights Reserved.
Portions of this product were created using LEADTOOLS© 1991-2001, LEAD Technologies, Inc. All Rights Reserved.
The Proximity Database ©Copyright 2008. All rights reserved. Proximity Technologies, Inc.
Adobe Systems Incorporated, 345 Park Avenue, San Jose, California 95110, USA.
Notice to U.S. Government End Users. The Software and Documentation are “Commercial Items,” as that term is defined at 48 C.F.R. §2.101, consisting of
“Commercial Computer Software” and “Commercial Computer Software Documentation,” as such terms are used in 48 C.F.R. §12.212 or 48 C.F.R. §227.7202,
as applicable. Consistent with 48 C.F.R. §12.212 or 48 C.F.R. §§227.7202-1 through 227.7202-4, as applicable, the Commercial Computer Software and
Commercial Computer Software Documentation are being licensed to U.S. Government end users (a) only as Commercial Items and (b) with only those rights
as are granted to all other end users pursuant to the terms and conditions herein. Unpublished-rights reserved under the copyright laws of the United States.
Adobe Systems Incorporated, 345 Park Avenue, San Jose, CA 95110-2704, USA. For U.S. Government End Users, Adobe agrees to comply with all applicable
equal opportunity laws including, if appropriate, the provisions of Executive Order 11246, as amended, Section 402 of the Vietnam Era Veterans Readjustment
Assistance Act of 1974 (38 USC 4212), and Section 503 of the Rehabilitation Act of 1973, as amended, and the regulations at 41 CFR Parts 60-1 through 60-60,
60-250, and 60-741. The affirmative action clause and regulations contained in the preceding sentence shall be incorporated by reference.

iii

Last updated 3/1/2010

Contents
Chapter 1: Getting started
Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Activation and registration
Help and support

............................................................................................ 1

...................................................................................................... 2

Services, downloads, and extras

........................................................................................ 7

Introduction to RoboHelp

............................................................................................. 7

What’s new in RoboHelp 8

............................................................................................. 8

Chapter 2: Exploring the workspace
Workspace overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Working with pods
Environments

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Menus and toolbars

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Create or remove keyboard shortcuts

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Chapter 3: Projects
Project basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Create and open projects
Manage projects
Manage files

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Manage folders

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Authoring content in multiple languages
Import PDF files

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Importing and linking Word and FrameMaker documents
Importing and linking Microsoft Word documents
Import FrameMaker documents
Import a DITA map file
Import XML files

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Import Microsoft HTML Help projects
Import WinHelp projects
Reports
Reference

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Chapter 4: Working with topics
Create, save, and open topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Author in XHTML

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Import and copy topics

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

View topics and design elements
Master pages
Manage topics

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Manage resources

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Check spelling and find and replace

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

USING ROBOHELP HTML 8 iv

Last updated 3/1/2010

Contents

W3C compliance
Reference

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Chapter 5: Editing and formatting
RoboHelp editors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Character formatting and fonts
Format paragraphs

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Borders, backgrounds, color, and sound
Tables
Lists

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Headers and footers
Text boxes

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

User-defined variables

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

Single-source with snippets
Reference

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Chapter 6: Styles and style sheets
Style types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Manage style sheets

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Create styles for style sheets
Table styles
List styles

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

Apply styles

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Edit styles in CSS files

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Delete styles from style sheets
Use color and images
Inline styles

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

Chapter 7: TOCs, indexes, glossaries
TOCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Indexes

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

TOCs and indexes in Microsoft HTML Help
Glossaries

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

Glossary hotspots

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

Chapter 8: Linking and navigation
Navigation basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Create text links

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

Link to a pop-up

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

Bookmarks

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

Link images and multimedia
External links
Link View

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

Link maintenance and repair
Link controls

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

Text-only pop-ups

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

RoboHelp Search

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

Browse sequences

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192

USING ROBOHELP HTML 8 v

Last updated 3/1/2010

Contents

Chapter 9: Multimedia and special effects
Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Adobe Captivate demos
Multimedia

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

Dynamic HTML and special effects
Marquees

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204

HTML comments in topics
Iframes

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

Chapter 10: Conditional text
Conditional text basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
Conditional build tags

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

Conditional build tag expressions

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

Chapter 11: Context-sensitive Help
About context-sensitive Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Author and developer roles in creating context-sensitive Help
Map files and map IDs

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

Information for developers
What’s This? Help

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245

Maintaining text-only topics (Microsoft HTML Help projects)
Working with text-only topics

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250

Testing context-sensitive Help

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252

Context-sensitive Help terms

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254

Reference

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255

Chapter 12: Generating Help and printed documents
Single sourcing basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
Work with layout types

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257

Generate, view, and publish output
Distribute the project output
Printed documents
Skins

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311

Windows

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316

Chapter 13: Advanced program features
ActiveX controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
Applets

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325

Forms

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326

Frames

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329

HTML Help controls

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332

Information types (for HTML Help)
Scripts

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337

About ExtendScript Toolkit support
Twisties

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339

USING ROBOHELP HTML 8 vi

Last updated 3/1/2010

Contents

Chapter 14: Integrating with Adobe Technical Communication Suite
Importing FrameMaker documents into RoboHelp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
Send PDF files for review

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363

Start an online meeting using ConnectNow

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364

Chapter 15: Default keyboard shortcuts
Index

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368

Last updated 3/1/2010

Chapter 1: Getting started
Resources
Before you begin working with your software, take a few moments to read an overview of activation and the many
resources available to you. You have access to instructional videos, plug-ins, templates, user communities, seminars,
tutorials, RSS feeds, and much more.

Activation and registration
To review complete system requirements and recommendations for your Adobe® RoboHelp® 8 software, see the
ReadMe file on the installation disc.

Install the software
1 Close any other Adobe applications open on your computer.
2 Insert the installation disc into your hard drive, and follow the onscreen instructions.

Note: For more information, see the ReadMe file on the installation disc.

Help with installation
For Help with installation issues, see the Installation Support Center at www.adobe.com/support/robohelp.

License activation
During the installation process, your Adobe software contacts an Adobe server to complete the license activation
process. No personal data is transmitted. For more information on product activation, visit the Adobe website at
www.adobe.com/go/activation.
A single-user retail license activation supports two computers. For example, you can install the product on a desktop
computer at work and on a laptop computer at home. If you want to install the software on a third computer, first
deactivate it on one of the other two computers. Choose Help > Deactivate.

Register
Register your product to receive complimentary installation support, notifications of updates, and other services.
Note: Register only once for RoboHelp 8.
❖ To register, follow the onscreen instructions in the Registration dialog box, which appears after you install the

software.
If you postpone registration, you can register at any time by choosing Help > Registration.

Last updated 3/1/2010

USING ROBOHELP HTML 8 2
Getting started

ReadMe
A ReadMe file for your software is available online and on the installation disc. Open the file to read important
information about topics such as the following:

• System requirements
• Installation (including removing the software)
• Activation and registration
• Troubleshooting
• Customer support

Help and support
Community Help
Community Help is an integrated environment on Adobe.com that gives you access to community-generated content
moderated by Adobe and industry experts. Comments from users help guide you to an answer. Search Community
Help to find the best content on the web about Adobe products and technologies, including these resources:

• Videos, tutorials, tips and techniques, blogs, articles, and examples for designers and developers.
• Complete online Help, which is updated regularly and is more complete than the Help delivered with your product.
If you are connected to the Internet when you access Help, you automatically see the latest online Help rather than
the set delivered with your product.

• All other content on Adobe.com, including knowledgebase articles, downloads and updates, Adobe Developer
Connection, and more.
Use the Help search field in your product user interface to access Community Help. You can search for content within
the Adobe.com site and also in websites that have useful information about your product. Moderators continue to
identify the most relevant web content for your product. You can add comments to online Help and view comments
added by other users. For a video of Community Help, see www.adobe.com/go/learn_community_help_en.

Adobe Help Viewer 2
Adobe Help Viewer 2 is an Adobe® AIR® application that seamlessly merges the online and offline experience. When
online, you get the most recently updated product Help on the web. You can also access an Adobe PDF version of Help.
When offline, you access Help installed with the product on your system. Adobe Help Viewer 2 has a user-friendly
interface that supports advanced navigation features. For example, you can get overviews of topics through mini TOCs
and bookmark local and online content.
The search feature supports both online and offline modes. Adobe Help Viewer 2 searches content in Community
Help when you are online and the Help installed with the product when you are offline. Online search suggestions offer
relevant results from product Help, Adobe.com, and other websites. Offline search uses indexes to return preferred
topics for key terms.
You can use the commenting feature to post your comments to Adobe.com or add notes for your own reference. Your
feedback on Help content is welcome.
Note: For a video of Adobe Help Viewer, see www.adobe.com/go/learn_air_viewer2_en.

USING ROBOHELP HTML 8 3

Last updated 3/1/2010

Getting started

Opening Adobe Help Viewer
Typically, you access the Adobe Help Viewer from a product by pressing the F1 key, or by accessing the Help menu
on the product interface. In addition, you can access the Adobe Help Viewer, just like any other application, from the
Windows start menu.

Adobe Help Viewer interface
Adobe Help Viewer includes a top navigation bar, a two-pane Help display, and a comments pane.
A

Adobe Help Viewer
A. Back navigation B. Forward navigation C. Favorites D. Comments E. Search F. Product list G. Browse sequence H. Online toggle button

Navigation bar includes the following controls:
Browsing History buttons View next and previously displayed help topics.
Favorites Manage favorites.
Search A search bar where you can enter any term and find its occurrences in the installed Help (offline mode), latest
web Help and Community Help (online mode). Use Community Help search to find answers to your questions from
across Adobe.com and identified resources for your product.
Comments Add and view comments on any topic viewed through the viewer. If you have an Adobe ID for accessing

Adobe website such as Acrobat.com, then you can post your comments to the Adobe Community Help server.
Moderators can then respond to comments and use them to keep improving the product.
Product list Select the Help system for your product from the list of installed products that support Adobe Help

Viewer.

Last updated 3/1/2010

USING ROBOHELP HTML 8 4
Getting started

Note: If there is only one product installed in your system, then the viewer turns off the Product list options.
When you select the Help system for a product from the Product Name field, or launch Help from a product, the
following information appears:

• A link to the online PDF file containing the Help system.
• TOC with the home page of the Help system, if you select the Help system from the viewer. If you launch the Help
from the product which has context-sensitive Help, the context-sensitive Help page appears. You can view the next
on the upper-right part of the Help pane.
and previous topics by clicking the arrow keys
Browsing Help topics
You can navigate to Help topics in the following ways:

• Select a topic from the table of contents
• Select the mini-TOC, See also references, or cross-references in the right pane
• Click the link on a search result
• Use navigation buttons in the right pane to sequentially navigate topics
• Use the links in the Favorites pane or RSS feeds
• Use browse buttons to display last viewed and next topics
• Open a context-sensitive Help topic from your product
Based on the view mode, topics you view are fed from the online Help location or the installed product Help.
Toggle online/offline mode
1 Move the pointer over the Online/Offline toggle button at the right bottom corner of the Adobe Help Viewer.
2 Click Go Online or Go Offline.

Switch between online and offline modes

If you change the setting, the previously set preference is used when launching the viewer. While online, if the viewer
loses connectivity, the viewer displays an error, and shifts to offline mode. When you toggle the online/offline mode,
the viewer opens the previously viewed Help page. If this page is not available or if the previously viewed page did not
belong to the Help system, the home page of the Help system opens.
The content browser history is reset when you toggle the online/offline setting. The viewer displays comments for that
pane based on the selected mode. Favorites and RSS feeds are common to both online and offline mode. Pre-populated
favorites and RSS feeds change across products.

Managing favorites
You can bookmark any Help page in the Help system or on the Internet as a favorite. Bookmarks help you build an
information repository within the viewer without having to access a browser.
Bookmarks are listed in the Links section of the Favorites pane. You can also subscribe to any RSS feed and view it.
When you select any RSS feed, the viewer updates the specified RSS feed in the right pane.
Note: Adobe Help Viewer supports RSS.92, .93, 1.0 and 2.0 versions.

USING ROBOHELP HTML 8 5

Last updated 3/1/2010

Getting started

You can add links and RSS feeds of your choice and view them in both online and offline mode. Some links are prepopulated. For example, you can quickly access links to the product page, or troubleshooting RSS feeds from the
Favorites pane.
View the Favorites pane
❖ Do one of the following:

• Click the Favorites
• Click the arrow

icon and select View Favorites from the pop-up menu.

icon (available at center left of Help pane) to display the Favorites pane.

Add a link as favorite
1 Click Add Link at the bottom of the Favorites pane.
Note: The link to current open web page or topic in Help content is pre-populated in the Add New Link dialog box.
2 Enter the link name and the URL in the Add New Link dialog box, and click OK.

Add an RSS feed
1 Click the RSS Feeds tab in Favorites pane.
2 Click Add RSS Feed at the bottom of the Favorites pane.
3 Enter the RSS feed name and the URL address in the Add New RSS Feed dialog box, and click OK.

The new RSS feed is added in the selected folder. Unread feeds appear in bold face.
You can also add links or RSS feeds using the

Add or View Favorites button.

Manage links and RSS feeds
From the Favorites pane, you can do the following:

• Delete, rename, or edit a link or RSS feed using the context menu.
• Create a folder to store links or RSS feeds. You can also drag-and-drop favorites across folders.
• Delete individual link items or RSS feeds in a folder or move them to other folders before you delete a folder.

Search Help content
Adobe Help Viewer provides powerful search options. In online mode, which is the default mode, you can search
across the community Help content for your product (select the Include Community Help option). Alternatively, you
can search only in the selected Help system (select This Help System Only option).
Community search results include following information:

• The latest version of the complete product Help (including comments moderated by experts.)
• Community content hand-picked by Adobe and industry experts, including videos, tutorials, tips and techniques,
blogs, articles, and examples for designers and developers.

• Other content on Adobe.com, including TechNotes, downloads and updates, Adobe Developer Connection
tutorials, and more.

• A custom search on Community Help content. Adobe experts work to ensure that the top search results include a
mixture of content, including product Help.

• A product portal page called the Help and Support page to access all the components of Community Help for a
specific product.

USING ROBOHELP HTML 8 6

Last updated 3/1/2010

Getting started

Adobe Help Viewer supports search suggestions indexed by the author, Community Help moderator, and search
engines. As you enter search text, you get search suggestions.

Keyword suggestions in the Search box

In the offline mode, you can search within local Help only.

Managing comments
You can use the commenting feature to add notes to any topic viewed through the viewer. You can view these
comments for later reference. Alternatively, you can post the comments to the Adobe Help Community server if you
are connected to the Internet.
You need an Adobe ID to post comments in the Adobe Help Community server. However, you can add comments in
your local Help system in the offline mode without signing in.
View the Comments pane
❖ Do one of the following:

• Click the Comments
• Click the dotted line

icon.
icon at bottom center of the Help pane.

Add private comments in local Help topics
1 Click Add Comments in the Comments pane and enter your comments.
2 Select the Keep Private check box, and click Save.

Note: In the offline mode, the Keep Private check box is selected by default.
Post comments to the Adobe Community Help Server
1 Open any Help topic from the online Help system or content from a website URL for commenting.
2 Click the Sign In URL to sign in with your Adobe ID.
3 (Optional) Click the Create A Free Adobe ID link to create an account.
4 (Optional) Enter the details in Create An Adobe ID dialog box, and click Sign In.
5 Click Add Comments in the Comments pane and enter your comments.
6 Clear the Keep Private check box, and click Save.

Other resources
Online Help also includes a link to the complete, updated PDF version of Help.
Visit the Adobe Support website at www.adobe.com/support/robohelp to learn about free and paid technical support
options.

Last updated 3/1/2010

USING ROBOHELP HTML 8 7
Getting started

Download the documentation of older versions of RoboHelp from
http://www.adobe.com/support/robohelp/documentation.html.

Services, downloads, and extras
You can enhance your product by integrating various services, plug-ins, and extensions in your product. You can also
download samples and other assets to help you get your work done.

Adobe Exchange
Visit the Adobe Exchange at www.adobe.com/go/exchange to download samples as well as plug-ins and extensions
from Adobe and third-party developers. The plug-ins and extensions can help you automate tasks, customize
workflows, create specialized professional effects, and more.

Adobe downloads
Visit www.adobe.com/go/downloads to find free updates, trials, and other useful software.

Adobe Labs
Adobe Labs at www.adobe.com/go/labs gives you the opportunity to experience and evaluate new and emerging
technologies and products from Adobe. At Adobe Labs, you have access to resources such as these:

• Prerelease software and technologies
• Code samples and best practices to accelerate your learning
• Early versions of product and technical documentation
• Forums, wiki-based content, and other collaborative resources to help you interact with like-minded users
Adobe Labs fosters a collaborative software development process. In this environment, customers quickly become
productive with new products and technologies. Adobe Labs is also a forum for early feedback. The Adobe
development teams use this feedback to create software that meets the needs and expectations of the community.

Adobe TV
Visit Adobe TV at http://tv.adobe.com to view instructional and inspirational videos.

Introduction to RoboHelp
Adobe RoboHelp 8 software is designed for developing Help systems, eLearning content, policies and procedures, and
knowledgebases. Its enhanced editing and layout capabilities enable you to create professional looking content. You
can publish this content to multiple channels, including Adobe AIR for an integrated online and offline user
experience.
Worldwide, Adobe RoboHelp 8 is a leader of online Help authoring tools through innovation. New features create a
more productive experience for technical communicators and their audiences.

Last updated 3/1/2010

USING ROBOHELP HTML 8 8
Getting started

What’s new in RoboHelp 8
Authoring enhancements
XHTML support RoboHelp creates topic files in Extensible Hypertext Markup Language (XHTML) and project-

specific files in XML. Structured authoring in XHTML ensures well-written code, closed tags, no overlapping of tags,
properly quoted attributes with explicit values, and no proprietary attributes. RoboHelp upgrades all the old RoboHelp
HTML topics to XHTML when it upgrades or imports them.
You can import an XHTML or HTML topic from the File menu and open the topic to edit in HTML view directly. For
detailed Help, see “Author in XHTML” on page 104.
Enhanced editing support in Design Editor The enhanced Design Editor in RoboHelp 8 lets you use advanced list and

table styles, drag and drop text in tables, and merge and split table cells. It provides clean code with no proprietary tags.
All the RoboHelp specific code is in the form of XML standard processing instructions (PIs). For more information
on lists and styles, see “Author in XHTML” on page 104.
World Wide Web 3 Compliance (W3C) RoboHelp 8 provides an option to validate topics and projects for W3C
compliance. It displays error messages or warnings that appear for any noncompliance with W3C. See “W3C
compliance” on page 120.
List and table enhancements RoboHelp 8 supports advanced lists and autonumbering. You can apply styles to change
the appearance of lists. See “List styles” on page 147.

Enhanced table support allows you to insert columns and rows in a table, and cut, copy, and paste columns, rows, and
cells. You can merge and split cells and insert a table within a table. See “Create and manage table styles” on page 146.
Enhanced language support RoboHelp 8 provides multiple-language support at the paragraph, topic, and project

level. The language defined at a paragraph level takes precedence over the language defined at a topic or project level.
The language that takes precedence at a level is called the effective language. The effective language is used in spellchecking, the dictionary and thesaurus, generation of the smart index, and preparation of the full-text search, not only
at a project level but also at a topic and paragraph level. See “Support for multiple languages” on page 45.
Insert HTML comments, iframe You can insert an HTML comment at any location in a topic. These HTML comments

are added in a particular format and viewed in a pop-up window. See “HTML comments in topics” on page 204.
You can insert an iframe in an HTML topic to include another HTML page or PDF file in it. You can also access URL
links to view a web page in an iframe. See “Iframes” on page 205.

Import enhancement features
Project-based common import settings Create a standard set of conversion settings for importing Adobe®

FrameMaker® or Microsoft® Word content into RoboHelp projects and use these settings across multiple projects.
These settings include FrameMaker or Word templates, Cascading Style Sheets (CSS) for RoboHelp projects, style
mapping between FrameMaker formats or Word styles and RoboHelp styles, and all other settings specified in the
Conversion Settings dialog box.
Direct import of HTML or XHTML files You can import HTML or XHTML files directly from File > Import >

HTML/XHTML File.
Enhanced FrameMaker document import In RoboHelp 8, you can import and link FrameMaker 8 and 9 books.

Last updated 3/1/2010

USING ROBOHELP HTML 8 9
Getting started

RoboHelp 8 maintains content integrity for imported FrameMaker content. RoboHelp retains lists, tables, images,
SWF content, conditional text, variables, tables of contents (TOCs), indexes, glossaries, and user-defined markers as
processing instructions (PIs). Enhancements in importing FrameMaker files allow for the following:

• Enhanced Add or Import settings from a common user interface
• New workflow
• FrameMaker template support
• Import styles for style mapping (table styles, list styles, and image settings)
• Enhanced import of vector graphics
• Import of alt text for anchored frames
• List conversion option for each style
• Import and export of settings
• Pagination on FrameMaker styles
• Custom HTML tag for each style
• Ignoring empty topics (after pagination)
• Project upgrade
Enhanced Word document import and linking RoboHelp enables you to include Microsoft Word document formats
(*.doc, *.docx, *.docm, *.rtf) as source files in RoboHelp 8. You can add Microsoft Word documents to a RoboHelp
project, update them when the Word documents change, and generate different single-source outputs. The source
documents as well as generated topics, CSS, images, multimedia, the TOC, the index, and the glossary are visible in
RoboHelp. You can manage, preview, sync, and control Word documents from RoboHelp. You can link Microsoft
Word documents in RoboHelp by copy or reference. See “Importing and linking Microsoft Word documents” on
page 54.
DITA content import RoboHelp 8 allows for the import of a DITA map file or a DITA topic into an existing RoboHelp

project. You can also import a DITA map file to create a RoboHelp project and publish the desired output. See “Import
a DITA map file” on page 84

Single-sourcing features
New CSS editor The style-editing interface is new, letting you change the most common properties quickly. The new
Style editor enables you to define new styles such as lists and table styles. You can define multilevel lists and
autonumbering in the Style editor. Using the Style editor, you can change images in twisties, and in drop-down and
expanding hotspots. See “Manage style sheets” on page 143.
Styles and Formatting pod The Styles and Formatting pod enables you to apply styles and lets you access the Style
editor to create a style or edit a style. See “Create a style using the Styles And Formatting pod” on page 145.
Master pages support Master pages separate content from the layout. Master pages also act as a template for a

particular HTML topic. In RoboHelp 8, you can define the placement of headers, footers, and HTML text. You can
add placeholders for breadcrumbs and mini TOCs in master pages. See “Master pages” on page 107.
Resource Manager pod The Resource Manager stores all the common resources to use across projects and allows for

quick access and management of common resource files. See “Resource Manager pod” on page 15.
Formatted user-defined variables A formatted user-defined variable is a single-sourcing inline element containing
styling information. Using the new Design Editor especially designed for editing variable styles, you can apply
formatting on the text and insert images, multimedia, and FLA files. See “Format a user-defined variable” on page 139.

Last updated 3/1/2010

USING ROBOHELP HTML 8 10
Getting started

Apply master pages or CSS in SSL Single-source layouts let you override master pages or the CSS when output is
generated. For different output results, you can apply different master pages or a different CSS to all the topics in a
project. See “Applying a master page or CSS at the time of generation” on page 110.

Publishing features
Adobe AIR The Adobe AIR output type allows you to generate Help in Adobe AIR format. The cross-platform Adobe

AIR Help format provides several enhancements, such as these:

• Easy navigation through breadcrumbs
• New templates and skins
• A rich branding experience, and the ability to insert corporate logos and an About box in Help
• Rich commenting and auto-updates
• Browser-based Help, with both offline and online content
• Ability to add and access RSS feeds
• Enhanced search
See “Adobe AIR layout” on page 269.
Search enhancements New RoboHelp search supports the following features:

• Ranking of search results
• Keyword search
• Synonym search
• Excluded topic search
• Multiple-language search
• Substring search
• Phrase search
• Customizable search results list
• Topic context in search list
• Baggage file search
See “RoboHelp Search” on page 191.
Enhanced printed documentation options Apply either a Microsoft Word template or a style sheet to the content

when you generate output.
Breadcrumbs and mini TOCs Use placeholders for breadcrumbs and mini TOCs in master pages and topics. Generate

or preview Help to automatically insert the breadcrumbs and mini TOCs. See “Insert a placeholder” on page 109.
Glossary enhancements In RoboHelp 8, a topic always has the updated definition for a marked term. The Glossary

Hotspot wizard inserts markers for the terms defined in the glossary. It does not insert definitions. Instead, RoboHelp
adds definitions when you generate previews or output. Thus a topic always has the updated definition for a marked
term. See “Glossary hotspots” on page 174.
Merged project enhancements Merged project enhancements introduce the concept of a child project referring to a

master TOC. Child projects automatically synchronize with the merged TOC, and you can see the merged TOC in the
child projects.

Last updated 3/1/2010

USING ROBOHELP HTML 8 11
Getting started

DHTML effects support in Safari and Firefox Some RoboHelp layouts support DHTML effects in Safari and Firefox
browsers. The supported DHTML effects include Spiral In, Spiral Out, Zoom In, Zoom Out, Show, Fly In, Fly Out,
and Elastic.
Twisties Use twisties in the CSS editor to enhance glossary terms, drop-down text, and expanding text. You can

change images in twisties for open and close. RoboHelp displays glossary terms, drop-down text, and expanding text
with images to expand or collapse them. See “Twisties” on page 339.

Productivity features
Scripting support In RoboHelp 8, you can create your own scripts to automate repetitive tasks and key workflows.
The Script Explorer pod enables you to execute and manage scripts, and you can execute your scripts using the
command-line parameters.

RoboHelp provides a set of sample scripts that you can use right away or customize for your needs. You can access
these sample scripts, such as Word Count, UDV Converter, EclipseHelp.jsx, SaveAsProjectTemplate.jsx, or Link
Converter, or create your own scripts using the Script Explorer pod. See “About ExtendScript Toolkit support” on
page 338.
Adobe ExtendScript Toolkit 4.0, included with RoboHelp 8, enables you to author and debug scripts.
Integration with Adobe Captivate 4, RoboSource Control 3.1, and RoboScreenCapture® Create and edit Adobe

Captivate® 4 demos and simulations from within the RoboHelp HTML application.
While installing RoboHelp HTML 8, you have the option to install RoboSource Control™ 3.1 to control the versions of
projects.
You can open and edit images using RoboScreenCapture from within the RoboHelp HTML application.
Custom To Do list RoboHelp 8 helps you manage a To Do list, facilitating addition and deletion of To Do items from
the project. By default, RoboHelp 8 supports 11 To Do list items. See “Using the To Do list” on page 39.

Usability features
Project Manager enhancements In the Project Manager pod, you can customize the ordering of topics in folders to

define a chapter layout for the project. The Auto-Create TOC feature uses the ordering to create a logical TOC. You
can sort the order of folders and topics alphabetically.
Option to install RoboHelp for Word The RoboHelp 8 installer gives you the option of installing RoboHelp for Word.

By default, the option is not selected.
File type mapping In RoboHelp 8, you can associate various file types with applications installed on your system. See

“Map file types” on page 40.
Re-create the project cache The new Re-create Project Cache option re-creates the project CPD file before opening
the project. This option ensures that you don't have to delete the CPD file manually.
Windows Explorer support Locate files and folders on your system using Microsoft® Windows® Explorer. In the

Project Manager and Project Set-up pods, right-click and select the Explore option to locate files or folders.
Desktop icons during installation You can opt to create desktop icons during installation.
Support for Adobe® Flash® content In RoboHelp 8, you can insert FLV files and play them in Flash® Player, which is

provided with RoboHelp 8.

Last updated 3/1/2010

USING ROBOHELP HTML 8 12
Getting started

Additional browser support In RoboHelp 8, you can open web-based Help in different browsers such as Firefox,
Safari, and Microsoft Internet Explorer. This support is improved for Firefox and Safari browsers.
Change default TOC, index, and glossary In RoboHelp 8, you have an option to set any TOC, index, or glossary as the

default.
Topic tab support You can close a topic from the topic tab by choosing File > Close, or by pressing Ctrl+F4.

Last updated 3/1/2010

Chapter 2: Exploring the workspace
Workspace overview
The RoboHelp workspace includes pods, panes, and customizable toolbars and menus. Expanding menus track
commands you frequently use and display them on a shortened version of each menu. You can also customize
keyboard shortcuts and add new toolbars.
Multiple Document Interface (MDI) support lets you edit multiple topics concurrently. You can paste objects and
selections across multiple topics. You can select horizontal or vertical tiling of topics.
A

C
D

RoboHelp workspace
A. Design Editor B. C. D. Clubbed pods

Working with pods
Pods are workflow panes that you can float or dock anywhere in the application window. They provide quick access to
logically grouped features from one location. For example, you can select and generate various layouts from the Single
Source Layouts pod.
RoboHelp provides access to your most frequently used pods and projects, with flexible options. You can move a pod
anywhere on the screen or to a different monitor. Use the auto-hide feature of pods to show or hide them on the
desktop.

Last updated 3/1/2010

USING ROBOHELP HTML 8 14
Exploring the workspace

View a pod
❖ Select View > Pods > [pod name].

Types of pods
Starter pod
The Starter pod provides links to common commands and product information.
Open A Recent Project Open recently used projects (up to ten recent projects are listed) and other projects.
Create New Select the Help type you want to generate.
Import Import a Help project, such as an HTML Help project, Word document, and all other available types.
Resources Access forums, developer centers, knowledgebase articles, and other online content.
News Announcements Access information about Adobe products.
View Online Help Access the complete online Help.
Quick Tour Of RoboHelp Link to the RoboHelp product page on the Adobe website.

Project Manager pod
The Project manager pod contains various folders where you create and delete project files, or edit their properties.

More Help topics
“Project Manager folders” on page 42

Project Set-up pod
The Project Set-up pod contains the following folders:
Windows folder Containers for output. Custom windows for projects are stored in this folder. Modify window
properties by double-clicking a window icon.
Master Pages folder Use master pages to reuse information and create a standard appearance across topics.
Skins folder Use skins with WebHelp or FlashHelp projects to change the appearance of the Help system. You can
match the appearance of a company website or add interest and style to the output. Use skins to customize colors,
buttons, text, fonts, icons, backgrounds, multimedia (FlashHelp projects), images for TOC icons and navigation
buttons, and more.
Context-Sensitive Help folder Container for the Map Files folder and the What’s This Help Files folder.

• Use the Map Files folder to access map files and perform most window-level context-sensitive Help tasks.
• Use the What's This Help Files folder for field-level context-sensitive Help in HTML Help projects.

More Help topics
“About context-sensitive Help” on page 212
“Map files and map IDs” on page 213

Last updated 3/1/2010

USING ROBOHELP HTML 8 15
Exploring the workspace

Snippet pod
Add custom HTML code snippets to a project for insertion later into desired topics. When you modify a code snippet
shared by different topics, the changes are reflected in all the associated topics.
Snippets are stored in a Snippet library as separate files with the .hts extension and always appear in a sorted order in
the Snippet pod. You can drag snippets to desired locations in a topic. You can also select snippets and then copy,
duplicate, or delete them. Select the Preview option from the context menu to preview a snippet.

More Help topics
“Single-source with snippets” on page 141

Styles And Formatting pod
Use the Styles And Formatting pod to apply styles quickly. Select a style in the pod and apply it to the selected text in
the topic. You can create and edit a style directly from the pod. Right-click the name of a style to rename, delete, or
preview that style.
Note: Select Format > Styles to view the Styles And Formatting pod. You must open a topic to view the Styles And
Formatting pod.

More Help topics
“Create a style using the Styles And Formatting pod” on page 145

User Defined Variables pod
From the User Defined Variables pod, you can accomplish these tasks:

• Create, edit, or delete variables.
• Create, edit, or delete variable sets.
• Provide and modify run time values uniquely for different variable sets while generating the output.
• Format variable values.

More Help topics
“User-defined variables” on page 138

Error List pod
The Error List pod shows buttons for errors, warnings, and messages which are displayed when you try to validate a
topic or a master page. You can click these buttons to display the relevant information in the Error list. The caption of
buttons shows the number of errors, warnings, and messages. You can click all of these buttons to display the relevant
information.

Resource Manager pod
The Resource Manager stores all the common resources to use across projects and allows for quick access and
management of common resource files.
Root folder Stores all folders or files in the root folder.
Category The Category folder is in the root folder. The contents of the Category folder, including the subfolders,

appear in the Resource Manager pod. If the Category folder is not present in the root folder, the Resource Manager
pod is empty.

Last updated 3/1/2010

USING ROBOHELP HTML 8 16
Exploring the workspace

File Type Lists the extensions associated with a category. (Each category has its own file type.) From the file type, you
decide which category the file belongs to.

You can preview the following files in the Resource Manager pod:

• Snippets
• Images
• HTML
• XML
• TXT
• Multimedia

RoboHelp Server pod
The RoboHelp Server pod enables you to connect to RoboHelp Server. You can configure the setup for the server by
selecting WebHelp Pro or FlashHelp Pro as the primary layout. You can enter the Servername:port/contextname/server and connect to it to publish your projects.

Environments
A RoboHelp environment refers to the arrangement of various workspace components, such as pods, in the main
application window.

Create and save an environment
You can create multiple environments for a project. Only one environment is loaded at a time.
1 Arrange pods.
2 Select File > Environment > Save Environment.
3 Type a filename, including the .rhs extension.
4 Specify a location for the environment. The default location is C:\Documents and Settings\[user name]\My

Documents\My RoboHelp Projects.
Note: You can exchange an RHS file with other authors.

Load an environment
1 Select File > Environment > Load Environment.
2 Browse to an RHS file and select it.
3 Click Open.

Note: The last environment you used before closing RoboHelp is used the next time you open RoboHelp.

Restore the default environment
❖ Select File > Environment > Load Default Environment.

Last updated 3/1/2010

USING ROBOHELP HTML 8 17
Exploring the workspace

Menus and toolbars
Customize menus
1 Right-click a toolbar and choose Customize.
2 Click the Commands tab.
3 Choose New Menu from the Categories list.
4 In the Commands section, click New Menu and drag it to the location where you want it to appear on the menu bar.
5 Right-click the New Menu item on the menu bar and click inside the Name field.
6 Type the desired menu name and press Enter.
7 Choose different categories and drag the desired commands to the menu.
8 Click Close.
9 Restart RoboHelp HTML to preserve changes.

Customize toolbars
1 Select View > Toolbars > Customize.

Note: You can also right-click a toolbar and choose Customize.
2 Do any of the following:

• To create a toolbar, click the Toolbar tab. Click New, type a name, and click OK.
• To add an item to a toolbar, click the Commands tab. Select a category, and drag a command to the toolbar.
• To edit a newly added toolbar item, right-click its icon in the toolbar and select options, such as Delete and
Name. The Begin Group option inserts a separator bar to the left of the item.
You can use an ampersand (&) in the name to add keyboard shortcuts. For example, for the Format menu, an
ampersand precedes the letter "o" in “Format”. To access the Format menu using the keyboard shortcut, press
Alt + O.

• To edit menus and toolbar items, click the Options tab. Set the following options as needed:
Always show full menus Select this option to show all the available menus.
Show full menus after a short delay Select this option to show few menus on starting the application and few

after a short delay.
Reset menu and toolbar usage data Click this button to delete the records of all the new or modified commands

you have used and restore the default settings.
Large icons Select this option to show large icons for the menus.
Show Screen Tips on toolbars Select this option to show Screen Tips on the toolbars.
Show Shortcut Keys In Screen Tips Select this option to show keyboard shortcuts in Screen Tips.
Menu animations Select an animation type from the pop-up menu.

More Help topics
“Create keyboard shortcuts” on page 18

Last updated 3/1/2010

USING ROBOHELP HTML 8 18
Exploring the workspace

Enable and disable smart menus
Smart menus display only the most frequently used commands. To access the hidden commands, click the down arrow
at the end of the command menu.
1 Right-click a toolbar.
2 Select Customize.
3 Click the Options tab.
4 Select or deselect Always Show Full Menus under Personalized Menus And Toolbars.

Create or remove keyboard shortcuts
Create keyboard shortcuts
1 Select View > Toolbars > Customize.
2 Click the Keyboard tab.
3 Select a command category.
4 Select a command to assign to a keyboard shortcut.
5 Type the keyboard shortcut in the Press New Shortcut Key box.
6 Click Assign.

Remove or reset keyboard shortcuts
1 Select View > Toolbars > Customize.
2 Click the Keyboard tab.
3 Do one of the following:

• To remove a keyboard shortcut, select the category and command for the shortcut to remove. Select the shortcut
in Key Assignments, and click Remove.

• To restore all shortcuts to their defaults, click Reset All.

Last updated 3/1/2010

Chapter 3: Projects
Project basics
Basic workflow
1. Create a project.

Every Help system has at least one project. The basic element of the project is the topic.
2. Author the content.

Create topics. You can add multimedia now, or later when you customize the output. Work with the application
developer to start planning which topics to also use for context-sensitive Help. Context-sensitive topics appear when
the user clicks a Help button in the user interface or presses F1.
3. Import files.

You can import HTML files, Microsoft Word files (.doc, .docx, .docm, .rtf), FrameMaker books and documents (.book,
.bk, .fm, .frm, .mif), XML files (.xml), and Adobe PDF files (.pdf).
4. Develop the navigation.

Based on the hierarchy, or organization scheme, of the content, create links among topics and to external content if
necessary. You can also link text or images to other content. Create a table of contents that reflects the content
hierarchy, and include an index that users can browse. You can also create browse sequences, paths a user can follow
through Help topics. For example, if a user must read several related topics to understand a feature completely, you
can link them in a browse sequence.
5. Customize the output.

You can apply layouts (which determine behavior and appearance) and formatting. You can also use conditional text
to show or hide content, depending on user interest, application being used, skill level, and other factors. Add
multimedia to make your Help more compelling and richer.
6. Create, test, and distribute the Help package.

Create the output so you can view the Help and check links, formatting, and so on. Test every output you intend to
distribute, including printed documentation.

About projects
Projects contain the source files that become the final Help system. Help authors work with the project files, and Help
users view the output. For CHM output, the project contains the content you create and the properties you set up, such
as what the output window looks like. The developer determines the window for webhelp and flashhelp output
formats, or leaves them to run in your browser window. Create folders in the Project Manager to organize topics and
structure the Help system.

Last updated 3/1/2010

USING ROBOHELP HTML 8 20
Projects

Projects are collections of files. The project file (XPJ file) contains information about the content and properties of the
project. Whenever you change the project, this file (and any other affected file) is updated automatically. Project files
consist of the following:
Content Project files contain topics with content and information about the location of topics, images, index, TOC,
and other files.
Properties Projects contain setting information, such as project title, language, and windows. When you first create a
project, the basic (default) settings are used. Modify these settings according to your design needs.
Navigation Projects include a table of contents, index, and full-text search.

You can view the elements that make up a project in several places, including the Project Manager, Single-Source
Layouts pod, and Project Settings dialog box. You can also generate various reports (Tools > Reports) that identify
project status, duplicate topics, files distributed with Help, and so on.

Help project components
Help systems are made up of different components that vary according to the Help format you deliver.
Projects RoboHelp HTML creates a main project file (with the extension .xpj) that contains the information about

your topics, images, and other files. (Open this file to open a project.) Project files also contain the settings that affect
the appearance and functionality of a Help system.
Topics The basic unit of a Help system is the topic. Topics communicate the message of the Help system, mainly
through text and images. You decide the content, format, and organization of your topics.
Table of contents If a table of contents is included, users see a Contents tab or button when they open the Help system.
The table of contents presents a hierarchical outline of what the Help project contains. Users can browse and select
topics to view from the Contents tab.
Indexes If an index is included, users see an Index tab or button when they open the Help system. The index displays

a multilevel list of topics and keywords or phrases that you’ve specified.
Full-text search Full-text search allows users to find specific words and phrases that occur in the content.
Links and navigation Users navigate a Help system by clicking links. You design the strategy that connects your topics

together. The most common links are from one topic to another. Links can also go to topics in different Help systems,
different output formats, and even to a website or an application.
Styles You format topics using styles. Styles are named formats that you design and apply to control the layout and
appearance of text.
Image and multimedia files Images and multimedia files enhance Help by adding graphics, sound, video, animation,

and more.
Windows Windows are the frames that display topics. In certain output formats, you can customize the appearance

and attributes of windows. You can also design new windows to suit your content. You can open multiple windows
and from the Windows dialog box, select a window and click Activate to bring it to focus. Click Save to save the
displayed window in focus. Using the Windows feature, you can rename the project title to display in the output.
Compilers The Help compiler isn’t part of the final Help file, but you sometimes need a compiler to create the Help

file. For example, in Microsoft HTML Help projects, the compiler aggregates the source files and other project
components. The compiler then creates one Help system file that you distribute to end users. (WebHelp and FlashHelp
projects are not compiled.)
Viewers and browsers Users access the Help system from within a viewer or browser.

Last updated 3/1/2010

USING ROBOHELP HTML 8 21
Projects

Files in a project
Main project file (XPJ)
The project file (.xpj) is XML-based. You can open project files with the .mpj extension, the format for older versions
of RoboHelp, but they convert to XPJ files.

Folder files (FPJ)
Each project folder has an FPJ file that lists the folder contents. RoboHelp displays only those subfolders and topics
that are listed in the FPJ file of a folder.
All the subfolders have their respective FPJ files. The name of an FPJ file except the FPJ file for the project folder is
same as that of the folder.
The name of the FPJ file for the project folder is root.fpj. The root.fpj file is modified if you add, delete, or rename a
topic or subfolder inside the respective folder. The root.fpj file is also modified if the order of topics or subfolders is
changed in Project Manager.

Single-source layout files (SSL)
A single-source layout file (SSL) is used for each single-source layout. An SSL file stores the properties of the respective
single-source layout and is modified when you edit the properties. An SSL file does not get modified on generating,
viewing, or publishing a single-source layout.

Auxiliary project files (APJ)
The following components have corresponding APJ files, which get modified when you edit the components:

• Baggage files
• Colors
• Conditional build tags
• Font sets
• Information types
• Map files
• Pop-up note topics
• See Also keywords
• Skins (when adding or removing skins only)
• Single-source layouts (when adding or removing single-source layouts only)
• Topic keywords
• Topic templates (when adding or removing single-source layouts only)
• Windows

Other types of files
When you modify the following components, the respective file gets modified:

• Browse sequences (BRS)
• Topics (HTM)
• TOC (HHC)

Last updated 3/1/2010

USING ROBOHELP HTML 8 22
Projects

• Index (HHK)
• Glossary (GLO)
• Image and multimedia files (filename extension varies)
• Style sheets (CSS)

About output types
RoboHelp can generate the following output types. These types have common basic characteristics but different
features and viewing and platform requirements.
WebHelp Adobe WebHelp format works with virtually any combination of browser and platform for web-based or

desktop applications, online Help, and online books. WebHelp also provides customizable navigation panes and quick
downloads.
WebHelp Pro WebHelp Pro is used for web-based applications, with features available only in server-based Help.

WebHelp Pro provides feedback on the use of your Help system. Authors can work on separate projects and publish
anytime, and projects are merged on the server at run time. RoboHelp Server is required to generate WebHelp Pro.
FlashHelp Adobe FlashHelp® uses Adobe Flash® to provide an interactive navigation pane, customizable navigation

controls, Flash animation, streaming video, audio, and graphics. Users need Flash Player.
FlashHelp Pro FlashHelp Pro is used for web-based applications, with features available only in server-based Help.
Authors can work on separate projects and publish anytime, and projects are merged on the server at run time.
RoboHelp Server is required to generate FlashHelp Pro.
Microsoft HTML Help Microsoft HTML Help is used as application and stand-alone Help for Windows 98 and later,

using Internet Explorer 4.x or later, and provides unique features.
Note: Due to Microsoft security changes, Microsoft HTML Help is now used where the Help has to be run on the users
PC; it cannot be installed on a server without registry changes. WebHelp and FlashHelp are used where the Help is to be
run from a server. WebHelp and FlashHelp can be run locally, but it is not recommended.
XML XML output exports to Extensible Markup Language (XML) format, used to structure, store, and send

information. XML files use style sheets, as well as handler files. Handler files determine how RoboHelp imports or
generates the XML files, associated style sheets, and related components.
JavaHelp JavaHelp, from Sun Microsystems™, works with Java applications and is a delivery system, not an authoring

tool. JavaHelp features (TOC, index, searches, controls, global search and replace, pop-ups) are created automatically,
along with HTML features (links, Related Topics buttons, and image files).
Oracle Help Oracle Help for Java™ is used with applications written in any language. Oracle Help and the ICE 5
browser provide TOC, index, full-text searches, pop-ups, context sensitivity, and customizable windows, through the
Oracle Help viewer.
Printed documentation RoboHelp enhanced printed documentation provides control over structure, content, and

appearance of printed documents. You can organize the content as needed, format using CSS or Word template styles,
and produce formatted and structured Word documents or PDF files.
Adobe AIR The Adobe AIR output type allows you to generate Help in Adobe AIR format. Generate your content in

the cross-platform Adobe AIR Help format that brings a host of enhancements, such as these:

• Easy navigability through breadcrumbs, and more
• New templates and skins
• A rich branding experience, and the ability to insert corporate logos and an About box in Help

USING ROBOHELP HTML 8 23

Last updated 3/1/2010

Projects

• Rich commenting and auto-updates
• Browser-based Help, with both offline and online content.
• Ability to add and access RSS feeds
• Enhanced search

End-user viewer requirements
End-user system WebHelp/Pro

FlashHelp/Pro

Microsoft HTML
Help

JavaHelp*

Oracle Help

AIR Help

Windows XP SP4
or later, XP, Vista

Web browser

Web browser
with Flash Player
8.0 or 9.0

Built-in viewer

JavaHelp viewer

Oracle Help
viewer

AIR Help Runtime

Mac OS, Linux®

Web browser

Web browser
with Flash Player
8.0 or 9.0

Not available

JavaHelp viewer

Not available

AIR Help Runtime

* Requires JavaHelp viewer, Sun Java 2 JDK or later, and JavaHelp 1.0 or later components.

Create and open projects
Create a project
1 Do one of the following:

• Select File > New > Project.
• In the Starter pod, click More under Create New.
2 On the New pane in the New Project dialog box, double-click a project type. You can change the project type after

your project is created.
Blank Project Customize and publish a project in any output. You can modify the window settings for WebHelp,

FlashHelp, and HTML Help outputs.
Application Help Create a Help system that you can install locally. The Application Help project has sample topics
with notes on how you can customize and modify the information. For example, you can create a Help system to
document information about a company product.

Note: By default, the Application Help does not use master pages or snippets but you can always add them.
e-Handbook Create a project for an electronic handbook, such as an employee handbook for a company. The eHandbook project template provides the relevant folders and topics for you to place company-specific information.
e-Learning Integrate and organize Captivate demos into a project. Using the layout and recommendations

provided, you can create computer-based and web-based training.
Knowledge Base Create a knowledgebase that has an interface similar to a wiki page. The knowledgebase project
template contains master pages that you can customize. You can also create self-updating pages.
Web Application Help Create a Help system that you can publish on a server. The Web Application Help project
has sample topics with notes on creating online Help for a software application.

Last updated 3/1/2010

USING ROBOHELP HTML 8 24
Projects

Department Guidelines Create a Help system to outline guidelines for a department in a company. For example,

you can create Help for a human resources department, outlining guidelines on recruitment and selection, flexible
working hours, and so on.
Disaster Recovery Plan Create a Help system with samples on how to write a disaster recovery plan.
Online Manual Create an online manual for a company product or software application.
Policies And Procedures Create a handbook or a document listing policies and procedures specific to an

organization.
Custom Customize a Help project template.

Specify options in the New Project Wizard dialog box:

• Leave Language as English or select another language to localize the project. Spell checking, indexing with the
Smart Index Wizard, and parts of the user interface are localized.

•

If you select Save As Default, the selected language is used for all new projects.

4 Click Finish.

The first topic opens in the Design Editor on the right. On the left, the Project Manager opens. The first topic is selected
in the HTML Files (Topics) folder.

More Help topics
“Change project settings” on page 29

Create a project by importing documents
1 Do one of the following:

• From the Starter pod, select a new project type from the Import list.
• Select File > New > Project. Click the Import tab and select a new project type.
2 Follow the prompts. The new project opens in RoboHelp.

Create a project using FrameMaker or Word documents
You can create new projects by importing FrameMaker or Word documents. While importing, you can map the styles
of these documents to styles in RoboHelp.
1 Select File > New > Project and click Import.
2 Select FrameMaker or Word documents and click OK.
3 Select from .book, .mif, .fm, .bk, and .frm files for FrameMaker and .doc, .docx, .rtf, and .docm files for Word. You

can import multiple FrameMaker or Word documents at the same time. You can import .book and .bk files one at
a time.
Note: For any FrameMaker format other than MIF, FrameMaker 8 or later is required. If the correct version is not
installed, you cannot import the file.
4 Enter the project title, filename, and location of the project.
5 Click Finish.

A new project wizard prompts you to select options to map the TOC, index, or glossary.
6 Select the required options, and click Next.
7 Click Edit.

USING ROBOHELP HTML 8 25

Last updated 3/1/2010

Projects

8 Select styles to map to the RoboHelp styles.

For information about different conversion options for FrameMaker documents, see “Conversion basics” on
page 72.
For information about different conversion options for Word documents, see “Converting Word styles to
RoboHelp styles” on page 59.
9 Click OK.

Note: If you click Cancel in the wizard, no files are imported and the empty project remains open.
10 Click Finish.

Create a project using a DITA map file
Important: For expert users only.
Before you import a DITA map file, Java JDK and the DITA Open Toolkit must be installed and running properly.
Experience with DITA and the DITA Open Toolkit is also required.
1 Select File > New > Project.
2 Click the Import tab.
3 Select DITA Map File.
4 Click OK.
5 Enter the following information in the New Project wizard:
DITA Map File To Import Specify path to a valid DITA map file that you want to import and create a project. Click

the Browse button

to select the file.

Location Of The Project Specify path to the location of the new project.

6 Click Next.
7 Specify the input required on the Open DITA Toolkit Processing Options dialog box.
8 Click Finish.

More Help topics
“Import a DITA map file” on page 84
“Converting Word styles to RoboHelp styles” on page 59

Define chapter layout
You can define a chapter layout for a project to order topics and folders logically in the Project Manager pod. The
default order is alphanumerical. You can drag folders and topics to customize the sequence. RoboHelp uses the
customized order to auto-create a TOC.
Notes:
• If you rename a folder or a topic, the topics and folders retain their order.

• If you delete a topic or a folder, the remaining topics retain their order.
• If you add a new topic or a folder, it is added at the top inside the parent folder.
• If you drop a topic or a folder on a non-topic/folder item (such as CSS, image, or baggage), it moves to the last
position inside the parent folder of the target.

Last updated 3/1/2010

USING ROBOHELP HTML 8 26
Projects

• When you upgrade a project from an older version of RoboHelp, all the topics appear randomly. You can customize
the order of topics later.

• You can right-click a folder or topic in the Project Manager pod and select Explore to open the topic or the folder
in Windows Explorer.

• You can drag folders from the Project Manager pod to the TOC pod. The dragged folders convert to TOC books,
and all the topics change to pages.

• The TOC items don’t change dynamically as you change them in the Project Manager or in a topic.
Drag folders
• Drag a topic or a folder above or below another topic or folder. For linked documents, you can drag only above the
linked documents.

• You cannot drag topics into or out of a linked document.

More Help topics
“Create TOCs” on page 153

Open a project
Open a project and view history
If you open a project created in a previous version of RoboHelp, you are asked whether to convert it before opening it.
Important: Make a copy of your project before converting it into the new format.
Do Not Open Project. I Want To Make A Copy First Closes the Open Project dialog box so that you can copy your

project files. For example, you can use Windows Explorer to copy your project files and store them in the My
Documents folder.
Convert Files As Needed Opens the project and converts files as you work. If you make a global change or a change

that affects more than one file, you are prompted to convert files. An example is a style sheet attached to several topics
in your project. When you try to edit that style sheet, you are prompted to convert all the topics to the new format.
Convert All Files Converts all the files in your project to the new format. Don’t select this option unless you have a

saved copy of the original version.

More Help topics
“Add a RoboHelp project to version control” on page 33

Open a project when starting RoboHelp
❖ From the Starter pod listing recently opened projects, click the project name. If you don’t see the project you want,

click Open.
You can use the following controls to locate the project you want to open:
My Places bar Find documents by using the shortcuts to the left of the Folder and Files list.
Desktop The Desktop folder lists all folders on your desktop.
My Computer The My Computer folder lists the hard drives configured on your computer.
My RoboHelp Projects The My RoboHelp Projects folder is the default working folder where RoboHelp stores all

projects. This folder is placed in the My Documents folder when Adobe RoboHelp is installed. When you start

Last updated 3/1/2010

USING ROBOHELP HTML 8 27
Projects

Adobe RoboHelp, projects stored in the My RoboHelp Projects folder are automatically listed in the Starter pod
under the Recent Projects list. All RoboHelp projects use the .xpj filename extension.
Look in list By default, this list displays the My RoboHelp Projects folder. Alternatively, if you have accessed other
folders, the last folder you accessed, is selected in this list. This list includes the My Computer, My Network Places,
and My Documents folders under the Desktop folder.
Go To Last Folder Visited icon Displays the last folder you accessed. Click the arrowhead to view a list of the most
recent folders you visited. This icon is disabled if you do not access a folder in the dialog box.
Up one level icon Enables you to move to the parent folder of the current folder displayed in the Look in list.
Delete icon Enables you to delete a selected folder or file. The deleted folder or file is sent to the Recycle Bin.
Create New Folder icon Enables you to create a folder under the parent folder selected in the Look in list.
View Menu icon The arrowhead enables you to choose the view in which the folder and file list must be displayed.

You can view the folders and files as thumbnails, tiles, icons, a simple list, or a list with details of the folders or files.
Tools icon Enables you to delete or rename a folder or file, add a folder or file to the My Places bar, or map a hard
drive to a computer or folder on your network. You can also view properties of a folder or file.

File Namebox

Enables you to specify the name of the file to access (to open, to import, and so on.)

Files Of Type menu Enables you to select the type of files to list in the folder and file list.

Open a project after starting RoboHelp
1 Select File > Open. The Open Project dialog box appears.

Note: You can also select the last ten projects opened from the bottom of the File menu.
2 Select RoboHelp HTML Help Project (.xpj) from the Files Of Type menu.
3 Locate the project file, and double-click it.

Pin a project to or remove it from the list of recent projects
Use the Pin feature to mark a project for easy access. Pin a project so that it always appears in the list of recent projects
that appears in the Starter pod and in the File menu.
1 Select Tools > Options.
2 On the General tab, select a project from the Most Recently Used list.
3 Click Pin or Unpin. Click Apply.

View the history of opened files
❖ Select Tools > Options. Click the General tab.

Use this dialog box to configure options for using the program and working with project files.
Save Without Prompt (Automatic Save) Disabled by default. Changes to the current topic are saved when you open

another topic or close the project without saving. You can disable this setting here if necessary. For example, if you
change a topic and want to restore the content, you can temporarily disable the automatic save.
Use Underscores In File Names Saves topic filenames with underscores between words (for example,

My_Help_Topic.htm). For HTML Help projects, topic filenames require underscores rather than spaces. This
convention enables the book or page to synchronize with the topic content displayed at the right side of the viewer.
Check For System HTML Editor You are prompted to determine whether to set RoboHelp HTML as the default editor.

USING ROBOHELP HTML 8 28

Last updated 3/1/2010

Projects

Auto-Compile Outdated Files When you view or publish your project, the program automatically generates your
primary layout when the output files are out of date. If this option is disabled, the program prompts you to generate
the primary layout if the output files are out of date.
Default Language Allows you to change the default language for every project which is created using the RoboHelp

application.
Auto-Show Output View Shows the Output View at the bottom of the program window when a project is generating.
Automatically Check For Updates The program checks for updates when you quit the program. You can also enable

this option by selecting Help > Check For Updates.
Show Alert On Modification Of Auto-Generated Topics from Linked Documents Allows you to enable or disable the

message displayed when you modify a topic generated from the contents of a linked Word or FrameMaker document.
Clear Project Cache (.cpd File) Before Opening Any Project Controls whether the old .cpd file will be

deleted each time while opening a project and a new .cpd will be created from the project files.
Convert RoboHelp Edited Topics To HTML Converts XHTML topics created or edited in RoboHelp into HTML in the

output. Topics created or edited with third-party editors are not converted.
Max Maximum number of recently used files to display. The default is 10.

Viewing projects
Help systems are displayed in a browser or viewer, depending on the output type, the application platform, and the
platforms of your end users. Help systems are displayed in a main window. Users can view topics in the right pane and
navigate with tabs, buttons, and toolbars in the left pane and along the top.
View your project often to test links and make sure that styles appear properly. View each single-source in the viewer
required for the specified output type.

More Help topics
“View output” on page 285

Manage projects
Save projects
Save frequently while you work.

• To save individual files, select File > Save [item].
• To save all files, click the Save All button

Disable auto-save
By default, RoboHelp saves changes when you close the project. If you prefer, you can disable the auto-save feature.
1 From the Tools menu, select Options.
2 Click the General tab.
3 Under Options, deselect Save Without Prompt.

Last updated 3/1/2010

USING ROBOHELP HTML 8 29
Projects

Change project settings
1 Choose File > Project Settings.
2 On the general tab, change settings as needed:
Project Title Enter a project title. This title appears in the window bar of the output.
Primary Output/Layout Select a primary layout.
Language Select the default project language.
Advanced Click to create or edit lists for localization. Set options in each pane.
To Do List Click Manage to manage the To Do list for your project. For more information, see “Using the To Do

list” on page 39.
Index Select an option for saving keywords:

• Index File (HHK) saves new index keywords in the project index file (HHK).
• Topics saves new index keywords in individual topic files (HTM).
• Binary Index uses a binary index in Microsoft HTML Help projects.
Set options on the Stop List pane
Use the Stop List tab to modify words contained in the Stop List file ProjectName.stp. A Stop List contains common
words (for example, “a” or “the”) that the search ignores for an accurate result.
Edit Select a word, click Edit. Type the new name. Press Enter. Right-click the word to display a drop-down box with
the Undo, Cut, Copy, Paste, Delete, and Select All options.
Reset To Default Removes the new entries and restores the default list.
New Adds a word. Click New. Type the word. Press Enter.
Delete Deletes a selected word.

Note: In Microsoft HTML Help projects, the stop list file can’t be larger than 512 K. If the file is larger, words at the end
of the file are not included in the CHM file.
Set options on the Phrases pane
Modify words in the Phrases file ProjectName.phr. This tab contains a phrase list the Smart Index Wizard includes in
keyword searches. For example, make project settings one phrase, not two words. You can add, rename, and delete
words.
Edit Select a word, click Edit. Type the new name. Press Enter. Right-click the word to display a drop-down box with
the Undo, Cut, Copy, Paste, Delete, and Select All options.
Reset To Default Removes the new entries and restores the default list.
New Click New. Type the new word. Press Enter.

Set options on the Always Ignore Words pane
Modify words in the Always Ignore Words file ProjectName.ign. This list contains “noise” words such “as,” “the,” or
“a.” The Smart Index wizard uses the list to keep the noise words out of the index.
Edit Select a word, click Edit. Type the new name. Press Enter. Right-click the word to display a drop-down box with
the Undo, Cut, Copy, Paste, Delete, and Select All options.
Reset To Default Removes the new entries and restores the default list.

Last updated 3/1/2010

USING ROBOHELP HTML 8 30
Projects

New Click New. Type the new word. Press Enter.

Set options on the LNG File pane
Change text elements in the user interface for WebHelp, WebHelp Pro, FlashHelp, FlashHelp Pro, AIR Help, printed
documentation, or HTML Help output.
See the complete list of available changes you can make in the LNG file tab.
When you edit the LNG file, your changes supersede settings made in Project Settings in other locations.
❖ Select an element, and click either of the following:
Edit Modify LNG file text for each user interface element listed. In Edit mode, you can also right-click on the edited
line to undo the edits, cut, copy, paste, delete, or select all.

Note: You can change the string to show expanding or collapsing mini TOCs in settings for master pages. For more
information, see “Master pages” on page 107.
Reset To Default Erases the new entries and restores the default list.

Set options on the Synonyms pane
Define words as synonyms. For example, you can define “find” and “locate” as synonyms for “search.” In the generated
output, when a user searches for “search,” results for “find” and “locate” are also displayed.
Reset To Default Removes the new entries and restores the default list.
Edit Select a word, click Edit. Type the new name. Press Enter. Right-click the word to display a drop-down box with
the Undo, Cut, Copy, Paste, Delete, and Select All options.
New Click to add a new word in the Synonym table and specify a synonym for it.
Delete Click to delete the Word and its synonyms.

More Help topics
“RoboHelp Search” on page 191
“Upgrade localized projects” on page 52

Rename a project
When you rename a project, the main project file (.xpj) and all other project files are renamed.
Note: The TOC, index, and glossary files are not renamed.
When you rename a project, the project closes and reopens. Any changes made since last saving are saved.
Note: You cannot rename projects under version control.
1 Open the project.
2 Select File > Rename Project.
3 In the Project Name box, enter the new project name (do not enter a filename extension).
4 Click OK. To make the changes take effect, the program closes and then reopens the project.

Note: If you are creating Microsoft HTML Help, the name of the compiled HTML Help file (CHM file) is based on the
project filename. If you change the project name, the name of the CHM file changes as well. You can rename the CHM
file to restore the old name.

Last updated 3/1/2010

USING ROBOHELP HTML 8 31
Projects

Version control
Note: Authors must use the "Add to Version Control" command from within the RoboHelp authoring client app itself
when adding a new project to version control. Do not add the folders and files within the RoboSource Control Explorer
interface, as this might cause file corruption.

About version control
RoboHelp works with version control software to check out files automatically (if already not in use) when you begin
editing and tracks their use. You can also view files by opening them from version control without checking them out.
To work with RoboHelp, your version control software must support the Microsoft SCC API. You can use Adobe
RoboSource Control (installed with RoboHelp) or a third-party package. Either way, you perform version control
tasks from within RoboHelp.
When you finish with a file, you can check it into version control, or let the program check in all files when you close
the project. Once your changes are checked in, other authors can access them. You can also set RoboHelp to
automatically check in files when you close the project.
Note: If you cannot check out a file, check if one or more files is checked out by another user. Or, check if the file is not in
version control.
Many topics are linked to other topics, or part of the TOC, index, and browse sequences. When you modify a file or
change the project structure, RoboHelp automatically checks out all affected, dependent files (if available). When you
move a file, the author is prompted to check out the source and destination folders.
To turn off prompts when performing version control tasks manually, deselect the option on the Version Control tab
(Select Tools > Options). Files are then checked out automatically. Files not selected in the list cannot be checked out.
RoboHelp shows which files you must check out and whether they are already checked out.
Note: RoboHelp checks out all the dependent files automatically.
To undo any changes in the checked out copy of a version-controlled file, undo the checkout of the file listed. Then
return to the latest copy from version control. This Undo Check Out command discards changes to the local file copy.
Version control safeguards files as you work, provides revision tracking, makes backups, and can provide file sharing
and organization. All files added to a project under version control are automatically added to version control and
checked out. All files removed from a project are automatically removed from version control, though file history is
retained.
You can perform version control tasks from project panes: Right-click the file, select a command, select the file, and
click a Version Control toolbar button. Or, select the file and then select an option from File > Version Control.

Apply version control
1 Install version control software that supports the Microsoft SCC API.
2 Work with your network administrator to address user access. See your version control software documentation.
3 Add the project to version control.

Access version control options in pods
File status pod Select View > Pods > File Status. Shows the list of files for file status and version control tasks. The
Version Control toolbar provides access to version control tasks.
Topics list pod Select View > Pods > Topics List. Use to open, view, and sort topics.

Last updated 3/1/2010

USING ROBOHELP HTML 8 32
Projects

Project Manager pod Select View > Pods > Project Manager. Displays file icons. A red check mark indicates that a file

is checked out.
Note: The RoboHelp user interface is optimized for RoboSource Control, Microsoft Team Foundation Server 2005, and
Microsoft Visual SourceSafe.

Version control FAQs
How does version control work?
A Help project includes topics, graphics, style sheets, TOC, windows, and other components, each with its own file so
authors can work on components independently.
How can multiple authors use version control?
• Edit project components while authors edit other components.

• View project components even while they are being worked on.
• Get the latest changes (after authors check in files).
• Configure and use version control from RoboHelp. (Using version control on your project outside RoboHelp is not
recommended.)
Can single-user projects use version control?
Yes, to use revision tracking, and to centralize projects onto a network for backup.
Are multiuser checkouts OK?
Multiuser checkouts are not recommended.
Where can I set version control options for RoboHelp?
Click Tools > Options > Version Control.
Will I need my version control program outside RoboHelp?
When removing files or folders from your project, remove them from version control also. Also use your version
control software to create user accounts or set program properties. You can open version control from RoboHelp.
Should I check out the project file (XPJ) to edit the project?
You don’t have to check out the XPJ file when editing. You check out the XPJ file only if you edit project settings.
Are items added to the project also added to version control?
Yes. New topics are added immediately; new folders are added when you save the project. When you rename a file or
folder, it is not renamed in version control. The new item is added, but the original item remains with its old name.
Remove the item by going into version control.
Save your project whenever you add files, but be sure to check files back in to add changes to version control. Changes
saved to your local hard drive aren’t added.
Are items removed from the project removed from version control?
Files are removed from version control as you delete them. Renamed items are added under their new name, but the
old version remains under its old name.

Last updated 3/1/2010

USING ROBOHELP HTML 8 33
Projects

Where are the latest changes made by the team?
You can get the latest file versions (checked in by other users) when you open the project, or manually.
How can I add output files to version control?
If others need access to your output files, add them to version control.

Add a RoboHelp project to version control
When you add a RoboHelp project to version control, create a database connection when you first connect to
RoboSource Control. RoboHelp uses this connection to access the database. See Adobe RoboSource Control Help for
more information.
1 Open the project in RoboHelp HTML.
2 Choose File > Version Control > Add To Version Control.
3 Select RoboSource Control and click OK.
4 If you are connecting to the RoboSource Control database for the first time from your computer, go to step 5 to

create a connection. If you have connected previously, verify that the correct connection is selected in the
Connection list. Then skip to step 9.
5 From the Connection list, select Create.
6 Do one of the following:

• If the RoboSource Control Server software is on your computer, select the database connection from the list on
the left

• If the RoboSource Control Server is on a server, complete the following fields:
Connection Name Enter any name to identify the database from RoboSource Control Client. If you want, you
can use the database name.
Server Enter either the IP address or the unique name of the server on your local network.
Database Enter the name of the database exactly as you entered it in the Create Database dialog box.

7 Click Create And Connect.
8 Connect to RoboSource Control.
9 In the Configure Source Control dialog box, click the Browse button next to the Root Path field.
10 If prompted, enter the same password that you entered to log in.

Note: When the Login dialog box is hidden behind the RoboHelp window, your screen appears to be frozen. Use
Alt+Tab to view the Login dialog box.
11 Click the root node $ to select it, click OK, and then click Yes in the displayed message.

All your RoboHelp project files are now copied to the server-based database, and all the files are flagged as checked out
to you. When you close the project, you are prompted to check the files into the database. If you answer Yes, all the
files are checked in.
Note: An additional File Status pod is displayed in the RoboHelp user interface. This pod lists all the project files that are
under version control and the status of each (checked in or out). Further documentation is installed with RoboSource
Control. This help file is accessed from within the RoboSource Control Explorer application.

File check-in/check-out
When you begin to modify a project file in RoboHelp, the topic file is checked out from version control (if not in use).

Last updated 3/1/2010

USING ROBOHELP HTML 8 34
Projects

Many topics are linked to other topics, or part of the TOC, index, and browse sequences. When you modify a file or
change the project structure, RoboHelp automatically checks out all affected, dependent files (if available).
If a project has dependent files, RoboHelp asks to check them out. If some are already checked out, ask users to check
them in.

Merging Help projects
Using RoboHelp you can create projects in an enterprise or distributed setup where different documentation projects
feed into a common project. After writers create their individual projects, you can merge them to create the common
project. By using skins and templates in the common project, you can achieve a unified appearance in the merged
projects.
The merging takes place at run time, after the projects are generated. Before merging the projects, you simply place
references to other projects inside a master project (the master project does not actually contain the child projects).
You insert each reference in the master project's table of contents, placing it where you want the TOC of the child
project to appear. This step gives you control over where end users access the child project and gives the appearance
of a single, unified Help system. End users see a single online system complete with a table of contents, an index, fulltext search, a glossary (in WebHelp projects), and link controls.
Merging multiple projects involves these steps:

• Merging child projects in the TOC of a master project.
• Publishing merged projects (for WebHelp, FlashHelp, WebHelp Pro, FlashHelp Pro projects, and browser-based
Adobe AIR Help only).

• Automatically merging projects (for WebHelp Pro and FlashHelp Pro projects only).

Merge Help Projects
This information applies to HTML, WebHelp, FlashHelp, and browser-based Adobe AIR projects.
1 Create the master project and the projects that you want to merge.
2 Open the master project.
3 Do one of the following:

• Select the default TOC of the master project from the Project Manager pod.
• Create a TOC for the master project.
4 To insert child projects, place your cursor in the TOC.
5 On the TOC pod, click the New Merged Project icon.
6 Do one of the following:

• For HTML Help projects, click the HTML Help tab in the Merged project dialog box.
• For WebHelp/FlashHelp/Adobe AIR projects, click the WebHelp/FlashHelp/Adobe AIR tab.
7 Do one of the following:

• For HTML Help projects, select a CHM file that is already in the current project folder or browse to the location
of the CHM file.

• For WebHelp/FlashHelp/Adobe AIR projects, enter the name of a WebHelp project (XPJ) or click Open to
browse to the project file.

Last updated 3/1/2010

USING ROBOHELP HTML 8 35
Projects

An icon with the filename is displayed in the TOC pod where you inserted the child projects. The filename is the
format .chm::/.hhc. The HHC file represents the TOC of the merged CHM file. This
icon appears where the TOCs of the child projects occur in the merged project. If needed, you can drag the icon
to another location in the TOC and drop it into place.
In case of WebHelp/FlashHelp/AIRHelp, the placeholder appears as the name of the project.
8 Generate the project.

When a project having merged project references in its TOC is generated, a folder "MergedProjects" appears in the
Project folder. The MergedProjects folder contains a folder for each referenced child project. In the case of
WebHelp/FlashHelp, the corresponding child project has to be generated in its own folder.
9 In the Result dialog, click View to see the results and test the merged project.
10 For WebHelp projects, publish the project on the server.

Notes:
• Before distributing a merged project, make sure to generate the latest child projects.

• Associate at least one index keyword with a topic in the master project. Otherwise, the merged project index has no
entries.

• Merged HTML Help projects use non-binary contents files (HHC). The names of the compiled output file (CHM)
and contents file (HHC) cannot include spaces. (To find out if they have spaces, look at them in your project folder
in Windows Explorer. Do not rename the files in Windows Explorer, however.) If either of the filenames has spaces,
open the project and rename the project file. Then, generate the project and change the name of the output file
(CHM file). The HHC filename is updated automatically when you change the project name.

• Do not assign the Binary TOC feature to your project. If you do, the external TOCs are not displayed in the
Contents tab in the HTML Help viewer.

• The name MergeProjects is reserved. Do not give any folder in the project folder the name MergedProjects.
• You can combine multiple WebHelp projects at run time and store the merged project on a server. You can also
publish the merged project either at an HTTP location or on the intranet.

• If you generate a WebHelp output using a skin, the skin from the master project overrides the skin of the child
project in the merged project. If you access the projects individually outside the merged project, the project-specific
skin is used.

• If you merge WebHelp projects and generate the master project using WebHelp, the child projects are available
only from the TOC (not from the index or full-text search). The child projects appear as individual books in the
TOC. When users click the TOC book of the child project, the child project opens in a new browser window.

Publish merged WebHelp child projects
This information applies to WebHelp projects only.
After you merge WebHelp projects, publish the child projects to place them in the correct location. Publishing the
projects enables you to view them together at run time. You can maintain child projects at different locations and
merge them at a different location. You can publish the merged project to a corporate intranet, an Internet site, a local
hard disk, or a network or FTP server. The output files of the merged project are stored only at the published site and
not at individual child project locations.
Publish child projects
1 Merge WebHelp projects.

Last updated 3/1/2010

USING ROBOHELP HTML 8 36
Projects

2 Open a child project.
3 Generate WebHelp output type.
4 Click Next until the Publish dialog box is displayed.
5 Specify a destination. For example, //servername/Finance project/.
6 Click Finish. The layout is generated.
7 On the Result dialog box, click Publish.

When the process is complete, a dialog box displays statistics about the publishing process and a list of files
published.
8 Click Close.
9 View the master project from its published location to see the merged Help.

View merged Help projects
1 To view the merged Help system from the local copy of the master project (instead of the published location), copy
WebHelp files of child projects to the master project's mergedProject\ folder.
2 Right-click the layout in the Single Source Layouts folder and select View. If you use this method, be sure not to use

the Republish All option in the master project, which could potentially overwrite newer child project files on the
network or server.
Remove merged child projects
1 To remove a merged WebHelp and Microsoft HTML Help project, click Delete in the TOC pod. The child project
icon is removed. Regenerate (and publish if applicable) the master project to remove the child project from the
output. For WebHelp projects, publish the child projects for the change to take effect.
2 Removing a child project from a master project does not remove it from a location in which it was published. Use

another tool to remove the old files or remove them manually.

Customize merged WebHelp/FlashHelp Pro projects
When multiple WebHelp/FlashHelp Pro projects are merged automatically using RoboHelp Server, the projects
appear in the table of contents in alphabetical order. To nest a project TOC within the TOC of another project, you
can rearrange the projects in the table of contents. You can ask your server administrator to change the order of the
projects for you in RoboHelp Server, or you can customize the projects yourself.
Customize merged WebHelp/FlashHelp Pro projects
1 Ask your server administrator to deselect the Automatically Merge All Projects option in RoboHelp Server (Web
Admin interface).
2 Open the master project. Select any project as the master or select a blank project as a master project.
3 In the TOC pod, click the New Merged Project icon. The Merged Project dialog opens.
4 In Project Name, type a WebHelp/FlashHelp Pro project (XPJ) name. Or, click Open to browse to the project file.

A reference to this project is inserted in the TOC of the current project where you clicked.
5 Click OK. An icon with the project name is displayed in the TOC where you inserted the child project. The icon is

a placeholder indicating where the TOC of the child project appears in the merged project. If needed, you can drag
the icon to another location in the TOC and drop it into place.
6 Generate all the projects to update any changes.
7 Publish the master project.

Last updated 3/1/2010

USING ROBOHELP HTML 8 37
Projects

8 View the merged project from the server.

FAQs about merging projects without a server
This information applies to WebHelp and Microsoft HTML Help projects.
Master projects
Which project works best as the master project?
This depends on your projects and requirements, but here are two guidelines:

• The largest project may provide a good foundation because it contains the most information, and thus the most
comprehensive TOC. Adding child projects to the most complete TOC allows you to work in the bigger context of
the Help system and organize the system more logically.

• If you do not have a project that should obviously be the master project, you can create a blank project with no
topics as a container for the child projects. The TOC of the master project can consist of references to child projects
only. (The TOCs of the child projects appear in the output.)
How many child projects can the master project reference?
There is no limit to the number of child projects that you can reference in the master project.
Can a master project be a child project of another master project?
Yes. For example, Project A can be a master project referencing Project B, and it can also be added as a child project
of Project C. Here are examples for each output type:
For WebHelp projects: To use Project A as a child project, publish it to the \mergedProjects\ folder of Project C.
For HTML Help projects: To use Project A as a child project, add the CHM file to Project C and generate the merged
projects.
Where do I place the child project in the TOC?
You can place the child project anywhere in the TOC of the master project (as a subbook or a top-level book). After
inserting the child projects into the TOC, you can drag them to the selected location in the TOC. However, you cannot
separate or divide the child project TOC in the master TOC. The TOC of the child project appears in its entirety where
you place it.
Does generating or publishing the master project update the child projects?
No. To update a child project in the merged Help system, generate the child project. In WebHelp projects, also publish
the child projects to the correct folder.
Features
Do I need to merge the index separately?
No. The updated merging function of RoboHelp merges the index automatically.
What happens if the merged projects have identical index keywords, glossary terms, or link controls?

• Index keywords
Identical index keywords are combined at run time. For example, if project A and project B both have the index
keyword "Installation," this keyword contains all the topics and subkeywords for both projects.

• Glossary terms

Last updated 3/1/2010

USING ROBOHELP HTML 8 38
Projects

In WebHelp projects, if the same term is used in the master project and the child projects, the definitions are
combined at run time (if different, the definitions are placed on separate lines in the "Definition for" pane).
In HTML Help projects, if the same term is used in the master project and the child projects, the definition in
the master project replaces the child project definition.

• See Also keywords
• In WebHelp, identical See Also keywords are not combined at run time. Each project uses its own See Also
keywords. For example, even if Project A and Project B both use the keyword "Setup," topics displayed are
for the individual projects only.

• In HTML Help, identical See Also keywords are combined at run time.
Can you merge browse sequences?
Yes, browse sequences are merged.
How is conditional text handled?
Child projects generated with a conditional build expression are supported in the master project. For example, if a
child project defines a conditional build expression to exclude Tag A, all topics and topic content with Tag A applied
are excluded from the child project and the master project.
For HTML Help projects, are links to external topics retained?
For merged HTML Help projects, index keywords, TOC books and pages, and HTML topics can all link to external
topics in any of the CHM files that are included in the master project. (Remote topics are not supported in WebHelp.)
WebHelp projects
How do I distribute merged WebHelp projects?
Publish merged WebHelp projects to an intranet or a web address, a local or network drive, or an FTP server.
Where do I publish the projects?
Although you publish the master project where you normally would, the child projects are published to a special
location.
What happens to references to child projects that are not published?
If you add a child project to the master project but do not publish it, the child project is not displayed when the master
project is published.
HTML Help projects
What type of index should I use?
The master project must have an index or the merged index is empty. To merge CHM files, your master project needs
to have a binary index when it is generated. With a binary index, all the keywords from the child projects are merged,
alphabetically sorted, and saved in the index file (HHK) of the master project. Binary format is ideal because it is highly
compressed, takes up less space, and is faster to load. Index files in the child projects do not have to be in the binary
format.
Set the Binary index option to the master project before merging the projects.
How do I distribute merged HTML Help projects?

Last updated 3/1/2010

USING ROBOHELP HTML 8 39
Projects

Distribute the CHM files for all the projects, and save them in the same folder as the master project. When you merge
projects, the CHM file of the child project is copied to the folder of the master project. Whenever you update and
generate the child project, copy the updated CHM file to the master project folder.(You can do this using Windows
Explorer.) Distribute the most current versions of all CHM files.

Manage files
List topics by title or filename
1 In the Project Manager pod, open the Project Files folder.
2 Select View > By Topic Title or By File Name.

Using the To Do list
The To Do list helps you track project tasks. You can customize the list by adding, deleting, or modifying the existing
To Do tasks.
Note: To Do settings are retained when you upgrade a project from an older version of RoboHelp to a newer version.
You can generate a report on the customized To Do list.

Edit items on the To Do list
1 Select File > Project Settings.
2 Click the General tab.
3 Click Manage.
4 Do either of the following:

• To add a task to the list, click Add. Type the name of the task item.
• To edit or remove a task, select the task and click Edit or Delete.
Note: From the Project Settings dialog box, you cannot see the Ran Smart Index item in the default To Do list. This
precaution ensures that you do not delete this item by mistake. By default, RoboHelp sets the option Ran Smart Index for
all the topics on which you run the Smart Index wizard.

Update the To Do list for a topic
1 Right-click a topic in the Project Manager pod and select Properties. Click the Status tab.
2 Select or deselect items on the To Do list.

Generate a status report
You can generate a Project Status report to view the number of topics using the To Do list.
❖ Select Tools > Reports > Project Status.

Edit the list of recently used files
Recently used files are listed in the RoboHelp Starter pod.
1 Select Tools > Options.

Last updated 3/1/2010

USING ROBOHELP HTML 8 40
Projects

2 Click the General tab. Set options under Most Recently Used File:

• To change the number of files listed, specify a number in the Max box.
• To remove a file from the list, select it and click Delete.

Add files to the Baggage folder
RoboHelp sometimes doesn’t automatically add references to external elements to the Baggage Files folder. If needed,
add files to the Baggage Files folder so the external elements appear correctly in the output:
1 Select View > Pods > Project Manager.
2 Right-click the Baggage Files folder. Select New > Baggage File.

Note: If the Baggage Files folder isn’t listed, click the Toggle Project Manager View button

3 Double-click the source file for any of the following:

• Bitmaps and icons used with HTML Help controls
• Image files used in style sheets, topic backgrounds, and scripts
• The JavaScript file that supports Dynamic HTML effects, such as pop-ups and drop-down hotspots
4 Click Yes.

Note: You can create a link to a baggage file by pressing the SHFT key while dragging and dropping it into a topic.

Remove files from the Baggage folder
To remove a file from the Baggage folder:
❖ Select the file and click Delete.

Map file types
Map file types to associate them with the applications used for editing them.

Associate a file extension with an application
1 Select Tools > Options.
2 Click the Associations tab.
3 For File Associations, click Add.
4 Enter a filename extension.
5 Select an editor to edit documents with the specified filename extension.

When you select a program, its location appears in the Edit With box. The programs appear alphabetically.
Note: Only those programs appear in the list whose registry entry is set to “NoOpenWith.”
6 Select a program to view the file.

You can also browse to a program not listed in the program list.

Add an HTML editor mapping
1 Select Tools > Options.
2 Click the Associations tab.

Last updated 3/1/2010

USING ROBOHELP HTML 8 41
Projects

3 For HTML editors, click Add.
4 Select from the recommended or other programs registered to edit or view .html or .htm files.

Note: When you select a program, its name and location appear in the Name and Location box. You can also browse
for a program that does not appear in the program list.
5 Click OK. The selected program appears in the list of HTML editors.

Note: To change the HTML editor, browse and select a new program.

Remove topics from projects
Before you remove files, back up all project files and view and print reports if your project is not under version control.
To avoid broken links, don’t remove files in Windows Explorer or version control software.
1 Select one or more files:

• To remove a topic, use the Project Manager pod.
• To remove multiple topics, use the Topic List pod.
2 Press Delete. If prompted, do NOT remove references to removed topics.

Note: You can choose to remove the references, but if you do that, you do not get to review the effect of the removal in
other topics. Electing NOT to remove the references, forces the links to display in Broken Links, from which you can
review each topic to see if any editing is required.

More Help topics
“Broken links report” on page 95
“Unused files report” on page 99

Manage folders
Create folders
The Project Manager contains default folders for project organization. You can create folders and subfolders only in
these folders: HTML Files (Topics), Images, Multimedia, Style Sheets, and Baggage Files.
Note: Do not use Windows Explorer to create subfolders to add, move, or rename files. RoboHelp does not recognize these
changes.
1 Select the Project Files folder in the Project Manager pod.

Note: If the Project Files folder isn’t listed, click the Toggle Project Manager View button
2 Right-click the folder, and select New > Folder.
3 Enter a name for the folder. Avoid special characters and spaces.
4 Press Enter.

Tips:
• Move files and folders in Project Manger by dragging.

• You can drag topics from the Topics List into multiple folders in the Project Manager.

Last updated 3/1/2010

USING ROBOHELP HTML 8 42
Projects

Project Manager folders
In the Project Manager pod, you edit, delete, and create project files. Two views are available in Project Manager. Both
views include a set of commonly used options for authoring. One view displays all the project files gathered together
in a single folder called Project Files; the other view groups the project files into various virtual folders based on file
or
, to change views.
type. Click the Toggle Project Manager View button
The Project Manager view that displays project files in various virtual folders contains the following folders:
HTML Files (Topics) Stores the topics of a project. Files are sorted alpha numerically (A-Z, 0-9). You can add folders

within this folder. You can use the structure to generate a TOC automatically and create browse sequences.
Images Images used in your project are stored in this folder. Image maps and their associated links (hotspots) are also

listed. You can drag an image from this folder into the Design Editor to add images to topics. You can also rename
images in this folder by selecting the image and pressing F2.
Multimedia All sound and video files used in your project are saved in this folder. Adobe Captivate demos (SWF files)

are also stored here. You can drag sound or video files into the Design Editor to add multimedia to topics. You can
also find out where the files are referenced in your project.
Style sheets Style sheets control the formatting of topics. When you change a style sheet, all topics associated with it

are updated. The RoboHelp default style sheets (CSS files) and any others you add to your project are stored in this
folder. Edit a style sheet by double-clicking its icon.
Baggage Files Certain files are automatically added to the Baggage Files folder in the Project Manager to display the

following correctly in the generated project:

• Bitmap and icon files used with HTML Help controls
• Image files used in topic backgrounds and scripts
• The JavaScript file (ehlpdhtm.js) that supports Dynamic HTML effects such as related topics pop-ups, smart popups, and drop-down hotspots.

• The support file for skins and the navigation pane in browser-based outputs (TOC, index, glossary, and full-text
search.
You can drag files from the Baggage Files folder into topics to create links to the files.
Broken Links Stores links to files that are not present in the project. To restore or remove a broken link, double-click it.
URLs Stores links to web addresses, FTP sites, newsgroups, e-mail addresses, and HTML topics in external CHM files.
From this folder, you can add a URL to an index. You can drag a URL into the Design Editor.
Tables Of Contents Stores the default TOC and all other TOCs created in the project.
Index Stores the default index and all other indexes created in the project.
Glossary Stores the default glossary and all other glossaries created in the project.
See Also Double-click the See Also folder to display the See Also pod. You can add the See Also keywords in the See
Also pod.

Rename folders
Use the Project Manager to rename folders.
1 Select the Project Files folder in the Project Manager pod.
2 Right-click the folder. Select Rename.
3 Type the new name. Don’t include special characters, and avoid spaces, especially for WebHelp and FlashHelp.

Last updated 3/1/2010

USING ROBOHELP HTML 8 43
Projects

4 Press Enter.

Move folders
Use the Project Manager pod to move folders.
1 Select Project Files in the Project Manager pod.
2 Drag the subfolder to its new location.

Remove custom folders
Before you remove the folder, move any items in it that you want to keep.
1 Select the custom folder in the Project Manager pod.
2 In the toolbar, click Delete.

File and folder icons
The Project Manager icons indicate the components and files included in your project.
Note: Icons with a red check mark indicate that the file is checked out (applicable only to topics under version control).
Icon

Description
Closed folders. Closed folders that contain files display a plus sign. Click the plus sign to show the folder
contents. Right-click for more options.
Open folders. Open folders display a minus sign with the contents shown below. Click the minus sign to collapse
the folder.

Toggle view. Click to switch between a simplified view with fewer folders or one showing all folders.
Show/hide files. Click to select the files you want to show in the Project Manager.
Empty folders. Empty folders display no signs.
HTML files (Topics). Double-click page icons to open a Design editor. Right-click for more options.
HTML topics with bookmarks. Topics with bookmarks have a plus sign. Click the plus sign to show all bookmarks.
Missing files. A red X indicates files that the program cannot locate. These files are not in the project path. Either
they have been deleted, or they are saved in a different folder of the project.
Bookmarks. Bookmarks appear alphabetically below their respective topics. Double-click to open a topic. Drag
bookmarks into topics in Design Editor to create links.
Framesets. Double-click to open a dialog box for changing frame attributes.
URLs, web addresses, FTP sites, newsgroups, e-mail addresses, or HTML topics in external CHM files. Double-click
to open a dialog box for adding keywords to a link. Drag URLs into topics open in Design Editor to create links.
Images (GIF, JPEG, and JPG formats). Double-click to preview the image, identify topics that use it, and view file
information. Drag images into topics in Design Editor to add them.
Image maps. Images with clickable links or hotspots. Click the plus sign to display links. Double-click to preview
the image, identify topics that use it, and view file information. Drag the image maps into topics in Design editor
to add them.

Last updated 3/1/2010

USING ROBOHELP HTML 8 44
Projects

Icon

Description
Image map links (hotspots). Double-click to identify topics that use image maps.
Sound files (AU, MID, RMI, and WAV formats). Double-click to identify topics that use them and view file
information. Drag sound files into topics in Design Editor to add them.
Video files (AVI and MOV formats). Double-click to identify topics that use them and view file information. Drag
video files into topics in Design Editor to add them.
Adobe Captivate files (SWF files). Double-click to identify topics that use them and view file information. Drag
Adobe Captivate files into topics in Design Editor to add them.
Custom windows. Double-click to modify window properties.
Style sheets (CSS). Double-click to modify styles.
Text-only files For What's This? Help (.TXT format). Double-click to create or modify text-only topics files.
Map Files For Context-Sensitive Help (.HH) Includes imported map files or automatically generated files.
All map IDs. Links map IDs to HTML topics for context-sensitive Help. Double-click to work with map IDs and map
files.
Table of contents folder. Shows the default and other table of contents in the project.
Table of contents folder. Expand to view the table of contents listed.
Table of contents. Double-click to open the selected table of contents pane.
Index folder. Shows the default and other indexes (if any) listed.
Index folder. Expand to view the indexes listed.
Index. Double-click to open the selected index pane.
Glossary folder. Shows the default and other glossaries (if any) listed.
Glossary folder. Expand to view the glossaries listed.
Glossary. Double-click to open the selected glossary pane.
See also. Double-click to open the See Also pane and add to See also keywords.
Baggage files (BMP, ICO, XML, JS, other image files). Files such as bitmaps and icons used with HTML Help
controls, including custom buttons for link controls and startup screens. If your project includes Dynamic HTML,
the file EHLPDHTMJS is included in your Baggage Files folder. Other image files are included as well, such as
topic backgrounds and scripts.

You can map filename extensions to applications. For example, map GIF files to Adobe Photoshop®. When you rightclick a GIF file from the Images folder and select Edit, the file opens in Photoshop.

More Help topics
“Define chapter layout” on page 25

USING ROBOHELP HTML 8 45

Last updated 3/1/2010

Projects

Authoring content in multiple languages
You can change the language of an existing project or a new project. The language affects the window text, as well as
the dictionary for the spell checker and the automatic indexing (Smart Index Wizard) customized settings.
You can also customize the display text, such as the text in browse sequence buttons, previous and next buttons,
show/hide buttons, some messages, and more. The text can be anything you specify. For example, the default text
“Search” on the Search tab can be changed to “Find” in the language of your choice.
When delivering the project to translators, always provide the source files and not the output files.
Note: In HTML Help systems, the end user’s operating system must be in the same language as the one used in your
project. Otherwise, the end user’s operating system overrides the language specified in your project. The dictionary and
index sorting are not affected in the end user’s system.

Support for multiple languages
RoboHelp provides multiple language support at the paragraph, topic, and project level. You can set the language at
the paragraph level and topic level through the RoboHelp user interface. Language defined at the paragraph level takes
precedence over language defined at a topic level. Language set at the topic level takes precedence over language
defined at a project level. Language defined at the project level can never take precedence over language defined at
paragraph level. You can think of the prioritized language as the effective language. Effective language is used in
spelling checks, in a dictionary or a thesaurus, in generating a smart index, and in preparing a full-text search.
The project language is defined at the project level. You can apply different language settings using File > Project
Settings.
You define the topic language using the Topic Properties dialog box.
You define the paragraph language using the Paragraph dialog box. Select any paragraph in the Design view and
choose Paragraph from the context menu.
RoboHelp supports the following languages:
Languages

Spell Check

User Dictionary

Thesaurus

Auto correct

Danish (Denmark)

Yes

German (Germany)

Yes

English (US)

Yes

English (UK)

Yes

Spanish (Spain)

Yes

French (France)

Yes

Italian (Italy)

Yes

Dutch (The Netherlands)

Yes

Norwegian Bokmâl (Norway)

Yes

Norwegian Nynorsk (Norway)

Yes

Portuguese (Brazil)

Yes

Swedish (Sweden)

Yes

Croatian (Croatia)

Yes

USING ROBOHELP HTML 8 46

Last updated 3/1/2010

Projects

Languages

Spell Check

User Dictionary

Thesaurus

Auto correct

Portuguese (Portugal)

Yes

French (Canada)

Yes

Finnish (Finland)

Yes

Catalan (Spain)

Yes

Russian (Russia)

Yes

Bulgarian (Bulgaria)

Yes

Czech (Czech Republic)

Yes

Polish (Poland)

Yes

Romanian (Romania)

Yes

Hungarian (Hungary)

Yes

Greek (Greece)

Yes

Turkish (Turkey)

Yes

Estonian (Estonia)

Yes

Latvian (Latvia)

Yes

Lithuanian (Lithuania)

Yes

Slovenian (Slovenia)

Yes

German (Switzerland)

Yes

Japanese (Japan)

Korean (Korea)

Traditional Chinese (Taiwan)

Simplified Chinese (China)

Thai (Thailand)

Vietnamese (Vietnam)

More Help topics
“Define a language for a paragraph” on page 128
“Create a topic” on page 102

Translation workflows
You can create content for multiple languages in a single RoboHelp HTML project by translating the English content
in the same project. You can then create tables of contents, indexes, glossaries, and conditional build tags in the project
for the desired languages. Finally, you can apply conditional build tags to content authored in the various languages,
and generate conditional output.
Follow the steps in this workflow, which uses translation from English to French and Japanese as an example:
1 Apply French language project settings by selecting French Language.

USING ROBOHELP HTML 8 47

Last updated 3/1/2010

Projects

2 Open an English topic, create a topic for the French language, and translate the content, including the topic title

from English to French. (Do not translate topic filenames.)
3 Create French tables of contents, indexes, and glossaries.
4 Create a conditional build tag, such as FrenchContent.
5 Apply the FrenchContent conditional build tag to French content and topics.
6 Generate output for the French language.
7 Apply Japanese language project settings by selecting the Japanese Language.
8 Open an English topic, create a topic for the Japanese language, and translate the content from English to Japanese.
9 Create Japanese tables of contents, indexes, and glossaries.
10 Create a conditional build tag called JapaneseContent.
11 Apply the JapaneseContent conditional build tag to the Japanese content.
12 Generate output for the Japanese language.

Note: To view the Japanese output, you must change your PC’s language to Japanese.
Note: To translate a webhelp project, first make a copy of the project, open that copy in Robohelp and author in your
desired language.

Compare content in different languages
1 Open topics created in different languages.
2 In Design Editor, position the topics side by side: Drag a topic tab slightly down or to the right, and release the

mouse when the page icon

appears. Choose New Horizontal Tab Group or New Vertical Tab Group.

Select a different language for translating a project file
1 Select File > Project Settings.
2 Select the desired language.
3 Click Advanced, and then use the following tabs:
Stop List Click New to add words that must be ignored during a text search.
Phrases Click New to add a phrase for the Smart Index Wizard to include when searching topic content for

keywords.
LNG File Click Edit to modify the text for each user interface element listed.
"Always Ignore" Words Click New to add a word or phrase that the Smart Index Wizard ignores when generating

the index.
Synonyms Click New to add a synonym for a word. This option enables you to search for words and their

synonyms. The results are always returned for the searched words.

Create a project with a different language
1 Select File > New > Project.
2 In the New tab, double-click Project Type. The New Project Wizard appears.

Note: To create a JavaHelp or Oracle Help project, first create a Microsoft HTML Help project, and then add a new
layout to that project.

Last updated 3/1/2010

USING ROBOHELP HTML 8 48
Projects

3 Enter project information.
4 From the Language menu, select the language. Click Save As Default to keep the language as the default.
5 Click Finish.

The first topic opens in the Design Editor. Generate and view your project to view the results.

More Help topics
“Create and edit single-source layouts” on page 256

Customizing text for localization
You can customize certain text in the user interface for WebHelp, WebHelp Pro, FlashHelp, FlashHelp Pro, and
HTML Help outputs. Here is what you can change for each format:
WebHelp, WebHelp Pro, FlashHelp and FlashHelp Pro
• With a skin Customize text in the Skin Editor. If you do not change the default text (such as “Contents” for the
Contents button), the text is automatically translated using the project language setting.). If you customize text in
a skin, the skin text overrides any customizations you make in the LNG file. For FlashHelp, the Flash developer uses
the Skin Development Kit to customize the text.
WebHelp only
• Without a skin Edit the language file. You can localize browse sequence button text; text on the Glossary tab,
Previous button, and Next button; certain messages; and the Contents, Index, and Search tabs. For example, you
can change the text on the Search tab from “Search” to “Find.”
HTML Help
You can customize browse sequence button text and all text on the Glossary tab. Change window titles in the Windows
Properties dialog box.

Edit the LNG (language) file
1 Create or open a project.
2 Select File > Project Settings.
3 Click the General tab. Click Advanced.
4 Click the LNG File tab.
5 Select the interface text. Click Edit.

Sample LNG file with default English values:

Last updated 3/1/2010

USING ROBOHELP HTML 8 49
Projects

[GlossaryTab]
TabCaption=&Glossary
TermCaption=&Term
DefinitionCaption=&Definition For:
[BrowseSequence]
PreCaption=Previous
PreTooltip=Previous Topic
NextCaption=Next
NextTooltip=Next Topic
BlockTooltip=Select Browse Sequence
[Common]
Contents=Contents
Index=Index
Search=Search
Show=Show
Hide=Hide
SyncToc=SyncToc
Prev=<<
Next=>>
Disabled Prev=<<
Disabled Next=>>
Separate = |
[WebHelp]
Cancel=Cancel
CantOpenURLorFile=Can't open URL or File
CompletingContents=Completing Contents
Display=Display
Done=Done
Find=Find
IndexInputPrompt=Type in a keyword to find:
RelatedTopicListPrompt=Click a topic, then click Display
LoadingContents=Loading Table of Contents
LoadingFTS=Reading Search Data
LoadingIndex=Loading Index
LoadingTOCItem=Loading Table of Contents:
Searching=Searching
FtsInputPrompt=Type in the word(s) to search for:
Topics Found=Topics found
BrowserLimitedMessage=Your browser does not support frames. We recommend that you update
your browser to a version that supports frames.
SuggestViewNoFrameMessage=To view the Help system without frames, click this
SuggestViewNoFrameMsg2=hyperlink."
TopicsNotFound=No Topics Found.
//JavaScript Alerts
JS_alert_appletNotLoad=Unable to load applet. If you are using an old version of Netscape,
edit the prefs.js file.
JS_alert_colorlimitation=WebHelp detected that your display is set to 16 colors. For full
WebHelp support, set your display to use 256 or more colors.
Blank_topic_text=This topic was created by WinHelp Project Conversion Wizard, and is the
destination of a missing topic or broken hyperlink.

6 Type the edits. Press Enter.

Notes:
• If RoboHHRE.LNG is already in your user's Windows folder, it overrides the file in the Baggage Files folder.

Last updated 3/1/2010

USING ROBOHELP HTML 8 50
Projects

• If you do not include the RoboHHRE.LNG file, or omit some values, your project defaults to the English values
shown in the example.

• If you are using a skin, the default text is translated to the default language. If you customized the text in a skin, the
skin text overrides customizations in the LNG file.

Change the default project language
1 Open the project.
2 Select File > Project Settings.
3 Click the General tab and select the language.
4 Click OK.
5 Generate and view your project.

Notes:
• If you use a skin, the default text uses the language setting of the project. Customized skin text overrides text settings
in the LNG file.

• Localize window captions in the Windows Properties dialog (not applicable to WebHelp projects).

Language support for associated dictionaries
If your project contains content authored for multiple languages, define RoboHelp language settings in the project,
topic, and paragraph separately. The effective language is used for dictionary or thesaurus association and for spell
checking. For example, suppose you set the project language to UK English and the paragraph language to French for
several paragraphs. The French spelling checker is activated for French paragraphs while the UK English spelling
checker is used for the rest of the content.
Note: Updated language settings for each language are stored at a common location in the project folder. You can access
the language settings information in the Projects\ !Language! folder.

Index localized text
Use the Smart Index wizard to index your localized project. You can assign keywords for each topic based on the topic
content. The index is generated based on language and search criteria you define in the Smart Index wizard. The Smart
Index Wizard suggests keywords based on topic content.
1 Select a language for a new or existing project.
2 Follow the steps for automatically creating your index.

Universal character sets
RoboHelp enables you to create content in multiple languages. However, authoring content in a multilingual
environment can be challenging when the languages span multiple Microsoft Windows code pages. Support for the
Unicode character encoding standard in RoboHelp overcomes many of these challenges.

Last updated 3/1/2010

USING ROBOHELP HTML 8 51
Projects

Without Unicode, operating systems use a code-page-based environment, in which each language script has its own
table of characters. Content based on the code page of one operating system seldom translates correctly on an
operating system that uses another code page. For example, suppose you are running the English version of the
Microsoft Windows® XP/Vista operating system with the German code page. Then suppose you open a plain text file
created in the Japanese version of Windows XP/Vista. In this case, the code points of the Japanese code page are
mapped to unexpected or nonexistent characters in the Western script. The resulting text is unintelligible.
The universal character set provided by Unicode and supported in RoboHelp overcomes this problem.

Support for Unicode text encoding standards
RoboHelp HTML 8 supports Unicode text encoding. You can create a topic in multiple languages, regardless of the
language used by the operating system running RoboHelp.
You can perform the following tasks related to Unicode:

• Author documents containing multilingual paragraphs and words. For example, you can have a set of Greek
characters followed by Russian characters, and then by French text in the same paragraph.

• Use the relevant language spelling checker to check Unicode content.
• Create, open, or edit Unicode-encoded HTML and text files (UTF-8 and UTF-16 encoded files).
• Enter Unicode characters in input forms and dialog boxes.
• Generate TOC, index, and glossary by using Unicode strings.
• Convert and import text of non-Unicode encoded file types (HTML, XML, MIGF, and so on).
• Publish content to a non-English server by adding multibyte characters in the complete path name.
• Create, open, or edit Unicode-encoded HTM files (UTF-8 and UTF-16 encoded files).
• Provide Unicode-encoded input and view Unicode content in fields, dialog boxes, wizards, and forms.

Set up input languages on Windows
Before you start typing non-English text or Unicode characters in the HTML files, ensure that RoboHelp HTML 8 is
running on a UTF-8 locale. Configure the regional language or locale settings on your computer to add additional
languages for keyboard input, across operating systems.
Use the Windows® XP regional and language settings to add additional languages for keyboard input. These languages
and speech settings appear in the Language bar on the desktop. After you select a language from the bar and a localized
keyboard, you can start typing the required text in the document. Microsoft® defines the keyboard layouts.
1 Open the Control Panel and double-click the Regional And Language Options icon. The Regional And Language

Options dialog box appears.
2 Click the Languages tab.
3 Click the Details button. The Text Services And Input Languages dialog box appears.
4 In the Settings tab, click the Add button.
5 Select a language from the Input Language list.
6 Click OK. The selected language is included in the Installed Services list.
7 Select the desired language in the Default Input Language list.
8 Click Apply and click OK to save the settings and close the Text Services And Input Languages dialog box.
9 Click the Regional Options tab, and choose the language you selected in the Default Input Language list.

USING ROBOHELP HTML 8 52

Last updated 3/1/2010

Projects

10 Click Apply and click OK to save the settings and close the Regional And Language Options dialog box. The

Language bar appears on the desktop of your computer.
11 Open RoboHelp, and type the content. The text appears in the selected language.

You can change the language in the Default Input Language list and the Regional Options tab. The language selected
in the Language bar is updated automatically to reflect your new choice.

Upgrade localized projects
If you customized a phrase, stop list, always-ignore-words list, or an LNG file in RoboHelp 6 or earlier, move the list
to RoboHelp 8 or later, which uses a different file structure and extensions.
Product level customization is moved to [install_folder]\Language in RoboHelp. For example, English is renamed as
en_US and en_UK, and French is renamed as fr_FR.
The project level customization is moved to [project folder]\!Language!\[language folder].
Minor customizations
1 Open Notepad.
2 Open the file to modify. These files reside in C:\Program Files\Adobe\Adobe RoboHelp

[version]\RoboHTML\!Language!\en_US.
3 Open the project. Do the following:

• Edit the LNG file.
• Edit the custom word lists.
Major customizations
1 Open Notepad.
2 Open the old file in C:\Program Files\Adobe\Adobe RoboHelp [version]\RoboHTML\Language.
3 Open the new file in a separate window in Project folder\Language.
4 Copy the customizations from the old file to the new file. See the table for filenames.
File description

Pre-7 filenames

7 Filenames

Phrase list

Phrases.wlf

ProjectName.phr

Always Ignore list

AlwaysIgn.wlf

ProjectName.ign

Stop list

*.stp

ProjectName.stp

Language file

*.lng

ProjectName.lng

Note: The above procedure is NOT the recommended way. The recommended way is described in “Change project
settings” on page 29

Import PDF files
You can convert an Adobe PDF file (version 1.4 or later) into a single topic or multiple topics for a new or existing
project.

• You cannot import encrypted PDF files (files that require a password).

Last updated 3/1/2010

USING ROBOHELP HTML 8 53
Projects

• TOCs or index field codes convert to PDF.
• Adobe Reader® or Adobe Acrobat® is not required to import PDF files.
• Sometimes fonts in PDF files do not convert correctly when imported into HTML.

Create a project by importing a PDF file
Note: You cannot import encrypted PDF files (files that require a password).
1 Select File > New > Project.
2 Click the Import tab. Select PDF Document and click OK.
3 Click the browse button to select one or more PDF files from a single folder. Click Open, and then click Next.
4 Enter the project information. Click Next.
5 Select options in the Conversion Options dialog box.
Topic Select how to split the PDF into topics.
Create New Topic(s) Based On Style(s) Activates the Next button. Click to select styles.
Create A Single Topic Creates one topic from the entire PDF.
Create A Topic For Each PDF Page Choose additional options.
Convert As HTML Creates a topic for each PDF page.
Convert As Image Renders each PDF page as a separate image.
Convert As Absolutely Positioned HTML (Advanced) Creates a topic for each PDF page. Positioning the content can
require advanced HTML and subsequent editing can be difficult. Use this option if the other options don’t produce
the results you want. This option is not recommended for printed documentation.
Image (JPG/GIF/PNG) Select the format for images converted from the PDF. To exclude images, select None.
Page Range By default, all PDF pages are converted. Alternatively, enter the page numbers on which to start and end.

Create new topics based on styles
Styles are converted based on the following:

• The most common style becomes the Normal style, which cannot be used to split topics.
• The remaining styles are ranked from largest point size to smallest. Style ranking also considers boldness (highest
precedence), italics, and normal (lowest precedence).

• Styles are ordered and numbered using “Heading 1” for the dominant heading style and “PdfParaStyle01” through
“PdfParaStyleX” for all other styles. Rename these styles using this dialog.
Create New Topics Based On Lists the styles used in the PDF document.
Description Displays a description of the selected style.
Paragraph Preview Displays a preview of the selected style.
Rename Style Renames the selected style in your project.
Finish Completes the import process.
Back Returns to the Conversion Options dialog box.

Last updated 3/1/2010

USING ROBOHELP HTML 8 54
Projects

Import PDF files into a project
1 In the Project Manager pod, right-click Project Files.
2 Select the file to import into.
3 Select File > Import > PDF Document.
4 Select one or more PDF files. Click Open.
5 Select options in the Conversion Options dialog box.
6 If Create New Topic(s) Based On Style(s) was selected, click Next to select styles.
7 Click Finish.

Importing and linking Word and FrameMaker
documents
You can import Microsoft Word and Adobe FrameMaker documents to your RoboHelp projects. If you are using the
Adobe Technical Communication Suite, you can link FrameMaker documents to your RoboHelp projects.

More Help topics
“Importing and linking Microsoft Word documents” on page 54
“Import FrameMaker documents” on page 68
“Integrating with Adobe Technical Communication Suite” on page 341

Importing and linking Microsoft Word documents
In RoboHelp, you can link and import Microsoft Word documents (files with .docx, .docm, .doc, or .rtf extensions
after the filename). You can create new projects by linking to or importing Word documents. Or, you can use the Word
documents as source files for an existing RoboHelp project. You can use this workflow to integrate content created by
different authors in Word.
The settings for linking to and importing Word documents are applied at the project level. For this reason, you have
consistent settings for all documents that you link to or import into RoboHelp projects. You can also export the
conversion settings that you define and reuse them across multiple projects. Defining a set of standard settings for
conversion ensures consistency across projects. See “Word conversion settings” on page 67.

Linking versus importing Word documents
You have two options for integrating content from Word documents into RoboHelp projects: linking and importing.
The following table lists the differences between the two methods:

USING ROBOHELP HTML 8 55

Last updated 3/1/2010

Projects

Option

Linking

Importing

Remarks

Ability to update generated
topics

Yes. You can update the
generated topics whenever the
source document or your
RoboHelp project settings
change.

No. When you import a Word
document into a RoboHelp
project, RoboHelp copies the
contents of the Word document
into RoboHelp project.
RoboHelp generates topics
based on conversion settings. If
the source document changes,
delete the generated topics and
reimport the Word document.

Use the link option when the
source Word document can
change. Typically, if multiple
projects share the Word
document, you link the Word
document.

No. When you import a Word
document, the generated TOC is
appended and index and
glossary are merged into the
selected TOC, index, and
glossary file.

Use the link option if you want
to automatically update the
TOC, index, and glossary
whenever these components
are updated in the Word
document.

If, however, you are bringing in
content as a one-time activity,
you can use the import option.

Ability to automatically update
TOC, index, and glossary
changes from the source
document

Yes. When you link a document,
separate TOC, index, and
glossary files are created and
associated with the linked Word
document. When the linked
Word document is updated, the
linked TOC, index, and glossary
files are also updated.

Ability to regenerate deleted
topics

Yes. You can delete a topic that No. Import the source
Use the linking option when you
is generated from an imported document again to generate the share the source document
Word document, and then
deleted topic.
across multiple projects.
regenerate the same topic when
you update the Word
document.

Ability to preserve changes in
generated topics

Yes. You can mark topics
generated from a linked Word
document to ensure that the
marked topics are not updated
when the linked document is
updated. In this way, you can
preserve any changes you made
in RoboHelp.

No. When you re-import a Word
document, all topics previously
generated from the imported
document are recreated,
overwriting any changes you
made in RoboHelp.

Use the link option if you need
to retain updates made to both
the linked Word document and
the generated topics.

Ability to change the filenames
and topic titles of generated
files from Project Manager

No. When you link a Word
document, you cannot change
the filenames or topic titles of
generated files from Project
Manager.

Yes. When you import a Word
document, you can change the
filenames or topic titles of
generated files.

Use the import option if you
want to customize the filenames
andtopic titles from Project
Manager.

Optimizing Word documents for online output
If you are importing Word documents that have been published in printed or online format, consider the following
before linking or importing them into RoboHelp projects.
Heading hierarchies Determine the best mapping of Word heading styles to RoboHelp styles so that you can achieve
automatic pagination based on heading styles. If your document does not employ hierarchical heading styles, apply
them before conversion. For example, you can apply Heading 1 style to stand-alone articles in your Word document.
Then map this style to a similar RoboHelp style and define pagination to create an HTML topic for each Heading 1
style. See “Pagination and topic naming in converted Word files” on page 62.
Inline styles and style overrides You can convert inline styles to CSS styles in RoboHelp. However, converting inline

styles to CSS styles can lead to numerous styles that share the same formatting. See “Converting Word styles to
RoboHelp styles” on page 59.
Header and footer information RoboHelp can convert headers and footers. However, to ensure consistency across
your topics, you can define a master page that contains the required header and footer information. By using master

Last updated 3/1/2010

USING ROBOHELP HTML 8 56
Projects

pages, you can also suppress page numbers in headers and footers. “Convert headers and footers in Word documents”
on page 59.
Chapter versus topic In printed documentation, the chapter is the logical and physical unit for grouping content. In

online Help, the organizational unit is the topic, and users see topics one at a time. Although you can group the content
into folders that expand when the user navigates the table of contents, only one topic appears on the screen at a time.
Try to provide comprehensive information without adding redundancy by grouping related topics. See “Pagination
and topic naming in converted Word files” on page 62.
TOCs As you import Word documents, you can also import the Word TOC into the RoboHelp TOC. You can define

the topic hierarchy and represent that hierarchy in the RoboHelp TOC. See “Importing a Word TOC, index, and
glossary” on page 58.
Context sensitivity In online Help formats, you can link specific topics to dialog boxes and other elements that users

encounter in the application workflow. You can assign map IDs to topics in RoboHelp. However, you can also assign
context-sensitive Help markers in Word documents using custom footnote entries. RoboHelp reads these footnote
entries and assigns the map IDs to the generated topics. Ensure that topics in the source Word document are not overly
fragmented. A topic must contain sufficient information to make sense as a stand-alone unit.
For example, if a short task doesn’t make sense without some introductory conceptual information, don’t display that
task as a stand-alone topic. To avoid overly fragmented content, assign context-sensitive Help markers to topics at a
higher level. In this way, the generated Help topic can contain the concept, the task, and any relevant graphics. See
“Convert context-sensitive Help markers in Word to map IDs” on page 63.

Linking options for Word documents
For linking Word documents to a RoboHelp project, you can specify one of the following options in the Import tab of
project settings (File > Project Settings):
Create A Reference You create a reference to an external Word document. In this case, the source Word document is

not copied into the RoboHelp project folder. It remains outside the project. You can edit and update the Word
document independently in Word. Later, in RoboHelp, you can update the topics generated from the linked
document.
Use the linking by reference option to bring in content that is shared across multiple projects. Because only a single
copy of the document exists, any change in the source document is reflected in all projects to which this document is
linked.
Create A Copy And Link You create a copy of the source document and link to the RoboHelp project. In this case, a

copy of the source document is copied into the RoboHelp project and is visible in the Project Manager pod. You can
edit and update the Word copy without affecting the source document. You update the topics generated from the
copied Word document whenever you edit the document.
Use the Create A Copy And Link option to maintain the Word document in RoboHelp, and restrict access to the
source document and allow editing only in the copy available in the RoboHelp project. For example, if you want to
bring in content from a static Word document, link the document by copying it to the RoboHelp project.
Note: This option is available only when you link Word documents. When you import a Word document, RoboHelp does
not keep any link to the source Word document.

Link and import Word documents
• Create a RoboHelp project by linking to or importing a Word document. You can import DOCX, DOC, DOCM,
or RTF files.

Last updated 3/1/2010

USING ROBOHELP HTML 8 57
Projects

• Link or import Word documents into a RoboHelp project.
• (For linked documents) Update the generated topics whenever any of the conversion settings or the source
documents change.
HTML files are not created until you define the conversion settings and generate the Help topics. The source Word
documents are unaffected by linking and subsequent editing. RoboHelp creates a copy of the linked or imported Word
documents before applying the conversion settings.

Create a project by importing a Word document
You can create a RoboHelp project by importing a Word document. To import Word files, you must have Microsoft
Word installed on your computer.
Note: DOCX and DOCM formats are not supported by versions earlier than Microsoft Word 2007. See Microsoft Word
Help for more information.
1 In the Starter pod, click Word Document under Import.
2 Select Word Documents from the Files Of Type pop-up menu, select the Word document, and click Open.
3 Enter relevant details in the New Project wizard and click Finish.

Link a Word document to a RoboHelp project
1 Create a project in RoboHelp.
2 Select File > Link > Word Document.
3 Click Browse to select one or more Word documents and click Open.

Note: To import multiple documents with separate TOCs, select them in the order they should appear in the master TOC.
4 Right-click the linked file in Project Manager, and select Properties.
5 In the Word Document Settings dialog box, do the following:

• To generate a TOC from the source document, select the Convert Table of Contents option, and specify a
filename.

• To generate an index from the source document, select the Convert Index option, and specify a filename.
• To generate a glossary from the source document, select the Convert Glossary option, and specify a filename.
Note: You can define the paragraph styles for a glossary term and definition in the project settings. See “Convert
Word paragraph styles to RoboHelp styles” on page 60.
Note: RoboHelp associates the generated TOC, index, and glossary files with the source Word document. So when the
source document is updated, the TOC, index, and glossary files are also updated.
6 Click OK.

John Daigle provides a step-by-step introduction in Linking to Microsoft Word documents on the Adobe RoboHelp
8 video tutorials page.

Import a Word document into a RoboHelp project
1 Create a project in RoboHelp.
2 Select File > Import > Word Document.
3 Click Browse to select one or more Word documents and click Open.

Note: To import multiple documents with separate TOCs, select them in the order they should appear in the master TOC.

Last updated 3/1/2010

USING ROBOHELP HTML 8 58
Projects

4 In the Content Settings dialog box, set conversion options for the TOC, index, and glossary, and click Next.

For information about various conversion options, see “Importing a Word TOC, index, and glossary” on page 58.
5 (Optional) To edit the conversion settings, click Edit.
6 Modify conversion settings according to your requirements, and click OK.

For information about converting headers and footers, see “Convert headers and footers in Word documents” on
page 59
For information about converting paragraph, character, and other styles, see “Converting Word styles to RoboHelp
styles” on page 59.
7 Click Finish.

Importing a Word TOC, index, and glossary
When you import a Word document into a RoboHelp project, you can also import the table of contents (TOC). Import
the TOC into the RoboHelp project to retain, in Help, the navigation structure you defined in your Word document.
If you import a Word-generated TOC, the first heading becomes a book. Lower-level headings become pages (unless
a book exists at a lower level).
To import multiple documents with separate TOCs, select the Word documents in the Open dialog box in the order
that they should appear in the master TOC. The converted TOC is based on the {TOC} field codes of the Word
document. Ensure that:

• Headings for main books have lower-level headings.
• Headings for sub-books appear under main headings and have lower-level headings.
• Headings for pages do not have lower-level headings.
For example, suppose you import a document with more styles than the TOC contains: The document contains
heading levels 1 through 3, but the TOC contains only heading 1 and 2 entries. To ensure that heading 3 styles appear
in the TOC, either include heading 3 in the Word TOC or auto-create the TOC in RoboHelp.
Import a Word TOC
1 Select File > Import > Word Document.
2 In the Content Settings dialog box, select Convert Table Of Contents.
3 Select one of the following options:
Add To Existing TOC Appends the TOC entries to any existing RoboHelp TOC present in the project. Select an
existing RoboHelp TOC from the list.
Create New Associated TOC Enter a name for a new associated TOC that is added to the RoboHelp project.

Import Word index entries
RoboHelp creates an index based on the index markers in the document you are importing.
1 Select File > Import > Word Document.
2 Select Convert Index in the Content Settings dialog box, and select one of the following options:
Add To Existing Index Add the Word index entries to the existing RoboHelp index of the project.
Create New Associated Index Enter a name for a new associated index that is added to the RoboHelp project.
Add To Topic Add the Word index entries to individual topics in which they appear.

Last updated 3/1/2010

USING ROBOHELP HTML 8 59
Projects

Import Word glossary entries
RoboHelp creates a glossary from the Word document you are importing, based on the paragraph styles defined for
the glossary terms and definitions in project settings.
Note: RoboHelp creates a glossary entry by finding a term and a definition in the specified styles in the Word document.
Consecutive instances of term styles or definition styles are rejected.
1 Select File > Import > Word Document.
2 Select Convert Glossary in the Content Settings dialog box, and select one of the following options:
Add To Existing Glossary Add the Word glossary entries to the existing RoboHelp glossary of the project.
Create New Associated Glossary Enter a name for a new associated glossary that is added to the RoboHelp project.

Convert headers and footers in Word documents
You can convert the header and footer text in your Word documents to headers and footers in the generated HTML
topics.
Note: Don’t use this procedure if your projects have topics natively created in RoboHelp and imported or linked from
other sources as well. Instead, use the master page feature in RoboHelp. Using master pages, you can define consistent
layouts and consistent headers and footers.
1 Select File > Project Settings.
2 In the Import tab of the Project Settings dialog box, click Edit under Word Document.
3 In the Conversion Settings dialog box, select Other Settings and then do the following:

• To convert the header in Word documents, select Convert Header.
• To convert the footer in Word documents, select Convert Footer.

Converting Word styles to RoboHelp styles
You can select the cascading style sheet (CSS) that RoboHelp uses to map Word styles to RoboHelp styles. RoboHelp
saves all the style conversion settings in this CSS file. By default, RoboHelp uses the RHStyleMapping.css file for your
project.
You can also use a custom CSS for your project. You can later edit the styles either in RoboHelp or in an external CSS
editing application, such as Adobe Dreamweaver®. You can define how the Word styles convert to RoboHelp styles at
the project level. All Word style definitions in the Word document appear in the mapping dialog box, irrespective of
whether they are used in the document.

Select CSS for style mapping
1 Do one of the following:

• Select File > Import > Word Document.
• Select File > Link > Word Document.
• Select File > Project Settings.
2 In the Import tab of the Project Settings dialog box, do one of the following:

• Select the CSS file from the CSS For Style Mapping menu. RoboHelp lists CSS files in the root folder of your
project, from which you can select a CSS file.

Last updated 3/1/2010

USING ROBOHELP HTML 8 60
Projects

• Click Add next to the CSS For Style Mapping menu, and select the CSS file that you want to use. Use this option
to specify a custom CSS for your project. When you select this option, RoboHelp copies the selected CSS file into
the root folder of your project, and uses the selected CSS for style mapping.

Convert Word paragraph styles to RoboHelp styles
By default, RoboHelp converts all Word styles to CSS, thus retaining the appearance and behavior of the Word styles
in the RoboHelp project. If you want to ensure consistency of your online Help projects, you can map the Word styles
to RoboHelp styles and edit them.
1 Do one of the following:

• Select File > Import > Word Document.
• Select File > Link > Word Document.
• Select File > Project Settings.
2 In the Import tab of the Project Settings dialog box, click Edit under Word Document.
3 In the Conversion Settings dialog box, select the Word style from the Paragraph group.
4 From the RoboHelp Style pop-up menu, select the RoboHelp style that you want to map to the Word style. To retain

the appearance of Word text in your online Help format, select [Source].
5 Select the properties for the selected Word style. To edit the selected RoboHelp style, click Edit Style.

• Select Glossary Definition Style to mark the style to consider for the glossary definition.
• Select Glossary Term to mark the style to consider for the glossary term.
Note: Follow Glossary Definition Style with Glossary Term Style for a complete a Glossary Term Definition pair.

• Select Pagination to create a Help topic at each occurrence of the selected Word paragraph style.
• Select or enter a user-defined HTML tag for the selected paragraph style.

Convert Word character styles to RoboHelp styles
You can map the Word character formats to character styles in RoboHelp. You can also edit the styles in RoboHelp.
1 Do one of the following:

• Select File > Import > Word Document.
• Select File > Link > Word Document.
• Select File > Project Settings.
2 In the Import tab of the Project Settings dialog box, click Edit under Word Document.
3 In the Conversion Settings dialog box, select the Character group.
4 Select the Word character style from the left pane of the Conversion Settings dialog box.
5 Select the RoboHelp character style from the pop-up menu. Optionally, you can do the following:

• To import the Word character style, select [Source] from the pop-up menu.
• To edit the character style in RoboHelp, click Edit Style.

Last updated 3/1/2010

USING ROBOHELP HTML 8 61
Projects

List mapping
You can map Word lists to RoboHelp lists or HTML lists in RoboHelp. If you have defined lists as paragraph styles in
RoboHelp, you can map these list styles in RoboHelp. If you do not select a style mapping option for a list, it is
converted to text without list properties.
1 Do one of the following:

• Select File > Import > Word Document.
• Select File > Link > Word Document.
• Select File > Project Settings.
2 In the Import tab, click Edit under Word Document.
3 In the Conversion Settings dialog box, select the Other Settings group.
4 Do one of the following:

• To convert the Word list styles to RoboHelp lists, select RoboHelp List from the Convert Word List To pop-up menu.
• To convert the Word list styles to HTML lists, select HTML List from the Convert Word List To pop-up menu.

Create custom HTML tags
You can define or apply a custom HTML tag instead of the standard tag for paragraph styles in the HTML output
for the formats that you import from a Word document. You can define separate HTML tags for each format in the
Word document.
1 Do one of the following:

• Select File > Import > Word Document.
• Select File > Link > Word Document.
• Select File > Project Settings.
2 In the Import tab, click Edit under Word Document.
3 In the Conversion Settings dialog box, select a Word paragraph style, and then select User Defined HTML Tag

option.
4 Type the name of the custom HTML tag or select an existing tag to use instead of the default HTML tag.

Convert Word table styles to RoboHelp table styles
You can map Word table styles to RoboHelp table styles. Alternatively, you can import the table styles as inline
formatting from the Word document. Optionally, you can edit the converted table styles in RoboHelp.
1 Do one of the following:

• Select File > Import > Word Document.
• Select File > Link > Word Document.
• Select File > Project Settings.
2 In the Import tab, click Edit under Word Document.
3 Select the Word table style from the left pane of the Conversion Settings dialog box.
4 Select the RoboHelp table style from the pop-up menu. Optionally, to edit the table style in RoboHelp, click Edit

Style.

Last updated 3/1/2010

USING ROBOHELP HTML 8 62
Projects

Convert Word references to hyperlinks
RoboHelp can convert the references such as foot notes, end notes, captions, bookmarks, and cross-references in the
Word documents. These references appear as hyperlinks in the generated Help topics.
1 Do one of the following:

• Select File > Import > Word Document.
• Select File > Link > Word Document.
• Select File > Project Settings.
2 In the Import tab, click Edit under Word Document.
3 In the Conversion Settings group, select Other Settings, and then select Convert References To Hyperlinks.

Create RoboHelp styles from inline formatting
Even though it’s best to avoid inline formatting in your Word documents, and apply defined paragraph and character
styles, you can link and import Word documents to RoboHelp. You can also create RoboHelp styles from inline
formatting in your Word documents. Such styles are added to the project CSS.
1 Select File > Project Settings.
2 In the Import tab, click Edit under Word Document.
3 In the Conversion Settings dialog box, select Other Settings and then select Auto-Create CSS Styles From Inline

Formatting.

Pagination and topic naming in converted Word files
In addition to defining the pagination and topic naming settings, you can do the following:
Convert header and footer Header and footer text in your word documents is converted and used in the Help topics.

See “Convert headers and footers in Word documents” on page 59.
Convert TOC and index entries TOC and index entries in the Word document are converted in your RoboHelp
project. See “Importing a Word TOC, index, and glossary” on page 58.
Map Word list styles to RoboHelp styles You can convert the list styles in Word to either RoboHelp list styles or
HTML list styles. See “List mapping” on page 61.
Convert references to hyperlinks You can convert the references to hyperlinks in RoboHelp topics. See “Convert

Word references to hyperlinks” on page 62.
Automatically create CSS styles from inline formatting See “Create RoboHelp styles from inline formatting” on

page 62.

Set pagination for online Help topics
When you import a Word document, you define how the contents of the Word file appear as topics in RoboHelp. For
example, suppose your Word file contains ten topics. If each topic contains subtopics, definition lists, tasks, and tables,
you can have each topic appear as a separate HTML file. If each of these topic headings is in Heading 1 style, you can
have each Heading 1 topic created as a separate HTML topic. If, however, you set the pagination at Heading 2, separate
HTML files are created for each Heading 2 topic.
Note: Pagination is based on the Word paragraph styles and not on RoboHelp styles.

Last updated 3/1/2010

USING ROBOHELP HTML 8 63
Projects

Even though you can set pagination for any Word paragraph style, the topic generated must contain relevant, complete
information for the reader. For example, if you set pagination for Heading 3, you run the risk of creating topics with
only task-level instructions. In this case, the required contextual information required to complete the task is isolated
in another Heading 3 level topic. To avoid such disjointed, incomplete topics, set the pagination at a higher level.
1 Do one of the following:

• Select File > Import > Word Document.
• Select File > Link > Word Document.
• Select File > Project Settings.
2 Click Edit under Word Document.
3 In the Conversion Settings dialog box, in the Paragraph group, select the paragraph style on which to base

pagination, and click OK.

Convert context-sensitive Help markers in Word to map IDs
You can convert the context-sensitive Help markers that you insert in your Microsoft Word documents and reuse
them as map IDs. You insert the context-sensitive markers using the Custom Footnote option in Word. You insert
context-sensitive Help markers using the Insert Footnotes And Endnotes dialog box in Word. To insert contextsensitive Help markers, enter a custom string such as TopicAlias and then insert the map ID as the marker text. The
custom string must not contain spaces or any other invalid characters. See Microsoft Word Help for more information
about inserting custom footnote markers.
Sometimes Word documents that you are linking to or importing have context-sensitive Help markers. If so, you can
incorporate them in the map ID header file that you generate. In the project header file, add the map IDs that you
assigned to topics in your Word documents. The context-sensitive marker string is a project-wide parameter. Ensure
that all Word documents that you link to or import contain the same string as the context-sensitive marker text.
1 Do one of the following:

• Select File > Import > Word Document.
• Select File > Link > Word Document.
• Select File > Project Settings.
2 Click Edit under Word Document.
3 In the Conversion Settings dialog box, in the Other Settings group, enter the context-sensitive Help marker string

and click OK.

Define the topic name pattern for generated topics
When you set heading styles for pagination, the heading text is included by default in the filename of the topic file
created in RoboHelp. For example, suppose you define Heading 2 for pagination. If the Word document has two
Heading 2 topics, “Introduction” and “Beyond basics,” the topics are created as files named introduction.htm and
beyond_basics.htm. The result is intuitively named HTML files that indicate the topic title. In addition to this default
scheme, you can define more naming conventions. If, however, the Help system uses sequentially numbered files, such
as helptopic001.html, helptopic002.html, and so on, you can define the pattern to support that convention.
1 Do one of the following:

• Select File > Import > Word Document.
• Select File > Link > Word Document.
• Select File > Project Settings.

USING ROBOHELP HTML 8 64

Last updated 3/1/2010

Projects

2 In the Conversion Settings dialog box, select Other Settings.
3 In the Other Settings tab, set the topic name pattern.

Topics are named according to the selected pattern. You can select one of the following or create a topic name
pattern.
Default

Uses the topic title text as the topic filename.

<$filename_no_ext>-<$paratext>

The name of the converted HTML topic contains the following:

•

The name of the Word source file without its extension

•

Hyphen as the separator

•

Paragraph text used to demarcate HTML topics

For example, a Word file named “Chapter.doc” with “1-Introduction” as paragraph text is
converted to an HTML topic named “Chapter-1-Introduction.”
<$filename_no_ext>-

The name of the converted HTML topic contains the following:

•

The name of the Word source file without its extension

•

Hyphen as the separator

•

A sequential number

For example, “Chapter.doc” is converted to an HTML topic named “Chapter-1.”
<$paratext_no_num>

The name of the converted HTML topic contains the paragraph text used to demarcate the
HTML topic, without numbering. For example, paragraph text “1.Introduction” is converted to
an HTML topic named “Introduction.”.

<$paratext>

The name of the converted HTML topic contains the paragraph text used to demarcate the
HTML topic. For example, paragraph text “Introduction” is converted into an HTML topic named
“Introduction.”

Synchronizing linked Word documents with RoboHelp projects
After you import or link Word documents to your RoboHelp project, you generate Help topics based on the project
settings. When you import a Word document into a RoboHelp project, the topics are generated immediately and
appear in the Project Manager pod. However, when you link a Word document to a RoboHelp project, the topics are
not generated until you explicitly generate them. Because RoboHelp maintains a live link with the linked Word
document, you can update a linked Word document if the source document or conversion settings in the RoboHelp
project change. Icons of the project files in the Project Manager pod indicate whether the documents are in sync with
the RoboHelp topics.
Update the topics generated from linked Word documents in the following scenarios:

• Source Word documents changed after you added or linked them to the RoboHelp project.
• You changed the pagination settings in the RoboHelp project.
• You changed the styles in the RoboHelp project and want to revert them to as in the FrameMaker document.
• You updated the CSS in the RoboHelp project.
If you imported documents into the project, the Project Manager pod does not indicate the synchronization status. If
either the Word documents or the conversion settings change, reimport the Word documents and overwrite the
RoboHelp topics already generated. When you update the documents, RoboHelp updates the converted HTML topics,
TOC, index, and glossary.

Last updated 3/1/2010

USING ROBOHELP HTML 8 65
Projects

Word document synchronization status indicators
The following table shows the different status indicators that appear on the Project Manager pod in RoboHelp for all
linked Word documents.
Icon

Description
Source Word document that was linked by reference missing. The source document that you have linked to the
RoboHelp project is moved to another folder, renamed, or deleted. Locate the source document and link to the new
location.
Source Word document that was linked by copy into the project is missing, renamed, or moved to another folder.
Locate the source document and link to the new location.
Source Word document that was linked by reference is out of sync because of changes in the source document.
Update the document.
Source Word document that was linked by copy into the project is out of sync because of changes in the source
document. Update the document.
Source Word document linked by reference is out of sync because of changes in the RoboHelp conversion settings.
Update the document.
Source Word document linked by copy into the project is out of sync because of changes in the RoboHelp
conversion settings. Update the document.
Source Word document linked by reference and generated topics are in sync.
Source Word document linked by copy into the project and generated topics are in sync.

Generate topics from linked Word documents
Generating Help topics from linked Word documents is a one-time activity. After you generate Help topics, you can
update them whenever the source document or conversion settings change.
❖ Right-click the linked Word document in the Project Manager pod, and select Update > Generate.

Update topics generated from linked Word documents
RoboHelp does not update linked documents automatically when you link Word documents to a RoboHelp project.
You define the conversion settings, including style mapping and pagination, and then generate the topics. Select
options to update a linked document manually.
❖ From the Project Manager pod, right-click a Word document, select Update, and select one of the following:
Generate Generates HTML topics from the linked Word document for the first time. After the topics are

generated, the option changes to Update.
Update Updates topics generated from the selected Word document. Only the topics that have changed are

updated.
Update All Updates all topics generated from all linked documents including all Word and FrameMaker

documents. Because all documents are updated, including those that you edited in RoboHelp, exercise caution
when you use the Update All option.
Force Update Overwrites the current set of topics generated from the selected Word document. Use this option to
force an update of the topics generated from the linked Word document after you edit the source in Microsoft
Word. This option updates all topics including those that haven’t changed.
Force Update All Updates all linked documents, including Word and FrameMaker documents, and overwrites all

generated topics.

Last updated 3/1/2010

USING ROBOHELP HTML 8 66
Projects

Preserve changes to a topic during an update
Normally, when you update a linked document, all topics generated from it are updated, overwriting any other
changes you made in the generated topics. However, you can selectively preserve changes in generated topics and
retain your edits.
1 Right-click the linked document in the Project Manager pod and select Properties.
2 In the Word Document Settings dialog box, select File Update Settings tab.
3 On the left column, select the files in which you want to preserve changes during update and click OK.

Set alert when editing generated topics
You can set RoboHelp to alert you when you make changes to topics generated from linked documents. When you
save the changes to such topics, RoboHelp alerts you that the changes would be lost when the linked documents are
updated.
1 Select Tools > Options.
2 In the General tab, select Show Alert On Modification Of Auto Generated Topics From Linked Documents and

click OK.
Mark topic edits for preservation
If you enabled alerts when saving changes to generated topics, you can mark the topic edits for preservation during an
update. Topics marked for preservation during updates are automatically added to the list of preserved topics in the
File Update Settings dialog box.
1 Edit a generated topic and save the changes.
2 In the alert message that appears, select Preserve Modifications To This File and click OK.

Delete a generated topic
When you delete a generated topic, you have two options. You can regenerate the deleted topic when you update the
linked Word document or completely remove the deleted topic from your project. By default, RoboHelp regenerates
the deleted topic when you update the Word document.
1 In the Project Manager pod, expand the linked Word document to display the topics generated from it.
2 Right-click the topic that you want to delete, and select Delete.
3 Do one of the following:

• Click OK to delete the topic from the project permanently. The deleted topic is not regenerated when you update
the Word document.

• Select Generate This File On Next Update and click OK to delete the topic. When you update the Word
document, the deleted topic is generated again.

Regenerate a deleted topic
If you delete a topic generated from a linked Word document, the topic is removed from the project. However, you
can regenerate topics deleted from a linked document.
1 Right-click the linked Word document in the Project Manager pod and select Properties.
2 In the Word Document Settings dialog box, select File Update Settings tab.
3 On the right column, select the deleted files that you want to retrieve and click OK.
4 Update the Word document.

Last updated 3/1/2010

USING ROBOHELP HTML 8 67
Projects

Edit a linked Word document
You can edit linked Word documents directly in Microsoft Word.
1 Right-click a document and select Edit.
2 Edit the Word document in Microsoft Word.
3 Click Save. The modified Word document now appears in the Project Manager pod with a different icon. This icon

indicates that the source content is now out of sync with the topics generated from the linked Word document.
Note: Force an update of the document after you edit the source in Microsoft Word.

Delete a linked Word document
You can directly delete documents linked by copy from the Project Files folder, and you can delete the references of
the documents linked by reference.
❖ Right-click a document and select Delete.

When you delete a linked file, all its associated documents, such as CSS, images, baggage files, and multimedia files,
are also deleted.
Notes:
• If a referenced file is moved to a different location, its icon changes. You can restore the link to the Word document
by pointing to its new location.

• Do not rename files generated after linking a Word document.
• You cannot drag the generated topics outside the parent Microsoft Word document folder to some other location
in the Project Manager pod.

Restore a link to a missing or renamed Word document
If any of the linked Word documents are moved or renamed, RoboHelp displays a missing link icon for the linked
document in the Project Manager pod. You can restore the link to a moved or renamed file and have all the topics
already generated from the document retained in the project.
1 In the Project Manager pod, right-click the Word document that has the missing link icon.
2 Select Restore Link To Word File, and browse to select the new location of the missing file.

Word conversion settings
You can create a standard set of conversion settings for importing Word content into RoboHelp projects and then use
these settings consistently across multiple projects.
You define these settings once. For subsequent projects, import these settings to the project. In this way, you can
quickly set up the project environment and publish Word content in several online formats.
These settings include:

• Cascading style sheets (CSS) for RoboHelp projects
• Style mapping between Word styles and RoboHelp styles
• Style conversion and other settings

Export conversion settings
1 Select File > Project Settings.

Last updated 3/1/2010

USING ROBOHELP HTML 8 68
Projects

2 On the Import tab of the Project Settings dialog box, click Export.
3 Specify a name for the RoboHelp Import Settings file (ISF) and click Save.

Import conversion settings to a project
1 Select File > Project Settings.
2 On the Import tab of the Project Settings dialog box, click Browse.
3 Select a RoboHelp Import Settings File (ISF). Click Open.

Import FrameMaker documents
FrameMaker and RoboHelp together provide an end-to-end authoring and publishing workflow. This integration lets
you exchange content and publish a variety of output formats such as PDF, online Help, and Help based on Adobe AIR.

Optimizing for online output before conversion
If your authoring process in FrameMaker is optimized for print output, consider the following before linking or
importing FrameMaker documents into RoboHelp projects.
Heading formats Determine the best mapping of FrameMaker heading formats to RoboHelp styles. FrameMaker

documents define various heading formats specifically for print documentation. Among these formats are side heads
and heading styles that start on a new page. These formats don’t apply to online formats. You generally map these
heading styles to a few standard styles in the RoboHelp project.
Page layout settings Often FrameMaker chapter templates specify an even number of pages so that new chapters
begin on a recto (right) page. For online Help, ignore these pagination considerations.
Headers and footers RoboHelp ignores headers and footers during conversion, including legal text such as
“Confidential” and copyright lines. Include such text in the headers and footers in a separate step, after conversion.
Similarly, in RoboHelp, re-create watermark text or images that you used in the printed documentation. Use the
master page feature in RoboHelp to make these changes.
Navigation In print, cross-references specify page numbers which are irrelevant in Help. You can map cross-reference

formats in FrameMaker to a format without the chapter and page number. Converting to online Help removes chapter
and section titles in headers and footers. You can enhance navigability by using breadcrumbs, back and next buttons,
and a defined browse sequence instead.
Redundant content To provide context in different sections of a printed document, writers generally add redundant
information such as brief summaries of concepts covered previously. Because online Help is a random-access,
nonlinear medium, it requires less redundant content. Use cross-references and conditional text options to minimize
redundant content in your outputs.
Chapter versus topic Printed documentation requires you to segregate content into self-contained chapters, which

allow readers to logically and physically separate content. Online Help segregates content at topic level, accessed one
topic at a time. Although you can group the content within chapters into folders that expand when a user navigates the
table of contents, only one topic appears at a time. In this case, try to provide comprehensive information without
adding redundancy by chunking related topics together.
Context sensitivity Online Help formats allow you to link specific topics to related content within the application

Last updated 3/1/2010

USING ROBOHELP HTML 8 69
Projects

For example, a short procedure as a stand-alone topic does not provide the conceptual information for the reader. To
avoid creating topics with incomplete information, assign context-sensitive Help markers to topics at a higher level, so
that the generated Help topic contains the concept, procedure, and any relevant graphics.

Preparing FrameMaker documents for conversion to Help
If the FrameMaker document that you are importing is an unstructured FrameMaker book, you can define a single
FrameMaker template for the conversion. You can then specify this template as the project template that overrides the
formats of individual documents at the RoboHelp project level. You can also reuse the conversion settings across other
projects by exporting the conversion settings.
Carefully examine the FrameMaker templates before importing the documents into RoboHelp, such as when you use
a general-purpose FrameMaker template. If this template contains formats that aren’t used in the book, omit those
formats in the template you use for the conversion.
1 Create a FrameMaker template that contains the formats you need in Help. Alternatively, customize the

FrameMaker template. You don’t have to apply the template manually. You can set RoboHelp to apply a selected
template to FrameMaker files before they are linked or imported to RoboHelp.
In Structured FrameMaker, the element definition document (EDD) or the DTD used in the structured
FrameMaker template automatically controls formatting. Because structured FrameMaker enforces a valid
structure and format, structured documents do not contain format overrides.
2 Apply context-sensitive Help markers to the required topics. See “Convert context-sensitive Help markers from

FrameMaker documents” on page 78.
3 Enclose graphics, callouts, and graphic or text frames you created with FrameMaker graphic tools into anchored

frames. RoboHelp imports only those FrameMaker graphics that are enclosed in anchored frames. By default, when
you import graphics and multimedia files into a FrameMaker document, these are placed in anchored frames. On
the other hand, if your FrameMaker document contains graphics that are placed in graphic frames, you should
place these into anchored frames before linking or importing the FrameMaker files into RoboHelp.
4 To maintain the original quality of images, insert them in FrameMaker documents by Reference. RoboHelp copies

See FrameMaker Help for more information.
6 Set up alternate text or captions for the images and graphics to create accessible online content. See “Create

alternate text for images” on page 84.
7 Apply conditional text settings in FrameMaker documents. See FrameMaker Help.
8 Edit the FrameMaker TOC reference pages to have indented hierarchical headings with different styles. See

“Convert a FrameMaker TOC” on page 72.

Importing FrameMaker documents
The RoboHelp workflow for linking or importing FrameMaker documents allows you to do the following:

• Create a RoboHelp project by importing a FrameMaker book. You can import BOOK or BK files.
• Import FrameMaker documents into a RoboHelp project. You can import FM files, or MIF files that are authored
in FrameMaker. XML files that are part of a FrameMaker book can be imported.
Before you import FrameMaker documents, check them in FrameMaker for errors such as unresolved cross-references
and format overrides. See “Prepare FrameMaker documents for conversion to Help” on page 342.

USING ROBOHELP HTML 8 70

Last updated 3/1/2010

Projects

Create a RoboHelp project by importing FrameMaker books or documents
You can create a RoboHelp project by importing FrameMaker books or documents. Importing these files requires that
FrameMaker 8 or later installed is in your computer.
1 On the RoboHelp Starter page, click More under Import or select File > New > Project.
2 On the Import tab of the New Project dialog box, select FrameMaker Document and click OK.
3 Select the FrameMaker book or document (BOOK, BK, FM, MIF, FRM) from the Files Of Type pop-up menu,

browse to select the FrameMaker book, and click Open.
Note: Use the above procedure to create a new project from scratch and import FrameMaker content in the new project.
However, linking of FrameMaker documents is not allowed in this case.

Import a FrameMaker book into a new RoboHelp project
1 Create a project in RoboHelp.
2 Select File > Import > FrameMaker Document.
3 Select FrameMaker book (BOOK) from the Files Of Type pop-up menu.
4 Browse to select the FrameMaker book file and click Open.

If you are importing a FrameMaker document, you can select the components that you want to import from the
Import Wizard that appears. You can select the TOC, index, and glossary, and specify the conversion settings.
Note: Use the above procedure if you already have a project with some content, and wish to import FrameMaker content.
Linking of FrameMaker document is allowed in this case.

Import FrameMaker documents into an existing RoboHelp project
1 Select File > Import > FrameMaker document.
2 Select the FrameMaker document type that you want to import.
3 Select the documents and click Open.

FrameMaker document components converted to RoboHelp
RoboHelp converts most of the FrameMaker components when you link or import FrameMaker documents. The
following tables list the major FrameMaker document components and show how they are converted in RoboHelp.
FrameMaker files
Book files

Documents contained within the book are converted (FM, XML, MIF, HTM, and HTML files). XHTML files
that are included in the FrameMaker book must be valid XHTML. Validate the XHTML in FrameMaker
itself. All other files in the FrameMaker book are ignored. Child books, folders, and groups in
FrameMaker 9 books are converted and appear as folders in the RoboHelp projects. See “Hierarchical
structure in a FrameMaker 9 book” on page 76.

TOC

Converted, if selected. See “Convert a FrameMaker TOC” on page 72.

Text insets

Text insets in the FrameMaker documents are considered part of the FrameMaker document itself and
are inserted as text in the RoboHelp topic. Once inserted, the content cannot be edited as a text inset in
FrameMaker but can only be edited as text within Robohelp.

Index and glossary

Index and glossary files generated in the FrameMaker book are not converted. Instead, the index
markers and glossary markers in the imported FrameMaker documents are converted if selected. See
“Import FrameMaker index entries” on page 73 and “Import glossary definitions” on page 73.

Last updated 3/1/2010

USING ROBOHELP HTML 8 71
Projects

Variables and conditional
text
Variables

Converted. User-defined variables in FrameMaker are converted as such in RoboHelp and can be
redefined. Apply relevant conditional text tags to suppress variables that shouldn’t appear in online
format. For example, you can suppress the Table Continuation variable in table headers for tables that
break across pages in the FrameMaker documents.

Conditional tags

Converted as RoboHelp conditional build tags. See “Conditional text” on page 206.

Equations

Convert equations to images and insert them in the RoboHelp topics after conversion.

Markers
Cross-references, hypertext,
URLs

Converted to hypertext links. You can map the cross-reference formats in RoboHelp so that you can
remove the volume, chapter, and page references that are not relevant in online format. Unresolved
cross-references and hypertext entries appear as text in online Help. URLs become live hypertext links
in the online Help output. See “Convert FrameMaker cross-reference formats to RoboHelp styles” on
page 76.

Index and glossary markers

Converted to an index and glossary when creating project. See “Import FrameMaker index entries” on
page 73 and “Import glossary definitions” on page 73.

Topic name markers

Converted if you select this option in the project conversion settings. Use topic name markers to create
topic titles and topic filenames from the marker text. See “Pagination for Help” on page 77.

Context-sensitive Help
markers

Converted if you select this option in the project conversion settings. Use Context Sensitive Help Makers
in FrameMaker to specify text in FrameMaker document for generating Context Sensitive Help. See
“Pagination for Help” on page 77.

Custom markers

Converted. You can use these markers for delineating topics from FrameMaker source, or to pass
processing instructions to RoboHelp for images and tables.

Formats
Paragraph formats

Converted. You can map FrameMaker paragraph formats to RoboHelp styles or import the source
formatting. See “Convert FrameMaker paragraph formats to RoboHelp styles” on page 79

Character formats

Converted. You can map FrameMaker character formats to RoboHelp styles or import the source
formatting. See “Convert FrameMaker character formats to RoboHelp styles” on page 79.

Table formats

Converted. You can map FrameMaker table formats to RoboHelp styles or import the source formatting.
See “Convert FrameMaker table formats to RoboHelp table styles” on page 82.

Footnote properties and table Converted. Because table title and table footnotes are paragraph formats in FrameMaker, you specify
footnotes
conversion settings for these paragraph formats separately.
Lists

Converted according to the settings you define. See “List-mapping scenarios” on page 81

Page layouts
Master pages

FrameMaker master pages are ignored. Master pages are used for layout, borders, and page numbers
in FrameMaker, so they are not applicable to online Help. RoboHelp provides master page support for
breadcrumbs, mini-TOCs, and headers and footers that can be selected when you publish a single
source layout.

Reference pages

Ignored. However, you can use the advanced scripting support in RoboHelp to convert images and
graphics placed in the reference pages that are associated with paragraph formats.

Page layout, size, and
pagination

Ignored. These elements are not applicable to online Help. See “Pagination for Help” on page 77.

USING ROBOHELP HTML 8 72

Last updated 3/1/2010

Projects

Headers/footers

Ignored. Headers and footers in FrameMaker usually contain chapter names, chapter numbers, and
page numbers, which are not applicable in online formats. After you generate topics in RoboHelp, you
can create headers and footers in RoboHelp that allow you to place information at the top and bottom
of topics.

Rotated text

Converted to text, such as in table cells. (Rotated text is not supported in HTML).

Images and anchored
frames
Images

Only converted if they are inside anchored frames. If the images are not in anchored frames, reinsert
them after you have imported the FrameMaker files. By default, FrameMaker places the imported and
linked images in anchored frames, so they are converted. However, images placed in graphic frames are
not converted. If images contained in anchored frames are missing, RoboHelp creates blank images
with the filename in a sequential manner. See “Image conversion settings” on page 82.

Drawings

Drawings created within anchored frames are converted to images. You can define the image
conversion settings. See “Image conversion settings” on page 82.

Anchored frames

Converted to images. See “Image conversion settings” on page 82.

ALT text on images and
anchored frames

Converted. If no ALT text is provided in the FrameMaker document for images RoboHelp applies the
filename of the converted images as the ALT text. See “Create alternate text for images” on page 84.

Text frames, graphic frames,
and images inside anchored
frames

Anchored frames and their content convert to images. All content within an anchored frame, including
text frames, multiple images, and callouts convert to a single image. RoboHelp inserts the filename of
the created image as the ALT text if no ALT text is defined for the anchored frame.

Equations

Enclose equations in anchored frames so that they are converted to images when RoboHelp converts
them. See FrameMaker Help.

Structured FrameMaker
components
XML files in book

Converted like FrameMaker documents.

XHTML files in book

Converted like FrameMaker documents.

Content references

Text or files inserted into FrameMaker documents as content references appear as part of the topics
where they appear. They do not appear as references in the online Help outputs. See “Content
reference” on page 76.

Conversion basics
Convert a FrameMaker TOC
When you import a FrameMaker book to a RoboHelp project, you can also import the table of contents (TOC). Import
the TOC into the RoboHelp project to retain the navigation structure you defined in the FrameMaker book.
1 Select File > Import > FrameMaker Document.
2 In the Content Settings dialog box, select Convert FrameMaker Table Of Contents, and browse to select the

FrameMaker TOC file.
3 Select one of the following options:
Add To Existing TOC Appends the TOC entries to any existing RoboHelp TOC in the project. Select an existing
RoboHelp TOC from the list.
Create New Associated TOC Enter a name for a new associated TOC that is added to the RoboHelp project.

Last updated 3/1/2010

USING ROBOHELP HTML 8 73
Projects

Styles in the FrameMaker TOC determine which TOC items become books, sub-books, or pages. The most important
element in determining the level is the leftmost indent, followed by the font size and font weight. TOC entries that have
indented items under them become books in the RoboHelp TOC. If all the TOC entries have the same indention, font
size, and weight, the TOC in RoboHelp appears flat.

• To make a heading a main book, include indented heading levels beneath that heading, or use smaller fonts or no
bold for the subsumed headings.

• To make a heading a sub-book, place the heading under a main heading. Then include indented heading levels
beneath the sub-book heading, or use smaller fonts or no bold for the subsumed headings.

• To make a heading a page, don’t include any heading levels beneath that heading. Indent the page heading, or use
smaller fonts or no bold.
Differences between FrameMaker and RoboHelp TOCs
You can either import the FrameMaker TOC or automatically create a TOC in RoboHelp from generated topics.

• In FrameMaker, the TOC is generated according to the heading styles that you include in the TOC. In RoboHelp,
the TOC is generated according to the topic titles. If you use topic name markers in FrameMaker to name the topics
when you import FrameMaker documents, filenames in RoboHelp differ from the topic titles.

• Autocreating a TOC for a FrameMaker 9 book can create multiple layers of content because of the folder structure
in a FrameMaker 9 book.

• In RoboHelp, you can place a TOC placeholder in another TOC, thus allowing you to create nested TOCs.

More Help topics
“Hierarchical structure in a FrameMaker 9 book” on page 353

Import FrameMaker index entries
RoboHelp creates an index based on the index markers in the document you are importing. However, the index file
generated in the FrameMaker book is not imported into the RoboHelp project.
1 Select File > Import > FrameMaker Document and select the FrameMaker book or document.
2 Select Convert Index in the Content Settings dialog box, and select one of the following options:
Add To Existing Index Add the FrameMaker index entries to the existing RoboHelp index of the project.
Create New Associated Index Enter a name for a new associated index that is added to the RoboHelp project.
Add To Topic Add the FrameMaker index entries to individual topics in which they appear.

Note: RoboHelp does not have any Project Level setting related to Index type. Index entries can be present in a Project
Index or Topic. FrameMaker linking allows you to select the Index type from the various possible options related to
Indexing. When output is generated from RoboHelp, the index entries present in the topic and the index entries present
in the selected (in SSL layout) Index are placed in the output.

Last updated 3/1/2010

USING ROBOHELP HTML 8 74
Projects

2 Select Convert Glossary in the Content Settings dialog box, and select one of the following options:
Add To Existing Glossary Add the FrameMaker glossary to the RoboHelp glossary of the project. You can select the

glossary from the list.
Create New Associated Glossary Enter a name for a new associated glossary in the RoboHelp project.

Converting FrameMaker formats to RoboHelp styles
You can define how the FrameMaker formats are converted to RoboHelp styles on the project level. All FrameMaker
format definitions in the FrameMaker document appear in the Conversion Settings dialog box, even if they aren’t used.
You specify the following:

• FrameMaker template used for conversion. This step is optional.
• RoboHelp style sheet for style mapping.

Select a FrameMaker template for conversion
If the FrameMaker document that you are importing is an unstructured FrameMaker book, you can define a single
FrameMaker template for conversion. For example, suppose the documentation set contains a Getting Started Guide,
Installation Guide, User Guide, and an Administration Guide. These documents can have different page layouts and
formats in print, none of which are relevant for online output. In such cases, you can define one template that contains
format definitions for all documents you want to convert.
You can then specify this template as the project template, which overrides the formats of individual documents at the
RoboHelp project level. You can also reuse the conversion settings across other projects by exporting the conversion
settings.
1 Select File > Project Settings.
2 Click the Import tab of the Project Settings dialog box. Select Apply FrameMaker Template Before Import.
3 Click Browse to select the FrameMaker template you want to use for the project.

Select the CSS for style mapping
You can select the cascading style sheet (CSS) that RoboHelp uses to map the FrameMaker formats to RoboHelp styles.
By default, RoboHelp uses the RHStyleMapping.css file for the project. You can also use a custom CSS. You can later
edit the styles either in RoboHelp or in an external CSS editing application such as Adobe® Dreamweaver®.
1 Select File > Project Settings.
2 Click the Import tab of the Project Settings dialog box. Do one of the following:

• Select the CSS file from the CSS For Style Mapping menu.
• Click Add next to the CSS for Style Mapping pop-up menu, and select a CSS file.
Use this option to specify a custom CSS for the project. When you select this option, RoboHelp copies the
selected CSS file into the root folder of the project, and uses the selected CSS for style mapping.

Last updated 3/1/2010

USING ROBOHELP HTML 8 75
Projects

When you upgrade a RoboHelp 7 project to RoboHelp 8, you can either retain the earlier document-level settings or
convert to the project-level settings supported in RoboHelp 8. After you upgrade your project, you cannot open the
project in RoboHelp 7.
You can add or remove documents to an upgraded project with the document-level conversion settings. You can
define document-level conversion settings for the newly added FrameMaker documents also. This option allows you
to retain the RoboHelp 7 behavior for your upgraded project. However, to take advantage of the enhanced features of
RoboHelp 8 and its integration with FrameMaker, you should upgrade the project completely. For example, RoboHelp
7 provided limited mapping options for autonumbering and list styles. On the other hand, RoboHelp 8 allows you to
map complex autonumber formats and multilevel list styles to RoboHelp styles or HTML lists.
Note: You can discard the document-level settings any time, even if you choose to retain them at the time of upgrading.
However, discarding the document-level settings is irreversible.
Retain or discard RoboHelp 7 settings when upgrading
To retain the document-level settings for converting FrameMaker content into your RoboHelp project, you override
the project-level settings of the converted project with the document-level settings inherited from the RoboHelp 7
project. By default, RoboHelp allows you to retain the document-level settings by overriding the project-level settings.
1 Open the RoboHelp 7 project in RoboHelp 8.
2 Select File > Project Settings.
3 In the Import tab of the Project Settings dialog box, do one of the following:

• To retain the document-level settings in the upgraded project, select the Override Project Settings At Document
Level option. This is the default behavior.

• To discard the document-level settings and use project-level settings, deselect the Override Project Settings At
Document Level option.
Edit document-level conversion settings
If you retain the document-level settings that override the project-level settings for a project converted from an earlier
version of RoboHelp, you can edit these settings.
1 In the Project Manager pod, right-click the added FrameMaker document and select Properties.
2 In the FrameMaker Document Settings dialog box, select the Conversion Settings tab, and set the following.
Apply FrameMaker Conditional Text Build Expression Select to apply conditional text settings before converting

the added FrameMaker document.
Convert AutoNumber To HTML List Select to convert the FrameMaker autonumbering to HTML lists in the

converted HTML topics.
Context-Sensitive Help Marker Specify the context-sensitive Help marker that RoboHelp should use for generating

context-sensitive Help.
User-Defined HTML Tag Select the user-defined HTML tag that you want to use instead of the standard
tags in

the generated topics.
Note: To select FrameMaker formats on which the user-defined tag must be applied, select the FrameMaker formats
from the Project Settings dialog box.
Topic Name Pattern Specify the topic name pattern for topics generated from the added FrameMaker document.
FrameMaker Styles For Pagination Specify the list of FrameMaker paragraph formats on which pagination for

online Help topics should be done. You specify the FrameMaker paragraph formats separated by commas.

Last updated 3/1/2010

USING ROBOHELP HTML 8 76
Projects

Note: Pagination is based on FrameMaker paragraph formats.

Hierarchical structure in a FrameMaker 9 book
With FrameMaker 9, you can enforce a hierarchical structure and grouping within the book. You can also include child
books within a book, and create folders and groups within a book.
When you link or import a FrameMaker 9 book, the Project Manager pod in RoboHelp shows the FrameMaker book’s
hierarchy. When linked or imported into RoboHelp, child books inherit the TOC, index, and glossary from the parent
book. See FrameMaker 9 Help for more information.

Hierarchy of FrameMaker book reflected in the Project Manager pod when you link a FrameMaker book into RoboHelp

Convert FrameMaker cross-reference formats to RoboHelp styles
By default, all cross-reference styles in the source document are used in the generated topics without mapping. Define
the mapping of these formats because FrameMaker documents can contain page and volume references in crossreferences that are not relevant to Help formats.
1 Select File > Project Settings.
2 In the Import tab of the Project Settings dialog box, click Edit under FrameMaker Document.
3 Select a cross-reference format from the Cross Reference group in the Conversion Settings dialog box.
4 Select a RoboHelp style to map to it, or type the RoboHelp style field to redefine the cross-references in the

FrameMaker document.
5 Double-click a building block to append it to the RoboHelp cross-reference definition.

Content reference
Text or files that you have inserted into the FrameMaker documents as content references appear as part of the topics
where they are referenced. They do not appear as references in the online Help outputs. See FrameMaker Help for more
information.

Conversion settings
RoboHelp allows you to define project-wide settings for each source type. For all FrameMaker documents, you define
the conversion settings only once. Similarly, the conversion settings of Microsoft Word documents remain the same
for imported Word documents.

Last updated 3/1/2010

USING ROBOHELP HTML 8 77
Projects

Project-wide conversion settings promote consistency not just in your project but across multiple projects. You can
quickly set up a RoboHelp project without having to define individual conversion settings for paragraphs, tables,
images, and so on.
These settings include:

• Defining a FrameMaker template
• Cascading style sheets (CSS) for RoboHelp projects
• Style mapping between FrameMaker formats and RoboHelp styles
• Format conversion settings, image conversion settings, and other settings
Export conversion settings
1 Select File > Project Settings.
2 On the Import tab, click Export.
3 Specify a name for the RoboHelp Import Settings file (ISF file) and click Save.

Import conversion settings to a project
1 Select File > Project Settings.
2 On the Import tab, click Browse.
3 Select a RoboHelp Import Settings File (ISF file) and click Open.

Pagination for Help
When you link or import a FrameMaker document, you define how the contents of the FrameMaker file are presented
as topics in RoboHelp. For example, if the FrameMaker file contains ten topics, with each topic containing subtopics,
tasks, and tables, you can set each topic to appear as separate HTML files. If each of these topic headings is at Heading
1 format, you can set each Heading 1 topic to be created as a separate HTML topic. On the other hand, if you set the
pagination at Heading 2, separate HTML files are created for each Heading 2 topic.
Even though you can set pagination for any FrameMaker paragraph format, follow these guidelines:
Completeness of content in the topic Ensure that the topic generated contains relevant and complete information for
the reader. For example, if you set pagination for Heading 3 level paragraph, it is possible that the topic contains only
the task information, without the required contextual information that is covered in another Heading 3 level topic. To
avoid such disconnected topics, set the pagination at a higher level so that complete information is available in a single
Help topic.
Drop-down text Ensure that the paragraph format for the drop-down text body is not set for pagination. The

paragraphs applied with this format must accompany the drop-down text caption paragraph format. See “Optimizing
for online output before conversion” on page 68.
Topic name pattern
When you set heading styles for pagination, the heading text becomes the default filename for the topic file created in
RoboHelp. For example, suppose you define Heading 2 for pagination, and the FrameMaker document has two
Heading 2 topics, “Introduction” and “Beyond basics.” In this case, RoboHelp creates the topics introduction.htm and
beyond_basics.htm. Thus, you get intuitively named HTML files that indicate the topic title. In addition to this default
scheme, you can define other naming conventions. If the filenames use sequential numbering, such as
helptopic001.html and helptopic002.html, you can define the pattern for such conventions.
1 Select File > Project Settings.

USING ROBOHELP HTML 8 78

Last updated 3/1/2010

Projects

2 In the Import tab of the Project Settings dialog box, click Edit under FrameMaker document.
3 In the Other Settings tab, select one of the following:
Topic Name Pattern Topics are named according to the selected pattern. You can select one of the following or

create a topic name pattern using the Topic Name Pattern building blocks provided by RoboHelp. In addition, you
can add standard static text, such as “HelpTopic,” followed by sequential number as the topic name pattern.
Building block

Converted topic name pattern

default

HTML topic generated has the filename consisting of the paragraph text.

<$filename_no_ext>-<$paratext>

HTML topic generated has the filename consisting of the filename of the FrameMaker
document without the .fm extension and the topic title, separated by a hyphen. For
example, the FrameMaker document named “Chapter.fm” with "1-Introduction" as
paragraph text is converted to an HTML topic with the filename "Chapter-1Introduction.htm”

<$filename_no_ext>-

HTML topic generated has the filename consisting of the filename of the FrameMaker
document without the .fm extension and the paragraph number separated by a
hyphen. For example, the FrameMaker document "Chapter.fm" is converted to an
HTML topic with the filename "Chapter-1.htm"

<$paratext_no_num>

HTML topic generated has the filename consisting of the paragraph text of the
paragraph format at which pagination is set, without the paragraph number. For
example, a heading 1 paragraph "1. Introduction" is converted to an HTML topic with
the filename "Introduction.htm"

<$paratext>

HTML topic generated has the filename consisting of the paragraph text of the
paragraph format on which pagination is set. For example, a heading 1 paragraph
"Introduction" is converted to an HTML topic with the filename "Introduction.htm"

Topic Name Marker Topics are named after the marker applied in the FrameMaker document. Ideally, you specify
the topic name as the marker text, so that topic names reflect their content. If you select this option, the pagination
settings applied on the Paragraph Styles pane are ignored. Use this option to precisely control the creation of
separate Help topics from the FrameMaker documents.

For example, suppose you define the topic name marker "OnlineHelp" in FrameMaker. You can apply this marker
to all paragraphs that begin a new Help topic. To gain maximum flexibility in defining topic titles and topic file
names, you can enter the file name and the topic title separate by the pipe symbol (|) as the marker text for each
entry in FrameMaker.

Convert context-sensitive Help markers from FrameMaker documents
You can convert the context-sensitive Help markers that you insert in your FrameMaker documents and reuse them
as map IDs. You specify the context-sensitive Help marker in the Project Settings dialog box before linking
FrameMaker documents. You can also specify this setting when you import FrameMaker documents. You can work
with context-sensitive Help markers in FrameMaker documents in two ways:
Automatic conversion of map IDs from FrameMaker documents You apply context-sensitive Help markers in your

FrameMaker documents, and specify the marker type in the conversion settings. RoboHelp imports the markers from
FrameMaker documents and adds the map IDs from the strings contained in the context-sensitive Help markers.
Manually adding a map ID file If you received map IDs from your development team, you use these map IDs as the

context-sensitive Help marker text strings for the marker to be used as context-sensitive Help marker in your
FrameMaker documents. Later, you create a map ID file by associating the map IDs from the development team and
the context-sensitive Help marker text you inserted in the FrameMaker documents. You then add this file to the

Last updated 3/1/2010

USING ROBOHELP HTML 8 79
Projects

project. When you link or import the FrameMaker documents, you specify the context-sensitive Help marker in the
conversion settings.
1 Select File > Project Settings.
2 In the Import tab of the Project Settings dialog box, click Edit under FrameMaker Document.
3 In the Other Settings group of the Conversion Settings dialog box, enter the Context-Sensitive Help Marker.

Apply FrameMaker conditional text build expressions
You can apply the Show/Hide settings of the conditional text build expressions to the content in your FrameMaker
documents imported into RoboHelp projects. RoboHelp imports the content after applying the Show/Hide settings to
the FrameMaker content. Any text that is hidden is not brought into RoboHelp project.
1 Select File > Project Settings.
2 In the Import tab of the Project Settings dialog box, click Edit under FrameMaker Document.
3 In the Other Settings group of the Conversion Settings dialog box, select Apply FrameMaker Conditional Text

Build Expression.

Converting FrameMaker content
Convert FrameMaker paragraph formats to RoboHelp styles
By default, RoboHelp converts all paragraph formats from FrameMaker to RoboHelp CSS styles, thus retaining the
appearance and behavior of the FrameMaker formats in the RoboHelp project. To ensure consistency of the online
Help projects, map the FrameMaker formats to RoboHelp styles and edit them.
1 Select File > Project Settings.
2 In the Import tab of the Project Settings dialog box, click Edit under FrameMaker Document.
3 On the Conversion Settings panel, select the FrameMaker format from the Paragraph group.
4 From the RoboHelp Style menu, select the RoboHelp style that you want to map to the FrameMaker format. To

retain the appearance of FrameMaker text in the online Help format, select [Source].
To edit the selected RoboHelp style, click Edit Style. See “Styles and style sheets” on page 143.
5 Select the properties for the mapped RoboHelp style:
Exclude From Output Select to discard the content in FrameMaker document that is applied with the selected
FrameMaker paragraph format.
Pagination Select to create a Help topic at each occurrence for the selected FrameMaker paragraph format.
User Defined HTML Tag Select or enter a user-defined HTML tag for the selected paragraph format.

If the selected FrameMaker format has auto numbering properties defined, specify how auto numbering is
converted.

More Help topics
“Custom HTML tags” on page 80
“Autonumber style mapping” on page 80

Convert FrameMaker character formats to RoboHelp styles
You can map the FrameMaker character formats to character styles in RoboHelp.

Last updated 3/1/2010

USING ROBOHELP HTML 8 80
Projects

You can also edit the styles in RoboHelp.
1 Select File > Project Settings.
2 In the Import tab of the Project Settings dialog box, click Edit under FrameMaker Document.
3 Select the FrameMaker character format from the left pane of the Conversion Settings dialog box.
4 Select the RoboHelp character style from the pop-up menu. Optionally, you can do the following:

• To import the FrameMaker character format, select [Source] from the pop-up menu.;
• To edit the selected RoboHelp style, click Edit Style.
• To exclude the text in the FrameMaker document applied with the selected character format, select Exclude
From Output.

• To apply a user-defined HTML tag to the imported text in HTML output, select User Defined HTML Tag, and
select the tag from the pop-up menu. You can also enter a new HTML tag. The custom HTML tag for the
character format replaces the tag in the generated HTML file.

Exclude a FrameMaker paragraph format from Help topics
You can exclude the content in FrameMaker documents that has a specified paragraph format from the converted
output. Use this option to remove content such as special notices that are not required in online output.
1 Select File > Project Settings.
2 In the Import tab of the Project Settings dialog box, click Edit under FrameMaker Document.
3 In the project settings, select a FrameMaker paragraph format in the left pane.
4 Click Exclude From Output.

Custom HTML tags
You can define or apply a custom HTML tag instead of the standard
tag for paragraph styles and tag for
character styles in the HTML output for the formats that you import from FrameMaker. You can define separate
HTML tags for each format in the FrameMaker document.
1 Select File > Project Settings.
2 In the Import tab of the Project Settings dialog box, click Edit under FrameMaker Document.
3 In the Conversion Settings dialog box, select the user-defined HTML tag option.
4 Type the name of the custom HTML tag or select an existing tag to use instead of the default HTML tag.

Autonumber style mapping
Choose the conversion setting for converting autonumber formats in the FrameMaker document to the Help format.
If the FrameMaker document contains hierarchical numbered lists, you can choose one of the following:
Ignore Autonumber Choose this option if the autonumber text is relevant only in print format. The converted
paragraph does not contain autonumbering. For example, suppose you ignore autonumbering for the FrameMaker
paragraph format "Section2 Level." In this case, "Section 1.1: System Requirements" in the source appears as "System
Requirements" in the RoboHelp topic generated.
Convert Autonumber To Text Choose this option to retain the appearance of the FrameMaker numbered lists. The
autonumber part loses its sequencing properties and appears as part of the paragraph text in RoboHelp topic.
Convert Autonumber To HTML List Choose this option to convert the autonumber to HTML lists using HTML tags

such as
, , and .

Last updated 3/1/2010

USING ROBOHELP HTML 8 81
Projects

Convert Autonumber To RoboHelp List Choose this option if you want to edit the generated HTML topics in
RoboHelp or use the RoboHelp styles to control the numbering properties.

List-mapping scenarios
RoboHelp allows you to convert list properties of FrameMaker paragraph formats in several ways. Consider the
following scenarios:
FrameMaker numbered list mapped to [Source]
The FrameMaker paragraph format autonumber property converts to a list according the autonumber conversion
settings you define for that FrameMaker paragraph format.
Ignore Autonumber The autonumber part of the FrameMaker paragraph format is ignored. The converted paragraph
style in the RoboHelp topic doesn't contain the list part.
Convert Autonumber To Text The autonumber part of the FrameMaker paragraph converts to text and appears as
paragraph text in the RoboHelp topic.
Convert Autonumber To HTML List Autonumber format converts to list items using HTML tags such as , ,

and .
Converted Autonumber To RoboHelp List Autonumber properties of the paragraph style convert to a RoboHelp list.

Example:

• Create a paragraph style "FM_Para1" in FrameMaker with autonumbering defined as and apply it to
paragraphs. The resulting paragraphs are ordered as "a, b, c, ...."

• Map the FrameMaker paragraph format "FM_Para1" to [Source].
Generated paragraphs in RoboHelp topics have the list style applied to them, where the list has properties similar to
those in the source document.
FrameMaker numbered list mapped to RoboHelp unnumbered style
You can map a FrameMaker paragraph format with autonumbering properties to a RoboHelp paragraph style that is
not linked to any list style. In this case, the autonumber is converted to a list according to the autonumber conversion
settings you define for the paragraph format.
Ignore Autonumber The FrameMaker paragraph autonumber is ignored and doesn't appear in the RoboHelp topic.
However, the paragraph style is mapped.
Convert Autonumber To Text The FrameMaker autonumber part is converted to text and appears as a part of
paragraph text in RoboHelp topic. The paragraph style is mapped.
Convert Autonumber To HTML List The FrameMaker paragraph format is converted to HTML list items using HTML

tags such as , , and .
Convert Autonumber To RoboHelp List The autonumber properties of the FrameMaker paragraph format are

ignored. The paragraph style is mapped.
FrameMaker unnumbered format mapped to RoboHelp numbered style
In this case, the converted paragraph has the RoboHelp paragraph style and inherits the RoboHelp list style. The
Autonumber conversion options do not affect the paragraph behavior in the RoboHelp topic.
For example:

• In the FrameMaker document, create a paragraph format "FM_Para 1" without autonumber properties.

Last updated 3/1/2010

USING ROBOHELP HTML 8 82
Projects

• Define a RoboHelp list style "RH_List1" in the RH style mapping CSS.
• Create a paragraph style "RH_Para1" and link the first level of list style "RH_List1" to the paragraph style
"RH_Para1".

• Map the FrameMaker paragraph style "FM_Para1" to RoboHelp paragraph style "RH_Para1".
The generated paragraph in the RoboHelp topic inherits the properties of the list style "RH_List1".
FrameMaker numbered list mapped to RoboHelp numbered list
The converted paragraph style has the RoboHelp paragraph style and inherits the RoboHelp list style. The
Autonumber conversion options do not affect the paragraph behavior in the RoboHelp topic.
For example:

• In FrameMaker, create a paragraph format "FM_Para1" with autonumbering defined as and apply it to a
paragraph so that the paragraph has an ordered list such as "a, b, c, …."

• Define a numeric list style "RH_List1" in the RoboHelp style mapping CSS with the first level definition as .
• In RoboHelp, define a paragraph style "RH_Para1" and link the first level of list style "RH_List1" to the paragraph
style "RH_Para1".

• Map the FrameMaker paragraph format "FM_Para1" to the RoboHelp paragraph style "RH_Para1".
The generated paragraph in the RoboHelp topic inherits the properties of list style "RH_List1" and displays a list of
type "1, 2, 3, ...."

Convert FrameMaker table formats to RoboHelp table styles
You can map FrameMaker table formats to RoboHelp table styles. Alternatively, you can import the table formats from
the FrameMaker document. You can also edit the table formats in RoboHelp. Cells in the FrameMaker document that
are merged (straddled) cannot be unmerged (unstraddled); however, the straddled cells appear merged in the
RoboHelp topic.
If the FrameMaker table formats contained table titles and table footnotes, convert these paragraph formats in
FrameMaker to RoboHelp paragraph styles separately. Decide whether you want to retain automatic numbering in the
table title styles and specify the autonumbering properties for the mapped RoboHelp paragraph style. For example, if
the table title formats in the FrameMaker documents included the chapter number, such as “Table 2-3: Quarterly
Results”, you can choose to ignore the autonumbering part and have only “Quarterly Results” appear as the table title.
See “List-mapping scenarios” on page 81.
1 Select File > Project Settings.
2 In the Import tab of the Project Settings dialog box, click Edit under FrameMaker Document.
3 Select the FrameMaker table format from the left pane of the Conversion Settings dialog box.
4 Select the RoboHelp table style from the pop-up menu and click OK. Optionally, to edit the table style in RoboHelp,

click Edit Style.

Image conversion settings
Some FrameMaker documents, especially those optimized for high-quality printing through PDF, contain images in
EPS format. Convert EPS images to web-supported image formats such as JPEG, GIF, or PNG for online Help.
You specify the following image conversion settings in the Conversion Settings dialog box:
Preferred Dimensions Specify the dimensions for the images. Select one of the following:

• Scale Scale images as a percentage of the existing size. The aspect ratio of the images is maintained.

Last updated 3/1/2010

USING ROBOHELP HTML 8 83
Projects

• Width and Height Specify the absolute image size as Height and Width, in points. Select Maintain Aspect Ratio to
ensure that the images are not skewed.
Note: To convert the images in FrameMaker documents to the actual dimensions of the images, specify the height and
width as 0pt. The tag for such images in the generated HTML does not have the height and width values. This
conversion is irrespective of the dimensions of the anchored frames that contained the images.

• Maximum Dimensions Set the maximum dimensions for images in online format. Images that exceed the
maximum dimensions you specify are automatically scaled down to fit the maximum size you specify. If you scale the
images and specify an aspect ratio, RoboHelp scales the images within the maximum dimensions specified and
maintains the aspect ratio.
Use this option to avoid large images causing the browser window to scroll horizontally or vertically. For example, if
you specify the window size to be 800 x 600 pixels, you can specify the maximum dimensions to be 640 x 480, so that
the images do not exceed the window size.
Margins Set the margins for the images:

• Set equal margins on all sides by setting the margin in All Sides.
• To set margins on individual sides, set the margins on each side.
Borders Set a border for the images:

• To set a uniform border on all sides, select All from the Border pop-up menu. Alternatively, you can specify the side
on which you want the border to appear from the pop-up menu.

• To set the border style, select the style from the Style pop-up menu.
• To set the border color, select the color from the Color pop-up menu.
• To set the border width, select it in, in points, from the Width menu.
Format Define the image format, color depth, and quality settings for the web-supported images that are converted
from the images in the FrameMaker document:

• As Is Select this option for retaining the images in the current web-supported format.
• JPG Select this option for multicolor images such as screenshots or photographs. JPG format with a high color
depth provides the best online quality, but increases the file size. Select this option for photographs.
• GIF Select this option if the FrameMaker document contains only line art, such as schematic diagrams.
• BMP Select this option for screenshots and other images. BMP files provide good quality at an increased file size.
• PNG Select this option for screenshots.
JPEG Quality Set the quality percentage for JPG images.
Color Bit Depth Set the color bit depth for bitmap images. JPG and PNG formats can have either 8- or 24-bit color

depth, while BMP images can be have color bit depths of 1, 4, 8, 16, 24, or 32. GIF images can have only 8-bit color
depth.
Grayscale Select this option if you want monochrome images.

More Help topics
“Preserve converted images” on page 362

Last updated 3/1/2010

USING ROBOHELP HTML 8 84
Projects

Preserve converted images
RoboHelp converts the images and anchored frames in the FrameMaker documents each time the topics are updated
or generated. You can skip updating the images if the corresponding images or SWF files from the corresponding
anchored frames are already present in the RoboHelp project. Use this option in the following cases:

• You want to avoid regenerating the images each time the FrameMaker document is updated
• You have edited the images in the RoboHelp project using another image-editing tool, and want to prevent
overwriting of the edited images

• You want to preserve the earlier generated image in the RoboHelp project even though the image in the
FrameMaker document has changed
If the order in which the images appear in the document or the image name has changed, you should clear this option
and allow RoboHelp to update the images.
❖ In the Image tab of the Conversion Settings dialog box, select Do Not Re-Generate Images.

Create alternate text for images
To create accessible content, create alternate text (ALT text) for images so that visually impaired users can access the
content through screen readers. If you link or import completed FrameMaker books into RoboHelp for publication,
add alternate text to graphics used in the FrameMaker documents. These entries are not visible in PDF files, but they
appear in online content when the mouse hovers over the images. See FrameMaker Help to learn about setting
alternate text for graphics and images.

Import a DITA map file
You can import DITA map files or topics in RoboHelp to generate XHTML output. The DITA Open Toolkit processes
the information in the DITA map file and provides the XHTML output. RoboHelp reads the XHTML output to
generate the XHTML topics, TOC, and index. RoboHelp shows processing information of the DITA Open Toolkit in
the Output View pod.
Note: RoboHelp depends on the DITA Open Toolkit to process the DITA map content. RoboHelp does not correct any
errors generated by the DITA Open Toolkit. For example, if the DITA Open Toolkit does not generate XHTML 1.0
transitional compliant files, RoboHelp does not generate errors. Therefore, the XHTML topics generated from the import
of DITA map file do not contain the meta tag

Note: The XHTML file must have well-formed XML.
1 Do one of the following:

• Select File > Import > DITA Map.
• Right-click the Project Files folder in the Project Manager pod. Select Import, and then select DITA Map as the
file type.
2 Select a DITA map file. Click Open.
3 In the DITA Open Tool Kit Processing Options dialog box, specify the following options:
Replace Default XSLT File For Conversion Select an XSL file to use for transforming the DITA files to XHTML
instead of the default XSL file used by the DITA Open Toolkit. The equivalent parameter for the Ant processing of
the DITA Open Toolkit file is args.xsl.

Last updated 3/1/2010

USING ROBOHELP HTML 8 85
Projects

Use DITA Val For Conditional Processing Specify a DITA Val file to use for conditional processing of the DITA files.

The XHTML is generated based on the Val file. A DITA Val file contains filter, flagging, and revision information.
The equivalent parameter for the Ant processing of the DITA Open Toolkit file is args.filter.
Show Index Entries In The Topics Select to show index entries (marked by in DITA topics) in

RoboHelp topics. The equivalent parameter for the Ant processing of the DITA Open Toolkit file is
args.indexshow.
Show Image Filename In Annotation Select to add annotations to images showing the filename of the image or the

full path to include in the topics. The equivalent parameter for the Ant processing of the DITA Open Toolkit file is
args.artlbl.
Include Draft And Cleanup Content Select to include draft and required cleanup content (items identified as left to
do before publishing). The equivalent parameter for the Ant processing of the DITA Open Toolkit file is args.draft.
Select XHTML File To Be Placed In The Header Area (hdf) Select the location of the file containing XHTML to place
in the header area of the output file. The equivalent parameter for the Ant processing of DITA Open Toolkit file is
args.hdf.
Select XHTML File To Be Placed In The Body Running-header Area (hdr) Select the location of the file containing the

XHTML to place in the body running-header area of the output file. The equivalent parameter for the Ant
processing of the DITA Open Toolkit file is args.hdr.
Select XHTML File To Be Placed In The Body Running-footer Area (ftr) Select the location of the file containing

XHTML to place in the body running-footer area of the output file. The equivalent parameter for the Ant
processing of the DITA Open Toolkit file is args.ftr.
DITA Open Tool Kit Home Directory Select the absolute location of the home folder of the DITA Open Toolkit.
Specify the valid DITA Open Toolkit home folder. You specify this location only once. It is stored in the registry.
You can change the location.

4 Click Finish.

Note: RoboHelp verifies the location of the selected files but does not validate the files as the DITA Open Toolkit processes
all the information.

Import XML files
When you import an XML file into an existing project, RoboHelp creates a topic for the XML file.
1 In the Project Manager pod, select the file to import into.
2 Select File > Import > XML File.
3 Select one or more XML files. Click Open.
4 Select options in the Select XML Import Handler dialog box.
5 (Optional) To set advanced options, select Import XML (CSS/XSL).
6 Click Advanced.
7 Select an option:
Treat As Text Flow Import the XML file as HTML text without formatting.
Treat As XML Tree View Import the XML file in HTML tree view. HTML imports as code.
Use Customized CSS/XSL File Select a file from the pop-up menu.

Last updated 3/1/2010

USING ROBOHELP HTML 8 86
Projects

8 Click OK.

Note: If multiple imported topics have the same topic name, this error is due to the XSL file used during the import
process. The XSL file used to transform the XML to HTML contains the specified field. Edit the XSL file and
reimport the XML file.
Select XML Import Handler
Handler Name The following are predefined handlers:

• Import DocBook As Topics A DocBook file is imported as an HTML topic.
• Import XML (CSS/XSL) If the XML file has an associated style sheet (CSS or XSL file), the file is imported as an
HTML topic. Otherwise, the file is imported as an HTML file without any display control.
Advanced Active if you select Import XML (CSS/XSL). Click for more import options.
Automatically Replace Topic(s) Imported From Previous Session Overwrites old data.
Validate XML Before Import RoboHelp validates the XML file before importing it.

Advanced XML Import Options dialog box
These options are available for importing XML with this handler only if no associated XML style sheet exists.
Treat As Text Flow Imports the XML file as HTML text without formatting.
Treat As XML Tree View Imports the XML file in HTML tree view. HTML imports as code.
Use Customized CSS/XSL File Select the customized file.

Note: You can create and edit customized handler files using the XML Handler Manager and the Handler Description
File (HDF) Editor.
About the XML Handler Manager
Handlers determine how XML is imported. Select one of the predefined handlers or create a custom handler to meet
your requirements. You can select a handler when you import an XML file into a project or when you generate XML
output.
The XML Handler Manager lists all Handler Description files (HDF files) that have been exported from the HDF
Editor.
Handler Description files (HDF files) Contain individual handlers and the files necessary to perform the XML
transformation. The predefined HDF files are organized by type (XHMTL, for example) and contain all related
handlers:
DocBook This handler type includes: Import DocBook As Topics, Export Project To DocBook, Export Topics To

DocBook.
XHTML This handler type includes: Import XHMTL (XML), Import XHTML (XHTML), Export Topics To XHTML,

Export Project To XHMTL.
XML/CSS This handler type includes: Import XML (CSS/XSL).

To open an HDF file and view the handlers in it, click the plus box to the left of an HDF file.
Edit After selecting an HDF file (XHTML, for example) or a specific handler, click to open the HDF Editor and edit a
handler.
Delete After selecting an HDF file (XHTML, for example), click to delete all handlers in it.

Last updated 3/1/2010

USING ROBOHELP HTML 8 87
Projects

Import Import an existing handler.

Note: Initially a handler is an HDF file with a subfolder of support files. To bring a handler file from the HDF Editor into
this program, export the HDF file as a ZDF file. Use the HDF Editor for this task.

Import Microsoft HTML Help projects
When you import an HHP file, a new RoboHelp project file (XPJ) is created.
1 Select File > Open.
2 Select HTML Help Project (*HHP) from the Files Of Type menu.
3 Navigate to the HHP file and open it.

You can also import FrameMaker (.fm, .book, and .mif) files, Word files (.doc, .docx), PDF files, and XML files.
Note: If you use an HTML editor other than Design Editor to author your content, you can still use RoboHelp for the
project.

More Help topics
“Create a project” on page 23
“Third-party HTML editors” on page 123

Import WinHelp projects
You can import compiled WinHelp 4.0 (HLP) or the WinHelp project file (HPJ) into a project.
The HPJ file is the main organizational file, containing all the source files. When generating WinHelp, RoboHelp
creates an HLP file and a CNT file. The HLP file doesn’t contain topics excluded by a conditional build expression, so
the new project might not mirror the original.
You can import HLP files to HTML-based projects, but the process is easier if you have the HPJ file.
You can’t output a WinHelp file from RoboHelp HTML.

Import WinHelp Project settings
Pop-ups
Smart Popups Create links that display pop-ups that resize to accommodate content. All HTML formatting is

supported.
Regular Hyperlinks Create links that open in the window in which the link appears.

What’s This Help
Text-Only Topic Files Create and save topics in text-only format (TXT). Use this option for What's This? Help topics.
Individual HTML Files Create and save topics as regular HTML topics for window-level context-sensitive Help.

Last updated 3/1/2010

USING ROBOHELP HTML 8 88
Projects

External topics
Links To External HTML Help Topic Convert external WinHelp topic links to HTML topic links in external CHM files.
Retain Keep External WinHelp Topic Links HTML topics include WinHelp Topic controls. Use this option when

linking HTML topics to WinHelp topics.
Images
Converts BMP images into GIFs or JPEGs.
Bullets/Numbering
HHTML Bullets And Numbering (Recommended setting) Convert numbered lists and bulleted lists into their HTML
equivalents using Pure HTML tags (<ol>, <ul>, <li>). These lists are auto-numbered or bulleted. Special paragraph
formatting used in RTF files is not carried over.
Formatted Text Retain indents, line spacing, and other paragraph formats from RTF files. Convert numbered lists into
hard-coded numbered lists. Convert bulleted-list items into hard-coded symbol characters.

Tips:
• Remove hard-coded numbers and bullets and replace with auto-numbered lists and bulleted lists in the Design
Editor.

• Create special bulleted and numbered list styles and apply them to paragraphs after they are converted.

WinHelp folder import options
Folder for HTML files
Do Not Create Subfolder Save all HTML topics at the root of the project folder.
Create Subfolder Save all HTML topics in a subfolder.
Create Folders Based On Source Document Names Create and save HTML topics in subfolders based on the DOC

files.
Create Subfolders Based On TOC Structure Create and save HTML topics in subfolders, based on the WinHelp table
of contents. Books within books are created as subfolders within folders. All topics not used in the WinHelp table of
contents are saved at the root of the project folder.

Folders for images
Do Not Create Subfolder Save all image files at the root of the project folder
Create Subfolder Save all image files in a subfolder

File options
HTML File Extension Save all HTML topics using the extension selected.
Always Use Lowercase Save filename extensions in lowercase letters. Select this option for UNIX® servers.

Last updated 3/1/2010

USING ROBOHELP HTML 8 89
Projects

WinHelp formatting import options
Work with or without style sheets. Without style sheets, topics format using inline styles. For external style sheets,
create new style sheets based on the formatting in WinHelp documents or select a style sheet already in use.
Inline Styles (No External Style Sheets) Convert all formatting into HTML inline styles. This option does not create or

apply styles or style sheets to the topics. Formatting is handled on a paragraph-by-paragraph and character-bycharacter basis. Apply styles after importing the project. Manually apply character and paragraph attributes to new
topics.
External Style Sheets (One For Each Source Document) Create one style sheet for each DOC file imported.
External Style Sheet Based On One Source Document Create a single external style sheet based on one DOC file. The
style sheet uses the same names and formatting as the styles in the WinHelp documents. The HTML topic text is
formatted using these styles.
External Style Sheet Based On Existing Style Sheet Link an existing style sheet to all topics. Styles in the DOC files
must have a one-to-one relationship to styles in the style sheet, including style names. Apply styles to the paragraphs
and characters that use them. With a one-to-one style relationship, styles in HTML topics use the same names and
formatting as the styles in WinHelp documents.

WinHelp general import options
Navigation pane
TOC Contents displays books and pages in the table of contents. The index displays keywords.
Glossary Provide definitions for the Help system.
Favorites Create a personalized list of favorite topics.
History See topics viewed previously. Sets options for the navigation pane.

Search:
No Search Select this feature to disable full-text searching.
Regular View a list of topics by title.
Advanced Provide advanced full-text search capabilities including Boolean, wildcard, and nested expressions. Limit
the search to previous results, match similar words, or search topic titles only.
Tab Position Select Top, Left, or Bottom.

Default pane
Set options for Help projects.
Websearch Quickly find topics on the web. A WebSearch button is added to the Help viewer.
Create Browse Sequences Transfer WinHelp browse sequences into HTML-based Help.
Ignore Secondary windows Format jumps to display the HTML topics in the viewer.

Note: Display pages from the WinHelp CNT in custom windows. HTML supports jumps from TOC pages to custom
windows.
Add Keywords To Selects the location for saving keywords:
Index File (HHK) Save all keywords in a single index file.
Each Topic Save all keywords in the HTML topic files referencing them.

Last updated 3/1/2010

USING ROBOHELP HTML 8 90
Projects

Note: The project compiles a binary index when keywords are added to HTML topics. Topic keywords are automatically
sorted in the index and cannot be cross-referenced. They can link only to local HTML topics. The destination topics can
be displayed only in the default Help window.

Advanced
Open the HTML Help Advanced Settings dialog to further customize the viewer.

HLP and HPJ files
When you import compiled WinHelp 4.0 files, RoboHelp does the following:

• Creates an HTML-based project. Information in the HLP or HPJ file is used to create the project file (HHP) and a
RoboHelp project file (XPJ).

• Creates HTML topics. Information in the HPJ file is used to create an HTML Help file and a RoboHelp project file
(XPJ). Open the project to open the XPJ file. A separate HTML topic is created for each WinHelp topic. These files
are saved in the HTML Files (Topics) folder.

• Converts WinHelp graphics to HTML images. WinHelp bitmap files (BMP, MRB) and metafiles (WMF) convert
into Graphic Interchange Format files (GIF). Images that are right-aligned are left-aligned in the HTML topics.
Modify the size and placement of these images in the Design Editor.

• Converts hotspot images into image maps. WinHelp hotspot images (SHG files) convert to HTML image maps
(GIF).

• Converts WinHelp navigation to HTML navigation. WinHelp jumps convert into HTML hyperlinks. WinHelp
pop-alls convert to smart ups. Browse sequences also convert. Mid-topic jumps are maintained.

• Maintains authorable buttons. Authorable text buttons, mini buttons, and graphic buttons all convert and work in
the HTML topics. Modify authorable buttons in the Design Editor. Authorable buttons are known as Link Controls
and HTML Help controls.

• Creates an HTML table of contents. An HTML Help table of contents (HHC file) is created from the WinHelp
contents file (CNT). Modify the table of contents in the TOC Composer.

• Creates an HTML index. An HTML Help index (HHK file) is created that includes the same keywords as in
WinHelp. A new index includes keywords that match jumps in the topic.
The RTF files are used to create an HTML index that includes the same keywords. Modify keywords in the Index
Designer and use the Smart Index wizard to automate indexing tasks.
Note: This information doesn’t apply to every HLP or HPJ project.

HTML projects from WinHelp: Frequently asked questions
Will WinHelp macros work in the HTML project?
All WinHelp macros with HTML counterparts are converted and included in the HTML project. Non-standard
WinHelp macros with no HTML equivalent are not converted.
Can HTML topics open in custom windows as in WinHelp?
You can format books and pages in the TOC to display destination topics in custom windows or frames. Microsoft
HTML Help does not support links to custom windows, though you can format these links to use pop-up note
windows and frames.

Last updated 3/1/2010

USING ROBOHELP HTML 8 91
Projects

Can I use tabs in HTML topics?
HTML does not support tabs and converts them to spaces. Use tables instead to position text in HTML.
How can I add spaces to position text in HTML topics?
You can edit topics in the RoboHelp HTML Editor and add non-breaking spaces to position text. However, display
issues can occur if the Help window is resized. Consider using tables instead to position text in HTML.
Tables convert into HTML topics, but the columns do not resize properly and a horizontal scroll bar appears.
Use the Design Editor to resize cells and tables.
How can I fix incorrectly formatted bullet lists?
You can remove broken bitmap references from topics and use HTML bulleted styles, and adjust hanging indents. You
can also use the Formatted Text option to import paragraph formatting from Word documents.
My WinHelp topics use manually numbered lists with {SEQ} fields. What happens to these fields?
HTML does not support {SEQ} fields, but recognizes number sequences and converts the lists into numbered
paragraphs. You can delete these numbers and apply an HTML numbered style to the list.
What happens to nonscrolling regions?
HTML projects do not support nonscrolling regions, and the tri-pane output window does not need them.
The background in the Design Editor is gray, but in the preview window is white. How can I make the background
always white?
The style sheets use a gray background (the HTML default), while the preview window uses a background specified by
your browser. To change the style sheet background, see “Use color and images” on page 151.
When I click a hyperlink, an error says the system cannot open the site or find the path. What does this mean?
The link is to a non-existent file or a topic in a DOC or WinHelp Help file not included in the project.
After I create the HTML project, is it ready to distribute?
Open the HTML project in RoboHelp, review the topics, TOC, index, and so forth. Preview the topics and test the
links.
Will context-sensitive topics transfer into an HTML project?
What's This? topics in RoboHelp for Word can convert into text-only topics. Dialog box level topics can convert into
individual HTML topics for use as window-level Help in RoboHelp.

Import a WinHelp HLP file into an HTML project
1 In the Starter pod, click More under Import.
2 Select WinHelp (*.hlp) and click OK.
3 In the Help-To-HTML wizard, define options for your HTML project.
4 Click Browse, navigate to the HLP file, and open it.
5 Click Next. Set up File options:

USING ROBOHELP HTML 8 92

Last updated 3/1/2010

Projects

Desired Result
Specify a hard drive and folder for saving the HTML project and
image (GIF) files (use the same folder for both).

Actions
Click Browse
and navigate to the drive/folder to select it.
Or enter the name of the folder in the text box.

Limit the length of the HTML files to eight characters.

Select Short Filenames. (Enter the first three characters in Prefix
if you want the filenames to use similar naming conventions.)

Distribute the HTML project as uncompiled HTML Help (not
using Adobe WebHelp)

Enter the name of the start page in Start Page Name.

Distribute the project as compiled Microsoft HTML Help or
cross-platform Help using Adobe WebHelp, JavaHelp, or Oracle
Help output.

Do not enter information in Start Page Name.

6 Click Next. Set up Style options:
Desired Result

Actions

Format HTML topics without attaching style sheets to them.

Select <No Stylesheet>. All topics use default HTML styles, gray
background, black serif font.

Format HTML topics to look exactly like the WinHelp topics.

Select <Embedded>. Style sheets are not attached to topics. All
formatting is embedded in individual topics. The topic title is
Heading 1 style. All other text (regardless of the styles used in
WinHelp) is in Normal style.

Attach a custom style sheet to all HTML topics.

Click Browse and navigate to the drive/folder where the style
sheet file (CSS) is located to select it.

7 Click Next. Set up HTML Help options:
Desired results

Actions

Specify where the Contents, Index, and Search tabs are
displayed in the viewer.

Select Top, Side, or Bottom.

Convert your WinHelp pop-up windows into standard HTML
links.

Deselect Display Popups In An Active pop-up window.

8 Click Finish.

Version-control projects may have more options.
Tips:
• If you link a style sheet to your HTML topics, a generic style sheet file called StylesCSS is created and added into
your project folder. You can modify the styles in this style sheet at any time.

• If you select Convert Numbered lists, all WinHelp topics that use numbered lists retain the numbered list
formatting in the HTML topics.

HTML limitations with HLP files
Bullets Make sure that the WinHelp topics do not use bitmap references as bullets. You can select an option to keep

bulleted lists. This option applies only to topics that use bullet characters and not images. If you use images, the HTML
output might not include hanging indents.
HTML jumps Jumps to HTML pages are not converted. You can easily re-create the links in the Design Editor after the

HTML topics are created.

Last updated 3/1/2010

USING ROBOHELP HTML 8 93
Projects

Jumps to external WinHelp topics Jumps to external WinHelp topics are stripped out of the HTML topics. If you are

using WinHelp projects (especially master projects) that include external jumps, use the HPJ file instead of the HLP file.
Macros, buttons, and shortcuts These macros convert: Jump Context, JumpId, and PopupId. Other macros are not
converted. Jump Context macros that send output to a window do not convert because links that send output to
custom windows are not supported. Only buttons convert for Popup Context macros. Graphic buttons retain their
images, but the button is not included.
Microsoft Word HTML styles Microsoft Word HTML styles are not used to format the HTML topics.
Microsoft Word templates Word templates that are used to format RTF files in WinHelp are not converted to HTML

style sheets.
Mid-Topic jumps Mid-topic jumps are converted to bookmarks. The bookmark name does not use the mid-topic jump

topic ID that was created in WinHelp. Instead, it is assigned a sequence of numbers so that it can be read in the HLP file.
Multimedia files (AVI and WAV) These files cannot be converted with HLP files. You can add sound and video to

HTML topics in the Design Editor. HTML topics can use AVI, AU, MID, RMI, WAV, and other files.
Non-scrolling regions HTML-based output does not support non-scrolling regions.
Numbered lists Numbered lists use a 12-point serif font by default. You can create a numbered list style and use it to

reformat numbered lists.
Related Topics buttons Related Topics keywords are translated into Related Topics terms. You see customizable
buttons when you view the topics.
Secondary windows WinHelp secondary windows are not translated. Unlike WinHelp topics, HTML topics do not

support links that display information in secondary windows. You can design custom windows in RoboHelp and use
them to display topics selected from Related Topics buttons, Keyword Link controls, See Also controls, the table of
contents, and the index.
Table of contents The HTML TOC file (HHC) does not support WinHelp pages that link to external WinHelp topics
or reference macros or that contain link statements. You can link HTML TOC items to HTML topics, web and e-mail
addresses, FTP sites, newsgroups, and multimedia.
What's This? Help Context-sensitive Help is not converted. What's This? Help-style topics or dialog topics are
converted into regular HTML Help topics. You can import map files and assign map IDs for the window-level Help
topics. For What's This? Help, you can re-enter the text from these HTML Help topics into a text-only dialog box and
create text-only topics. You can also import context-sensitive Help created with the What's This? Help Composer into
your HTML Help projects. If you use the HPJ file, you can transfer the context-sensitive Help topics into HTML Help.
Microsoft Word formatting Formatting that is not converted in the HTML topics includes underlining, paragraph

spacing, indents, alignments, table borders, spreadsheets, background colors, and watermarks.

Tips for creating HTML projects with HLP files
• Help files for Windows 3.x and 95 and later are supported.
• HTML topics cannot use styles and formatting from the WinHelp project. All topic titles are formatted to the
Heading 1 style and the rest of the topic is formatted to the Normal style.

• Embed the formatting when selecting style options. Instead of attaching a style sheet, the HTML topics are
formatted to closely resemble the formatting used in the WinHelp topics.

• A style sheet is not required. It can be created after generation.
• If the entire WinHelp project is available, create the HTML project using the HPJ file rather than the HLP file.

Last updated 3/1/2010

USING ROBOHELP HTML 8 94
Projects

Import a WinHelp HPJ file into an HTML project
1 Select File > New > Project.
2 Click the Import tab.
3 Select WinHelp Project. Click OK.
4 Click the browse button, and select the HPJ file to import. Click Next.
5 Specify the output folder and filename.
6 Under Choose Source Document(s), select the Word documents you want to import.
7 Click Finish or click Next to step through the remaining steps in the wizard.

Tips for creating HTML projects with HPJ files
• To ensure that the HTML project suits your preferences, review the steps before you start.
• All files referenced by the WinHelp project (HPJ) must be in the locations you specify before you generate the
project files.

• You can create a single style sheet and apply it to all topics or use different style sheets for different topics.
•

WinHelp topics can use a combination of defined styles and manual character and paragraph formatting. If so,
create style sheets that use the same styles from the WinHelp topics to retain the special formats.

• You can select an existing style sheet that you use with other HTML projects. Make the style names in the WinHelp
topics identical to the style names in the style sheet. Also, format the paragraphs in the WinHelp topics to use these
styles. Otherwise, you'll have to apply styles from the style sheet to paragraphs in the HTML topics after the project
is generated.

• You do not have to use a style sheet at all. The HTML topics include the formatting from the DOC files (as inline
styles which are individually formatted paragraphs and characters). You can always create styles and apply them to
topics after the HTML project is created. (If your project is large, do use style sheets to create the HTML topics.
When you revise the styles, the topics are automatically updated.)

• Run a small test project to become familiar with the options. Experiment with different options until you get the
HTML output you want.

• If you are generating a large project, decide how you want to organize it beforehand. In HTML, you have one
HTML topic file for each WinHelp topic. You have several options for organizing these files. You can save them at
the root of the project folder or in a subfolder. You can create subfolders based on the DOC filenames and save the
corresponding topics in them. Finally, you can save topics based on their use as pages in the table of contents.
(Folders are created for each book and subfolders are created for sub-books in your CNT file.)

• Often a project is used in combination with several other WinHelp projects (for example, as a master project). If
so, create HTML projects with each HPJ file separately so that all the links work.

• After the project is generated, you often want to make a few changes to the style sheet. By default, it uses a gray
background. You can change it to white by changing the document properties for the style sheet.

Reports
Export project reports
1 Click Tools > Reports. Select report type.
2 Customize the report.

Last updated 3/1/2010

USING ROBOHELP HTML 8 95
Projects

3 Click Save As.
4 Browse to the location where you want to save the file.
5 Enter a name for the file.
6 From the Save As Type list, select RTF or TXT.
7 Click Save.

Print reports
1 Select Tools > Reports.
2 Select the report type.
3 Customize report options.
4 Click Print.

Print the table of contents or index from the TOC pod or Index pod. Select File > Print.

Send reports
You can share reports with others by sending the content as an e-mail message.
1 Select Tools > Reports.
2 Select the report type. The Reports dialog box appears.
3 Use the options available to customize the report. (Not all reports are customizable.)
4 Click Mail To.

Your e-mail program creates a message and the report information is added as the content of the message. Edit this
text and add information as you would any other e-mail message.
5 Address and send your e-mail.

Note: If you need assistance using the Mail To feature (for example, your system prompts you to set up a profile), contact
your e-mail administrator.

Generate and customize reports
All reports are available from Tools > Reports.

Broken links report
This report (available from Tools > Reports > Broken Links) finds files that contain broken links. This report is not
customizable.
Notes:
• In a multi-author, version-controlled environment, ensure that you don’t link to topics that have been moved,
renamed, or removed. These links will be broken.

• For a version control project, have one person test the latest version for broken links before releasing the final
output.

Last updated 3/1/2010

USING ROBOHELP HTML 8 96
Projects

Conditional Build Tag report
This report provides information about usage of topic-level, content-level, and TOC-level build tags in the entire
project.
It displays a summary of the project. It identifies the conditional build tags used in the project. For each tag, it shows
the detailed path of all topics in which the tag is used.
1 Select Tools > Reports. Select Conditional Build Tags. The Reports dialog box appears, with the Build Tags tab

selected, displaying the Conditional Build Tag report.
By default, the report sorts the tags by Build Tag Name.
2 (Optional) To change the sort order, select Options. The Build Tag Report Option dialog box appears.
3 Select Topic, TOC, And Index Name.
4 Click OK. You can view the tags usage report sorted by Topic, TOC, and Index Name.

See Also report
1 Select Tools > Reports > See Also. The See Also report appears.
2 Customize these options as needed:
Keywords Includes all keywords from the index.
Keywords And Topics Contains a list of keywords. Each keyword lists the topics that use it. You can discover if

keywords are not linked to any topics and identify topics to remove from keywords.
Topics And Keywords Contains a list of topics. Each topic list the keywords associated with the topic. You can

discover if topics are missing keywords, inconsistent phrasing, and identify keywords to remove from topics.

Duplicate Map IDs report
Each map number in your project must be unique. Use this dialog to remove duplicate map IDs.
If your project includes context-sensitive Help, make all map numbers in your map files unique. If some map files use
the same map numbers, the Duplicate Map IDs tab identifies them for you.
Note: If duplicate map IDs exist in your project, some of your context-sensitive Help topics might not work properly.
❖ Select Tools > Reports > Duplicate Map IDs.

Use this report to test your help project. With the RoboHelp BugHunter tool, you can test map numbers and topics.

External Topics report
The External Topics report (Tools > Reports > External Topics) includes data on these topics:

• URLs
• Links to HTML topics in other CHM files
• FTP addresses
• Newsgroup addresses
• E-mail addresses
Tips:
• Use this report to test your links.

Last updated 3/1/2010

USING ROBOHELP HTML 8 97
Projects

• Share this report with authors who use these URLs.

Glossary report
1 Select Tools > Reports > Glossary.
2 Select one of these options from the Reports menu:
Detailed Lists Terms and definitions
Overview Lists Terms without definitions

The glossary report is shown for the glossary selected.

Index report
1 Select Tools > Reports > Index.
2 To customize, select from the following options:
Keywords Includes all keywords from the index.
Keywords And Topics Contains a list of keywords. Each keyword lists the topics that use it. You can discover if

keywords are not linked to any topics and identify topics to remove from keywords.
Topics And Keywords Contains a list of topics. Each topic lists the keywords associated with the topic. You can

identify missing keywords, inconsistent phrasing, and keywords to remove from topics.
Select Index Select an Index from the list to generate a report for the index selected.

Images report
❖ Select Tools > Reports > Images. The Image report appears.
View An Alphabetized List Of Images Grouped under each image is a list of all topics that use it.
View An Alphabetized List Of Topics Grouped under each topic is a list of all images they include.

Map IDs report
Use this report (Tools > Reports > Map IDs) to generate a project summary. It includes the number of map IDs, topic
ID and location, map number, and map filename.
The Map IDs report provides information about all the context-sensitive Help topics that are used in your project,
including map IDs and text-only topics (for What's This? Help).
First, the report displays a summary of the entire project. It identifies the number of map IDs and then gives more
specific information. Each topic in the project that has a map ID assigned is listed with topic ID, map number, map
filename, and topic location.
Use this report as a reference for testing Help.

Project Status report
Generate information for a group of topics (Tools > Reports > Project Status) by selecting a specific folder from the
Folder list.

• Total number of topics completed, in progress, and ready for review
• Total number of topics in a project
• Estimated development time to author all topics

Last updated 3/1/2010

USING ROBOHELP HTML 8 98
Projects

• Information on To Do items

Snippets report
Select Tools > Reports > Snippets. The Snippets report appears showing the snippets defined in the project. The
Snippets report also shows the topics in which a particular snippet has been used.

Style Sheets report
Use this report (Tools > Reports > Style Sheets) to view an alphabetized list of style sheets or topics. The list of style
sheets shows which topics use each style sheet. The list of topics identifies which style sheet each topic is attached to.
To sort, choose an option from the Sort By menu.

Table Of Contents report
Use this report (Tools > Reports > Table Of Contents) to view information about TOCs. Specify the level of detail you
want to see:
Detailed Includes titles of books and pages, names of linked topics, and location of files.
Overview Includes titles of books and pages and the names of linked topics.

The Table of Contents report is shown for the TOC selected.
You can change your table of contents whenever you change topic titles or filenames.

Topic Properties report
Use this report (Tools > Reports> Topic Properties) to filter reports according to various properties. To customize the
report, click Options, and select details to add:
General Folder and bookmark names and locations.
Topic Status Status, priority, time, completed To Do items, and comments.
References Links to the topic, links from the topic, map IDs, table of contents, See Also keywords, and keywords.
Advanced Information types, conditional build tags, search keywords, and style sheet, and exclude from search.

You can filter the list of topics included in the report by selecting a specific folder from the Folder list.

Topic References report
Use this report (Tools > Reports > Topic References) to track topic references. References include:

• Topic links
• TOC books and pages that use the topic
• Keywords and phrases that use the topic
Select the Folder list to generate information for a topic group.
Tips:
• Use this report to find references to remove when updating your topics.

• Before you remove a topic, you can remove all references to it. Use this report to identify the references and relink
them to different topics.

• If you don't remove references when you remove a topic, this report identifies the breakable references.

Last updated 3/1/2010

USING ROBOHELP HTML 8 99
Projects

Topics By Priority report
The Topics By Priority report (Tools >Reports > Topics By Priority) provides a summary of your project. It lists topics
sorted by the priority assigned by the author. This information is gathered from the topic properties. Therefore, the
key to making this report work for you is to change topic properties as you author.
To customize the information in this report, click Options and select the information you want to include in it. You
can select a range of priorities or view all priorities. You can also filter the list of topics included in the report by
selecting a folder from the Folder list.

Unreferenced Topics report
This customizable report (Tools > Reports > Unreferenced Topics) tracks unreferenced topics in the TOC, index, or
in other topics. Use it to identify:

• Inaccessible topics (To fix, create links from other topics.)
• Topics excluded from the TOC
• Topics without index or See Also keywords (To fix, add keywords, or add the topic to a See Also keyword.)
Note: Some topics do not use references. For example, if you create window-level context-sensitive Help, topics are only
accessible when end-users press F1 or click Help. They don't need references. You can identify unreferenced topics that
you are using as context-sensitive Help topics.

Unused files report
Use this report (Tools > Reports > Unused Files) to view unused files in one place. You can sort by filename or file type
by selecting from the Sort By menu.
You cannot remove these files from within your project. Make a list of the unused files and their paths and then use
Windows Explorer to delete the files.
Important: Before you delete files, make a backup copy of the project in case you need to revert changes.
Note: Indiscriminate deletion of files other than what is listed by the unused files report, results in broken links, missing
files and other undesirable consequences.

Unused index keywords report
Use this report (Tools > Reports > Unused Index Keywords) to track all index keywords that are not associated with
topics. Use it to:

• Identify index keywords that you can remove from your project.
• Find index keywords that must be associated with topics.
• Review cross-references included in your index.

Used Files report
Use this report (Tools > Reports > Used Files) for an inventory of all files in the project.

Missing topics report
Use this report (Tools > Reports > Missing Topics) to track missing topics and several associated elements:

• TOCs, books, and pages that reference missing topics
• Index keywords and phrases that reference missing topics
Select a folder from the Folder list to generate topic group information.

Last updated 3/1/2010

USING ROBOHELP HTML 8 100
Projects

Tips:
• Before you remove a topic, remove all references to it.

• If you do not remove references when you remove a topic, this report identifies the breakable references.

Variables report
Use this report (Tools > Reports > Variables) to list variables in the order they were created along with their values and
information about their usage.
If you view all variables in the project, the report indicates the variables defined in Variable sets and the files in which
they are used. You can also find variables that have not been used.
This report is useful when you want to remove variables. Locate all topics in which the variables are used and delete
references to the variables before deleting the variables.

Reference
URL Properties dialog box
Use this dialog box to link index keywords to URLs in your project.
Keywords Enter the word or phrase that end users must enter in the index to access the URL.

Delete Old Project dialog box
Delete the old WebHelp Pro project from the RoboHelp Server before publishing the renamed project.

Move File Into Project dialog box
Restore a broken topic link by finding a file or creating a link.
Try To Find Browse for the linked file.
Create New Create a topic and save it in your project folder to repair the broken link.

Help to HTML style options
Select The Style Sheet To Use Specifies the style sheet name to attach to all created HTML topics.
No Stylesheet Does not attach a style sheet. All topics use default formatting.
Embedded Styles Does not attach a style sheet to the topics. All HTML topics use WinHelp formatting. Formatting is
embedded into each HTML element.
Convert Bulleted Lists Uses bulleted list items from WinHelp topics in topics (retains bulleted lists).
Convert Numbered Lists Uses numbered list items from WinHelp topics in topics (retains numbered lists).

Tips:
• You can modify any style sheet after you convert the project.

• Create new style sheets after converting and attach them to topics.
• Projects can include multiple style sheets.

Last updated 3/1/2010

USING ROBOHELP HTML 8 101
Projects

HTML Help Advanced Settings tri-pane
Buttons
Defines the buttons/controls to include in the toolbar. Options:
Hide/Show Hides the left-tab components in the tri-pane.
Options Displays a menu of options.
Locate Synchronizes the left and right panes (when Auto Synchronize TOC is not selected).

Navigation pane
Defines how content appears in the viewer. Options:
Auto Show/Hide Nav Pane Hides the left navigation pane when end users switch from a compiled help file to a
program. The content remains visible in the right pane. The left tabs can't be viewed until the user selects the window.
Auto Synchronize TOC Formats the left and right panes to synchronize as users navigate content.

Note: Project filenames cannot include spaces. You can automatically replace spaces with underscores after you create
the project.
Width Defines the navigation pane width in pixels.

Note: Project filenames cannot include spaces. You can automatically replace spaces with underscores after you create
the project.
Width Defines the width of the navigation pane, in pixels.

Font
Selects a font for displaying titles on the Contents tab.
Select Opens the Font dialog box.
Default Sets the font to use your default system setting.

HTML Help Advanced Settings TOC tab
Border Add a border around the Contents pane.
Dialog Frame Add a frame around Contents pane.
Lines From Root Display lines connecting books and pages starting at the root.
Plus/Minus Squares Display plus and minus squares that open and close books.
Folders Instead Of Books For table of contents book items, display a folder icon in place of a book icon.
Single-Click To Open Book Formats book items to open with a single click. When this feature is not selected, books

open with a double-click.
Lines Between Items Add lines between books and pages.
Raised Edge Format the table of contents so it looks raised from the tri-pane.
Sunken Edge Format the table of contents so it looks sunken into the tri-pane.

102

Last updated 3/1/2010

Chapter 4: Working with topics
Create, save, and open topics
Create a topic
1 In the Project Manager pod, open the XHTML Files (Topics) folder.
2 To store the topic in a specific custom folder, select the folder.
3 Do either of the following:

• Click the New Topic icon

• To create the topic with a different HTML editor, right-click and select New > Topic With. Then select the
editor.
Note: You can also right-click in the Topic List and select New Topic With > [editor].
4 Specify a topic title and filename.

For best results, use underscores instead of spaces in filenames, and follow the HTML file naming protocol. Avoid
using these characters in filenames: \ / : * ? < > | # ", $, &, [ ]
(Apply these same conventions to folder names.)
5 (Optional) Select a master page.
6 Specify a language for the new topic.

Note: If you do not specify a language for the topic you are creating, RoboHelp uses the language setting for the project.
RoboHelp uses the language setting for a topic for the spelling checker, the thesaurus, smart indexing, and full-text
search indexing. The output UI is controlled by the project language setting. For more information about language
support, see “Authoring content in multiple languages” on page 45
7 Add keywords to enable search on this topic. To separate the keywords, you can use commonly used characters,

such as comma, semicolon, and space. Space works in most languages.
Note: The keywords you specify are added to the index. For more information, see “Topic keywords” on page 158.
8 Select Exclude From Search only if you do not want to display this topic in the search results.

Note: Exclude From Search is not available for Microsoft HTML Help (CHM) search.
To open a topic in a third-party editor, right-click the topic in the Project Manager or the Topic List and select Edit
With. The topic opens in the editor you specified (the Editor box still displays the editor set for the project).

More Help topics
“Add underscores to filenames” on page 112

Save topics
Save a topic
• Press Ctrl+S.

Last updated 3/1/2010

USING ROBOHELP HTML 8 103
Working with topics

• In the toolbar, click Save.

Enable or disable Save
If you deselect Save Without Prompt, you are prompted to save topics.
1 Select Tools > Options.
2 Click the General tab.
3 Under Options, select or deselect Save Without Prompt.
4 Click OK.

Rename topic files
Note: Avoid using Windows Explorer or your version control application to rename files. The Project Manager cannot
update file references.
1 Do either of the following:

• In the Project Manager pod, expand the appropriate folder. Select View > By File Name. Right-click the file, and
select Rename.

• In the Topic List pod, right-click the file. Select Properties.
2 Type the new name.

For best results, use underscores instead of spaces, and follow the HTML filenaming protocol. Avoid using these
characters in filenames: \ / : * ? < > | # ", $, &, [ ]
If the filename has multiple words, use underscores instead of spaces.

Open topics
You can open topics in Design Editor or another editor while still using RoboHelp to add online Help features.
❖ In the Project Manager or Topic List pod, do one of the following:

• To open the topic in Design Editor (or a third-party editor you’ve set as the default editor), double-click the
topic.

• To open the topic in an editor, right-click the topic and select Edit With > [editor].
If you are prompted whether to continue with possible HTML code changes, click Yes. However, to avoid code
changes from one editor to the next, edit topics in the same editor and click No.

More Help topics
“RoboHelp Design Editor” on page 122
“Third-party HTML editors” on page 123

Support for multiple document interfaces
You can open multiple topics in Design Editor. You can edit topics simultaneously, compare topics, and copy content
from one topic to another.
Each open topic has a corresponding tab in the Design Editor pod. Click a tab to make its topic window active. Click
the scroll arrows to scroll through tabs and reveal hidden tabs. Drag the tabs to position topic windows horizontally
or vertically within Design Editor.

Last updated 3/1/2010

USING ROBOHELP HTML 8 104
Working with topics

Author in XHTML
You can use RoboHelp to create topic files in XHTML and project-specific files in XML. Structured authoring in XHTML
ensures well-written code, closed tags, no overlapping of tags, properly quoted attributes with explicit values, and no
proprietary attributes. RoboHelp upgrades all the old RoboHelp for HTML topics to XHTML when it imports them.
The RoboHelp editor creates all the topics in XHTML. All topic files are compliant with XHTML 1.0 Transitional.
XHTML generated from RoboHelp conforms to the XHTML 1.0 Transitional specification from the World Wide Web
Consortium (W3C). All topics have the XHTML 1.0 Transitional doc type:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

Every XHTML topic contains an HTML tag and an xmlns attribute value of http://www.w3.org/1999/xhtml.
Note: To view the XHTML source of a topic, open the topic in the Design Editor and select the HTML view.
You can use third-party editors such as Notepad, Microsoft Word, or Adobe Dreamweaver to edit your files and retain
these files in their existing format. You can edit topics using a third-party XHTML editor. RoboHelp retains its
processing instructions (PI) as comments to avoid any data loss. You can use RoboHelp to edit the third-party HTML
or XHTML topics and generate XHTML output.
Note: Snippets, master pages, and framesets are created in XHTML format only.
When creating a project, RoboHelp creates several project-specific files, such as APJ, CSS, and BRS files, in XML
format. For example, the TOC, index, glossary, and the following project filename extensions are generated in wellformed XML:
.ali, .brs, .phr, .stp, .ign, .lng, .ssl, .xpj, .apj, .syn, .glo, .hhk, .hhc, .ppf, .fpj
These files are in the root of the RoboHelp project folder. You can open these XML files and read the data using XML
processors.

Convert XHTML to HTML
1 Select Tools > Options > General.
2 Select Convert RoboHelp Edited Topics To HTML.

Selecting this option converts all the topics to HTML in the SSL output. You can generate the SSL to check whether
the output files are in HTML or XHTML. XHTML pages support all the DHTML effects that can be applied using
RoboHelp HTML. HTML pages do handle DHTML effectively. Within a topic, right-click and select View or Preview
Topic. View the source of the output file or preview the topic to verify whether it is XHTML or HTML.

More Help topics
“RoboHelp editors” on page 122

Validate XHTML
You can validate the RoboHelp generated XHTML code against W3C specifications for compliance with XHTML
Transitional 1.0. You can select File > W3C Compliance > Validate and RoboHelp validates the topic. You can select
Validate All to validate all the topics.
The following features are not supported in XHTML:

• Marquees in topics

USING ROBOHELP HTML 8 105

Last updated 3/1/2010

Working with topics

• Border color in framesets
• Background sound in topic properties
Use of these features results in invalid XHTML code. Remove these features to generate valid XHTML code.

More Help topics
“W3C compliance” on page 120

Import and copy topics
Import topics
1 Select View > Pods > Project Manager. The Project Manager pod appears.
2 Open the HTML Files (Topics) folder.
3 To save the file in a subfolder, select the folder.
4 Select File > Import > HTML/XHTML File.
5 Navigate to the HTML/XHTML file.
6 Select the file. Press Ctrl to select multiple files.
7 Click Open.
8 Click Yes to copy the file into the project folder. Click Yes To All to copy the file and all its components.

Note: You can similarly import FrameMaker documents (*.mif, *.fm, *.book, *.bk), PDF documents (*.pdf), Word
documents (*.docx, *.docm, *.doc, *.rtf), XML files (*.xml), DITA maps (*.ditamap), and DITA topics (*.xml, *.dita).

Copy topics into a project
1 Do one of the following:

• Select View > Pods > Project Manager. The Project Manager pod appears.
• Select View > Pods > Topic List. The Topic List pod appears.
2 Select a topic.
3 Right-click and select Duplicate Topic.
4 In the Topic Title box, type the title.
5 If the topic is associated with a master page, it appears in the Master Page pop-up menu. If None appears, the topic

uses the default style sheet.
6 Click the View icon

to view the master page. Or, browse to a new master page.

7 Click the Appearance tab to change the style sheet.
8 Click OK.

The new topic is appended to the project. It appears in the Project Manager.

USING ROBOHELP HTML 8 106

Last updated 3/1/2010

Working with topics

View topics and design elements
Preview topics
Preview topics instead of generating an entire project. Click links and Related Topics buttons, see Dynamic HTML
effects, access frames and forms, and view features.
1 Open a topic in Design view or select the topic in the Topic List pod or Project Manager pod.
2 From the toolbar, click the View icon

3 (Optional) To preview conditional text areas, choose a conditional build tag expression from the menu.

Tips
• To go back to the previously displayed topic in preview mode, press the Backspace key. Or, right-click in the
preview window and select Back.

• Leave the window open and change the topic in Design Editor. When you click anywhere in the preview window,
the window updates the content to display the new changes.

• Certain features do not work in preview mode, such as See Also controls and Keyword Link controls.

Define a conditional build expression
1 In the preview window, click Define.
2 Specify tags to exclude from the output:

• To move one tag, select it and click the single arrow button.
• To move all tags, click the double arrow button.
3 (Optional) Click Advanced. Select a conditional build tag from the menu. Click Add Tag. Click the AND, OR, or

NOT operators to define an expression. Click Clear to remove the expression.
NOT Excludes topics that use a named conditional build tag. NOT has the highest priority of all the build

expressions.
AND Includes or excludes topics that use specified conditional build tags. AND has the second-highest priority of

all the build expressions.
OR Includes or excludes topics that use specified conditional build tags.

4 Click OK to return to the preview window.
5 To remove the condition from the preview, select None from the menu.

View design elements
❖ Select View > Show > [design element].

USING ROBOHELP HTML 8 107

Last updated 3/1/2010

Working with topics

Design element

Appearance in the Design Editor

Bookmarks
Paragraph markers
Table gridlines

Glyphs
Fields
Unknown tags

Conditional areas

Comments

Master pages
Note: Master pages replace templates in RoboHelp HTML 7 and earlier.
An HTML page is made up of three elements: content, layout, and styling. For single sourcing, the best practice is to
separate content from styling and layout. Although CSS files help to separate styling from the content, layout remains
embedded in the HTML code. By using master pages, you can separate layout and styling from the content. A master
page contains the layout information and is associated with a CSS file.
A master page is a template for HTML topics. You define the placement of headers, footers, and placeholders for the
body, breadcrumbs, and mini TOC. Master pages can include snippets and user-defined variables. You can create a
topic using a master page or associate an existing topic with a master page. When you create a topic using a master
page, the body content is placed in the resulting topic. If you apply a master page to an existing topic, the body content
is ignored.
The layout information defined in the master pages is not visible in Design view. However, you do see the CSS of the
master page in Design view. You can see the layout when you generate output or a preview. The topic content is placed
in the body placeholder, and the layout is inherited from the master page. All placeholders defined in the master page
are also populated with relevant information when you generate output.
You can use tables to create a precise layout where each placeholder is placed in a table cell.
Body placeholder When you create a topic from a master page, the topic includes content from the master page.
Copyright information is an example. When you apply a master page to a topic, actual content of the topic replaces the
body placeholder at the time of preview and generation.

Note: When you apply a master page to a topic, the header and footer of the topic are overridden by those of master pages.
Mini TOC placeholder Shows the automatically generated mini TOC at the time of generation or preview of Help topic.
Define the exact location and format of the mini TOC by designing the layout of the master page. By default, the levels
allowed for a TOC layout are heading 2 to heading 6.

Last updated 3/1/2010

USING ROBOHELP HTML 8 108
Working with topics

Breadcrumbs placeholder Shows the automatically generated breadcrumbs at the time of generation of Help topic.

The breadcrumbs are generated based on the TOC. When you preview a topic, actual breadcrumbs links are not
generated and only the layout of breadcrumbs is visible.
You can apply conditional build tags to the mini TOC and breadcrumbs placeholders but not to the body placeholder.
However, you can apply a conditional build tag to the content inside or outside the body placeholder.

Create a master page
1 Do one of the following:

• Select File > New > Master Page.
• Select and right-click Master Pages in the Project Set-up pod.
2 Select New Master Page.
3 Enter a name for the new master page in the General tab.

Note: Master pages have the filename extension .htt.
4 Click the Appearance tab.
5 Select a style sheet to apply to the master page.
6 (Optional) Select the Background Sound options.
7 Click OK.

A new master page shows the body placeholder by default. You can insert mini TOCs by clicking the Mini TOC icon
and breadcrumb placeholders by clicking the Breadcrumbs icon
from the toolbar in the Design editor of master
pages. But this toolbar does not appear for normal pages. You can insert any number of mini TOCs or breadcrumbs
at any location in the master page.

Create a master page from a topic
1 Open a topic.
2 Do one of the following:

• Right-click in the Design Editor and select Add To > Master Pages.
• Select File > Add To Master Pages
All the content in the topic is wrapped in the body placeholder. After you add a topic to a master page, any new topic
created from this master page includes its body placeholder content.
When topics are associated with a master page, the style sheet, header, and footer of the master page override style
properties of the topic. You can edit or change the CSS of a topic later.
Note: Use the Topic Properties option to change the master page associated with a topic.

More Help topics
“Headers and footers” on page 136

Formatting master pages
When you generate or preview a layout, border and shading properties of the master pages override border and
shading properties of topics. If the properties do not conflict, they are applied independently. For example, if you set
border properties for a master page, and background color for a topic, the final output topic has both applied to it.

USING ROBOHELP HTML 8 109

Last updated 3/1/2010

Working with topics

Edit a master page
1 Do one of the following:

• Right-click a master page in the Project Set-up pod and select Edit.
• Select a master page in the Project Set-up pod and select Edit > Edit [name of the master page].htt.
• Double click a Master Page in the Project Set-up pod.
2 Make the desired changes.

Change the CSS associated with a master page
1 Right-click in a master page and select Properties.
2 Click the Appearance tab.
3 Select a style sheet from the list of style sheets available in a project.
4 Click OK.

Note: Select the Used In tab in the Master Page Properties dialog box to see a report of the topics associated with the
master page.

Insert a placeholder
You can insert placeholders for mini TOCs, breadcrumbs, and topics in master pages. By default, a body placeholder
is inserted in a new master page.
1 Place the cursor below or after the body placeholder.
2 Select Insert > Placeholder > Mini TOC or Breadcrumbs.

Note: You cannot insert a placeholder inside a paragraph as inline text or in headers or footers.

More Help topics
“Headers and footers” on page 136

Format and edit placeholders
You can format styles in placeholders using the Format Placeholders option from the context menu. Open a master
page in Design view and do one of the following:

• Right-click a placeholder. Select Format Placeholder.
• Select a placeholder and click the Format Placeholder button

in the Design Editor toolbar.

• Double-click in the placeholder.
• Select Format > Placeholder.
Notes:
• If a body placeholder is deleted from the master page or does not appear, the resultant topic has its headers appear
first (if at all), followed by the HTML content of the master page, the topic content, and the footer (if present).

• You cannot apply DHTML effects on the placeholders. The content inside the body placeholder is normal HTML
content, so you can apply DHTML effects to it.

• You can preview the master pages to see how the placeholder content is displayed in the final output. If the
associated master page has mini TOC and breadcrumbs placeholders, the mini TOC and breadcrumbs are
generated at the time of preview or layout generation.

Last updated 3/1/2010

USING ROBOHELP HTML 8 110
Working with topics

More Help topics
“Add breadcrumbs to topics” on page 178

Importing master pages
You can import master pages from other projects and apply them to topics in your current project. When you upgrade
from RoboHelp 7 or earlier, topic templates convert to master pages when you import them. Except for the header and
footer, all the content in the topic template is wrapped in the body placeholder.

Applying master pages
You can apply or change the master page to one or multiple topics at a time. Use this option to change the master page
of one or more, but not all topics in your project. You can apply the master page to all topics when you generate the
Help output.

Apply a master page to a topic
1 From the Topic List, right-click the topic, and select Properties.
2 In the Topic Properties dialog box, select the General tab.
3 All the master pages in a project are listed in the Master Page menu. Select a master page and click OK. Optionally,

you can do the following:

• To preview the selected master page, click the Preview icon.
• To select a master page that is not in the current project, click the Browse button.

Apply a master page to multiple topics
1 In the topic list, sort the topics by the master page associated with them.

Note: If the Master Page column is not visible, right-click a column header, and select Master Page from the menu.
2 Select the topics that are associated with the master page that you want to substitute. If you are applying master

pages for the first time, select the topics that are not associated with a master page. You can also select multiple sets
of topics with different master pages applied to them.
3 Right-click, and select Properties.
4 In the Topic Properties dialog box, select General tab.
5 Select the master page from the Master Page menu, and click OK.

Applying a master page or CSS at the time of generation
Single-source layouts let you override the master page or the CSS when you generate output. For different output
results, apply different master pages or a different CSS.
Each single-source layout except the Printed Documentation layout provides an option to apply master pages or CSS.
You can choose to apply a master page or a CSS across all the topics in a project.
Note: For the Printed Documentation layout, you can apply only a different CSS.

USING ROBOHELP HTML 8 111

Last updated 3/1/2010

Working with topics

To apply to all topics, select Apply To All Topics and choose either a master page or a CSS. The Master Pages and CSS
menus show all the master pages and CSS available in the project.

• If you do not select the Apply To All Topics option, the master pages associated with individual topics take effect.
If no master pages are associated with individual topics, RoboHelp applies no master pages when it generates
output.

• If you choose to apply a master page, master pages associated with individual topics are overridden. The CSS
associated with the master page becomes effective and overrides the CSS associated with all other individual topics.

• If you choose to apply a CSS, master pages associated with individual topics take effect. The selected CSS is applied
to all the topics whether any master page is associated with them or not.

• If a master page is not associated with any CSS, the CSS associated with each individual topic becomes effective.

Manage topics
Rename a topic
When you rename a topic, the title is updated in the topic properties. Links to the topic still work. Other references are
not automatically updated. For example, you may need to edit the TOC page title in the TOC Editor.
If you create new topics using a master page, topic titles are automatically updated when you change a topic title in
Topic Properties.
1 Do one of the following:

• Select View > Pods > Project Manager.
• Select View > Pods > Topic List.
2 Select a topic.
3 In the toolbar, click the Properties icon

. Click the General tab.

4 In the Topic Title box, type the new title.
5 Click OK. The topic title is updated.
6 To change the topic heading, open the topic in the Design Editor. Edit the heading text.

Note: To match the filename to the updated topic title, change the filename when you change a topic title.

More Help topics
“Rename topic files” on page 103
“Manage files” on page 39

Update topic references
If you rename a topic title, make sure that you update the following items as indicated.
Text links The path of the link is updated, but the link text that is visible to a user is not. If link text in any topics

includes the topic title, update each topic.
Topic heading If you want to change the topic heading to match the topic title, change it in the Design Editor.
Table of contents Update a book or page with the new title. In the Table Of Contents pod, right-click the book or page
and select Rename. Enter the new title.

Last updated 3/1/2010

USING ROBOHELP HTML 8 112
Working with topics

Index If the topic title is an index keyword, update the keyword in the Index pod. Right-click the keyword in the upper

pane and select Rename. Type the new title.

Add underscores to filenames
If topic filenames have multiple words, you can set RoboHelp HTML to replace underscores with spaces. This
convention enables TOC books and pages to synchronize with topic content displayed in the viewer.
Existing filenames aren’t affected unless you edit them.
1 Select Tools > Options.
2 Click the General tab.
3 Select Use Underscores In Filenames.

Change topic properties
Topics have properties that define their appearance and index keywords. You can change properties for a single topic
or a group of topics.
1 Do one of the following:

• Right-click one or more topics in the Topic List pod. Select Properties.
• Right-click a topic in the Project Manager pod. Select Properties.
• Right-click a topic in the Design Editor and select Topic Properties.
2 Click a tab and make changes.
3 Click OK.

Use options on the Status tab to track topic development and manage the project. (To access the Status tab, right-click
a topic and select properties. On the Topic Properties dialog box, select the Status tab.) You can also generate project
reports based on properties you set.
Change topic properties on the Index tab (WebHelp Pro)
Work with keywords referenced by the topic.
Select Index Select an index to add keywords or view the related referenced keywords.
Index Keywords Create and edit keywords.
Add Add a keyword from the Index Keywords text box.
Add Existing Copy a keyword from other topics.
Delete Remove a keyword.
Replace Replace a keyword with text from the text box.
Smart Index Open the Smart Index wizard.
Properties Open the General tab. Save the keyword in either the index file or in the current topic.

Changing master pages
To change which master page is applied to a topic, select a master page from the Master Pages menu. The default is the
or browse to a
last master page applied to the topic. You can view the master page by clicking the View button
new master page by clicking the Browse button.

Last updated 3/1/2010

USING ROBOHELP HTML 8 113
Working with topics

More Help topics
“Update the To Do list for a topic” on page 39
“Link a style sheet to topics or master pages” on page 143
“Apply conditional build tags to multiple topics” on page 208
“Identify the browse sequences a topic is assigned to” on page 194

Find a topic
Find topics within your project from the Table Of Contents, Index, and Project Manager pods.
You can search on all or part of a topic title or on topic properties.
1 Click the pod to search:

• To find out which folder a topic is in, click the Project Manager pod.
• To find out where a topic is in the table of contents, click the Table Of Contents pod.
• To find out where a topic is referenced in the index, click the Index pod.
• To find out if a topic is in your project, click the Topic List pod.
2 Select Edit > Find Topic.
3 To conduct a simple search, click the Search tab and type all or part of the topic title next to Topic Title Includes.
4 To conduct an advanced search, click the Advanced tab. You can search according to the following options:
Topic Title Includes Enter text to help you find the topic by title.
File Name Includes Enter text to help you find the topic by filename.

You can search for the following topic properties:
Status Click to ignore status in the search or search for topics that are assigned to a specific status.
File Modified Click to ignore file modification dates or search for files modified before or after specific dates. You

can enter a date at the right of this option.
Priority Click to ignore topic priorities in the search or to search for topics based on a specific priority assignment.

You can enter a number at the right of this option.
Note: Searching by author is not supported.
The Found Topics area has these features:
Found Topics Displays the topics that match the search criteria. Select a topic from this list to preview it or modify

its properties.
View button

Displays the selected topic in the Preview window.

By Title Click to search for text in topic titles instead of in filenames.
Topics Containing <item> Displays the topics that match the search criteria. Select a topic from this list to preview

it or modify its properties.
5 Click OK.

USING ROBOHELP HTML 8 114

Last updated 3/1/2010

Working with topics

Assign a default topic
The default topic appears in the Topic panel when the Help system is opened.
1 In the Single Source Layouts pod, right-click the layout. Select Properties.
2 Next to the Default Topic box, click Select.
3 Select a topic. Click OK.
4 Click Save.
5 Generate and view the layout.

Track topic status
The status of new topics is In Progress by default. You can change this status as you work.
Status information is used in the Project Status report.
1 In the Topic List pod, select topics.
2 Click the Properties button

3 Click the Status tab.
4 Set options as needed:
Status Click the triangle

to select a development stage.

Priority Enter a number.
Hours Enter a number to assign estimated or actual hours of topic development.
To Do list Select items as you complete them.
Comments Enter text.

More Help topics
“Generate and customize reports” on page 95

View and manage topic details in the Topics List pod
❖ In the Topic List pod, do any of the following:

• To view details about topics, choose View > Details View.
• To sort topics, click the column header.
• To select details to appear in the Topic List pod, right-click a column header, select More, and select the details.
• To view or update topic properties, select one or more topics and click the Properties button

• To create topic references, drag topics from the list to create a table of contents, index, and See Also keywords.

More Help topics
“Reports” on page 94

USING ROBOHELP HTML 8 115

Last updated 3/1/2010

Working with topics

Work with the Tag list
The Tag list in Design view shows the hierarchical structure of the HTML page. The top of the hierarchy is on the left
(always the document). The currently selected item is on the right.

• To display the Tag list, select View > Show > Tag list.
• To select an item in Design Editor, click the item in the Tag list.
• To edit the properties of an item in the Tag list, double-click the item. Set options.
Specify formatting attributes to remove:
Tag HTML tag that creates the specified format type.
Text Text to which the formatting is applied.
Class Class (style specified in the style sheet) used in the HTML tag. Not all tags have classes assigned.
Id ID (tag for JavaScript or Dynamic HTML) used in the HTML tag. Not all tags have IDs assigned.

Manage resources
You can manage resources from the Resource Manager pod.
1 Select View > Pods > Resource Manager.
2 Do any of the following:
Edit You can right-click a file to edit it in the associated editor.
Explore Right-click a folder and select Explore to open the folder in the Windows Explorer. You can right-click a

file and select Explore to open the parent folder of the file in Windows Explorer.
Rename Right-click a file to select Rename to rename a file or a folder.
Export Select Export from the right-click options of a file or folder to export to the selected folder in the Exports
dialog box.
Delete Select Delete from the right-click menu to delete a file or a folder.
Copy to the Project Files folder Copies the selected files to the project root folder.

Note: You must have the project open to copy the files to the project root folder.
Import Imports one or more files into the selected folder.

Note: Drag files and folders between Resource Manager and Windows Explorer. Drag images, style sheets, and topics
between Project Manager and Resource Manager. Drag snippets between the Snippets pod and Resource Manager. Drag
master pages between the Project Set-up pod and Resource Manager.

Add a category
You can add various categories in the root folder of the Resource Manager pod to manage different resources.
1 Select View > Pods > Resource Manager. Do one of the following:

• Click the Add/Edit Categories button

• Right-click in the blank area of the Resource Manager pod.
2 Click the browse button

and select the desired root folder.

USING ROBOHELP HTML 8 116

Last updated 3/1/2010

Working with topics

3 Click Open.
4 Click the Add Category button

5 Enter a name for the new category.
6 Click OK.
7 Click the Add File Type button

to add a file type for the selected category. For example, for an Images category,
you can define *.jpg, *.gif, *.png as file types.

Notes:
• You can add file types to an existing category.

• You can edit the file types in an existing category.
• You can click Reset To Default Settings to reset to the default view of the Resource Manager. All the user-defined
categories and file types still exist in the root folder.

Show or hide a category
1 Select View > Pods > Resource Manager. Do one of the following:

• Click the Show/Hide Categories button

in the Resource Manager pod.

• Right-click in the blank area below the displayed categories and select Show/Hide categories from the Resource
Manager pod.
2 Select or deselect the categories to show or hide in the Resource Manager pod.

Check spelling and find and replace
Note: If your project is localized, the spelling checker uses a dictionary in the selected language.

Check spelling in the TOC, index, see also list, or glossary
When the spelling checker finds an error, you can ignore the word, change it, or add it to the dictionary.
1 Open the component you want to check.
2 Select Tools, and then select Spell Check TOC, Index, See Also, or Glossary.
3 Select a suggested word or type a replacement in Not In Dictionary.
4 Select options.
5 To add a word to the custom dictionary, click Add.

Note: Online glossaries are available with WebHelp and Microsoft HTML Help.

Specify spelling options
❖ Select Tools > Spelling Options and select from the following sets of options:

Main Options
Check Spelling As You Type Checks for misspelled words as you type.

Last updated 3/1/2010

USING ROBOHELP HTML 8 117
Working with topics

Auto-Correct When Possible Corrects misspelled words as you type. To view a list of typically misspelled words, open
the Dictionary Editor dialog box.
Match Case Searches for uppercase or lowercase as indicated.

Note: The Auto-Correct When Possible and Match Case options do not work if you do not select the Check Spelling As
You Type option.
Special Options
Ignore All Uppercased Words Ignores all uppercase words.
Ignore Mixed Letters/Digits Ignores strings containing both letters and digits.
Ignore Doubles Ignores repeated words.
User Dictionary Lets you modify the existing dictionary.

Auto-correct spelling options
Auto-correction is possible only if you select the Auto-Correct When Possible option and the Check Spelling As You
Type option in the Spelling Options dialog box. (Select Tools > Spelling Options). You can define misspellings along
with the correct version. For example, you can add ”r;adn” as a misspelling and define the correct spelling as ”random.”
Note: Misspellings are not predefined; be sure to add them explicitly. This feature is Unicode-compliant. You can add
words in any language, including Russian and Japanese, in the same project, a topic, or a paragraph.
Replace Specify a misspelling in the Replace box.
With Specify the correct word in the With box.
Add Click to add the word to the Auto-Correct list.
Delete Click to delete the misspelled entries.
Cancel Cancels any changes made in the dialog box fields.
OK Click to save the changes made in the dialog box fields.

View Ignore Words list
❖ Select the Ignored Words tab. Use this dialog box to view the list of words ignored during spelling checks.
Ignored Words Lists words ignored during the spelling check.
Delete All Click to delete all words from the Ignored Words list.
Delete Click to delete the selected words from the Ignored Words list.

Check spelling in topics or projects
1 Open a topic in the Design Editor. Do one of the following:

• Select Tools > Spell Check.
• Select Tools > Spell Check All Topics. (Optional) Click Skip Topic.
• Select Tools > Spell Check Project. (Optional) Click Skip.
2 Select a suggested word or type a replacement in Not In Dictionary.
3 Select options as needed.
4 To add the word to the custom dictionary, click Add.

Last updated 3/1/2010

USING ROBOHELP HTML 8 118
Working with topics

Spelling check options for topics
Not In Dictionary Display the questionable word.
Suggestions Display a list of suggested spellings for the word.

If a word is not listed, enter the correct spelling in Not In Dictionary.
Add Add the word to the dictionary.
Ignore Skip the word and continue the spelling check.
Ignore All Add the word to the Ignore Word list.
Change Replace the word displayed in Not In Dictionary with the word selected in Suggestions.
Change All Replace all occurrences of the word displayed in Not in Dictionary with the word selected in Suggestions.
Close End the spelling check and close the dialog box.

Note: The Spell Check tool works for the language selected. If the selected language does not support the Spell Check tool,
the tool is disabled in the Tools menu.
Spelling check options for projects
Currently Checking Display the topic currently being checked.
Skip Skip the current topic.
Not In Dictionary Display the word not found in the dictionary.
Add Add the word to the dictionary.
Suggestions Show a list of words similar to the word not in the dictionary.
Ignore Ignore the word not found in the dictionary.
Ignore All Ignore all the suggestions for the selected word.
Change Replace the word under Not In Dictionary with the one in the Suggestions list.
Change All Change all the instances of the word.

Note: Words are added to the custom dictionary of the language the project is using.

More Help topics
“Authoring content in multiple languages” on page 45

Customize a dictionary
Use the Dictionary Editor to add words, for example, “RoboHelp,” to your dictionary. The dictionary is specific to the
language and the user. Every language has its own dictionary, and every user can save changes to the dictionary.
Note: The Dictionary Editor is case sensitive.
1 Select Tools > Spelling Options.
2 Click the Options tab.
3 Click Modify.
4 In the Dictionary Editor, under Word, type a new entry and click Add. To delete an entry, select it and click Delete.

Note: You cannot cancel additions or deletions made in the Dictionary Editor, so the Cancel button is disabled.

Last updated 3/1/2010

USING ROBOHELP HTML 8 119
Working with topics

Use the thesaurus
1 In the Design Editor, open a topic.
2 Select a word.
3 Select Tools > Thesaurus.
4 Select a synonym or antonym and click Replace.
Looked Up Display the word selected in the topic or type a word to look up.
Replace With Display a suggested replacement for the word.
Category Display the meaning of the word and its part of speech. If more than one category appears, select one to

see different synonyms.
Synonym Display words that are equivalent alternatives to the selected word. Select a word to replace the word you

looked up.
Replace Replace the current word with the new one.
Look Up Adds words in the Look Up pop-up menu.
Close Close the dialog box.

Find and replace text in a topic
1 Open a topic.
2 Select Edit > Find or Edit > Replace.
3 Type the text in the Find box.
4 (Optional) Set options. Use expressions to broaden or restrict search results.
5 Click Find or Find Next.
6 Click Replace or Replace All, or ignore the selection and click Find Next.

Windows expressions
? c?rd finds card and cord
* r*m finds ram and random
[ ] [cg]lass finds class and glass
[-] [c-g]lip finds clip and flip
@ ste@p finds step and steep

UNIX expressions
? sells? finds sell and sells
* co*p finds cop, coop, and cp; r.*m finds ram and random
[ ] [cg]lass finds class and glass
[-] [c-g]lip finds clip and flip
+ ste+p finds step and steep

Last updated 3/1/2010

USING ROBOHELP HTML 8 120
Working with topics

Find options
❖ Select Edit > Find.
Find Type a word or phrase to search for (the search string).
Find Next Search for the next occurrence.
Close End the search.
Allow Regular Expressions Recognize Microsoft Word-style or UNIX-style expressions.
Match Case Limit the search to strings that exactly match the case of the entered search string.
Direction Select the direction of the search.
Backward Search up from the current insertion point.
Forward Search down from the insertion point.

Find and replace options
❖ Select Edit > Replace.
Find What Search for this word or phrase.
Replace With Use this word or phrase as the replacement text.
Find Next Locate the first occurrence in the text.
Replace Replace selected text.
Replace All Replace all occurrences.
Close End the search.
Allow Regular Expressions Recognize MS Word-style or UNIX-style expressions.
Match Case Limit the search to strings that exactly match the case of the entered search string.
Direction Select the direction of the search.
Backward Search up from the current insertion point.
Forward Search down from the insertion point.

W3C compliance
You can validate XHTML or HTML topics for World Wide Web Consortium (W3C) compliance and view error
messages, informative messages, or warnings. You can validate the following for W3C compliance:
Topics Do one of the following:

• Right-click a topic in the Project Manager pod and select Validate W3C Compliance.
• Select any topic in Project Manager view and select File > W3C Compliance > Validate. RoboHelp validates the
selected topic and displays warnings or error messages in the Output View pod or the Error List pod.
Project Do one of the following:

• Right-click Project Files in the Project Manager pod and select Validate W3C Compliance.
• Select File > W3C Compliance > Validate All.

Last updated 3/1/2010

USING ROBOHELP HTML 8 121
Working with topics

RoboHelp validates all the HTML/XHTML topics and shows warnings or error messages for any non-compliance in
the Output View pod and Error List pod. RoboHelp displays errors, warnings, and information in different situations:

• Errors appear if you have added an incorrect tag or if you have not closed a tag.
• Warnings appear if a tag is not valid for XHTML.
• Information appears when all topics are validated.
Note: You can double-click an error or a warning message in the Error List pod to open it. When you place the cursor on
an error in the Error List pod, it shows the line of the topic where the error occurred.

Reference
General pane for Oracle projects
The General pane applies to the Topic Properties and New Topic dialog boxes in Oracle Help projects.
Use the General pane to create topic titles and filenames.
Topic Title Displays in the viewer, or when viewing topics by titles in the Project Manager.
File Name Name of the topic file (default is based on the title). Displays when viewing topics by filenames in the Project

Manager.
You can automatically save filenames using underscores, letting you synchronize the TOC book and pages in the
Contents tab with content in the viewing pane.
Template Displays or selects a template for a topic. Select None to use formatting from the default style sheet. To view

the displayed template, click the View button.
Editor (For Topic Properties) Shows the HTML editor for the project. Change this setting to use one other than the

RoboHelp Design Editor.
Note: Oracle Help uses topic IDs (in a map file) to make context-sensitive Help calls. You can change the ID by editing
the topic META tag.

More Help topics
“Add underscores to filenames” on page 112

Last updated 3/1/2010

Chapter 5: Editing and formatting
RoboHelp editors
RoboHelp provides two editors by default: Design Editor and HTML Editor. You can also use third-party editors to
edit their respective documents. For example, you can use Microsoft Word to edit a Word document linked to a
project.

RoboHelp Design Editor
When you select a topic file from the Project Manager pod, the topic opens in Design Editor. Use the RoboHelp Design
Editor to perform word-processing tasks and to insert online elements, such as links, multimedia, Dynamic HTML,
and See Also/Related Topics buttons. You can also add index keywords to topics, apply conditional text, create browse
sequences, map IDs, and edit master pages.
You can edit any standard XHTML or HTML file in Design Editor. (You can import stand-alone HTML files into a
project and edit them).
Note: To switch to HTML Editor from Design Editor, click the HTML tab.

RoboHelp HTML Editor
You can author topics in RoboHelp by writing XHTML code in the RoboHelp HTML Editor. RoboHelp HTML Editor
is a text editor for XHTML and HTML tags and text.

Open RoboHelp HTML Editor
1 Select a topic file from the Project Manager pod. The topic opens in Design Editor.
2 Click the HTML tab to view the HTML code for the topic.

Undo a change
❖ Click the Undo The Last Action button.

Note: If you switch views after making a change, you can’t undo the change.

View line numbers
❖ Right-click the body of the topic and select Line Numbers.

All code lines are numbered in the HTML Editor.

Add keyword expansions
Keyword expansions allow matching keywords to appear for text you type in the editor. The closest match is
highlighted. Click an entry in the list to insert it.
For example, suppose you add "RoboHelp" as an expansion. When you type "R", a list of keywords that begin with "R"
appears. When you type the next letter "o," the keyword "RoboHelp" is highlighted. Click it to insert it in the HTML
Editor. Text assigned to this keyword (for example, Adobe RoboHelp) appears in the HTML Editor.
Note: If the characters you enter do not have a matching keyword, the pop-up window disappears.

122

USING ROBOHELP HTML 8 123

Last updated 3/1/2010

Editing and formatting

You can add keyword expansions in the HTML Editor.
1 In the HTML Editor, right-click and select Edit Expansions.
2 Click New.
3 (Optional) Enter a new keyword in the Keyword box.
4 Enter a caption for the keyword in the Caption box.
5 Enter some text in the Text To Insert text area. This text appears when you select a keyword from the list in the

HTML Editor.
6 Click OK.

Change code color
You can change the color of code in the RoboHelp HTML Editor. However, the content text is always black.
1 In HTML view, right-click and select Colors.
2 In the Color Table dialog box, select an item and specify a color for the text, highlight, or both.
3 Click OK.

More Help topics
“Modify colors” on page 130

Third-party HTML editors
Using RoboHelp with other HTML editors
When using RoboHelp with a third-party HTML editor, note the following details:

• You can edit HTML in another editor while RoboHelp is open. When you open a topic in a third-party HTML
editor, RoboHelp functionality is not available. You can insert HTML code and elements, but you can’t insert or
edit RoboHelp features, such as text-only pop-ups or link controls.

• Close files in the third-party editor before opening them in RoboHelp.
• If you insert an image using a third-party editor, add the image to the project Baggage Files folder. The same is true
for JavaScript-based special effects with images, including accompanying .js files.

Add an HTML editor
For a list of detected HTML editors, select Tools > Options > Associations.
1 Select Tools > Options.
2 Click the Associations tab. Click Add in the HTML Editors area.
3 Do either of the following: Type the name of the HTML editor. Press Enter.

• Select an editor from the Recommended Programs or Other Programs folder. The Name and Location boxes
display the information for the selected program.

• Click the browse button

. Select the EXE file for the HTML editor and click Open. Type a name for the

editor.
Note: If you install a new HTML editor, you can’t add it until you restart RoboHelp.

Last updated 3/1/2010

USING ROBOHELP HTML 8 124
Editing and formatting

Remove or rename an HTML editor
1 Select Tools > Options.
2 Click the Associations tab.
3 Select an editor. Click Edit.

• To rename the editor, click Edit and type a name in the Name box.
• To remove the editor, click Remove.
Note: RoboHelp Design Editor, RoboHelp HTML Editor, and Windows Notepad cannot be changed or removed
from the list.

Auto-select an HTML editor or set a default
RoboHelp can automatically open a third-party HTML editor for you. RoboHelp detects the editor to open based on
the HTML file itself. The Auto Select option also lets you associate an editor with its own Meta/Generator tag to
automatically open topics with the editor that created them.
Note: To find out the editor associated with an installation of RoboHelp, select Tools > Options and check the default
editor setting on the Associations tab.
You can set a default HTML editor. The default editor is used for creating new topics, even if the auto-select feature is
enabled.
1 Select Tools > Options.
2 Click the Associations tab. Do one or more of the following.

• Select Use Default Editor. Click Set As Default.
• Select Auto Select Editor.
3 To change the associations between editor and tag, select Auto Select. You can change the HTML editor but not the

Generator tag. You cannot remove the tags either. Choose from these Generator tags:
<None> The editor associated with this tag is used for files with no Meta/Generator tag.
<Unknown> The editor associated with this tag is used for files with Meta/Generator tags not in the Associations
HTML Editors list.
<Robohelp> The editor associated with this tag is used for files created with all versions of RoboHelp.

Change the associations between editor and tag using the following options:
Add Associate an editor and a Meta/Generator tag.
Remove Remove an association between an editor and a Meta/Generator tag.
Set Editor Display the editors in the Associations tab. Change associations between editors and Meta/Generator tags.
Set Tag Modify associations between Meta/Generator tags and editors by typing a Meta/Generator tag in the field

or browsing to an HTML file that contains the Meta/Generator tag.
4 Click OK when you finish.

Notes:
• You can also use third-party HTML editors on a topic-by-topic basis, even if you set a default editor. Right-click
the topic in the Project Manager pod or the Topic List pod and select Edit With.

• All editors must be associated with a Meta/Generator tag.

USING ROBOHELP HTML 8 125

Last updated 3/1/2010

Editing and formatting

Specify an editor for new topics
Specify the default editor for new topics.
1 In the Project Manager pod, right-click a topic. Select New > Topic With.
2 Select an editor. Click OK. Click the General tab, and specify options.
3 Select Tools > Options. Click the Associations tab. Select Use Default Editor.

Character formatting and fonts
If you format characters using the toolbar or the Format > Font option, you create inline styles. Inline styles override
style sheets. For repeated use, create or modify a character style in a style sheet.

Apply or remove character formatting
❖ Select the text to format. Do one of the following:

• In the toolbar, click the tool for the formatting option.
• Choose Format > Font.

Apply color to text
1 Select text.
2 In the toolbar, click the arrow on the Change Font Color button

3 Click a color swatch, or click More Colors to select from additional swatches or to apply a custom color.

More Help topics
“Create styles for style sheets” on page 145

Define advanced font options
1 Select Format > Font.
2 Click Advanced.

You can define the following advanced options for fonts:
Style Specifies that the font is displayed in either normal, italic, or oblique
Weight Defines the font weight property (to make it appear lighter or darker). The bolder and lighter values are

relative to the inherited font weight, while the other values are absolute font weights. Not all fonts have all the possible
display weights.
Overline Inserts a line above the selected text.
Preview Shows a Design Editor representation of how your text looks with the selected font options. The view updates

as you apply different settings at the tab.

Last updated 3/1/2010

USING ROBOHELP HTML 8 126
Editing and formatting

Change character spacing
1 Select Format > Font.
2 Click the Spacing tab.
3 Select Normal, Expand, or Compress. Set options:
By (For Expand or Compress) Specify the amount of space between characters.
Position Specify a location for the text.

4 Click OK.

Change font size
1 Select the text.
2 In the toolbar, select a font size.

You can also change font sizes in navigation panes using the WebHelp Skin Editor.

Create a font set
A font set is a collection of fonts to apply in style sheets or character and paragraph formatting. For example, you can
create a font set with Verdana as the first font, and then (in order) Arial® and Sans Serif as substitute fonts. If users do
not have Verdana installed, the viewer uses Arial and then Sans Serif.
1 Select Format > Font Sets.
2 Click New, type a name, and click Modify. Select the first font, and click Add.

Note: Font sets are saved with projects.

Apply a font set to text
1 Open a topic in the Design view. Select the text to format.
2 Select a font.

Change font sets
1 Select Format > Font Sets.
2 Select a font.
3 Click Modify.
4 Add fonts from Available Typefaces or delete them from Font Set Selections.
5 Click OK.

Remove font sets
Note: Before removing a font set, reformat all text that uses that font set. If you don't, the font set you remove is re-created.
1 Select Format > Font Sets.
2 Select the font to remove.
3 Click Delete.

USING ROBOHELP HTML 8 127

Last updated 3/1/2010

Editing and formatting

Insert symbols and special characters
1 Open a topic in the Design Editor. Select a location for the character.
2 Select Insert > HTML > Symbol.
3 Double-click the symbol.

Insert a non-breaking space
❖ Place the insertion point where you want the non-breaking space. Press Ctrl+Alt+spacebar.

Format paragraphs
If you format a paragraph using the toolbar or the Format > Paragraph option, you create inline styles. Inline styles
override style sheets. For repeated use, create or modify a paragraph style in a style sheet.

Align paragraphs
1 Open a topic in the Design view. Select the paragraph to align.
2 From the toolbar, click an alignment button.

Indent paragraphs
1 Click in the paragraph.
2 Do one of the following:

• In the toolbar, click the Decrease Indent

or the Increase Indent button

in the toolbar.

• Select Format > Paragraph. Set indents:
• For a left or right margin indent, click Up or Down and select a number from the list.
• For a first line indent, click the triangle under Special and select First Line. Under By, click Up or Down and
select a number from the list.

• For a hanging indent, click the triangle under Special and select Hanging. Under By, click Up or Down and
select a number from the list.

Indent text lines
1 Select View > Show > Ruler.
2 In the Design Editor, insert your cursor where you want to create the indent or select the text you want to change.
3 On the ruler, do one of the following:

• To create a hanging indent, drag the lower marker where you want the indent to start.

Marker position for a hanging indent

• To create a first-line indent, drag the upper marker to the position where you want the text to start.

Last updated 3/1/2010

USING ROBOHELP HTML 8 128
Editing and formatting

Marker position for a first-line indent

Change margins
Follow this procedure if you want to change a single topic. Otherwise, use a style sheet.
1 Select View > Show > Ruler.
2 In the Design Editor, insert your cursor where you want to change the margins or select the text to change.
3 Drag the margin markers on the ruler.

Tips:
• In tables, apply margin settings to each cell as you move your cursor through the table.

• To specify exact margin measurements, select Format > Paragraph.
• To specify a margin setting that affects a certain style, modify your style sheet.
• Right-click the ruler to access the Snap To Tick Marks option. Select it and drag the markers on the ruler so they
align with the tick marks on the ruler. To move the markers in smaller increments, deselect Snap To Tick Marks.

More Help topics
“Create styles for style sheets” on page 145

Change the unit of measure for the ruler
1 Select View > Show > Ruler.
2 Right-click the ruler.
3 Select a unit of measure.

Define a language for a paragraph
Select a language for the paragraph. If no language is selected, the project language applies to the paragraph.
❖ Right-click and select Paragraph. Select a language from the Language menu.

More Help topics
“Support for multiple languages” on page 45

Apply text wrapping
1 In the Design Editor, double-click an object.
2 Under Text Wrapping, select an option.

Note: To use Around (For Tables), the table must be left- or right-aligned.
3 (Optional) To set spacing between the object and surrounding text, click Margins.

• Enter values for the amount of space between the selected object and the surrounding text.
• Set the spacing between text and object or by entering an amount in inches. Depending on whether you select
left or right text wrapping, you can enter the spacing for All Sides or Left/Right and Top/Bottom.

USING ROBOHELP HTML 8 129

Last updated 3/1/2010

Editing and formatting

4 Click OK.

Notes:
• Tables must be left- or right-aligned to use text wrapping, and they must be less than 100% in size.

• If text wrapping is applied around an image, the image cannot be aligned.

Adjust line spacing
1 Select Format > Paragraph.
2 Set Spacing options:
Before Specify the amount of space above each paragraph.
After Specify the amount of space after each paragraph.
At (for Multiple and Exactly) Enter the spacing (in points) between selected lines.

3 Click OK.

Add line breaks to paragraphs
A manual line break ends the current line and aligns the text on the next line.
1 Open the topic in the Design Editor. Click where you want the line break.
2 Press Shift + Enter.

Borders, backgrounds, color, and sound
Applying formatting without styles creates inline styles. Inline styles override style sheets.

Add or edit borders and backgrounds in topics
1 Open a topic. Select the topic or topic elements, such as paragraphs or table cells.
2 Select Format > Borders And Shading.
3 Click the Borders or Shading tab.
4 Specify border or shading options. Click OK.
5 Click the Save All button

More Help topics
“Add or edit borders or backgrounds in style sheets” on page 151

Add borders to images
1 In the Design Editor, double-click the image.
2 Click the Image tab. Click Borders.
3 Set border options.
4 Click OK.

USING ROBOHELP HTML 8 130

Last updated 3/1/2010

Editing and formatting

More Help topics
“Add or edit borders or backgrounds in style sheets” on page 151

Remove borders or backgrounds
1 Open a topic.
2 Select the item with the border or shading.
3 Do one or more of the following:

• In the toolbar, click the Border Type button
• In the toolbar, click the Fill Color button

and select the option for no border.
and select None.

• Select Format > Borders And Shading. Click the Borders or Shading tab. Set the border to None or the fill color
to Transparent. To remove a background image, remove the image name from the Image box in the Pattern area.

Add or delete horizontal lines
Add a horizontal line
You can insert a GIF image of a horizontal line or use the following procedures to add and change lines.
1 Open the topic in the Design view, and click where you want to add the line.
2 Select Insert > HTML > Horizontal Line.
3 Select line options.

• To change line length, enter a value in Width.
• To change line thickness, enter a value in Height. (The lower the number, the narrower the line.)
• To specify alignment, select a line position.
• To change line color, click Custom and select a color.
• To add margins, click Margins and choose options.
• To add a border, click Border and choose options.

Delete a horizontal line
Select the line and click the Delete button

Modify colors
1 Select Format > Colors.
2 Click New. Type a name for the color.
3 Click Modify. Do one or more of the following:

• Click a basic color swatch.
• Click the color spectrum box and the vertical color bar to adjust the amount of black and white in the color.
• Specify values for Hue, Saturation, and Luminosity. Enter values from 0 to 255.
• Specify values for Red, Green, and Blue. Enter values from 0 to 255.
• Drag the slider to adjust the luminosity.

Last updated 3/1/2010

USING ROBOHELP HTML 8 131
Editing and formatting

• Select Snap To Safe to change the selected color to the closest web-safe color.

Remove colors
Note: Before you remove a color, reformat any text using it.
1 Select Format > Colors.
2 Select the color to remove.
3 Click Delete.

Add sound to topics
1 From the Topic List pod, select one or more topics.
2 Click the Properties button.
3 Click the Appearance tab.
4 In the Background Sound box, enter the name of the sound file. The following formats are supported:
.au Used on UNIX systems. Supported by Microsoft Windows and HTML Help.
.mid, .rmi Musical Instrument Digital Interface. Standard for synthesized sound from electronic instruments.
.wav The native sound format for Windows.

5 In the Sound Loop Count box, enter the number of times to play the sound file.

Tables
About tables
In RoboHelp for HTML, you can create tables to organize complex data in a simplified format. You can organize
various elements in a table, segregate them using different colors, or draw patterns for easy identification of different
elements in a group.
Table styles allow you to choose different formats for tables. Styles can define header rows and columns, first or last
rows, repeatable groups of rows or columns, margins within cells, and so on. Using Table properties, you can set
margins in a table, define width and height of various cells and select different table styles. In addition to using the
predefined table styles in RoboHelp for HTML, you can create your own table styles to display for different kinds of
data. For example, you can have simple tables showing salary components or tables displaying the sum of salary
components, tax deductions including tax saving investments. You can have some global table styles, which can be
used across multiple topics.
You can import tables from FrameMaker and Word documents and map their table styles to RoboHelp table styles or
retain the original styles from other formats.
You can add text in tables. You can add cross-references, images, hypertext links to the content in a table. You can
apply conditional build tags to rows or columns to hide or show them in certain outputs. For example, you can have a
table describing features for each of the RoboHelp outputs. You can apply a conditional build tag on each column
listing the features for the specific output and display only if you generate that output.
Support for mini TOCs and breadcrumbs in Tables make them more useful for displaying content in an organized and
user-friendly fashion.

USING ROBOHELP HTML 8 132

Last updated 3/1/2010

Editing and formatting

Workflow for creating a table
1 Insert a table using the toolbar or the Table menu. Then select the number of rows and columns in the table grid.

See “Insert tables” on page 132.
2 Select a global style to apply on the table. You can also create your own table styles using the Format > Styles option.

Note: If you do not select a table style, a default table style is applied to the table.
See “Table styles” on page 146.
3 Change the table properties in the Table properties dialog box. You can set the margins, align cells in the table, and

apply shading and borders to the table.
See “Edit tables” on page 133.

Insert tables
You can insert a table anywhere in a topic or a master page, including headers and footers. You can also insert a table
within a table. You can apply different table properties to the inserted table to display complex data.

Insert a basic table
1 Click where you want the table.
2 Choose View > Toolbars > Tables And Borders.
3 In the toolbar, click the Insert Table button

4 On the table grid, drag to determine the columns and rows to add.
5 Click to insert the table.

Insert a custom table
1 Click where you want to add the table.
2 Select Table > Insert > Table.
3 Specify the number of rows and columns.
4 Select a table template, or select a custom style from CSS Styles.
5 Click OK.

To add a line below a table, click inside the lower-right cell of the table. When the cursor is blinking, press the Right
or Down Arrow. Press Enter to begin a new line.

Inserting tables within tables
When you insert a table within a table, the second table resides in a single cell within the first table. You can change
the table properties individually to differentiate the information.
The second table is 100% of the width of the cell in which you insert it. You can change this setting after you insert it.

Copy and paste tables
You can cut, copy, and paste tables.
1 Select the dotted outline around the table. Boxes around the table indicate that it is selected.
2 Right-click. Select Copy, or select Cut to move the table.
3 Right-click the destination. Select Paste.

Last updated 3/1/2010

USING ROBOHELP HTML 8 133
Editing and formatting

To add a line below a table, click inside the lower-right cell of the table. When the cursor is blinking, press the Right
or Down Arrow. Press Enter to begin a new line.

Edit tables
For a demonstration of table editing, see the Table manipulation section of the Easy ways to create and manage tables
and table styling video.

Insert table rows or columns
• Click in a table. Select Table > Insert > Row or Column.
• To insert multiple rows or columns, select multiple cells in the table. Select Table > Insert > Row or Column.
• Select rows or columns. Copy or cut the selection, and paste it at the new location.
• Remove tables or parts of a table. To remove a table, row, a column or a cell, select and right-click. Select Delete
[object].
Note: You can also cut, copy, and paste rows, columns, and cells within the same table or other tables.

Edit table properties
1 Click a table.
2 Select Table > Table Properties.
3 Set options.

Set autofit table properties
1 Click a table.
2 Select Table > Autofit.
3 Select a command:
Autofit To Contents Sets the column width to the width of the column contents.
Autofit To Window Sets the column width to the width of the table.
Fixed Column Width Sets the column width to a fixed size.

Edit cell properties
To edit cell properties, you can place your cursor inside the table and click Table > Table Properties > Cell tab.

• You can enter the amount of space between cells. If a CSS table style has the cell spacing set or row or column
formatting done, this option is not enabled in Table Properties > Cell.

• Select the vertical alignment of the text within an individual cell.
Note: Setting the alignment and cell spacing using the Cell tab applies to all cells in the table.

Edit spacing within cells
Define the amount of space between the cell contents and its inside edges. Add extra padding to prevent your tables
from looking crowded.
1 Select one or more cells to modify.
2 Click Format > Borders and Shading.
3 Click Borders tab. Click Padding.

Last updated 3/1/2010

USING ROBOHELP HTML 8 134
Editing and formatting

4 In the Top, Bottom, Left, and Right boxes, enter a value.
5 Click OK twice to apply changes.

Note: The Margins option sets the spacing around the table.

Merge or split table cells
1 Select the cells to merge or split.
2 Select Table > Merge Cells or Table > Split Cells.

You can split a cell into numerous rows and columns to create a table.

More Help topics
“Table styles” on page 146

Lists
Indent lists
❖ Select the list items to indent. Do one of the following:

• Click Decrease Indent and Increase Indent in the toolbar.
Note: You can also press Shift+Tab and Tab to decrease and increase indent.

• From the Format menu, select Paragraph. Type a number in Left or Right.
• (Multilevel list) On the ruler, drag the markers to set the spacing between the number or letter and the list item.

Apply bullet styles
Note: When you format lists using the toolbar or Format menu, inline styles are created. Style sheets aren’t affected.
Specify an inline bullet style
1 Open the topic in the Design Editor.
2 Select text.
3 From the Format menu, select Lists > Bullets And Numbering.
4 Do one of the following:

• Select a bullet style.
• To create a custom bullet, click Browse. Select a GIF file. Click OK. The file is added to Baggage Files.
Create a bullet style for a style sheet
1 Open the topic to customize a bullet style.
2 From the Format menu, select Styles.
3 In List, select All Styles.

USING ROBOHELP HTML 8 135

Last updated 3/1/2010

Editing and formatting

4 From Available In, select an external or embedded style sheet.
5 From the Styles list, select a style and click the Create New Style button

6 Under Style Type, select Paragraph Style.
7 Type a name for the new style. The name can contain letters and numbers only and cannot begin with a number.
8 Under Style For Following Paragraph, select (No Change).
9 Click Format and specify settings.

Match bullet color to text
Match color using an inline style
❖ Select the bulleted list and choose Format > Font.
The bullet and text color become inline instead of being associated with a style.
Match color using a style sheet
1 Place your cursor in the Design Editor, and select Format > Styles.
2 From the Style list, select the style sheet, and click the Create New Style button

3 Under Style Type, select Paragraph Style.
4 Type a name for the new style. The name can contain letters and numbers only and cannot begin with a number.
5 Under Style For Following Paragraph, select a style.

Paragraph styles apply to entire paragraphs and affect the font, spacing between lines, numbering, borders and
shading, and DHTML effects.
6 Select Format > Font.
7 Select a color.
8 Click OK twice.
9 Select the text that you want to format. Click Bulleted List.
10 From the Styles list, select the style you created.

Remove bullets and numbering
1 Select the bulleted or numbered list items.
2 From the Format menu, select List > Bullets And Numbering.
3 Click the option for no bullets.

You can also use the Create a Bulleted List, Create a Numbered List, and Create a Multilevel List buttons in the
toolbar to remove formatting.

Apply a numbering format
Note: When you format lists using the toolbar or the Format menu, inline styles are created. Style sheets aren’t affected.
1 Open the topic in the Design Editor.
2 Select the numbered list.
3 From the Format menu, select List > Bullets And Numbering.

Last updated 3/1/2010

USING ROBOHELP HTML 8 136
Editing and formatting

4 Click the Numbered tab. Select a numbering format.

Add a paragraph within a list
Use this procedure to insert paragraphs between numbered or bulleted items in a list.
1 Click at the end of the line to insert a paragraph over it.
2 Press Shift + Enter.
3 To end the line break and restart the numbering or bullets, press Enter.
4 (Optional) Drag the ruler at the top of the Design Editor to indent the paragraph.

Stop and start lists by clicking the Numbered List button in the toolbar.

Restart or continue numbering or lettering
After you insert a nested list, you can adjust numbering or lettering of the container list.
1 Click in the line where the new numbering or lettering sequence begins.
2 Select Format > List > Bullets And Numbering.
3 Select the Numbered tab.
4 In Restart Numbering At, enter the start number.

For an alphabetical list, type the numeric equivalent for the start letter. For example, type 4 for the letter D.
5 Click OK.

Headers and footers
You can create headers or footers in topics or master pages.
If you edit or remove headers/footers, topics and master pages are affected as follows:
In a topic The changes apply to the topic.
In a master page The changes apply to all topics associated with the template.
In a topic associated with a master page You can choose whether to apply the changes to the current topic or to the

master page and all associated topics.

Create or edit headers and footers
1 Open the topic or master page.
2 Select View > Header or Footer.
3 Type the content for the header or footer. Text-only pop-ups are not supported.
4 (Optional) To add or edit margins, borders, color, or an image, right-click in the header or footer, and select Header

Properties or Footer Properties.
Note: Any image file you select is added to the Baggage Files folder and is included in the project when you generate it.
5 Click outside the header or footer.

Last updated 3/1/2010

USING ROBOHELP HTML 8 137
Editing and formatting

6 Click the Save All button.

Remove headers and footers
1 Open the topic or master page containing the header or footer.
2 Click the Header button or the Footer button.
3 Right-click in the header or footer, and select Remove Header or Remove Footer.
4 Click the Save All button.

Text boxes
Insert text boxes in topics
Notes:
• Select Positioning from the View menu.

• Text can flow around a text box.
• If users have Internet Explorer 4.0 or later, you can apply Dynamic HTML effects to a paragraph by placing the
paragraph in a text box.
Insert a text box
1 Click where you want to insert the text box.
2 Select Insert > HTML > Text Box.
3 (Optional) Right-click the text box and click Text Box Properties. Modify the properties.
4 Click in the text box to enter text or insert an image or other element.

Insert a positioned text box
Precisely position information on the page, allowing other elements to flow behind the text box.
1 Select Insert > HTML > Positioned Text Box.
2 Select the positioned text box and drag it where you want it.
3 Right-click the positioned text box and select Positioned Text Box Properties. Adjust the properties.

Layer positioned text boxes
Layer positioned text boxes and specify their display order by applying Dynamic HTML (DHTML) effects.
1 Select the text box for the bottom layer.
2 Select View > Toolbars > Positioning.
3 From the Z menu, select 1.
4 Repeat for additional text boxes.

Last updated 3/1/2010

USING ROBOHELP HTML 8 138
Editing and formatting

Layered text boxes

Change text box properties
1 Right-click the text box. Select Text Box Properties or Positioned Text Box Properties.
2 Change the properties.

Remove text boxes from a topic
1 Select the text box.
2 In the toolbar, click the Delete button.

User-defined variables
User-defined variables store static global information that can be used repeatedly in your project, making information
portable and simple to update. When you modify a variable or value, every occurrence of that variable or value is
updated across the project. The User Defined Variables pod (available from View > Pods) lists all the user-defined
variables in a project. The user-defined variables exist in variable sets. In the User Defined Variables pod, you can
create different variable sets to override the values of variables in the Default Variable Set.
You can import documents with variables into a project.
Note: When you upgrade from previous versions of RoboHelp, variable values are converted to HTML text, and these
variable values appear in the Default Variable Set.

Create a user-defined variable
For global variables, ensure that all required variables exist.
1 Do one of the following:

• Select View > Pods > User Defined Variables.
• Select Insert > User Defined Variable.
• Right-click a word in the topic. Select Add To > User Defined Variable.
2 Enter a variable name and value.

Variable names can contain only alphanumeric characters, underscores, and hyphens, and can't exceed 255
characters. A variable value can be blank.

Last updated 3/1/2010

USING ROBOHELP HTML 8 139
Editing and formatting

3 Click OK. The variable is inserted.

Press Ctrl+F9, and then specify the variable name within the curly brackets that appear in the topic. Double-click the
variable to specify its value in the Variable dialog box.
Note: You can create variables only in the Default Variable Set, but you can modify the variable value in other variable sets.

Create a variable set
Variable sets enable you to modify values of various user-defined variables and use them in different outputs.
1 Click the Add/Edit Variable Set icon.
2 Click Add to add a new variable set.
3 Click OK.

Note: You can edit and delete a variable set in the Variable Set dialog box by clicking the respective buttons.

Edit a user-defined variable
1 In the User Defined Variables pod, select a user-defined variable from the Default Variable Set.
2 Do one of the following:

• Right-click and select Edit.
• Select and edit its value in the Design Editor.
• From the Edit menu, select Edit [variable name].
3 (Optional) Select a different variable set.
4 Modify the value.
5 Click OK.

Note: You can format a user-defined variable in the Design Editor included in the User Defined Variables pod.

Format a user-defined variable
You can format variable values in the Design Editor of the User Defined Variables pod. You can also achieve the
following using the Design Editor:

• Insert images, hypertext links, and multimedia files in the variable values.
• Apply conditional build tags to the values.
• Perform a spell-check on the variable values.

Insert user-defined variables
1 Place the insertion point at the desired location.
2 Select Insert > User Defined Variable.
3 Select a variable and click OK.

You can drag a user-defined variable from the User Defined Variable pod to the Design Editor.

Last updated 3/1/2010

USING ROBOHELP HTML 8 140
Editing and formatting

View properties of a user-defined variable
1 In the User Defined Variables pod, select Default Variable Set.
2 Select a variable.
3 Do one of the following:

• Right-click and select Properties.
• Select Edit > Properties.
4 View details (Variable Name, Variable Set, Variable Value, Used In Topics).
5 Click OK.

Delete user-defined variables
1 In the User Defined Variables pod, select Default Variable Set.
2 Right-click a user-defined variable, and select Delete.
3 Select one of the following options:
Delete Variable And Its References Delete the variable and its references across the topics, TOC, index, SSL, and
templates. No warning is shown before the deletion.

Note: Use the Variables report to locate the variables you want to remove.
Delete Only The Variable Delete the value of a variable locally. Deleting a user-defined variable in the TOC does
not remove it from the index.

Note: If the variable value is overridden in the Single Source layouts file, it is removed from the variable list in the
Single Source layouts dialog box.
Delete Variable And Replace With Actual Content Delete the variable across the topics, TOC, index, SSL, and

templates. The formatting rules for the variable remain the same.

Rename user-defined variables
When you rename a user-defined variable, all instances of the variable are updated across all the variable sets, the
topics, templates, TOC, index, and SSL.
Note: You can’t modify saved variable names.
1 Select View > Pods > User Defined Variables. The User Defined Variables pod appears.
2 Right-click a variable and select Rename.
3 In the Variable Name field, enter a name.
4 In the Variable Value field, modify the value.
5 Click OK.

USING ROBOHELP HTML 8 141

Last updated 3/1/2010

Editing and formatting

Single-source with snippets
A snippet is an element that you can single-source and reuse in various locations. It can be a paragraph of text, a code
listing, an object such as an image, or an entire topic unto itself. When you create a snippet, RoboHelp adds it to the
Snippet pod as a file with the .hts extension. If you change a snippet, it is automatically updated in all topics that share
it. Snippets can contain images, variables, and conditional text tags. When shared in a topic, they retain inline text
formatting. CSS formatting changes according to the CSS applied in the topic containing snippet.
The Snippet pod shows a preview of all the snippets on their individual selection. Right-click in the Snippet pod to
enable and disable Preview mode. Drag snippets from the pod to a topic or from Windows Explorer to the Snippet
pod. You can also select one or multiple snippets and then copy, duplicate, or delete them.
Note: You can generate reports on unused snippets and delete the snippets not in use.
You can drag and drop snippets from the Snippet pod to the Resource Manager to export them to the target folder.
The exported snippet exists at a global level and is visible to every user. Drag a snippet from the Resource Manager pod
to the Snippet pod and RoboHelp imports the selected snippet file and its associated files to the project.
Note: You can drag and drop a snippet in the Design Editor to edit its contents.

More Help topics
“Manage resources” on page 115

Create and manage snippets
• To create a snippet from scratch, select File > New > Snippet.
• To create a snippet from existing content, select text. Right-click and select Add To > Snippets.
• To view snippet properties, right-click the snippet in the Snippet pod. You can also see which topics share that
snippet.

• To copy a snippet, right-click a snippet in the Snippet pod and select Copy from the context menu.
• To import a snippet, select File > Import > Snippet and navigate to the source folder.
• To export a snippet, select it in the Snippet pod (or click

in the toolbar) and navigate to the destination folder.

• To insert a variable in a snippet, insert the pointer and drag a variable from the User Defined Variables pod.
• To preview a snippet, right-click a snippet in the Snippet pod and select Show Preview.

Insert a snippet in a topic
1 Open a topic.
2 Do one of the following:

• From the Object toolbar, click Insert Snippet

• From the Snippet pod, select a snippet and drag and drop it into the topic.
• Select Insert > Snippet. Select a snippet from the list in the dialog box and click OK.
Note: Right-click a snippet in the Resource Manager and select Add to Project to add the snippet to the project.

Insert a snippet in a drop-down text editor
1 Open a topic.

Last updated 3/1/2010

USING ROBOHELP HTML 8 142
Editing and formatting

2 Select some text to expand.
3 Select DHTML > Create Drop-down Hotspot And Text.
4 Drag a snippet from the Snippet pod and drop it in the Drop-down Text editor.

Note: You can preview the topic and click the DHTML applied text. The snippet appears in the drop-down text.

Applying conditional build tags to a snippet
Use the Conditional Build Tags pod or right-click to apply conditional text on an entire snippet or a part of it. The
preview option also lets you apply a conditional tag on selected text, code, or an image. You can exclude or include a
conditional build tag from the output.

Inserting variables in snippets
Choose a variable from the User Defined Variables pod or right-click in a topic and choose Insert User Defined
Variable. The snippet shows the variable value at the insertion point.

Reference
META tags default editor
Click Yes to make RoboHelp Design Editor the default editor for topics without META tags. Click No to retain the
current editor. The topic then opens in the selected editor.

143

Last updated 3/1/2010

Chapter 6: Styles and style sheets
Style types
You can manage style sheets at the project level and apply styles at the topic level. Master pages provide the layout of
a topic and help control the styling. These types of styles are available:
Inline styles A block of text and its formatting within an HTML file (topic) formatted directly in the Design Editor. If

you link the file to a style sheet, inline styles override styles in the style sheet and embedded styles.
Embedded styles Style definitions saved in an HTML file (topic). If you link the file to a style sheet, embedded styles

override the styles in the style sheet. You can create a character style or a paragraph style.
Styles in cascading style sheets (CSS) Style definitions stored in a CSS file. You can create a character style, a paragraph

style, a list style, a multilevel list style, and a table style.
After you convert a WinHelp project to an HTML-based project, styles are available as follows:
Project created from an HPJ file You can create styles that use the same formatting as styles in Word templates. These

styles are saved in style sheets that are attached to the HTML topics. If you do not want style sheets, translate the Word
formatting into inline styles in the HTML topics.
Project created from an HLP file Preformatted style sheets are available to apply to HTML topics. Topics are formatted

to use the default HTML styles.

More Help topics
“Master pages” on page 107

Manage style sheets
Link a style sheet to topics or master pages
You can associate one style sheet with any number of HTML topics, including a topic in Design view, multiple topics,
or a new topic.
If you create a style sheet in a project and apply it to a new topic, all topics you create later use the new style sheet. Link
a topic to another one, if necessary.
1 From the Topic List, select one or more topics.
2 Click the Properties icon

in the toolbar. Click the Appearance tab.

3 Select a style sheet. If needed, click the Browse button

to navigate to a style sheet, or click New to create a style

sheet.
4 (Optional) Edit the style sheet:
Edit Add, modify, or remove styles in the style sheet.
Background Sound Add a sound clip that plays when the topic opens in the viewer or browser.

USING ROBOHELP HTML 8 144

Last updated 3/1/2010

Styles and style sheets

Sound Loop Count Define the number of times the sound clip plays when the topic is opened. Select Infinite to play

the sound continuously while the topic is open.
5 Click OK.

Note: Use this same procedure to link a style sheet to a topic in Design Editor.

More Help topics
“Applying a master page or CSS at the time of generation” on page 110

Unlink a style sheet from topics or master pages
After you unlink a style sheet from a topic, the style sheet formatting is removed from the topic.
1 From the Topic List, select one or more topics.
2 Click the Properties icon

in the toolbar. Click the Appearance tab.

3 Select None in the list of style sheets, or click the browse button

to select a different style sheet to apply.

4 Click OK.

Create a style sheet
The new style sheet (default.css) is the default until you create a style sheet or link another style sheet to a new topic.
1 Click the Style Sheet button

. If necessary, select View > Toolbars > Formatting to view the toolbar.

2 Select New.
3 In Name, type a filename and include the .css extension.
4 In Folder, select a location.
5 (Optional) To base your new style sheet on an existing one, select Copy Styles From. Select a style sheet.
6 Click Create, create new styles, and click OK.

Create a style sheet and topic simultaneously
1 Select File > New > Topic. Click the Appearance tab.
2 Click New.
3 Enter a filename and include the .css extension.
4 Create or edit predefined styles in the Styles dialog box.
5 Click OK.

Export a style sheet
1 Select the Design Editor.
2 Select Format > Export Styles.
3 Browse to where you want to export the style sheet.

If necessary, rename the style sheet, keeping the .css filename extension.
Note: This feature is applicable only for styles applied in a topic and not at a project level.
4 Click Save.

USING ROBOHELP HTML 8 145

Last updated 3/1/2010

Styles and style sheets

Note: You can export topic-specific inline styles only.

Create styles for style sheets
Create a style in the Styles dialog box
1 In the Project Manager pod, right-click the style sheet where you want to create the style, and click Edit.
2 Click New and select a style type, for example, Paragraph style. By default, the new style is created with a default

name such as Style1.
3 In the Styles box, change the default name of the style. Do not use special characters or spaces in the name.

Note: If you use special characters, RoboHelp prompts you to fix the name. Some browsers cannot read styles with
names containing special characters.
4 Select options in the Formatting section of the Styles dialog box. Changes appear in the Paragraph Preview section.
5 (Optional) To set additional values, click Format, and select an option:
Font Select font families, size, and attributes, such as bold or italics.
Paragraph Set up indents, line spacing, and alignment.
Borders And Shading Use the Borders tab to set border types, color, line thickness, and spacing. Use the Shading
tab to set background color and image options.
DHTML Effects Select which dynamic HTML effect to include and when to include it.

Note: If you modify a style to include a Dynamic HTML effect, resave topics attached to the style sheet. Select Tools >
Update DHTML Effects In Topics. When you resave the files linked to the style sheet, topics authored in third-party
editors are converted to RoboHelp HTML. Special HTML tags are added to support specific Help features in the
program.

Create a style using the Styles And Formatting pod
1 To open the Styles And Formatting pod, open a topic and select Format > Styles.
2 Click the Create New Style button

in the Styles And Formatting toolbar, and select a style type, such as List Style.

3 Type the style name and click OK.
4 Select font and formatting options, and click OK.

More Help topics
“Styles And Formatting pod” on page 15

Create a style using the Design Editor
1 In the Design Editor, select some text in the topic.
2 Apply a format, such as bold.
3 With the text still highlighted, type a style name in the Style list in the toolbar and press Enter.
4 Click Create.

USING ROBOHELP HTML 8 146

Last updated 3/1/2010

Styles and style sheets

Table styles
With Style Editor, you can create and customize table styles according to your requirements. Applying a table style
instead of inline formatting helps you add standard and easy-to-maintain tables. If you modify a table style, all tables
using that style also change.
You can modify the appearance of existing tables by applying a style. RoboHelp asks you if you want to remove inline
formatting also.
For tips and workarounds related to customizing tables, see the Table section in Peter Grainge’s RoboHelp tour.

Global table styles
You can select predefined styles for a table. These styles are available globally and can be used across projects to define
different tables. Global table styles are present at C:\Documents and Settings\[user name]\Application
Data\Adobe\RoboHTML\[version]\Templates\Tables. For Windows Vista®, global table styles are present at
C:\users\[user name]\AppData\Roaming\Adobe\RoboHTML\[version]\Templates\Tables.
Note: If you delete the Tables folder from the suggested location, the global table styles are still visible in the Global Styles
list. You can always recover the styles from C:\Program Files\Adobe\Adobe RoboHelp
[version]\RoboHTML\Gallery\Tables.
In addition to the predefined global styles, you can copy table styles from a project folder and paste at C:\Documents
and Settings\[user name]\Application Data\Adobe\RoboHTML\[version]\Templates\Tables. These table styles are
available globally for all the projects.
Click the Apply Global Table Style

icon on the Tables And Borders toolbar to apply a style on the table.

Apply table styles
To apply a table style on an existing table, do the following:
1 Select an existing table in a topic.
2 Click the Apply Global Table Style icon

on the Tables And Borders toolbar to apply a style on the table.

3 In the Select Table Style dialog box, select Clean Table Inline Formatting. Selecting Clean Table Inline Formatting

removes any inline styles used in the table.
4 Select a style from the Available Styles list or select a global table style (table template).
5 Click OK.

Note: You can double-click a style in the Table Style dialog box to apply it to a table.

Create and manage table styles
Besides using global table styles (table templates) and predefined table styles in the CSS, you can create custom table
styles to ensure consistent table layouts, borders, alignment, shading, and fonts. You can vary characteristics such as
the colors, fonts, bold, italics, and alignments applied to rows and columns.
John Daigle demonstrates some easy ways to create and manage tables and table styling.

Create table styles
1 Select Format > Styles.

USING ROBOHELP HTML 8 147

Last updated 3/1/2010

Styles and style sheets

2 Click Create New Style and select Table Style.
3 Name the new table style and click OK.
4 Apply formatting to the whole table, first or last column or row, or a group of rows or columns. From the Apply

Formatting To list, select the columns or rows to format. For example, you can make the background of the first
row blue and the background of first column yellow.
5 Select font, size, and color.
6 Select border and border color.
7 Click Apply. The new style appears in the CSS Styles list of the Table Styles dialog box. Select this style to create

tables with the same style later.
Notes:
• Click the Apply Global Table Style icon

on the Tables And Borders toolbar to apply a style to the table.

• Based on the sequence of changes, in the first and last cell of a row, the row color overrides the column color.
The appearance of a table is the result of several classes, such as Table, TR, and TD. RoboHelp applies these subclasses
to the respective table item when you apply a table class. Therefore, if you want to change a table style through code or
script, write a class attribute (class=”myTableClass”) in the table tag. RoboHelp applies all the table patterns for the
remaining items of the table in Design Editor.

Apply conditional build tags to tables
Conditional build tags let you exclude content from output.
1 Select a row, column, table, or text in a table.
2 Select Format > Apply Conditional Build Tags > New/Multiple.
3 Select tags. Click OK.

List styles
About list styles
RoboHelp provides three types of lists: HTML lists, advanced lists, and autonumbered lists. Advanced lists can be
either single level or multilevel lists. You can define HTML list styling under List Styles and Advanced lists under
Multilevel List Styles. Define autonumbered lists under Paragraph Styles.
HTML lists All the ordered <ol> and unordered <ul> lists come under HTML lists.
Advanced lists Creates a hierarchical or outline list, such as numbered heading styles, with numbering such as 1, 1.1,

1.1.1, and so on. Like simple numbered lists, hierarchical numbered lists and the accompanying paragraph styles share
the same formatting. The multilevel lists set up complex nested steps, such as steps, step results, substeps, and so on.
Multilevel lists define only the numbering properties. Multilevel lists do not have their formatting until they are linked
to paragraph styles.
For an example of how to create a multilevel list based on a supplied style (list template), see the Outline Numbering
section in Peter Grainge's RoboHelp tour.
Autonumbered lists Autonumbered lists are linked to paragraph styles. To autonumber a paragraph, you can apply
autonumbering to it. To number figures or tables sequentially, define a simple numbered list format, such as Figure

Last updated 3/1/2010

USING ROBOHELP HTML 8 148
Styles and style sheets

Number or Table Number. In simple numbered lists, the paragraph style and numbering styles share the same font,
font size, font weight, and font color.
For a video introduction by John Daigle, see Easy ways to create lists and autonumbering on the Adobe RoboHelp 8
video tutorials page.

Create HTML lists
1 Right-click List Style in the Styles dialog box.
2 Click New.
3 Name the new list.
4 Select a font, font size, or a color for the new list style.
5 Click the Create A Numbered List button to create a numbered list or the Create A Bulleted List button to create a

bulleted list.
6 (Optional) Select other formatting options in the Formatting section of the Style editor.

Note: To edit a list style, select different formatting options in the Formatting section of the Style editor and preview them
in the Preview section.

Create multilevel lists
1 Do one of the following:

• On the Style And Formatting pod, click Create New Style, and select Multilevel List Style. Then type a name for
the new multilevel list, and click OK.

• Right-click a multilevel list style in the Style And Formatting pod, and select Edit.
2 Select a list level from the Apply Formatting To menu. List Preview displays the hierarchical order of the selected

level.
3 (For multilevel lists only) Select the paragraph style to apply to the current list level.
4 Select a predefined list style from the List Style pop-up menu, or click New to create a list style. For example, you

can have a sequenced list style such as Months, and you can have a sequence of all 12 months added to this sequence.
5 You can prefix a sequence or a multilevel list. To prefix a list style, enter text or numbers to prefix in the Edit Style

box. To specify the level to prefix, select the level from the Insert Level menu. You can add a prefix to the level in
the Edit Style box by separating the level and prefix with a separator such as a dot (.) or an angle bracket (>).
6 Apply formatting to the list style:

• Font, font size, color, highlight color, bold, italic, and underline
• List indention, space between list prefix, and accompanying paragraph text
For more information about the numbering behavior, indentation and margin control, or prefix formats, see this
article.

Create an autonumbering style
Autonumbering is linked to Paragraph styles. You can autonumber a paragraph style and apply it as a numbered list
style.
1 Do one of the following:

• Select a paragraph style in the Styles dialog box.

USING ROBOHELP HTML 8 149

Last updated 3/1/2010

Styles and style sheets

• Create a paragraph style.
2 Click the Autonumber button

3 (Optional) Select Inherit Numbering Property From Multilevel List to inherit the multilevel list style to apply

autonumbering. Select the multilevel list style from the List Class pop-up menu and select the level to apply
autonumbering. Click OK.
4 Enter a prefix for the new autonumbering style in the Format text box.
5 Select a predefined numbering option from the Numbering pop-up menu or select New to create a sequenced

autonumbering style.
For more detailed information, see this article.

Create a sequencing prefix
You can create custom sequencing prefixes to assign to Advanced lists.
1 In the Styles dialog box, click New.
2 In the Create/Edit Custom Sequence dialog box, click the plus sign to create a sequence.
3 Enter a unique sequence name such as Months and click OK.
4 Select the font for the sequence from the Sequence Font pop-up menu and click Add.
5 Click the Edit Sequence box and type the sequence that you want. For example, January, February, and so on. After

you enter January, click Add to add February, and so on.
For more information about custom sequencing, see this article.

Edit a sequencing prefix
1 In the Styles dialog box, click New.
2 Select the sequence from the Sequence pop-up menu, and do one of the following:

• To edit a sequence entry, select the entry in the Edit Sequence list, and click Edit. Make your edits in the Edit
Sequence box.

• To delete a sequence entry, select the entry in the Edit Sequence list, and click Delete.
• To reorder the sequence, delete entries and reenter them in the desired order.

Delete a custom sequence
1 In the Styles dialog box, click New.
2 Select the sequence. Click the plus sign.
3 Click Yes to confirm. Then click OK.

Apply styles
After you link a CSS file, an external style sheet, or embedded styles to a topic, you can apply styles.
1 In the Design view, do one of the following:

• Select the text to format.

Last updated 3/1/2010

USING ROBOHELP HTML 8 150
Styles and style sheets

• Click inside the paragraph to format. For multiple paragraphs, select the paragraphs.
2 In the Styles And Formatting pod, double-click a style.

• Character styles apply to selected blocks of text and impact fonts and DHTML effects.
• Paragraph styles apply to entire paragraphs and impact fonts, spacing between lines, numbering, borders and
shading, and DHTML effects.

• Table styles apply to the content in the tables.
• List styles apply to all numbering and bullet styles.
• Multilevel list styles apply to hierarchical lists.
To remove a character style, select the text and select a different style from the Style list. To remove a paragraph style,
select the style None.

Edit styles in CSS files
When you edit styles in a CSS file, all topics that are linked to the file are updated.
Important: You cannot use the Undo command to undo changes to a CSS file. Edit the CSS file to revert to a previous
style.

Edit a style using the Styles dialog box
1 In the Project Manager pod, right-click the CSS file. Click Edit.
2 Deselect Hide Inherited Styles.
3 From Available In, select a style sheet.
4 In the Styles box, select a style.
5 Click Format, and select the attributes.
6 (Optional) Select formatting options from the Formatting section.
7 Click OK.

Edit a style using the Styles And Formatting pod
1 Select a style in the Styles And Formatting pod.
2 Click Edit Selected Item.
3 In the Styles dialog box, select formatting options.
4 Click OK.

To prevent a user-defined color from displaying in the browser background, set the Background Text style to a white
background. This style is for normal topic text, such as headings and paragraphs. It controls the default settings for
background images, background colors, and borders.

Delete styles from style sheets
1 In the Project Manager pod, right-click the style sheet containing the style to remove, and click Edit.

Last updated 3/1/2010

USING ROBOHELP HTML 8 151
Styles and style sheets

2 If Hide Inherited Styles is selected, deselect it to see available styles.
3 From the Available In menu, select the style sheet name. For embedded styles, select the topic name.
4 From the Style menu, select the style to remove.

To delete custom formatting from a default style, select the style.
5 Click Delete.
6 Click Yes at the prompt.

Note: To remove a style from the style sheet or the Formatting toolbar, select None from the Styles menu.

Use color and images
Change text and link colors in a style sheet
RoboHelp incorporates changes you make to a CSS file into every topic the CSS file is linked to. You cannot undo
changes to a CSS file.
Using the WebHelp Skin Editor, you can change the color of text in the TOC, index, and Search panels for WebHelp
and WebHelp Pro.
1 In the Project Manager pod, right-click the CSS file. Select Edit.
2 Deselect Hide Inherited Styles.
3 From Available In, select a CSS file.
4 In the Styles box, select Character.
5 Expand Character Style, and select a link or text style from these options, among others:
Background + Text (Body) In the default style sheet, body text (normal text). This style is for text, tables, and

headings in topics. This style also controls the default settings for background images, background colors, and
borders.
Hyperlink (Unvisited) Hyperlink (Visited) Hyperlink (Active) The selected hypertext link.

6 Select Format > Font.
7 Under Font Color, select a color. Click OK.

More Help topics
“Create styles for style sheets” on page 145
“Skins” on page 311

Add or edit borders or backgrounds in style sheets
1 In the Project Manager pod, right-click the style sheet where you want to edit borders or backgrounds, and click

Edit.
2 Deselect Hide Inherited Styles.
3 From Available In, select a CSS file.
4 Under Other in the Styles box, select Background + Text (Body).
5 Select Format, and then select Borders And Shading.

USING ROBOHELP HTML 8 152

Last updated 3/1/2010

Styles and style sheets

6 Click the Border or Shading tab, define the borders or backgrounds, and click OK.

Note: Any image file used for borders or backgrounds is added to the project Baggage Files folder and is included in the
output you generate.

More Help topics
“Add or edit borders and backgrounds in topics” on page 129

Inline styles
Apply or edit inline styles
1 In the Design Editor, select the block of text to format.
2 Do one of the following:

• Select a formatting option from the toolbar.
• From the Format menu, select the desired formatting from the Font, Paragraph, Bullets And Numbering,
Borders And Shading, or Topic Borders And Shading options.

Remove inline styles from text
1 In the Design Editor, select the block of text with the inline style.
2 In the toolbar, click the options menu

Options menu

3 Select Default Paragraph Font.

next to the Styles box.

153

Last updated 3/1/2010

Chapter 7: TOCs, indexes, glossaries
TOCs
TOC basics
About TOCs
The table of contents is a hierarchy of the folders, topics, and any subfolders in the Project Manager. RoboHelp creates
books from custom folders and pages from the topics in these folders. Any topics not saved in custom folders appear
as pages at the first level in the table of contents.
You can reorder books and pages after you create the table of contents.

Create TOCs
Automatically create a table of contents based on the chapter layout defined in the Project Manager pod. If you
automatically create a table of contents, books and pages are sorted alphabetically.
1 In Project Manager, right-click the Table of Contents folder, and select New Table Of Contents.

If the project has many topics, collapse the Project Files folder first to view the Table Of Contents folder.
2 Specify a name for the TOC.
3 (Optional) Select Copy Existing Table of Contents and browse for an existing TOC file (.hhc) to create the TOC

from an available TOC.
4 Click OK. RoboHelp opens the Table Of Contents pod.
5 In the Table Of Contents pod, click the Auto-Create TOC button

6 Select an option in the Auto-Create TOC dialog box:
Delete Current TOC Before Creating New Removes books and pages before automatically creating the table of
contents. If this option is deselected, existing books and pages are included in the table of contents.
Create TOC Pages For Mid-Topic Links Creates pages in the table of contents based on bookmarks. RoboHelp
makes the topic that contains the bookmark into a book and all bookmarks into pages.

7 Click OK.

Note: In Microsoft HTML Help projects, you synchronize the table of contents in window properties. Folder names and
filenames, including those for topics, must use underscores rather than spaces.

More Help topics
“Reorder TOC books and pages” on page 155
“Define chapter layout” on page 25

Print TOCs
1 Click the Table Of Contents pod.
2 In the toolbar, click Print.

USING ROBOHELP HTML 8 154

Last updated 3/1/2010

TOCs, indexes, glossaries

3 From the pop-up menu, select the information to print.
Overview Print all book and page titles.
Detailed Print all book and page titles, the topic titles linked to each, and the folders in which the topics are located.

4 Click Properties or Page Setup to specify print options.

Create TOC books and pages
Version-control projects may have more options.

Create TOC books
1 Open the Table Of Contents pod by double-clicking the required TOC in Project Manager.
2 In the toolbar, click the New TOC Book button

3 In the Book Title box, type the name to appear in the table of contents.
4 Click OK.

Note: A book must include at least one page for it to appear in the output.

Create TOC books and pages with targeted links
You can link books and pages in a table of contents to content that you specify. When a user clicks a book or page icon,
the linked content appears in the Topic pane. You can link to topics, websites, and so on.
1 In the Table Of Contents pod, do one of the following:

• Click the New TOC Book button

. Select Book With Link.

• Click the New TOC Page button

2 Under Book (or Page) Destination, specify a destination:

• Select an item in the list. If needed, select from the pop-up menu and navigate to the item. You can link to items
in other projects.

• To create a topic, click New Topic. Type a title, change the filename if needed, and select a master page. Link a
book or page to it.
3 Click OK.

Create TOC books from pages
1 In the Table Of Contents pod, right-click a page.
2

Select Create Book From Page.

A book is created with the same title as the page. The page is placed inside the new book.

Create TOC pages by dragging
1 Open the Table Of Contents pod and the Topic List pod.
2 In the Topic List pod, select one or more topics.
3 Drag the topics into the Table Of Contents pod.

Note: Titles of topics dragged into the Table Of Contents pod are based on the topic titles. To rename a topic title, rightclick it and select Rename.

Last updated 3/1/2010

USING ROBOHELP HTML 8 155
TOCs, indexes, glossaries

Create TOC books and pages with user-defined variables
1 In the Table Of Contents pod, right-click and select New > Book or Page.
2 From the Available Variables menu, select a variable. Click Add. The variable is listed in the Page Title box.
3 (Optional) In the Page Title box, add a prefix or suffix to the variable. For example, add the prefix “Adobe” to the

variable “RoboHelp.”
4 From the Existing Topics list, select a topic for the new page.
5 Click OK. The book or page appears in the table of contents. Its title displays the user-defined variable with the text

you added.
To view or change the variable applied to a TOC item, right-click the item and select Properties.

Edit TOC books and pages
Rename TOC books and pages
Note: If you rename a TOC page, the topic title linked to the page isn’t affected. Similarly, if you change a topic title, the
name of the TOC page isn’t affected. Rename the TOC page separately, if desired.
1 In the Table Of Contents pod, right-click a book or page. Select Rename.
2 Type the new name. Press Enter.

You can also rename a book or page by changing its properties.

Reorder TOC books and pages
1 In the Table Of Contents pod, select a book or page.
2 Do one of the following:

• Drag the item to a different location.
• Click arrows in the toolbar to move the item.
Version-control projects may have more options.

Remove TOC books or pages
If you remove a page from the table of contents, the topic it links to is not deleted.
1 In the Table Of Contents pod, select a book or page icon.
2 In the toolbar, click the Delete button.

Version-control projects may have more options.

Change properties for TOC books or pages
Rename a book or page, or edit a destination, window frame, or custom icon.
1 In the Table Of Contents pod, right-click a book or page. Select Properties.
2 Make changes on the General and Advanced tabs.
3 Click OK.

Version-control projects may have more options.

Last updated 3/1/2010

USING ROBOHELP HTML 8 156
TOCs, indexes, glossaries

Manage TOCs
Manage TOCs with reports
RoboHelp provides several reports to help you manage tables of contents and resolve errors.
❖ Select Tools > Reports > [report name].

You can save, print, copy, and mail reports.
Table Of Contents report
This report displays the hierarchy of books and pages in a table of contents. You can view parts of a table of contents
by selecting a specific folder from the Folder list. If you change topic titles or filenames, you can compare them with
the titles used in the books and pages.
Choose from these report formats:
Detailed Includes titles of books and pages, names of topics that are linked to them, and names of folders in which

files are located.
Overview Includes titles of books and pages and names of topics linked to them.

Use this report as a project outline.

Topic Properties report
Customize this report to display any of these items:

• Topic titles
• Filenames
• Folder names
• Books and pages that reference topics
Topic Reference report
This report tracks references to the topics in a project, including books and pages in the table of contents that are
targeted to topics.
Unreferenced Topics report
This report tracks topics in a project that aren’t used in the table of contents, the index, or navigation components.
Broken Links report
This report displays the broken links in a project, grouped by file.

Identify and fix broken TOC links
If books or pages have broken links, they appear in the Table Of Contents pod with a red X.
1 Select Tools > Resolve Broken Links.
References To Selected Topic Shows all references to the missing topic. The Open Book icon

TOC references.
All Missing Topics Displays topics missing from the project.

2 To remove a TOC item, select it under References To Selected Topic, and click Delete.

indicates broken

USING ROBOHELP HTML 8 157

Last updated 3/1/2010

TOCs, indexes, glossaries

More Help topics
“Fix broken links” on page 185

Multiple TOCs
About multiple TOCs
You can create multiple tables of contents for a single project. You can use this feature for single-source publishing.
For example, you can create separate tables of contents for a project that contains multiple languages or outputs for
different audiences.
Note: To set a TOC as default, right-click a TOC in the Project Manager pod and select Set As Default.
If you merge subprojects into a master project, the tables of contents of the subprojects are available in the master
project.

Move books and pages to TOCs
1 In the Project Manager pod, double-click tables of contents in the Table Of Contents folder.
2 Drag books and pages from one Table Of Contents pod to another.

Create multiple TOCs for a project
1 Do one of the following:

• In the Project Manager pod, right-click the Table Of Contents folder. Select New Table Of Contents.
• Click the Create/View Table Of Contents button

. In the Select TOC dialog box, click New.

2 Type a name.
3 (Optional) Select Copy Existing Table Of Contents to base the new table of contents on an existing one. Click the

browse button

to locate the HHC file in the project folder, and select it.

4 Click OK.

By default, an empty table of contents with the same name as of the project appears in the Table Of Contents folder.
Note: Click the Auto-Create TOC button

, to automatically create a table of contents.

Merge TOCs
Follow this procedure to merge the tables of contents within a project.
1 In the Table Of Contents pod, select the book or page where you want to merge the table of contents.
2 Click the Insert TOC Placeholder button

. The Insert TOC Placeholder dialog box appears.

3 From the Select Table Of Contents menu, select the table of contents to merge.
4 Click OK.

When you generate a layout, select the merged table of contents from the list in the Layout screen of the wizard. The
selected table of contents appears in the output view of the Help.

More Help topics
“Merging Help projects” on page 34

Last updated 3/1/2010

USING ROBOHELP HTML 8 158
TOCs, indexes, glossaries

Create browse sequences from TOCs
You can use multiple tables of contents to generate browse sequences.
1 Select Tools > Browse Sequence Editor.
2 Click Auto-Create Using TOC.
3 In the text box, specify how many levels for each book to include in the sequence.
4 From the pop-up menu, select the table of contents for the browse sequence.
5 Click OK.

Indexes
Index basics
About indexes and keywords
You create an index by adding keywords and associating them with topics. You can spell check an index, and you can
use topic To Do lists to track your work while indexing. Change the capitalization of keywords in the Index pod.
An index can include multiple levels of keywords and cross-references to other keywords. Subkeywords can be listed
under a main keyword or in a Topics Found window. If a main keyword is linked to more than two topics, it needs
subkeywords.

Topic keywords
Topic keywords appear the same as index file (HHK) keywords, but they are stored within individual HTML topics.
The Index Designer identifies topic keywords with a key/page icon .
When working with topic keywords, consider the following details:

• When you import topics into a project, their keywords are added to the index.
• You can copy topic keywords to other topics and create index file keywords from them.
• You can use topic keywords with Keyword Link controls.
• If you remove a topic from a project, its keywords remain in the index in bold (indicating they are not linked to a
topic). The keywords don’t appear in the index until you link them to other topics.

• Topic keywords can link only to local HTML topics. The topic can appear only in the default Help window.
• Topic keywords cannot cross-reference (link to) other keywords in the index. Create the cross-reference using an
index file keyword.

• Topic keywords are sorted in the index in alphabetical order. You cannot reorder the keywords.
Additional details for HTML Help projects
• You can merge topic keywords from multiple CHM files into a master project.

• If you add index controls to topics, the index file (HHK) for the control displays only index file keywords.
Additional details for WinHelp projects
• When you convert a WinHelp project (HPJ) file to a RoboHelp project, the keywords in the WinHelp topics are
saved as keywords in the index file.

USING ROBOHELP HTML 8 159

Last updated 3/1/2010

TOCs, indexes, glossaries

Index file keywords
Index file keywords are saved in the project index file (HHK) rather than in the code of individual HTML topics. The
Index Designer identifies index file keywords with a key icon . You can create and maintain multiple indexes for a
project.
When working with index file keywords, consider the following details:

• You can use index file keywords with all supported output types and with Keyword Link controls.
• Index file keywords can cross-reference (link to) other index file keywords.
• Index file keywords can link to local HTML topics, multimedia files, baggage files, bookmarks, and URLs.
Depending on the Help format, a topic can appear in the default Help window, a custom window, or a frame.

• If you aren’t creating a binary index, and the project contains no topic keywords, you can sort the keywords in any
order.

• When you remove a topic from the project, index file keywords remain in the index if other topics use them. You
can remove or retain the keywords, regardless of whether other topics use them.

• You can merge index files with other projects. For HTML Help, binary indexes are required to merge projects.
Keywords in binary indexes are sorted alphabetically and cannot be reordered.

• If you import topics into a project, assign index file keywords separately. Index file keywords aren’t included with
topics, as are topic keywords.

• When you remove an index file keyword from an index, the keyword is also removed from topics that were assigned
to it.

• If you remove a topic from a project, and you don’t remove references to the index file keywords it uses, the
keywords are marked unused. (The exception is if other topics use them.) If these keywords aren’t used by other
keywords, the project includes broken links.

Specify keyword types for a project
A project can include index file keywords, topic keywords, or both. To specify the type to work with, change the project
settings.
1 Select File > Project Settings.
2 Click the General tab.
3 In Add New Keywords To, specify the keyword type.

• To add index file keywords, select Index File (HHK).
• To add topic keywords, select Topics.
4 Click OK.

New keywords use the type specified until you change the setting.
Notes:
• When you add a keyword to an index, it is automatically added to the index (HHK) or topic (HTM) files.

• Index file keywords use the key icon

. Topic keywords use the page icon

Print indexes
1 Click the Index pod.
2 From the pop-up menu, select the items to print.

USING ROBOHELP HTML 8 160

Last updated 3/1/2010

TOCs, indexes, glossaries

3 In the toolbar, click Print.
4 Click Properties and Page Setup to specify print options.

Use the Index report or the See Also report to print customizable keyword lists.

Add and link index keywords
• If you add the same keyword to an index using different capitalization, the Index Designer adds the keywords as
one entry, based on the first entry.

• If the index includes index file keywords and topic keywords that are identical, the keywords are merged when you
generate the project. In the Index tab, they appear as one keyword. (In the Index Designer, they appear as separate
keywords.)

• When you convert a WinHelp project (HPJ file) into a RoboHelp project (XPJ file), the keywords in the WinHelp
topics are saved as keywords in the index file.

More Help topics
“Create an index automatically” on page 164

Add index keywords using the toolbar
1 In the Index pod, do one of the following:

• To add a keyword, click the New Index Keyword button

• To add a subkeyword, select a parent keyword from the list. Click the New Index Subkeyword button

2 Type the keyword in the text box. Press Enter.

The keyword is added to the index. It appears in bold, indicating that it is not yet linked to topics.
To quickly add a keyword and subkeywords, skip step 1 and type the keyword and the subkeywords separated by
\ and click Add Keyword.
3 Select View > Pods > Topic List. The Topic List pod appears.
4 To link the keyword to topics, drag topics from the Topic List pod to the lower panel in the Index pod.

The linked keyword changes from bold to plain text.

Add index keywords based on a topic title
1 Open the Index pod.
2 Select View > Pods > Topic List.
3 In the Topic List pod, select a topic.

A question mark icon

indicates that a topic is not added to the index.

4 Drag the topic into the upper pane of the Index Designer.

The keyword name is based on the topic title. You can rename it.

Add index keywords using topic properties
1 In the Topic List or Project Manager pod, select a topic.
2 Click the Properties button

USING ROBOHELP HTML 8 161

Last updated 3/1/2010

TOCs, indexes, glossaries

3 In the Topic Properties dialog box, select the Index tab.
4 In the text box, type a keyword. To add a subkeyword, type the main keyword, a backslash, and the subkeyword.
5 Click Add.

Add index keywords by selecting topic text
1 Double-click a topic to open it in the Design view.
2 Select text to use as a keyword.
3 Right-click the text, and select Add To > Index Keyword > [index].

Copy index keywords
You can copy index keywords between topics. After copying, you can customize them to work with individual topics.
1 In the Topic List pod, right-click a topic and select the Properties button

2 Click the Index tab.
3 Click Add Existing.

On the left, a list of all keywords in the project appears. On the right, a list of all keywords for the current topic
appears. If the topic is not yet indexed, no keywords appear.
4 Copy the index keywords to the topic:

• To copy a single keyword, select it on the left and click the single arrow button.
• To copy all keywords, click the double arrow button.
5 Click OK. The keywords are linked to the topic.

To modify index keywords you copy, select a keyword. Enter text under Index Keywords. Click Replace.

Select an index keyword destination
You can link keywords to various destinations. When a user clicks the keyword, the destination opens in the topic pane.
1 In the Index pod, select a keyword.
2 Under Topics For, right-click a keyword topic.
3 Select Properties.
4 Under Existing Topics, specify a destination and click OK.

• Select an item in the list. If needed, select from the pop-up menu and navigate to the item. You can link to items
in other projects.

• To create a topic as an index keyword topic, click New Topic. Type a title, change the filename if needed, and
select a master page.

• To link to another type of destination, click the Link To pop-up menu and select a destination type. Type the
identifying URL, e-mail address, FTP address, or baggage filename for the destination type.
Notes:
• The Name and Link To fields are disabled when you specify topic keywords. With topic keywords, a keyword can
link only to the topic in which it is stored. It uses the topic title as the name.

• Find Topic locates a topic within the project to add an index keyword topic or modify its properties.

Last updated 3/1/2010

USING ROBOHELP HTML 8 162
TOCs, indexes, glossaries

Create index keywords with user-defined variables
User-defined variables let you create multiple versions of an index keyword.
1 In the Index pod, right-click a keyword. Select Properties.
2 From the Available Variables menu, select a variable. Click Add.

The variable is listed in the Index Keyword box.
3 (Optional) In the Index Keyword box, add a prefix or suffix to the variable. For example, add the prefix “Adobe” to

the variable “RoboHelp.”
4 From the Topics list, select a topic to link this new keyword to.
5 Click OK.

Cross-reference index keywords
You can cross-reference index keywords so that when users select the cross-referenced keyword in the index, an
alternate keyword appears. The user can select it to display the topic.
You can cross-reference only index file keywords.
1 In the Index pod, add a keyword to cross-reference. (This keyword links to the alternate keyword).
2 Right-click a keyword. Select Properties.
3 Select Cross-References. From the pop-up menu, select an alternate keyword.

The cross-reference appears in the lower panel of the Index Designer.
Version-control projects may have more options.

Edit index keywords
Move and sort index keywords
When you move an index keyword, its subkeywords are moved.
Topic keywords are automatically sorted first numerically and then alphabetically.
❖ In the Index pod, do any of the following:

• Select a keyword. Click an arrow button in the toolbar. A button is unavailable if the action isn’t allowed.
• Drag the keyword.
• Right-click a keyword. Select Sort > [sort option].
Note: The Sort command is unavailable with a binary index. The sort function is enabled only when the primary
layout is HTML Help and the Index is set to Index File with no Binary Index. In all other layouts, the index remains
sorted but for HTML output, the sorting of the index can be changed. Sorting enables the up and down keys on
Index Pod.
Version-control projects may have more options.

Rename keywords for a project
This procedure renames keywords in the index and topic keywords.
1 In the Index pod, right-click a keyword. Select Rename.
2 Type the new keyword in the text box.

USING ROBOHELP HTML 8 163

Last updated 3/1/2010

TOCs, indexes, glossaries

Rename keywords for a topic
To rename a topic keyword referenced by a specific topic, change the topic properties. If other topics use the same
keyword, the original keyword remains in the index. Only the topic you change is updated.
1 In the Topic List pod, select a topic.
2 Click the Properties button

3 Click the Index tab. Select a keyword.
4 Type the new keyword in the text box.
5 Click Replace.

Change the capitalization of a keyword
1 In the Index Designer, select a keyword.
2 On the Index Designer toolbar, click the Lowercase

or Uppercase

button.

Remove index keywords from the Index pod
If you remove a keyword from the Index pod, it’s removed from all topics that were linked to it.
1 In the Index pod, select a keyword.
2 In the toolbar, click Delete.

Unused keywords in the index are not referenced by other topics. They appear in bold in the Index pod. You can
automatically remove them.

Remove index keywords from topics
If you remove a keyword from a topic, only the topic you change is affected. Other topics that reference the keyword
are still linked to it.
1 In the Topic List pod, select a topic.
2 Click the Properties button

3 Click the Index tab.
4 Select a keyword from the list.
5 Click Delete.

Manage indexes
Manage indexes with reports
RoboHelp provides reports to use in managing indexes, such as the Index and Unused Index Keywords reports. The
Index report lets you choose options to define how the report displays information. You can display all the keywords,
a list of keywords with their related topics, or a list of topics and their related keywords.
The Unused Index Keywords report lists keywords that topics do not reference. These keywords reside in the index
file. Use this report to identify keywords to remove or to associate with topics.
You can save, copy, print, and mail reports.
1 Select Tools > Reports.
2 Select a report, such as Index, and view the results.

USING ROBOHELP HTML 8 164

Last updated 3/1/2010

TOCs, indexes, glossaries

3 Click Close.

Identify and fix broken references for keyword topics
1 In the Project Manager pod, open the Broken Links folder.

Missing topics are listed. They appear with a red X.
2 Right-click a missing topic. Select Properties.

Keywords that reference the missing topic appear with a key icon
in the Index pod.

. You can remove or relink the topic reference

Remove topic references from keywords
Note: If you remove all topics from the keyword, the Index pod displays the keyword in bold text to indicate that it is
unreferenced.
If you select a keyword in the Index pod, the lower panel displays all the topics that reference it. You can remove any
topic from this panel to remove the keyword from the topic. The name of the topic that is no longer in the project that
references the selected keyword is displayed. If you remove the topic from this panel, the broken link is removed and
the index file is updated.
1 In the Index pod, select a keyword.

The lower panel of the Index pod lists the topics that reference the keyword.
2 Select a topic. In the toolbar, click the Delete button

Remove unused index keywords
Unused keywords aren’t associated with topics. The Index pod displays unused index keywords in bold. Unused
keywords don’t appear in the index.
The index keeps unused keywords after you remove topics that reference them. This way, you can assign the keywords
to other topics without having to read them.
Note: This procedure doesn’t remove keywords that have one or more subkeywords.
❖ In the Index pod, select a keyword. In the toolbar, click the Delete button

Select Tools > Reports > Unused Index Keywords to identify unused keywords.

Apply conditional build tags to an index
1 In the Index pod, select a keyword.
2 Click Format > Apply Conditional Build Tag > New/Multiple.
3 Select tags or click Check All.
4 Click OK.

Automatic indexing with the Smart Index wizard
Create an index automatically
Use the Smart Index wizard to search the content of topics. Select from suggested keywords.

Last updated 3/1/2010

USING ROBOHELP HTML 8 165
TOCs, indexes, glossaries

Note: Close third-party files before running the Smart Index wizard.
1 Select Tools > Smart Index Wizard.
2 Select the search criteria.
Find New And Existing Index Keywords Add keywords based on topic content and existing index entries.
Add Existing Index Keywords To Topic(s) Search topics for keywords already used and link the keywords to the

topics.
Use Custom Search Settings Select Settings, and set custom search options. In the Smart Index Settings dialog box,
you can define an effective language to find index keywords. For example, if you define the project language as
French and the paragraph language is English, the Smart Index uses English dictionary to identify keywords for the
paragraph.

Note: This option is applicable for English language only.
In the Settings area of the Smart Index Settings dialog box, you can select options to include as keywords in the
index. For example, capitalize or mixed words, phrases, words in a phrase or words not in the dictionary.
In the Other Settings area, you can select options to exclude as keywords from the index. For example, select verbs
or adverbs to exclude and include adjectives or nouns as keywords.
3 Select items to search for index keywords.
4 To specify words or phrases to ignore, select Always Ignore or select Phrases. Edit, add, or delete entries.
5 To capitalize the first letter of the keyword, select Capitalize All New Index Keywords. (You can change the case

later in the Index pod.)
6 Click Next.
7 Select Confirm Adding Index Keywords For Each Topic.

To add keywords without confirmation, select Automatically Add Index Keywords For All Topics, and click Finish.
8 (Optional) Select filter options for the search.
Folder Search topics in a specified folder.
Status Search topics by status.
Check Only New Topics (That Have Not Been Smart Indexed) Search only non-indexed topics.

9 Click Next. Suggested keywords appear for the first topic.
10 Select, deselect, rename, or remove keywords.

To skip to the next topic, click Skip. Click Options to add verbs, synonyms, and existing index keywords.
Note: The Sentences Containing box shows the suggested keyword in the context where it is found. The Info field
indicates whether the selected keyword is new or existing.
11 Click Next, and click Close in the Results dialog box.

The new keywords appear in the Index pod.
Notes:
• You can change the case of keywords and subkeywords.

• You can link keywords to destinations other than topics.
• Index keywords are different from See Also keywords.

Last updated 3/1/2010

USING ROBOHELP HTML 8 166
TOCs, indexes, glossaries

Specify keywords to ignore
You can create a list of words or phrases that the Smart Index wizard ignores. This list is the Always Ignore list.
When the Smart Index wizard searches topics, it checks the Always Ignore list. If it finds an exact match, it ignores that
match as a potential keyword.
1 Select Tools > Smart Index Wizard.
2 Click Always Ignore.
3 Do one of the following:

• To add a word, click New and enter text.
• To edit a word, select it. Click Edit and enter text.
• To delete a word, select it. Click Delete.
The list is stored as a WLF file in the project folder.
Note: The words and phrases that you enter are not case sensitive unless they are uppercase words or mixed-case words.
In these instances, the Smart Index wizard must find an exact match before suggesting a new keyword.

Specify common words to ignore
You can create a list of common words (such as a) that the Smart Index wizard ignores. This list is the Stop list.
The Stop list can be only 512 characters long. Every word in the Stop list contains one added unseen character. If the
character limit is reached mid-word, the entire word is not compiled.
1 Select Tools > Smart Index Wizard.
2 Click Always Ignore.
3 Click the Stop List tab.
4 Do one of the following:

• To add a word, click New and enter text.
• To edit a word, select it. Click Edit and enter text.
• To delete a word, select it. Click Delete.
The list is stored as an STP file in the project folder.
Version-control projects may have more options.

Specify custom phrases
For greater control over the index keywords (words and phrases) suggested by the Smart Index wizard, create a custom
phrase list. This list of keywords is unique to the project. For example, you can include product names.
When the Smart Index wizard searches topics, it checks the phrase list. If it finds a match in a topic that is not a
keyword in the topic, it suggests the item as a keyword.
1 Select Tools > Smart Index Wizard.
2 Click Phrases.
3 Click New.

• To add a phrase, click New and enter text.
• To edit a phrase, select it. Click Edit and enter text.
• To delete a phrase, select it. Click Delete.

USING ROBOHELP HTML 8 167

Last updated 3/1/2010

TOCs, indexes, glossaries

The list is stored as a PHR file in the project folder. You can edit this file in a text editor, such as Windows Notepad.
Note: The words and phrases that you enter are not case sensitive unless they are uppercase words or mixed-case words.
In these instances, the Smart Index wizard must find an exact match before suggesting a new keyword.

Look up synonyms for indexing
Note: This option is available only in English.
1 Select Tools > Smart Index Wizard.
2 Click Next twice.
3 Select a keyword.
4 Click Options. Select Synonyms.

The keyword appears in the Word box.
5 (Optional) Click Antonyms to see antonyms for the keyword.
6 Under Categories, select the best match for the word.
7 Under Synonyms, select a word to add as a keyword. Click Add To Topic.
8 Click Close.

To view synonyms and antonyms for additional words, type in the Word box and click Look Up.
Version-control projects may have more options.

Multiple indexes
Create multiple indexes
You can create multiple indexes in the same project. New indexes are added to the Index folder. With multiple indexes,
you can right-click any index and select Set As Default to set the index as default index. You can right-click an index
and select Rename to rename the index as well.
You can copy and drag keywords across multiple indexes.
1 Do one of the following:

• In the Project Manager pod, right-click the Index folder. Select New Index.
• Click the Create/View Index File button

. Click New.

2 Type a name in the text box.
3 (Optional) To copy an existing index, select Copy Existing Index. Click the browse button

index.
4 Click OK.

Merge indexes
Follow this procedure to merge the indexes within a project.
1 In the Project Manager pod, open the Index folder.
2 Double-click an index.
3 In the Index pod, select a keyword where you want to insert the merged index.

to navigate to the

USING ROBOHELP HTML 8 168

Last updated 3/1/2010

TOCs, indexes, glossaries

4 Click the Insert Index Placeholder button

5 From the Select Index menu, select the index to insert.
6 Click OK.

The merged index appears with the New Index icon

7 Double-click the icon, and click View.

The merged index appears in the Index pod.

More Help topics
“Automatic indexing with the Smart Index wizard” on page 164
“Create binary indexes (HTML Help)” on page 169
“TOCs and indexes in Microsoft HTML Help” on page 168
“Merging Help projects” on page 34

TOCs and indexes in Microsoft HTML Help
Assign custom TOC icons (HTML Help)
1 In the Table Of Contents pod, right-click a book or page. Select Properties.
2 Click the Advanced tab.

Under Image, Auto indicates that the book or page uses the standard icon.
3 From the pop-up menu, select an icon.

You can assign other icons to books and pages after you add the bitmap file (BMP) to your project.
4 (Optional) Select Mark As New to display the standard icon with a red star. The star indicates to users that the TOC

item contains new information.
5 Click OK.

Version-control projects may have more options.
Note: The Table Of Contents pod displays all books and pages with the standard icons regardless of the selection you make
at the Advanced tab. After you generate the project, you can view icons in the Contents pane.

Create binary contents files (HTML Help)
Use binary contents files for large projects to reduce opening time.
Important: Do not merge projects that use binary contents files.
1 In the Project Manager pod, double-click a table of contents in the Table Of Contents folder. The Table Of Contents

pod appears.
2 Select View > Pods > Single Source Layouts.
3 Expand the Single Source Layouts folder.
4 Right-click a layout. Select Properties.
5 Click Edit.

USING ROBOHELP HTML 8 169

Last updated 3/1/2010

TOCs, indexes, glossaries

6 Click the TOC Styles tab.
7 Select Binary TOC.
8 Click OK.
9 Generate the project.

Version-control projects may have more options.

Create binary indexes (HTML Help)
Microsoft HTML Help projects require binary indexes in certain cases:

• When projects have topic keywords. Topic keywords are saved in the HTML files that reference them.
• When HTML projects are merged. When you merge projects, each CHM file remains in its own project, but
keywords from each index file are combined into the master project. Distribute each CHM file along with the
master CHM file.
1 Make sure that Microsoft HTML Help is the primary layout.
2 Select File > Project Settings.
3 In the General tab, select Binary Index.
4 Click OK.
5 Add topic keywords (marked with a key icon

6 Merge subprojects if needed.
7 Generate and view the project.

Version-control projects may have more options.

More Help topics
“Merging Help projects” on page 34
“Generate, view, and publish output” on page 274

Customize a TOC (HTML Help)
Select a custom font for displaying book and page titles, and synchronize books and pages with topic content. Use
raised or sunken edges to give a three-dimensional look.
1 In the Single Source Layouts pod, right-click a layout for HTML Help output.
2 Select Properties.
3 Click Edit next to Advanced Settings.
4 Click the TOC Styles tab.
5 Set style options:
Border Add a border around the table of contents.
Dialog Frame Add a frame around the table of contents.
Plus/Minus Squares Display plus and minus icons that open and close books.
Always Show Selection Display the topic selected from the Contents tab (even if this tab is not the left-pane focus).
Folders Instead Of Books Display folder icons instead of book icons.

Last updated 3/1/2010

USING ROBOHELP HTML 8 170
TOCs, indexes, glossaries

Single-Click To Open Book Enable books to open with one click.
Raised Edge or Sunken Edge Create a three-dimensional appearance.
Lines Between Items Add lines between books and pages.
Lines From Root Displays lines connecting books and pages starting at root.

6 Specify a font.
7 Set window, frame, and other options:

• To display the topic in a custom window, select the window name from Default Window.
• To display the topic in a custom frame, select the frameset name from Default Frame.
• To use custom book and page icons, select a BMP file from Custom Image File. Make sure that you include the
image path, such as C:\Program Files\Adobe RoboHelp [version]\My.bmp.
Note: For custom book and page icons, create an icon strip. See the MSDN Library on the Microsoft website.
8 Click OK.

Version-control projects may have more options.
Note: The binary TOC option is recommended only for large Help systems. It requires compiled HTML Help and doesn’t
support customization or external TOC files.

Customize an index (HTML Help)
The index type for the HTML Help project determines the index properties:
Index file keywords For index file keywords in non-binary indexes, you can customize the keyword fonts. Click the

Index tab in the HTML Help viewer.
Merged indexes If merging indexes from CHM files, select the Binary Index option.
Topic keywords If your index includes topic keywords, create a binary index.

1 In the Single Source Layouts pod, right-click a layout for HTML Help output.
2 Select Properties.
3 Click Edit.
4 Click the Index tab. Set properties:
Default Window Select the custom window to display topics. Custom windows can link only to index file keywords.
Default Frame Select a custom frame to display topics. Custom frames can link only to index file keywords.
Select Font Select a font name and size.

Version-control projects may have more options.

Add TOC controls (HTML Help)
When a user opens a topic, the table of contents appears.
If a topic is in a subfolder, copy the contents of the file into the subfolder before adding the control.
1 Open a topic in the Design view.
2 Click where you want to add the table of contents.
3 Select Insert > HTML Help Controls > Table Of Contents. The Contents control appears in the Design Editor.

Last updated 3/1/2010

USING ROBOHELP HTML 8 171
TOCs, indexes, glossaries

4 To test the control, generate the project. The Table Of Contents control displays the same table of contents as in the

final output.
Version-control projects may have more options.
You can link other contents files in your project. Copy the HHC file into the project if you want to select the HHC file
with the TOC control.

Add index controls (HTML Help)
If your project does not support a tri-pane design, you can add an index control to a topic to make the index file
available. The index appears when the topic is opened with the index control.
1 If the topic is in a subfolder, copy the index file (HHK) to the subfolder.
2 In the Design Editor, open the topic with the control.
3 Click where you want to add the index.
4 Select Insert > HTML Help Controls > Index.

The index control appears.
To test the index control, compile the project. The index control displays the same index as in the final output.
Version-control projects may have more options.
You can use other index files in your project. Copy the HHK file and associated files (topics, images, multimedia) to
select the HHK file with the index control.

Link keywords and TOC items to custom windows and frames (HTML Help)
Custom windows can display context-sensitive Help and links from index keywords, TOC books, and TOC pages.
1 Create a custom window or frame.
2 Do one of the following:

• In the Table Of Contents pod, right-click a book or page. Select Properties.
• In the Index pod, right-click an index file keyword. Select Properties.
3 Click the Advanced tab.
4 From the Window pop-up menu, select a custom window.
5 From the Frame pop-up menu, select a custom frame.
6 Click OK.

Version-control projects may have more options.
Note: Microsoft HTML Help doesn’t support links to custom windows from the topic, only links to pop-ups.

More Help topics
“Link to a pop-up” on page 180
“Automatic indexing with the Smart Index wizard” on page 164

USING ROBOHELP HTML 8 172

Last updated 3/1/2010

TOCs, indexes, glossaries

Glossaries
Create glossary terms
1 In the Project Manager pod, double-click a glossary in the Glossary folder.
2 In the Glossary pod, type a term in the Term box.
3 Click the Add Term button (plus sign) or press Enter.

The term appears in bold, indicating that it doesn’t have a definition.
4 In the Definition For panel, type a definition.

You cannot use formatted text, tabs, or returns.
For terms and definitions to appear within topics, add expanding glossary hotspots.
5 If needed, enable the Glossary tab in the single-source layout wizard so that it appears in the output. Add at least

one term and its definition to enable the glossary checkbox in the single-source layout wizard.
Note: (Microsoft HTML Help) When you distribute the final output, include an HHActiveX.DLL file with the CHM file.
This DLL file is the ActiveX® control that supports online glossaries. This file must be copied to and registered on end-user
Windows systems.

Import glossary terms and definitions
Before importing a glossary file (GLO), print a detailed report of both glossaries. The reports can help you determine
which terms exist in both glossaries and compare definitions.
1 In the Project Manager pod, select a glossary in the Glossary folder.
2 Select File > Import > Glossary.
3 Click the browse button

to navigate to a GLO file.

4 Do one or more of the following:

• For definitions in the external glossary to overwrite matching terms, select Replace Existing Glossary
Definitions.

• Select one or more terms in the Terms In Imported Glossary list. Click Add.
• To import all terms, click Add All

5 Click OK.

Test and print glossaries
Test the glossary in the output
1 Make sure that the Glossary pod is enabled.
2 Generate a layout.
3 Click View Result.
4 Click Glossary.

USING ROBOHELP HTML 8 173

Last updated 3/1/2010

TOCs, indexes, glossaries

5 Select terms and view their definitions.

Print a glossary
1 Click the Glossary pod.
2 In the toolbar, click Print.
3 From the pop-up menu, select the information to print.
Overview Print all terms.
Detailed Print all terms and definitions.

4 Click Properties and Page Setup to specify print options.
5 Click OK.

Remove terms from the glossary
Removing terms doesn’t remove expanding glossary hotspots. Remove hotspots separately.
1 In the Project Manager pod, double-click a glossary in the Glossary folder.
2 In the Glossary pod, select a term from the list.
3 In the toolbar, click Delete.

More Help topics
“Glossary hotspots” on page 174

Change glossary definitions
Note: If you change a definition that is used as an expanding glossary hotspot, update the project by running the Glossary
Hotspot wizard.
1 In the Glossary pod, select the term to change.
2 Edit the definition text.

Create multiple glossaries
You can create multiple glossaries in the same project. New glossaries are added to the Glossary folder.
You can copy and drag terms across multiple glossaries.
Note: You cannot delete the default glossary.
1 Do one of the following:

• In the Project Manager pod, right-click the Glossary folder. Select New Glossary.
• Click the Create/View Glossary File button

. Click New.

2 Type a name in the text box.
3 (Optional) To copy an existing glossary, select Copy Existing Glossary. Click the browse button

to navigate to

the glossary.
Click the Start Glossary Hotspot Wizard button

in the toolbar to mark existing glossary terms in topics.

USING ROBOHELP HTML 8 174

Last updated 3/1/2010

TOCs, indexes, glossaries

Merge glossaries
1

In the Project Manager pod, open the Glossary folder.

2 Double-click a glossary.
3 Click the Import Glossary button
4 Click the folder button

. Select the glossary to merge. Click Open.

5 If needed, deselect Replace Existing Glossary Definitions.

Select this option to replace existing definitions in the glossary with definitions from the merged glossary.
6 Select terms from the imported glossary list. Click the single right arrow to merge them. Click the double right

arrow to merge all terms.
Note: Select terms in the current project list and click the Left Arrows to deselect terms selected for merging.
7 Click OK.

The merged glossary terms appear in the Glossary pod.

More Help topics
“Glossary hotspots” on page 174

Glossary hotspots
About expanding glossary hotspots
The Glossary Hotspot wizard finds glossary terms within topics and marks them in the topics. You can mark all terms
to convert to expanding hotspot when you generate or preview output.
Notes:
• Expanding glossary hotspots require Internet Explorer 4.0 or later. If they are used in a style, they require Internet
Explorer 5.0 or later. Netscape Navigator doesn’t support expanding glossary hotspots.

• The Glossary panel is not supported in Oracle Help. Definitions appear inline instead of in a hotspot.
• The glossary appears in the printed documentation and appears at the end of the page.
• Control the hotspot appearance by modifying the glossary term and character style in the Styles editor (accessible
from the Stylesheets button in the Product Manager pod).

Add expanding glossary hotspots
❖ Do one of the following:

• Drag a term from the Glossary pod into a topic.
Use this method if the term doesn’t occur in the topic, or if the term isn’t in an ideal place to expand.

• In the Glossary pod, click the Glossary Hotspot Wizard button

The Glossary Hotspot wizard finds glossary terms within topics and marks them in the topics. You can mark all
terms to convert to expanding hotspot when you generate or preview output.

Last updated 3/1/2010

USING ROBOHELP HTML 8 175
TOCs, indexes, glossaries

Preview a hotspot by double-clicking it in the Design Editor.

Update expanding glossary hotspots
The Glossary Hotspot wizard inserts markers for the terms defined in the selected glossary. It doesn’t insert definitions
for terms in the topic. When you generate a preview or output, RoboHelp adds definitions for the terms. As a result,
topics always have the updated definitions for marked terms.
1 Click Tools > Glossary Hotspot Wizard.
2 Select options. In the Select Term menu, select an individual term or all terms.
Confirm Marking Terms For Each Topic Select to choose which terms in topics are marked to expand as glossary

hotspots.
Automatically Mark Terms For All Topics Tell the Glossary Hotspot wizard to mark all glossary terms it finds in

topics to expand to glossary hotspots.
Case-Sensitive Makes search case sensitive.
Mark Only The First Instance Of Term In Topic And Unmark Subsequent Instances Select this option to turn the first

marked instance of a term into an expanding glossary hotspot when you preview or generate output.
3 Click Next.

Select a term to mark in a chapter.
4 To assign the new definition to the term, select the box next to the term that does not match.
5 Click Next. Repeat steps for each topic that the Glossary Hotspot wizard displays.
6 Click Finish.

Test expanding glossary hotspots
1 In the Topic List pod, right-click the topic containing the hotspot.
2 Click View.
3 Click the glossary term in the topic.
4 Click the term again to close the hotspot.

Unmarking expanding glossary hotspots
Unmark hotspots using the Glossary Hotspot wizard
1 Select Tools > Glossary Hotspot Wizard.
2 Select Confirm Adding Definitions For Each Topic.
3 Select a folder and status to search.
4 From the Select Term menu, select the term to remove.
5 Click Next.
6 As each topic appears, deselect the check boxes to remove expanding glossary hotspots.
7 Click Finish.

Last updated 3/1/2010

USING ROBOHELP HTML 8 176
TOCs, indexes, glossaries

Unmark hotspots in Design view
1 Open the topic in the Design view. Select the term.
2 Right-click and select Remove Expanding Text.

You can click the definitions of marked glossary terms in the Glossary Definition Viewer but you cannot edit the term
definition.
Note: When you upgrade a glossary from an older version, all the local changes are lost.

Last updated 3/1/2010

Chapter 8: Linking and navigation
Navigation basics
Navigation options
The following navigation options are available for use in Help projects.
Hypertext links Open the link destination.
Pop-ups Display an HTML topic in a pop-up window rather than in the default viewer. Pop-ups can be linked only to
another HTML topic or to bookmarks.
Link controls Clickable objects that open a list of related topics. Types of link controls are See Also, Related Topics, or

Keyword Links.
Breadcrumbs These links appear on a Help page and outline the position of the page in the table of contents, or the

directory structure of the project.
Browse sequences The sequence of a series of topics. You define the order of topics in the sequence.
Searches Find topics that contain search keywords. The search results appear as links in the Search tab of the

navigation pane. The search keywords are highlighted in the topic pane.
In-topic navigation bars Navigation bars added to a layout using WebHelp as the output type.
Expanding hotspots, drop-down hotspots, and twisties Text links that expand to display additional information, but
not other topics. These hotspots are available in browsers that support Dynamic HTML (DHTML).
Text-only pop-up A window that displays only text, not topics or web pages. Text-only pop-ups are useful for

definitions or details. Unlike regular pop-ups, a text-only pop-up resides in the topic that contains it. It’s not a separate
topic.
Image maps An image in an HTML topic that contains graphical links to other topics. Clickable areas in the image are

hotspots.
Image links A link in an image that takes users to a destination or opens a pop-up. Creating image links is like creating

text links.
Bookmarks A link that takes users to a specific place in a topic.
WinHelp topic control (Microsoft HTML Help only) A clickable object that opens a WinHelp system.

You specify many of these features through settings in the Properties > Navigation dialog box for the specific layout:
Show Navigation Pane Link In Topics Select to include a link to the navigation pane in topics that are opened through

the context-sensitive Help calls.
Add Breadcrumbs Links Select to add breadcrumbs in the topic pages.
Show Merged TOC In Child Project Select to view the merged TOC in the child project.
Format Click to change the format of breadcrumbs.
Show Context In Search Result (WebHelp, FlashHelp) Select to display the context of topics in search results.
Enable Highlight Search Result Select to highlight the search results in Topics. Select the color to highlight the search

results.

177

Last updated 3/1/2010

USING ROBOHELP HTML 8 178
Linking and navigation

Add About Box Set up information that appears in a dynamic window when users click the image in the main toolbar.

Example of About box

Browse Sequences Create browse sequences before enabling them.
Detail Change the text displayed for the in-topic navigation bar elements.
Search Input Field In Toolbar Include a search field in the main toolbar.
Synchronize Table Of Contents Synchronize the TOC with the topic in the right pane so that users see where they are

in the structure.

About breadcrumbs
Breadcrumbs are navigational links displayed in web pages of the Help system. These links outline the position of the
page in the table of contents or the directory structure of the project. You can define breadcrumbs in a master page or
a topic. They can also be configured at run time to appear on the top or bottom of a page.
The user can click a portion of the breadcrumb trail to go directly to a page. For example, if the trail is Home >
Installation > Hardware Requirements, the user can click Installation to go directly to the Installation page.
Breadcrumbs are displayed in merged projects. The breadcrumb trail for a page in a merged project shows the position
of the page with respect to the merged project and the master project.
For example, suppose the master project MultiCuisine contains the project AsianCuisine. AsianCuisine in turn
contains the project JapaneseRecipes. The breadcrumb trail for the topic “Common Japanese Ingredients” is as follows:
Home > MultiCusine > AsianCuisine > JapaneseRecipes
Breadcrumbs are generated only in WebHelp, WebHelp Pro, FlashHelp, FlashHelp Pro, HTML Help, and AIR Help.
For all other layouts, breadcrumbs are not generated, even if placeholders are present.

Add breadcrumbs to topics
1 Select View > Pods > Single Source Layouts.
2 Double-click the WebHelp/WebHelp Pro/FlashHelp/FlashHelp Pro layout, and click Next.
3 In the Navigation dialog box, select Add Breadcrumbs Links, and click Format.
4 In the Layout area, select the placement and alignment for the breadcrumbs.
5 In the Text area, select or specify a name for the link to the main Help page, which appears on every topic page.
6 Select a separator for the Breadcrumbs.
7 Type a label that precedes the breadcrumbs trail. For example, you can add the static text "You are here" before the

breadcrumb trail.
8 Preview the layout and formatting of breadcrumbs in the Preview pod.
9 Select a background color.
10 (Optional) Select Use Topic Level Format to use the default format settings.

USING ROBOHELP HTML 8 179

Last updated 3/1/2010

Linking and navigation

11 (Optional) Click Format to change the default font settings.
12 Click OK, and then click Finish.

In the generated WebHelp, all the topic pages show a breadcrumb trail reflecting the TOC hierarchy.

More Help topics
“Insert a placeholder” on page 109

Create text links
You can create links with most items you see in the Project Manager and TOC Composer. These items include topics,
bookmarks, URLs, baggage files, newsgroups, FTP sites, files (such as PDF) associated with other programs, and
remote topics.
Use Design Editor to create text links
1 In the Design Editor, select the insertion point for the link.
2 Click the Insert Hyperlink button

3 Select an option from the Link To menu. Specify the source location in the box.
4 If Display In Frame is selected, select an option from the pop-up menu.
Display In Frame If the destination is a frame, this option defines the frameset for displaying the destination
content. You can select the frame type or enter custom frame information. This option is unavailable for linking to
topics.
Display In Auto-sizing Popup Displays the destination topic in a pop-up window rather than in the viewer or
browser. The window size adjusts to the content. If you have a long topic, use a custom-sized pop-up.
Display In Custom-sized Popup Displays the destination topic in a pop-up window. To manually size the window,

type a number in the Width and Height fields. If the text goes beyond the pop-up's height or width, the pop-up
includes scroll bars. This option is available only for linking to topics.
5 Add tool tip text to appear when you hover over the link.
6 Select a local topic, bookmark, frame, or URL that exists in your project as the link destination. To filter the list,

click the triangle.
Drag to create links
1 In Design Editor, select the item in the topic for the hotspot. Select text, an image, or a multimedia object.
2 In the Project Manager pod, open the folder containing the destination item (such as a URL in the URLs folder, or

a topic in a custom folder).
3 Locate and select the destination item.
4 (Optional) Click the TOC tab to display the TOC Composer or the Project tab to display the Project Manager.
5 Drag the destination item from the Project Manager pod or Topics List pod onto the selected item in the Design

Editor.
Note: Topics with information types are not supported as links.

USING ROBOHELP HTML 8 180

Last updated 3/1/2010

Linking and navigation

More Help topics
“Image maps” on page 198

Link to a pop-up
You can create a link that displays an HTML topic in a pop-up rather than in the default browser or viewer. A pop-up
supports HTML formatting, images, Dynamic HTML, link controls, and other HTML features of the destination topic.
When a user clicks the link, the pop-up opens and sizes to fit either the content of the topic or dimensions that you
specify.
A pop-up can be used only to link to a topic or bookmark within the project.
1 In the Design Editor, place the cursor where you want a link, or select text or an image to define a hotspot.
2 In the toolbar, click the Insert Popup button

3 Select Hyperlink Options.
4 Select a size option. If you choose Custom-Sized Pop-up, enter values in points in the Height and Width boxes.
5 Under Select Destination (File Or URL), select a topic

, bookmark

, or frameset.

6 Click OK.

Note: A link within a pop-up to another pop-up doesn't work in the HTML Help viewer or in Internet Explorer.
Exclude pop-ups from full-text searches
1 Create a small HTML Help project to contain the pop-up topics.
2 Generate the project to create a CHM file.
3 Link to the pop-up topics in the second CHM file. (Do not merge the two Help systems.)
4 Distribute both CHM files to users.

More Help topics
“Text-only pop-ups” on page 190

Bookmarks
Use bookmarks to create incremental links within a topic. You can link to a bookmark from within the topic itself;
from any other topic in your project; or from an index entry, TOC entry, or image map. The Bookmark icon
appears next to bookmarked objects. To view bookmarks from the Project Manager, click the plus sign
next to a
topic.
Create bookmarks
1 Click left of the location for the bookmark.
2 Do one of the following:

• Click the Insert Bookmark icon

• Select Insert > Bookmark.
3 Enter a name, without spaces, using any combination of letters and numbers.

USING ROBOHELP HTML 8 181

Last updated 3/1/2010

Linking and navigation

After you save the topic, bookmark icons appear indented under topics listed in the Project Manager pod and next to
topics in the Topics List pod.
Create links to bookmarks
1 Open the destination for the link. To create a link within a topic, create a bookmark in the topic.
2 In the Design Editor, select the link location and then click the Insert Hyperlink button

3 Under Select Destination (File Or URL), select the bookmark to link to.
4 Click the View icon

to test the link.

Note: Bookmarks are grouped with their topics.
Rename bookmarks
1 Open the topic with a bookmark. Select the bookmark, right-click it, and select Bookmark [bookmark name]
Properties.
2 Edit the name and click OK.
3 Unassign and reassign the map ID for the renamed bookmark.
4 If the bookmark is used in context-sensitive Help, edit the map ID.

Locate bookmarks
1 Open a topic in the Design Editor.
2 Select Edit > Go To Bookmark.
3 Select a bookmark to locate.
4 Click Go To.

Remove bookmarks
1 Remove all links to the bookmark.
2 Select the bookmark icon in the topic. In the toolbar, click the Delete button.

More Help topics
“Edit a map ID” on page 216

Link images and multimedia
Add links to multimedia clips
You can include links to image, video, sound, and other multimedia files.
1 In the Design Editor, place the cursor where you want the link, or select text or an image to create a hotspot for the

link.
2 Click the Insert Hyperlink button
3 In Link To, click the triangle button
4 Select the file to link. Click Open.

.
and select Multimedia.

USING ROBOHELP HTML 8 182

Last updated 3/1/2010

Linking and navigation

Add links from images and multimedia
Topics can include multimedia as links, sound or video clips, local or external HTML topics, bookmarks, web or FTP
sites, e-mail, or newsgroups.
1 In the Design Editor, click the multimedia object or the image to link.
2 Click the Insert Hyperlink button

• To link from multimedia, in Link To, click the triangle button

and select Multimedia.

• To link from images, select the destination. Images can contain only one link.
Link from a sound or video object in the topic by right-clicking the object and selecting Insert Hyperlink.

External links
Link to external topics (Microsoft HTML Help projects)
1 In the Design Editor, select a link location.
2 Click the Insert Hyperlink button
3 In Link To, click the triangle button

.
to select Remote Topic.

Link to external files
1 Choose a link location in the Design Editor.
2 Enter text.
3 Highlight the text and click the Insert Hyperlink button
4 Click the triangle button

next to Link To and then select File.

5 Browse to a file, open it, and copy it into the project folder.
6 Generate the file to test links to external topics.
WebHelp projects The external file must be distributed in the WebHelp folder.
Microsoft HTML Help projects The external file must be distributed with the CHM file.

Note: The external CHM file must be in the same folder as the project CHM file.

Link to WinHelp topics (Microsoft HTML Help projects)
Add WinHelp topic controls to link to a topic in a WinHelp file from an HTML topic.
1 In the Design Editor, click a location for the control.
2 Select Insert > HTML Help Controls > WinHelp Topic.
3 Set the button options.
4 Click Next. Select the WinHelp file and topic.
5 Click Next. Set font options for the button label.
6 Click Finish.
7 To test the project, generate it.

USING ROBOHELP HTML 8 183

Last updated 3/1/2010

Linking and navigation

Link to e-mail addresses, FTP sites, newsgroups, and web addresses
1 In the Design Editor, choose a location for the link or select text or an image to define a hotspot.
2 Click the Insert Hyperlink button

3 In Link To, click the triangle button

and then do any of the following:

• To link to e-mail, select Email.
• To link to FTP sites or newsgroups, select FTP or Usenet News.
• To link to intranets or websites, select Web Address.

Link View
Use Link view to view and navigate project links.

Navigate in the Link View pod
The icon in the center of the Link View pod represents the current topic. Lines on either side of the icon represent
inbound and outbound links. Each line is color coded to denote the type of link.
1 Select View > Pods > Link View. Link View appears as a document in the Doc Pad.
2 Select the pod (workflow pane) from which to drag topics. Do any of the following:

• To display topics from the Project Manager, select View > Pods > Project Manager.
• To display topics from the TOC Composer, select View > Pods > TOC.
• To display topics from the Index Designer, select View > Pods > Index.
3 Select a topic from Topics For, and then drag it into the center of Link View. Click the previous and next buttons

to view the connected links.
4 To view another topic's links, in Link View, drag a topic on top of the one in the center of the group to display all

links to and from it.

Change the appearance of links in the Link View pod
Change icon sizes
1 Select View > Pods > Link View.
2 Click the Use Small Icon button

Note: The tool tip text indicates the action you can perform on the icons.
Set Link View scroll features
1 Select View > Pods > Link View.
2 Do any of the following:

• To scroll the topic with the linked topics, click the Keep Topic Elastic button
• To scroll hyperlinks only, click the Keep Topic Centered button
• For large projects, click the Display Limited Links button

Last updated 3/1/2010

USING ROBOHELP HTML 8 184
Linking and navigation

Set options in the Link View pod
Click the icons to see different types of links.

• The current topic is in the center and has a blue border.
• Inbound links appear on the left.
• Outbound links appear on the right.
Define use of the Link View window.
Icon Size Sets the size of the icons used to display topics. You can use small or large icons.
Center Topic Placement Positions the center with inbound and outbound links.
Move Center Topic With View Positions the topic to scroll with the links in the window.
Keep Center Topic Centered Keeps the center topic stationary while links move with the scroll bar.

Link maintenance and repair
Update and remove links
Open the topic containing the link. Do any of the following:

• To update the link, right-click the link, select Hyperlink Properties, and make changes.
• To remove a link, right-click the link and select Remove Hyperlink.
• To remove the link and the text, select the text and click Delete.

Manage broken links
To identify broken links, use the Broken Links folder in the Project Manager. It displays the names of deleted or
missing topics that are referenced in a project.
❖ Select these options from the Tools menu to identify and fix broken links:
Show Topic Links Displays a topic in Link View.
Show Topic References Identifies references for one topic. Use this option to determine whether the topic is
referenced in a TOC or index and whether other topics link to it.
Enable BugHunter For context-sensitive topics in Microsoft HTML Help systems. Use this option to diagnose

problems that can occur when linking HTML Help systems to Windows applications. BugHunter is available with
Adobe RoboHelp.
Resolve Broken Links Identifies missing or deleted topics that caused broken links. Use this option to determine
where the broken links originate and to restore topic links.
Edit Topic References Lets you look up references for topics in a project. Use this option to determine where
references originate and to modify them.
Edit External Topic References Identifies external topics (such as remote links or URLs) that are referenced in a
project. Use this option to modify or remove them from the project.

Last updated 3/1/2010

USING ROBOHELP HTML 8 185
Linking and navigation

Fix broken links
❖ Select Tools > Resolve Broken Links > References To Selected Topic.

• To fix a link, first select a link. Then click Edit, and edit or remove the hyperlink.
• To fix a TOC item, index keyword, or image map, first select the item. Then click Edit, and select a valid
destination to repair the broken link.

• To remove TOC entries, select the TOC item and click Delete. The book or page is removed from the table of
contents.
Note: If you use version control in a multi-author environment, some files might link to topics that have been moved,
renamed, or removed by another author. If you don't have the latest version of the files, they appear as broken links.

Identify and update topic references
Identify topic references
1 Select Tools > Edit Topic References.
2 From the Topics List pod or the Project Manager pod, select a topic.

• To show references for a single topic, right-click the topic and select Show > Topic References.
• To show references for all topics in the project, select Tools > Edit Topic References. On the right, select a topic.
The left view shows all topic references.
Update topic references
❖ Select Tools > Edit Topic References.

• To fix broken links, in References To Selected Topic, select the link to repair. Click Edit or remove the link.
• To fix or remove TOC items and entries, in References To Selected Topic, select the TOC item. Click Edit and
select a destination, or click Delete.

More Help topics
“Change an image map” on page 198

Identify and update external topic references
1 Select Tools > Edit External Topic References.
2 Do any of the following:

• To identify external references, select the topic.
• To fix broken links, in References To Selected Topic, select the link. Click Edit and make changes.
• To fix or remove TOC items and entries, in References To Selected Topic, select the item. Click Edit and select
a destination, or click Delete.
Note: You cannot change index keywords from this dialog box.

More Help topics
“Fix broken links” on page 185

USING ROBOHELP HTML 8 186

Last updated 3/1/2010

Linking and navigation

View and test hyperlinks
View hyperlinks and identify browse sequences
In the Design Editor, right-click and select Show Topic Links. Or, use the procedure that follows.
1 Select View > Pods > Link View. The Link View pod appears.
2 Drag topics from the Project Manager pod into the Link View pod.
3 Click the Project Manager pod.
4 Open the HTML Files (Topics) folder or a custom folder, and select a topic to view.
5 Drag the topic into the Link View pod over the center Link View icon

6 Release the mouse button to display links.

Test links in a topic
1 Select View > Pods > Topic List. The Topic List pod appears.
2 Right-click the topic and select View.
3 Click links to test them.

More Help topics
“Browse sequences” on page 192

Link controls
About link controls
Link controls are navigational alternatives to the TOC and index. A link control works like a link and can appear as
text, a button, or an image.
Note: When you update a topic, make sure that its link controls are up-to-date. Deleting a topic or changing a topic title,
topic content, or filename can affect link controls.
Link controls function in the following ways:

• Direct users to related topics and information. Link controls can save users time spent searching.
• Organize information for different kinds of users.
• Manage topic content by keeping information needed by multiple topics in a single topic and providing access to
it from several places with link controls.

• Manage topic layout by inserting link controls as objects rather than as long lines of links.
Types of link controls
Related Topics Displays a list of topics that you specify. You change the related topics list by topic, according to user
need. Related Topics controls require more maintenance than other link controls. If you add or remove topics, make
sure that you add or remove the topics in each Related Topics control.
See Also Displays a list of topics that you group into a logical category. All topics assigned to identical See Also
keywords appear in a list when users click See Also. See Also controls require less maintenance than other controls

USING ROBOHELP HTML 8 187

Last updated 3/1/2010

Linking and navigation

because you define the group of topics in one location (not in each topic). Make sure that you update the See Also
control when you add or remove topics. Automatic updates occur in each topic containing the control.
Keyword Links Controls that let you use index keywords for navigation within topics. Indexes group related topics

based on keywords. When a user clicks an index keyword, an associated topic list appears. If you add or remove an
index keyword in the index or in topic properties, the control updates within each topic that contains it. Keyword Link
controls are usable with main-level, or parent-index keywords.
Keyword link properties
Assign index file keywords and topic keywords from the index file to Keyword Link controls.
Keywords In Project Display all keywords available for the control.
Keywords In Control Display keywords assigned to the control.
Add Select the keyword from Keywords In Index. Select Add.
Delete Select the keyword from Keywords In Control. Select Delete.

For HTML Help projects:
Set Remote Keywords Use keywords from other CHM files.
Note: While similar to the Related Topics control, the See Also control has the added feature of being able to leave out of
its list, the topic where it is placed. In addition, it can be automatically updated in each topic containing the control. This
means that the control can be copy/pasted among associated topics.

Add Related Topics controls
Changes you make to titles or filenames are not applied to the Related Topics control.
1 In the Design Editor, click a location for the control.
2 Click the Insert > Related Topics.
3 Choose an option to show related topics as a button, which can be a label or an image, or to show related topics as text.
4 From Topics In Project, select a topic and click Add. Continue to add all topics you want to appear as related topics.

Note: The URL box displays the location of the topic file linked, and Title shows the title of the topic page.
5 (Optional) Click Change to update the topic name in Related Topics.
6 Choose options to display in a Topics found dialog or in a pop-up menu.
7 Select an option to display the selected topic in a frame or new window.
8 Select display and font options.
9 Click Finish and then click the View button

to test.

Note: (Microsoft HTML Help) If the topic contains a Related Topics control, the links might not work properly because
of a known Microsoft HTML Help bug. Consider using See Also controls, Keyword Link controls, or standard HTML
links.
Related Topics wizard
Use the Related Topics wizard to change how a link for a Keyword Link or Related Topics control appears: as a button
with text or an image, as plain text, or as a hidden control that works with scripts.
Button Defines how a control appears in a topic.

USING ROBOHELP HTML 8 188

Last updated 3/1/2010

Linking and navigation

Label Displays a control as a square gray button with black text. The text in the box displays on the button. You can

edit the label.
Image Displays a control as an image. The image filename appears in the box below this option. (You can't add a text

label to an image or edit the label in RoboHelp.) To select an image, click the Browse button
image from the dialog box. Save the image as a Windows bitmap (BMP) and icon (ICO) file.

, and then select an

Text Displays a control as a text link (Example: More information).
Hidden (For Scripts) Hides the control. Used for a topic to which you add a script. The control isn't visible in the topic.

Work with a developer to configure a script.
(HTML Help Projects Only) If No Topics Are Associated With Any Of The Keywords, Disable The Button If you create a

Keyword Link control and then remove all the keywords assigned to the control, the control is disabled when a user
opens the topic.
Choose Topic From Defines how the list of topics is displayed when a user clicks a link control.
Topics Found dialog Displays the list of topics in a Topics Found dialog box. The topic appears when a user selects a
topic and then clicks Display.
Popup Menu Displays the list of topics in a pop-up menu. Users select a topic to open it.
Frame Specifies a frame in which to display a topic when the keyword is clicked. Custom framesets appear in the list.

For HTML Help projects using See Also or Keyword Link controls:
If no topics are associated with any of the specified keywords, disable the button Disables the control if there are no

topics associated with the control keywords. For example, if you create a Keyword Link control and then remove all
the keywords assigned to the control, the control is disabled when users open the topic.

Create, assign, and add See Also keywords and controls
Create and assign See Also keywords
1 Do one of the following:

• Double-click the See Also folder in the Project Manager pod. The See Also pod appears.
• Type the See Also keyword in the text box. Click the plus sign.
• Click the Add New See Also Keyword button

icon. Type the new keyword and press Enter.

The keyword appears in bold, indicating that no topics are associated with it.
2 To assign topics to the See Also keyword, click the Topic List pod and do one of the following:

• To add the keyword to multiple topics, select a topic, drag it into the lower pod, and repeat for all topics you
want to assign.

• To add the keyword to individual topics, click the Topic List pod, select a topic, click the Properties button
and select See Also. Type the keyword to assign to the topic and click Add.
3 Add a See Also control to the new keyword.

See Also pod
See Also Keywords Create See Also Keywords or edit existing ones.
Add Add the See Also Keyword entered in the box.
Delete Remove a See Also keyword from the list.

USING ROBOHELP HTML 8 189

Last updated 3/1/2010

Linking and navigation

Replace Replace an existing See Also Keyword with text from the box.

Set See Also properties on the See Also pod
Add only See Also Keywords that are assigned to topics.
See Also Keywords In Project Display all See Also keywords available for the control.
See Also Keywords In Control Display See Also keywords assigned to the control.
Add Select the name from See Also Keywords In Project to add.
Delete Select the name from See Also Keywords In Control to delete.

For HTML Help projects:
Set Remote See Also Keywords Select to use See Also keywords that are used in other CHM files.

Set See Also Keywords in the See Also wizard
See Also Keywords In Project Display a list of all available See Also keywords.
Add Select the name from See Also Keywords In Project to add.
Delete Select the name from See Also Keywords In Control to delete.
See Also Keywords In Control Display See Also keywords assigned to the control.

For HTML Help projects:
Set Remote See Also Keywords Use See Also keywords from other CHM files.

Set keywords in a remote CHM file
Note: HTML projects only.
The CHM file is copied to the project folder. Keywords are referenced only from the CHM file.
CHM File Name Enter the remote CHM file to reference.
❖ Click the Browse button

to browse for remote CHM files.

Keyword Enter the keyword to reference. Type the name exactly as it is used in the CHM file.
Add Add a keyword to Remote Keywords In Control.
Delete Remove keyword from Remote Keywords In Control.
Remote Keywords In Control Display the keywords insert.

Set See Also keywords in a remote CHM file
Note: HTML projects only.
Use See Also keywords in the Help project that are used in other CHM files. The CHM file is copied to the project
folder. See Also keywords are not copied.
CHM File Name The remote CHM file
Browse button

Click to browse to the remote CHM file.

See Also Keyword Type the name of the See Also keyword exactly as it is used in the CHM file.
Add Add the See Also keyword to the Remote See Also keywords in the control field.
Delete Remove the See Also keyword from the Remote See Also keywords in the control field.

USING ROBOHELP HTML 8 190

Last updated 3/1/2010

Linking and navigation

Remote See Also Keywords In Control Display the See Also keywords to insert into the control.

Add See Also controls
1 Create See Also keywords.
2 In the Design Editor, click a location for the control.
3 Click Insert Help Control

4 Select See Also.
5 Select the link options.
6 Under See Also Keywords In Project, select a See Also keyword.
7 Click Add. Repeat for all keywords you want to add. Click Next.
8 Select display and font options.
9 Click Finish. To test the control, generate the project.

Change, reuse, or remove link controls
❖ In the Design Editor, open a topic containing the link control.

• To change a control, double-click the control and change its properties.
• To reuse a control, right-click the control and select Copy. Right-click in the destination topic and select Paste.
• To remove a control, select the control and click Delete

Text-only pop-ups
Work with text-only pop-ups
Text-only pop-ups are short text passages, such as definitions, that appear when a user clicks a linked term. You can
insert a text-only pop-up anywhere except in topic headers and footers. For longer text passages, or if you need
graphics, use a regular pop-up.

More Help topics
“Link to a pop-up” on page 180

Create text-only pop-ups
1 In the Design Editor, select the text.
2 From the Insert menu, select Text-Only Popup.
3 Type the pop-up text directly into the window.

Edit text-only pop-ups
1 Right-click the text-only pop-up and select Text Popup Properties.

• To edit the text, type in the Popup Text box.
• To edit background color, fonts, and margins, click in the appropriate box and make the changes. Your
selections apply to text-only pop-ups you create in the future.

USING ROBOHELP HTML 8 191

Last updated 3/1/2010

Linking and navigation

2 To test, click the View button

and select the text-only pop-up.

Remove text-only pop-ups
❖ Right-click the pop-up and click Remove Text Popup.

Test text-only pop-ups
Test before generating
1 From the Design Editor, open the topic containing the text-only pop-up.
2 Click the View button

3 Click the text-only pop-up.

Test after generating
1 Click the View Primary Layout icon

. If you are prompted to generate, click Yes.

2 Navigate to the topic containing the text-only pop-up.
3 Click the text-only pop-up.

RoboHelp Search
When you enter a search term in the Search box, RoboHelp displays a list of topics containing that term. The topic list
sometimes provides context, depending on output type. When you view the topic, RoboHelp highlights the search
term. RoboHelp search supports these features:
Keywords You can assign a keyword to a topic that does not contain that word. For example, you can assign the
keyword "formatting" to a topic about fonts, styles, and point sizes. If you enter "formatting" as a search term,
RoboHelp displays that topic even though it doesn't contain the word "formatting." When ranking search results,
RoboHelp gives more weight to keywords than to search terms found in the body of a topic.

Note: Keyword search is not available in Microsoft HTML Help (CHM).
Synonyms Define synonyms to allow for variations in search terms. For example, you can define "cursor," "pointer,"

and "mouse" as synonymous terms. If the search term is "mouse," RoboHelp returns all topics containing the word
"cursor," with that term highlighted.
Excluding topics from search You can exclude entire topics from search by selecting the Exclude From Search option

in topic properties.
Note: Exclude From Search is not available in Microsoft HTML Help (CHM).
Multiple language search RoboHelp search supports multiple languages at the project, topic, and paragraph level. For
example, suppose you search for a German word in an English topic with an embedded German paragraph. If
RoboHelp finds the German word, it displays the English topic with the German word highlighted.
Substring search (WebHelp/Pro, FlashHelp/Pro) If you enable this feature, a search for "log" returns topics containing
the words "catalog" and "logarithm." Substring search takes longer than whole-string search.
Phrase search To search for a phrase, enter it in quotation marks in the search box. If the search term is "color swatch,"

RoboHelp returns all topics with the phrase "color swatch".

Last updated 3/1/2010

USING ROBOHELP HTML 8 192
Linking and navigation

Customizable search results list (WebHelp/Pro) By default, ten search results appear at a time. In these two outputs,

the Search pane contains an option for the maximum number of search results to show in a list.
Topic context in search list By default, the search results list shows the first 60 characters of each topic to give context.

You can disable the display of context by using the SSL dialog box.
Note: Only WebHelp/Pro and FlashHelp/Pro support context in Help results. In Flash Help/Pro, the context appears as
a tool tip.
Search Office and PDF files (WebHelp/Pro, FlashHelp/Pro) You can search for baggage files (such as PDF, Word, and

Excel files) in published output. To appear in search results, these baggage files must be referenced in a topic through
a hyperlink.
Note: You must have iFilter for Microsoft and PDF installed on to enable baggage file search.
Rank search results You can rank search results based on their relevance. For example, if a word appears in the title of
a topic, its rank is higher than the word in the keyword list. A topic with the word appearing in heading 1 ranks higher
than the word appearing in heading 2 and is displayed first in the search results.

Browse sequences
Create or edit browse sequences
Use browse sequences to provide a path for your readers to move through a series of topics. When working with
browse sequences, keep in mind the following:

• You cannot include HTML files or external topics from other Help systems in browse sequences.
• A single topic can belong to multiple browse sequences.
• Each type of Help displays browse sequences differently.
• Enable browse sequences for them to become active in projects. See the documentation for the single source layout
output for information on how to enable browse sequences.

Create browse sequences automatically
An automatically created browse sequence replaces existing browse sequences.
1 Create the table of contents.
2 Select Tools > Browse Sequence Editor.
3 Click Auto-Create Using TOC.
4 Enter the number of levels from the TOC hierarchy that you want to include in the browse sequence, and click OK.
5 Click OK. If the Enable Browse Sequence dialog box appears, click Yes.

Create browse sequences manually
1 Select Tools > Browse Sequence Editor.
2 Click New and then name the browse sequence.
3 From Available Topics, select the folder containing the topics you’re adding.

USING ROBOHELP HTML 8 193

Last updated 3/1/2010

Linking and navigation

4 Add topics to the browse sequence.

• To move a single topic, select the topic and click Add, or click the Add Browse Sequence button

to move it.

• To move a group of topics, select the folder containing the topics and click the Add All Browse Sequence
button

5 Click OK. If the Enable Browse Sequence dialog box appears, click Yes.

Remove a topic from a browse sequence
❖ From the Browse Sequence list, select the topic and click Remove.

Rename or remove a browse sequence
From the Browse Sequence list, select the browse sequence.

• To remove it, click Remove.
• To rename it, click Rename and enter the new name.

View and test browse sequences
Identify topics associated with browse sequences
1 Select Tools > Browse Sequence Editor.
2 Under Browse Sequences, click the plus sign

next to each browse sequence to display the topics.

Test browse sequences
Topics that belong to multiple sequences appear within the browse sequence that is listed first in Link View.
1 Select View > Pods > Link View. The Link View pod appears.
2 Click the Project Manager tab.
3 In the Project Manager, open the HTML Files folder and select a topic.
4 Drag the topic into the Link View pod.

When a yellow line appears around the Link View icon
the topic.
If the topic is part of a browse sequence, the Previous

, release the mouse button to display links to and from
and Next

5 Click the Previous and Next buttons to test the browse sequence.

View sequences for a single topic
1 Select a topic.
2 Click the Properties button

3 Click the Advanced tab.

Test browse sequences in a browser or view
1 Verify that browse sequences are enabled.
2 Click the Generate button

to generate.

buttons appear above and below it.

USING ROBOHELP HTML 8 194

Last updated 3/1/2010

Linking and navigation

3 Click View Result and click through the browse sequence.

Identify the browse sequences a topic is assigned to
1 Open a topic in the Design Editor.
2 Click the Properties
3 Click the Advanced tab.

button.

195

Last updated 3/1/2010

Chapter 9: Multimedia and special effects
Images
Image basics
Image file formats
GIF (Graphic Interchange Format) An 8-bit color format that can display 256 colors and is useful for images with a
limited range of color. GIF images support the transparent attribute. They are best for grayscale photographs, cartoons,
small icons, buttons, bars, lines, and bullets. They can be interlaced and animated.
JPEG (Joint Photographic Expert Group) JPEG format is commonly used to display photographs and other

continuous-tone images in HTML documents. If you use images with 256 colors or more, use JPEG format. JPEG files
have either a .jpeg or .jpg filename extension.
BMP (Windows Bitmap) The standard bitmap image format intended for Windows, used in WinHelp applications.

Bitmap images support up to 24-bit color. When you import WinHelp projects into HTML, the bitmaps are converted
into GIF or JPG format. You can use bitmaps and icon formats (ICO files) when you add link controls or HTML Help
controls (custom buttons.)
MRB (Multi-Resolution Bitmap) A Windows Help image format that contains an image saved in different screen
resolutions in a single file. The program imports these files from WinHelp projects and converts them into GIF images.
WMF (Windows Metafile) A vector graphics format intended for Windows systems. WMF files are commonly used as

clip art for word-processing applications. The program imports these files from WinHelp projects and converts them
into GIF images.
PNG (Portable Network Graphics) A bitmap image format like GIF. The most recent versions of Netscape Navigator

and Microsoft Internet Explorer support PNG.
Tips:
• Create a stationery watermark effect by displaying background colors and images from the Borders And Shading
dialog box.

• When you select an image, the Cable Drum button appears

. Use it to link topic items (such as images, text, and
tables) with another topic item, and assign a Dynamic HTML effect to the connection.

• When you import a Microsoft Word file or an HTML file, all images are imported with the file (images must be in
anchored frames.)
Note: If you generate WebHelp Pro or WebHelp output, use GIF or JPEG files.

Locate images
Use the Graphics Locator to scan hard drives and folders for image files, view thumbnails, and copy files.
1 In the Toolbox pod, double-click the Graphics Locator
2 Select the graphic file format to search for.
3 Enter the path for the search or browse to a new location.
4 Click Search.

USING ROBOHELP HTML 8 196

Last updated 3/1/2010

Multimedia and special effects

Copy an image
1 In the Toolbox pod, double-click the Graphics Locator button

2 Select an image from the Image Files list.
3 Browse to a destination.
4 Click Copy File.

View an image
To view an image, you associate the filename extension with an application:
1 In the Project view, select the Images folder.
2 Right-click an image.
3 Click View.
4 Select Tools > Options.
5 Click the Associations tab.
6 Click Add next to File Associations. Enter a filename extension.
7 Click Select. Browse to the application to use for editing and viewing the file type.

Add an image to a topic
You can insert files with the following filename extensions: .gif, .jpeg, .jpg, or .bmp.
Note: For Web-based Help, use GIF or JPEG files.
1 In the Design Editor, select a location for the image.
2 In the toolbar, click the Insert Image button

3 Do either of the following:

• Click the Browse button

to browse to a file.

• If the image file is in the project, select a folder from the Images In Project Folders pop-up menu. Select All
Folders to see all images in the project.
4 Click OK.

Tips:
• For an image used in the project, drag it from the Project Manager\Images folder into the topic.

• To add predefined images, click the Gallery tab in the Image dialog box, select a category, and select the image. To
add it to the project, click OK.

• You can paste screen captures into the Design Editor without using a third-party image-editing tool. The images
are saved as either GIF or JPEG files. Press Alt + PrtScr to capture the active screen.

Add a RoboScreenCapture image to a topic
Simultaneously create and add images.
1 Move the cursor to a desired location in the Design Editor of a topic.
2 Click the Insert ScreenCapture button
3 Enter a filename for the new image.
4 Select a file format.

on the Object toolbar. The Insert ScreenCapture dialog box appears.

USING ROBOHELP HTML 8 197

Last updated 3/1/2010

Multimedia and special effects

5 Click OK. RoboScreenCapture opens and RoboHelp is minimized.
6 Select Capture > Active Window or any desired capture. The new image appears in the blank area.
7 Click Save

8 Close RoboScreenCapture. The Image dialog box of RoboHelp for HTML appears.
9 (Optional) Resize the image or place borders around it.
10 Click OK.

Remove an image from a topic
• To remove an image from a topic, in the Design Editor, select the image. Click the Delete button. The image
remains in the Images folder.

• To remove an image from a project, delete the file from all topics. The image is removed from the Images folder.

Edit an image in RoboHelp
1 In the Design Editor, select the image to edit.
2 Do one of the following:

• In the toolbar, click the Edit Selected Image button

• Select Edit > Edit item.
• In the Project Manager pod, right-click an image name. Select Edit.
3 Set options:
Text Wrapping Select the alignment of the image with the surrounding text.

Note: If text wrapping occurs around an image, then the image cannot be aligned. If text wrapping is set to None, then
the image, or the line it is on, can be aligned.
Screen Tip Enter text to display when the user hovers the cursor over the image.
Size Click to set the dimensions of the image in pixels. In the Size dialog box, select Maintain Aspect Ratio to
maintain the height to width proportion.
Margins Click to specify the space between the image and the text.
Borders Click to add a border to the image and specify a style.

Edit an image with RoboScreenCapture
1 In the Design Editor, select the image to edit.
2 Do one of the following:

• Select Edit > Edit With RoboScreenCapture.
• Right-click and select Edit with RoboScreenCapture.
• Click the Edit with RoboSourceControl

button in the Objects toolbar.

3 Edit the image.
4 Click Save.

Note: See RoboScreenCapture Help for more information.

USING ROBOHELP HTML 8 198

Last updated 3/1/2010

Multimedia and special effects

Image maps
Create an image map
1 In the Design Editor, open a topic containing an image.
2 Right-click the image. Select Insert Image Map.
3 Select Rectangle, Circle, or Polygon.

The cursor becomes a cross hair

4 Draw a clickable area within the image border.
5 In Link To, click the triangle pop-up menu

. Select a file under Select Destination (File Or URL) or another

destination.
6 In Screen Tip Text, enter text to display when users hover the mouse over the image map.
7 Click OK.

The Project Manager saves the image map with the image in the Images folder. A plus sign at the left side of the
Image button indicates an image map:
. Click the plus sign to see a list of all hotspots in the image map.
Hotspot links appear with the Hotspot icon
.
8 To test, click the View button in the toolbar. Click the hotspot.

Change an image map
1 In the Design Editor, open the topic containing the image map.
2 Double-click the hotspot.
3 In Link To, click the triangle pop-up menu

. Select a file under Select Destination (File Or URL) or another

destination.
4 Select OK. If prompted, select OK to copy the file into the project.
5 To test, click the View button

in the toolbar. Click the hotspot.

More Help topics
“Create text links” on page 179
“Link to a pop-up” on page 180

Adobe Captivate demos
Create an Adobe Captivate demo
1 Click the Project Manager tab. Place the cursor on the folder.
2 Select File > New, and choose Adobe Captivate Demo.
3 In the Topic Title box, type a host topic name.
4 In the File Name box, type a filename with the extension .htm.
5 Click OK.
6 Create the demo.

USING ROBOHELP HTML 8 199

Last updated 3/1/2010

Multimedia and special effects

7 Save the demo and close Captivate.
8 To test the demo, select or open the host topic, and click View

9 Open the host topic and add additional information, such as a header, footer, background color, or title text.

Note: You cannot access RoboHelp while Adobe Captivate is open.

Insert an Adobe Captivate demo
You can link to the demo topic from other topics in the project, from books and pages in the TOC, and from index
keywords. When users click the link, the demo starts.
1 In RoboHelp, open the topic where you want to insert the demo.
2 Place the cursor where you want to insert the demo.
3 From the Insert menu, select Adobe Captivate Demo. The Adobe Captivate Demo dialog box appears:

• If the demo SWF file is already in the project, select it from the Multimedia In Project Folders list.
• If the file is outside the project folder, click the Browse button

, navigate to the SWF file, and click Open. At

the prompt, click Yes to copy the file to the project folder.
4 Click OK. An object in the topic indicates where the file was placed.
5 To test the demo, click View

Edit an Adobe Captivate demo
1 Open the topic containing the Adobe Captivate demo, or in the Project Manager, expand the Multimedia folder.
2 Right-click the demo. Select Edit.
3 Make the changes.
4 Close Adobe Captivate.

Note: When you preview an Adobe Captivate demo in RoboHelp, a prompt may ask you to update the file in the project.
This prompt appears if you saved the Adobe Captivate demo outside RoboHelp to the default Adobe Captivate location.
(The default location is C:\Documents and Settings\[user name]\My Documents\My Adobe Captivate Projects\.)
Update the file to apply the changes made outside RoboHelp.

Multimedia
Add multimedia
1 Select a location for the sound or video. An object or image indicates the multimedia location.
2 Select Insert > Multimedia/Demo.

• To add a new file, click the Browse button

, and navigate to the file. Double-click it. Select Yes.

• To add an existing file, select it from the Multimedia In Project Folders list.
3 Set options:
Screen Tip Replaces the multimedia file with a text label if users disable multimedia in their browsers.

4 Click OK.

USING ROBOHELP HTML 8 200

Last updated 3/1/2010

Multimedia and special effects

5 Create a link to the multimedia file near the object with a note prompting users to select the link if they cannot

access the multimedia file.
6 To test, click the View button

in the toolbar.

Note: Some file formats do not work properly in compiled Microsoft HTML Help files.
The following are the allowed multimedia file types:

• Video Files: *.avi, *.asf, *.asx, *.mpg, *.mpeg, *.mpg4, *.mpe, *.mov, *.qt, *.ra, *.rm, *.rpm, *.wmv, *.wvx
• MPEG Video Files: *.mpg, *.mpeg, *.mpg4, *.mpe
• Windows Media Files: *.avi, *.asf, *.asx, *.wma, *.wmv, *.wax, *.wvx
• Quick Time Files: *.qt, *.mov
• Real Files: *.ra, *.rm, *.rpm
• Audio Files: *.asf, *.asx, *.mp3, *.mp4, *.wav, *.au, *.mid, *.rmi, *.ra, *.rm, *.wma, *.wax
• Flash Files: *.swf
• Flash Video Files: *.flv, *.f4v
• Adobe Captivate Files: *.swf
If you use the multimedia file in other topics, add it by dragging the file from the Multimedia folder.
Note: Multimedia content might have dependencies such as Flash or video/audio players that you need to install before
you can view or hear them.

Change multimedia
1 Double-click the multimedia object. The Multimedia dialog box appears.
2 Make the changes.
3 Click OK.
4 To test, click the View button

in the toolbar.

Remove multimedia from topics
1 Click to select the multimedia object.
2 Click the Delete button.

Click Undo

to restore a multimedia object you removed.

Dynamic HTML and special effects
Dynamic HTML (DHTML) combines the capabilities of multimedia and scripting to create visual and 3D effects. The
effects you insert perform an action or move in response to user input (such as a mouse click). Keep in mind the
following details when working with DHTML:

• Mouse rollover effects include Drop Shadow, Font Change, Glow, and Rock 'n Roll.
• Page-load, page-click, or trigger activation effects include Blur, Elastic, Fade In/Fade Out, Flip
Horizontally/Vertically, Fly In/Out, Gray, Show/Hide, Spiral, and Rock 'n Roll.

USING ROBOHELP HTML 8 201

Last updated 3/1/2010

Multimedia and special effects

• Some effects can be combined.
• For best results, use DHTML with Internet Explorer 5.0 and later.
• Dynamic effects in styles are not supported in W3C-compliant output. If you validate the code for W3C
compliance, the report can indicate errors.
Note: HTML files support DHTML effects in IE and non-IE browsers, but XHTML does not support all instances of
DHTML effects.

More Help topics
“W3C compliance” on page 120

DHTML basics
Add DHTML effects to a topic
1 Open a topic in the Design Editor and select an element. Do one of the following:

• Select text.
• For paragraph-based effects, click inside the paragraph.
• For positioned boxes, select the text box so you see gray boxes on its edges.
2 Select DHTML > Insert/Edit Dynamic HTML Effects.
3 From the When list, select the event for initiating the effect.
4 From the What list, select the effect you want to apply.
5 From the Settings list, adjust the properties.

The DHTML effect appears with light gray hash marks

To ensure that you apply the effect to the correct topic, use the Design tag list.

Apply DHTML effects to multiple paragraphs
1 In the topic, click where you want the text box.
2 Select Insert > HTML > Text Box.
3 Right-click the box, and select Text Box Properties. Set properties.
4 Type text in the box.
5 Click to select the box.
6 Select DHTML > Insert/Edit Dynamic HTML Effects.
7 From the When list, select the event for initiating the effect.
8 From the What list, select the effect you want to apply.
9 From the Settings list, adjust the properties.

Update DHTML effects in a topic
Update Dynamic HTML (DHTML) effects by resaving topics in either of these two situations:

• You add or modify a style to include a Dynamic HTML effect. In this case, resave all topics attached to the style
sheet so that they include code for creating the effect.

USING ROBOHELP HTML 8 202

Last updated 3/1/2010

Multimedia and special effects

• You’re able to open a project in a version of RoboHelp earlier than version 8.0.
You can resave the topics at the prompt or update them later by clicking the Design tab and selecting Tools > Update
DHTML In Topics.

Change or remove DHTML effects
1 Open the topic in the Design Editor.
2 Do one of the following:

• Select the topic with the effect that you want to change. Select DHTML > Insert/Edit Dynamic HTML Effects.
• Select the element to remove, and then select DHTML > Remove Dynamic HTML Effects.

Dynamic hotspots
About DHTML hotspots
DHTML hotspots display information when clicked.
Expanding hotspot When clicked, displays additional text next to the hotspot.
Drop-down hotspot When clicked, displays additional information below the hotspot.

Add DHTML hotspots
1 Open the topic in the Design view. Select the text to use as the hotspot.
2 Do one of the following:

• For expanding hotspots, select DHTML > Create Expanding Hotspot And Text. In the Expanding Text Editor,
type the text to appear in the hotspot. Click outside the window to close the editor.

• For drop-down hotspots, select DHTML > Create Drop-Down Hotspot And Text. Enter text or images in the
drop-down box. Click outside the Drop-down Text Editor.
3 Click the View button

to test.

Format DHTML hotspots differently from surrounding text to make them noticeable to readers.

Remove hotspots
Note: Content inside a hotspot is removed when you remove the hotspot.
❖ Right-click a hotspot. Select Remove Expanding/Drop-Down Text.

Change formatting of DHTML hotspots
Change the formatting in a single topic or change for all topics using a style sheet. For multiple style sheets, modify
each style sheet attached to the topics that use hotspots.
1 Select Format > Styles.
2 Do one of the following:

• To change formatting in a single topic, choose Available In and select the name of the topic to change.
• To change formatting in all topics using a style sheet, choose Available In and select the external style sheet.
3 Under Styles, select the hotspot style to change.

USING ROBOHELP HTML 8 203

Last updated 3/1/2010

Multimedia and special effects

4 Click Modify.
5 Click Format and select the attributes to change.
6 Click OK. Click Close.

Triggers and targets
About triggers and targets
Triggers are text or images that have a special DHTML effect applied. When users click text or an image that's assigned
a trigger, a target appears. To open DHTML effects using triggers, first assign a trigger to text or an image. Then
connect the trigger to a target and assign a DHTML effect. When working with triggers and targets, keep in mind the
following details:

• Triggers and targets must reside in the same topic.
• To indicate that an item is clickable, change the font color and underline, or add text to an image.

Trigger and target images

Assign a trigger to text or images
1 Select the text or image to assign as the trigger.
2 Select DHTML > Make Trigger. A cable drum icon

appears. Hash marks shade the text.

3 Connect the trigger to an image or text.

Connect triggers to text
1 Select the text to use as the target.
2 Select DHTML > Insert/Edit Dynamic HTML Effects.
3 Under When, select 1st Trigger Activation.
4 Select What (the effect that occurs the first time the user clicks the trigger), and then select property settings.
5 Select 2nd Trigger Activation and set the properties.
6 Click OK. A plug icon

appears next to the text, indicating that it is a target.

7 Click the trigger and drag to connect the trigger to the target text. To connect the trigger to multiple text targets,

hold down the Shift key and click the trigger. Continue to hold the Shift key and drag the mouse to the next target
text.

Connect triggers to images
1 Click the trigger image once to display the green cable drum icon

2 Click the cable drum icon and drag to connect the image to the target image. A green line shows the connection

between the trigger and target.
3 From the menu, select a DHTML effect.
4 To connect to another target, hold the Shift key and click the trigger again. Continue to hold the Shift key and drag

to the next image.
5 From the menu, select a DHTML effect for the target image.

USING ROBOHELP HTML 8 204

Last updated 3/1/2010

Multimedia and special effects

Removing triggers
❖ Right-click the topic item assigned to a trigger and select Remove DHTML Trigger.

Marquees
Add marquees
A marquee is a moving text message.

• To place a marquee around existing topic content, select the topic content and set marquee properties.
• To set marquee properties first, click the marquee destination in the topic. Set marquee properties, and enter the
marquee content.
Note: XHTML does not support Marquees.

Set or change marquee properties
1 Select Insert > HTML > Marquee.
2 Right-click the marquee, select Marquee Properties, and specify or change marquee properties.

• In Amount, select the rate at which the marquee moves. Higher number indicates faster speed.
• In Delay, select the duration in milliseconds for display.
• In Behavior, specify how the marquee moves.
Scroll The marquee moves continuously across the window.
Slide The marquee slides across the screen.
Alternate The marquee bounces from the starting direction to the opposite window border.

• In Repeat, specify repetitions of the marquee. Select Continuously to repeat the marquee as long as the topic is open.
3 Click the View button

to test.

Delete marquees
1 Place the cursor on the marquee boundary.
2 Click the left mouse button.
3 Click Delete

HTML comments in topics
Insert an HTML comment
1 Open a topic in Design Editor.
2 In Design view, insert the cursor and select Insert > HTML > Comments.

USING ROBOHELP HTML 8 205

Last updated 3/1/2010

Multimedia and special effects

3 In the Comment Editor, type your comment using the following format:

4 Click OK.

View an HTML comment
1 Open a topic in Design view or HTML view.
2 Select View > Show > Comments.

Comments appear as green callouts in Design view and as green text in HTML view.
3 (Design view) Move the cursor over the callout. The comment appears in a text pop-up note.

Iframes
Use iframes (inline frames) to insert PDF files or HTML files within an HTML topic. If you want to show a PDF file
or an accessible URL link in an HTML page, you can insert an iframe and display the required files within the selected
HTML page.

Insert an iframe
1 Select Insert > HTML > IFrame.
2 Double-click the iframe.
3 Specify a name. Click the browse button

to select a URL, HTML file, or PDF file to link.

4 (Optional) Click the Border tab to set border options.
5 Click OK.

Note: You can view the inserted file in the preview as well as in the generated Help.

Edit an iframe
• Double-click the iframe to change the name, the linked item, or the border.
• Drag the frame handles to resize the frame.

Last updated 3/1/2010

Chapter 10: Conditional text
Conditional text basics
Conditional text lets you generate subsets of the content within a project for various purposes or audiences. You can
create conditional build tags to exclude content from output, and then assign those tags to topics or elements within
topics.
Customize printed output
Online documentation often contains elements that are not useful in a printed manual, such as text describing online
features. You can tag these elements as conditional text and exclude them from the output. If the manual is a subset of
the online documentation, you can apply a conditional build tag to the topics and topic content to include. Then apply
another tag to the other elements. When you generate the project, you can exclude the online-only tag.
Target custom content to specific audiences
Sometimes topics pertain to products, experience levels, or types of users. Using conditional text, you can reduce the
amount of information you deliver to each group. You can also eliminate notes explaining small differences between
products.
Deliver versions of an application
To deliver demo, trial, and shareware versions of the application, you can omit topics in each version.

Design and test conditional text
1 Determine the types of output needed, such as printed manuals or online tutorials; consider current and future

requirements. Determine whether versions for different skill levels are required.
2 Determine which conditional build tags to apply to each output type. All untagged components are included in the

output. Determine whether to apply multiple tags to topics, for varied output types. For example, to deliver a
manual for testers of beta software, tag the beta-specific topics with a tag such as Beta. Tag the other topics with a
tag such as Printed. Then you can include beta-related topics first, and exclude them later.
3 Use the Topic Properties report or the Conditional Build Tag report to review the tags applied to each topic.
4 Determine whether to apply a conditional build tag to the entire topic or to one or more areas within a topic. For

example, if you are creating a printed manual, exclude text that mentions an online glossary.
5 Decide on tag names and colors, especially if the project is large and requires multiple output types. Define tag

names that describe the output, such as Print or Online. Tag colors help you differentiate conditional text areas
within a topic.
6 When updating a project, determine whether to delete content that is made obsolete by single-sourcing and

conditional output. For example, a project contains text (such as “for advanced users”) or images that explain which
content applies to which users. You can delete these elements or use conditional text to hide them in the output.
7 Determine which TOCs or pages of a TOC to include in the output, as you apply each tag.
8 Determine which indexes to include in the output. You can create multiple indexes in a project and include each

one in the appropriate output.

206

USING ROBOHELP HTML 8 207

Last updated 3/1/2010

Conditional text

9 Test the conditional tags by generating the output and viewing the results. Exclude combinations of tags you

applied to topics, TOCs, or indexes. You can also preview topics, without generating, to experiment with
conditional areas.

More Help topics
“Preview conditional text areas” on page 209

Workflow to implement conditional text
1 Create a conditional build tag.
2 Apply the tag to a combination of topics, topic content, TOCs, and indexes.
3 Define the tags to exclude from and include with the output.
4 Define the conditional build expression to include or exclude tagged topics.

The expression uses Boolean logic operators (OR, AND, NOT) to form phrases that exclude content marked with
a tag.
5 Generate the output.

Managing links to excluded topics
If you exclude content from output, broken links can occur in topics that reference the excluded content. RoboHelp
manages most of these links as described in the following table.
Type of link

Result

Browse sequence

An excluded topic doesn’t appear in the browse sequence

Image maps

If an image with an image map is excluded from output, the image map is removed.

Index

An index keyword that is linked to a topic that is excluded doesn’t appear in the Index pane.

Link control

A link control (such as a Related Topic or Keyword Link) that references an excluded topic
doesn’t display the topic.

Table of contents

A TOC book or page that is linked to an excluded topic doesn’t appear in the Contents pane.

Conditional build tags
Create a conditional build tag
1 Open a topic in Design Editor.
2 Select Format > Apply Conditional Build Tag > New/Multiple.
3 Click New. Type a name for the tag.
4 Assign a color to the tag by clicking the Build Tag Color button

. In the color box, click a color to select it, or
click Custom Color to define a new color. If you do not assign a color to the icon, RoboHelp assigns a unique color
to the icon by default.

Note: Two default tags are provided in all new projects: Online and Print. You can change their color, rename them, or
apply them to topics or topic content.

USING ROBOHELP HTML 8 208

Last updated 3/1/2010

Conditional text

Apply conditional build tags to content
Content that has a conditional build tag applied appears with diagonal hash marks in the color specified for the tag. If
a project is generated using a conditional build tag expression, the topic doesn’t display the content to which the tag
applies. The color of the diagonal hashing differentiates tagged areas. For a folder, no hash marks appear. You can
display hash marks for topics inside a folder.
Notes:
• Remove text references to excluded topics, such as links. Hotspots are not active for excluded topics.

• You can apply a conditional build tag to topics in the TOC pod.
• Show or hide conditional text by choosing View > Show > Conditional Areas.

Verifying tags applied to topics
The Used area of the Conditional Build Tag Properties dialog box lists the topics using a tag. The Level column shows
how a tag is applied:
<Topic> Applied to a topic.
<Content> Applied to topic content.
<Both> Applied to both topic and content.

The File column lists the file containing the tagged information.
❖ Right-click a conditional build tag in the Conditional Build Tag pod and click Properties.

Apply conditional build tags to a topic
1 Select View > Pods > Topic List. Select the topic.
2 Click Format > Apply Conditional Build Tag, and select a tag.

Apply conditional build tags to multiple topics
1 Select View > Pods > Topic List.
2 Select multiple topics.
3 Click the Properties icon

in the Project toolbar, and then click Advanced.

4 In the Conditional Build Tags (Topic Level Tags) pod, select a tag. Click OK.

Apply conditional build tags to topic content
1 Open a topic in the Design Editor.
2 Select topic content.
3 Click Format > Apply Conditional Build Tag.
4 Select a tag and click OK.

Apply multiple conditional tags to topic content
1 Open a topic in the Design Editor.
2 Select topic content.
3 Click Format > Apply Conditional Build Tag > New/Multiple.
4 Select tags or click Check All. Click OK.

Last updated 3/1/2010

USING ROBOHELP HTML 8 209
Conditional text

Apply conditional build tags to a folder, index, or TOC
1 Do one of the following:

• To apply tags to a folder, select a folder in the Project Manager pod.
• To apply tags to an index, click the Index folder in the Project Manager pod. Select a keyword or subkeyword.
• To apply tags to a TOC, click the Table of Contents folder in the Project Manager pod. Select a book or a page.
If you apply tags to the entire TOC, the TOC is unavailable in the output. If you apply them only to pages in the
TOC, the TOC is available. The tagged pages are not.
2 Click Format > Apply Conditional Build Tag > New/Multiple.
3 Select tags or click Check All. Click OK.

Apply conditional build tags to placeholders
❖ Do one of the following:

• Select a placeholder placed in a master page and select Format > Apply Conditional Build Tag > [new tag].
• Right-click a placeholder in the master page and select Apply Conditional Build Tag > [new tag].
Note: You can apply conditional build tags on snippet instances as well but not on snippets.

Preview conditional text areas
To check the format of a topic with a conditional text area, preview it using a conditional build tag expression you have
already defined. You can also define a conditional build tag expression while previewing the topic.
1 Open a topic in the Design Editor.
2 Select View > View Item.
3 Do one of the following:

• To preview an existing expression, choose it from the Conditional Build Tag Expression menu.
• To define and preview a new expression, click Define, and select tags to exclude from the output. Click OK.
To remove the conditional build tag expression from the preview, select None from the Conditional Build Tag
Expression menu.

Hide and view conditional text
Items with conditional build tags applied appear in the Design Editor with diagonal hatching in the color specified for
the tag.
Conditional text is always visible in the Design Editor, but you can hide the diagonal hatching.
❖ In View > Show > Conditional Areas, do one of the following:

• To hide the conditional text, deselect the option.
• To show the conditional text, select the option.

Remove conditional build tags
1 Do one of the following:

• To remove conditional build tags from a topic, select one or more topics in the HTML files folder of the Project
Manager pod.

Last updated 3/1/2010

USING ROBOHELP HTML 8 210
Conditional text

• To remove conditional build tags from topic content, open a topic in the Design Editor. Select topic content.
• To remove conditional build tags from a TOC, click in the TOC pod. Select one or more books or pages.
• To remove conditional build tags from an index, click in the Index pod. Select a keyword or subkeyword.
2 Click Format > Conditional Build Tags > New/Multiple.
3 Deselect tags or click Clear All. Then click OK.
4 To remove conditional build tags from a project, click Project. Expand the Conditional Build Tags folder, click a

tag, and select Delete. Then click OK.
Before removing a conditional build tag from a project, run a project report to determine the topics affected.

Rename conditional build tags
1 Right-click a tag in the Conditional Build Tags pod.
2 Select Rename, and enter a new name in the box.
3 Press Enter. Topics using this tag are updated with the new name.

Make sure that the conditional build expression is updated with the new build tag name before you regenerate the
project.

Conditional build tag expressions
Define conditional build tag expressions
An expression is a set of instructions. Expressions specify topics to include or exclude from the output. You can define
a basic expression that excludes tags, or a complex expression with Boolean operators, such as AND, OR, NOT.
Users cannot access topics or TOCs that are excluded from output. Index keywords and TOC entries do not appear.
RoboHelp removes links to the topic and removes the topic from link controls. It removes links to bookmarks inside
areas tagged as excluded. Tags applied to topic content do not affect TOC, index, or link controls.
Make sure that you have a single-source layout in which to store the expression. If needed, create a layout or modify a
default layout.
You can bypass build tags and generate output including all topics in the project whether build tags have been applied
or not. Select None in the Conditional Build Tag list, in the Options wizard, while generating the project.
1 Create a conditional build tag. Apply it to topics or topic content.
2 In the Single Source Layouts pod, right-click a layout and select Properties.
3 Click Define, and define a basic or advanced expression.
4 Click Save.

Remove a conditional build tag expression
1 In the Single Source Layouts pod, right-click a layout, and select Properties.
2 In the Conditional Build Expression list, select None. Then click Save.

USING ROBOHELP HTML 8 211

Last updated 3/1/2010

Conditional text

Advanced conditional build tag expressions
If you define advanced conditional build tag expressions using Boolean operators, use these guidelines for customizing
output. You can also let the program create them for you using the basic method.
Desired Result

Action

All topics to which one tag has been applied

Use the tag name. For example: Tag1

All topics to which multiple tags have been applied

Use AND with the tag names. For example: Tag2 AND Tag3

All topics to which any combination of tags has been applied

Use OR with the tag names. For example: Tag3 OR Tag4

All topics except those topics to which one tag has been applied

Use NOT with the tag name. For example: NOT Tag2

All topics except those topics to which multiple tags have been
applied

Use NOT in combination with AND with the tag names. For
example: NOT Tag1 AND NOT Tag2 AND NOT Tag4

Note: Topics and topic text to which you have applied no conditional build tag are included in the output.

Last updated 3/1/2010

Chapter 11: Context-sensitive Help
About context-sensitive Help
A context-sensitive Help (CSH) topic provides information about the user interface of an application relative to the
task a user performs. For example, CSH topics provide details about fields and controls in dialog boxes, descriptions
of windows or screen objects, and explanations of messages. The user accesses a CSH topic by pressing F1, clicking a
Help button, selecting from a menu, or clicking a question-mark icon.
The process for creating and implementing context-sensitive Help typically involves the content author and the
application developer. To specify context-sensitive topics, the author creates map IDs and map files. When a user
accesses context-sensitive Help, a map number and Help file name are sent to the Help engine. The engine matches the
map number to a topic ID and an HTM filename so that the correct topic appears.
The final step in the process is to test the context-sensitive Help. RoboHelp HTML provides several tools you can use
in addition to testing context-sensitive Help in the application.
Window-level topic Describes windows, dialog boxes, and messages in an application. Each window-level topic is in
HTM format and stored in a file with the extension .htm. It can contain text formatting, links, images, and other
features. These topics are more detailed than field-level topics because they describe the user interface components.
Users access these topics by pressing F1, clicking Help buttons, and selecting from menus.

If a custom window is not included with the application Help, context-sensitive topics appear in the HTML Help
viewer.
Field-level (What's This?) topic (WinHelp and Microsoft HTML Help projects) Briefly describes a field. A user

accesses the topic by clicking a question-mark icon, and then clicking a field in a dialog box. In RoboHelp, field-level
topics are called What’s This? topics.
Note: WebHelp, WebHelp Pro, FlashHelp, FlashHelp Pro, and AIR Help do not support What’s This Help. WebHelp
window support is available only with the context-sensitive Help API (Application Programming Interface).
Airplane Help Offline Help unsupported by an Internet connection. To use RH_ShowHelp, associate the offline Help

system with the function RH_AssociateOfflineHelp. This step tells the function how to operate if no Internet
connection is available. Individual calls to RH_ShowHelp must specify offline Help. Both RH_ShowHelp and
RH_AssociateOfflineHelp are in the support files. Use airplane Help to provide back-up Help when an Internet
connection fails.
Note: RH_ShowHelp is a programming function that a developer uses to display a help topic using rules found in
RoboHelp's CSH API.

212

USING ROBOHELP HTML 8 213

Last updated 3/1/2010

Context-sensitive Help

Author and developer roles in creating contextsensitive Help
Author

Developer

Writes the Help topics that describe how to use application
components such as windows, dialog boxes, fields, and controls.

Builds the components (windows, dialogs, fields, controls) that
make up the application.

Imports map files and assigns map IDs to each context-sensitive
Help topic. Communicates to the developer any unclear
assignments or changes in assignments.

Generates the map files that contain the map IDs and gives them
to the author.

or
Obtains map files that contain the map IDs from the author.

Creates map files and assigns map IDs to each context-sensitive
Help topic. Exports map files to the development environment
when complete and notifies the developer of any changes.
Generates the project to include the context-sensitive Help topics
with the output.

Writes code that calls the correct Help topics from within the
application (based on map IDs included in the map files).

Tests the context-sensitive topics in the application. Repairs errors Notifies the author when changes are made to the application (or
in the Help system.
map files) so that the Help project can be updated and
regenerated. Repairs errors in the application code.

On the Authoring home page of Peter Grainge’s website, you can find information about four methods of calling
WebHelp:

• Using URLs
• Using map IDs
• Using map IDs in merged WebHelp
• Using topic IDs

Map files and map IDs
About map numbers, map files, and map IDs
Map number A numeric value associated with a topic ID. Map numbers and topic IDs are saved in map files. Map
numbers are used with applications to specify a topic for calling context-sensitive Help. Whether application
developers use map numbers, topics IDs, or both depends on the programming language they use.
Map file A text file containing topic IDs and map numbers. You associate map IDs and map files with topics. As
author, if you receive a map file from your developer, assign a map ID from the map file. If you manually create a map
file, either auto-generate or manually create the map ID. A project can include multiple map files. Map files use the
extensions .h, .hh, and .hm. The default map file is BSSCDefault.h.
Map ID A string that pairs a topic ID with a map number. For example:
#define ID_SetupScreen 101

•

ID_SetupScreen is the topic ID.

•

101 is the map number.

•

ID_SetupScreen 101 is the Map ID.

Last updated 3/1/2010

USING ROBOHELP HTML 8 214
Context-sensitive Help

An Icon indicates the status of a map ID:

• Blue icons
• Yellow icons
• Locked icons

indicate that map IDs match topics.
indicate that map IDs do not match any topics.
(blue or yellow) indicate that the map ID is in a map file that is locked. It cannot be assigned or

unassigned.
Create map IDs, auto-generate map IDs, or import map files to use map IDs. A unique map ID must be assigned to
each topic ID. Assign a map ID to a Help topic to display the Help topic in context-sensitive Help.
Mapping table A mechanism that maps fields and controls in dialog boxes to map numbers. The mapping table is

programmed into the application to provide context-sensitive Help functionality.

Managing map files
Create a map file
Map files are text files that include a map ID list. Map filenames use the .h extension. When creating filenames, use
underscores instead of spaces, and avoid using these illegal characters: \ / : * ? < > | # ", $, &, [ ]
Authors or developers can create the map file. If the developer creates the map file, the author then imports it.
You can lock a map file to make it read-only.
1 Open the Project Set-up pod.
2 Expand the Context-Sensitive Help folder.
3 Right-click the Map Files folder.
4 Choose New Map File.
5 Enter a name.
6 Click OK. The file is added to the Map Files folder.

Note: Obsolete files potentially contain map numbers used for updated files.

Import a map file
1 Do one of the following:

• Click File > Import > Map File.
• Expand the context-sensitive Help folder in the Project Set-up pod.
2 Navigate to the map file. Make sure that it’s unlocked.
3 Double-click the map file to add it to the project Map Files folder.

Export a map file
1 In the Project Set-up pod, expand the Context-Sensitive Help folder.
2 Right-click the Map Files folder.
3 Select Export Map Files.
4 Select the programming languages to save the map files to.
5 Specify a location for the map file. Click OK.

Last updated 3/1/2010

USING ROBOHELP HTML 8 215
Context-sensitive Help

When you export a map file, the original file remains in your project.

Lock or unlock a map file
Locked map files are read-only files. Do not add, remove, or change map IDs in locked map files. Do not modify the
file if Remove Unused Map IDs is selected. If you do, you can possibly lose changes in the files. Imported map files are
locked by default.
1 Select View > Pods > Project Set-up.
2 Expand the Map Files folder (or a custom folder in the Map Files folder).
3 Right-click the map file.
4 Select Properties.
5 Select the Locked option. To unlock the file, deselect the Locked option.
6 Click Close.

Remove an obsolete map file
Obsolete map files sometimes contain map numbers used for updated files. These map numbers can dynamically call
a wrong topic. Delete unused map files to prevent this issue.
1 Open the Project Set-up pod.
2 Expand the Context-Sensitive Help folder.
3 Expand the Map Files folder.
4 Select the map file.
5 Click Delete.

Remove an unused map ID
Your map files must be unlocked to use this option. To remove unused map IDs:

• Expand the Context-Sensitive Help folder in the Project Set-up pod.
• Right-click the Map Files folder.
• Select Edit.
• Do the following:
Map Files Select the map files from which to remove unused map IDs.
Select All Click to remove unused map IDs from all map files.
Clear All Click to deselect all map files and not remove unused map IDs.

Managing map IDs
Create a map ID
1 Open the Project Set-up pod.
2 Expand the Context-Sensitive Help folder.
3 Expand the Map Files folder.
4 Double-click All Map IDs.

USING ROBOHELP HTML 8 216

Last updated 3/1/2010

Context-sensitive Help

5 In Map File, click the Down Arrow and select a map file to store the map ID.
6 Click the Create/Edit Map ID button

7 In Topic ID, type a word or phrase to identify the topic.
8 In Map Number, type a number.

Note: You can create individual map IDs per topic or auto-generate using the Auto Map button. See “Auto-generate
a map ID” on page 217

Edit a map ID
You can assign or unassign topic map IDs, create new map IDs and files, and automatically map (auto-map) IDs. You
can sort the topics by column.
1 Open the Project Set-up pod.
2 Expand the Context-Sensitive Help folder.
3 Right-click the Map Files folder.
4 Select Edit Map IDs.
5 Choose from the following options:
Map File List available map files (including imported map files).
<All Map Files> Display all map IDs.
<Project Map File> Display map IDs in the default map file BSSCDdefault.h. The map IDs for deselected map files

reside in BSSCDefault.h.
Click to open the New Map File dialog box and create a custom map file. Map numbers for custom
map files are numbered automatically.

Map file icon

Map # Display the map number of the topic ID. Map numbers reside in map files (.h, .hh, .hm).
Topic Display the topic assigned to the map ID.
Hide Used IDs Show unassigned map IDs.
New icon

Create a map ID. The ID is appended to the map file selected in Map File.

Edit icon

Edit the selected map ID.

Delete

Remove the selected map ID. Before removing the ID, click Unassign to prevent a broken link to the topic.

Options Customize topic auto-mapping.
Assign Assign the selected topic to the selected topic ID. This button is available when a topic is selected on the right

and a map ID is selected on the left.
Unassign Disassociate the map ID from the topic on the right.
Auto Map Assign a map ID in the custom or default map file (BSSCDefault.h). Select a map file and a topic. Click Auto
Map. This button is available only when you select <Project Map File> or a custom map file. If you auto-map a map
ID and a map file is not selected, the map ID resides in the default map file (BSSCDefault.h).

• The program assigns the topic title or filename as the topic ID and assigns a map number. Click Options to
customize auto-mapping.

• You cannot assign multiple topics to a map ID. You can assign multiple map IDs to a topic.

USING ROBOHELP HTML 8 217

Last updated 3/1/2010

Context-sensitive Help

Topic Lists the project topics. To filter the list, click the triangle

. Select All Folders, Top Level Folder, or a custom

folder.

• Properties icon
• Preview icon

Show all topic IDs assigned to the topic.
Display the topic.

Note: If you assign a map ID to a bookmark, you see a misleading error message indicating that the file does not exist.
Disregard the warning. The topic does exist.

Reassign a map ID
Update the map ID if the Help topic doesn’t open, if the wrong topic opens, or if the developer changed the application
that in way that affects the map IDs.
1 Select a map file under Map IDs in the Edit Map IDs dialog box.
2 Click Create/Edit Map ID.
3 Do one of the following:

• Reassign the map ID. Under Map ID, select the map ID. Click Unassign. Select another topic and click Assign.
• Change the topic ID or map number. Double-click the map ID and change the desired value.

Auto-generate a map ID
You can generate map IDs using a custom map file or the default map file (BSSCDefault.h). Before you generate map
files, check with the developer to determine naming conventions.
1 In the Project Set-up pod, expand the Context-Sensitive Help folder.
2 Expand the Map Files folder.
3 Double-click All Map IDs.
4 In Map File, click the triangle button.
5 Select a map file.
6 Set options for naming and numbering map IDs. By default, the application assigns the topic title or filename as the

topic ID and assigns a map number.
7 In the Topic field, select the topic.
8 Click Auto Map to create a map ID.
9 If necessary, double-click the map file to edit it.
10 Provide a copy of the map file to the developer.

Generate a map ID
The IDs reside in the map file you select from the Edit Map IDs dialog box.
❖ Click Options in the Edit Map IDs dialog box.
Prefix Map IDs With Select to enter a value at the beginning of each map ID.
Make Uppercase Select for uppercase auto-generated map IDs.
Start Numbering With Select to enter a starting number for map numbers.

Notes:
• Setting these options does not affect existing map IDs.

USING ROBOHELP HTML 8 218

Last updated 3/1/2010

Context-sensitive Help

• By default, the application assigns the topic title or filename as the topic ID and assigns a map number.
• Auto-generating map IDs is available when you select <Project Map File> or a custom map file. If you auto-map a
map ID and do not select a map file, the map ID resides in the default map file (BSSCDefault.h).

• You cannot assign multiple topics to a map ID. You can assign multiple map IDs to one topic.

Assign a map ID to a topic
1 Open the Project Set-up pod.
2 Expand the Context-Sensitive Help folder.
3 Expand the Map Files folder.
4 Double-click All Map IDs.
5 In Map File, click the Down Arrow and select the map file that contains the map ID.
6 Select the map ID to assign.
7 Select the topic.
8 Click Assign.
9 Click Close.
10 Generate the project.
11 Test the window-level topics with the application.

Unassign a map ID
1 Open the topic.
2 Click the Properties button

3 Click the Advanced tab.
4 Click Assigned Map IDs.
5 Select the map ID to unassign.
6 Click Edit Map IDs.
7 Click Unassign.
8 Click Close.
9 Generate the project.
10 Test the window-level topics with the application.

Note: If you assign map IDs to bookmarks and remove the bookmarks from the topics, manually unassign map IDs from
the bookmarks.

Information for developers
The API shares parameters with HTML Help and WinHelp. You can create custom dialog boxes.
Note: "Custom dialog boxes" refers to the feature that the projects using these APIs have to create their own dialog boxes
based on their requirements.

USING ROBOHELP HTML 8 219

Last updated 3/1/2010

Context-sensitive Help

Call your Help projects with the function RH_ShowHelp. The source code for this function is contained in the support
files which you import into your development project. Languages supported are Visual Basic, C/C++, JavaScript, and
Java. The files are in C:\Program Files\Adobe\Adobe RoboHelp [version]\CSH API. The files are:

• CSH API\RoboHelp_CSH.vb (Visual Basic)
• CSH API\RoboHelp_CSH.cpp (C/C++, dependent on the .h)
• CSH API\RoboHelp_CSH.h (C/C++, dependent on the .cpp)
• CSH API\RoboHelp_CSH.js (Web pages - HTML/JavaScript)
• CSH API\RoboHelp_CSH.java (Java applications)
RH_ShowHelp has four parameters as shown in the following table:
Parameter

Description

hParent

Handle to calling dialog HTML Help Only: This parameter closes the Help dialog when the calling
window is closed.

a_pszHelpFile

Help Source (depends on the Output type)
For Webhelp/FlashHelp: "Path to project start page"
For Webhelp Pro: "http://<ServerName>/roboapi.asp"
For HTML Help: "Path to .CHM file". To specify a dialog, use ">WindowName" at the end of the
parameter.

uCommand

Constants:
HH_DISPLAY_INDEX Displays Index pane and default topic.
HH_DISPLAY_SEARCH Displays Search pane and default topic.
HH_DISPLAY_TOC Displays Contents pane and default topic.
HH_HELP_CONTEXT Opens topic associated with map ID in dwData parameter.

dwData

To obtain the map ID, export the map file for the programming language. Use HH_HELP_CONTEXT in
the uCommand parameter.

Program Help for Visual Basic applications
This information is for developers connecting context-sensitive Help topics to Visual Basic applications.
1 Open the project in Visual Basic.
2 If the map files were created in RoboHelp, ask the Help system author to export the map files from RoboHelp to

Visual Basic.
3 Include RoboHelp_CSH.vb with your project. The function RH_ShowHelp is defined in RoboHelp_CSH.vb.
4 Add a reference to the Microsoft Internet Controls.
5 To launch the Help system, call RH_ShowHelp with uCommand set to HH_DISPLAY_INDEX, HH_DISPLAY_SEARCH, or
HH_DISPLAY_TOC and dwData set to "0".

6 Set the value of the Help source parameter (according to the Output type) in a string variable called

StrPathAndWindow as follows:

Last updated 3/1/2010

USING ROBOHELP HTML 8 220
Context-sensitive Help

Note: In the following examples, the API shares the same parameters regardless of output type. The only change made
is the location of the Help file.
WebHelp/FlashHelp Stores the full path to the start page and a dialog name in a string variable called
StrPathAndWindow. An example of this string is "C:\Program
Files\MyApplication\WebHelp\MyStartPage.htm>MyWindow.”
WebHelp Pro Stores the full path to the server and a window name in a string variable called StrPathAndWindow.

Check with the web administrator to determine whether the project name is required. (The project name is
required if the Auto-Merge option in the RoboHelp Server Configuration Manager is set to Off.)
An example of this string is http://<servername>/robohelp/rest/search?project=<projectname>&quesn=<search-query>

HTML Help Stores the full path to the CHM file and a dialog name in a string variable called StrPathAndWindow.

An example of this string is “C:\Program Files\MyApplication\MyHelp.chm>MyWindow.”
Do not hard-code the string variable StrPathAndWindow.
7 To call a Help topic, call the function RH_ShowHelp with a_pszHelpFile set to StrPathAndWindow, uCommand set

to HH_HELP_CONTEXT, and dwData set to the map ID of the topic.

RH_ShowHelp syntax
RH_ShowHelp syntax
RH_ShowHelp(hParent As Long, a_pszHelpFile As String, uCommand As Long, dwData as Long) As
Boolean

Example:
To open the topic mapped to number 1:
Public cshObject as new RoboHelp_CSH .RH_ShowHelp Me.HWND, StrPathAndWindow,
cshObject.HH_HELP_CONTEXT, 1;

Notes:
• In WebHelp Pro projects, the new context-sensitive Help API is supported only with RoboHelp Server.

• Create one global RoboHelp_CSH object to use for all context-sensitive Help calls.

Airplane Help for Visual Basic applications
If using Airplane Help, associate offline Help before making function calls.
Syntax
Public Function RH_AssociateOfflineHelp(pszPrimaryHelpSource As String, pszBackupHelpSource As
String) As Boolean

Example
strOnline = "http:// www.mycompany.com/roboapi.asp?project=myproject"
strOffline = "C:\Program Files\My App\WebHelp\StartPage.htm"
Public cshObject as new RoboHelp_CSH ' Should be global object
cshObject. RH_AssociateOfflineHelp strOnline, strOffline

Last updated 3/1/2010

USING ROBOHELP HTML 8 221
Context-sensitive Help

Program Help for Visual C++ applications
This information is for developers connecting context-sensitive Help topics to C++ applications.
1 Open the project in the C++ IDE.
2 Add RoboHelp_CSH.cpp and RoboHelp_CSH.h to the project.
3 Link the wininet.lib and hhctrl.lib libraries to the application. Look for the hhctrl.lib library in the CSH API

subfolder of the installation folder.
4 If you are using Microsoft Visual C++ with MFC, set the RoboHelp_CSH.cpp file so that it doesn’t use precompiled

headers.

Prevent RoboHelp_CSH.cpp from using precompiled headers
Visual Studio 6
1 Select Project > Settings.
2 Select Robohelp_Csh.Cpp.
3 On the C/C tab, change Category to Precompiled Headers.
4 Select Not Using Precompiled Headers.
5 Click OK.

Visual Studio .NET
1 Right-click Robohelp_Csh.Cpp. Select Properties.
2 In the C/C folder, select Precompiled Headers.
3 Select Not Using Precompiled Headers.

Function calls from Visual C++ applications
Note: Connect context-sensitive WebHelp, WebHelp Pro, FlashHelp, FlashHelp Pro, or HTML Help topics to Visual C++
applications.
Note: You can call the context-sensitive help from other languages too. Visual C++ is given as an example here.
RH_ShowHelp syntax
int RH_ShowHelp(HWND hParent, const char * a_pszHelpFile, unsigned int uCommand, DWORD dwData)

USING ROBOHELP HTML 8 222

Last updated 3/1/2010

Context-sensitive Help

Parameter

Data type

Description

hParent

HWND

Handle to calling the dialog box HTML Help Only: Close the Help dialog
box with the calling window.

a_pszHelpFile

const char *

Help source For Webhelp/FlashHelp: "Path to project start page" For
Webhelp Pro: "http://[ServerName]/roboapi.asp"
* For HTML Help: "Path to .CHM file"
To specify a dialog box, use ">WindowName" at the end of this
parameter.

uCommand

unsigned int

parameter.
dwData

DWORD

To obtain the map ID, export the map file for the programming
language. Use HH_HELP_CONTEXT in the uCommand parameter.

RH_OpenHelpTopic Syntax
Call "RH_OpenHelpTopic” function to open a Help Topic in WebHelp or FlashHelp.
int RH_OpenHelpTopic(const TCHAR * a_pszHelpMainPage,
const TCHAR * a_pszTopicRelPath);
Parameter

Data type

Description

a_pszHelpMainPage

const char *

Help source For Webhelp/FlashHelp: "Path to project start page" . To
specify a window, append ">WindowName" at the end Path to the
project start page.

a_pszTopicRelPath

const char *

Relative path of the topic corresponding to the main page.

To open to the default topic, make a Help call that sets uCommand to HH_DISPLAY_INDEX, HH_DISPLAY_SEARCH, or
HH_DISPLAY_TOC, and dwData to "0". In WebHelp Pro systems, default window settings for default navigation
buttons override the HH_DISPLAY constant.

Call a context-sensitive Help function for AIR Help
Note: The AIR Help API is provided for many languages including JAVA, VC.NET, CS.NET, VB, VB.NET. The following
example shows how to invoke the AIR Help API using Visual C++.
Call RH_AIR_ShowHelp function to show AIR Help Application.
int RH_AIR_ShowHelp(const TCHAR * a_pszViewerPath,
const TCHAR * a_pszHelpId,
const TCHAR * a_pszWindowName,
unsigned long ulMapNum,
const TCHAR * a_pszMapId,
const TCHAR * a_pszTopicURL);
Parameter

Data Type

Description

a_pszViewerPath

const char *

Path to the installation directory of AIR Help Application.

USING ROBOHELP HTML 8 223

Last updated 3/1/2010

Context-sensitive Help

a_ pszHelpId

const char *

(Optional) ID of help content to be viewed in Viewer. It is specified in
.helpcfg file.

a_pszWindowName

const char *

(Optional) Customized output window name.

ulMapNum

unsigned long

Context-sensitive map number

a_pszMapId

const char *

(Optional) Context-sensitive map ID. If specified it takes priority and
ulMapNum is ignored.

a_pszTopicURL

const char *

(Optional) URL of the topic to appear. If specified, this parameter takes
priority over ulMapNum and a_pszMapId.

The return value is 0 for a successful result and non-zero if any error occurs.
RH_GetAIRAppPath
Call RH_GetAIRAppPath function to get AIR Help Application.
TCHAR * RH_GetAIRAppPath(const TCHAR * a_pszAppId,
const TCHAR * a_pszPublisherId);
Parameter

Data Type

Description

a_pszAppId

const char *

Help app ID, specified in RoboHelp during AIR generation.

a_pszPublisherId

const char *

ID corresponding to the digital certificate used for signing the AIR
application.

The return value path of the AIR application. The user can call the function free() to free up the memory.
Note: Data Type can also be const wchar * for Unicode enabled applications.

Call a context-sensitive function for WebHelp, FlashHelp, or FlashHelp Pro
The following example assumes the full path to the WebHelp/FlashHelp start page and a dialog box name are stored
in a string variable called StrPathAndWindow. An example of this string is “C:\\Program
Files\\MyApplication\WebHelp\MyStartPage.htm>MyWindow.” Do not hard-code this string.
Note: Export the map files to the location.
Example:
To open the topic mapped as number 1:
RH_ShowHelp(GetSafeHwnd(), strPathAndWindow, HH_HELP_CONTEXT, (DWORD)1);

Note: If using airplane Help, associate the offline Help before making calls.

Last updated 3/1/2010

USING ROBOHELP HTML 8 224
Context-sensitive Help

Call a context-sensitive function for WebHelp Pro
1 Call the function.

The following example assumes the full path to the server and a window name are stored in a string variable called
StrPathAndWindow. The project name is required if the Auto-Merge option is set to Off. The value of this string
is: http://<servername>/robohelp/rest/search?project=<project-name>&quesn=<search-query> for
getting the URL for a given keyword.
For getting the context-sensitive information, the URLs are
http://servername>/robohelp/rest/robowindow?wtype=ctx
&context=<id>[&area=<area_of_publishing>&type=project_type>]

or
http://servername>/robohelp/rest/robowindow?wtype=prj&window=<windowname>[&area=<area_of_p
ublishing>&type=<project_type>]

Note: Export the map files to the location.
Example:
To open the topic mapped to number 1:
RH_ShowHelp(GetSafeHwnd(), strPathAndWindow, HH_HELP_CONTEXT, (DWORD)1);

2 Run and test the Help call.

Note: If using airplane Help, associate the offline Help before making calls.

Call a context-sensitive function for HTML Help
1 Call the function.

The following example assumes the CHM file and a window name are stored in a string variable called
StrPathAndWindow. The value of this string indicates the path to the CHM file, such as C:\Program
Files\MyApplication\MyHelp.chm>MyWindow.
Example:
To open the topic mapped as number 1:
RH_ShowHelp(GetSafeHwnd(), strPathAndWindow, HH_HELP_CONTEXT, (DWORD)1);

2 Run and test the Help call.

Notes:
• If using airplane Help, associate the offline Help before making calls.

• In WebHelp Pro projects, the Help API is supported only with RoboHelp Server or RoboEngine 3.0 or later.

Overriding the default MFC Help Handler
This topic is for Visual C++ developers who create MFC-based applications.

• As stated in the RoboHelp_CSH.h header file, the wininet.lib and hhctrl.lib libraries must be linked into the
application. The hhctrl.lib library can be in the CSH API folder in the RoboHelp installation folder.

• Include the RoboHelp_CSH.cpp file in your project.

Last updated 3/1/2010

USING ROBOHELP HTML 8 225
Context-sensitive Help

• To use the RoboHelp API instead of the default MFC Help handler, override the WinHelp function in your
mainframe class. By default, Visual Studio calls this class CMainFrame, and you can use the class wizard inside
Visual Studio to create the function override.

• After overriding the function and including RoboHelp_CSH.h, replace the contents of the function with this code.
(Set the path to your Help file properly. The example shows RoboHelp Server-based Help.)
Note: Modify the path to server-based Help according to your project. In this example, the path applies to RoboHelp
Server Help. See the rest of the API documentation to determine parameter values for each command and specify
secondary windows for context-sensitive Help calls.
CWaitCursor wait;
if (IsFrameWnd()) {
// CFrameWnd windows should be allowed to exit help mode first
CFrameWnd* pFrameWnd = (CFrameWnd*)this;
pFrameWnd->ExitHelpMode();
}
// cancel any tracking modes
SendMessage(WM_CANCELMODE);
SendMessageToDescendants(WM_CANCELMODE, 0, 0, TRUE, TRUE);
// must use top level parent (for the case where m_hWnd is in DLL)
CWnd* pWnd = GetTopLevelParent();
pWnd->SendMessage(WM_CANCELMODE);
pWnd->SendMessageToDescendants(WM_CANCELMODE, 0, 0, TRUE, TRUE);
// attempt to cancel capture
HWND hWndCapture = ::GetCapture();
if (hWndCapture != NULL)
::SendMessage(hWndCapture, WM_CANCELMODE, 0, 0);
// Set the path to server-based help
CString csOnlineHelpPath = _T("http://myserver/RoboAPI.asp");
// Translate the nCmd from WinHelp commands to RoboHelp commands
unsigned int nRHCmd;
switch (nCmd) {
case HELP_CONTEXT: nRHCmd = HH_HELP_CONTEXT; break;
case HELP_CONTENTS: nRHCmd = HH_DISPLAY_TOC; break;
case HELP_CONTEXTMENU: nRHCmd = HH_TP_HELP_CONTEXTMENU; break;
case HELP_WM_HELP: nRHCmd = HH_TP_HELP_WM_HELP; break;
case HELP_FINDER: nRHCmd = HH_HELP_FINDER; break;
default: nRHCmd = nCmd; break;
}
// finally, run the RoboHelp Help engine
if (!RH_ShowHelp(pWnd->m_hWnd, csOnlineHelpPath, nCmd, dwData))
AfxMessageBox(AFX_IDP_FAILED_TO_LAUNCH_HELP);

Visual C++ developers using Visual Studio .NET
• As stated in the RoboHelp_CSH.h header file, the wininet.lib and htmlhelp.lib libraries must be linked into the
application.

• Include the RoboHelp_CSH.cpp file in your project.
• To use the RoboHelp API instead of using the default MFC Help handler, override the HtmlHelp function in your
mainframe class. By default, Visual Studio calls this class CMainFrame, and you can use the class wizard inside
Visual Studio to create the function override.

• After overriding the function and including RoboHelp_CSH.h, replace the contents of the function with the
following code. (Set the path to your Help file accordingly. The example shows server-based Help.)

Last updated 3/1/2010

USING ROBOHELP HTML 8 226
Context-sensitive Help

CWaitCursor wait;
// Get the path to the Help system
CWinApp* pApp = AfxGetApp();
ASSERT_VALID(pApp);
// Set the path to server-based help
CString csOnlineHelpPath = _T("http://RoboHelp Server:port/robohelp/server");
PrepareForHelp();
// must use top level parent (for the case where m_hWnd is in DLL)
CWnd* pWnd = GetTopLevelParent();
// finally, run the RoboHelp Help engine
if (!RH_ShowHelp(pWnd->m_hWnd, csOnlineHelpPath, nCmd, dwData))
AfxMessageBox(AFX_IDP_FAILED_TO_LAUNCH_HELP);

Note: In WebHelp Pro projects, the new context-sensitive Help API is supported only with RoboHelp Server or
RoboEngine 3.0 or later.

Airplane Help for C++ applications
Syntax
void RH_AssociateOfflineHelp(const char * a_pszPrimaryHelpSource, const char *
a_pszBackupHelpSource)

Example
m_sOnline = "http://www.mycompany.com/roboapi.asp?project=myproject";
m_sOffline = "C:\Program Files\My App\WebHelp\StartPage.htm";
RH_AssociateOfflineHelp(m_sOnline, m_sOffline);

Note: To specify different window names for online and offline Help, you can map windows to RH_AssociateOfflineHelp.
Follow this example for Visual Basic:
strOnline = "http://www.mycompany.com/roboapi.asp?project=myproject>RemoteWindow1"
strOffline = "C:\Program Files\My App\MyHelp.chm>LocalWindow1"
Public cshObject as new RoboHelp_CSH ' Should be global object
cshObject. RH_AssociateOfflineHelp strOnline, strOffline
strOnline = "http://www.mycompany.com/roboapi.asp?project=myproject>RemoteWindow2"
strOffline = "C:\Program Files\My App\MyHelp.chm>LocalWindow2"
cshObject. RH_AssociateOfflineHelp strOnline, strOffline

Note: WebHelp Pro context-sensitive Help API is supported only with RoboHelp Server or RoboEngine 3.0 or later.

Program Help for Java applications
This information is for developers connecting context-sensitive Help topics to Java applications.
1 Open the project in your Java IDE (integrated development environment).
2 Add RoboHelp_csh.java to the project.
3 Call the function defined in RoboHelp_csh.java using any needed parameters.

Note: Airplane Help is not supported in the Java API.

Function calls from Java applications
In the following examples, the API shares the same parameters regardless of output type. The only change made is the
location of the Help file.

USING ROBOHELP HTML 8 227

Last updated 3/1/2010

Context-sensitive Help

public static boolean RH_ShowHelp(int hParent, String a_pszHelpFile, int uCommand, int
dwData)
Parameter

Data Type

Description

hParent

int

Reserved for future versions. Use 0.

a_pszHelpFile

String

Help source For Webhelp/FlashHelp: "<Path to project start page>" For
WebHelp Pro: "http://[ServerName]/roboapi.asp"
*Optional: Specify dialogs using ">WindowName" at the end of this
parameter

uCommand

int

parameter.
dwData

int

Topic map ID (defined in Edit Map IDs in RoboHelp). To obtain the map
ID, export the map file for your language (use HH_HELP_CONTEXT in
the uCommand parameter).

To launch the Help system (open to the default topic), make a Help call that sets uCommand to HH_DISPLAY_INDEX,
HH_DISPLAY_SEARCH, or HH_DISPLAY_TOC, and dwData to "0". In WebHelp Pro systems, default window settings for
default navigation button override the HH_DISPLAY constant (however, the Help system still opens to the default topic).

Call a context-sensitive function for WebHelp, FlashHelp, or FlashHelp Pro
1 Call the function.
RoboHelp_CSH.RH_ShowHelp(0, StrPathAndWindow, RoboHelp_csh.HH_HELP_CONTEXT, 1);

Where the full path to the WebHelp/FlashHelp start page and a window name (optional) are stored in
StrPathAndWindow. (Never hard code this string.)
Note: "Do not hard-code" here suggests that it should be left as a variable which should be taken as input from the user
in order for the code to be reusable, for opening different help files.
2 Run the application and test the Help call.

Call a context-sensitive function for WebHelp Pro
1 Call the function.
RoboHelp_CSH.RH_ShowHelp(0, StrPathAndWindow, RoboHelp_csh.HH_HELP_CONTEXT, 1);

Where the full path to the RoboHelp server and a dialog box name (optional) are stored in StrPathAndWindow.
(The project name is required if the Auto-Merge option is set to Off in the RoboEngine Configuration Manager.)
Examples of this value are “http://RoboHelp Server:port/robohelp/server” or “http://RoboHelp
Server:port/robohelp/server?project=MyProject>MyWindow.”
To open the topic mapped as number 1:
RoboHelp_CSH.RH_ShowHelp(0, StrPathAndWindow, RoboHelp_csh.HH_HELP_CONTEXT, 1);

2 Run the application and test the Help call.

Last updated 3/1/2010

USING ROBOHELP HTML 8 228
Context-sensitive Help

Program Help for web pages
This information is for developers connecting context-sensitive Help topics to web pages.
1 Talk to the Help author to determine the following:

• Who provides the map numbers.
• If the project has context-sensitive Help.
• Where the Help system resides (locally or on a server).
2 Open your web pages.
3 Link the pages to RoboHelp_csh.js.
4 Call the function contained in RoboHelp_csh.js wherever you call Help from the website.

Program Help for web pages (WebHelp/Pro)
Use the context-sensitive Help support files. These files allow developers to call built-in functionality.
The example below shows one way to declare a JavaScript function that displays a secondary dialog. The ShowHelp
function shows the specified topic in a custom window with the attributes defined by the strHelpOptions variable.
var strHelpOptions = "location=no";
strHelpOptions += ",toolbar=no";
strHelpOptions += ",menubar=yes";
strHelpOptions += ",status=yes";
strHelpOptions += ",scrollbars=yes";
strHelpOptions += ",resizable=yes";
strHelpOptions += ",top=0";
strHelpOptions += ",left=0";
strHelpOptions += ",width=400";
strHelpOptions += ",height=400";
function ShowHelp(strUrl)
{
window.open(strUrl, "Help", strHelpOptions);
}

To use ShowHelp, place the above script between the </HEAD> and <BODY> tags in the HTML file. Include an
anchor tag like the following where users can get help:
Help!
This tag makes a hyperlink with the text Help! When an end user clicks the hyperlink, widget.htm opens in a secondary
browser.

Function calls from web pages
Note: This information is for developers connecting context-sensitive WebHelp, WebHelp Pro, FlashHelp, or FlashHelp
Pro topics to web pages.
In the following examples, the API shares the same parameters regardless of output type. The only change made is the
location of the Help file.
RH_ShowHelp syntax
function RH_ShowHelp(hParent, a_pszHelpFile, uCommand, dwData)

USING ROBOHELP HTML 8 229

Last updated 3/1/2010

Context-sensitive Help

Parameter

Data Type

Description

hParent

var

Reserved for future versions of API. Use "0."

a_pszHelpFile

var

Help source For WebHelp: "<Path to project start page>" (Can be local
or on a server) For WebHelp Pro: "http://[server name]/roboapi.asp"
*Optional: To specify a window, use ">WindowName" at the end of this
parameter

uCommand

var

parameter.
dwData

var

Map ID of the topic displayed. To obtain the map ID, the author can
export the map file for a programming language using
HH_HELP_CONTEXT in the uCommand parameter.

RH_OpenHelpTopic Syntax
Call the "RH_OpenHelpTopic" function to open a WebHelp/FlashHelp topic.
function RH_OpenHelpTopic(a_pszHelpMainPage, a_pszRelTopicUrl)
Parameter

Data Type

Description

a_pszHelpMainPage

var

Help source for WebHelp/FlashHelp: "Path to project start page". To
specify a window, append ">WindowName" at the end Path to the
project start page.

a_pszRelTopicUrl

var

Relative path of the topic corresponding to the main page.

To launch the entire Help system (open to the default topic), make a Help call that sets uCommand to
HH_DISPLAY_INDEX, HH_DISPLAY_SEARCH, or HH_DISPLAY_TOC, and dwData to "0". In WebHelp Pro systems,
default window settings for default navigation buttons override the HH_DISPLAY constant.

Call a context-sensitive function for WebHelp Pro
1 Call the following API for getting the context-sensitive information from the server.

The following example assumes that you have stored the full path to your RoboHelp server and a window name
(optional) in a string variable called StrPathAndWindow. The project name is required if the Auto-Merge option
is set to Off in the RoboEngine Configuration Manager. Examples of the value of this string are “http://RoboHelp
Server:port/robohelp/server” or “http://RoboHelp Server:port/robohelp/server?project=MyProject>MyWindow.”
Note: Ask your technical writer which windows to call. Also, if the writer creates the map files, ask the writer to export
the map files to the location.
For example:
To open the topic mapped as number 1:
<p>Click for Help (map number 1)</p>

2 Run the application and test the Help call.

Note: In WebHelp Pro projects, the new context-sensitive Help API is supported only in RoboEngine 3.0 or later.

Last updated 3/1/2010

USING ROBOHELP HTML 8 230
Context-sensitive Help

Call a context-sensitive function for WebHelp or FlashHelp
1 Call the following API for getting the context-sensitive information from the server.
http://servername>/robohelp/rest/robowindow?wtype=ctx&context=<MAP ID>

For example:
To open the topic mapped as number 1, change the <MAP ID> with 1.
2 Run the application and test the Help call.

Program Help for .NET
.NET basics
Supports all forms of RoboHelp Server with .NET development:

• Creates web services, WebForms, and WinForms.
• Provides comprehensive support for .NET Framework.
• Operates as a self-contained .NET web service.
• Provides APIs to support Help development in Visual C .NET, C# .NET, Visual Basic .NET, and ASP .NET.
• Ensures that existing context-sensitive Help supports .NET requirements.
RoboHelp Server with .NET is designed to create applications for desktops, intranets, or the Internet and to support
the development of these applications.
Create server-based Help within the .NET environment and generate real-time analysis of end-user activity in a Help
system. Use with Visual C .NET, ASP .NET, Visual Basic .NET, or C# .NET to integrate Help systems.
Context-sensitive Help support files for .NET
Support files for programming context-sensitive Help allow you to import code and enter variables instead of writing the
code. The context-sensitive Help API for .NET supports Visual C++ .NET, ASP .NET, Visual Basic .NET, and C# .NET.
The API shares parameters with HTML Help and WinHelp. Custom windows are supported. Context-sensitive Help
works without any modifications.
Import file for the corresponding language from the respective folders at:
C:\Program Files\Adobe\Adobe RoboHelp 8\CSH API

C# .NET
C# .NET is an object-oriented language that enables C and C++ programmers to transition to the new .NET
environment while providing integration with existing applications. Components can be converted into XML and run
using any language on any operating system.
ASP .NET
ASP .NET is part of the .NET Framework for building web applications and XML web services. ASP .NET pages use a
compiled, event-driven programming model to generate markup such as HTML, WML, or XML. It allows the
separation of application logic and user interface. You can use any .NET language, such as Visual Basic .NET or C#
.NET, to create ASP .NET pages and AS P.NET XML web services files containing server-side logic.

Make a Help call
Use the context-sensitive Help code samples that Adobe provides.

USING ROBOHELP HTML 8 231

Last updated 3/1/2010

Context-sensitive Help

Make sure that context-sensitive Help function calls specify the online Help in the individual calls to RH_Showhelp.
When a remote Help call is made, the online version of the Help system appears. If connecting to the Internet is not
possible, offline Help appears.
Call context-sensitive Help for WebHelp or FlashHelp from C# .NET
1 Include the RoboHelp_CSH.cs file in the project.
2 Call the RH_ShowLocalHelp (hParent, strtHelpURL, strWndName, nCommand, nData)function.
Parameter

Data Type

Description

hParent

Object

Handle of the parent window.

strHelpURL

String

Help source for WebHelp; specifies the path to the project start page.

strWndName

String

Name of the window to be opened.

nCommand

Int

Class constants.
OptionConstants.CSH_DISPLAY_CONTEXT Opens the topic
associated with the map ID in the nData parameter
OptionConstants.CSH_DISPLAY_TOC

Displays the Contents pane

and the default topic
OptionConstants.CSH_DISPLAY_INDEX

Displays the Index pane

and the default topic
OptionConstants.CSH_DISPLAY_SEARCH

Displays the Search pane

and the default topic
nData

Int

Displays the map ID of the topic. To obtain the map ID, you can export the map
file for a programming language using
OptionConstants.CSH_DISPLAY_CONTEXT in nCommand.

Call context-sensitive Help for WebHelp Pro or FlashHelp Pro from C# .NET
1 Open VisualStudio.
2 Do one of the following:

• Select File > New > Project.
• Open a C# .NET project.
3 Add a button named Help.
4 Navigate to the context-sensitive Help supporting files in C:\Program Files\[RoboHelp Install Folder]\CSH

API\CS.NET.
5 Copy the RoboHelp_CSH.cs file.
6 Paste the files to the C# .NET project.
7 Right-click the Reference folder. Select Add Reference.
8 Select .Net tab > System.Web.Services.Dll.
9 Click OK.
10 Right-click the Reference folder. Select Add Reference.
11 Select
c:\windows\system32\msxml2.dll

USING ROBOHELP HTML 8 232

Last updated 3/1/2010

Context-sensitive Help

12 Select OK.
13 Double-click the Help button.
14 Copy C# .NET context-sensitive Help example code and paste into the code.
15 Add using RoboHelpAPI to the top of the document.
16 To test, compile, and run the project, select the Help button.

Call context-sensitive Help for WebHelp or FlashHelp from ASP .NET
1 Include the RoboHelp_CSH.cs file in the project.
2 Call the RH_ShowLocalHelp (hParent, strtHelpURL, strWndName, nCommand, nData)function.
Parameter

Data Type

Description

hParent

Object

Handle of the parent window.

strHelpURL

String

Help source for WebHelp; specifies the path to the project start page.

strWndName

String

Name of the window to be opened.

nCommand

Int

Class constants.
OptionConstants.CSH_DISPLAY_CONTEXT Opens the topic
associated with the map ID in the nData parameter
OptionConstants.CSH_DISPLAY_TOC

Displays the Contents pane

and the default topic
OptionConstants.CSH_DISPLAY_INDEX

Displays the Index pane

and the default topic
OptionConstants.CSH_DISPLAY_SEARCH

Displays the Search pane

and the default topic
nData

Int

Displays the map ID of the topic. To obtain the map ID, you can export the map
file for a programming language using
OptionConstants.CSH_DISPLAY_CONTEXT in nCommand.

Call context-sensitive Help for WebHelp Pro or FlashHelp Pro from ASP .NET
1 Open VisualStudio .NET.
2 Do one of the following:

• Select File > New > Project.
• Open an ASP.NET project.
3 Navigate to the context-sensitive Help supporting files in C:\Program Files\[RoboHelp Install Folder]\CSH

API\ASP.NET.
4 Copy the RoboHelp_CSH.cs file.
5 Paste the supporting files to the ASP.NET project.
6 Right-click the Reference folder. Select Add Reference.
7 Select .Net tab > System.Web.Services.Dll.
8 Click OK.
9 Add a button in the application.

USING ROBOHELP HTML 8 233

Last updated 3/1/2010

Context-sensitive Help

10 Double-click the button.
11 Copy the ASP.NET context-sensitive Help example code. Paste it into the code.
12 In the code, add using RoboHelpAPI.
13 To test, compile and run the project. Select the Help button.

Call context-sensitive Help for WebHelp or FlashHelp from Visual Basic .NET
1 Include the RoboHelp_CSH.vb file in the project.
2 Call the RH_ShowLocalHelp (hParent, strtHelpURL, strWndName, nCommand, nData)function.
Parameter

Data Type

Description

hParent

Object

Handle of the parent window.

strHelpURL

String

Help source for WebHelp; specifies the path to the project start page.

strWndName

String

Name of the window to be opened.

nCommand

Int

Class constants.

Opens the topic associated with the map
ID in the nData parameter
CSH_DISPLAY_CONTEXT

CSH_DISPLAY_TOC

Displays the Contents pane and the default

topic
CSH_DISPLAY_INDEX

Displays the Index pane and the default

topic
CSH_DISPLAY_SEARCH

Displays the Search pane and the default

topic
nData

Int

Displays the map ID of the topic. To obtain the map ID, you can export the map
file for a programming language using CSH_DISPLAY_CONTEXT in
nCommand.

Call context-sensitive Help for WebHelp Pro or FlashHelp Pro from Visual Basic .NET
1 Open VisualStudio.NET.
2 Do one of the following:

• Select File > New > Project.
• Open a Visual Basic .NET project.
3 Navigate to the context-sensitive Help files for ASP .NET in C:\Program Files\[RoboHelp Install Folder]\CSH

API\VB.NET.
4 Copy the RoboHelp_CSH.vb file.
5 Paste the supporting files to the ASP .NET project.
6 Right-click the Reference folder. Select Add Reference.
7 Select .Net tab > System.Web.Services.Dll.
8 Click OK.
9 Right-click the Reference. Select Add Reference.
10 Select:
msxml2.dll

USING ROBOHELP HTML 8 234

Last updated 3/1/2010

Context-sensitive Help

11 Select OK.
12 Add a button in the application.
13 Double-click the button.
14 Copy the Visual Basic .NET context-sensitive Help example code and paste it into the code.
15 To test, compile and run the project. Select the Help button.

Locate the RoboHelp Server with .NET samples
1 Select Start > Programs > Robohelp Office Pro For .Net Development Kit.
2 Select the sample for the application language.
Name

Language

RoboHelp Server CSH.NET VC Sample

Visual C++ .NET

RoboHelp CSH.NET VB Sample

Visual Basic .NET

RoboHelp CSH.NET C# Sample

C# .NET

Specify the URL (WebHelp Pro)
1 In code samples, find the string with the name:
m_strServer

2 Assign the server address to m_strServer:
http://server.com/robohelp/rest

3 Specify a project name.
m_strProject = P1

4 Specify the window name in the variable m_strParamValue.

Note: STRPRIMARY specifies the primary Help system and STRBACKUP specifies local Help. For Visual Basic .NET,
Visual C++ .NET, and C# .NET the application is on the client, allowing both online and offline Help systems. For ASP
.NET, all information is on a Web server. Specify a WebHelp Pro online Help system as a primary Help system and a
WebHelp online Help system as a backup.

Web services provided in RoboHelp Server with .NET
RoboHelp Server provides the following two services using the REST web services.
Robowindow Requests the server to get the window properties and context Help URL. See code details.
Search Performs the sentence search and returns results. See code details.

Steps without using support files
WebHelp Pro
WebHelp Pro is an uncompiled output type that is RoboHelp Server-based and supports standard Help features (such
as TOC, index, and search). A browser is not required to view the output. In addition, WebHelp Pro provides end-user
feedback reports on how people are using your system and other features available only with RoboHelp Server.
WebHelp Pro projects require RoboHelp Server for context-sensitive Help.

Last updated 3/1/2010

USING ROBOHELP HTML 8 235
Context-sensitive Help

Display content
An ASP file is included for viewing content. The default hyperlink is http://<RoboHelp Server>/Roboapi.Asp. You can
pass a parameter to the ASP file:

• project=Project_Name
• context=MapNumber
• url=URL
For example:

• This URL displays default content from the server: http://<RoboHelp Server>/Roboapi.Asp
• This URL displays the project_name project (merged with any other projects): http://<RoboHelp
Server>/robohelp/rest/search?project=<project-name>&quesn=<search-query>

• This URL displays content for map number 101: http://<RoboHelp Server>/
/robohelp/rest/robowindow?wtype=ctx&context=<id>&project=<project name>
Advanced window control
When opening context-sensitive WebHelp Pro from a browser, use the context-sensitive Help API and support files.

WebHelp
Context-sensitive Help for Visual Basic applications
Use this information to connect context-sensitive WebHelp or WebHelp Pro topics to Visual Basic applications.
The sample code here uses a function called Showhelp that opens a local or remote topic regardless of the browser type.
The ShowHelp function has two parameters: strTopic takes a URL or local filename as a value, and bIsLocal takes
a Boolean value. It indicates whether the first parameter is a local filename (TRUE) or remote URL (FALSE). If the file
is local, ShowHelp tells the browser to find the file in the Help subfolder of the application folder.
Public Function ShowHelp(strTopic As String, _
bIsLocal As Boolean) As Boolean
Dim strDir As String
If bIsLocal Then
' Get registry entry pointing to Help
strDir = App.Path + "\Help\"
End If
' Launch topic
Dim hinst As Long
hinst = ShellExecute(Me.hwnd, vbNullString, _
strTopic, vbNullString, _
strDir, SW_SHOWNORMAL)
' Handle less than 32 indicates failure
ShowHelp = hinst > 32
End Function

To call ShellExecute , declare the function. For example:

Last updated 3/1/2010

USING ROBOHELP HTML 8 236
Context-sensitive Help

Private Declare Function ShellExecute Lib _
"shell32.dll" Alias "ShellExecuteA" _
(ByVal hwnd As Long, _
ByVal lpOperation As String, _
ByVal lpFile As String, _
ByVal lpParameters As String, _
ByVal lpDirectory As String, _
ByVal nShowCmd As Long) As Long

The ShowHelp function requires an explicit filename or URL. But for context-sensitive Help, it is better to code the
application to use context IDs rather than explicit topic names. Use the following sample function, ShowHelpContext,
which maps integer context IDs to topic name strings, then calls ShowHelp to launch the topic.
Public Function ShowHelpContext(nContextId As Integer) As Boolean
Dim strTopic As String
Dim bIsLocal As Boolean
bIsLocal = True
Select Case nContextId
Case HH_GADGET_DIALOG
strTopic = "gadget.htm"
Case HH_WHATSIT_DIALOG
strTopic = "whatsit.htm"
Case HH_WIDGET_DIALOG
strTopic = "widget.htm"
Case HH_TECH_SUPPORT:
strTopic = "http://www.mycompany.com"
bIsLocal = False
Case Else
strTopic = "unknown-context.htm"
End Select
ShowHelpContext = ShowHelp(strTopic, bIsLocal)
End Function

..............................................................................................................................................
Using ShowHelpContext makes maintaining context-sensitive Help much easier because, if a topic name changes,
only one function must be modified. Declare context IDs (for example, HH_GADGET_DIALOG) as constants that can be
shared among the program modules that use context-sensitive WebHelp or WebHelp Pro.
Const HH_GADGET_DIALOG As Integer = 1
Const HH_WHATSIT_DIALOG As Integer = 2
Const HH_WIDGET_DIALOG As Integer = 3
Const HH_TECH_SUPPORT As Integer = 4

Connect context-sensitive WebHelp and WebHelp Pro topics to Visual C++ applications
Note: This information is for developers who must connect context-sensitive WebHelp and WebHelp Pro topics to Visual
C++ applications.
The sample code provided here uses a function called ShowHelp that opens a local or remote topic regardless of the
browser type.
The ShowHelp function has two parameters: szTopic takes a URL or local filename as a value, and bIsLocal takes a
Boolean value. It indicates whether the first parameter is a local filename (TRUE) or remote URL (FALSE). If the file is
local, ShowHelp tells the browser to find the file in the Help subfolder of the application folder.

Last updated 3/1/2010

USING ROBOHELP HTML 8 237
Context-sensitive Help

BOOL ShowHelp(LPCTSTR szTopic, BOOL bIsLocal)
{
TCHAR szDir[MAX_PATH] = "";
if (bIsLocal)
{
// Get directory of application
DWORD dw = GetModuleFileName(AfxGetInstanceHandle(), szDir, MAX_PATH);
TCHAR* pchEnd = _tcsrchr(szDir, '\\') + 1;
ASSERT_POINTER(pchEnd, TCHAR);
*pchEnd = '\0';
// Append subfolder name
_tcscat(szDir, _T("Help"));
}
// Open topic
HINSTANCE hinst = ShellExecute(NULL, //no parent hwnd
NULL, // open
szTopic, // topic file or URL
NULL, // no parameters
szDir, // folder containing file
SW_SHOWNORMAL); // yes, show it
// handle less than 32 indicates failure
return hinst > (HINSTANCE)32;
}

.......................................................................................................................................
The ShowHelp function requires an explicit filename or URL. But for context-sensitive Help, it is better to code the
application to use context IDs rather than explicit topic names. Use the following sample function, ShowHelpContext,
which maps integer context IDs to topic name strings, then calls ShowHelp to open the topic.
BOOL ShowHelpContext(int nContextId)
{
CString strTopic;
BOOL bIsLocal = TRUE;
switch (nContextId)
{
case HH_GADGET_DIALOG:
strTopic = _T("gadget.htm");
break;
case HH_WHATSIT_DIALOG:
strTopic = _T("whatsit.htm");
break;
case HH_WIDGET_DIALOG:
strTopic = _T("widget.htm");
break;
case HH_TECH_SUPPORT:
strTopic = _T("http://www.mycompany.com");
bIsLocal = FALSE;
break;
default:
strTopic = _T("unknown-context.htm");
break;
}
return ShowHelp(strTopic, bIsLocal);
}

...........................................................................................................................................

Last updated 3/1/2010

USING ROBOHELP HTML 8 238
Context-sensitive Help

Using ShowHelpContext makes maintaining context-sensitive Help much easier because if a topic name changes, only
one function has to be modified. The context IDs (for example, HH_GADGET_DIALOG) should be declared in a
header file that can be shared among the program modules that use context-sensitive WebHelp or WebHelp Pro. This
can be the same file where the prototypes for ShowHelp and ShowHelpContext are defined.

Programming HTML Help in applications
Note: Microsoft HTML Help projects only.
Window-level Help for Windows applications
• To call a topic using a map number, make a call to the HTML Help API using the following syntax:
HWND HtmlHelp(Window(), "c:\path\helpfile.chm", HH_HELP_CONTEXT, Number);

• To call a topic using a filename, make a call to the HTML Help API using the following syntax:
HWND HtmlHelp (Dialog(), "c:\path\helpfile.chm", HH_DISPLAY_TOPIC, "topicfile.htm");

What’s This? Help for Windows applications
The method for programming What’s This? Help depends on the way the context-sensitive Help was created.

• If the Help was created in RoboHelp as text-only topic files, see your software development kit for details.
• If the Help was created in What’s This? Help Composer, see “Create What's This? Help” on page 245.
Note: For more information, see the HTML Help API Reference at http://msdn.microsoft.com/enus/library/ms670068(VS.85).aspx.
Window-level Help for non-Windows platforms
• Use WebHelp to display context-sensitive Help topics for C++ and Visual Basic applications, Java applications, and
Web pages. For more information, see “WebHelp” on page 235.

• Use JavaHelp to display context-sensitive Help topics for Java applications. For more information, see “Create
context-sensitive JavaHelp” on page 240.

• Use Oracle Help to display context-sensitive Help topics for Java applications, or applications written in other
programming languages. For more information, see “Create context-sensitive Oracle Help” on page 241.
Note: If you must use your HTML Help output as a backup to a WebHelp, WebHelp Pro, FlashHelp, or FlashHelp Pro
system that is on a server, use Adobe's airplane Help.

Context-sensitive HTML Help function call
Sample code:
HtmlHelp(hWnd,
/*Window handle of program or dialog*/
"CSHHelp.chm",
/*Name of the CHM file*/
HH_HELP_CONTEXT,
dwMapNumber);
/*Map number from map file*/

HtmlHelp(hWnd Program or dialog box window handle. A window handle identifies a window so the HTML Help

engine discovers what application is performing the action.
CSHHelp.chm Compiled HTML help file. It includes context-sensitive help. Give the developer this file for use with
the application.
HH_HELP_CONTEXT This is the command sent to the HTML Help engine for window-level Help. (A command such

as HH_TP_HELP_WM_HELP is used for What's This? Help.)

USING ROBOHELP HTML 8 239

Last updated 3/1/2010

Context-sensitive Help

Dwmapnumber A map number from the map file.

Troubleshoot window-level Help
Note: Microsoft HTML Help projects only.
Problem

Wrong Help topic opens.

Error message

Command: HH_HELP_CONTEXT
Processing C:\Project Folder\HelpProject.chm
Map Number: 2750
File: Folder_Name\Topic_Name.htm

Cause

Incorrect map ID.

Resolution

Update the map ID.
Generate the project and retest.

OR:
Cause

Wrong or outdated map file.

Resolution

Ensure everyone is using the correct map file.
If the correct map file is used, unassign the map ID for the topic.
Remove the old map file and import the new map file.
Assign new map IDs.
Generate and retest.

Problem

Topic is not displayed.

Error message

1. No message
2. Command: HH_HELP_CONTEXT
Result: HH_HELP_CONTEXT called without a [Map] section
3. Command: HH_HELP_CONTEXT
Processing C:\Folder Name\Project_Name.chm
Result: Cannot find 180010 in C:\Folder Name\Project_Name.chm

Cause

No assigned map ID.

Resolution

If the map file does not exist, the message "HH_HELP_CONTEXT called without a [Map] section"
appears.
For developer-supplied map files, import the map file. Assign the map IDs.
If the message "Cannot find 180010 in C:\Folder Name\Project_Name.chm" displays, update the
map ID.
Generate and retest.

USING ROBOHELP HTML 8 240

Last updated 3/1/2010

Context-sensitive Help

Problem

Topic does not appear or wrong topic appears.

Error message

1. Command: HH_HELP_CONTEXT
Processing C:\Project Folder\Project_Name.chm
Map Number: 1
File: Folder_Name\Topic_Name.htm
2. Command: HH_HELP_CONTEXT
Processing C:\Project Folder\Project_Name.chm
Result: Cannot find 180010 in C:\Project Folder\Project_Name.chm

Cause

Wrong map number used in the call.

Resolution

Print the Map IDs report and give it to the developer.
Use this file to correct map number assignments.

Problem

Topic appears in wrong dialog box.

Error message

"HTML Help Author" opens and displays, "The window name 'window' passed to
HH_GET_WIN_TYPE has not been specified."

Cause

Wrong dialog name used in the call or author did not inform the developer that a custom
window was created for the topics.

Resolution

Ensure the developer knows about the custom dialog.
Generate and retest after the application updates.

Problem

Topic is not displayed.

Error message

1. Message is not displayed
2. Command: HH_HELP_CONTEXT
Result: HH_HELP_CONTEXT called without a [Map] section

Cause

Map file or map number is missing.

Resolution

For developer-supplied map file, restore or update the map file.
Generate the and retest.

Create context-sensitive JavaHelp
Use the context-sensitive Help API and support files to call built-in functionality, rather than creating functions to
display topics.
Context-sensitive JavaHelp requires custom code from your developer.
A printed copy of the .JHM file may help your developer.

Last updated 3/1/2010

USING ROBOHELP HTML 8 241
Context-sensitive Help

Example:
public class ContextHelp
{
private HelpSet hs;
private HelpBroker hb;
public boolean ShowHelp(String strTopic, String strHelpSet){
if (hb == null) {
ClassLoader loader = getClass().getClassLoader();
URL url;
try {
url = HelpSet.findHelpSet(loader, strHelpSet);
hs = new HelpSet(loader, url);
}
catch (Exception e) {
return false;
}
hb = hs.createHelpBroker();
}
hb.setCurrentID(strTopic);
hb.setDisplayed(true);
return true;
}
}

Test context-sensitive JavaHelp
Testing context-sensitive JavaHelp involves authors and developers.
Compress The Project Compile the project and create a .JAR file. Give the .JAR to your developer.
Test Context-Sensitive Topics Test topics in the application to ensure they appear in the correct dialogs and windows.
Resolve Errors Work with your developer to solve any problems.

Create context-sensitive Oracle Help
Note: This information is for developers who need to connect context-sensitive Oracle Help topics to applications.
The context-sensitive Help API and support files let you call built-in functionality instead of having to create the
functions to display topics.
Oracle Help supports context-sensitive Help, but your developer must write and customize the code to make it work.
A working example of a Java application with context-sensitive Help is shown below. To run the example:
1 Ensure that you have the Oracle Help for Java components and the Sun Java 2 SDK or later.
2 Copy and paste the code below into a file called CSHDemo.java.
3 Compile the file (for example, javac CSHDemo.java).
4 Run the Java applet (for example, java .cSHDemo <Oracle Help Helpset file>). The Oracle Help helpset file

parameter is the fully-qualified path to the helpset file. As an example, if you create an Oracle Help helpset file named
"sample.hs" and saved it in "C:\myFiles," the command to run this application with your helpset file would be:
java CSHDemo C:\myFiles\Sample.hs

Last updated 3/1/2010

USING ROBOHELP HTML 8 242
Context-sensitive Help

Sample context-sensitive Java application
/*********************************************************************************
* Oracle Help Context-Sensitive Help Sample Application
*
* This application is intended to demonstrate a few methods for invoking
* context-sensitive Help with Oracle Help.
*
* USAGE: CSHSample <full path to helpset file>
*
*********************************************************************************/
import
import
import
import
import

oracle.help.Help;
oracle.help.CSHManager;
oracle.help.library.Book;
oracle.help.library.helpset.HelpSet;
oracle.help.navigator.Navigator;

import java.awt.*;
import java.awt.event.*;
import java.net.URL;
public class CSHSample extends Frame implements ActionListener
{
private Help helpObj;
private Book bookObj;
private CSHManager contextManager;
private MenuItem exitMenu;
private MenuItem contentsMenu;
private MenuItem searchMenu;
private MenuItem indexMenu;
// Constants set to TopicIDs from map file for Helpset passed in
// via command line.
public static final String LABEL = "what_is_a_label_htm";
public static final String FIELD = "what_is_a_text_field_htm";
public static void main(String[] args)
{
if (args.length != 1) {
System.err.println("Usage: CSHSample <full path to helpset file>");
System.exit(1);
}
Book bookObj = null;
String filename = args[0];
// Expects filename format to be: "file:/[<drive>:/]dir/<helpset_file>"
// e.g., "file:/c:/myPath/myHelp.hs"
if (filename.charAt(0) == '/')
filename = "file:" + filename;
else
filename = "file:/" + filename;
try {
bookObj = (Book) new HelpSet(new URL(filename));
}
catch (Exception e) {

Last updated 3/1/2010

USING ROBOHELP HTML 8 243
Context-sensitive Help

System.err.println("CSHSample Error: " + e.getMessage());
System.exit(1);
}
CSHSample sampApp = new CSHSample(bookObj);
sampApp.setVisible(true);
}
// Class Constructor
public CSHSample(Book bookObj)
{
super("CSH Sample Application");
setResizable(false);
setSize(300, 200);
// Create Help Objects
try {
helpObj = new Help(false, false);
contextManager = new CSHManager(helpObj);
contextManager.addBook(bookObj, true);
}
catch (Exception e) {
System.err.println("CSHSample:: Failed While Creating Help object");
e.printStackTrace();
System.exit(1);
}
/********************************************************************
* Add UI Components
*******************************************************************/
MenuBar menubar = new MenuBar();
Menu filemenu = new Menu("File");
exitMenu = new MenuItem("Exit");
filemenu.add(exitMenu);
exitMenu.addActionListener(this);
menubar.add(filemenu);
Menu helpmenu = new Menu("Help");
contentsMenu = new MenuItem("Help Contents");
contentsMenu.addActionListener(this);
helpmenu.add(contentsMenu);
indexMenu = new MenuItem("Topic Index");
indexMenu.addActionListener(this);
helpmenu.add(indexMenu);
searchMenu = new MenuItem("Full Text Search");
searchMenu.addActionListener(this);
helpmenu.add(searchMenu);
menubar.add(helpmenu);
setMenuBar(menubar);
Panel mainPanel = new Panel();
add(mainPanel, BorderLayout.CENTER);
// Add label

Last updated 3/1/2010

USING ROBOHELP HTML 8 244
Context-sensitive Help

Label label = new Label("Country:", Label.LEFT);
mainPanel.add(label);
// Set context help for component. TopicID = LABEL
// Pass the component with the associated TopicID to the CSHManager Object
contextManager.addComponent(label, LABEL, true, true);
// Add TextField
TextField field = new TextField(15);
mainPanel.add(field);
// Set context help for component. TopicID = FIELD
// Pass the component with the associated TopicID to the CSHManager Object
contextManager.addComponent(field, FIELD, true, true);
/********************************************************************
* End: Add UI Components
*******************************************************************/
addWindowListener(
new WindowAdapter()
{
public void windowClosing(WindowEvent e)
{
setVisible(false);
System.exit(0);
}
}
);
}
public void actionPerformed(ActionEvent e)
{
Object source = e.getSource();
if (source == exitMenu) {
setVisible(false);
System.exit(0);
}
else if (source == contentsMenu) {
// Show Help; Display Contents tab
Navigator[] navs = contextManager.getAllNavigators();
if (navs != null)
contextManager.showNavigatorWindow(navs[0]);
}
else if (source == indexMenu) {
// Show Help; Display Index tab
Navigator[] navs = contextManager.getAllNavigators();
if (navs != null)
contextManager.showNavigatorWindow(navs[1]);
}
else if (source == searchMenu) {
// Show Help; Display Search tab
Navigator[] navs = contextManager.getAllNavigators();
if (navs != null)
contextManager.showNavigatorWindow(navs[2]);
}
}
}

Last updated 3/1/2010

USING ROBOHELP HTML 8 245
Context-sensitive Help

Note: Oracle Help uses topic IDs (in a map file) to make context-sensitive Help calls. You can change the topic ID by
editing the topic's META tag.

What’s This? Help
About the What's This? Help Composer tool
The What's This? Help Composer tool installs with RoboHelp. It supports both WinHelp authored in RoboHelp for
Word and Microsoft HTML Help.
This tool scans applications and generates projects. It reads program files and creates context-sensitive Help topics for
all controls and fields in dialog boxes. It can add suggested text to each Help topic to save authoring time.
Supported files for Microsoft HTML Help:

• Program files (EXE)
• Dynamic Link Libraries (DLL)
• ActiveX controls (OCX)
You can add context-sensitive Help to any RoboHelp project. The result is a single text-only file (Context.txt) that
contains text used for each context-sensitive Help topic that you create.

What's This? Help and Microsoft HTML Help
Creating a What's This? Help project for Microsoft HTML Help does the following:

• Creates a Context.txt file, which contains the context-sensitive topics.
• Attaches the Context.txt file to the project.
• Stores the Context.txt file in a database, updated when you edit the topics.
• Saves Dialog.cid and Context.h files (contain topic IDs) in the project folder. The developer uses these files.
• Stores the Context.txt file in the What's This? Help Files folder, in the Context-Sensitive Help folder. Double-click
the Context.txt file to open the What's This? Help Composer for editing.
Note: Deleting any of these files from Project Manager removes the What's This? Help project from your HTML Help
project.

Use What's This? Help Composer for context-sensitive Help
• Open the HTML Help project, then select this file to open it in What's This? Help Composer.
• Compiling the HTML Help project also complies the context-sensitive topics into your project, as part of the CHM file.
• See What's This? Help Composer's online Help system.

Create What's This? Help
1 Open the RoboHelp project.
2 Select File > New > What's This? Help Project.

Last updated 3/1/2010

USING ROBOHELP HTML 8 246
Context-sensitive Help

3 Select an application. This is the name of the executable file (.exe), dynamic link library (.dll), or ActiveX control

(.ocx).
4 Click Browse. In Files Of Type, select the file format.
5 Navigate to the folder that contains the application. Double-click the application file to select it.
6 Click Next. The name and location of the project file appear.

All What's This? Help Composer projects are titled "Context.txt" and are saved in the same folder as the HTML
Help project.
7 Click Next. The names of all files containing dialog boxes for the application appear. These files are in the same

folder as the application (or they are called by the application). The files listed are included in the What's This? Help
project. You can remove unwanted files. If you are unsure about what files to use, consult your application
developer.
8 Click Next. What's This? Help Composer can generate Help topics for default buttons such as OK and Cancel.
9 To include these topics, select Yes, Create Default Help Text For This Project.
10 Click Finish.

The application's files are scanned and a database of information is generated. After a few moments, the new project
opens in What's This Help Composer and a summary report appears. You can view this report, copy it to the
Windows clipboard, and print it.
11 When you finish working with the summary report, click OK.

All the components of the dialog boxes and windows are identified in the Dialog Boxes pane. You can start
authoring What's This? Help topics.
12 To return to RoboHelp and work on the HTML Help topics, save the What's This? Help project and close the

program.
Version-control projects may have more options.
Tips:
• To work on the What's This? Help topics, open the Help project in RoboHelp, and then open What's This? Help.

• Before you start a What's This? Help project, consult your developer to determine details that might affect the
application files and the way you author topics.

Import What's This? Help projects
You can import existing What's This? Help projects intended for C and C++ applications into your Microsoft HTML
Help projects. You can use only one What's This? Help project with an HTML Help project.
1 Open the RoboHelp project.
2 Select File > Import > What's This? Help Project.
3 Navigate to the What's This? Help project file's (.chj) folder. Double-click to import it.

Version-control projects may have more options.
Notes:
• All What's This? Help project files are saved in the project folder.

• To update What's This? Help topics, edit the Context.txt file. This file is in the Project Manager, in the Text-Only
Topic Files folder (in the Context-Sensitive Help folder). This file cannot be renamed.

USING ROBOHELP HTML 8 247

Last updated 3/1/2010

Context-sensitive Help

• To open your project in What's This? Help Composer, double-click the Context.txt file.

Open What's This? Help projects
1 Open the project in RoboHelp.
2 Select View > Pods > Project Set-up.
3 Select Edit > What's This? Help Project. The project opens in What's This? Help Composer.

Note: Only HTML Help systems that are intended for C or C++ applications are supported by What's This? Help
Composer.

Remove What's This? Help from a project
1 Open the HTML Help project.
2 Select View > Pods > Project Set-up. The Project Set-up pod appears.
3 Open the Context-Sensitive Help folder.
4 Open the Text-Only Topics folder.
5 Select Context.Txt (the What's This? Help file).
6 Click Delete

Version-control projects may have more options.
Note: You can restore a What's This? Help file. The What's This? Help project file (.CHJ) remains in your project folder,
and you can import it into your project to create a CONTEXT.TXT file. See Importing What's This? Help projects into
HTML Help projects.

Test What's This? Help with BugHunter
Note: BugHunter is for use with Microsoft HTML Help projects only.
1 Before testing, verify that the following requirements are met:

• The application used with the Help topics is available on the authoring system.
• What's This? Help topics exist in the HTML Help project (CHM file).
• The application is programmed to use HTML Help.
• A copy of the map file is available for use in testing.
2 Generate the HTML Help project so all the What's This? Help topics are included in the CHM file. Copy the file

into the same folder as the application.
3 Select Tools > Enable BugHunter.
4 Start the application and open a dialog box to test.
5 Click the question mark icon

and click a field or control.

Test HTML Help API
Test map numbers and window-level topics with map IDs in Microsoft HTML Help projects. To run the test, you must
have access to the application. To recompile the CHM file after using this tool, close the program and reopen the
project.
Select A Compiled HTML Help File Specifies the HTML Help (CHM) file to use.

USING ROBOHELP HTML 8 248

Last updated 3/1/2010

Context-sensitive Help

Command Test a map number or a topic. HH_DISPLAY_TOPIC requires the relative path and filename in the HTML

File field.
Dialog (Optional) Identifies the custom window for topic content. Use only if you have a custom window for
displaying window-level Help topics.
HTML File The HTML file to test for with HH_Display_Topic.
Map Number The map number to test for HH_Help_Context.

Troubleshoot What's This? Help
Note: Microsoft HTML Help projects only.
Before you test What's This? Help with BugHunter, right-click in the BugHunter pane and select Options > Display
Options. Deselect Only Window-Level Help Messages.
Problem

Topic does not appear.

Error message

No message

Cause

Author did not create a text-only topic (for a field or control in a dialog).

Resolution

Create a text-only topic for the field or control in the dialog box.
For developer-supplied map files, import the file first, then create text-only topics.
Compile the project. Retest using the updated CHM file.

Problem

The wrong What's This? Help topic appears in a field or control.

Error message

Command: HH_TP_HELP_WM_HELP?HH_TP_HELP_CONTEXT_MENU
Processing: Project_Name.chm
Control ID: 1174
Help ID: 1003
File: Folder_Name/FileName.TXT

Cause

Developer incorrectly handled a message that requests What's This? Help.

Resolution

Provide the Map IDs report to the developer.
Text-only topics are indicated by Text-only Popup MapID.
Compile the project. Retest using the updated CHM file.

USING ROBOHELP HTML 8 249

Last updated 3/1/2010

Context-sensitive Help

Problem

The wrong topic or no topic appears.

Error message

No message
or
Command: HH_TP_HELP_WM_HELP?HH_TP_HELP_CONTEXT_MENU
Processing: Project_Name.chm
Control ID: 1174
Help ID: 1003
File: Folder_Name/FileName.TXT

Cause

A map number in the map file is missing its matching topic ID.
or
A topic ID is matched to the wrong topic.

Resolution

If the problem is caused by a missing topic ID, correct the map file.
If the developer supplies the map file, update the map file.
For an auto-generated map file: Open the Context-Sensitive Text-Only Topics dialog box. Select
the map number. Enter the topic ID. Click Add/Update.
If the problem is caused by a topic ID matched to the wrong topic, remove the text-only topic.
Create one for the topic ID.
Compile the project. Retest using the updated CHM file.

Maintaining text-only topics (Microsoft HTML Help
projects)
When changes are made to the application, update your text-only topics to reflect these changes. (If you use What's
This? Help Composer, most of these maintenance issues apply.)
Changes in the application affect the following:

• The map files used in your project.
• The content in your text-only topics that explain how to use the application's features.
• The text-only topic files (.TXT) you create for What's This? Help.
Type of Change

Action

Obsolete features (dialog boxes, message boxes, and windows
are removed from the application).

Remove the text-only topics from the text-only files (.txt).

Updated and improved features (a dialog box is changed to
include new controls, some fields are removed).

Edit the content of the text-only topics so they accurately
explain how to use the features or if fields were removed from
dialog boxes.

New features (for example, new dialog boxes are added).

Create new text-only topics.

New map files (for new features).

Import the map files into the project before creating the textonly topics.

Updated map files (for new or existing features).

Update the existing map file by removing the obsolete map file
and importing the updated one.

Last updated 3/1/2010

USING ROBOHELP HTML 8 250
Context-sensitive Help

Notes:
• If you are creating text-only topics and window-level topics, avoid using the same map file for both.

• Each time you update your context-sensitive Help, test all topics that have been changed or added.

Working with text-only topics
Create text-only topics
When creating text-only topic files for Microsoft HTML Help, you create topics and write content in the same dialog
box. If using map files from your developer, import them before you begin.
1 Select View > Pods > Project Set-up. The Project Set-up pod appears.
2 Open the Context-Sensitive Help folder.
3 Right-click the What's This? Help Files folder. Select Create/Import Text-Only Topic File.
4 In File Name, enter a name for the topic file. If you imported a map file, use its name (Pizza.h and Pizza.txt).
5 Click Open.
6 Select a topic ID for the first topic to create:

• When auto-creating a map file In Topic ID, enter the topic ID.
• When importing a map file, select the topic ID from the list.
Sample of Topic ID entries
7 In Topic Text, enter topic content. This text appears in a popup when users request help for the field or control:

Sample of Topic Text

❖ Click Add/Update.

Version-control projects may have more options.
Tips:
• Topics or added code are not needed for OK, Cancel, Save, Open, and other buttons associated with Windows
dialogs.

• HTML Help projects can include multiple .txt files.

Edit text-only topics
1 Select View > Pods > Project Set-up. The Project Set-up pod appears.
2 Open the Context-Sensitive Help and What's This? Help Files folders.

Last updated 3/1/2010

USING ROBOHELP HTML 8 251
Context-sensitive Help

3 Double-click the topic file (.TXT).
4 Select the topic from the Topic ID list.
5 Edit the text in Topic Text.
6 Click Add/Update.

Version-control projects may have more options.
You can edit map numbers in this dialog.

Test text-only topics
Testing text-only topics requires access to the application.

• If you auto-generated map files, give these files to your developer.
• When done testing, compile the Help. Provide your developer with the CHM file.
• Install the latest version of the application, including the latest CHM file.
• If installing the latest application from a network or CD, replace the existing CHM file with the new copy when you
compile. Copy the CHM file into the folder with the application EXE file.

• Print a Map IDs report as a checklist for testing dialog boxes. Print the text-only topics file that matches topic IDs
to topics.
Tips:
• Use BugHunter to test application calls.

• Use the Duplicate Map IDs to resolve problems with repeated map numbers.

Remove text-only topics
You can remove text-only topics in Microsoft HTML Help projects when changes to dialog box controls and fields
affect context-sensitive Help.
1 Select View > Pods > Project Set-up. The Project Set-up pod appears.
2 Open the Context-Sensitive Help and What's This? Help Files folders.
3 Double-click the topic file (.txt).
4 Select the topic to remove.
5 Click Delete.

Version-control projects may have more options.
Tips:
• If your developer provides updated map files, replace them before removing the topic.

• Removing text-only topics leaves the topic ID and map number in the map file. You can remove unused Map IDs
if you no longer need them.

USING ROBOHELP HTML 8 252

Last updated 3/1/2010

Context-sensitive Help

Remove text-only topic files
Remove text-only topic files (.txt) from Microsoft HTML Help projects when you no longer need them.
1 Select View > Pods > Project Set-up. The Project Set-up pod appears.
2 Open the Context-Sensitive Help and What's This? Help Files folders.
3 Select the topic file (.txt).
4 Click Delete.
5 Open the Map Files folder.
6 Select the map file (.H) associated with the removed .txt file.
7 Click Delete. The topic file and its map file are deleted.

Version-control projects may have more options.

Testing context-sensitive Help
Test with the Context-Sensitive Help tool
The Context-Sensitive Help tool simulates Help calls from an application.
1 In the Tools pod, double-click CSH Test.
2 Do one of the following:

• To test server-based Help, select Online.
• To test local Help, select Offline.
3 Do one of the following:

• For server-based Help, enter the server location and project name by using the following syntax for FlashHelp Pro:
http://RoboHelp Server/robohelp/server?project=MyProject&area=area-name&type=flashhelp

For WebHelp Pro, use the following syntax:
http://RoboHelp Server/robohelp/server?project=MyProject&area=area-name&ver=1

• For local Help, click the Browse button, and select a Help file.
4 (Optional) Enter a window name.
5 Click the map file icon

and select a map file.

6 Click the triangle and select a map number.
7 Click Show Help.

If Help is working correctly, the topic associated with the map number appears.

Test with BugHunter for HTML Help
Note: Microsoft HTML Help projects only.
BugHunter is a troubleshooting tool to test context-sensitive Help topics and diagnose problems. During testing,
BugHunter captures and displays calls that the application makes.

Last updated 3/1/2010

USING ROBOHELP HTML 8 253
Context-sensitive Help

Use BugHunter for the following tasks:

• Test Help buttons, F1 Help, or What's This? Help.
• Track the causes of errors.
• Copy data to the clipboard or annotate it and save it in a text file.
• Discover why the wrong topic appears.
• Determine if a particular map number is used.
• Determine if a window-level Help topic has a map ID assigned.

Start and close BugHunter
1 Select View > Pods > BugHunter.
2 Do one of the following:

• To start capturing data, right-click inside the pane and select Enable BugHunter.
The output dialog box displays capture data while the program is enabled. When you activate Help in an
application's dialog box, messages from BugHunter appear in the output window. Right-click in the pane to
copy, annotate, or save the data.

• To clear the pane, right-click inside it and select Clear All. Data remains in the pane until you clear it.
• To stop capturing data, right-click inside the pane and deselect Disable BugHunter.

Interpret BugHunter data
BugHunter data resembles this example:
C:\APPLICATION FOLDER\HELP_FILE.CHM, Custom Folder\Help_Topic_Name.htm, HH_HELP_CONTEXT,
10253, Topic launched

Multiple lines of data resemble this example:
Project: C:\APP FOLDER\HELP_FILE.CHM
File: Custom Folder\Help _Topic_Name.htm
Command: HH_HELP_CONTEXT
Map Number: 10253
Result: Topic launched

Interpret the data as follows:
Project Application location. Filename of the HTML Help that contains the called Help topic.
File Folder and subfolders where the .htm topic exists.
Command The command name sent to HTML Help.
10253 Map number.
Result Activity summary. “Topic launched” indicates that the topic map ID matches the application code.

Customize the BugHunter pane
❖ Right-click inside the BugHunter pane and click Options.

View map numbers in hex format
1 Select Tools > Options. Click the BugHunter tab.
2 In Display options, select Map Numbers In Hex.

Last updated 3/1/2010

USING ROBOHELP HTML 8 254
Context-sensitive Help

Test in the application
To test context-sensitive Help in the application, follow these guidelines:

• If you auto-generated map IDs in RoboHelp, export the map files and provide them to the developer. Update the
application to use the map IDs, if it doesn’t already.

• Generate the project. Provide the output files to the developer.
• If you designed a custom window for displaying window-level topics, inform the developer. The application
requires coding to display topics this way.

• Install the latest version of the application, or access the Web application. If you install the latest build of the
application from a network drive or CD, you can replace the output file with the new copy each time you generate.
Put the output files in the same folder as the application EXE file.

• Print the Map IDs report. Use it as a checklist for testing dialog boxes.
• In the application, click Help or press F1 to verify that the correct Help topic opens in each dialog box.
• Update any map IDs that did not work and check the following:
• Ensure that the correct map ID is assigned.
• Ensure that the topic has a window assigned to it.
• Generate the project to retest edited topics.

Context-sensitive Help terms
ALI file A project file that is automatically created in the project folder when you add, update, or remove map IDs. It
shows the topic ID/topic match (for example: ID_ABCForm=ABC.htm).
CHM file The file created when an author compiles a Microsoft HTML Help project. All the files in the project,

including context-sensitive Help topics and map files, are compressed and saved in this file.
Header file A developer's term used to see map files. Developers create header files, which are text files containing a

list of topic IDs and their corresponding map numbers. Header files use the .h, .hh, or .hm extension. When a
developer provides the author with header files, the author needs to import the files into the project.
HHCTRL.OCX (Microsoft HTML Help projects) The Microsoft ActiveX control that contains the HtmlHelp()

application programming interfaces. Developers ensure that HHCTRL.OCX is invoked when users request Help.
HH_HELP_CONTEXT (Microsoft HTML Help projects) Using this HTML Help API command, calls can be made to the

application using the map number.
HTML Help API (Microsoft HTML Help projects) The application programming interface for Microsoft HTML Help
that allows a Help window from an application to display. The HTML Help API contains commands for developers to
specify the type, style, and position of Help windows.
HTML Help translator (Microsoft HTML Help projects) A mechanism in Microsoft HTML Help that looks up
context-sensitive Help topics when users request help in applications.
HTML Help viewer (Microsoft HTML Help projects) The default window used to display compiled Microsoft HTML
Help (CHM files). Authors can also design a separate custom window to display context-sensitive Help topics.
Prefix Characters affixed to the beginning of topic IDs (for example, in the topic ID, Idd_Mytopicid, "IDD_" is the

prefix). Development tools that generate map files use a default prefix. When you generate map files in RoboHelp, you
can specify a prefix. Prefixes are not mandatory, but they are useful for organizing topic IDs.

Last updated 3/1/2010

USING ROBOHELP HTML 8 255
Context-sensitive Help

RH ShowHelp RoboHelp API function used to call context-sensitive Help topics. You can call this function for
WebHelp Pro, WebHelp, and HTML Help.
Support files (WebHelp and WebHelp Pro projects) Adobe provides support files that allow developers to import
code and enter variables. Each supported language has a corresponding support file with functions to use for calling
WebHelp Pro or WebHelp projects and displaying individual topics for context-sensitive Help.

Reference
BugHunter tab of the Options dialog box (HTML Help)
Display options
Window-Level Help Messages captures messages only for window-level Help.
Clear this option to test What's This? Help.
Map Numbers In Hex Displays map numbers in hexadecimal notation rather than decimal format.
Each Message On A Single Line Displays output on a single line. Multiple lines organize the data by the type of

information.
Example (single line)
C:\APPLICATION FOLDER\HELP_FILE.CHM, Custom Folder\Help_Topic_Name.htm, HH_HELP_CONTEXT,
10253, Topic launched

Example (multiple lines)
Project: C:\APPLICATION FOLDER\HELP_FILE.CHM
File: Custom Folder\Help_Topic_Name.htm
Command: HH_HELP_CONTEXT
Map Number: 10253
Result: Topic launched

Color options
Select the color for displaying Help, error messages, prompts, annotations, and the window background color.

256

Last updated 3/1/2010

Chapter 12: Generating Help and printed
documents
Single sourcing basics
About single-source layouts
Single-source layouts act as templates for different versions of the project output. RoboHelp provides single-source
layouts for each output type.
Typically, when generating a different version of the project (such as an online tutorial), you use different settings for
the output. You can save these settings in single-source layouts. After creating the layout and defining output settings,
generate, view, or publish output whenever needed, singly or in batches.
Layouts save settings and preferences for each version of the project, helping to ensure consistency. Conditional tags
and conditional build expressions let you create different output for different versions of a project.

More Help topics
“Work with layout types” on page 257

Specify the primary layout
A primary layout is the default layout that you set for the work environment. It lets you generate output without
specifying additional options. The primary layout contains settings for the output type with which it is associated.
1 In the Single Source Layouts pod, right-click a layout.
2 Select Set As Primary Layout.

The primary layout is labeled in the Single Source Layouts pod.
Note: If you create new windows, the window type is based on the default layout.

Create and edit single-source layouts
Create or duplicate single-source layouts
A duplicate layout retains the settings of the original.
1 In the Single Source Layouts pod, do one of the following:

• To create a layout, click the Create Layout button

• To duplicate a layout, click the Duplicate Layout button
2 In the Layout Name box, type a name.
3 For a new layout, select an output type from the pop-up menu.

Note: You cannot change the output type of a duplicated layout.
4 Click OK.

USING ROBOHELP HTML 8 257

Last updated 3/1/2010

Generating Help and printed documents

5 For a new layout, set options in the Properties dialog box that appears. Click Save.

Edit single-source layouts
1 In the Single Source Layouts pod, right-click the layout.
2 Select Properties.
3 Set options. Click Save.

Note: You cannot change the Output Type of a layout. Create a layout instead.

Rename a single-source layout
1 In the Single Source Layouts pod, right-click the layout.
2 Select Rename.
3 Enter the name.

More Help topics
“Work with layout types” on page 257
“Generate, view, and publish output” on page 274

Remove single-source layouts
Removing a layout does not affect other parts of a project.
1 In the Single Source Layouts pod, right-click the single-source layout. It cannot be the primary layout.
2 Select Delete.

Work with layout types
WebHelp layout
About WebHelp
WebHelp is an uncompiled output type that ensures that users can view web-based or desktop application Help on
any browser and platform. It supports standard Help features and provides customizing capabilities.
You can author content in another HTML editor, such as Adobe Dreamweaver, and still take advantage of the
WebHelp navigational and organizational Help features.
WebHelp also provides client project merging and a context-sensitive Help API.
For older browsers that don’t support DHTML (used to display the navigation pane), WebHelp displays the navigation
pane using another supported format.

USING ROBOHELP HTML 8 258

Last updated 3/1/2010

Generating Help and printed documents

Differences between WebHelp and Microsoft HTML Help
WebHelp

Microsoft HTML Help

Supported by a web browser

Relies on Microsoft HTML Help engine for support

Uncompiled set of output files

Compiled and compressed (CHM file)

Runs on any platform

Requires 32-bit Windows platforms

Ideally suited for server-based distribution

Workarounds required for server-based distribution

Mac OS limitations for WebHelp
• Mac OS filenames have a 32-character limit.

• Output is displayed as HTML lists instead of DHTML.
• BMP image files don’t appear properly.

Add or remove search highlights in WebHelp
In a WebHelp system, search results are highlighted by default in the displayed topics.
Note: WebHelp, WebHelp Pro, FlashHelp, and FlashHelp Pro projects use the same procedure to enable Search highlight.
1 Double-click the WebHelp layout.
2 In the WebHelp Navigation dialog box, click Next. You also can use the Highlight Search Result option on the

Search pane.
Deselect the Highlight search results checkbox to get a clear printout of the search results.
3 Select or deselect Enable Search Highlight Result.
4 Select a highlight color from the pop-up menu.

Creating Section 508-compliant WebHelp
Section 508-compliant output facilitates Help access for users with visual, hearing, or mobility impairments.
Text-to-speech utilities read the contents of the active window, available options, or text you type. These utilities and
screen review aids translate onscreen text to speech or to a dynamic, refreshable, Braille display. This technology can
provide keyboard assistance or shortcuts, captions for speech and sound, and visual warnings such as flashing toolbars.
Consider the following when you create Section 508-compliant WebHelp:

• WebHelp systems generated with the Section 508 option open in all supported browsers. However, view output
with Internet Explorer to ensure compliance.

• For master projects generated using pure HTML or Section 508-compliant WebHelp, the subprojects are available
only from the TOC if you merge WebHelp systems. They are not available from the index or full-text search.
Subprojects appear as a book in the TOC. When users click the subproject TOC book, the subproject opens in a
new browser window.
WebHelp features that support Section 508 compliance
• A Section 508 Compliant option that provides alternative text for images, dynamic elements, frames, forms, and so
on. Visually impaired users using assistive software can hear where they are in the output and what they are
selecting.

USING ROBOHELP HTML 8 259

Last updated 3/1/2010

Generating Help and printed documents

• Alternative text is provided for images of TOC books, pages, and the plus/minus icons, TOC/Search/Index tabs or
panes, navigation buttons, and buttons from design-time controls.

• Other elements with alternative text include expanding and drop-down text, triggers and targets, and pop-up
menus.

• Navigation frames that assistive software can read.
• Generation of HTML tables so that assistive software can identify row and column headers.
• Online forms that assistive software can read.
• Output that more than one mode of operation and information retrieval can use. For example, mobility-impaired
users can use the keyboard or mouse. No features require auditory, visual, or mobility ability alone.
Guidelines to ensure Section 508 compliance in Help systems
• WebHelp is compliant for framesets and navigation. Make sure that other elements in topics are compliant.

• If the Help system contains form buttons or multimedia elements, such as images and audio, provide visual
equivalents, such as screen tips so that assistive software can read from the screen.

• Construct information with multiple methods of access to accommodate disabilities. Offer information in color in
an alternative way that doesn’t use color.

• Use basic external style sheets so that documents are readable if the style sheet is unavailable.
• If a web page uses applets, include a link to the location where users can download the appropriate reader.
• Document keyboard shortcuts and other methods of accessibility.
• Do not use HTML Help controls.

More Help topics
“Generate, view, and publish output” on page 274
“Microsoft HTML Help layout” on page 262
“Create custom skins for WebHelp and WebHelp Pro projects” on page 314
“Merging Help projects” on page 34

WebHelp Pro and FlashHelp Pro layouts
About WebHelp Pro and FlashHelp Pro
WebHelp Pro and FlashHelp Pro layouts deliver server-based output for web and applications. To publish this output
to a server, RoboHelp Server must be installed.
WebHelp Pro is an uncompiled output type that supports standard Help features.
You create WebHelp Pro or FlashHelp Pro projects in RoboHelp, authoring content, adding features, and customizing
the appearance. When you're ready to view and test the output, generate the project. RoboHelp creates output files in
a single folder within the project folder.
RoboHelp Server-based Help offers these advantages:
Increased speed The Contents, Index, and Search tabs appear more quickly.
Usage information logged in a database Access the database to improve applications.

USING ROBOHELP HTML 8 260

Last updated 3/1/2010

Generating Help and printed documents

Runtime project merging Merge multiple projects at runtime or when accessing the Help system from a server.
Window properties Server access accommodates Toolbar, Menu, Location Bar, and Status Bar options. To set these
tool properties, double-click a window in the Windows folder of the Project Set-up pod.

About RoboHelp Server
RoboHelp Server lets you create, deliver, and measure web-based Help systems. It stores information about how users
navigate and interact with the Help system and produces reports. RoboHelp Server hosts and displays any content you
create with RoboHelp.
Reports

Authoring Tool

Project A

Project B

Project C

RoboHelp Server

Database

IIS

Users
RoboHelp Server interaction with Help-building components

Convert desktop Help to WebHelp Pro
1 Contact the server administrator or IT department to ensure that RoboHelp Server is installed and to learn its

name.
2 Find the path or location of RoboHelp Server and specify it in the project.
3 Open the project in RoboHelp. Set WebHelp Pro as the output.
4 Connect to the server by publishing the project files.
5 To access the server, enter its domain name in the browser address bar. Ask the server administrator for the URL.
6 View the output. To view reports, click the Usage Reports tab in the program window. Click Connect Now.

More Help topics
“Specify the primary layout” on page 256
“View output” on page 285
“Publish output” on page 287

FlashHelp layout
About FlashHelp
FlashHelp solves DHTML limitations for browsers and platforms and high-security firewall issues. Users need only
Flash Player 8 or later and a web browser to view the Help system. Nearly all browsers have Flash Player installed.

USING ROBOHELP HTML 8 261

Last updated 3/1/2010

Generating Help and printed documents

FlashHelp supports the traditional tri-pane Help system layout (toolbar on top, navigation at left, content at right). It
can also generate Help systems in a vertical orientation that minimizes the required screen area by stacking the
navigation above the Help content.
FlashHelp consists of these layers:
Presentation Layer Uses Adobe Flash for its platform-neutrality and configurability.
Navigation Layer Uses XML data structures to define and control elements such as the table of contents, index,

glossary, and full-text search.
Content Layer Uses HTML and related technologies to render content with full fidelity.

A skin is required for the FlashHelp output. Use the default RoboHelp skin, specify a skin from the gallery, or create a
custom skin with the Skin Development Kit (SDK) provided with RoboHelp.

More Help topics
“Skins” on page 311

Project source files for FlashHelp
Note: When distributing HTML Help systems, include the CHM file, and all linked secondary CHM files, HLP files, and
CNT files.
Project source files (generated at the top level of the project folder)
Other project files (created when building and generating a project)
Filename extension

Description

*.chm

Compressed output for compiled HTML Help, used to view the Help system.

(HTML Help only)

CHM files added as subprojects to a master project must also be in the same folder as the master
project.

CONTEXT.txt

Text-only topics file added to context-sensitive Help in the What's This? Help Composer.

(HTML Help only)
*.fhs

Information about FlashHelp skins.

*.hlp

WinHelp file compiled if the project includes links to WinHelp topics. Not included in the CHM
file and must be shipped separately. (For WinHelp 4, also distribute the .cnt file.)

(HTML Help only)
*.hhp

Created when generating a CHM file.

*.htt

Topic template file.

*.htm, *.html

Topic content.

*.skn

Information about WebHelp or WebHelp Pro skins.

(WebHelp, WebHelp Pro only)
*.txt

Project compilation log.

Log file
(HTML Help only)
*.txt
Text-only topics

Text-only file for context-sensitive Help topics (What's This? Help), included in the compiled
CHM file.

USING ROBOHELP HTML 8 262

Last updated 3/1/2010

Generating Help and printed documents

Microsoft HTML Help layout
About Microsoft HTML Help
Microsoft HTML Help is an online Help standard based on HTML.
HTML uses tags to mark elements, such as text and graphics, in a document with display instructions. HTML Help
includes HTML documents (HTM files) for the topics, along with project source files. You use RoboHelp to add
features such as links, a table of contents, an index, special effects, and related topics buttons.
You distribute a compressed file (CHM) to users that they view in the HTML Help viewer.
The main components of HTML Help include the following:
HTML Help ActiveX control Supports navigation features such as the table of contents, index, and link controls (related
topics and keyword links). It also supports HTML Help controls: WinHelp topic links, startup screens, and close
window controls.
Layout engine Microsoft Internet Explorer 6 and later supply the required components for HTML Help support.
HTML Help viewer Displays compiled HTML Help (CHM file). It uses components of the Internet Explorer browser
while displaying content in its proprietary window interface.
Compressed HTML A collection of all files in the project in a single CHM file that occupies less disk space and is faster

to load. You can ship this compiled file with an application or distribute it to users as a stand-alone online document.

Generating Microsoft HTML Help
The RoboHelp Help compiler processes all source files into a distributable format, which can then be tested or
distributed.
You can generate the output at any stage in the project.
Compiler Messages
The compiler displays messages, statistics, and compiling errors during generation. If the compiler finds problems
with the source files, error messages appear:
Notes Conditions that probably do not cause a serious problem in the output. Note numbers range from 1000

through 2999.
Warnings Conditions that result in defective output. For example, if the compiler cannot locate an image, it displays

a warning and continues generating. Warning numbers range from 3000 through 4999.
Errors Conditions that stop the compiler. You can't generate the output until you correct the error. Error numbers

range from 5000 through 6999.
Internal Errors Errors caused by the HTML Help Workshop program. Internal error numbers are 7000 and greater.

Link TOC books or pages to custom windows (Microsoft HTML Help)
1 Right-click a topic in the TOC pod, select New > Book or Page, and click the Advanced tab.
2 Specify the options for displaying the TOC book or page:
Window Specify the custom window in which the topic is displayed.
Frame Specify the frame in which the topic is displayed. Custom framesets appear in this list.
Comment TOC comments are not visible to users.

USING ROBOHELP HTML 8 263

Last updated 3/1/2010

Generating Help and printed documents

Image Select custom icons for displaying the book or page in the TOC. Click the pop-up menu

and press the
Down Arrow key to move through the list of available icons. Select different icons for the closed book state and the
open book state.
Note: Generate and view the Contents tab in the HTML Help viewer to display custom icons.
Mark As New Displays a red star with the TOC book or page icon to indicate new items to end users. The standard

icons look like the following:

•

New book

•

New page

Use Information Types This option is only available when Book With Link is selected on the General tab. Select it

to use a TOC book or page with information types.
Information Types Click Add to select topics for the information type. Click Edit to change an information type,

and click Remove to delete an information type.
Types Display book or page information types.

3 Click OK.

Extract CHM files
You can extract source files from a compiled Microsoft HTML Help file (CHM).
1 In the Toolbox pod, double-click HTML Help Studio.
2 Select File > Open, and then select a CHM file. Click Open.
3 Do either of the following:

• To extract an individual file or folder, select it and click the Extract button

• To extract all files, click the Extract button. Select All Files.
4 Specify a destination for Extract To.
5 Click Extract.

Rename CHM files
The CHM filename is based on the project filename (.xpj).
1 In the Single Source Layouts pod, right-click HTML Help. Select Properties.
2 In Output Folder And Filename, type a name for the file, including the .chm extension.
3 Click Save.

The CHM file is renamed the next time you generate Help.

Find HTML Help files and components
1 In the Toolbox pod, double-click Find HTML Help Files or Find HTML Help Components.
2 Click Search.

To rearrange or resize columns, drag their headings or separator bars.

USING ROBOHELP HTML 8 264

Last updated 3/1/2010

Generating Help and printed documents

Replace CHM files
1 In the Toolbox pod, double-click HTML Help Registration.

The Name column lists CHM files that are currently registered on the authoring system.
2 Select the CHM file to replace.
3 Click Edit.
4 Click the browse button

and navigate to the replacement CHM file.

5 Select the file, and click Open. Click OK.

Note: Replacing a CHM file does not affect how users view the Help project.

Register or unregister CHM files
Sometimes compiled Microsoft HTML Help files (CHM) are registered if they are used with applications. You register
CHM files on the authoring system. Registering the files doesn't affect how users view the Help project after it's
distributed.
❖ In the Toolbox pod, double-click HTML Help Registration.

• To register a CHM file, click Register. Navigate to the CHM file, and click Open. Click OK.
• To unregister a CHM file, select it and click Unregister. Click OK.

JavaHelp layout
About JavaHelp
JavaHelp is a compressed output type that works with applications written in the Java programming language.
JavaHelp and Java applications run on various platforms.
RoboHelp provides support for the JavaHelp format and automatically creates all Java-based Help features and the
HTML-based features such as HTML content and hypertext links. You can also leverage existing WinHelp and HTML
projects to create JavaHelp systems. A file compression feature is available for distributing the JavaHelp system.
JavaHelp is a compressed file (JAR file) or a set of files used to run a Help system for a Java application. RoboHelp
copies all the files to distribute into the JavaHelp folder, or into a JAR file if you choose to compile Help.
Authoring requirements
• Sun Java 2 SDK or later

•

JavaHelp 1.1.3 or later

User requirements
• Java Runtime Environment (JRE) 1.2.1 or later

• JavaHelp 1.1.3 or later

Generate JavaHelp output
Generating JavaHelp saves the source files in the project subfolder JavaHelp (default).

USING ROBOHELP HTML 8 265

Last updated 3/1/2010

Generating Help and printed documents

When you generate JavaHelp files, RoboHelp can translate Related Topics controls into controls specifically for
JavaHelp.
1 Place the Bsscjhrc.jar file in the application extensions folder, or in the class path passed to the Java Virtual Machine

(Java.exe).
2 Incorporate related topics controls in the topics.
3 Generate the output.

Note: If question marks appear instead of Related Topics controls, the Bsscjhrc.jar file is not in the correct location.

More Help topics
“Generate output” on page 275

Merge JavaHelp projects
❖ Add a reference to an external HelpSet file (.hs) when you generate the output.

Adding the reference merges all elements in the external HelpSet file with the existing project.
Note: You can add external navigation views (TOC, index, search) as remote views. However, adding the reference to an
external HS file adds all views, with other project files, to the existing project.

JavaHelp limitations
Capitalization Supports all caps and small caps.
Custom colors Some custom colors don’t appear accurately in the JavaHelp viewer.
Expanding glossary hotspot definitions Appear inline.
Fonts Fonts are automatically set to JavaHelp default fonts. Font size is unsupported.
Forms Only simple forms appear properly in the JavaHelp viewer.
Framesets Unsupported.
HTML files generated by Word 2000 or later Unsupported.
HTML Help controls Supports WinHelp topic, Shortcut, Table of Contents, Index, Splash Screen, Close Window, and

HHCTRL Version.
Images Don’t appear consistently in compressed JavaHelp. Background images and image maps are unsupported.
Links Supports links to e-mail addresses, FTP sites, and external files.
Lists Only simple bulleted or numbered lists appear properly in the JavaHelp viewer.
Multimedia Supports sound files, such as WAV or MIDI, and video files, such as AVI.
Paragraph alignment Supports tags, such as P align=”center”.
Plain text Supports non-HTML files.
Pop-up links The pop-up note window does not have a bottom border if the entire pop-up note is contained within

the content frame. This limitation does not apply to text-only pop-up notes.
Special effects Supports ActiveX controls, DHTML, JavaScript, startup screens, and Visual Basic scripts.
Style sheets Support for partial cascading style sheets is provided with JavaHelp 1.1. (External style sheets work

correctly.) You can use level 1 cascading style sheets with the Sun Java 2 JDK or later, or Swing 1.1.1 with Sun Java 2
JDK or later.

USING ROBOHELP HTML 8 266

Last updated 3/1/2010

Generating Help and printed documents

Table attributes The following attributes are unsupported:

• Values set in the initial tag (TABLE) of a table override cell width specifications.
• The table width attribute (TABLE WIDTH) functions when specified in absolute pixels, but not in percentages.
• When used within the TABLE tag, the background color attribute (BGCOLOR) does not function.
• When used within the TABLE tag, the break tag (BR) causes the table cell to expand by the number of BR tags used.
Note: This feature is supported in JavaHelp 1.1.3 and later.

• Table alignment cannot be set precisely.
Text animations and effects Unsupported.

Oracle Help layout
About Oracle Help
Oracle Help is an output type that works with applications written in Java or any other programming language.
Oracle Help is a compressed file (.jar) or a set of files used to run a Help system for an application. When you generate
Oracle Help, the files to distribute are created in a single output folder.
Authoring requirements
• Oracle Help components, version 3.2.2, or 4.1.2 or later
Note: Version 3.2.2 is built using the Oracle internal Java GUI tool kit called EWT. Version 4.1.2 is built using Java
Foundation Classes. The functionality, APIs, and supported file formats are the same in both versions. To build
applications using JFC, or to build custom navigators for the Help project, use version 4.1.2 or later. If developers are
using Oracle products, use version 3.2.2.

• Sun Java 2 SDK or later
• Java Runtime Environment (JRE), version 1.2.1 or later
Oracle Help includes the Oracle Help components, the Oracle Help viewer, and API documentation for developers.
User requirements
• Oracle Help components (version 3.2.2, or 4.1.2 or later)

• The Oracle Help project (as either a compiled JAR file or a folder containing individual source files)
• Sun Java SDK (version 2 or later) or Java Runtime Environment (version 1.2.1 or later)
Note: When compiling Oracle Help, make sure to set the encoding type to utf-8 (-Dfile.encoding=UTF8) while calling the
java compiler command. This ensures that the help is properly generated and can be displayed on all systems.

Update topic IDs for Oracle Help
Oracle Help uses topic IDs (in a map file) to make context-sensitive Help calls. You can change the topic ID by editing
the topic meta tag.
1 Open the topic in the HTML Editor.
2 In the meta tag area, insert the new topic ID in the NewTopicID tag.

Last updated 3/1/2010

USING ROBOHELP HTML 8 267
Generating Help and printed documents

Notes:
• If two topics have the same topic title, the latter is assigned another ID when you generate. For example, TopicID
becomes TopicID1.

• If two topics have the same topic ID meta tag, a warning is displayed in the Output View when you generate.
• If a topic has no title or meta tag specifying the topic ID, RoboHelp creates a topic ID based on the filename.

Set the topic window for Oracle Help
Specify a window in which topics appear by editing the topic meta tag in the Design Editor. If you specify no window,
the default window is used.
1 Open the topic in the HTML Editor.
2 Edit the meta tag.
meta name = "window-type" content = ["window name"]

Oracle Help remote views
Oracle Help uses views to define the contents of the Navigator left pane: TOC, keyword index, and full-text search.
You can also add remote views to Oracle Help projects. A remote view is an external table of contents, index, or fulltext search database. Use remote views if you are merging smaller projects into one master project. You can specify
that a remote view remain in its own tab, or merge with an existing view. By default, Oracle Help merges all views
having the same engine, type, and label.
Oracle Help makes an important distinction between labels and titles:
Labels Assigned to tabs.
Titles Assigned to top-level books or nodes in the TOC.

Merge Oracle Help projects
❖ Add a reference to an external HelpSet file (with the .hs extension) when you generate Oracle Help.
Adding a reference to an external HS file adds all views, with other project files, to the existing project.
Oracle Help indexes
One level of indenting is supported. Users can search for keywords in the list. As keywords are selected, topics are listed
in the lower pane. Double-clicking a topic in the lower pane displays its content in the topic window on the right.
You can import external indexes and merge them using Oracle Help remote views. You can create separate tabs for
each index or you can merge them.

Last updated 3/1/2010

USING ROBOHELP HTML 8 268
Generating Help and printed documents

Example of an Oracle Help index

Oracle Help full-text search
Oracle Help displays search results by relevance, not alphabetically. You can import full-text search databases from
other projects using Oracle Help remote views.

Example of an Oracle Help full-text search

USING ROBOHELP HTML 8 269

Last updated 3/1/2010

Generating Help and printed documents

Oracle Help limitations
Not all limitations apply to every Oracle Help project.
Capitalization Supports all caps and small caps.
Expanding glossary hotspot definitions Appear inline.
Fonts Limited font support.
Glossary pane Unsupported if you use Glossary Designer.
HTML Help controls Supports WinHelp topic, Shortcut, Table of Contents, Index, Splash Screen, Close Window, and

HHCTRL Version.
Links Supports links to e-mail addresses, FTP sites, and external files.
Lists Only simple bulleted or numbered lists appear properly in the Oracle Help viewer.
Multimedia Supports sound files, such as WAV or MIDI, and video files, such as AVI.
Plain text Supports non-HTML files.
Special effects Supports ActiveX controls, DHTML, JavaScript, startup screens, and Visual Basic scripts.
Unsupported DHTML appears as plain text in generated Oracle Help projects.
Text animations and effects Unsupported.

XML layout
RoboHelp uses handlers to convert XML to HTML and import XML files into topics. Handlers can also export topics
or even entire projects as XML. You can create or customize XML handlers using the HDF Editor.
The following predefined handler files are available:
Import DocBook As Topics Imports the selected DocBook files as HTML topics.
Import XHTML (*.XML) Imports the selected XHTML files as HTML topics.
Import XML (CSS/XSL) If the selected XML file has an associated style sheet (CSS or XSL file), this handler imports the
XML file as an HTML topic, including formatting. If the selected XML file lacks an associated style sheet, this handler
converts the XML file to an HTML file without formatting. This import option also provides advanced import options.
You can import the XML file as text flow or tree flow or select a customized CSS or XSL file.

Note: If all the HDF files (and therefore handlers) have been deleted, you cannot access the XML import or output
functionality. Use the XML Handler Manager to import an HDF file containing a handler or reinstall RoboHelp to enable
this functionality.

More Help topics
“Set options for generating XML output” on page 284
“Import XML files” on page 85

Adobe AIR layout
You use the Adobe AIR layout to generate Help as an Adobe AIR application, browser-based Help (with the theme
and skin of an Adobe AIR application), or a packaged data file that can be viewed in an AIR Help viewer.
Adobe AIR is a cross-platform runtime for building and deploying applications that connect the desktop to the web.
For a list of benefits of generating output in the Adobe AIR layout, see “About output types” on page 22.

USING ROBOHELP HTML 8 270

Last updated 3/1/2010

Generating Help and printed documents

For more information about Help applications using Adobe AIR, see
www.adobe.com/devnet/robohelp/articles/air_help.html.

Configure the Adobe AIR layout
You configure the Adobe AIR layout from the Adobe AIR option in the Single Source Layouts pod. In the Adobe AIR
dialog box, you can select the output type, configure the installer settings, and define how the Help content is presented
to the users.
❖ Select Adobe AIR from the Single Source Layouts pod and do one of the following:

• Right-click and select Properties from the context menu.
• Select Edit > Properties.
Select Help output
You can select one of the four output options for Adobe AIR:
❖ In the General tab of the Adobe AIR dialog box, select the output type:
Adobe AIR Application Generates Adobe AIR output as embedded Help. The Help system is created as a single AIR
application installer. You can install the AIR application locally or distribute it to your users. Users can update their
installed Help system based on Adobe AIR whenever an update is available on the web. For more information about
autoupdates, see the AutoUpdating section in the Adobe AIR Help article by Peter Grainge.

Note: You need JRE 1.6 or higher installed on your system to install the Adobe AIR application.
Browser Based Help Generates browser-based Help as an Adobe Flex application that you can use as online or

embedded Help. You can upload this output to the server with specific configurations. Users can view this Help
using a browser with Adobe Flash plug-in 9.0 or later installed.
Note: Browser-based Help does not support Adobe AIR application features such as commenting, favorites, resources,
RSS, and auto-update.
AIR Application And Browser Based Help Generates the Help system in two formats simultaneously: Adobe AIR

application and browser-based Help. You can view the AIR application after installing it on your computer. You
can view the browser-based Help by uploading it to a server. The two Help systems are independent of each other.
Help Content Only Generates the Help system as a data file (RHA) that you can view in a Help viewer. Use the Help

Viewer wizard in RoboHelp to create a Help viewer. To view multiple files in a single view, you can write the
location of all those files in a HelpConfig file.
Note: For the syntax of the HelpConfig file, see “Create and locate a Help configuration file” on page 287
Configure Help settings
❖ In the General tab of the Adobe AIR dialog box, set the following.
Output Location of AIR File Click Browse to select a folder for the Help application installer (AIR file) and specify

a name. By default, RoboHelp names the Help application installer by appending .air to your project name.
Output Location of Start Page (Browser-based Help Only) Specify the first page to display in browser-based Help.
Help Title Specify a title for your Help application.
Version Specify a version number for the generated Help application. Typically, you set 1.0 as the version number

for the initial release of your Help application, and increment the version number for subsequent releases. The
incremental version numbers help your users identify updated Help content in their local installations.

USING ROBOHELP HTML 8 271

Last updated 3/1/2010

Generating Help and printed documents

Help ID Specify a unique identifier for the Help application. The Help ID can be alphanumeric and include periods
and hyphens.

Note: When you deliver updated Help, change only the version number. The installed AIR Help uses the combination
of Help ID and Version to identify whether a later version of Help is available.
Configure content
You configure the presentation of content in the Help application.
❖ In the Content tab of the Adobe AIR dialog box, set the following:
Conditional Build Expression Specify a conditional build expression to apply to the output. See “Conditional build

tag expressions” on page 210.
Table Of Contents Select the TOC to be displayed in the generated Help. See “TOCs” on page 153.
Index Select the index to be displayed in the generated Help. See “Indexes” on page 158.
Glossary Select the glossary to be displayed in the generated Help. See “Glossaries” on page 172.
Variable Set Select a variable set to override the default variable set in the generated Help. See “User-defined

variables” on page 138.
Default Topic The topic that appears when Help opens. By default, the first topic in the table of contents is the

default topic.
Override Settings Use the Apply To All Topics option to specify whether to apply a master page or a CSS to all the
topics. If you do not select the Apply To All option, the master pages associated with individual topics become
effective. If no master pages are applied to topics, they are generated as is. See “Applying a master page or CSS at
the time of generation” on page 110

Configure the Help application installer
You configure the settings for the Help application installer.
❖ In the General tab of the Adobe AIR dialog box, set the following under the Installer Settings group:
Digital Certificate A digital signature ensures that the Help system (or its updates) has not been altered or

corrupted since it was created. All Adobe AIR applications require a digital signature and can't be installed without
one. If your organization has purchased one from a certificate authority, click Browse to select it. Otherwise, click
Create to create a self-signed (and reusable) certificate. See “Create a self-signed digital certificate” on page 274.
Password Enter the password assigned to the digital certificate.
Include Timestamp Select to include a timestamp on the digital certificate. The timestamp provides information on

how long the certificate is valid.
Program Menu Folder Specify the program menu folder name. For example, on Windows, the string that you

specify is appended to form the path Start > Programs > [program menu folder name] > [Help system title].
Set the Help viewer window and branding options
Appearance settings define the appearance for the Help viewer window.
❖ In the Adobe AIR dialog box, select the Template group and set the following:
Template Select a template from the pop-up menu.
Skin Select a skin from the pop-up menu.
Width And Height Set the width and height of the Help window.

USING ROBOHELP HTML 8 272

Last updated 3/1/2010

Generating Help and printed documents

company publishing the Help content.
Specify Branding options Click Select to choose PNG images for your Help system based on Adobe AIR. You can
select different icons for the desktop shortcut, About dialog box, title bar, and taskbar. You can also display your
copyright information or any brand-related information in the status bar of the Help application.

Template for the Help application
Choose the template that you want to use for your Help application. You can select one of the following three
templates:
Note: Templates are not applicable if you selected the Help Content Only output type.
Classic Help The Classic Help template divides the page into a top pane, left pane, and a content pane.
Multi Tab Accordion The Multi Tab Accordion template divides the page into a top pane, left pane, and a content pane.
Uni Pane The Uni Pane template divides the page into a top pane and a content pane.

All the templates have different appearance and navigation options. They also have some common features. These
features are support for TOC, index, glossary, search, print, and the Content pane. The following table shows the
differences among three types of templates:
Features

Classic Help

Multi Tab Accordion

Uni Pane

How do I

Yes

Search results that show context No

Yes

Showing/hiding the left pane

Yes

Viewing status bar

Yes

See “Browse sequences” on
page 192.
Search

Note: Press F11 to show or hide the left and top panes.
You can choose any of the templates to use in the Help system and preview it before generating it.
Note: You can customize a template. By default, all the available options for content display and navigation in a template
are selected.
Configure content presentation
You configure how the Help application behaves when a user uses it.
❖ In the Adobe AIR dialog box, select the View group, and set the following:
Enable Highlight Search Results Select to enable highlighting of search results. Topics that match the search criteria
appear with the search term highlighted. Click the Text pop-up menu to set the highlight color.
Enable Substring Search Select to have search results include not only the exact search string but also text in which

the string is embedded. For example, a search for “log” returns topics containing the words “catalog” and
“logarithm.” A substring search takes longer than a whole-string search.
Show Context In Search Results Select to have the search results displayed along with the first few lines of the topic.
Enable Commenting Select to enable commenting. Click Browse to choose the local network folder where the
reviewers' comments will be stored.

USING ROBOHELP HTML 8 273

Last updated 3/1/2010

Generating Help and printed documents

Enable commenting before you send the Help application for review so that reviewers can add comments to topics
that they can exchange among their peers. See “Start a shared review” on page 290.
Add Click Add to add the location of Mac OS and Linux systems to synchronize comments.
Enable Auto Update Enables the AIR application to synchronize the AIR file installed on a desktop with the current
content on the network drive or an HTTP server location. Do one of the following:

• Content updates within your network Select File from the Type menu and click Browse to select the folder and
file with the content updates.

• Content updates outside your network Select HTTP from the Type menu and enter the URL of the XML file
that contains the updates to the Help contents.
The Auto-update feature helps your users update the Help application whenever an update is available. You can
send the auto-update in the form of an XML file or host it on a web server. See “Hosting updates for AIR Help” on
page 290.

• Add Click to specify Mac OS and Linux locations to update the installed Help if you are hosting the XML file
on a local or network drive.
Add Resources Select and click the Add tab to add external links that appear in the Favorites group in the Help

application.
You can add resources such as technical support pages, knowledgebase articles, RSS feeds, and related websites.
Show Online Content Specify a URL from where the viewer picks up the online Help. This option is applicable
only if you select the output type as Adobe AIR Application or AIR Application And Browser Based Help.

Configure a server to host browser-based Help
You can directly upload the generated browser-based Help to a server. Consult your system administrator for
information about which server to use.
Note: Server configuration is not applicable if your output type is Adobe AIR Application.
1 Select Server in the Adobe AIR dialog box.
2 Click New. Specify the following options in the New Destination dialog box:
Descriptive Name Name for the server to publish the Help system to. For example, if you are publishing a Help
system for internal review, enter “Internal Review Server.”
Connection Protocols Select the protocol for connecting to the server. Select FTP, HTTP, or File System.

These are the FTP server connection details:

• Hostname Enter the host name of the FTP server.
• Port Enter the port number. Typically, FTP connections use the default port, 21.
• User ID and Password If your FTP server requires user authentication, enter the user ID and password that your
system administrator provided for you.
• Anonymous Select Anonymous if your FTP server allows anonymous FTP. You do not require a user ID and
password for connecting to the FTP server.
Specify these details for the HTTP server connection:

• Host Name Enter the host name of the server.
• Server Directory Enter the directory on the HTTP server to place the Help system contents. Some HTTP servers
require a trailing slash (/) at the end of the path.

USING ROBOHELP HTML 8 274

Last updated 3/1/2010

Generating Help and printed documents

Select File System and enter the destination path if you have access to a network path where you can directly upload
your Help system contents.
3 Set the following options:
Check For Deleted Files Check for files that have been deleted from the destination.
Prompt Before Overwriting Files Receive a warning before overwriting files on the server.
Republish All Republish all files to the destination, overwriting existing files on the server.

Note: If you are setting options for a master project, and a copy of the subproject is in the output folder, ensure that
Republish All is not selected.
4 To publish Help, click Finish.

Tips:
• For merged Help systems, publish individual projects to the same location. Do not use Republish All in the master
project.

• Set layout options once and automatically generate the primary layout by selecting the Generate button.
• Generate or publish multiple layouts in a batch.

Create a self-signed digital certificate
You can create a digital certificate to test or privately distribute the Adobe AIR Help application. However, if you
distribute Help through your website, be sure to procure a digital certificate from a certificate authority (CA), such as
Thawte or VeriSign. Use the digital certificate to sign the Help system.
Digital certificates from certificate authorities can be verified through the web. They assure end-users that the Help
application installer is genuine and free from malware. See www.adobe.com/go/learn_air_digital_certificate for more
information.
1 Click Create near the Digital Certificate label.
2 In the Create Self-Signed Digital Certificate dialog box, enter the following details:
Publisher Name Specify the name of the publisher. Usually, it is the name of your company. If you are creating a

Help application based on Adobe AIR for another company, specify the name of your client. Optionally, you can
specify the organizational unit and organization name.
Country Select the country of the publisher.
Type Select the encryption standard for the digital certificate. The 2048-RSA standard provides stronger

encryption than the 1024-RSA standard.
Save As Click Browse to select a folder and save the digital certificate that you created. Self-signed digital
certificates are saved with a .p12 extension.

Generate, view, and publish output
Generate output to view it and test links, browse sequences, and other elements. Generating output also updates files
containing information about the project and the output files.
Publishing the output (WebHelp and FlashHelp only) places the output files or folders at a specified location. The
location can be a website, the local hard drive, or a network folder.

Last updated 3/1/2010

USING ROBOHELP HTML 8 275
Generating Help and printed documents

Generate output
You generate output to your local hard drive. When you generate a layout output for the first time, a new subfolder is
created for the generated output files. It is in the project folder under \!SSL!\[layout name].
Note: Each time you generate output, RoboHelp deletes the output folder files created in the last session. If you add or
hand-code files in the output subfolder, copy them to another location before you generate output.
1 In the Single Source Layouts Pod, right-click the layout. Select Generate.
2 Set options according to the layout type.
3 Click Finish.

Tips for optimal project generation
• Work locally, not from a network.
RoboHelp must access all of the files in your project when generating the output. If a project consists of thousands
of files, even a minor delay caused by network traffic compounds as RoboHelp attempts to access each file. These
delays can adversely affect the generation times.

• Exclude the project folder from virus scan.
Note: Turning off virus-scanning software increases speed but is not recommended for security reasons.

• Ensure that your system has sufficient memory.

More Help topics
“Navigation options” on page 177
“User-defined variables” on page 138

Set options for generating WebHelp
1 Set the following options, and then click Next.
Select Output Folder And Start Page Specifies a location and start page for the Help files. To choose a location for

. To select a start page other than the default for the Help project,
the output folder, click the browse button
enter it using the .htm extension. The start page is a frameset for Help content to which file developers link when
calling the Help system from an application.
Use Lowercase File Names Create filenames that use only lowercase letters. This option is recommended for UNIX

users.
Note: Don’t select this option for merged projects. Links to topics in other projects will convert to lowercase, whereas
the topic filenames will remain the same. The mixed cases create broken links on UNIX.
Conditional Build Expression If you have conditional tags in the project, click Define to specify conditional build

expressions.
Skin (Optional) Browse to a skin in the project, or click Gallery to select one from the Skins Gallery. Apply skins
to customize the colors, buttons, text, fonts, and icons in the output.

USING ROBOHELP HTML 8 276

Last updated 3/1/2010

Generating Help and printed documents

Variables Set Select a variable set to override the default variable set values in the generated Help.
Default Topic Click Select to specify the topic that appears when the Help opens. By default, the first topic in the
table of contents appears.
Section 508 Compliant Output Select to deliver Section 508-compliant WebHelp. Output cannot include skins or

other features such as DHTML.
W3C Compliant Topics For W3C-compliant topics, this option passes the topics through an HTML validator.

Note: Dynamic effects in styles aren’t supported in W3C-compliant output.
Add Mark Of The Web Mark of the Web is a comment in the HTML markup for a web page. Internet Explorer 6
and later reference this comment to determine the security zone for the page on the user’s computer. Select this
option to avoid having Internet Explorer block the output.

Note: Before merging projects, ensure that the Mark Of The Web option is either selected or deselected for the projects.
Apply To All Topics Select this option to apply master pages or CSS at the project level:

• Master Page The selected master page overrides the settings of all the individual topics with or without a master
page applied to them in the project. The CSS and layout of the master page override the CSS and appearance of all
the topics. If the selected master page does not have a header or footer, no topic displays a header or footer
irrespective of if it had one header or footer defined.
• CSS The master pages associated with individual topics become effective. The selected CSS overrides all the
topics and their CSS irrespective of whether they are associated with a master page or not.
2 Set the following options, and then click Next.
Toolbar Buttons Select navigation toolbar buttons to appear in the left pane.
Show Navigation Pane Link In Topics Select to include a link to the navigation pane in topics that are opened
through the context-sensitive Help calls.
Add Breadcrumbs Links Select to add breadcrumbs in the topic pages.
Show Merged TOC In Child Project Select to view the merged TOC in the child project.
Format Click to change the format of breadcrumbs.
Show Context In Search Result Select to have the search results displayed along with the first few lines of the topic.
Enable Highlight Search Result Select to enable highlighting of search results. From the pop-up menu, select a color

for the highlight.
Add About Box Set up information that appears in a dynamic window when users click the image in the main

toolbar.
Example of About box

Enable Substring Search If you enable this feature, a search for "log" returns topics containing the words "catalog"

and "logarithm." Substring search takes longer than whole-string search.
Browse Sequences Create browse sequences before enabling them.
Detail Change the text displayed for the in-topic navigation bar elements.
Search Input Field In Toolbar Include a search field in the main toolbar.

USING ROBOHELP HTML 8 277

Last updated 3/1/2010

Generating Help and printed documents

Synchronize Table Of Contents Synchronize the TOC with the topic in the right pane so that users see where they

are in the structure.

• To synchronize the TOC automatically, click the pop-up menu and select Automatically.
• To add a button that users can click to synchronize the TOC, click the pop-up menu and select Manually.
Note: If you use custom skins, provide a button icon in the WebHelp Skin Editor.
Set the following options and then click Next.
Preferred Format Specify how WebHelp handles Dynamic HTML (DHTML) and how end users access Help. The

option you choose depends on user environment, such as the types of browsers and firewalls used.

• DHTML > Pure HTML Uses Dynamic HTML when supported, pure HTML otherwise. If users have firewalls that
block Java applets, select DHTML > Pure HTML, which eliminates Java applets from Help.
• Pure HTML Displays Help using list-based, pure HTML in all browsers. However, Pure HTML reduces
navigation functions.
Optimize Speed For Select the option by which most users access Help. XML formats reduce load times by
downloading only the data immediately needed. For example, the Contents pane fills quickly by initially
downloading only enough data to fill the pane. The rest is downloaded in time for the user to move down the list.

• Web Site (Internet) Select if access is from a website. Assumes slower connections, uses data in smaller pieces,
and requires more WebHelp files.

• Local PC or Intranet (Internal Network) Select if access is from an intranet or a local computer. Assumes
faster connection, uses data in larger pieces, and requires fewer WebHelp files.
3 Set the following options, and then click Finish.
Servers Specify a server location for the output.
Options Specify how to handle changes to files in the output:

• Check For Deleted Files If selected, RoboHelp HTML checks for files that have been deleted from the
destination location and republishes them.
• Prompt Before Overwriting Files If selected, RoboHelp prompts you before overwriting files.
• Republish All Select to republish all files to the destination target. For master projects with a copy of the
subproject in the subfolder, do not select Republish All. You then avoid overwriting output files already published
to the same location.
Note: If you change the destination to a new host, specify the user ID and password and save the password in the
registry, if necessary.

More Help topics
“Dynamic HTML and special effects” on page 200

Set options for generating FlashHelp
In addition to the standard generate options, set the following FlashHelp options, as necessary:
1 Set the following options, and then click Next.
Output Folder And Start Page Specifies a location and start page for the Help files. To choose a location for the

. To select a start page other than the default for the Help project, enter it
output folder, click the folder button
using the .htm extension. The start page is a frameset for Help content to which file developers link when calling
the Help system from an application.

USING ROBOHELP HTML 8 278

Last updated 3/1/2010

Generating Help and printed documents

Use Lowercase File Names Select if you want to create filenames that use only lowercase letters. This option is

recommended for UNIX users.
Note: Don’t select this option for merged projects. Links to topics in other projects will convert to lowercase, whereas
the topic filenames will remain the same. The mixed cases create broken links on UNIX.
Conditional Build Expression If you have conditional tags in the project, click Define to specify conditional build

expressions.
Skin Choose from the skins in the project, or click Gallery to select one from the Skins Gallery. Skins let you
customize the output by changing the colors, buttons, text, fonts, and icons. A skin is required for FlashHelp output.

Note: The Skin option is disabled if you select the Section 508 Compliant Output option. Use the Traditional Style No Skin option.
Table Of Contents Select a table of contents to display in the generated Help.
Index Select an index to display in the generated Help.
Glossary Select a glossary to display in the generated Help.
Variables Select a variable set to override the default variable set values in the generated Help.
Default Topic The topic that appears when Help opens. Click Select to specify a topic. By default, the first topic in
the table of contents is the default topic.
W3C Compliant Topics For W3C-compliant topics, this option passes the topics through an HTML validator.

Note: Before merging projects, ensure that the Mark Of The Web option is either selected or deselected for the projects.
Auto-Manage Flash Security RoboHelp automatically adds the output path to the local-trusted sandbox for Flash

Player for the machine to ensure compatibility with Flash security features.
Apply To All Topics Select this option to apply master pages or CSS at the project level:

downloading only the data immediately needed. For example, the Contents pane fills quickly by initially
downloading only enough data to fill the pane. The rest is downloaded in time for the user to move down the list.

• Web Site (Internet) Select if access is from a website. Assumes slower connections, uses data in smaller pieces,
and requires more WebHelp files.

• Local PC or Intranet (Internal Network) Select if access is from an intranet or a local computer. Assumes
faster connection, uses data in larger pieces, and requires fewer WebHelp files.
2 Set the following options, and then click Next.
Toolbar buttons Select items to include as toolbar buttons. Click Up or Down to reorder buttons, and click Set As
Default to specify the default button.

USING ROBOHELP HTML 8 279

Last updated 3/1/2010

Generating Help and printed documents

Navigation Select the navigation items you want to include in the output.
Additional Options Select the following options as desired:

• Browse Sequences Enables support of browse sequences if you created them. The window contains Previous
and Next buttons. Use skins to customize the browse sequences.
• Search Input Field In Toolbar Adds the Search button to the toolbar. Use skins to customize the Search Input
Field.

• Synchronize Table Of Contents Indicates in the table of contents the location of the viewed topic.
• Add About Box Click Add to specify information that appears in an About window that the user opens from the
main toolbar.
Search Options Specify search options for the generated Help:

• Enable Highlight Search Result Select to enable highlighting of search results. From the pop-up menu, select a
color for the highlight.

• Show Context In Search Result Select to have the search results displayed along with the first few lines of the
topic.

• Enable Substring Search If you enable this feature, a search for "log" returns topics containing the words
"catalog" and "logarithm." Substring search takes longer than whole-string search.
3 Set the following options, and then click Finish.
Server Specify a server location for the output.
Options Specify how to handle changes to files in the output:

• To update the skin, download the skin again from Community Help, see the SDK documentation, or contact the
Flash developer.

Set options for generating WebHelp Pro or FlashHelp Pro
1 Set the following options, and then click Next.

Note: The order of some options varies according to the type of output you generate.
Project Name Differentiates multiple versions of a project on a server, if you merge projects.
Output Folder And Start Page Specifies a location and start page for the Help files. To choose a location for the

output folder, click the folder button

. To select a start page other than the default for the Help project, enter it

USING ROBOHELP HTML 8 280

Last updated 3/1/2010

Generating Help and printed documents

using the .htm extension. The start page is a frameset for Help content to which file developers link when calling
the Help system from an application.
Conditional Build Expression If you have conditional tags in the project, click Define to specify conditional build

expressions.
Skin Choose from the skins in the project, or click Gallery to select one from the Skins Gallery. Skins let you

customize the output by changing the colors, buttons, text, fonts, and icons. A skin is required for FlashHelp output.
Note: The Skin option is disabled if you select the Section 508 Compliant Output option. Use the Traditional Style No Skin option.
Table Of Contents Select a table of contents to display in the generated Help.
Index Select an index to display in the generated Help.
Glossary Select a glossary to display in the generated Help.
Variable Set Select a variable set to override the default variable set values in the generated Help.
Default Topic The topic that appears when Help opens. Click Select to specify a topic. By default, the first topic in
the table of contents is the default topic.
Default Window The container in which the Help displays. By default, the Help system opens in the user default

browser window.
Show Navigation Pane Link In Topics Includes a link to the navigation pane in topics opened through context-

sensitive Help.
Add Breadcrumbs Links Select to add breadcrumbs in the topic pages.
W3C Compliant Topics For W3C-compliant topics, this option passes the topics through an HTML validator.

Note: Before merging projects, ensure that the Mark Of The Web option is either selected or deselected for the projects.
Add About Box Click Add to specify information that appears in an About window that the user opens from the

main toolbar.
Auto-Manage Flash Security (FlashHelp Pro) If selected, the generated output path is copied to the local-trusted

sandbox of Flash Player. Because of security changes in Flash 7 and later, place SWF files in the trusted security
sandbox of Flash Player. RoboHelp maintains the RoboHelp[version].cfg file in the FlashPlayerTrust folder.
Note: Dynamic effects in styles are not supported in W3C-compliant output.
Show Context In Search Result Select to have the search results displayed along with the first few lines of the topic.
Enable Highlight Search Result Select to enable highlighting of search results. From the pop-up menu, select a color

for the highlight.
Apply To All Topics Select this option to apply master pages or CSS at the project level:

USING ROBOHELP HTML 8 281

Last updated 3/1/2010

Generating Help and printed documents

• CSS The master pages associated with individual topics become effective. The selected CSS overrides all the
topics and their CSS irrespective of whether they are associated with a master page or not.
2 Set the following options, and then click Finish.
Servers Specify a server location for the output.
Options Specify how to handle changes to files in the output:

Set options for generating Microsoft HTML Help
❖ Set the following options, and then click Finish.
Select Output Folder And File Name Specifies a location and start page for the Help files. To choose a location for

the output folder, click the browse button
enter it using the .chm extension.

. To select a start page other than the default for the Help project,

Conditional Build Expression If you have conditional tags in the project, click Define to specify conditional build

expressions.
Table Of Contents Select a table of contents to display in the generated Help.
Index Select an index to display in the generated Help.
Glossary Select a glossary to display in the generated Help.
Variables Select a variable set to override the default variable set values in the generated Help.
Default Topic The topic that appears when Help opens. Click Select to specify a topic. By default, the first topic in

the table of contents is the default topic.
Default Window The container in which the Help displays. By default, the Help system opens in the user default

browser window.
Add Breadcrumbs Links Select to add breadcrumbs in the topic pages.
Optimize CHM Size Reduces the size of the CHM file.
Advanced Settings Click to specify custom styles for the table of contents and index.
Apply To All Topics Select this option to apply formatting at the project level:

USING ROBOHELP HTML 8 282

Last updated 3/1/2010

Generating Help and printed documents

Set options for generating Oracle Help
1 Set the following options, and then click Next.
Select Output Folder And Filename Name and location of output files.
Use Lowercase Filenames Recommended for UNIX users or users accessing files on a UNIX server.
Conditional Build Expression Click Define to specify conditional build expressions.
Default Topic Click Select to select a topic to display when the Help opens.
Navigation Pane Specify the tabs that appear in the Help navigation pane.
In-Topic Navigation Bar Options for the navigation bar.
Table of Contents Select a table of contents to display in the output.
Output Specify the type of Oracle Help output:

• Uncompressed Oracle Help With Source Files Generates HS files and individual source files.
• Compressed Oracle Help Generates JAR and HS files.
• Compressed Oracle Help With Source Files Generates JAR and HS files, and individual source files.
Note: Generating Oracle Help source files empties the Oracle Help output folder.
Table Of Contents Select the table of contents to display in the output.
Index Select the index to display in the output.
Variables Select a variable set to override the default variable set values in the generated Help.
Apply To All Topics Select this option to apply formatting at the project level:

3 Set the following options, and then click Next:
Title (Optional) Specify text that appears in the viewer. Leave the boxes empty to use default text (Contents, Index,
Full-Text Search).
Image Click the browse button to select an image that appears next to the table of contents title.

4 Click Add to specify a remote view for the TOC, index and Search. Enter view properties, and then click Next:
General tab Set the following options:

• Name (Optional) A unique name for the remote view.
• Type Remote view type: TOCNavigator, KeywordNavigator, or SearchNavigator. Oracle Help merges views
with identical labels and view types.

• Engine Format of the data file for the view.
• Data File Path (filename or URL) to the remote view.

USING ROBOHELP HTML 8 283

Last updated 3/1/2010

Generating Help and printed documents

Optional tab Set the following options:

• Text Specify the tab label and view title. Leave the boxes empty to use the default text (Contents, Index, FullText Search).
• Image Click the browse button to select an image to use in the toolbar.
Map Reference tab Click the browse button to add a pointer to the map file for the remote view.

5 To merge an external HelpSet file (.hs) with the project, specify the path in SubHelp Sets, and click Add.
6 Click Finish.
7 If the JavaHelp JDK Requirement dialog box appears, select one of the following options:

Note: This dialog box appears if Sun Java 2 JDK or later isn’t installed.
Generate without Full-text Search Click to generate output without full-text search functionality.
Locate Java SDK Install Folder Click to browse to the Java JDK install folder. Click Network to locate and map the

folder on a network drive.

Set options for generating JavaHelp Help
1 Set the following options, and then click Finish.
Select Output Folder And Filename Name and location of output files.
Use Lowercase Filenames Recommended for UNIX users or users accessing files on a UNIX server.
Conditional Build Expression Click Define to specify conditional build expressions.
Default Topic Click Select to select a topic to display when Help opens.
In-Topic Navigation Bar Specify options for the navigation bar.
Table Of Contents Select a table of contents to display in the output.
Index Select an index to display in the output.
Glossary Select a glossary to display in the output.
Variables Select a variable set to override the default variable set values in the generated Help.
Version Specify the JavaHelp version.
Compressed Select from the following options:

• Uncompressed JavaHelp With Source Files Generates HS files and individual source files.
• Compressed JavaHelp JAR Generates JAR and HS files.
• Compressed JavaHelp With Source Files Generates JAR and HS files, and individual source files.
Note: Generating JavaHelp source files empties the JavaHelp output folder.
Advanced Navigation view properties and merging options
Apply To All Topics Select this option to apply formatting at the project level:

USING ROBOHELP HTML 8 284

Last updated 3/1/2010

Generating Help and printed documents

2 If the JavaHelp JDK Requirement dialog box appears, select one of the following options:

Note: This dialog box appears if Sun Java 2 JDK or later isn’t installed.
Generate without Full-text Search Click to generate output without full-text search functionality. The JavaHelp

SubHelpSets dialog box appears.
Merge an external JavaHelp HelpSet (HS file) into the project.

• Subhelp sets Enter the full path (filename or URL) to the HelpSet (.hs) file.
• Add Add the specified HS file.
• Update Change the location of a SubHelpSet file already added. Highlight the file, change the path in the
SubHelpSet box, and click Update.
• Remove Delete the selected SubHelpSet file.
Locate Java SDK Install Folder Click to browse to the Java JDK install folder. Click Network to locate and map the

folder on a network drive.
You can define the viewer class for a given MIME type by specifying the following information.
Type Enter the MIME type.
Class Enter a Java class for viewing the MIME type.

Set options for generating XML output
❖ Set the following options, and then click Finish.
Select Output Folder And File Name Name and location of output files.
Conditional Build Expression Click Define to specify conditional build expressions.
Select Export Handler Advanced options include the following:

• Export Project To DocBook Exports the entire XML project to DocBook format.
• Export Topics To DocBook Exports only the topics to DocBook format.
• Export Project To XHTML Exports the XML project to XHTML format. All topics are converted to XHTML files.
• Export Topics To XHTML Exports only the topics to XHTML format.
For DocBook options, click Advanced to set additional options:

• Content Only Exports only the meaningful content (text and data) contained in the project or topic. No
DHTML effects are included.
• Export Exports the entire project or topic contents (text and data and their related display format). All DHTML
effects are included.
Table Of Contents Select a table of contents to display in the output.
Index Select an index to display in the output.
Glossary Select a glossary to display in the output.
Override Select this option to apply formatting at the project level:

USING ROBOHELP HTML 8 285

Last updated 3/1/2010

Generating Help and printed documents

More Help topics
“XML layout” on page 269

Batch-generate output
Batch-generating output eliminates the need to wait for each output to finish processing before starting the next one.
You can publish output from different layouts to different locations. Batch-processing saves time if you use conditional
build tags to test, view, or distribute different outputs.
Layouts are processed in the order they appear in the Batch Generate dialog box.
Important: During generation, RoboHelp deletes the output folder files created in the last session. If you add or handcode files in the output subfolder, copy them to another location before generating the output.
1 In the Single Source Layouts pod, right-click a layout.
2 Select Batch Generate.
3 Select the layouts for the outputs to generate.
4 Click Generate or Publish.

Notes:
• Generating WebHelp or WebHelp Pro requires a browser.

• To generate printed Word documents for the first time, enable macros in Word.
• Publish is available only if destinations for the selected WebHelp layouts are defined.
• Check the status of a generation in the Batch Generate dialog box. For a status of Failed, check the compiler
messages in the lower pane to resolve the problem. For WinHelp projects, generate the project in the Layout wizard
and use Error wizard to locate the problem.

• View published WebHelp or WebHelp Pro output from the server to see changes and server-dependent features.

View output
❖ Do one of the following:

• If the output is already generated, in the Single-Source Layouts pod, right-click the layout and select View. If
prompted, click Yes to regenerate the output before you view it.

• If you have generated the layout, click View Result. After viewing, you can click Done, or publish the output to
the location specified in the layout by clicking Publish.

• First publish the master project and view the master project from the published location to see the merged
system. To publish the project, click Publish.
Note: If the Publish button is disabled, add a destination in the Publish dialog box when generating or editing.

View WebHelp, WebHelp Pro and FlashHelp Pro output
To preview a WebHelp Pro or FlashHelp Pro project locally without publishing to the Adobe RoboHelp Server, open
it in a web browser. You can’t preview the index, table of contents, links, and browse sequences locally.
You also can test the published project, including all server-dependent features, by viewing it from the server.

USING ROBOHELP HTML 8 286

Last updated 3/1/2010

Generating Help and printed documents

View the project in the browser to test links, images, browse sequences, and other elements.
View WebHelp, WebHelp Pro, and FlashHelp Pro remotely
1 Open the project, and ensure that the appropriate layout is the primary layout.
2 Select File > View > Primary Layout From Server.

View WebHelp, WebHelp Pro and FlashHelp Pro locally
1 In the Single Source Layouts pod, right-click the layout. Select View. If prompted, click Yes if you want to update
the output. Otherwise click No.
2 If a Limitations dialog box appears, click OK. The dialog box lists features that you cannot view without being

connected to a server, such as the Search button and Windows properties.
The project opens in the default browser.
To view a merged Help system from the master project local copy, copy the subproject WebHelp files to the master
project mergedProject\[project name] folder. Right-click the layout in the Single Source Layouts pod. Select View. Do
not use the Republish All option in the master project.

View compiled Microsoft HTML Help
1 In the Single Source Layout pod, right-click Microsoft HTML Help.
2 If prompted, click Yes if you want to update the output. Otherwise click No.

Note: To see inbound and outbound links by topic, select View > Pods > Link View.

More Help topics
“View topics and design elements” on page 106

Help Viewer Wizard
Help Viewer Wizard enables you to generate an AIR Help viewer (AIR file) and installer, define the content
appearance, and specify other settings.
Generate an AIR Help viewer
1 Select View > Pods > Toolbox.
2 Double-click to start Help Viewer Wizard.
3 Specify the required information.

Note: Just select the path for the file and enter any name as the file name.
4 Specify a version number and an ID.
5 Create a self-signed digital certificate. See “Create a self-signed digital certificate” on page 274.
6 Click Finish.

Copy the Help content file
❖ Copy the Help content file (RHA) to your computer. It can be in any location, but the installer needs to remember
the location.
See “Select Help output” on page 270 for information about how an RHA file is generated.

USING ROBOHELP HTML 8 287

Last updated 3/1/2010

Generating Help and printed documents

Install the Help application
The AIR Help viewer is an AIR file that installs the Help application.
1 Go to the C:/Program Files/[folder name].
2 Double-click the AIR file.
3 Go to the same folder and double-click the EXE file.

Create and locate a Help configuration file
The AIR Help viewer must be associated with the Help content file to display content in the selected format. Create an
XML file with a .helpcfg extension to associate the RHA file with the AIR Help viewer. Save the file at the same location
as the installed AIR file. The AIR Help viewer uses the .helpcfg file to locate the path to the Help content file and then
displays the Help content.
Repeat the XML code for every Help file that you want to display with the Help viewer.
For example, an XML file that contains the Help configuration contains the following line of code:
<?xml version="1.0" encoding="utf-8" ?>
<contents>
<data id="" label="" onlineurl="" offlineurl=""/>
</contents>
Attribute name

Attribute value

The unique string that distinguishes a Help data file from other Help data files in the viewer. You
can use this ID to call the CSH API or to start the AIR Help viewer.

label

The label for Help content when the Help viewer contains multiple Help data files. The Help
viewer displays this string in the selected Help content.

onlineurl

The online URL of the Help content that is hosted on a server.

offlineurl

The offline location of the Help file if locally installed Help is available.

useoffline

Optional setting. If you set this attribute to “true,” the AIR Help viewer picks offline Help content
when you launch the Help application. If no offline Help is available, then you don’t need this
attribute in the Help configuration file.

Note: The name of the .helpcfg file can be set to any name. The name does not need to match the name of the .air or .exe
file in the installation folder.

Publish output
You can publish output for WebHelp and FlashHelp projects. After you specify an output location, publish the output
whenever needed. Publish multiple versions of a project (including to multiple locations) using batch-processing.
You can select to publish only the files that changed since they were last published.
1 In the Single Source Layouts pod, right-click the layout. Select Properties, and click Next until the Publish dialog

box appears.
2 Specify a publishing destination by doing one of the following:

• Select or edit an existing destination from the Servers box, set options as necessary, and click Save.
Check For Deleted Files If selected, RoboHelp HTML checks for files that have been deleted from the
destination location and republishes them.
Prompt Before Overwriting Files If selected, RoboHelp prompts you before overwriting files.

USING ROBOHELP HTML 8 288

Last updated 3/1/2010

Generating Help and printed documents

Republish All Select to republish all files to the destination target. For master projects with a copy of the
subproject in the subfolder, do not select Republish All. You then avoid overwriting output files already
published to the same location.

Note: If you change the destination to a new host, specify the user ID and password and save the password in the
registry, if necessary.

• To specify a new destination, click New. Type a descriptive name and set options as necessary. Click OK.
Connection Protocols Specify the type of transfer protocol to use to reach the new destination. Select File System
to publish files to a local or network drive. For Front Page Enabled, first install and customize Microsoft
FrontPage and its server extensions.
Merging Help Systems To publish a subproject to the MergedProjects folder, specify the following information:

• In Host Name, enter the IP address or URL.
• In Web Name, type the name of a web on the server (or the empty string for the root web).
• In Server Directory, enter the path to the master project: /.../[master project]/MergedProjects/[subproject].
This path resides on the server after the master project is published.
Options Options depend on the selected connection protocol.

• Server Name Server on which to publish files. You can use an IP address.
• User ID Specifies the user ID to connect to the host.
• Password Specifies the password for the user ID. The network system administrator can provide this
information.

• Save Password Saves the password so you do not need to enter it when you publish the files. (Saving the
password enters the password into the registry. It is not encrypted.)
• Port Port to use when connecting to the host.
• Anonymous User Publishes the files as an anonymous user that does not require a password. If you supply a
password or other anonymous information such as an e-mail address, deselect this option. Type Anonymous
in the user ID box, and type a password in the Password box.
• Server Directory Specifies the destination directory on the server. The default is a forward slash.
• Web Name The name of a FrontPage Web on the server selected in Host Name. (No initial slash is required
for subwebs.)
Note: Web Name is used only if FrontPage Server Extensions are installed on the server. Otherwise, the files are
published to the server directory specified using FTP://.

• Destination Path (HTTP protocol) Path to the location to publish the files.
3 In the Single Source Layouts pod, right-click the layout, and select Publish. If prompted, choose whether to generate

and include changes before publishing.
4 Click Close.

View the output from the server to see changes and server-dependent features.

Generate and publish output from the command prompt
Command-line generation publishes layouts without opening RoboHelp, or automatically in a scheduled batch.
Command-line and batch generation and publishing can occur simultaneously.

Last updated 3/1/2010

USING ROBOHELP HTML 8 289
Generating Help and printed documents

Note: To access the command prompt from within RoboHelp, click Start > Programs > Adobe RoboHelp [version]> Tools
> RoboHelp Command Prompt.

Open the application from the command prompt
1 At the command prompt, enter the command in the following format:
rhcl myproject\myproject.xpj

2 Access the output files in the default output folder.

Generate layouts from the command prompt
• To generate a single layout to the default output folder (!SSL!), enter the command in the following format:
rhcl [project path] [-l] [layout name]

• To generate a single layout to a custom output folder, enter the command in the following format:
rhcl [project path] [-l] [layout name] [-o] [path of custom output folder]

• To generate all layouts to the default output folder (!SSL!), enter the command in the following format:
rhcl [project installation path] [-b]

• To generate all layouts to a custom output folder, enter the command in the following format:
rhcl [full or relative path of the RoboHelp project] [-b]

Publish layouts from the command prompt
❖ Enter the command in the following format:
rhcl [project path] [-p] [server name][user name][password]

The server name, user name, and password are optional.

Command prompt options
Commands must start with rhcl and include the project path and name. Enter commands using the following format:
rhcl [-?] [-h] [project path] [-l] [layout name] [-p] [server name:user name:password] [-o]
[output folder path] [-d] [-b] [-g]

Not all options are required when entering a command.
-l Generates a layout. Specify the layout name (for example, -l FlashHelp). The application generates the primary
layout if a layout is not specified.
-p Publishes a layout. Configure all publishing destinations using the New Destination dialog box.
“ Indicates spaces.
-o Sends the output to a folder.
-d Displays layout and publishing destination names at the command prompt.
-b Generates the layouts set for batch generation. Outputs to the output folder for a particular single-source layout.
-h Displays Help.

•

rhcl

•

rhcl -h

•

rhcl -?

USING ROBOHELP HTML 8 290

Last updated 3/1/2010

Generating Help and printed documents

-g Specifies a log filename.

If you specify this option with the rhcl command, rhcl writes the output into the specified log file. The output is not
sent to the console. The specified log filename cannot contain Unicode characters. If a file by this name exists, that file
is overwritten.

Hosting updates for AIR Help
After you publish your initial Adobe AIR application, you can correct and revise the content as needed. By default,
when a user launches the Help application, it displays the online content, so the displayed Help contains your updates.
When you generate a new version of an Adobe AIR application, a Help configuration file is created along with the
output. This XML file is unique for each version of the Help application. It contains information about the location of
the published Help application, the Help ID, and the version number. Place this XML file with the Help application
installer on the specified shared server location for users. When a user’s installed version checks for updates from this
location, the Help application is updated.

Create and host an update
1 Right-click Adobe AIR in the Single Source Layouts pod, and select Properties.
2 Specify the updated information for your Help content.

Since you are updating existing Help content, retain the Help title and Help ID of the Help output you configured
earlier, but update the version number.
3 In the Adobe AIR dialog box, select the View group and select Enable Auto Update, if it is not enabled already.
4 Specify the location of the updated Help configuration file (XML file) that is hosted on a shared location or web

server.
To distribute Help updates within your network, select the file path. To distribute outside the network, select a web
server location.
5 Update any other parameters you require, such as resource tabs.
6 Generate the Help output formats.

Post an update
You can post an update for the Adobe AIR application at the specified web server address (HTTP location) or in the
network folder.
❖ Generate Help and then post the updated Help application installer and the associated XML file to the web server

or folder.

Start a shared review
You can start a shared review of Help if you generate the output as an Adobe AIR application with commenting
enabled. Reviewers use commenting and review options to add comments to topics and publish those comments at a
common location. Reviewers within your network can publish their comments to an XML file in a shared folder.
1 Enable commenting and specify the path of the shared folder to upload comments from internal reviewers.
a Set the primary layout as Adobe Air (File > Project Settings > General > Primary Output). Click OK.
b Generate the primary layout (File > Generate > Primary Layout).
c In the Adobe AIR dialog box, select General.

USING ROBOHELP HTML 8 291

Last updated 3/1/2010

Generating Help and printed documents

d Either import an existing digital certificate or create one by clicking Create.
e Select View.
f

Select Enable Commenting and specify the location for publishing comments.

g Click Finish.
2 Publish the Help application and notify your reviewers.

More Help topics
“Adobe AIR layout” on page 269

Distribute the project output
After you create and test the project output, you distribute it to the developer or publisher. The output you deliver
depends on the project. By default, the output for distribution is in the project subfolder. (For Microsoft HTML Help,
the output is compiled into a single CHM file.)
Some RoboHelp tools provide Help functions through DLL and OCX files. Be sure to distribute these files. They must
be included with the installer for the Help system.
DLLs required by a RoboHelp application are listed in application Help. Redistributables are listed in Redistrb.Txt in
the Redist folder in RoboHelp [version] Program Files.
Note: Add the output to version control to provide accessibility to others.

Distribute WebHelp
For Help systems published to a central location, only the information relevant to the current inquiry is downloaded
to user browsers. The system can also be stored locally.
By default, all WebHelp output files are placed in a project subfolder (!SSL!/WebHelp). The WebHelp folder includes
subfolders. Do not rename or move any of these folders.

• To distribute WebHelp with an application, copy the WebHelp Folder and its contents to a location designated by
the developer. Let the developer know the name of the start page (HTM file).

• To publish WebHelp files to a server, website, or other network location, publish subprojects to the correct folder
in the MergedProjects subfolder.

• When distributing WebHelp as a stand-alone product, copy the WebHelp folder and its contents to a CD, a server,
or any location on user systems. Let users know which start page (HTM file) to select to view the Help system.

Output files in the WebHelp folder
Generating WebHelp creates the following output files in subfolders of the project folder.
Note: Do not import WebHelp-generated HTM files into the project. They are for runtime uses only.
File

Description

cshdat_robohelp.htm

Data for context-sensitive Help

cshdat_webhelp.htm

Legacy support for context-sensitive API

default.css

Style sheet

USING ROBOHELP HTML 8 292

Last updated 3/1/2010

Generating Help and printed documents

File

Description

default.skn

Default skin

EHLPDHTM.JS

JavaScript for advanced functionality such as Dynamic HTML effects

.GIF files

Images for skins, navigation, and browse sequences

NewProject.htm

Project start page

NewProject.log

Lists all necessary files

NewProject_csh.htm

Legacy support for context-sensitive API

NewProject_rhc.htm

Supports context-sensitive API

WEBHELP.CAB

WebHelp applet

webhelp.jar

Supports applet-based WebHelp

whestart.ico

Internet Explorer Favorites menu icon

whfbody.htm

Full-text search lower pane

whfdhtml.htm

Full-text search frameset

whfform.htm

Full-text search upper pane

whfhost.js

JavaScript for full-text search

whform.js

Index and full-text search fields

whframes.js

Framesets

whgbody.htm

Glossary terms

whgdef.htm

Glossary definitions

whgdhtml.htm

Manages glossary terms and definitions

whghost.js

Supports glossary

whhost.js

Lists and loads files in index and glossary

whibody.htm

Index lower pane

whidhtml.htm

Index frameset

whiform.htm

Index upper pane

whihost.js

Supports index

whlang.js

Language support

whmozemu.js

Netscape Navigator functions

whmsg.js

Message type definition and structure

whnjs.htm

Displayed when JavaScript disabled

whphost.js

Determines project contents

whproj.htm

Project data

WHPROJ.JS

JavaScript that supports WHPROJ.HTM

whproj.xml

XML project data

whproxy.js

Framework support

USING ROBOHELP HTML 8 293

Last updated 3/1/2010

Generating Help and printed documents

File

Description

whres.xml

Applet support (custom fonts and colors)

whskin_banner.htm

For logo dialog box- About author (skins)

whskin_blank.htm

Internal support file (same as _blank.htm) (skins)

whskin_frmset01.htm

Frameset separating navigation pane, navigation bar, and topic (skins)

whskin_frmset010.htm

Frameset separating navigation bar and navigation pane (skins)

whskin_info.htm

System information page (skins)

whskin_mbars.htm

Supports navigation bar (skins)

whskin_papplet.htm

Navigation pane for applet (skins)

whskin_pdhtml.htm

Navigation pane for Dynamic HTML (skins)

whskin_plist.htm

Navigation pane for Pure HTML

whskin_tbars.htm

Toolbar (skins)

whst_topics.xml

Parses topics during generation

whstart.ico

WebHelp icon

whstart.js

Supports start page

whstub.js

Framework support

whtbar.js

Supports navigation bar

whtdhtml.htm

TOC body

whthost.js

Supports TOC

whtopic.js

Supports in-topic navigation bar

whutils.js

Supports common functions

whver.js

Determines browser version

Output files in the Whgdata subfolder
Files in !SSL!\Webhelp\Whgdata are used with Pure HTML WebHelp.
File

Description

whexpbar.gif

Sets default navigation pane width

whlstf0.htm

Full-text search body

whlstfl0.htm

Level 2 full-text search letters

whlstg0.htm

Glossary terms

whlsti0.htm

Index terms

whlstt0.htm

Contents (part 2)

whlstt1.htm

Contents (part 2)

whnvf30.htm

TOC frame

whnvf31.htm

Index frame

USING ROBOHELP HTML 8 294

Last updated 3/1/2010

Generating Help and printed documents

File

Description

whnvf32.htm

Full-text search frame

whnvf33.htm

Glossary frame

whnvl31.htm

Level 1 index letters

whnvl32.htm

Level 1 full-text search letters

whnvl33.htm

Glossary letters

whnvp30.htm

TOC navigation pane

whnvp31.htm

Index navigation pane

whnvp32.htm

Full-text search navigation pane

whnvp33.htm

Glossary navigation pane

whnvt30.htm

TOC tabs

whnvt31.htm

Index tabs

whnvt32.htm

Full-text search tabs

whnvt33.htm

Glossary tabs

Output files in the Whdata subfolder
Files in !SSL!\Webhelp\Whdata are for DHTML versions of WebHelp on older browsers.
File

Description

whftdata0.htm

Full-text search data - HTML support

whftdata.js

Full-text search data - JavaScript supporting WHFDATA0.HTM

whftdata0.xml

Full-text search data - XML support

whFull-text search.htm

Full-text search index data - HTML support

whFull-text search.js

Full-text search index data - JavaScript supporting whFull-text search.htm

whFull-text search.xml

Full-text search index data - XML support

whfwdata0.htm

Full-text search keywords - HTML support

whfwdata.js

Full-text search index data - JavaScript supporting whfwdata0.htm

whfwdata0.xml

Full-text search keywords - XML support

whgdata.js

Loads glossary term definitions

whGlossary.htm

Glossary index data - HTML support

whGlossary.js

Glossary index data - JavaScript supporting whGlossary.htm

whGlossary.xml

Glossary index data - XML support

whidata0.htm

Index data for non-XML browsers

whidata.js

JavaScript supporting WHIDATA0.HTM

whidata0.xml

Index data - XML version

whidx.htm

Index of index data - HTML support

USING ROBOHELP HTML 8 295

Last updated 3/1/2010

Generating Help and printed documents

File

Description

whidx.js

Index of index data - JavaScript supporting whidx.htm

whidx.xml

Index of index data - XML version

whtdata0.htm

TOC data - HTML support

whtdata.js

TOC data - JavaScript supporting whtdata0.htm

whtdata0.xml

TOC data - XML support

whtoc.htm

TOC index of TOC - HTML support

whtoc.js

TOC index of TOC - JavaScript supporting whtoc.htm

whtoc.xml

TOC index of TOC - XML support

Output files in the Whxdata subfolder
Files in !SSL!\Webhelp\Whxdata are used in Java applet and DHTML versions of WebHelp on newer browsers.
File

Description

whftdata0.xml

Full-text search data

WHFTS.XML

Full-text search index data

WHFWDATA0.XML

Full-text search keywords

WHGDATA0.XML

Glossary definition data

WHGLO.XML

Glossary index data

WHIDATA0.XML

Index data

WHIDX.XML

Index of index data

WHTDATA0.XML

TOC data

WHTOC.XML

TOC index of TOC

Distribute FlashHelp
Users need a browser and Flash Player 8.0 or later to view FlashHelp. If the Help system is stored locally, the.
By default, all FlashHelp output files are placed in a project subfolder (!SSL!/FlashHelp). When you generate
FlashHelp, you can specify the name of the folder where the FlashHelp source files are located, and the name of the
start page.
If the project includes subfolders, the FlashHelp folder includes these subfolders with the files in them. Do not rename
or move any of these folders to keep the project structure intact.

Distribute FlashHelp with an application
❖ Copy the FlashHelp Folder and its contents to a location designated by the developer. Let the developer know which

.htm file is the start page.

Publish FlashHelp to a disc, server, or desktop
1 Copy the FlashHelp folder and its contents to a disc, server, or local desktop.
2 Let users know which start page (.htm file) to select to view the Help system.

USING ROBOHELP HTML 8 296

Last updated 3/1/2010

Generating Help and printed documents

Output files for FlashHelp
Output files are created when you use RoboHelp to generate FlashHelp. During project generation, output files are
saved by default in a subfolder named FlashHelp.
Output files in the FlashHelp folder
File

Description

cshdat_WEBHELP.htm

Legacy support file for context-sensitive API

*.css

Style sheet

*.FHS

FlashHelp skin file

WF_TOPICS.CSS

Style sheet for customized topic scroll bars. Generated based on settings in FlashHelp skin

EHLPDHTM.JS

Contains JavaScript functions that RoboHelp uses for advanced functionality such as Dynamic
HTML effects

.GIF files

Images for skins, navigation, and browse sequence images

<ProjectName>.htm

Project start page

<ProjectName>_csh.htm

Legacy support file for context-sensitive API

<ProjectName>_rhc.htm

Context-sensitive Help API support file

wf_favicon.ico

Icon for Favorites menu in Internet Explorer

WF_*.HTM

FlashHelp run time FLA files

SKIN_*.SWF

Skin files

WFRES.XML

Localization file (generated from LNG file) that contains all strings loaded into FlashHelp at run
time

WHPROJ.XML

Project file used by the DHTML version of FlashHelp to load navigation data

whmozemu.js

Functions supported in Netscape Navigator

WF_MASTER.JS

JavaScript file required for FlashHelp run time

wf_dispatcher.js

JavaScript file required for FlashHelp run time

whtopic.js

Topic support file (In-topic navigation bar)

whutils.js

Utility file for common functions

whver.js

Determines browser version

Output files in the whgdata subfolder
File

Description

whexpbar.gif

Used to size default navigation pane width

whlstf0.htm

Body of full-text search

whlstfl0.htm

Letters for full-text search level 2

whlstg0.htm

Glossary words list

whlsti0.htm

Index words list

whlstt0.htm

Contents list part 1

USING ROBOHELP HTML 8 297

Last updated 3/1/2010

Generating Help and printed documents

File

Description

whlstt1.htm

Contents list part 2

whnvf30.htm

TOC frame

whnvf31.htm

Index frame

whnvf32.htm

Full-text search frame

whnvf33.htm

Glossary frame

whnvl31.htm

Index letters level 1

whnvl32.htm

Full-text search letters level 1

whnvl33.htm

Glossary letters

whnvp30.htm

TOC navigation pane

whnvp31.htm

Index navigation pane

whnvp32.htm

Full-text search navigation pane

whnvp33.htm

Glossary navigation pane

whnvt30.htm

TOC tabs

whnvt31.htm

Index tabs

whnvt32.htm

Full-text search tabs

whnvt33.htm

Glossary tabs

Output files in the whxdata subfolder
The output files in !Sl!\Flashhelp\whxdata are XML data files used in Java applet and DHTML versions of FlashHelp
running on later browsers.
File

Description

whftdata0.xml

Full-text search data file

WHFTS.XML

Full-text search index data file

WHFWDATA0.XML

Full-text search keyword data

WHGDATA0.XML

Glossary definitions data file

WHGLO.XML

Glossary index data file

WHIDATA0.XML

Index data file

WHIDX.XML

Index of index data file

WHTDATA0.XML

TOC data file

WHTOC.XML

TOC index of TOC file

Note: Do not import FlashHelp-generated HTM output files into the project. They are used for runtime purposes only.

Distribute Microsoft HTML Help
1 Distribute the following system Help files to the developer for installation with the program executable (EXE) file.

Or, distribute the files for stand-alone use.

USING ROBOHELP HTML 8 298

Last updated 3/1/2010

Generating Help and printed documents

Note: Users can run stand-alone Microsoft HTML Help by double-clicking the CHM file in Windows Explorer.
CHM A single distributed Help system in a single Help file, in addition to any CHM files for subprojects to the

master project. These child CHM files aren’t compiled into the master CHM.
HLP, CNT If the project includes links to topics in a compiled WinHelp file, distribute the HLP and CNT files. They

are not compiled into the master CHM file
DOC, PDF, XLS If the project includes links to external files, distribute the external files. They are not compiled into

the master CHM file unless they are added to the Baggage Files folder.
2 The application developer distributes the following support files, depending on the features used in the project and

the versions of Windows that users have.

• Microsoft HTML Help Support Files Built-in components.
• HHActiveX.DLL is an Adobe ActiveX control that provides support for online glossaries and browse sequences.
Install and register the HHActiveX.DLL file on user systems. Copy this file from C:\Program
Files\Adobe\Adobe RoboHelp [version]\RoboHTML into the same folder as the CHM.

• If the Help system includes third-party ActiveX controls, install and register the component support files for the
user systems. Users copy the ActiveX control files into a custom folder, placing the path for the alternate folder
before the .ocx or .dll extension, and then register the files.
Note: The Adobe licensing agreement lets you redistribute Microsoft HTML Help and Internet Explorer files with the
HTML Help output.
Register ActiveX controls
If the project provides ActiveX controls, provide these instructions to users so they can register the controls that you
distribute with the Help system.
1 Choose Start > Run.
2 To register the HHActiveX.DLL file, type the following command, specifying the HHActiveX.DLL path, and click OK:
regsvr32 [path] hhactivex.dll

3 To register third-party ActiveX controls, type the following command:
regsvr32 [activex_name.dll or activex_name.ocx]

More Help topics
“Create a project” on page 23
“Manage files” on page 39
“ActiveX controls” on page 323

Distribute JavaHelp
Distribute the following files and components:

• If the project is compressed, distribute the JAR file.
• If the project is not compressed, distribute all source files in the output folder.
• JavaHelp 1.1.3 or later components.
• Java Runtime Environment file (JRE), or have users download it from the Sun website.
• If the project contains related topics buttons, distribute the Bsscjhrs.jar file.

USING ROBOHELP HTML 8 299

Last updated 3/1/2010

Generating Help and printed documents

Output files for JavaHelp
Output File

Description

.HS

HelpSet file. Points to a set of map files and defines associated navigational views (TOC, index,
and search).

.JAR

Compressed JavaHelp file (optional) containing all project output.

default.css

Default cascading style sheet file applied to all project topics.

projectname_ndx.xml

Index file describing content and layout for the index view.

projectname_map.xml

Map file associating Help topic IDs to HTML files with relevant content, and Window Types. Used
in the API for context-sensitive calls, TOC, and index.

projectname_toc.xml

TOC file describing content and layout for the TOC view.

Distribute Oracle Help
When you generate the output, you can compress all source files into a single JAR file. The JAR file is used for software
application Help, and for distribution as a stand-alone product.
❖ Include the following components when you distribute Oracle Help:

• If the project is compressed, the JAR file
• If the project is not compressed, all files and subfolders in the OracleHelp output folder
• JavaHelp 1.1.3 or later components
• Java Runtime Environment (JRE) or Java Development Kit (JDK)
Output files for Oracle Help
File

Description

.HS

HelpSet file. Points to a set of map files and defines associated navigational views (TOC, index,
and search).

.JAR

Compressed Oracle Help file (optional) containing all project output.

default.css

Default cascading style sheet file applied to all project topics.

Projectnumber_fts.idx

Full-text search file containing the full-text search database.

Projectnumber_nd.xml

Index file describing content and layout for the index view.

Projectnumber_lnk.xml

File containing associative links (See Also controls) to topics associated with See Also keywords.

Projectnumber_map.xml

Map file associating Help topic IDs to HTML files with relevant content, and Window Types. Used
in the API for context-sensitive calls, TOC, and index.

Projectnumber_toc.xml

TOC file describing content and layout for the TOC view.

Distribute XML output
During generation, CSS, XSL, XML, HTM, and GIF output files are created in a subfolder in the project folder. Other
files include the following:

USING ROBOHELP HTML 8 300

Last updated 3/1/2010

Generating Help and printed documents

Output files In XML_Output folder

Description

EHLPDHTM.JS

Contains JavaScript functions for advanced functionality

NewProject.htm

Project start page

NewProject.log

Output file that lists all necessary files

More Help topics
“View output” on page 285

Distribute Adobe AIR output
Distribution of Adobe AIR output depends on the output type you select.
Output type

File(s) to distribute

Required on user computers

Adobe AIR Application

AIR (.air) file generated in the output location

AIR Runtime
See Adobe AIR Runtime Distribution

Browser Based Help

All files generated in the output folder

Flash plug-in 9.0 or later

When distributing browser-based Help as a
See Configure FlashPlayerTrust to
standalone Help system, copy the output folder and run local browser-based Help.
its contents to a CD, a server, or any location on user
systems. Let users know the start page (HTM file) to
select to view the Help system.
AIR Application And Browser Based
Help

Separately distribute:

AIR Runtime

AIR (.air) file generated in the output location

Flash plug-in 9.0 or later

All files generated in the output folder
Help Content Only

RHA (.rha) file generated in the output location

AIR Runtime

Configure FlashPlayerTrust to run local browser-based Help
To run browser-based Help from a local drive, the installation folder must be added in the list of trusted folders defined
in the RoboHelp.cfg file of in the FlashPlayerTrust folder.
1 Select Start > Run.
2 Type %appdata%\Macromedia\Flash Player\#Security\FlashPlayerTrust\ and click OK.
3 Open the RoboHelp.cfg file in a text editor.
4 Add the path to the local folder in which the browser-based Help files are stored.

Printed documents
About printed documents
Online output and printed documents share source files. Similarly, you can generate PDF files and print documents
from the same source files.

USING ROBOHELP HTML 8 301

Last updated 3/1/2010

Generating Help and printed documents

Organize and customize content
Design a printed document based on only part of the project or the entire project. Determine where topics go in the
document by arranging the pages and books during generation. Base printed document structure on the project TOC
or select topics from custom folders in the Project Manager.
Map project styles to Word
Control how styles are used in printed documents with style mapping. Copy project styles directly to a Word
document. Any applied project style retains the style in Word. You can alternatively skip style mapping and use topic
styles.
Types of Word documents to create
Individual documents Separate Word files for the title page, table of contents, glossary, and index. A separate
document is also created for each root-level book (chapter) and page in the printed table of contents.
Master document An optional document that links to the individual documents. Familiarity with master documents
in Word is recommended. Do not edit this file; it contains only field codes referencing the documents. Do not use a
master document for large manuals.
Single document One Word file containing the title page, TOC, chapters, glossary, and index.

Printed document structure
• Books and pages at the root level of the printed document begin a new chapter.

• Subbooks and pages that are not at the root level of the printed document continue uninterrupted.
• For books that link to pages, the link destination is placed directly after the book in the printed document.
• Pages that link to a destination other than a topic are not available to use in the printed document.
• Organize sections of the printed documentation output in the Section Layout dialog box.
Conversion of online features
RoboHelp converts many common project features. It removes others, including ActiveX controls, borders, Dynamic
HTML, headers and footers, JavaScript, link controls, and topic borders. The following table provides conversion
details for specific features.
Feature

Conversion notes

Bullets and numbering

Converted (except image bullets).

Conditional build tags

Topics and topic content that are excluded with conditional build
tags and expressions are removed.

Drop-down hotspots and expanding hotspots

If specified, expanding text and drop-down text appears inline.
Map a style to hotspots so that they look different from the other
text.

Expanding glossary hotspots

Selecting expanding text and drop-down text in the printed
output converts and displays inline. Map a style to hotspots so that
they look different from the other text.

Font sets

Word uses the first font. If the first font does not exist, Word creates
a default font.

Forms

Converted to HTML in Word. Third-party forms are removed from
documents.

USING ROBOHELP HTML 8 302

Last updated 3/1/2010

Generating Help and printed documents

Feature

Conversion notes

Images

Specify whether you want to place or embed images. Placed
images are included in an images folder in the output folder.
Embed images if you want to place them within the document.
Images can be included in headings, and then they also appear in
the printed TOC.

Marquees

Converted as text in Word.

Positioned text boxes

Converted and placed at the end of the document or the bottom of
the page.

Shading

Fills but not patterns are converted.

Text boxes

Converted and resized to fit text only.

Page setup
RoboHelp assigns default page settings to the printed documentation in Microsoft Word.

Body page settings
Starting Page All documents start on an odd-numbered page. If the document ends on an odd-numbered page, a
blank page is added at the end of the document. The blank page lacks a header, footer, or page number.
Headers Headers repeat at the top of each page and are blank on the first page of sections. The name of the document

appears on even-numbered pages, left-justified. The name of the root chapter appears on odd-numbered pages, rightjustified.
Footers Footers repeat at the bottom of each page and contain page numbers. Page numbers are left-justified on even-

numbered pages and right-justified on odd-numbered pages.
Page Numbers Page numbers are located in footers and are generally Arabic (1, 2, 3, and so on). The TOC document

uses lowercase Roman numerals (i, ii, iii, and so on).

Additional settings
To create Microsoft Word documents, note the following details for the source files and set them up accordingly.
Title page
• The title page uses settings from the document.

• Specify a default title page when you generate the printed documentation.
• The name of the document (which appears on the title page) is the printed document name you define in the Print
Document General dialog box. This dialog box appears when you double-click the Printed Documentation layout.

• The header and footer are blank.
• The title page contains no page number.
• The title page document uses the style TitlePageTitle that is copied to the Word document.
• The filename is Chapter_{##}_Title_page.doc.
• When you add the file, copy it to the project folder if you want RoboHelp to generate a copy in the output folder.
Table of contents
• The TOC is based on the heading levels of topic titles and the printed document structure hierarchy. You can define
the printed document structure in the Print Document Content dialog box.

USING ROBOHELP HTML 8 303

Last updated 3/1/2010

Generating Help and printed documents

Note: You can also create a TOC from the Project Manager. Right-click a topic in the TOC pod, and choose AutoCreate TOC. Topics from the Project Manager are automatically promoted or demoted in heading style depending on
their placement in the printed document structure.

• Most TOCs have multiple levels of headings, showing a hierarchy, or structure, of information to help users find
information more quickly.

• TOC 1 – 9 are the styles used for TOC entries.
• Table Of Contents Page Title is the style used for the title of the TOC.
• Page numbers for the TOC document are lowercase Roman numerals (i, ii, iii, and so on).
• The filename is Chapter_00_Table_Of_Contents.doc.
Chapters
• Chapter files contain the topics you specified in the Print Document Content dialog box. Root-level topics and
books create new documents (except if you select the Single Document option when you generate).

• Page numbers for chapter documents are Arabic (1, 2, 3, and so on).
• The filename is Chapter_{##}_{Book or Page Name}.doc.
Glossary
• The glossary is based on the terms and definitions in the project. If no terms and definitions exist in the project, a
glossary document is not generated.

• To convert expanding glossary hotspots, click the Start Glossary Hotspot wizard icon in the Glossary toolbar in the
Glossary pod. You can specify whether definitions are converted to inline text, and whether inline text appears in
the paragraph where the term appeared.

• The glossary document uses three styles that are copied to the Word document:
Glossary Heading The style used for the header letters (A, B, and so on). If the project has a specified language, the
header letters are localized in that language.
Glossary Label The style used for the glossary terms.
Glossary Definition The style used for glossary definitions. Definitions appear on the same line as terms, with a
hanging indent for subsequent lines.

• Page numbers for the glossary document are Arabic (1, 2, 3, and so on).
• By default, the filename is Chapter_{##}_Glossary.doc. ## is the number after the last chapter number.
Index
• The index is based on the keywords and subkeywords in the project. Topic keywords are included only if the
associated topics are generated in the output.

• Index styles are based on the style Index Heading and Index 1-9 in the Word template you select for the printed
documentation.

• By default, the index is indented with two columns. If the project has a specified language, the header letters are
localized in that language.

• Page numbers for the index document are Arabic (1, 2, 3, and so on).
• The filename is Chapter_{##}_Index.doc. ## is the number after the glossary chapter number. If the document
contains no glossary, it is the number after the last chapter number.

USING ROBOHELP HTML 8 304

Last updated 3/1/2010

Generating Help and printed documents

Accessory pages
• An accessory page, such as an acknowledgment, appendix, foreword, or copyright, retains its original formatting.

• The filename is Chapter_{##}_{Document name}.
• When you add the file, you can copy it to the project folder. A copy is also generated in the output folder.
• Add new sections using the Section Layout dialog box.
Images
You can handle images in these ways:
Embed In Documents Keep images within the document. Embedding images creates larger DOC files that are not
dependent on outside image files.
Link To Documents Reference the images outside the document (creates smaller DOC files that reference outside

image files). Image files are copied and stored in the Images folder in the printed document output folder.
Images in heading styles are removed. Change settings to include images in headings.

Organize and customize document content
1 In the Single Source Layouts pod, double-click Printed Documentation.
2 In Printed Document General, set general options for the printed document.
Name Specify the name of the document. This name is used in the document headers and on the title page.
Location Specify the path for Word documents. PDF documents also are saved to this location. Creates the printed

documentation files under !SSL!\[layout name] in the project folder. Click the Browse button to browse to a
different folder. Click OK.
Note: Printed Word documentation supports both DOC and DOCX formats.
PDF Settings Set PDF properties.
Settings Select options for document files creation.

• Generate Individual Documents Create a separate Word file for each chapter and section of the document. A
chapter is any book or page at the root level of the TOC specified in the Print Document Content dialog box.

• Generate A Single Document Create one Word file that contains the title page, TOC, chapters, glossary, and
index.
Note: If Generate Individual Documents is selected, click Create Master Document to enable viewing of all documents.

• Retain Hyperlinks Select to retain hypertext links.
• Start Each Topic On A New Page Select to create page breaks.
Images Set image options.

• Embed In Documents Keep images within the document.
• Link To Documents Reference the images outside the document. Image files are copied and stored in an Images
folder in the printed document output folder.
By default, images that are included in heading styles are removed. To select to include them, click the Advanced
button and select Images In TOC.
Define Click to specify conditional build expressions.

USING ROBOHELP HTML 8 305

Last updated 3/1/2010

Generating Help and printed documents

Content Select TOC, index, and glossary to display in the generated Help.
Variable Set Select a variable set for the printed document.
Advanced Specify detailed TOC, glossary, and text options.

3 Click Next.
4 In Print Document Content, under Topics, click the pop-up menu to display and select topics.
Show All Topics Displays all topics regardless of conditional build tags.
TOC Displays all topics in TOC
Folder buttons To show topics in the Project Manager pod, select the folder button for a custom folder, a Top Level
Folder, or All Folders. (View topics by title or filename.)

5 Under Topics, select the topics to add and design the TOC.

Select Maintain HTML Heading Levels to disable automatic mapping. Heading style levels are retained. If the
printed document structure does not match the structure in the Chapter Layout column, rework it in Word.
Drag and drop topics from the left to the right. The topic icon on the left turns blue to indicate that the topic is
added.
Topics excluded in the General dialog box using conditional build tags have a gray icon in the Chapter Layout
column.
Missing topics are displayed with a broken page icon

6 Under Chapter layout, edit or reorganize the content.

To add a new book, click the New Chapter button. To move a book or page, click the arrow buttons.
Moves an item to a higher level in the TOC.
Moves an item to a lower level in the TOC.
Moves up an item up in the TOC.
Moves an item down in the TOC.
7 Click Next to set the section layout for the document.

The left column lists each section of the document. Chapter Layout in the right column represents the topics as you
organized them in Print Document Content. You can add, remove, or sometimes reorder the sections. You can also
edit an added section.
Click to add a section. Locate the file, select it, and click Open.
Click to remove a section.
Select the added section in the left column, and click to edit it. Save in Microsoft Word. The changes are
included in the printed document.
Use the arrow buttons to position a section in the printed document.
8 Do one of the following:

• Select Next to map styles.
• Save changes.
• Select Finish to generate. When the PrintDoc.dot macro message displays, click Disable Macros to continue.
When the PrintDoc.dot macro message displays, click Disable Macros to continue.

USING ROBOHELP HTML 8 306

Last updated 3/1/2010

Generating Help and printed documents

Notes:
• All Microsoft Word documents must be closed.

• Document content changes do not affect TOCs.
• TOCs updated in the TOC Composer do not affect the chapter layout.
• To use the updated TOC, click Remove All. Then click Add All.

Prepare for printed documents
Printed document organization
• Before generating, print a Table of Contents Report. Choose Tools > Reports > Table Of Contents. Place a check
mark next to the topics for the printed document so that you can easily identify them when the document is
generated.

• For large documents, create individual documents. Place more books at the root level in the printed document
structure to create more DOC files. Otherwise, the printed document includes only several large files. Do not create
documents over 100 pages long.

Styles and formatting
Ensure that both project styles and template styles are ready for generating.
Apply styles to all topic text
When using a Word template for printed documentation, ensure that all topic text has a style applied from an external
style sheet.
Inline formatting does not map to styles in Word and is converted as inline formatting.
Embedded styles do not map into Word. They are converted to inline styles. If any topics use embedded styles, link an
external style sheet to the topic and apply styles to the text.
Apply styles to topic headings
To treat topics as separate sections instead of continuing text, ensure that all topic headings have a Heading Style. Also
place them at the root level of the printed document structure.
If a custom heading does not use the RoboHelp heading style names in the format Heading [number], the topic doesn’t
appear in the TOC. To solve this problem, modify one of the RoboHelp heading styles with settings from the custom
heading style.
Use styles consistently
Printed documentation maps styles in the project to styles in Word.
Apply project styles consistently throughout the topics. For example, instead of applying inline styles, such as bold, to
text, apply a character style that uses bold. Consistency ensures that the printed TOC converts as expected and that
you can update styles globally later, if needed.
Select a template
• Custom template

• RoboHelp Style Mapping.dot template
• A Word default template

USING ROBOHELP HTML 8 307

Last updated 3/1/2010

Generating Help and printed documents

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
in the Print Document Content dialog box.
are denoted with a gray question mark icon

More Help topics
“Define conditional build tag expressions” on page 210

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.
• Books that link to pages are treated like topics.

USING ROBOHELP HTML 8 308

Last updated 3/1/2010

Generating Help and printed documents

RoboHelp makes these heading adjustments when it creates the printed document TOC.
Paragraph styles Paragraph styles can be mapped only to paragraph styles in Word. They apply to font attributes, line

spacing, numbering, and borders and shading.
Character styles Character styles can be mapped only to character styles in Word. They apply to font attributes.
Embedded styles Embedded styles that are not defined in the external style sheet are applied inline in the Word

document. They are not available for global use.
Inline styles Inline styles are applied inline in the Word document and are not available for global use in the template.
List styles List styles can be mapped only to list styles in Word.

Unmapped styles
The following styles aren’t available for mapping:

• Background + Text (BODY). These style settings are applied inline.
• Heading styles.
Unmapped styles denoted by Unassigned - Use Style In Project in the Print Document Appearance dialog box are added
to the Word document. This style has the same attributes as the project style. To access the Print Document
Appearance dialog box, double-click a printed documentation layout in the Single Source Layouts pod, and click Next
three times.

Style naming
Mapped template styles retain the name of the Word template style.

Styles that RoboHelp adds
If title page title, TOC title, and glossary definitions, terms, and headings are defined in the selected Word template,
RoboHelp maps them to the Word document.

Duplicate styles
If the project has multiple style sheets with duplicate style names, the most frequently used style is mapped.

Map styles
1 Double-click Printed Documentation in the Single Source Layouts pod, and click Next until Print Document

Appearance appears.
Project styles appear on the left. Matching template styles appear on the right. If a matching style is not found, you
see [Unassigned - Use style in project]. Heading styles, which are mapped automatically, are not listed.
2 Under Microsoft Word Template, select a template already in the project or another template option from the pop-

up menu.
(None) Use The Project's CSS Styles Formats from topics, not from a template.
Use Microsoft Word Templates In the Select Template File dialog box, open a template. Choose copy to the project
folder or overwrite an existing template. Click Yes to enable quick access to the template. To share the template with
other authors and maintain it in one location, click No.
Style Mapping. dot Uses default template.

USING ROBOHELP HTML 8 309

Last updated 3/1/2010

Generating Help and printed documents

Browse
Lets you select a custom template not yet in the project, or browse to the location of a ZPL file from
another layout. Click Browse Files to browse to the location of the desired template. Select copy to the project folder
or overwrite an existing template.

Note: If the template you select has the same name as one of the default Word templates, _RHT is added to the custom
template name.
3 Under Project’s CSS Styles, select a project style to map to a template style. A sample of the selected style is displayed

underneath Preview.
Project’s CSS Styles (All) Displays all styles in the project.
Project’s CSS Styles (Used Only) Displays only the styles used in the project.
Character Preview the font attributes of a style.
Paragraph Preview the font attributes and spacing of a style.
Description Preview a text description of a style.

4 Under Microsoft Word Template Styles, select the pop-up menu to display template styles.
Microsoft Word Styles (All) Displays all styles in the template including Word defaults.
Microsoft Word Styles (User Defined) Displays only user-defined styles.

Note: Styles must be mapped to other styles of the same type, character to character and paragraph to paragraph.
5 Select a style, and map all desired project styles, selecting them from the pop-up menu of the selected Microsoft

Word style.
6 Map all desired project styles.
7 Click Finish to generate.
8 When the macros message appears, click Always Trust Macros From This Publisher. Then click Enable Macros.

Printed documentation files appear under !SSL!\[layout name] in the project folder.
9

Click View Result to view the output, or click Done.
Microsoft Word opens the document. Depending on the settings selected, the TOC, master document, or a single
document is displayed.

Export style maps
Ensure that the project styles are all mapped to the same Word template styles.
1 Open the project.
2 Create a printed documentation layout.
3 Map the styles. Save the settings.
4 In the Single Source Layouts pod, right-click the layout containing the style map to export. Select Export

Preferences.
5 Browse to the destination for the style map. Click Save.

Import style maps
Share style maps to ensure that the project styles are all mapped to the same Word template styles.
1 In the Single Source Layouts pod, right-click the printed documentation layout. Select Import Preferences.
2 Browse to the exported style map (.zpl file).

USING ROBOHELP HTML 8 310

Last updated 3/1/2010

Generating Help and printed documents

3 Select Open.

• If the template associated with the style map is not in the project, select Yes to copy it to the project folder.
• Select Yes to overwrite the template.
When you generate output, the imported style map is used.
4 To edit the style map after it is imported, right-click the layout. Select Properties. Set options and click Next for each

screen of the Properties dialog box.
5 Click Save.

Generate PDFs
PDFs retain links, bookmarks, formatting, graphics, fonts, special characters, and colors.

Generate a PDF
1 Open the project.
2 Click File > Generate > PDF.

Generate a PDF with setup options
1 In the Single Source Layouts pod, double-click the printed documentation layout.
2 In the Output Format area, select Generate Adobe PDF.
3 Click PDF Settings. Set options.
4 Select options on each screen to set up the chapter layout, the section layout, and the styles. Click Next to progress

through the screens.
5 Click Finish.
6 (Optional) Click View Result.

Generate printed documents
You can create printed documentation and single-source layouts, and generate PDF files simultaneously with printed
documents.
If no template is used, every document retains the formatting used inside the topics.
1 In the Single Source Layouts pod, double-click the printed documentation layout.
2 Select options in the Print Document General dialog box.
3 Arrange the document structure in the Print Document Content dialog box.
4 Map Microsoft Word styles in the Print Document Appearance dialog box.
5 Copy hand-coded or added files to another location before generating the layout.
6 Click Finish. Click Disable Macros.
7 Click View Result. Select individual documents or a single document in the Print Document General dialog box.

By default, printed documentation files are created under !SSL!\[layout name] in the project folder. Templates are
saved in the root project folder.
Note: Some list items do not convert properly when generating printed documents with 1500 or more list items without
Microsoft Office 2000 SP-2 or later installed.

USING ROBOHELP HTML 8 311

Last updated 3/1/2010

Generating Help and printed documents

Specify default printer options
You can configure the default printer settings from within RoboHelp. The options that are available vary according to
the selected printer.
Note: The settings you specify affect how documents print in other Windows applications.
Settings include:
Paper Size Specifies the size of the paper.
Paper Source Specifies the location of paper in the printer. Options vary according to the printer. Examples of paper

source are upper tray and envelope feed.
Orientation Specifies if the orientation is Portrait or Landscape.
Margins Specifies left, right, top, and bottom margins in inches.

Skins
About skins
Use skins to change the appearance of WebHelp and FlashHelp systems. Skins apply to the left side of a window and
the toolbar across the top of the output. Customize the Help system by changing colors, buttons, fonts, and icons, and
by adding backgrounds and logos.
RoboHelp includes predefined skins in the RoboHelp Skins Gallery.

Edit skins
Edits to skin properties take effect the next time you generate using the skin.
Note: If you localize a project, default skin text is translated using the project language setting. If you edit skin text,
RoboHelp overrides customizations in the LNG file.
1 In the Project Set-up pod, expand the Skins folder.
2 Right-click a skin. Select Edit.
3 Click the Toolbar tab. Set options, as needed:

Note: Some options aren’t available, depending on the output type.
Main Lists items that appear on the main toolbar.

(WebHelp and WebHelp Pro only) Click to add a custom button to the main toolbar.
In the Custom Toolbar Item dialog box, define the text, image, or both for the button on the Text tab. Type spaces
before or after the text to add space between the edge of the button and text.

Add custom toolbar item

On the Action tab, define a link or a script for the button:

• Link Link the button to a URL. Type the path or click the Browse button
copied to the skins folder (ProjectName\!SkinSubFolder!\YourSkin).

to browse to it. Linked files are

For JavaScript, specify the function calls for these actions:

• Onload Specify a function to call when the page containing the button is loaded (MyFunction())
• OnMouseOver Specify the function to call when the pointer is over the button.

USING ROBOHELP HTML 8 312

Last updated 3/1/2010

Generating Help and printed documents

• OnClick Specify the function to call when the button is clicked.
Under Advanced, add or remove dependent files for the custom toolbar item when using the multi-author feature.

• Dependencies Lists the dependent files already added. Click Add to specify the name of another dependent file.
• Add Browse to the location of a dependent file. Click OK. External files are copied to the project folder
automatically.
• Remove Remove a dependent file from the Dependencies list. An image in the custom toolbar cannot be
removed. Files are removed only from the RoboHelp software, not from the hard disk.
• Inline JavaScript Write function definitions for custom button functions in the project.
• External JavaScript File Browse for and select the file.
Remove custom toolbar item

Click to delete a selected custom toolbar item.

Contents, Index, Search, Glossary Select the button to change and click the Edit button

to edit the button text

or to place an image on the button.
Search Input Double-click to edit the field that appears in the toolbar and the Search pane. The button options

apply to both the toolbar and the Search pane. The Caption and the Text Box Width apply to the toolbar only. The
box can be from 10 to 40 characters wide.
About Select and click Edit to change which image is displayed in the upper right of the main toolbar. Specify an

About Button image, which is copied to the Skins folder. Then specify the following information, as needed for the
output format:

• Image Select an image to display at the left of the About box.
• Company Enter the company name, which is displayed below the logo. This text is a hypertext link to a URL
specified under URL.
• Copyright Enter a copyright notice.
• URL Enter a web address for the company website.
• Title Image Specify an image to display at the top of the About box. Keep the image smaller than 211 by 60
pixels.

• Author Identify the system or give more information to users.
• E-mail Enter the e-mail address of the author.
Navigation Bar Modify the items directly under the main toolbar

Previous, Next, Sync TOC, and Hide Select the item to change and click Edit to change the image for the button.

The Previous and Next buttons let users move back and forward through a series of topics you define in browse
sequences. You can change the image shown for the buttons when they are enabled and disabled. Enabled indicates
that the user can click the button for more topics. Disabled indicates that no topics exist in that direction.
You can change the image for the Sync TOC button. When you generate, select Synchronize TOC (Manually) to
ensure that the button appears on the navigation bar.
Note: The Hide button does not appear in all versions of Netscape Navigator when the output uses a skin.
4 Click the Navigation tab. Click the browse buttons

to select images, and specify other settings as needed:

Note: The toolbar is automatically resized to accommodate images. Images are tiled in backgrounds for the content
and label region backgrounds.
Topic/Page Select an image for TOC topics.

USING ROBOHELP HTML 8 313

Last updated 3/1/2010

Generating Help and printed documents

Remote URL Select an image for links not in the project.
Background Image Select an image to use in the background of the content region. The images are tiled.
Hover Color Select a color to display when the pointer moves over links.

5 Click OK.
6 To rename the selected skin, right-click, select Rename, and type a name in the Name box.

Note: You cannot rename skins in the gallery.
7 Click Update View to view updates. Click Preview to see the full skin.

Tips:
• Use URL icons for website links, or use folder icons instead of book icons.

• To use TOC icons that are a different color, browse to the Image Gallery. The gallery is in C:\Program
Files\Adobe\Adobe RoboHelp [version]\ RoboHTML\gallery\images\Books_and_Pages. You can also edit the
image color in a graphics editor.

• When generating a project with custom toolbar items, select the custom button in the Navigation dialog box.
• To remove a button from a skin without deleting the image file, clear the option when you generate the project. Do
not clear it in the WebHelp Skin Editor.

• Additional files, such as image files or JavaScript files for buttons, reside in the Project
Folder\!SkinSubFolder!\<Skin Name>. The skins reside in separate subfolders in the !SkinSubFolder! folder.

• To specify a script that uses other files (such as HTML files or image files), copy these files to the skin subfolder
under !Skinsubfolder!.

Add skins to the gallery
Store or reuse skins by adding them to the Skins Gallery.
1 In the Project Set-up pod, expand the Skins folder.
2 Right-click a skin. Select Add To Gallery.

Import skins
When you import WebHelp SKN files or FlashHelp FHS files, all associated files are added to the skins subfolder. You
can also import a compressed ZKN (for WebHelp) or FHZ (for FlashHelp) file.
1 In the Project Set-up pod, right-click the Skins folder. Select Import.
2 Navigate to a skin file or a compressed skin file.
3 Select the file. Click Open.
4 (Optional) Type a name and filename for the skin.
5 Click OK.

You can select this skin the next time you generate output.

Export skins
Exporting a skin saves it as a compressed file that contains the skin and its associated files.
1 In the Project Set-up pod, expand the Skins folder.

USING ROBOHELP HTML 8 314

Last updated 3/1/2010

Generating Help and printed documents

2 Right-click a skin. Select Export.
3 Navigate to the location for the exported skin. Click Save.

Delete skins
1 Do one of the following:

• To delete a skin from the project, select it in the Skins folder in the Project Set-up pod.
• To delete a skin from the gallery, select the skin in C:\Program Files\Adobe\Adobe RoboHelp
[version]\RoboHTML\Sqskinsext\Gallery.
2 Press Delete.

Preview skins
You can preview skins for WebHelp, WebHelp Pro, FlashHelp, and FlashHelp Pro projects.
1 In the Project Set-up pod, expand the Skins folder. Select a skin.
2 In the toolbar, click the View button

Create custom skins for WebHelp and WebHelp Pro projects
The custom skin is saved as an SKN file to [Project folder]\!SkinSubFolder!\[skin name].
If you create a custom a skin from a gallery skin, the gallery skin remains unchanged.
1 In the Project Set-up pod, right-click the Skins folder. Select New Skin.
2 Do one of the following:

• Select Create Custom WebHelp Skin. Click OK.
• Select Create Skin From Gallery. Click OK. Select a skin. (Optional) Click Preview to view the selected skin.
3 Set options in the toolbar and Navigation panes.
4 Click Update View to view changes in the dialog box. Click Preview to view the changes in a separate window.
5 Click OK. Type a name and filename for the skin, including the .skn extension.

You can use the skin the next time you generate output.
To share a skin file (SKN) with others, define all customizable elements of the skin beforehand so that other authors
can include or exclude certain elements when they generate output.

Customize FlashHelp skins
You can customize FlashHelp skins by replacing elements in an existing skin with elements from another skin. You
also can create a skin with Adobe Flash or the RoboHelp Skin Development Kit.

Customize or create a skin with Flash
Use an existing compressed skin file (FHZ) from the RoboHelp Skin Gallery or create one.
1 Navigate to the SDK template folder in C:\Program Files\Adobe Robohelp [version]\FlashHelp SDK.

• To view the FlashHelp SDK documentation, open Help.htm or use the FlashHelp SDK.PDF.
• To distribute to a developer, share the FlashHelp SDK folder.

USING ROBOHELP HTML 8 315

Last updated 3/1/2010

Generating Help and printed documents

2 When finished with the skin, share the compressed skin file (optional). Then, import the skin into the project.
3 Preview the skin.
4 When generating a FlashHelp layout, select the skin from the FlashHelp Options dialog box.

Modify the skin without Flash
FlashHelp skins are composed of Flash skin files (SWF files). Each SWF file is used for different skin elements, such as
toolbar buttons and icons. Use Windows Explorer to replace individual SWF files in an existing skin with the SWF files
of another.
1 Ensure that the project contains all the skins to use by importing them.
2 Navigate to !Skinsubfolder!\[skin name].
3 Open the skin subfolder that contains the SWF files to copy.
4 Right-click the SWF file and select Copy.
5 Open the skin subfolder containing the SWF files to replace.
6 Paste and replace the files.
7 In RoboHelp, when you generate the project, select the newly modified skin in the FlashHelp Properties dialog box.

When project generation has finished, click View Result to test the skin.

Select and preview WebHelp or FlashHelp skins from the Skin gallery
1 In the Single Source Layouts pod, double-click a FlashHelp layout.
2 Click Gallery.
3 Select a skin. Click Preview to view it. Then click OK to select it.
4 Click Finish to generate the FlashHelp output.

The skin is added to the project and appears in the Skins project subfolder with a Flash icon

FlashHelp vertical-style skins
In vertical-style skins, toolbar icons have tool tips. Tool tips appear when the mouse hovers over the button.
Prefix the names of these skins with “Vertical,” such as Vertical-Breeze.
Note: Vertical-style skins do not have a Search field in the toolbar.

USING ROBOHELP HTML 8 316

Last updated 3/1/2010

Generating Help and printed documents

Example of vertical-style skins

Windows
RoboHelp supports WebHelp and FlashHelp windows for use with the context-sensitive Help API.

Create or edit windows
Note: This procedure applies to WebHelp, WebHelp Pro, FlashHelp, FlashHelp Pro, and HTML Help.
1 Specify the primary layout.
2 In the Project Set-up pod, right-click the Windows folder. Select New Window.
3 Type a name and caption in the text boxes.
4 Set options. Many of the options are common to all the output types.
Placement To change placement visually, point and click inside the sample window. To change size visually, point

to a border in the sample window. To use exact measurements, in Placement, enter values in Top and Left for the
position (percent of the browser window). To resize, enter values in Height and Width.
Windows To Display Selected windows appear in the preview area of the upper-left corner.

5 Click OK.

For JavaHelp and Oracle Help projects, set navigation pane options when you generate output.

USING ROBOHELP HTML 8 317

Last updated 3/1/2010

Generating Help and printed documents

More Help topics
“Specify the primary layout” on page 256

WebHelp, WebHelp Pro, FlashHelp, FlashHelp Pro Options
In addition to the standard Window Properties options, WebHelp Pro provides the following options. In WebHelp
Pro and FlashHelp Pro, you can view settings after the project is published to the server.
Buttons Click the up and Down Arrows to change button order as the buttons appear in the browser. Select the

buttons to include. You can customize these buttons or add new buttons using skins.
Set As Default Click to set the selected button as the default. Contents is the default.
WebSearch Displays the WebSearch button. This button is available only if enabled in the project.
Browse Sequences Enables support of browse sequences if you created them. The window contains Previous and Next

buttons. Use skins to customize them.
Search Input Field In Toolbar Adds the Search button to the toolbar. Use skins to customize the Search Input Field.
Use Default Browser Settings Select to use the user default browser size, toolbars, placement, and other properties.

When deselected, the standard browser toolbar, menu, location bar, and status bar are available.

• Resizable Selecting this option lets users resize the window. This setting is available when used with the contextsensitive Help API.
• View Select One Pane to display the topic pane. Select Two Pane to also display the navigation pane.

HTML options
In addition to the standard Window Properties options, HTML Help provides the following options:
Buttons (HTML Help) Select buttons to display.
Button

Description
Opens and closes the navigation pane.

Hide/Show
Opens the previous topic.
Back
Opens the next topic in a pre-viewed sequence.
Forward
Stops a web page form displaying.
Stop
Updates the topic content.
Refresh
Shows the default web page.
Home

USING ROBOHELP HTML 8 318

Last updated 3/1/2010

Generating Help and printed documents

Button

Description
Opens menu access to Home, Show, Back, Stop, Refresh, Print, and Search Highlight On/Off.

Options
From the Contents tab, prints pages, headings, and subtopics or the entire TOC. From the Index
or Search tab, opens the Print dialog box.
Print

Locate

Click to synchronize books and pages in the Contents tab with the topics in the right pane. This
option differs from Auto-synchronize TOC, which synchronizes books and pages with topics as
users view topics.
Opens a web page, intranet site (defined with a URL) or help topic (defined by its filename if
included in the same file).

Jump1
Opens a web page, intranet site (defined with a URL) or help topic (defined by its filename if
included in the same CHM file).
Jump 2

Tri-pane Tabs And Windows Select tabs to include in the navigation pane. If you select TOC And Index and the project
does not include a TOC, the HTML help viewer does not display the Contents tab.

• TOC And Index Displays the Contents and Index tabs in the navigation pane. A navigation pane requires these tabs.
If you do not select this option, the navigation pane options are unavailable.
• Favorites Displays the Favorites tab in the navigation pane.
• Glossary Displays the Glossary tab in the navigation pane.
• Search Displays the Search tab in the navigation pane.
• Adv Search Enables users to search for topics using Wildcard and Boolean characters.
• Browse Sequences Enables support if you have created browse sequences.
• Default Tab Select the tab to display when the HTML Help project opens.
• Tab Position Select a default location for the window tabs.
Tri-pane Options Set properties for the onscreen appearance and behavior of the panes.

• Hide Nav Pane On Startup Hides the navigation pane. Click Show to open it.
• Auto Synchronize TOC Synchronizes books and pages in the Contents tab with the topic displayed in the right pane.
(For this feature to work properly, the Always Show Selection option must be active. To check if it is active, open the
single source layout and click Advanced Settings Edit. In TOC Styles, verify that Always Show Selection is selected.)
Make sure that the filenames have underscores, not spaces.
• Remember Window Size And Position Notes the last size and position of the viewer.
• Auto Show/Hide Nav Pane Automatically hides the left pane when users switch focus from the HTML Help viewer
to a program. The topic content remains visible but the left tabs are temporarily closed from view. These tabs appear
as soon as the HTML Help viewer is clicked.
Note: If you select Auto Show/Hide Nav Pane, click Advanced Properties > Extended Styles, and select Top-Most window.
This option prevents the right pane from being hidden behind the open application.

• Nav Pane Width Enter the width in pixels. The width to assign depends on the number of window tabs.

USING ROBOHELP HTML 8 319

Last updated 3/1/2010

Generating Help and printed documents

• Advanced Properties Specify advanced HTML windows properties on the Destinations, Styles, and Extended
Styles tabs. Some options require coding in the application.
Advanced window Destinations properties
Default Assign default topic.
Home Define the URL to display when clicking Home.
Table Of Contents Assign an alternate contents file (.HHC).
Index Assign an alternate index file (.HHK).
Button 1 Label Assign a label to Button 1.
Custom Button 1 URL defines the destination for Button 1.

Note: Custom 1 button does not reference external CHM files if Internet Explorer 5.5 is installed.
Button 2 Label Assign a label to Button 2.
Custom Button 2 URL defines the destination for Button 2.

Advanced window Styles properties
System Menu Includes a system menu. Window style ID is WS_SYSMENU.
Minimize Box Includes a minimize box. Window style ID is WS_MINIMIZEBOX.
Maximize Box Includes a maximize box. Window style ID is WS_MAXIMIZEBOX.
Clip Siblings Specifies whether the window covers other sibling windows. Window style ID is WS_CLIPSIBLINGS.
Clip Children Specifies whether the window covers other children windows. Window style ID is

WS_CLIPCHILDREN.
Vertical Scroll Includes a vertical scroll bar. Window style ID is WS_VSCROLL.
Horizontal Scroll Includes a horizontal scroll bar. Window style ID is WS_HSCROLL.
Popup Uses pop-up menu windows. Window style ID is WS_POPUPWINDOWSTYLE.
Minimize Minimizes application when window is open. Window style ID is WS_MINIMIZE.
Maximize Maximizes application when window is open. Window style ID is WS_MAXIMIZE.
Border Displays border around window. Window style ID is WS_BORDER.
Dlg Frame Displays window in a dialog frame. Window style ID is WS_DLGFRAME.
Visible Creates a visible window. Window style ID is WS_VISIBLE.
Thick Frame Displays window using a thick frame style. Window style ID is WS_THICKNESS.
Disabled Disables a window so that it does not accept user input. Window style ID is WS_DISABLED.

Advanced window Extended Styles properties
Tool Window Sets the window for use as a floating toolbar. Window style ID is WS_EX_TOOLWINDOW.
Client Edge Creates a 3D border with a sunken edge. Window style ID is WS_EX_CLIENTEDGE.
Static Edge Creates a 3D border for windows that does not accept input. Window style ID is WS_EX_STATICEDGE.
Transparent Makes the window transparent. Window style ID is WS_EX_TRANSPARENT.
Accept Files Lets the window accept drag-and-drop files. Window style ID is WS_EX_ACCEPTFILES.

USING ROBOHELP HTML 8 320

Last updated 3/1/2010

Generating Help and printed documents

Control Parent Lets users navigate among child windows using the Tab key. Window style ID is

WS_EX_CONTROLPARENT.
Context Help Adds a clickable question mark to the title bar that changes the cursor to a question mark pointer.

Clicking in a child window then displays a WM_HELP message. Window style ID is WS_EX_CONTEXTHELP
Right-to-Left Order Displays window text using the right-to-left reading order properties. Window style ID is
WS_EX_RTLREADING.
No Parent Notify Specifies that a child window does not send the WM_PARENTNOTIFY message to its parent
window when created or destroyed. Window style ID is WS_EX_NOPARENTNOTIFY.
Right -aligned Text Specifies generic right-aligned properties. Window style ID is WS_EX_RIGHT.
Left Scroll Bar Places a vertical scroll bar left of the client area. Window style ID is WS_EX_LEFTSCROLLBAR.
Top-most Window Places the window above all non-topmost windows, even when the window is deactivated.

Applications can use the SetWindowsPos member function to change this position. Window style ID is
WS_EX_TOPMOST.
To test this feature, generate and view the CHM file. When the HTML Help viewer opens, select a window. The viewer
remains the topmost window.

Adding HTML buttons
You can add extra buttons that link to intranet, websites, and HTML pages. You can add a home button and two jump
buttons to any URL. These buttons appear at the top of the HTML Help viewer.
Add a home button
1 In Windows Properties, click Buttons > Home.
2 Click Advanced Properties.
3 On the Destinations tab, in Home, enter the URL.
4 Click OK > OK.

Add a jump button
1 On the Windows Properties dialog box, select Button 1.
2 Click Advanced Properties.
3 On the Destinations tab, in the Button 1 label, enter label text for the icon displayed in the window (optional).
4 In Custom Button 1 URL, enter the link website address.
5 Click OK > OK.

Notes:
• Custom windows without a navigation pane do not support custom buttons. If you select options such as Back,
Forward, or Hide/Show, these buttons do not appear when you test Help topics.

• Website links to custom windows must include the tri-pane design (navigation pane).
• From the HTML Help viewer or window, Home buttons and URLs look like the following:
Home

USING ROBOHELP HTML 8 321

Last updated 3/1/2010

Generating Help and printed documents

Button 1
Button 2

Edit windows for JavaHelp and Oracle viewers
The JavaHelp viewer includes a customizable navigation pane and a content pane. To omit the navigation pane, clear
the TOC, Index, and Search settings. If you do not create a TOC or index, clear the corresponding settings.
1 Click Project.
2 Double-click the single-source layout.
3 Set options for the navigation pane and in-topic navigation bar.

Options for JavaHelp viewers
Desired Result

Actions

Specify the location for browse sequences and WebSearch.

Select Top Right, Bottom Left, or Bottom Right.

Specify the appearance of browse sequences or WebSearch
controls.

Select Button or Text.

Specify JavaHelp output type.

Uncompressed JavaHelp With Source Files to create HS and
individual output files.
Compressed JavaHelp to create .JAR and .HS files.
Compressed JavaHelp With Source Files to create .JAR, HS, and
individual output files.

Options for Oracle viewers
Desired result

Action

Add (or remove) the Contents tab from the navigation pane.

Select or clear TOC.

Add (or remove) the Index tab from the navigation pane.

Select or clear Index.

Add (or remove) the Search tab from the navigation pane.

Select or clear Search.

Enable WebSearch. (Select to provide access to WebSearch from
the Help viewer.)

Select WebSearc.h

Enable browse sequences (If you create browse sequences in the
project, select this feature so functionality is available in the
browser.)

Select Browse Sequences.

Specify the location for the in-topic navigation bar.

Select Top Right, Bottom Left, or Bottom Right as the location.

Specify the appearance of the in-topic navigation bar.

Select Button or Text as the style.

Assign a default window
If the project doesn’t include custom windows, the settings for New Window are used to display Help. If no windows
are in the project, Help is displayed using the default settings of the browser or viewer.
1 In the Single Source Layouts pod, expand the Single Source Layouts folder.

Last updated 3/1/2010

USING ROBOHELP HTML 8 322
Generating Help and printed documents

2 Double-click a layout that uses WebHelp Pro or HTML Help.
3 In the Default Window menu, select the custom window.

Remove a window
1 In the Project Set-up pod, expand the Windows folder.
2 Right-click a window. Select Delete.

Last updated 3/1/2010

Chapter 13: Advanced program features
ActiveX controls
About ActiveX controls
ActiveX controls are Microsoft Windows-based applications that you can plug into projects. They are small, precompiled, modular, and reusable. Web developers use ActiveX controls to extend the functionality of their HTML
pages. You can use ActiveX controls to extend the functionality of topics.
ActiveX controls work exclusively in browsers that support ActiveX technology. Microsoft Internet Explorer and the
HTML Help viewer support these controls. Netscape Navigator does not support ActiveX controls.
RoboHelp includes several ActiveX controls for HTML Help functionality, including link controls and HTML Help
controls. You can add other ActiveX controls. ActiveX controls can perform credit card transactions, spreadsheet
calculations and provide database communications.
Some ActiveX controls are included with projects. For example, the HHCTRL.OCX provided by Microsoft is a
required ActiveX control. It enables the table of contents, index, and full-text search.
Note: Copy ActiveX controls to and register them on user systems. ActiveX controls are not included in compiled CHM
files. For WebHelp and WebHelp Pro projects, Internet Explorer 4.0 or later supports ActiveX controls.

Add design-time controls
Note: This information applies to Microsoft HTML Help projects.
1 Insert the cursor in the topic where you want to place the control.
2 Select Insert > HTML > Advanced > Design-Time Control.
3 From the list of controls, select a control to insert into the project.
4 Click OK.

Types of HTML Help ActiveX controls
Calendar Control When users open a topic with a calendar control, a calendar appears in the text. Users can select

months and years to view and print.
Custom Buttons Users can download the latest information from a database or the latest version of the application
with custom buttons.
Banner When users open a topic that contains a banner, they are directed to the content. The banner lets you design
and test text, images, and icons to display at designated intervals in a topic.
Chart Lets users draw charts that they can view and print. They can change the chart properties by selecting options

and check boxes. They can also enter data to display in the chart or graph.
Calculations Lets users enter data, for example, in an online test. Users can obtain test results and view results (the

correct answers to each question).

323

Last updated 3/1/2010

USING ROBOHELP HTML 8 324
Advanced program features

You can insert any ActiveX control registered on the system into topics in projects. To add other ActiveX controls,
install and register the ActiveX control on the system before using it.

Add ActiveX controls
For the controls to work, distribute and register Custom ActiveX.ocx files on the user systems. (The RoboHelp license
allows you to distribute these controls.) By default, the controls are at C:\Program Files\Adobe\Adobe RoboHelp
[version]\Redist.
1 Insert the cursor in the topic where you want to place the control.
2 Select Insert > HTML > Advanced > ActiveX Control.
3 Select the ActiveX control to add and click OK.
4 Double-click the ActiveX control to edit its appearance and properties. HTML Help doesn't support all ActiveX

controls, and some controls don't have properties dialog boxes.

Customize ActiveX control properties
1 Double-click the ActiveX control in the topic to open the Properties dialog box, and view ActiveX control

properties including the following:
Code Source Provides an address (URL) for the latest copy of the ActiveX control (if it is not on the local system).
Data Source Provides an address (URL) that specifies where the ActiveX control searches to find any of its data

arguments.
ID Displays the identification of the ActiveX control (if it includes an ID).

2 Click the ActiveX Control tab, and click Add to specify the following properties. Then click OK.

• In Name, select the property type to add from the list of customizable properties for the ActiveX control.
• In Value, enter a value for the selected property.
3 Click the Margins tab, and specify the margins.
4 Click the Borders tab. Under Settings, select Box or Custom.

The Custom setting lets you add a border of a different size and color to each side of the ActiveX control. Specify
line style and border color and thickness, and preview the selections.
5 In the Size tab, specify the following Size properties:

• Enter Preferred Width and Height in pixels (px) (default) or percentages (%).
• Click Maintain Aspect Ratio to keep the height and width proportional.

Remove ActiveX control properties
1 In the Design Editor, double-click the ActiveX control to open the Properties dialog box.
2 Select the name or value of the property to delete.
3 Click the Delete button.

Customize the calendar control
1 Select Insert > HTML > Advanced > ActiveX Control.

USING ROBOHELP HTML 8 325

Last updated 3/1/2010

Advanced program features

2 Select Calendar Control [version]. The control appears in the Design editor, as shown in the following example:

3 Double-click it and change the available settings in the ActiveX Control tab.
4 To change the font color for weekday headings, click Add in the ActiveX Control tab.
5 Select Dayfontcolor, enter a color value, and click OK.
6 To view the calendar, click the View button

Applets
1 Select Insert > HTML > Advanced > Applet.
2 Add the following information:
Code The class files to use.
Code Base Path to the selected class files. If the applet is in the project folder, leave this field blank.
Name Name for the class files. Assign applet names for several applets to communicate with each other.
Alt Text alternate text used if the browser cannot display the applet.
Parameters Name and value of parameters defining variable elements of an applet, such as background color or font.
Add Opens a dialog box to enter the name and value of applet parameters. Examples of name and value are FontType
and FontType=Arial respectively.
Edit Opens a dialog box to edit parameters.
Delete Removes selected parameters.
Size Sets object width and height.
Margins Sets object margins.
Borders Sets a border around the object.

Notes:
• To use an applet in a topic, move the applet to the project folder before adding it.

• Most applets are class files. Work with the developer to obtain class files for the applet.
• To add class files to version control, manually add them to the Baggage Files folder.
• Applets work only in WebHelp, WebHelp Pro, FlashHelp, and FlashHelp Pro projects.

Last updated 3/1/2010

USING ROBOHELP HTML 8 326
Advanced program features

Forms
Workflow to create forms
Note: Forms created in the Design Editor must have a corresponding Common Gateway Interface (CGI) script on the
server.
1 Add the form and set form properties.
2 Add specific form elements.
3 Link to a script that acts on the data that the user enters. This step requires a CGI script written in a scripting or

programming language.
Top of Form
Bottom of Form

Add a form to a topic
1 Select a location where you want to insert a form.
2 Select Insert > HTML > Form > Form. A rectangular box is inserted to hold the form elements.

Set form properties
1 Right-click inside a form and select Form Properties.
2 Set the following options in the Form tab, and then set Size in pixels and Margin, Border, and Shading options.

Click OK.
Action In the Form Action box, enter the address to use to carry out the action of the form.
Method From the Method list, select the method to use for sending form data to the server.

• Post Sends the data through an HTTP post transaction
• Get Appends the arguments to the action URL, and opens it as if it is an anchor.
Name In the Name box, enter the form name.

If you want to include a background image or pattern, click the Browse button

to locate the image to use.

Form elements
Form elements are available from the Design Editor.
Text Field Lets users type text in a form. You can enter default text in the field to guide users, or you can leave the field

empty.
Multi-Line Text Field Lets users enter over one line of text in a form field.
Hidden Field Lets users add names and values for hidden fields.
Password Field Lets users apply password protection. When users type in the box, the viewer displays the password as
a series of asterisks (*) for confidentiality.
Radio Button Lets users select only one alternative from a group. Options are presented in a list, one of which is

selected by default. Clicking a new button clears the previously selected item.

Last updated 3/1/2010

USING ROBOHELP HTML 8 327
Advanced program features

Check Box Enables users to select any combination of alternatives. Check boxes can represent a group of non-

exclusive choices.
Button Lets users insert a plain button on the form, designate the caption, and perform customized actions defined by

the author.
Submit Button Lets users submit a completed form to a server.
Image Button Lets users insert a custom image on top of a button that performs an action when clicked.
Reset Button Lets users reset the form to its initial state.
Drop-Down Menu Lets users insert a drop-down menu in the form. Users can select one or more items, depending on

how you configure the drop-down menu.

Add and edit text fields
1 Select a location in the form to insert a text field or multi-line text field, and select Insert > HTML > Form > Text

Field. You can also select Insert > HTML > Form > Multi-Line Text Field.
2 For a text field, double-click the element to open the Text Field dialog box, specify the following properties, and

click OK.
Control Type Indicates the type of field.
Control Identifier Indicates the name to associate with the field. Not displayed on the form. The CGI program uses

it to identify the form element. To include a label next to the text field, type the text in the Design Editor.
Initial Text Displays text when the form opens. (If you select Password under Control Type, all characters in this

field appear as asterisks.)
Preferred Width Sets the width of the field.
Length Limit Sets the maximum number of characters that users can enter.

3 For multi-line text fields, double-click the element to open the Multi-Line Text Field dialog box, specify the

following properties, and click OK.
Control Identifier Name for the field. Not displayed on the form, but used to identify the form element. To include

a label next to the text field, enter text in the Design Editor.
Rows Number of rows in the field.
Columns Number of columns in the field.
Initial Text Text that appears when the form opens.

Add special fields
1 Place the cursor where you want to insert the field.
2 Select Insert > Fields and Variables.
3 Select the type of field from the Value list:
Date Day, month, year or combinations of the day, month, and year
Time Time of day (including AM or PM, if desired)
Title Topic title or other text
File Filename format
Variable Name and value

Last updated 3/1/2010

USING ROBOHELP HTML 8 328
Advanced program features

4 Select a format for the field from the Format list.
5 (Optional) Click New. A line with the default formatting is added at the end of the Format list. Type a name for the

new format in the Current Format box. The Example column displays how the field appears in the topic.
6 Click OK. The field is added to the topic.

Select Auto-Update This Field to update the field upon opening the topic. To view topic fields, from the View menu,
select Show, and choose Fields.

Add buttons to forms
1 Select a location to insert the button, select Insert > HTML > Form > Button, and double-click the placeholder

button that appears.
2 In Control Type, select the type of button:
Submit Button (Caption) Appears as a standard button and sends the form to the CGI script for processing.
Submit Button (Image) Appears as a custom image and sends the form to the CGI script for processing.
Reset Clears the form of any entries made by the user.
Plain Button Lets you customize the action the button performs.

3 In the Control Identifier box, type the button name.
4 In the Button Caption box, type the button caption.
5 If you select Submit Button (Image), specify a screen tip in the Screen Tip box.
6 If you select Submit Button (Image), specify a button in Button Image Path.
7 Click OK.

Add image buttons
1 Place the cursor inside the form to contain the button.
2 Select Insert > HTML > Form > Image Button, and click OK.
3 Enter an image name, select an image from the Images In Project Folder, or choose an image in the Gallery tab.
4 To specify screen tip, button caption, and size, double-click the image and select or enter the desired values.

Add check boxes
1 Select a location in the form to insert a check box.
2 Select Insert > HTML > Form > Check Box.
3

Double-click the check box, and specify the check box options:
Control Type Select Check Box.
Control Identifier Type the name to associate with the check box.
Control Value Enter the value for the control.
Select This Control Is Initially Selected Makes the option a default selection when the topic is opened.

4 Click OK.

Last updated 3/1/2010

USING ROBOHELP HTML 8 329
Advanced program features

Add radio buttons
1 Select a location in the form to insert a radio button.
2 Select Insert > HTML > Form > Radio Button.
3 Double-click the radio button and specify the properties:
Control Type Select Radio Button.
Control Identifier Type the name to associate with the radio button.
Control Value Enter the value for the option.
Select This Control Is Initially Selected Makes the option a default selection when the topic is opened.

4 Click OK.

Add drop-down menus
1 Select a location in the form for the menu.
2 Select Insert > HTML > Form > Drop-down Menu.
3 Double-click the drop-down menu.
4 Set options for the Drop-down Menu tab:
Control Identifier Type a name for the menu. This name is not displayed. It is used to sort data from the form. Use

the Design Editor to add a label next to the menu.
Rows Set how options display. For example, set to 1 to show one item at a time.
Allow Multiple Selections Lets users select multiple options.

5 Set options on the Options tab:
New Lets you specify a new label. Enter a name in the Label field, and a value in the Value field.
Selected Marks the option as a default.

6 Click OK.

Frames
About frames and framesets
Design framesets to customize navigation:
Frames Divide the viewer into separate regions for separate topics.
Framesets Allow some topics to change while topics in another frame remain stationary.

The frameset tells the viewer how to display the frames and which topics to display inside each frame. Topics that are
displayed in the frames are the frame source topics. You can use framesets as regular HTML topics.
You can have multiple frames in a frameset. Because screen space determines how many frames are practical, too many
frames give the viewer a cluttered look. Sometimes only parts of words appear inside each frame. Numerous frames
cause increased load times.

USING ROBOHELP HTML 8 330

Last updated 3/1/2010

Advanced program features

Notes:
• Printing is restricted to one frame at a time, although you can print the entire project from the viewer or browser.

• Target hypertext links to specific frames.
• Hypertext-linked external topics or URLs sometimes display incorrectly.
• Framesets are saved in the HTML Files (Topics) folder in the Project Manager. A square icon

indicates frameset

files.

More Help topics
“Create text links” on page 179

Create framesets
1 Select View > Pods > Project Manager.
2 Right-click Project Files and select New > Frameset, and click a template.
3 Enter a title. The title becomes the filename. Click Next.
4 Define the properties for each frame in the frameset:

• In Name, enter a name.
• From the All Folders pop-up menu, select the file or URL to attach to the frame. The selection appears in the
Initial File field.

• Design the frame, specifying values for the height, width, frame margins, and border color. Specify the following
options, and then click Finish:
No Resize Prevents users from resizing the frame.
Scrolling Controls the display of scroll bars inside the frame.

• Auto Displays a scroll bar if the entire topic content can be viewed only by scrolling.
• Yes Always displays scroll bars.
• No Does not display scroll bars.
New Topic Creates a topic and assigns it to a frame.

Change frames and framesets
1 Select View > Pods > Project Manager.
2 In the HTML Files (Topics) folder, double-click the frameset file.

Note: If the folder isn’t visible, click the Toggle Project Manager View button

3 Make changes.

Note: You cannot select a template for a defined frameset. To use a different template, create a frameset.

Change the size of a frame
Note: This procedure does not change the default settings.
1 Drag the cursor to the gray line between the two frames (frame divider).

USING ROBOHELP HTML 8 331

Last updated 3/1/2010

Advanced program features

2 After the cursor has changed, drag the frame divider left or right to make one frame larger and the other frame

smaller.

Remove framesets
If you accidentally delete a frameset, you can import it back into the project if it has not been removed from the hard disk.
1 Select View > Pods > Project Manager.
2 Expand the HTML Files (Topics) folder.
3 Select the frameset file to remove.
4 Click the Delete button

Deleting a frameset in the TOC, or one that is referenced by a hypertext link, moves the frameset to the Broken Links
folder. To add it back into the project, right-click and select Restore.

Link framesets to books or pages
1 Select View > Pods > Project Manager.
2 Double-click the Table Of Contents folder.
3 Right-click a table of contents in the folder, and click the New TOC Book

or New TOC Page tool

in the TOC

toolbar.
4 Enter a title to appear in the TOC, and select Book With Link.
5 Select a frameset from Existing Topics, and click OK.

Link to topics in frames
1 Ensure that the frameset is open in the browser or viewer.
2 Open a topic and select the text to link.
3 Right-click and select the Insert Hyperlink button
4 In Link To, click the triangle pop-up menu

to select a type of destination.

Or, select the topic or URL from Select Destination (File Or URL).
5 In the Display In Frame pop-up menu, select the destination. This option defines the frame for displaying content.
Page Default (None) Opens the topic in the same frame as the Help file window.
New window Opens the topic in a new browser window.
Same Frame Opens the topic in the same frame as the current topic.
Parent Frame Opens the topic in the link parent frame and hides the original topic.
Whole Page Opens the topic in the Help file window, replacing the original topic or frameset.

6 Click OK.

Last updated 3/1/2010

USING ROBOHELP HTML 8 332
Advanced program features

HTML Help controls
Reuse HTML Help controls
HTML Help controls are portable. You can copy the controls into topics and change them to suit their locations.
1 In the Design Editor, open the topic that contains the control to reuse.
2 Right-click the control and select Copy.
3 Open the topic that needs the control.
4 Right-click the place for the control and select Paste.
5 To change the control, double-click it.

Add WinHelp topic controls
Note: You cannot call topics with the @ character in the title from a Related Topics control in compiled HTML Help files.
1 In the Design Editor, click a location for the control.
2 Select Insert > HTML Help Controls > WinHelp Topic.
3 Set the button options.
Text Inserts a standard gray button with black text. Edit the text for the button in the text field.
Image Inserts a BMP or an ICO file. Click the folder button to browse to the file. Select the file and copy it into the

project.
Hidden Inserts a control that is not visible in the topic. This option does not insert the control as an object in the

topic.
4 Click Next. Select the WinHelp file and topic.
Help Specifies the Help file. Click Yes to copy the HLP file into the project folder. If the WinHelp system includes

a table of contents file, click Yes to copy it into the project folder.
Display As Popup Displays the WinHelp topic in a pop-up menu.
Window Specifies the type of window.
Specify Topic Defines topic by topic title, topic ID, or map number.

5 Click Next to set the font options for the button label.
6 Click Finish. Compile the Help system to test.

Distribute the HTML Help system with the HLP and CNT files.

More Help topics
“Add design-time controls” on page 323

Add index controls
Note: Applies to Microsoft HTML Help projects only.
The tri-pane design includes an Index tab, where users can access keywords.

Last updated 3/1/2010

USING ROBOHELP HTML 8 333
Advanced program features

If the project does not support a tri-pane design, you can add an index control to a topic to make the index file
available. The index appears when users open the topic with the index control.
If the topic is in a subfolder, copy the index file (.HHK) to the subfolder before you add the control.
1 In the Design Editor, click the place in the topic to add the index.
2 Select Insert > HTML Help Controls > Index.
3 To test the index control, compile the project. The index control displays the same index as in the final output.

You can use other index files (HHK) in the project. Copy the HHK file and associated files (topics, images,
multimedia) to select the HHK file with the index control.

Add table of contents controls
Note: Applies to Microsoft HTML Help projects only.
When users open a topic, the TOC appears.
If a topic is in a subfolder, copy the contents of the file into the subfolder before adding the control.
1 In the Design Editor, click the place in the topic to add the TOC.
2 Select Insert > HTML Help Controls > Table Of Contents.
3 To test the control, first generate the project. The Table Of Contents control displays the same table of contents as

in the final output.
You can link other contents files in the project. Copy the HHC file into the project to select the HHC file with the TOC
control.

Add splash screens
Note: Applies to Microsoft HTML Help projects only.
You also can include splash screens when topics open. You can use Windows bitmaps (BMP) and GIF images.
1 In the Design Editor, open the topic to display the splash screen when opened.
2 Select Insert > HTML Help Controls > Splash Screen.
3 From Image File For Splash, click Browse and navigate to the image to use in the project.
4 Highlight the image file and click Open.
5 In Duration Of Splash Display (Seconds), set the amount of time that the image remains on the screen.
6 Click Finish. To test the splash screen, preview the topic.

You see a Splash object that identifies its location in the file. This object is not displayed in the viewer. When the topic
is opened, only the image is displayed.

Add shortcuts
Note: Applies to Microsoft HTML Help projects only.
1 In the Design Editor, click the place in the topic to add the shortcut control.
2 Select Insert > HTML Help Controls > Shortcut.
3 Set the button options.
Text Inserts a gray button that performs the action.

Last updated 3/1/2010

USING ROBOHELP HTML 8 334
Advanced program features

Image Inserts a custom image (BMP or ICO) that performs the action.
Hidden Inserts a control that is not visible in the topic.

4 Click Next to set up shortcut functionality.
Program To Run Specifies the program to run from the control. Navigate to the drive/folder where the EXE file is
located and double-click it.
Program Parameters Defines command-line arguments to apply when the program runs, if needed.
Window Class Of Program Window Specifies the window class.
Topic To Display Specifies a topic to display if the program cannot be located.

5 Click Next to set the font options for the button label.
6 Click Finish.

Add HHCTRL version controls
An HHCTRL version control shows the version number of the Microsoft HTML Help on a user system.
1 In the Design Editor, click the place in the topic to add the control.
2 Select Insert > HTML Help Controls > HHCTRL Version.
3 Select button options.
Text Inserts a gray button with black text that performs the action. Use the existing label or edit the text.
Image Inserts a custom image (BMP or ICO) as the button.
Hidden Inserts a control that is not visible in the topic. See the developer for a script that closes the window. You

can also add scripts to topics.
4 Click Next to set the font options for the button label.
5 Click Finish.

Preview the topic to test the HHCTRL version control.

Add close window controls
1 In the Design Editor, click where you want to add the close window control in the topic.
2 Select Insert > HTML Help Controls > Close Window.
3 Set up the button options for the control.
Text Inserts a gray button that performs the action when selected. Edit the text to appear on the button.
Image Inserts an image that performs the action when selected.
Hidden Inserts a control that is not visible in the topic. See the developer for a script that closes the window. You

can add scripts to topics.
4 If you are adding a standard button, click Next and set up the font options for the button label. You can assign a

different font, style, and size.
5 Click Finish.

To test the close window control, compile the Microsoft HTML Help project.

Last updated 3/1/2010

USING ROBOHELP HTML 8 335
Advanced program features

Change HTML Help controls
Note: Applies to Microsoft HTML Help projects only.
1 In the Design Editor, open the topic with the control.
2 Double-click the control.

Right-click a control and select Design-Time Control Properties to change properties.

Remove HTML Help controls
1 In the Design Editor, open the topic that contains the control to remove.
2 Select the control.
3 Click Delete.

Click Undo to restore a control that you removed by mistake.

Information types (for HTML Help)
Information types are designed for HTML Help (CHM Help) only.

About information types (HTML Help)
Information types control which books and pages a user can access from the Contents tab in the HTML Help viewer.
They are an optional feature that you can use in Microsoft HTML Help projects only.
You first define categories and add information types to them. Then assign topics (pages or books) to the information
types. From the Contents tab in the HTML Help viewer, users can customize books and pages that appear in the table
of contents. If you do not assign an information type to a topic, the topic appears in the HTML Help viewer regarless
of user customization.
A category is a way to group information types, such as job description or skill level. You can create up to 10 categories
and 32 information types.
Information types fall into two categories:
Inclusive All information types from a category are available to users.
Exclusive Restricts users so they can select only one information type from a category. For example, you can assign

Exclusive classifications by skill level, so that users can access only the Help topics that pertain to their skill level.
With the current version of Microsoft HTML Help, it is not possible to filter Index and Search tabs to support
information types. Users cannot access a topic from the HTML Help index that is not in the information types that
they select.
For a detailed explanation of information types, see Strategies for Using Information Types in HTML Help by Rob
Houser.

Define categories and information types (HTML Help)
1 Select Edit > Information Types.

Last updated 3/1/2010

USING ROBOHELP HTML 8 336
Advanced program features

2 In the Category field, enter a name.
3 Classify the category:
Inclusive Users can select any combination of information types in a category.
Exclusive Users can only select one information type in a category.
Hidden Users do not see these topics in the TOC. They cannot customize information types to filter them. If you

are assigning topics to information types for context-sensitive Help, select this option.
4 Click Add Category. Repeat steps 2 through 4 to add more categories.
5 Select a category to add information types.
6 In Information Type, enter an information type.
7 Click Add Info Type. Repeat steps 6 and 7 to add more information types in the same category.
8 Click OK.

Assign information types (HTML Help)
After creating information types, assign them to books or pages in a TOC.
Note: Make sure that Microsoft HTML Help is set as the primary layout.
1 In the Project Manager pod, double-click a table of contents in the Table Of Contents folder.
2 In the TOC pod, right-click the book or page, and select Properties.
3 Click the Advanced tab.
4 Select Use Information Types.
5 Click Add and select a topic to associate with the selected book or page.
6 Select an entry in Information Types and click Types.
7 Select an information type.

Access information types from the HTML Help viewer
When users open Help systems, the system prompts them to select information types. All topics not assigned to
information types are available from the index.
1 Click the Contents tab.
2 Right-click inside Contents and select Customize.
3 Select Custom.
4 Click Next. The list that appears depends on the Exclusive or Inclusive classification of the information types.
5 Select any combination of information types, and click Next.
6 Click Finish. The Contents tab is updated to display only pages that correspond to the information types selected.

If the Help system displays in the Internet Explorer browser, you can use information types as long as the first topic
includes the TOC ActiveX control.

Last updated 3/1/2010

USING ROBOHELP HTML 8 337
Advanced program features

Edit information types (HTML Help)
Change categories for information types (HTML Help)
1 Select Edit > Information Types.
2 From the list of categories, select one.
3 Click in the Category box and edit the text.
4 To change its classification from Inclusive to Exclusive or Hidden, click the option. Then click the Change button.

Remove categories from information types (HTML Help)
When you remove a category, you also remove its associated information types.
1 Select Edit > Information Types.
2 From the list of categories, select one to remove.
3 Click Delete Category. The category along with all its information types are deleted.

Remove information types (HTML Help)
Remove information types from books and pages (HTML Help)
1 In the Project Manager pod, double-click a table of contents in the Table Of Contents folder.
2 In the TOC pod, right-click the book or page, and select Properties.
3 Click the Advanced tab.
4 From Information Types, choose the topic folder.
5 Click Remove to remove assignments.

Remove information types from categories (HTML Help)
1 Select Edit > Information Types.
2 From the list of categories, select the one that includes the information type to remove.
3 Select the information type.
4 Click Delete Info Type.

Scripts
About scripts
Scripts are coded instructions that tell the HTML Help viewer or browser how to react to events. Scripts add power
and more functionality to HTML Help systems, intranets, and websites.
Two common supported scripting languages are VBScript and JavaScript. The scripting used is the same kind used by
web pages. Scripts are uncompiled. You can view them in the RoboHelp HTML Editor. Because they are uncompiled,
they do not require a dynamic-link library (DLL).
Because HTML Help does not support macros, use scripts to provide the same functionality that macros provide for
WinHelp systems. Application developers can provide scripts for you to plug right into the topics.

USING ROBOHELP HTML 8 338

Last updated 3/1/2010

Advanced program features

Note: Add support files used in scripts (such as image files) to the Baggage Files folder to include in the project.

Add a script to an HTML topic
1 In the Design Editor, click the place in the topic to add the script.
2 Select Insert > HTML > Advanced > Script.
3 In the Source tab, enter the scripting code.

• If you first copy the script to the Clipboard, you can click inside the Source tab and paste the data into the box.
You can also type the script directly into the box.

• Enclose the script within comment tags  for compatibility with all browsers.
4 Select the Tag tab, select a Name or Value tag to edit, and select Edit Name or Edit Value.
5 Change the tag, as needed, and click OK. The value can be VBScript or JavaScript.

The icon

indicates where the script is inserted in the topic. To edit the script, double-click the icon.

6 Test the HTML file after you generate output.

About ExtendScript Toolkit support
Create your own scripts to automate repetitive tasks and time-consuming workflows. For example, you can write a
script that counts the images used in a RoboHelp project.
RoboHelp provides a set of sample scripts that you can use or customize. You can access these sample scripts from
Tool > Scripts:
EclipseHelp Use this script to convert WebHelp output to EclipseHelp output. For more information about generating
EclipseHelp output, see this article.
Link Converter Use this script to convert an anchor link href target across all the files in a RoboHelp project. For

example, define a link to convert www.adobe.com to www.adobe.com/support/ across all the Help files in a project.
See the script file for more information.
SaveAsProjecTemplate Use this script to save a RoboHelp project as a template for creating similar RoboHelp

projects.
UDV Converter with UI Use this script to convert a keyword into a user-defined variable and change its value across all
files in a project. Enter a keyword, a user-defined variable name, and its value.
UDV Converter Use this script to convert a keyword into a user-defined variable and change its value across all the files
in a project. See the script for more details.
Word Count Use this script to get a word count for an opened RoboHelp project. It provides a word count by topic
and by project. To run the Word Count script, right-click the script and select Run. The word count summary appears
in the Output View pod.

Creating scripts
You can write scripts and debug them using the Script Explorer of the ExtendScript Toolkit.
John Daigle provides a step-by-step introduction in Automating tasks with built-in scripting on the Adobe RoboHelp
8 video tutorials page.

USING ROBOHELP HTML 8 339

Last updated 3/1/2010

Advanced program features

For information about the methods covered in the Data Object Model, see Adobe RoboHelp 8 Scripting Guide.

Manage script folders
Create a script folder Create a folder for storing specific scripts. For example, you can store scripts that record data in

one folder and scripts that display output in another folder.
Note: The sample scripts are stored in the \RoboHTML\presets\scripts folder of your RoboHelp 8 installation.
Drag folders You can drag folders into and out of the Script Explorer.
Import and export You can export and import folders in different projects and locations. To import or export a folder,

it must contain at least one script file.

Manage script files
Create a script file Create a script file and specify a name.
Edit Right-click a script in the Script Explorer or Windows Explorer to edit it using ExtendScript Toolkit. Double-click

a script file to edit it using a third-party editor.
To add a third-party editor, go to Tools > Options, click the Associations tab, and add the .jsx filename extension for
the third-party editor.
Import and export Export a script file to or import it from a computer or a network.
Drag script files Drag a script file into different folders on a computer or a network.

Run scripts
Using the command line You can run scripts by entering a command in the following format:
Robohtml.exe -x [scriptfilenames]

You can specify multiple script filenames, separated by a space, to run one script after another. If the filename path
contains a space, enclose the filename path in single or double quotation marks.
Using the Tools menu You can use the RoboHelp scripting samples available at Tools > Scripts or create new scripts
to run them; see the ExtendScript Toolkit documentation.
Using Windows Explorer Double-click a script to open it in the ExtendScript Toolkit and run it.
Using ExtendScript Toolkit Start RoboHelp directly from the ExtendScript Toolkit and run your scripts. To start

RoboHelp, select Adobe RoboHelp [version] from the ExtendScript Toolkit pop-up menu. Click the Click To Connect
to run RoboHelp. The icon is green to indicate that RoboHelp HTML is running.
To Target Application
Note: If you don’t select Adobe RoboHelp in the ExtendScript Toolkit, and you try running a script, an error occurs.

Twisties
Use twisties to enhance glossary terms, drop-down text, and expanding text with images for open and close. Users will
see different images when they open or close glossary, drop-down, or expanding text.

Add or change images in a hotspot
1 Select Drop-down hotspot style in the Styles dialog box.

USING ROBOHELP HTML 8 340

Last updated 3/1/2010

Advanced program features

2 Expand Character styles to view the Drop-down hotspot style.
3 Click the Select Twisties Images button

4 Select an image to display closing drop-down text and one image to open a drop-down hotspot.
5 Select an option to place the images either at the Start Of Text or End Of Text. Similarly, you can change images for

expanding text.

Add or change images of glossary terms
1 Select a glossary term style in the Styles dialog box.
2 Click the Select Twisties Images button

3 Select an image to display closing drop-down text and another image to open a drop-down hotspot. Select different

images to differentiate between opening and closing a hotspot.
4 Select an option to place the images either at the Start Of Text or End Of Text. Similarly, you can change images for

expanding text.

Removing Twisties images
❖ To remove images from glossary terms or drop-down hotspots, click the Clear button in the Select Twisties Images

dialog box.

Last updated 3/1/2010

Chapter 14: Integrating with Adobe
Technical Communication Suite
Importing FrameMaker documents into RoboHelp
Authoring and publishing workflow using FrameMaker and RoboHelp
FrameMaker and RoboHelp together provide features for end-to-end authoring and publication workflow. With
major enhancements in the integration between these two tools, you can move content from one tool to the other. You
can also publish to various output formats such as PDF, online Help, and Help based on Adobe AIR. If your authoring
and publishing environment includes these two tools, you have multiple options of incorporating their strengths into
your workflow.
You can map FrameMaker formats directly to RoboHelp styles in a standard CSS that ensures consistency in
appearance and behavior across the entire project. In addition, within FrameMaker, you can use markers to denote
context-sensitive topics, which you can directly reuse in RoboHelp to create a context-sensitive Help system.
FrameMaker and RoboHelp as independent products If you have FrameMaker and RoboHelp as independent
products, you can retain your authoring workflow. In this workflow, you author content in FrameMaker for print and
PDF output. Then you use RoboHelp to generate richly formatted online Help. Both FrameMaker and RoboHelp
provide enhanced features for importing FrameMaker content into RoboHelp projects. You can also use them
together to create online Help formats such as WebHelp and Help based on Adobe AIR.
Adobe Technical Communication Suite Adobe® Technical Communications Suite provides technical communicators

a streamlined workflow to author content once and deliver in multiple formats. You can author in FrameMaker and
publish richly formatted PDF for print and online viewing. Technical Communication Suite provides more features
than the component applications that make the suite. You can integrate FrameMaker and RoboHelp authoring and
publishing and dynamically link FrameMaker and RoboHelp content.
Adobe Technical Communication Suite includes Adobe Captivate and Adobe Photoshop—tools that you can use to
include rich multimedia capabilities in your output formats. In addition, you can use Adobe Acrobat to set up shared
reviews and consolidate review comments and edits. You can later import these comments and edits into your
FrameMaker documents.
To ensure best results from your workflow, you can optimize the authoring and publishing practices.

341

USING ROBOHELP HTML 8 342

Last updated 3/1/2010

Integrating with Adobe Technical Communication Suite

Similarly, in RoboHelp, re-create watermark text or images that you used in the printed documentation. Use the
master page feature in RoboHelp to make these corrections.
Navigation In print, cross-references specify page numbers which are irrelevant in Help. You can map cross-reference

formats in FrameMaker to a format without the chapter and page number. Converting to online Help removes chapter
and section titles in headers and footers. You can enhance navigability by using breadcrumbs, back and next buttons,
and a defined browse sequence instead.
Redundant content To provide context in different sections of a printed document, writers generally add redundant
information such as brief summaries of concepts covered previously. Because online Help is a random-access,
nonlinear medium, it requires less redundant content. Use cross-references and conditional text options to minimize
redundant content in your outputs.
Chapter versus topic In printed documentation, chapters signal stand-alone logical units, which readers use to grasp

the scope of content. Online Help segregates content at topic level, accessed one topic at a time. You can group the
content into chapter-like folders that expand when a user navigates the table of contents. Even so, only one topic
appears at a time. In this case, try to provide comprehensive information without adding redundancy by grouping
related topics together.
Context sensitivity Online Help formats allow you to link specific topics to related content within the application

workflow. Although you can assign map IDs to topics in RoboHelp, you can also assign context-sensitive Help markers
in FrameMaker documents. RoboHelp reads these markers and assigns the map IDs to the generated topics. Ensure
that the topics created in FrameMaker contain sufficient information.
For example, a short procedure as a stand-alone topic does not provide conceptual context for the reader. To avoid
creating topics with incomplete information, assign context-sensitive Help markers to topics at a higher level. In this
way, the generated Help topic contains the concept, procedure, and any relevant graphics.

Prepare FrameMaker documents for conversion to Help
If the FrameMaker document that you are importing is an unstructured FrameMaker book, you can define a single
FrameMaker template for the conversion. You can then specify this template as the project template that overrides the
formats of individual documents at the RoboHelp project level. You can also reuse the conversion settings across other
projects by exporting the conversion settings.
Carefully examine the FrameMaker templates before importing the documents into RoboHelp, such as when you use
a general-purpose FrameMaker template. If this template contains formats that aren’t used in the book, omit those
formats in the template you use for the conversion.
1 Create a FrameMaker template that contains the formats you need in Help. Alternatively, customize the

FrameMaker template. You don’t have to apply the template manually. You can set RoboHelp to apply a selected
template to FrameMaker files before they are linked or imported to RoboHelp.
In Structured FrameMaker, the element definition document (EDD) or the DTD used in the structured
FrameMaker template automatically controls formatting. Because structured FrameMaker enforces a valid
structure and format, structured documents do not contain format overrides.
2 Create the required DHTML effects such as expanding text and drop-down text using the RoboHelp menus in

FrameMaker.
3 Apply context-sensitive Help markers to the required topics.
4 Enclose graphics, callouts, and graphic or text frames you created with FrameMaker graphic tools in anchored

frames. RoboHelp imports only those FrameMaker graphics that are enclosed in anchored frames. By default,
graphics and multimedia files imported into a FrameMaker document are placed in anchored frames. If your
FrameMaker document contains graphics in graphic frames, place them in anchored frames before linking or
importing the FrameMaker files into RoboHelp.

USING ROBOHELP HTML 8 343

Last updated 3/1/2010

Integrating with Adobe Technical Communication Suite

5 To maintain the original quality of images, insert them in FrameMaker documents by reference. RoboHelp copies

the referenced images directly from the source if the complete image is visible inside the anchored frame. Similarly,
if the images are large, insert them in the source document by reference.
6 Fix any issues in the document such as unresolved cross-references, missing fonts, and irregular numbering issues.
7 Set up alternative text or captions for the images and graphics to create accessible online content.
8 Apply conditional text settings in FrameMaker documents.
9 Edit the FrameMaker TOC reference pages to have indented hierarchical headings with different styles.

More Help topics
“Pagination for Help” on page 354
“Create alternative text for images” on page 362

Linking options for FrameMaker documents
When you link a FrameMaker document to a RoboHelp project, you have two options:
Create A Reference You create a reference to an external FrameMaker document. In this case, the source document is

not copied into the RoboHelp project folder. It remains outside the project. You can edit and update the source
document independently. Later, in RoboHelp, you can update the topics generated from the linked document.
Use the linking by reference option to bring in content that is shared across multiple projects. Because only a single
copy of the document exists, any change in the source document is reflected in all projects to which this document is
linked.
Create A Copy And Link You create a copy of the source document and link to the RoboHelp project. In this case, a

copy of the source document is copied into the RoboHelp project and is visible in the Project Manager pod. You can
edit and update the copy without affecting the source document. You update the topics generated from the copied
document whenever you edit the document.
Use the Create A Copy And Link option to restrict access to the source document. This option allows editing only in
the copy available in the RoboHelp project. For example, if you want to bring in content from a static FrameMaker
document, link the document by copying it to the RoboHelp project.
Note: FrameMaker books are always linked by reference, irrespective of the linking option you choose.

Trade-offs between linking and importing
• Link FrameMaker and Word documents when your entire authoring is in one or both of these tools. You can make
full use of RoboHelp’s advanced integration features, such as converting TOC, index, and glossaries, and creating
context-sensitive Help. Whenever the source content changes, you can quickly update the topics generated in
RoboHelp from the linked documents. In such cases, RoboHelp converts your FrameMaker or Word documents
to multiple Help outputs with a few clicks, with little, or no native authoring in RoboHelp.

• Import FrameMaker and Word documents when you have multiple independent documents and carefully use
RoboHelp’s integration features. In addition, ensure that the documents you import are stable and don’t require
updates independently until you have finished publishing the online Help.

• Avoid editing the generated topics in RoboHelp so that you don’t lose your edits if you have to update the generated
topics or overwrite them. Topics generated from linked documents can be preserved with their edits, but topics
generated from imported documents are overwritten.

USING ROBOHELP HTML 8 344

Last updated 3/1/2010

Integrating with Adobe Technical Communication Suite

• If you are making minimal updates to a large RoboHelp project, it is best not to link or import documents into
RoboHelp. Doing so can disturb the natively created TOC, index, and glossary, pagination, and context-sensitive
Help settings.

Linking and importing FrameMaker documents
The RoboHelp workflow for linking or importing FrameMaker documents allows you to do the following:

• Create a RoboHelp project by importing a FrameMaker book. You can import BOOK or BK files.
• Link or import FrameMaker books into a RoboHelp project. You can link BOOK files. FrameMaker book files
created in a version earlier than FrameMaker 6 (BK) can only be imported into RoboHelp; they cannot be linked.

• Link or import FrameMaker documents into a RoboHelp project. You can import FM files or MIF files that are
authored in FrameMaker. XML files that are part of a FrameMaker book can be imported.
When you link a FrameMaker book to a RoboHelp project, HTML files are not created until you define the project
settings and generate the Help topics. At the same time, you can see the added files in their hierarchical order.
Importing the FrameMaker documents and editing the HTML files generated from them in RoboHelp does not affect
the source FrameMaker documents.
Before you import FrameMaker documents, check them in FrameMaker for errors such as unresolved cross-references
and format overrides.
Create a RoboHelp project by linking or importing FrameMaker books or documents
You can create a RoboHelp project by importing FrameMaker books or documents. To import these files, you must
have FrameMaker 8 or later installed on your computer.
1 On the RoboHelp Starter page, click More under Import, or select File > New > Project.
2 On the Import tab of the New Project dialog box, select FrameMaker Document and click OK.
3 Select the FrameMaker book or document (BOOK, BK, FM, MIF, FRM) from the Files Of Type pop-up menu.

Then browse to select the FrameMaker book, and click Open.
Link or import a FrameMaker book into a new RoboHelp project
1 Create a project in RoboHelp.
2 Select File > Link > FrameMaker Document, or File > Import > FrameMaker Document.
3 Select FrameMaker BOOK (book files) from the Files Of Type pop-up menu.
4 Browse to select the FrameMaker book file and click Open.

If you are importing a FrameMaker document, you can select the components that you want to import from the
Import wizard that appears. You can select the TOC, index, and glossary, and specify the conversion settings.
Link or import FrameMaker documents into an existing RoboHelp project
1 Select File > Link > FrameMaker Document or select File > Import > FrameMaker Document.
2 Select the FrameMaker document type that you want to link or import. You can link FM and MIF documents and

import FRM from the Files Of Type pop-up menu. Select the documents and click Open.
Note: FrameMaker documents created in versions earlier than 6.0 (FRM files) can be imported but not linked.

USING ROBOHELP HTML 8 345

Last updated 3/1/2010

Integrating with Adobe Technical Communication Suite

Generate HTML topics from linked FrameMaker documents
Linking FrameMaker documents does not automatically create the topics. You generate the topics after you set the
project and conversion settings.
❖ Do one of the following:

• Right-click the linked FrameMaker document from the Project Manager pod and then select Update >
Generate.

• Select File > Update > Generate.
However, if you are importing a FrameMaker document, topics are generated immediately according to the
conversion settings you specify. In addition, you can select the components that you want to import from the Import
wizard that appears. You can select the TOC, index, and glossary, and specify the conversion settings.

Convert a FrameMaker TOC
When you import a FrameMaker book to a RoboHelp project, you can also import the table of contents (TOC). Import
the TOC into the RoboHelp project to retain the navigation structure you defined in the FrameMaker book.
1 Select File > Import > FrameMaker Document.
2 In the Content Settings dialog box, select Convert FrameMaker Table Of Contents, and browse to select the

• To make a heading a main book, include indented heading levels beneath that heading, or use smaller fonts or no
bold for the subsumed headings.

• To make a heading a sub-book, place the heading under a main heading. Then include indented heading levels
beneath the sub-book heading, or use smaller fonts or no bold for the subsumed headings.

• To make a heading a page, don’t include any heading levels beneath that heading. Indent the page heading, or use
smaller fonts or no bold.

Differences between FrameMaker and RoboHelp TOCs
You can either import the FrameMaker TOC or automatically create a TOC in RoboHelp from generated topics.

• Autocreating a TOC for a FrameMaker 9 book can create multiple layers of content because of the folder structure
in a FrameMaker 9 book.

• In RoboHelp, you can place a TOC placeholder in another TOC, thus allowing you to create nested TOCs.

USING ROBOHELP HTML 8 346

Last updated 3/1/2010

Integrating with Adobe Technical Communication Suite

More Help topics
“Hierarchical structure in a FrameMaker 9 book” on page 353

Import glossary definitions
RoboHelp creates a glossary based on glossary markers in the document you are importing. The text inside the glossary
marker is the glossary term, and the paragraph text that contains the marker is the definition.
1 Select File > Import > FrameMaker Document and select the FrameMaker book or document.
2 Select Convert Glossary in the Content Settings dialog box, and select one of the following options:
Add To Existing Glossary Add the FrameMaker glossary to the RoboHelp glossary of the project. You can select the

glossary from the list.
Create New Associated Glossary Enter a name for a new associated glossary that is associated with the existing
glossary in the RoboHelp project.

Synchronizing linked FrameMaker documents with RoboHelp projects
You can update a linked FrameMaker document if the source FrameMaker document has changed or conversion
settings in the RoboHelp project have changed.
Note: Linking eliminates the need to reimport the FrameMaker document and overwrite the topics when you update.
Update the topics generated from linked FrameMaker documents in the following scenarios:

• Source FrameMaker documents changed after you added or linked them to the RoboHelp project.
• You changed the pagination settings in the RoboHelp project.
• You changed the style mapping in the RoboHelp project.
• You updated the CSS in the RoboHelp project.
• You edited the topics generated from the linked documents.
Icons of the project files in the Project Manager pod indicate whether the documents are in sync with the RoboHelp
topics.
On the other hand, if the documents were imported into the project, the Project Manager pod does not indicate the
synchronization status. If either the FrameMaker documents or the conversion settings change, reimport the
FrameMaker documents and overwrite the RoboHelp topics already generated. When you update the documents,
RoboHelp updates the converted HTML topics, TOC, index, and glossary.

USING ROBOHELP HTML 8 347

Last updated 3/1/2010

Integrating with Adobe Technical Communication Suite

FrameMaker book synchronization status indicators
Icon

Description
FrameMaker book missing. The source FrameMaker book that you have linked to the RoboHelp project is either moved to
another folder or deleted. Locate the source book and link them to the new location.
FrameMaker book out of sync because of changes in the source document. Update the RoboHelp topics.
Topics generated from the linked FrameMaker book are out of sync because of changes in the RoboHelp Project Import
Settings. Update the RoboHelp topics generated from the FrameMaker book.
Topics generated are in sync with the linked FrameMaker book.

FrameMaker document synchronization status indicators
Icon

Description
Linked FrameMaker document missing. The source FrameMaker book that you have linked to the RoboHelp project is
either moved to another folder or deleted. Locate the source book and link them to the new location.
FrameMaker document out of sync because of changes in the source document. Update the RoboHelp topics.
Topics generated from the linked FrameMaker document are out of sync because of changes in the RoboHelp Project
Import Settings. Update the RoboHelp topics generated from the FrameMaker document.
Topics generated are in sync with the linked FrameMaker document.

Update FrameMaker documents
❖ From the Project Manager pod, right-click a FrameMaker book and select Update, then choose one of the

following:
Generate Generates HTML topics from the linked FrameMaker document for the first time. After generating the

topics, the option changes to Update.
Update Updates topics generated from the selected book or document alone.
Update All Updates all topics generated from all linked FrameMaker documents.
Force Update Overwrites the current set of topics generated from the selected FrameMaker book or document. Use

this option to force update the topics generated from the linked FrameMaker book or document.
Force Update All Updates all linked documents and overwrites all generated topics.

Alternatively, you can select the linked FrameMaker book or document and update the RoboHelp topics generated
from the linked FrameMaker book or document.

Preserve changes to a topic during an update
Normally, when you update a linked document, all topics generated from it are updated, overwriting any other
changes you made in the generated topics. However, you can selectively preserve changes in generated topics and
retain your edits.
1 Right-click the linked document in the Project Manager pod and select Properties.
2 In the FrameMaker Document Settings dialog box, select the File Update Settings tab.
3 On the left column, select the edited files you want to preserve changes during update and click OK.

Any files that you had selected earlier for preserving changes are displayed in the right column.

USING ROBOHELP HTML 8 348

Last updated 3/1/2010

Integrating with Adobe Technical Communication Suite

Set alert when editing generated topics
You can set RoboHelp to alert you when you edit topics generated from linked documents. When you save the changes
to such topics, RoboHelp alerts you that the changes would be lost when the linked documents are updated.
1 Select Tools > Options.
2 In the General tab, select Show Alert On Modification Of Auto Generated Topics From Linked Documents and

Delete a generated topic
When you delete a generated topic, you have two options. You can regenerate the deleted topic when you update the
linked FrameMaker document or completely remove the deleted topic from your project. By default, RoboHelp
regenerates the deleted topic when you update the FrameMaker document.
1 In the Project Manager pod, expand the linked FrameMaker document to display the topics generated from it.
2 Right-click the topic that you want to delete, and select Delete.
3 Do one of the following:

• Click OK to delete the topic from the project permanently. The deleted topic is not regenerated when you update
the FrameMaker document.

• Select Generate This File On Next Update and click OK to delete the topic. When you update the FrameMaker
document, the deleted topic is generated again.

Regenerate a deleted topic
If you delete a topic generated from a linked FrameMaker document, the topic is removed from the project. However,
you can regenerate topics deleted from a linked document.
1 Right-click the linked FrameMaker document in the Project Manager pod and select Properties.
2 In the FrameMaker Document Settings dialog box, select File Update Settings tab.
3 On the right column, select the deleted files that you want to retrieve and click OK.
4 Update the FrameMaker document.

Edit a linked FrameMaker document
You can edit linked FrameMaker documents directly in FrameMaker.
1 Right-click a document and select Edit.
2 Edit the FrameMaker document.
3 Click Save. The modified FrameMaker document now appears in the Project Manager pod with a different icon.

This icon indicates that the source content is now out of sync with the topics generated from the linked
FrameMaker document.
Note: Force an update of the document after you edit the source in FrameMaker.

USING ROBOHELP HTML 8 349

Last updated 3/1/2010

Integrating with Adobe Technical Communication Suite

Delete a linked document
You can directly delete documents linked by copy from the Project Files folder, and you can delete the references of
the documents linked by reference.
❖ Right-click a document and select Delete.

• Do not rename files generated after linking a document.
• You cannot drag the generated topics outside the source document folder to some other location in the Project
Manager pod.

Restore a link to a missing or renamed document
If any of the linked documents are moved or renamed, RoboHelp displays a missing link icon for the linked document
in the Project Manager pod. You can restore the link to a moved or renamed file and have all the topics already
generated from the document retained in the project.
1 In the Project Manager pod, right-click the document that has the missing link icon.
2 Select Restore Link To FrameMaker File, and browse to select the new location of the missing file.

TOC

Converted, if selected. See “Convert a FrameMaker TOC” on page 345.

Text insets

Text insets in the FrameMaker documents are considered part of the FrameMaker document itself and
are flattened in the RoboHelp topic.

Index and glossary

Variables and conditional
text
Variables

Conditional tags

Converted as RoboHelp conditional build tags.

USING ROBOHELP HTML 8 350

Last updated 3/1/2010

Integrating with Adobe Technical Communication Suite

Variables and conditional
text
Equations

Convert equations to images and insert them in the RoboHelp topics after conversion.

Markers
Cross-references, hypertext,
URLs

Index and glossary markers

Converted to an index and glossary when creating project. See “Import FrameMaker index entries” on
page 346“Import glossary definitions” on page 346.

Topic name markers

Context-sensitive Help
markers

Custom markers

Converted. You can use these markers for delineating topics from FrameMaker source, or to pass
processing instructions to RoboHelp for images and tables.

Formats
Paragraph formats

Converted. You can map FrameMaker paragraph formats to RoboHelp styles or import the source
formatting. See “Convert FrameMaker paragraph formats to RoboHelp styles” on page 357

Character formats

Converted. You can map FrameMaker character formats to RoboHelp styles or import the source
formatting. See “Convert FrameMaker character formats to RoboHelp styles” on page 358.

Table formats

Converted. You can map FrameMaker table formats to RoboHelp styles or import the source formatting.
See “Convert FrameMaker table formats to RoboHelp table styles” on page 360.

Converted according to the settings you define. See “List-mapping scenarios” on page 359

Page layouts
Master pages

Reference pages

Ignored. However, you can use the advanced scripting support in RoboHelp to convert images and
graphics placed in the reference pages that are associated with paragraph formats.

Page layout, size, and
pagination

Ignored. These elements are not applicable to online Help. See “Pagination for Help” on page 354.

Headers/footers

Rotated text

Converted to text, such as in table cells. (Rotated text is not supported in HTML).

USING ROBOHELP HTML 8 351

Last updated 3/1/2010

Integrating with Adobe Technical Communication Suite

Images and anchored
frames
Images

Drawings

Drawings created within anchored frames are converted to images. You can define the image
conversion settings. See “Image conversion settings” on page 361.

Anchored frames

Converted to images. See “Image conversion settings” on page 361.

ALT text on images and
anchored frames

Converted. If no ALT text is provided in the FrameMaker document for images RoboHelp applies the
filename of the converted images as the ALT text. See “Create alternative text for images” on page 362.

Text frames, graphic frames,
and images inside anchored
frames

Equations

Enclose equations in anchored frames so that they are converted to images when RoboHelp converts
them.

Structured FrameMaker
components
XML files in book

Converted like FrameMaker documents.

XHTML files in book

Converted like FrameMaker documents.

Content references

Conversion basics
Converting FrameMaker formats to RoboHelp styles
You can define how the FrameMaker formats are converted to RoboHelp styles on the project level. All FrameMaker
format definitions in the FrameMaker document appear in the Conversion Settings dialog box, even if they aren’t used.
You specify the following:

• FrameMaker template used for conversion. This step is optional.
• RoboHelp style sheet for style mapping.

USING ROBOHELP HTML 8 352

Last updated 3/1/2010

Integrating with Adobe Technical Communication Suite

2 Click the Import tab of the Project Settings dialog box. Select Apply FrameMaker Template Before Import.
3 Click Browse to select the FrameMaker template you want to use for the project.

Upgrading from RoboHelp 7 to RoboHelp 8
RoboHelp 7 allowed document-level conversion settings for the FrameMaker documents that you added to a
RoboHelp project. With RoboHelp 8, the conversion settings are applied project-wide, allowing you to have a
consistent set of conversion parameters. If you are opening a RoboHelp 7 project that had FrameMaker documents
added by reference or by copy, you can retain the document-specific settings defined in RoboHelp 7 project.
When you upgrade a RoboHelp 7 project to RoboHelp 8, you can either retain the earlier document-level settings or
convert to the project-level settings supported in RoboHelp 8. After you upgrade your project, you cannot open the
project in RoboHelp 7.
You can add or remove documents to an upgraded project with the document-level conversion settings. You can
define document-level conversion settings for the newly added FrameMaker documents also. This option allows you
to retain the RoboHelp 7 behavior for your upgraded project. However, to take advantage of the enhanced features of
RoboHelp 8 and its integration with FrameMaker, you should upgrade the project completely. For example, RoboHelp
7 provided limited mapping options for autonumbering and list styles. On the other hand, RoboHelp 8 allows you to
map complex autonumber formats and multilevel list styles to RoboHelp styles or HTML lists.
Note: You can discard the document-level settings any time, even if you choose to retain them at the time of upgrading.
However, discarding the document-level settings is irreversible.
Retain or discard RoboHelp 7 settings when upgrading
To retain the document-level settings for converting FrameMaker content into your RoboHelp project, you override
the project-level settings of the converted project with the document-level settings inherited from the RoboHelp 7
project. By default, RoboHelp allows you to retain the document-level settings by overriding the project-level settings.
1 Open the RoboHelp 7 project in RoboHelp 8.
2 Select File > Project Settings.
3 In the Import tab of the Project Settings dialog box, do one of the following:

• To retain the document-level settings in the upgraded project, select the Override Project Settings At Document
Level option. This is the default behavior.

• To discard the document-level settings and use project-level settings, deselect the Override Project Settings At
Document Level option.

Last updated 3/1/2010

USING ROBOHELP HTML 8 353
Integrating with Adobe Technical Communication Suite

Edit document-level conversion settings
If you retain the document-level settings that override the project-level settings for a project converted from an earlier
version of RoboHelp, you can edit these settings.
1 In the Project Manager pod, right-click the added FrameMaker document and select Properties.
2 In the FrameMaker Document Settings dialog box, select the Conversion Settings tab, and set the following.
Apply FrameMaker Conditional Text Build Expression Select to apply conditional text settings before converting

the added FrameMaker document.
Convert AutoNumber To HTML List Select to convert the FrameMaker autonumbering to HTML lists in the

converted HTML topics.
Context-Sensitive Help Marker Specify the context-sensitive Help marker that RoboHelp should use for generating

context-sensitive Help.
User-Defined HTML Tag Select the user-defined HTML tag that you want to use instead of the standard <p> tags in

online Help topics should be done. You specify the FrameMaker paragraph formats separated by commas.
Note: Pagination is based on FrameMaker paragraph formats.

Hierarchy of FrameMaker book reflected in the Project Manager pod when you link a FrameMaker book into RoboHelp

USING ROBOHELP HTML 8 354

Last updated 3/1/2010

Integrating with Adobe Technical Communication Suite

FrameMaker document.
5 Double-click a building block to append it to the RoboHelp cross-reference definition.

Conversion settings
You can create a standard set of conversion settings for importing FrameMaker content into RoboHelp projects and
then use these settings consistently across multiple projects.
You define these settings once. For subsequent projects, import these settings to the project. In this way, you can
quickly set up the project environment and publish FrameMaker content in several online formats.
These settings include:

Import conversion settings to a project
1 Select File > Project Settings.
2 On the Import tab, click Browse.
3 Select a RoboHelp Import Settings File (ISF file) and click Open.

USING ROBOHELP HTML 8 355

Last updated 3/1/2010

Integrating with Adobe Technical Communication Suite

Even though you can set pagination for any FrameMaker paragraph format, follow these guidelines:
Completeness of content in the topic Ensure that the topic generated contains relevant and complete information for
the reader. For example, if you set pagination for Heading 3 level paragraph, it is possible that the topic contains only
the task information, without the required contextual information that is covered in another Heading 3 level topic. To
avoid such disconnected topics, set the pagination at a higher level so that complete information is available in a single
Help topic.
Drop-down text Ensure that the paragraph format for the drop-down text body is not set for pagination. The

paragraphs applied with this format must accompany the drop-down text caption paragraph format.
Topic name pattern
When you set heading styles for pagination, the heading text becomes the default filename for the topic file created in
RoboHelp. For example, suppose you define Heading 2 for pagination, and the FrameMaker document has two
Heading 2 topics, “Introduction” and “Beyond basics.” In this case, RoboHelp creates the topics introduction.htm and
beyond_basics.htm. Thus, you get intuitively named HTML files that indicate the topic title. In addition to this default
scheme, you can define other naming conventions. If the filenames use sequential numbering, such as
helptopic001.html and helptopic002.html, you can define the pattern for such conventions.
1 Select File > Project Settings.
2 In the Import tab of the Project Settings dialog box, click Edit under FrameMaker document.
3 In the Other Settings tab, select one of the following:
Topic Name Pattern Topics are named according to the selected pattern. You can select one of the following or

Converted topic name pattern

default

HTML topic generated has the filename consisting of the paragraph text.

<$filename_no_ext>-<$paratext>

<$filename_no_ext>-<n>

<$paratext_no_num>

<$paratext>

USING ROBOHELP HTML 8 356

Last updated 3/1/2010

Integrating with Adobe Technical Communication Suite

Limitations of style-based pagination and topic titles
Even though it is easy to define pagination and topic title generation based on FrameMaker paragraph formats, this
approach has the following limitations:
Lack of topic-level controls Because the pagination settings are set at the project level, you cannot exercise discrete

control over topics that are not in the defined heading levels. For example, suppose you want to make an H3 level topic
a separate Help topic. If you set pagination at H2 for your project, you can’t do so. The H3 topic is included under the
topic immediately above it.
Uniform topic naming convention Help topics use the same file-naming conventions that you define in the conversion

settings, especially if your authoring environment is Structured FrameMaker. You can’t deviate from these
conventions.
Lack of flexibility in topic titles You cannot selectively alter the titles or filenames of the topics without changing the
source content. When you search for content in RoboHelp, topic titles are displayed in search. An intuitively titled
topic helps the reader quickly identify the most relevant information from search results.
Possibility of inconsistency in documents from multiple books Linked and imported FrameMaker documents from
multiple books can lead to inconsistent heading styles for generated topics.

For example, suppose you link to or import FrameMaker documents from a user guide and reference guide. In this
case, topic titles can reflect differences in style for instructional content and reference content. If topic titles are derived
from the paragraph text at which pagination is set, the Help topics generated can have inconsistent titles.

Advantages of pagination based on FrameMaker custom markers
Using custom markers in FrameMaker, you can overcome these drawbacks for smaller projects and do the following:
Create workflow-based content With the intelligent use of custom markers in FrameMaker, you can create RoboHelp

topics that present users information about the workflow. You can create Help topics irrespective of the heading styles
applied in the FrameMaker document.
Optionally, define the titles of the topic This option becomes useful when you want to combine many topics and

assign a relevant title to the combined topic, rather than derive the topic title text from one of the heading styles.
Optimize topic length Because you define from FrameMaker how Help topics are created in RoboHelp, you can

precisely control the topic length suited for topic-based authoring. However, if you use the mini-TOC feature for your
Help topics, limit the number of headings included in a topic. A long mini-TOC can make the topic contents accessible
only through scrolling.
After you define these markers in your FrameMaker documents, you can set the conversion settings in RoboHelp to
create and name topics according to your preferences.

USING ROBOHELP HTML 8 357

Last updated 3/1/2010

Integrating with Adobe Technical Communication Suite

the context-sensitive Help marker text you inserted in the FrameMaker documents. You then add this file to the
project. When you link or import the FrameMaker documents, you specify the context-sensitive Help marker in the
conversion settings.
1 Select File > Project Settings.
2 In the Import tab of the Project Settings dialog box, click Edit under FrameMaker Document.
3 In the Other Settings group of the Conversion Settings dialog box, select Context-Sensitive Help Marker.

Build Expression.

Converting FrameMaker content
Convert FrameMaker paragraph formats to RoboHelp styles
By default, RoboHelp converts all paragraph formats from FrameMaker to RoboHelp CSS styles. It retains the
appearance and behavior of the FrameMaker formats in the RoboHelp project. To ensure consistency of the online
Help projects, map the FrameMaker formats to RoboHelp styles and edit them.
1 Select File > Project Settings.
2 In the Import tab of the Project Settings dialog box, click Edit under FrameMaker Document.
3 On the Conversion Settings panel, select the FrameMaker format from the Paragraph group.
4 From the RoboHelp Style menu, select the RoboHelp style that you want to map to the FrameMaker format. To

retain the appearance of FrameMaker text in the online Help format, select [Source].
To edit the selected RoboHelp style, click Edit Style.
5 Select the properties for the mapped RoboHelp style:
Exclude From Output Select to discard the content in FrameMaker document that is applied with the selected
FrameMaker paragraph format.
Pagination Select to create a Help topic at each occurrence for the selected FrameMaker paragraph format.
User Defined HTML Tag Select or enter a user-defined HTML tag for the selected paragraph format.

If the selected FrameMaker format has auto numbering properties defined, specify how auto numbering is
converted.

More Help topics
“Custom HTML tags” on page 358
“Autonumber style mapping” on page 358
“Styles and style sheets” on page 143

USING ROBOHELP HTML 8 358

Last updated 3/1/2010

Integrating with Adobe Technical Communication Suite

Convert FrameMaker character formats to RoboHelp styles
You can map the FrameMaker character formats to character styles in RoboHelp.
You can also edit the styles in RoboHelp.
1 Select File > Project Settings.
2 In the Import tab of the Project Settings dialog box, click Edit under FrameMaker Document.
3 Select the FrameMaker character format from the left pane of the Conversion Settings dialog box.
4 Select the RoboHelp character style from the pop-up menu. Optionally, you can do the following:

Custom HTML tags
You can define or apply a custom HTML tag instead of the standard <p> tag for paragraph styles and <span> tag for
character styles in the HTML output for the formats that you import from FrameMaker. You can define separate
HTML tags for each format in the FrameMaker document.
1 Select File > Project Settings.
2 In the Import tab of the Project Settings dialog box, click Edit under FrameMaker Document.
3 In the Conversion Settings dialog box, select the user-defined HTML tag option.
4 Type the name of the custom HTML tag or select an existing tag to use instead of the default HTML tag.

Autonumber style mapping
Choose the conversion setting for converting autonumber formats in the FrameMaker document to the Help format.
If the FrameMaker document contains hierarchical numbered lists, you can choose one of the following:
Ignore Autonumber Choose this option if the autonumber text is relevant only in print format. The converted
paragraph does not contain autonumbering. For example, suppose you ignore autonumbering for the FrameMaker
paragraph format “Section2 Level.” In this case, “Section 1.1: System Requirements” in the source appears as “System
Requirements” in the RoboHelp topic generated.
Convert Autonumber To Text Choose this option to retain the appearance of the FrameMaker numbered lists. The
autonumber part loses its sequencing properties and appears as part of the paragraph text in RoboHelp topic.

USING ROBOHELP HTML 8 359

Last updated 3/1/2010

Integrating with Adobe Technical Communication Suite

Convert Autonumber To HTML List Choose this option to convert the autonumber to HTML lists using HTML tags

such as <ol>, <ul>, and <li>.
Convert Autonumber To RoboHelp List Choose this option if you want to edit the generated HTML topics in
RoboHelp or use the RoboHelp styles to control the numbering properties.

paragraph text in the RoboHelp topic.
Convert Autonumber To HTML List Autonumber format converts to list items using HTML tags such as <ol>, <ul>,

and <li>.
Converted Autonumber To RoboHelp List Autonumber properties of the paragraph style convert to a RoboHelp list.

Example:

• Create a paragraph style “FM_Para1” in FrameMaker with autonumbering defined as <a+> and apply it to
paragraphs. The resulting paragraphs are ordered as “a, b, c, ...."

• Map the FrameMaker paragraph format “FM_Para1” to [Source].
Generated paragraphs in RoboHelp topics have the list style applied to them, where the list has properties similar to
those in the source document.
FrameMaker numbered list mapped to RoboHelp unnumbered style
You can map a FrameMaker paragraph format with autonumbering properties to a RoboHelp paragraph style that is
not linked to any list style. In this case, the autonumber is converted to a list according to the autonumber conversion
settings you define for the paragraph format.
Ignore Autonumber The FrameMaker paragraph autonumber is ignored and doesn't appear in the RoboHelp topic.
However, the paragraph style is mapped.
Convert Autonumber To Text The FrameMaker autonumber part is converted to text and appears as a part of
paragraph text in RoboHelp topic. The paragraph style is mapped.
Convert Autonumber To HTML List The FrameMaker paragraph format is converted to HTML list items using HTML

tags such as <ol>, <ul>, and <li>.
Convert Autonumber To RoboHelp List The autonumber properties of the FrameMaker paragraph format are
ignored. The paragraph style is mapped.

FrameMaker unnumbered format mapped to RoboHelp numbered style
In this case, the converted paragraph has the RoboHelp paragraph style and inherits the RoboHelp list style. The
Autonumber conversion options do not affect the paragraph behavior in the RoboHelp topic.

USING ROBOHELP HTML 8 360

Last updated 3/1/2010

Integrating with Adobe Technical Communication Suite

For example:

• In the FrameMaker document, create a paragraph format "FM_Para 1" without autonumber properties.
• Define a RoboHelp list style “RH_List1” in the RH style mapping CSS.
• Create a paragraph style “RH_Para1” and link the first level of list style “RH_List1” to the paragraph style
“RH_Para1”.

• Map the FrameMaker paragraph style “FM_Para1” to RoboHelp paragraph style “RH_Para1”.
The generated paragraph in the RoboHelp topic inherits the properties of the list style “RH_List1”.
FrameMaker numbered list mapped to RoboHelp numbered list
The converted paragraph style has the RoboHelp paragraph style and inherits the RoboHelp list style. The
Autonumber conversion options do not affect the paragraph behavior in the RoboHelp topic.
For example:

• In FrameMaker, create a paragraph format “FM_Para1” with autonumbering defined as <a+> and apply it to a
paragraph so that the paragraph has an ordered list such as “a, b, c, ….”

• Define a numeric list style “RH_List1” in the RoboHelp style mapping CSS with the first level definition as <x>.
• In RoboHelp, define a paragraph style “RH_Para1” and link the first level of list style “RH_List1” to the paragraph
style “RH_Para1”.

• Map the FrameMaker paragraph format “FM_Para1” to the RoboHelp paragraph style “RH_Para1”.
The generated paragraph in the RoboHelp topic inherits the properties of list style “RH_List1” and displays a list of
type “1, 2, 3, ...."

Convert FrameMaker table formats to RoboHelp table styles
You can map FrameMaker table formats to RoboHelp table styles. Alternatively, you can import the table formats from
the FrameMaker document. You can also edit the table formats in RoboHelp. Cells in the FrameMaker document that
are merged (straddled) cannot be unmerged (unstraddled); however, the straddled cells appear merged in the
RoboHelp topic.
If the FrameMaker table formats contained table titles and table footnotes, convert these paragraph formats in
FrameMaker to RoboHelp paragraph styles separately. Decide whether you want to retain automatic numbering in the
table title styles and specify the autonumbering properties for the mapped RoboHelp paragraph style. For example, if
the table title formats in the FrameMaker documents included the chapter number, such as “Table 2-3: Quarterly
Results”, you can choose to ignore the autonumbering part and have only “Quarterly Results” appear as the table title.
1 Select File > Project Settings.
2 In the Import tab of the Project Settings dialog box, click Edit under FrameMaker Document.
3 Select the FrameMaker table format from the left pane of the Conversion Settings dialog box.
4 Select the RoboHelp table style from the pop-up menu and click OK. Optionally, to edit the table style in RoboHelp,

click Edit Style.

More Help topics
“List-mapping scenarios” on page 359

USING ROBOHELP HTML 8 361

Last updated 3/1/2010

Integrating with Adobe Technical Communication Suite

Image conversion settings
Some FrameMaker documents, especially those optimized for high-quality printing through PDF, contain images in
EPS format. Convert EPS images to web-supported image formats such as JPEG, GIF, PNG, or BMP for online Help.
You specify the following image conversion settings in the Conversion Settings dialog box:
Preferred Dimensions Specify the dimensions for the images. Select one of the following:

• Scale Scale images as a percentage of the existing size. The aspect ratio of the images is maintained.
• Width and Height Specify the absolute image size as Height and Width, in points. Select Maintain Aspect Ratio to
ensure that the images are not skewed.
Note: To convert the images in FrameMaker documents to the actual dimensions of the images, specify the height and
width as 0 pt. The <img> tag for such images in the generated HTML does not have the height and width values. This
conversion is irrespective of the dimensions of the anchored frames that contained the images.

• Set equal margins on all sides by setting the margin in All Sides.
• To set margins on individual sides, set the margins on each side.
Borders Set a border for the images:

• To set a uniform border on all sides, select All from the Border pop-up menu. Alternatively, you can specify the side
on which you want the border to appear from the pop-up menu.

• As Is Select this option for retaining the images in the current web-supported format.
• JPG Select this option for multicolor images such as screenshots or photographs. JPG format with a high color
depth provides the best online quality, but increases the file size.
• GIF Select this option if the FrameMaker document contains only line art, such as schematic diagrams.
• BMP Select this option for screenshots and other images. BMP files provide good quality at an increased file size.
• PNG Select this option for screenshots and photographs.
JPEG Quality Set the quality percentage for JPG images.
Color Bit Depth Set the color bit depth for bitmap images. JPG and PNG formats can have either 8- or 24-bit color

depth, while BMP images can be have color bit depths of 1, 4, 8, 16, 24, or 32. GIF images can have only 8-bit color
depth.

USING ROBOHELP HTML 8 362

Last updated 3/1/2010

Integrating with Adobe Technical Communication Suite

Grayscale Select this option if you want monochrome images.

More Help topics
“Preserve converted images” on page 362

Create alternative text for images
To create accessible content, create alternative text for images so that visually impaired users can access the content
through screen readers. If you link or import completed FrameMaker books into RoboHelp for publication, add
alternative text to graphics used in the FrameMaker documents. These entries are not visible in PDF files, but they
appear in online content when the mouse hovers over the images.

Creating dynamic HTML effects in FrameMaker documents
You can create dynamic HTML effects such as drop-down text and expanding text in your FrameMaker documents if
you want to have the published online Help formats to have these options.
Note: This option is available only if you have Technical Communication Suite installed.
Use the drop-down text effect to provide alternative task options and basic conceptual topics, summarize the questions
on an FAQ, and shorten nested procedures. Text that you mark as drop-down body is displayed in your PDF output.
But the text appears online only when the user clicks the drop-down text caption on the Help page.
Similarly, you can use expanding text DHTML effect to display expanded definitions, key terms, or links to overview
topics embedded in a paragraph. Expanding text requires an expanding text caption that contains the link and
expanding text body that is displayed when a user clicks the expanding text link. Expanding text body is not displayed
in PDF. It appears only in the Help page when a user clicks the text that contains the expanding text link.
These DHTML effects require two components: a caption and body. You apply the drop-down text effects to
paragraphs and the expanding text effect to characters. When the drop-down text effect is created, two paragraph
formats, DropDownCaption and DropDownBody, are added to the FrameMaker document. When the expanding text
effect is created, two character formats—ExpandingTextCaption and ExpandingTextBody—are added. These formats
are imported to the RoboHelp project when you import the FrameMaker documents. The effects are visible in the
created HTML topics.

USING ROBOHELP HTML 8 363

Last updated 3/1/2010

Integrating with Adobe Technical Communication Suite

If the HTML topic generated contains only the captions without the accompanying body formats, links are generated
and visible in the HTML topic. If the HTML topic generated contains a text body without the corresponding captions,
no links are generated. In addition, if a paragraph to which the drop-down text body format is applied is also specified
for conversion to an autonumbered list, the list conversion is ignored.

Create drop-down text in a FrameMaker document
1 Select the text or paragraph on which you want to place the drop-down text caption.
2 Select Adobe RoboHelp > Dynamic HTML Effects > Drop Down Caption.
3 Select the text that should appear as drop-down text in your online Help page.
4 Select Adobe RoboHelp > Dynamic HTML Effects > Drop Down Body.

Create expanding text in a FrameMaker document
1 Select the term or phrase on which you want to place the expanding text caption.
2 Select Adobe RoboHelp > Dynamic HTML Effects > Expanding Text Caption.
3 Select the text that should appear as expanding text in your online Help page.
4 Select Adobe RoboHelp > Dynamic HTML Effects > Expanding Text Body.

Send PDF files for review
Use the Convert To Adobe PDF And Send For Review feature in RoboHelp to save a project as a PDF file to send for
review by e-mail. The HTML files in the project convert to a PDF file attached to a new e-mail message in your default
e-mail application.
Note: You can use this feature only if you have installed Adobe Acrobat 8 or later. Reviewers must have Adobe Reader 7
or later installed on their computers to review the document.
RoboHelp uses the Printed Documentation layout to generate the PDF. You can modify the layout to generate a PDF
according to your requirements.
1 Open the RoboHelp project.
2 Select Tools > Convert To Adobe PDF And Send For Review. The Generating Printed Documentation progress

window appears, indicating the progress of the PDF file generation. The generated PDF file opens in Acrobat with
the Getting Started page of the Attach For Email Review wizard displayed.
The new PDF file is the default file selected to be sent for review. If necessary, select a different PDF file.
3 Click Next. The Invite Reviewers page is displayed.
4 Click Address Book, and select the e-mail addresses of persons to review the PDF file. Click OK.
5 Click Next.

In the Preview Invitation page, specify the subject and content of the e-mail invitation to be sent to reviewers.
6 Click Send Invitation.

Acrobat notifies you that an e-mail message has been sent to the default e-mail application on your computer. A
copy of the PDF is sent to the reviewers as an attachment. When reviewers open this file attachment, Acrobat opens
the PDF file with a commenting toolbar.
7 Click OK.

USING ROBOHELP HTML 8 364

Last updated 3/1/2010

Integrating with Adobe Technical Communication Suite

More Help topics
“Generate PDFs” on page 310

Start an online meeting using ConnectNow
You can start Adobe ConnectNow from all the components of the Adobe Technical Communication Suite (Adobe
Acrobat Extended, Adobe Captivate, Adobe FrameMaker, Adobe RoboHelp, and Adobe Photoshop). Start Adobe
ConnectNow to set up or access online meeting rooms.
Note: For more information on using ConnectNow, see www.adobe.com/acom/connectnow/.

Create a ConnectNow account
Create an Adobe ConnectNow account so you can set up online meetings. The online meeting functionality is enabled
in Acrobat versions later than Adobe Acrobat 3D version 8.
Note: Reviewers must have Adobe Reader 7 or later versions installed to review the documents.
1 In RoboHelp, Click Tools > Start Meeting. The Adobe Acrobat Professional Extended application opens with the

Sign In (Acrobat.com) dialog box displayed.
2 Click Create Adobe ID to create a ConnectNow account. Follow the onscreen instructions.

Start and use ConnectNow
1 In RoboHelp, Click Tools > Start Meeting. The Adobe Acrobat Professional Extended application opens and

displays the Sign In (Acrobat.com) dialog box.
2 Enter your Adobe ID (e-mail address) and password. Click Sign In. ConnectNow opens your meeting room,

displaying the Meet Online With Others dialog box.
3 Click Send Email Invitation Now to invite other users to your ConnectNow meeting room. Type the e-mail

addresses of attendees in the e-mail application window that opens, and send the message.
You can also invite participants by clicking Meeting > Invite Participants on your meeting room page.
Note: If you want to change the URL of your meeting room, click Customize Your Meeting URL in the Meet Online
With Others dialog box.
4 Click Meeting > Preferences on your meeting room page to review and set your ConnectNow preferences.
5 Click Share My Computer Screen to share your computer screen with other users. The Start Screen Sharing dialog

box appears.
6 Click Share. A brief introduction to screen sharing appears. Review it and click OK.

Note: When you share your screen, attendees see everything that happens on your computer screen, including e-mail
pop-ups, alerts, and visible windows and applications.
7 When a person joins your meeting, a pop-up window prompts you to grant access to them. The person’s name

appears in the Attendees pod after you click Accept.
8 You can control how attendees take part in your online meeting. To do so, select the person’s name from the

Attendees pod, and click Role from the pop-up menu. Select one of the following:
Host Select if you want the attendee to share their desktop.
Participant Select if you want the attendee to be able to enter notes in the Shared Notes pod.

Last updated 3/1/2010

USING ROBOHELP HTML 8 365
Integrating with Adobe Technical Communication Suite

Audience Select if you don’t want an attendee to be able to enter notes in the Shared Notes pod.

9 To chat with the attendees, type a message in the Chat pod, select the attendees to whom you want to send the

message, and click Send.
To take notes during the meeting, use Notepad.

366

Last updated 3/1/2010

Chapter 15: Default keyboard shortcuts
Adobe RoboHelp HTML provides shortcuts to help you quickly work in documents without using the mouse. Use
these shortcuts in Design Editor. Additional keyboard shortcuts appear next to the command names in menus.
Note: To use certain shortcuts, you must select text first. Those cases are marked with an asterisk (*).
Task

Keyboard shortcut

Basic operations
Open project

CTRL+O (letter O)

Save All

CTRL+S

Undo

CTRL+Z

Redo

CTRL+Y

Cut

CTRL+X

Copy

CTRL+C

Paste

CTRL+V

Delete

Delete button

Close All

Ctrl+Alt+X

Select all

CTRL+A

Find

CTRL+F

Replace

Ctrl+H

Go to bookmark

Print from active pane

CTRL+P

Help

Spell check active pane

Thesaurus

SHIFT+F7

Create a topic

Ctrl+T

Duplicate a topic

Ctrl+D

Edit item

Ctrl+E

Close a topic

Ctrl+F4

Rename

Paragraph markers

CTRL+SHIFT+8

Preview topic

CTRL+W

Insert hypertext link*

CTRL+K*

Insert image

CTRL+G

Insert text-only pop-up window*

CTRL+ALT+P

USING ROBOHELP HTML 8 367

Last updated 3/1/2010

Default keyboard shortcuts

Task

Keyboard shortcut

Open Project Settings dialog

CTRL+SHIFT+/

Open Topic Properties dialog

ALT+ENTER

Display Conditional Build Tag dialog*

CTRL+N

Text formatting in Design Editor
Bold

CTRL+B

Italicize

CTRL+I

Underline

CTRL+U

Format – Paragraph menu

CTRL+SHIFT+D

Format – Font menu

CTRL+D

Font change

CTRL+SHIFT+F

Increase font size to next size in menu*

CTRL+SHIFT+>

Decrease font size to previous size in menu*

CTRL+SHIFT+<

Increase font size by 1 point*

CTRL+]

Decrease font size by 1 point*

CTRL+[

Styles in Design Editor
Apply a style*

CTRL+SHIFT+S

Apply the Normal style

CTRL+SHIFT+N

Apply a Bullets or Numbering style

CTRL+SHIFT+L

Apply Heading 1*

ALT+CTRL+1

Apply Heading 2*

ALT+CTRL+2

Apply Heading 3*

ALT+CTRL+3

TOC pod
Move book or topic up in the table of contents

CTRL+Up Arrow

Move book or topic down in the table of contents

CTRL+Down Arrow

Move book or topic to the left in the table of contents

CTRL+Left Arrow

Move book or topic to the right in the table of contents

CTRL+Right Arrow

Index pod
Change index keyword to lowercase

CTRL+L

Change first letter of index keyword to uppercase

CTRL+J

Version Control
Refresh version status on File Status tab

*Select text first.

368

Last updated 3/1/2010

Index
Symbols
.doc, .docx 56

G
glossary 172

.NET 230

P
pods 13
printed documentation 300

.rtf 56

H
Help 2

project names 30

A
ActiveX controls 323

HTML comments 204
HTML editor 122

R
rename project 30

adding images 196

HTML files 42

Resource Manager 15

alt text 70, 349

HTML Help 262

RoboSource Control 31

APIs 218

HTML tags 80, 358

B
baggage files 40, 41

I
iframes 205

breadcrumbs 178

import CHM 262

skins 311

BugHunter 252

import FrameMaker 68

snippets 141

import Word 54

style sheets 143

C
CHM 262

indexes 158

Styles pod 15

conditional build 207
conditional text 206

J
JavaHelp 264

context-sensitive Help 212

JavaScript 218

server 260

synonyms 29

create TOCs 153
CSH files 218

S
search 177

T
table of contents 153
table styles 131
templates 107

CSS 143

K
keyword search 191

D
database 33

L
language support 45

designing skins 311

lists 134

U
user-defined variables 138

map files 213

vb.net 219

map IDs 213

Visual Studio 221

TOCs 153
twisties 339

DITA map 84
E
expanding text 339

mapping styles 59
F
file mapping 40

master pages 107
merge projects 34

W
WebHelp 257

Flash Player 23

mini TOC 107

WebHelp Pro 259

Flash skins 314

multi-lingual Help 45

WebHelp skins 314

FlashHelp 260
FlashHelp Pro 259
font sets 125

What Is? Help 245
N
NET 230

font type 125
fonts 125
frames 329

What’s This? Help 245
WinHelp 87
Word files 56

O
Office Pro .NET 230
output formats 22

X
XHTML 104
XML 85

</pre><hr>Source Exif Data: <br /><pre>File Type : PDF
File Type Extension : pdf
MIME Type : application/pdf
PDF Version : 1.4
Linearized : Yes
Tagged PDF : Yes
Page Mode : UseOutlines
XMP Toolkit : Adobe XMP Core 4.0-c320 44.284297, Mon Apr 16 2007 09:10:35
Format : application/pdf
Title : Using Adobe® RoboHelp® HTML 8
Description : Adobe RoboHelp 8
Creator : Adobe Systems Incorporated
Create Date : 2010:03:01 22:54:39Z
Modify Date : 2010:03:01 22:54:39Z
Creator Tool : FrameMaker 8.0
Producer : Acrobat Distiller Server 8.1.0 (Sparc Solaris, Built: 2007-09-07)
Document ID : uuid:abbb1e7c-1dd1-11b2-0a00-001838d80016
Instance ID : uuid:abbb1e83-1dd1-11b2-0a00-ffbff2d8fdb2
Page Count : 374
Subject : Adobe RoboHelp 8
Author : Adobe Systems Incorporated
</pre>
<small>EXIF Metadata provided by <a href="https://exif.tools/">EXIF.tools</a></small>

<div id="ezoic-pub-ad-placeholder-110">
<script async src="//pagead2.googlesyndication.com/pagead/js/adsbygoogle.js"></script>

<ins class="adsbygoogle"
style="display:block"
data-ad-client="ca-pub-0545639743190253"
data-ad-slot="6172135303"
data-ad-format="link"></ins>
<script>
(adsbygoogle = window.adsbygoogle || []).push({});
</script>
</div>
</div>
<div id="catlinks" class="catlinks catlinks-allhidden" data-mw="interface"></div> <div class="visualClear"></div>
</div>
</div>
<div id="mw-navigation">
<h2>Navigation menu</h2>

<form action="https://usermanual.wiki/search.php" id="searchform">
<div id="simpleSearch">
<input type="search" name="search" placeholder="Search UserManual.wiki" title="Search UserManual.wiki [ctrl-option-f]" accesskey="f" id="searchInput" tabindex="1" autocomplete="off"><input type="hidden" value="Special:Search" name="title"><input type="submit" name="go" value="Go" title="Find a User Manual" id="searchButton" class="searchButton"> </div>
</form>
</div>-->
<ul>
<li id="pt-mycontris"><a href="https://usermanual.wiki/upload" title="Upload User Manual" accesskey="y">Upload a User Manual</a></li>
</ul>
</div>
<div id="left-navigation">
<div id="p-namespaces" role="navigation" class="vectorTabs" aria-labelledby="p-namespaces-label">
<h3 id="p-namespaces-label">Versions of this User Manual:</h3>
<ul>
<li id="ca-nstab-main"><span><a href="https://usermanual.wiki/adobe/robohtml8en.138503044" title="User Manual Wiki" accesskey="c">Wiki Guide</a></span></li> <li id="ca-nstab-main"><span><a href="https://usermanual.wiki/adobe/robohtml8en.138503044/html" title="HTML" accesskey="c">HTML</a></span></li> <li id="ca-nstab-main"><span><a href="https://usermanual.wiki/adobe/robohtml8en.138503044/amp" title="Mobile AMP" accesskey="c">Mobile</a></span></li> <li id="ca-nstab-main" class="selected" ><span><a href="https://usermanual.wiki/adobe/robohtml8en.138503044/help" title="Discussion / FAQ / Help" accesskey="c">Download & Help</a></span></li>
</ul>
</div>
</div>
<div id="right-navigation">
<div id="p-views" role="navigation" class="vectorTabs" aria-labelledby="p-views-label">
<h3 id="p-views-label">Views</h3>
<ul>

<li id="ca-view"><span><a href="#">User Manual</a></span></li>

<li class="selected" id="ca-edit"><span><a href="https://usermanual.wiki/adobe/robohtml8en.138503044/help" title="Ask a question" accesskey="e">Discussion / Help</a></span></li>

</ul>
</div>
</div>
</div>
<div id="mw-panel">
<div id="p-logo" role="banner"><a class="mw-wiki-logo" href="https://usermanual.wiki/Main_Page" title="Visit the main page"></a></div>
<div class="portal" role="navigation" id="p-navigation" aria-labelledby="p-navigation-label">
<h3 id="p-navigation-label">Navigation</h3>

</div>
<div class="portal" role="navigation" id="p-tb" aria-labelledby="p-tb-label">

</div>
</div>
</div>
<div id="footer" role="contentinfo">
<ul id="footer-info">
<li id="footer-info-lastmod">© 2024 UserManual.wiki</li>
</ul>
<ul id="footer-places">
<li id="footer-places-privacy"><a href="https://usermanual.wiki/ContactUs" title="UserManual.wiki:Contact Us">Contact Us</a></li>
<li id="footer-places-about"><a href="https://usermanual.wiki/DMCA" title="UserManual.wiki:DMCA">DMCA</a></li>
</ul>
<ul id="footer-icons" class="noprint">
<li id="footer-poweredbyico">

</li>
</ul>

</div>

</div></body></html>
<script src="/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js" data-cf-settings="526683dc77ca0e8c65915e6f-|49" defer></script>