rtf-ctrl has been Revised

When Word 6.0 was released, it introduced some new control words which rtftohtml 2.7.5 was not aware of. These caused messages to appear like:
ReadStyleSheet: unknown token "\widctlpar"
Unknown symbol "\sprstsm" near line 9, position 66.
Unknown symbol "\truncex" near line 9, position 74.
Unknown symbol "\nolead" near line 9, position 81.
Unknown symbol "\msmcap" near line 9, position 88.
Unknown symbol "\widctlpar" near line 12, position 17.
In addition, Word 6.0 uses \super for footnotes instead of \up, which confuses the filter.

To correct these problems, get the new version of rtf-ctrl and copy it into your folder or directory containing the filter.

Download the new rtf-ctrl

Changes in rtftohtml 2.7.5

*    some list element\line
     more stuff belonging to same list element, but on a different line.


IMPORTANT!

To make drag-n-drop of MSWord 6.0 RTF files work on your Macintosh, you must:

1. Download rtftohtml 2.7.5 onto your Macintosh

2. Copy ALL PREVIOUS VERSIONS of rtftohtml onto a backup disk. Then REMOVE them from your hard-disk.

3. Restart your Macintosh, while holding down the OPTION and Apple keys. This will re-build your desktop.


Changes in rtftohtml 2.7.4

Changes in rtftohtml 2.7.3

Changes in rtftohtml 2.7

Notes on rtftohtml 2.5

This release of rtftohtml requires a new version of the html-trans file. Using your old one will not work.

The new format file has an additional item added to the .PTag table. An entry now looks like this:
#"name","starttag","endtag","col2mark","tabmark","parmark",allowtext,cannest,DelteCol1,fold
.PTag
...
"Normal","","\n","\t","\t","<p>\n",1,0,0,1
"pre","<pre>","</pre>","\t","\t","\n",0,0,0,0

The fold field should be set to zero (0) for all entries except "pre" or "listing". A zero entry allows rtftohtml to insert newlines "\n" into the source so that lines do not get too long in your HTML file. This feature is designed to make editing/viewing of HTML source files easier with editors like vi. You must use one (1) for "pre" and "listing" because newlines are significant characters for these markups.

You must add the following entry to your .PTag table. This is required to support table translation.

# This is a required entry; tables will be formatted with this entry
"_Table","<pre>","</pre>","\t","\t","\n",0,0,0,0

You must add the following entry to your .PMatch table:

# This is a required entry; tables will be formatted with this entry
"_Table",0,"_Table"

Table Translation

rtftohtml will now translate tables into preformatted ascii tables. Tables cannot contain any markup. That is, BOLD, ITALIC etc. will be ignored. Also tables cannot contain anchors, footnotes, or hidden text.

The filter will produce a table that has the same number of columns as the input. The size of the columns will be proportional to the sizes of the input columns. Note that there is no guarantee that text that fit in your original table will still fit in the formatted version. This is because the point size of input may not be proportional to the fixed size 80-characters per-column output. If you find that you do not like the look of the formatted table - you must re-size the columns in your RTF source.

Columns are always separated by two blanks.

Columns can be left justified, right justified or centered.

Merged cells are allowed.

There is no support for decimal aligned data. This just looked too hard and prone to error. For now, you will have to make sure that all your data has the same number of trailing digits and stick to right justified text.

A REAL Macintosh interface

The filter now supports drag-n-drop on the Macintosh!

Options are set with menu selections!

The signiture is even registered with Apple!

To use rtftohtml on the Macintosh:

Keep all of the translation files (html-trans, ansi-map...) in the same folder as the application.

Drag any RTF file onto rtftohtml (requires system 7.) The output files will be placed in the same folder as your input file. If there are any errors in translating your file, the error messages will be put into a file called filename.err . Some errors will cause rtftohtml to exit, others will not.

Once rtftohtml is started, it will continue to run! This allows you to translate many documents at a time. You can drag lots of files onto rtftohtml and it will translate all of them (unless it encounters a fatal translation error.)

To use non-default translation options, simply start rtftohtml by double clicking on it. Then choose your option from the options menu. These settings will remain in effect until rtftohtml exits. The next time you run rtftohtml you must choose your option settings again.

You can open RTF files using Open... from the File menu. This will only work for files with an extension of .rtf (or .RTF). If you want to open a file without an extension of .rtf, you must hold down the option key when selecting Open.

Options Menu

The Graphic file extension in the Options menu allows you to change the default extension for graphic files from ".gif" to an extension of your own chooseing.

The Inline graphics option will (when set) use <IMG SRC=... markup in HTML files for graphics instead of <A HREF=...

The Auto Filenames option when set will put the HTML output in the same folder as the input, with a .HTML extension. If you want to specify your own filenames, turn this option off. Then rtftohtml will prompt you for an output file name each time a file is translated.

Miscellaneous Features

"toc 1",0,"_Discard"
"toc 2",0,"_Discard"
"toc 3",0,"_Discard"
"toc 4",0,"_Discard"
"toc 5",0,"_Discard"
"index 1",0,"_Discard"
"index 2",0,"_Discard"
"index 3",0,"_Discard"
"index 4",0,"_Discard"
"index 5",0,"_Discard"

Bugs Fixed in 2.5

rtftohtml was generating "unknown symbol" errors for optional destinations (RTF with a markup of {\*\xxx ... } The convention for RTF readers is that any optional destination that a reader does not understand should be silently ignored. This bug was also causing extra text to be inserted into HTML files.

Bugs fixed in 2.1

Bugs fixed in 2.0.1