Known Bugs
This file is under construction.
Please send bug reports to cjh@cray.com.
Bugs fixed in 2.1
- rtftohtml generates empty anchors <a name="myname"></a> where the "Named Anchor" feature is used. Xmosaic does not support empty anchors, although other browsers (including Mac Mosaic) do. I have reported this as a bug to the good folks at NCSA. I am hoping that they fix this so that I don't have to patch the filter. Stay tuned. - The good folks at NCSA told me not to wait, so I revised rtftohtml to create anchors with an extra space: <a name="myname"> </a>
- Imbedded object were not appearing in the HTML output. Now they are!
- Fixed the usage line to reflect that -H is not a legal option.
- Windows Metafiles were given an extension of ".meta". That has been changed to ".wmf".
- The Mac version failed to find html-trans, html-map when the input file was not in the same folder.
- Nested lists were not working properly. How did I miss that one :?>
Bugs fixed in 2.0.1
- RTF files created without a leading /pard caused aborts
- Graphics within a HOT text area caused failures instead of generating IMG links
- Anchor names and Hot Text links were getting an extra ">" inserted.
- Footnotes incorrectly got a "#" at the anchor points.
- Footnotes reference marks were generated without any separating text or space. Should be generated as [1]
- filter did not understand \tql which is generated in FrameMaker RTF output. This has been added to reader.c and rtf.h in the source directory. Eventually, these changes will be incoporated in an official distribution of the RTF package. (Binary versions of rtftohtml contain the fix)
- FrameMaker RTF assumes that \pard implies \plain - MS Word for the Mac appears to handle it that way, so I have updated the filter.
Bugs not fixed and non-bugs, annoyances etc.
- Outline, Shadow and Dotted Underline formatting are not available on Word for Windows. Because of this, the html-trans that I supply MUST be modified for PC users. I am hoping that some fine Windows user will modify html-trans and send me a copy, or a pointer to one.
PBMPLUS Bug
I also ran into a bug in picttoppm. The fix is supplied below:
diff -c picttoppm.c picttoppm.old.c
*** picttoppm.c Sat Jul 31 08:56:32 1993
--- picttoppm.old.c Mon Jul 19 20:24:37 1993
***************
*** 1081,1094 ****
pm_error("no memory for colour table");
for (i = 0; i <= ctSize; i++) {
! val = read_word();
/* seems that if we have a device colour table, the val is ! * invalid, so I assume we allocate up the list of colours.
*/
if (ctFlags & 0x8000)
val = i;
- if ((val ) > ctSize)
- pm_error("pixel value greater than colour table size");
colour_table[val].red = read_word();
colour_table[val].green = read_word(); colour_table[val].blue = read_word();
--- 1081,1093 ----
pm_error("no memory for colour table");
for (i = 0; i <= ctSize; i++) {
! if ((val = read_word()) > ctSize)
! pm_error("pixel value greater than colour table size");
/* seems that if we have a device colour table, the val is
! * always zero, so I assume we allocate up the list of colours.
*/
if (ctFlags & 0x8000)
val = i;
colour_table[val].red = read_word(); colour_table[val].green = read_word(); colour_table[val].blue = read_word();