users_guide.html

将rft格式文件转换成html格式文件

because we leave that up to the HTML client. No nesting is allowed - (see the
discussion on nested styles). No text is deleted. Every paragraph using this
markup will also generate a level-1 table of contents entry.

<pre>

"Normal","","\n","\t","\t","&lt;p&gt;\n",1,0,0,0
</pre>
This
is the default for normal text. Regular text in HTML has no required start and
end-tags. The "\n" in the end-tag field forces a newline in the HTML markup.
Since newlines are ignored in HTML (except in &lt;pre&gt;) it's only effect is
to make the HTML output more readable. There is no difference between the first
tab and any other. They both translate to a tab mark. Paragraph marks generate
"&lt;p&gt;" followed by a newline (just for looks). Text markup (like
&lt;b&gt;) is allowed within Normal text. No nesting is allowed - (see the
discussion on nested styles). No text is deleted.

<pre>

"ul","&lt;ul&gt;\n&lt;li&gt;","&lt;/ul&gt;","\t","\t","\n&lt;li&gt;",1,1,0,0
</pre>
This
is the entry for unordered lists. This generates a "&lt;ul&gt;\n&lt;li&gt;" at
the start of the list and "&lt;/ul&gt;/n" at the end. There is no difference
between the first tab and any other. They both translate to a tab mark.
Paragraph marks generate "&lt;li&gt;" preceded by a newline (just for looks).
Text markup (like &lt;b&gt;) is allowed, and this entry may be nested - and it
allows others to be nested within it. This allows nested lists. No text is
deleted.<p>


<pre>
"ul-d","&lt;ul&gt;\n&lt;li&gt;","&lt;/ul&gt;","\t","\t","\n&lt;li&gt;",1,1,1,0
</pre>
This
entry is identical to the previous except that the DeleteCol1 field is set to
1. This is used to remove bullets (which really appear in the RTF) because we
don't want to see them in the HTML.<p>

<h3>
<a name="RTFToC14">.TTag
Table
</a></h3>
Each entry in the .TTag table describes an HTML text markup. The format is: <p>
.TTag<p>
"name","starttag","endtag"
<dl>
<dt><b>name</b>
<dd>A unique name for this entry. These names are referenced in the .PMatch
table.
<dt><b>starttag</b>
<dd>This string will be output once at the beginning of any text for this
markup.
<dt><b>endtag</b>
<dd>This string will be output once at the end of any text for this
markup.</dl>Note that unlike the .PTag table, no text markup should appear more
than once. (Of course there is no good reason that it should appear.) If you
have two entries with &lt;b&gt;&lt;/b&gt; start and end tags, it would be
possible to get HTML of the form &lt;b&gt;&lt;b&gt; text&lt;/b&gt;&lt;/b&gt;. I
don't know if this is invalid markup, but it sure is ugly.<p>

<h3>
<a name="RTFToC15">.PMatch
Table
</a></h3>
Each entry in the .PMatch correlates a paragraph style name to some entry in
the .PTag table. The format is: <p>
.PMatch<p>
"Paragraph Style",nesting_level,"PTagName"
<dl>
<dt><b>Paragraph Style</b>
<dd>The paragraph style name that appears in the RTF input.
<dt><b>nesting_level</b>
<dd>The nesting level. This should be zero except for nested list entries.
<dt><b>PTagName</b>
<dd>The name of the .PTag entry that should be used for paragraphs with this
paragraph style. </dl><p>

<h4>
<a name="RTFToC16">Sample
.PMatch Entries
</a></h4>

<pre>
"heading 1",0,"h1"
</pre>
This
is a level 1 heading.  Any paragraphs with this paragraph style will be mapped
to the entry in the .PTag table named "h1".

<pre>

"numbered list",0,"ol-d"
</pre>
This
is used for numbered lists.  Any paragraphs with this paragraph style will be
mapped to the entry in the .PTag table named "ol-d". 

<pre>

"numbered list 2",2,"ol-d"
</pre>
This
is an entry for a nested paragraph style. The nesting level of two is used to
indicate that this paragraph should appear in the HTML nested within two levels
of paragraph markups. The paragraph marked with this style may only appear
after  a paragraph style that has a nesting level of 1 or greater.

<pre>

</pre>

<h3>
<a name="RTFToC17">.TMatch
Table
</a></h3>
Each entry in the .TMatch table describes processing for text styles. The
format is: <p>
.TMatch

<pre>
"Font",FontSize,Match,Mask,"TextStyleName"
</pre>
<dl>
<dt><b>Font</b>
<dd>The name of a Font, or "" if all fonts match this entry.
<dt><b>FontSize</b>
<dd>The point-size of the font, or 0 if all point sizes match this entry.,
<dt><b>Match</b>
<dd>A bit-mask, where each bit represents a text attribute. These bits are
compared to the attributes of the style being output. They must match for this
entry to be matched. One in a bit position means that the text style is set, a
zero is not set.
<dt><b>Mask</b>
<dd>A bit-mask, where each bit represents a text attribute. In comparing the
style of the text being processed, to the Match bit-mask, this field is used to
select the bits that matter. If a zero appears in a  bit-position, then that
style attribute is ignored (for the purpose of matching this entry.) Only 1
bits are used in the above comparision.
<dt><b>TextStyleName</b>
<dd>This is either the name of an entry in the .TTag table indicating the HTML
markup to use, or it is one of "_Discard", "_Name",  "_HRef", "_Hot", or
"_Literal".</dl>

<pre>
The order of bits in the Match and Mask bit-maps are:
#    v^bDWUHACSOTIB - Bold
#    v^bDWUHACSOTI - Italic
#    v^bDWUHACSOT - StrikeThrough
#    v^bDWUHACSO - Outline
#    v^bDWUHACS - Shadow
#    v^bDWUHAC - SmallCaps
#    v^bDWUHA - AllCaps
#    v^bDWUH - Hidden
#    v^bDWU - Underline
#    v^bDW - Word Underline
#    v^bD - Dotted Underline
#    v^b - Double Underline
#    v^ - SuperScript
#    v - SubScript
</pre>
<p>

<h4>
<a name="RTFToC18">Sample
.PTag Entries
</a></h4>

<pre>
# double-underline/not hidden -&gt; hot text
# double-underline/hidden -&gt; href
#    v^bDWUHACSOTIB,v^bDWUHACSOTIB
"",0,00100000000000,00100010000000,"_Hot"
"",0,00100010000000,00100010000000,"_HRef"
</pre>
The
first entry will match any text formatted with double underline EXCEPT if it is
hidden text. This is accomplished by using those two bits to compare (the MASK
field) and having a 1 in the double underline bit and a zero for the hidden
text bit. The second entry will match any text formatted with BOTH double
underline and hidden text. Any text that matches the first will be treated as
the hot text of a link. Any text that matches the second will be taken as the
href itself. (The filter requires that the HRef text immediately precede the
Hot text.) <p>


<pre>
# Regular matches - You can have multiple of these active
# monospace fonts -&gt; tt
"Courier",0,00000000000000,00000000000000,"tt"
</pre>
This
will match any text that uses the Courier font and mark it using the HTML text
markup appearing in the .TTag table with the entry name "tt".<p>


<pre>
# bold -&gt; bold
#    v^bDWUIACSOTIB,v^bDWUIACSOTIB
"",0,00000000000001,00000000000001,"b"
</pre>
This
will match any text that has bold attributes and will mark it using the HTML
text markup appearing in the .TTag table with the entry name "b". Note that
bold text using the Courier font would match both this entry and the previous.
This will yeild markup of the form &lt;b&gt;&lt;tt&gt;hi&lt;/tt&gt;&lt;b&gt;.
Note that "b" is the name of an entry in the .TTag table, not the HTML markup
that is used! <p>

<h2>
<a name="RTFToC19">Adding
Paragraph Styles
</a></h2>
To add a new paragraph style, simply go to the .PMatch table and add an entry
to the end. Put the name of the paragraph style (quoted), the nesting level
(usually zero) and the name of the .PTag entry that should be used. 
<h1>
<a name="RTFToC20">Command
Line Options
</a></h1>
The syntax of the rtftohtml command is as follows:

<pre>
rtftohtml [-i] [ -V] [-o filename] [-P extension] [-T] [-G][file]
</pre>
<dl>
<dt><b>-i</b>
<dd>Indicates that imbedded graphics should be linked into the main document
using an IMG tag. The default is to use an HREF style link.
<dt><b>-V</b>
<dd>Prints the current Version to stderr.
<dt><b>-o filename</b>
<dd>Indicates that the output file name should be "filename". If any other
files are created (such as for graphics,) the basename of the other files will
be "filename" without ".rtf" if it is present in the name.
<dt><b>-P extension</b>
<dd>Use "extension" as the extension for any links to graphics files. The
default for this is "gif".
<dt><b>-T</b>
<dd>Indicates that no table of contents file is to be generated.
<dt><b>-G</b>
<dd>Indicates that no graphics files should be written. The hypertext links to
the graphics files will still be generated. This is a performance feature for
when you are re-translating a document and the graphics have not changed.
<dt><b>"file"</b>
<dd>The file name to be processed. If no file is given, standard input is used.
If standard input is used, the body of the document will be written to standard
output (unless overridden by the -o option.) If a file name appears, the output
is written to "filename" with ".html" as an extension. (If ".rtf" appears as an
extension on the original input file, it is stripped before appending the
".html") </dl><h1>
<a name="RTFToC21">Nested
Lists
</a></h1>
Nested lists can be made from an RTF document by using a different style for
each level of indentation. The styles "bullet list 1" "numbered list 2" ...
represent different levels of nesting. The only rule for use is that no levels
of nesting are skipped. For example, a "ol 3" paragraph must not appear
immediately after a "Normal" paragraph. It must follow a paragraph with a
nesting level of 2 or higher. For examples of nesting see 
<a href="sample_styles.html">
the sample style sheet.</a> .rtf
<ol>
<li></ol>
</body></html>