| |
TechNote 10010: How WinHelp RTF content is converted
This
TechNote attempts to explain how HyperText Studio converts the content in an
RTF file.
Footnotes
| Footnote |
Description |
Action |
| $ |
Title |
Set as the topic title |
| # |
Context string |
Set as the topic's context string. If the context string
already exists in the project, a unique context string is created.
If the footnote is not at the start of the topic an anchor is created,
using the specified context string.
|
| + |
Browse no |
If auto browse numbering (in the book properties) is on will
attempt to create a structure in the contents tree based on the available
sequences and numbers.
If auto browse numbering is off will set the topic's browse sequence
property to the footnote string.
|
| * |
Build Tag |
Ignored |
| A,K |
Keywords |
Creates the specified keywords if necessary. If the footnote
is at the start of the topic, the keywords are applied to the topic, otherwise
an anchor is created for them. |
| ! |
Macros |
Creates an entry macro in the topic. |
| @ |
Comment |
Creates a comment tag in the topic containing the comment. |
| > |
Window |
Sets the window property for the topic. |
| - |
internal hts |
Processed by the HyperText Studio. |
| < |
internal hts |
Processed by the HyperText Studio. |
| Anything else |
|
Added as a multi char keyword |
Macro links
Macro links are left as they are except for OsTools_OpenURL which is converted
to an Internet link.
SHG files
SHG files are converted to bmp or wmf and output into a project folder. Hotsposts
are created as an image map in each topic that uses the shg. This is because
HTML requires each use of the image to have its own image map. This means that
in the future you need to change the hotspots in multiple places if you have
used the SHG file that way.
|
|