|
|
|
|
|
HTML purposely has just a few constructs with which to tag information.
Headings: <h1></h1>, <h2></h2>, <h3></h3>
Paragraph text: <p></p>
Pre-formatted text: <pre></pre>
For proper viewing in HTML, all FM formats need to mapped to one of these. Thankfully, the cascading style sheet (CSS) permits the definition of classes that can further define formatting to one of these tags.
Even though my FrameMaker environment has four levels of paragraph formats - Title<...>, Head<1>[Kwp], Head<1>[Kwp], Head<1>[Kwp] - they are all mapped to h1. The <hn> tags in HTML are used for display and not necessarily hierarchical relationships.
[ParaStyles] TitleChapter=h1 TitleAppendix=h1 TitleFront=h1 TitleIndex=h1 TitleIntro=h1 Head1=h1 Head2=h1 Head3=h1 Head1Kwp=h1 Head2Kwp=h1 Head3Kwp=h1
The Voyant documentation sometimes has programming code or command-line syntax that would be incorrect if permitted to automatically word-wrap based on the browsers Window size. The appropriate FrameMaker code<...> paragraph format provides the correct font and layout characteristics in the print/PDF. In order to assure that no inadvertent word-wrapping occurs in the HTML output, these FM paragraph formats are mapped to the HTML <pre> tags.
[ParaStyles] Code=PRE Code1=PRE Code10pt=PRE Code11pt=PRE Code2=PRE Code3=PRE Code4=PRE Code4 (body Indent)=PRE Code5=PRE Code9pt=PRE CodeAPI=PRE
It is assumed that all other FrameMaker styles encountered during the export to HTML will be mapped to a <p> style with an appropriate class refinement (that the cascading style sheet controls).
The mapping of styles using [ParaStyles] is a construct that is part of Mif2Go in one of its INI files. However, the ability to map styles is a fundamental part of any other Help Authoring Tools, such as WebWorks Publisher (WWP). Such tools will have a configuration tool or file that can establish the same settings.
|
|
|
Open-Source tools compliments of Voyant Technologies, Inc. and Glenn C. Maxey.
01/13/2003
TP Tools v2-00-0a
# tpt-hug-02