Version 4.0.433 (22-Apr-2003)

The following issues have been resolved in this build:

• When saving (or autosave kicks in) the Topic could flash to the top and back again.
• When importing, the first style that occured in your document was not recognized by the import rules.
• When importing Word documents:
  • Character styles within tables were not recognized.
  • Soft page breaks were not being removed from the Topic Text.
• Inserting a symbol left the cursor in the wrong location.
• When importing HTML Help projects:
  • If no HHC or HHK file is found in the general section, the files section is now checked.
  • Some files defined in the HHP appeared incorrectly in the log as "file not found".
• When importing HTML, sometimes imported text was truncated mid word for no apparent reason.
• When importing WinHelp:
  • Some footnotes could cause Topic Text to end up in the Heading field.
  • Map IDs are now imported.
  • Some links were importing incorrectly, with forward-slashes being incorrectly replaced with back-slashes.
• When creating the Cascading Style Sheet file (stylesheet.css):
  • The border-color definition for "all borders" is now defined before the individual borders. This is preferable for browsers that understand both syntaxes as declaring the border-color-top after the general border-color will cause the setting to be overridden. Early versions of Netscape only understand the border-color syntax.
  • Graphics associated with HTML bullets were ignored and not copied to the publishing folder. These files are now referenced correctly from the CSS and copied to the publishing folder for all HTML outputs. Oracle Help for Java still won't display these files correctly, for no reason we can discern.
  • Setting the background-repeat property to (none) in the style object didn't insert it into the CSS. The default in IE is to repeat causing images to repeat even when set not to. If the background-repeat property is set to (none) we now set the value as no-repeat in the CSS.
• When attempting to displaying variable usage for a Topic that had neither variable usage or assignments an error occured.
• Find and Replace now shows a "finished" dialog if nothing was found.
• If a hypertext link was also a spelling mistake, replacing the word caused the hypertext link to disappear.
• Inserting a File Object from the menu in the Book Editor lost the focus from the Book Editor.
• Inserting a File Object sometimes displayed the size incorrectly. The file was inserted correctly, just the size displayed was incorrect.
• File Objects inserted on one computer were unusable on another computer. Several unusual situations could cause this and the problem was eventually tracked down to the difference in LOCAL_ID on the two computers. For example, embedding a File Object with your local as English (U.S.) and then trying to publish from a computer with the local set to Russian would fail.
• Adding a new style (or changing the name of an existing one) didn't update the dropdown style lists correctly.
• Selecting a group of objects that are marked "check out" and selecting "don't check out" from the popup menu didn't work.
• The view command line function (that allows you to automate publishing jobs) was missing a quote after the Author-it path and Filename.
• When exporting to jet (using the export to jet command line parameters) the /compact parameter caused an error.
• Adding, modifying and deleting variable assignments now updates the search results. Previously, you needed to open a Topic (or reindex Topic Text relationships) to update the search index.
• Exporting a Jet library to SQL Server could display an error if there were large quantities of additional files attached to some objects.
• When publishing, mini table of contents would sometimes (incorrectly) list the same topic twice.
• When publishing to WinHelp output:
  • if a hollow square was being used for a bullet it showed (incorrectly) as a 'n' or 'q' instead. This was a bug in the WinHelp compiler where it incorrectly removed the WingDing font from its list of fonts in the mistaken belief that it wasn't being used. Dummy text inserted with the wingding style applied to fool the WinHelp compiler.
  • Table headings that immediately followed a Heading would appear in the non-scrolling area.
• When publishing HTML outputs:
  • Linked AVI files were not being copied to the publishing folder.
  • The handling of Related Topic group publishing has been speed up considerably.
  • The file name now uses the Object Key (not the Object ID) which ensures it will remain the same from one version to another.
  • Tables imported from Word could end up with borders 2/3 of a pixel wide. Most browsers would not display this. Borders are now rounded to the nearest pixel for all HTML formats.
• When publishing to HTML Help (CHM) output, incorrect table handling could cause the publisher to hang.
• When publishing to JavaHelp output:
  • Indexes were incorrect if the Topic description contained a colon (:)
  • Links to glossary terms were sometimes created incorrectly (or not at all).
• When publishing to Word output:
  • Several very large graphics within a single Topic could cause publishing to hang.
  • Fields now use the local language name for the various field types.
  • A Topic with no heading would still occur in the related topic group.
  • Page number references (in indexes, hypertext links etc) were being calculated while show hidden text was on, often resulting in incorrect numbers. Page numbers are now updated while hidden text is hidden and the page numbers are now correct.
  • An extra space was being inserted above Topics with the No Heading Template applied.
  • An extra space occured before the heading in some glossary headings and indexes.
  • Some styles in Word were displaying incorrectly in Word (i.e Normal + Font name + Bold...)
  • If a Microsoft Word Template exists in the ...Documents and Settings\user name\Application Data\Microsoft\Templates directory that has the same name as the Word template pointed to by the Book being published then Microsoft Word uses the wrong Template. This is by design for Microsoft Word. A warning is now added to the publishing log.
  • The words "Chapter 1" etc. were not displayed in the TOC even though the "add super heading" option was checked in the TOC Object.
  • Very small graphics that were being scaled down for Word caused errors. These errors now only appear in the publishing log.

The following new features have been added to this build:

• A report has been added to the Administrator that allows you to see what all external file references are. This should enable better management of external files. See AuthorIT Administrator > Reports > New Files Report