Version 4.0.427 (21-Jan-2003)

The following issues have been resolved in this build:

• The evaluation version brands all published outputs. Text is randomly selected and replaced with the words "AuthorIT Evaluation". If the text selected to be replaced contains a paragraph mark or graphic, the substitution no longer happens.
• When publishing Word output, cross reference page numbers and mini table of contents links were not "hot" (i.e. the link didn't work with the mouse). This was caused by "\h" switch in the published HYPERTEXT field incorrectly containing a space. The switch was incorrectly formatted as "\ h" not "\h".
• When publishing Word output, tables were not using the indent of the preceding paragraph.
• When publishing Word output, a Hypertext link object that pointed to a single URL had an extra space added after the URL under some circumstances.
• When publishing to HTML, "popup" style hypertext links were missing the "type" parameter in the "script" class. This caused the HTML to fail W3C validation. These popup style links are now defined correctly, and validate.
• When importing from another library, File objects that contained embedded graphics did not import.
• Some Topic objects that have been imported from Word documents retained formatting that was not mapped to a Style object. When publishing to Word, an error occured in function CharStyleRemove.
• Some Topic objects that have been imported from Word documents retained margin note type fields. When publishing to Word, the publisher would hang.
• When importing from another library, Index Entry objects that contain references to multiple Topic objects with the same name (and where these Topic Objects were not being imported, but one with the same name already existed in the library) caused an error

  Error 3022

  "The changes you requested to the table were not successful because they would create duplicate values in the index, primary key, or relationship. Change the data in the field or fields that contain duplicate data, remove the index, or redefine the index to permit duplicate entries and try again."

  Now if multiple Topic objects with the same name are referenced by an imported Index Entry object, and they aren't being imported, a single reference is created instead.

• Performing a searching beginning with the pipe character (|) caused an error. The pipe character has a logical meaning (OR) within the search. A meaningful dialog now displays informing of this. To search for the pipe character as a literal, include it within quotes. I.e. you could search for "File | Open" within quotes.
• The View Output button didn't work on some JavaHelp and Oracle Help for Java installations. This occured when the JavaHelp or Oracle Help for Java was not installed (or was incorrectly installed) on the client computer. The new install now includes these files automatically.
• Upgrading a version 3.2 library to version 4.0 with the Desktop version failed to start the AuthorIT Administrator automatically. The library could still be opened with the administrator and upgraded.
• Upgrading any property on an Embedded-type File Template caused all File objects based on that template to lose their embedded graphics.
• When publishing Word output, there were problems with some non-English Word Templates. An incorrect assumption was being made that certain fields would contain the text MERGEFIELD. This resulted in "Bookmark not found" errors within the published output.
• Creating a Topic with the Windows Help | Display and Contents | Help Window field set to (auto) caused problems when publishing to WinHelp. This is the default setting for a new Topic not based on a Template. If (auto) is selected then the Media object "Main" is used for WinHelp and "Normal Section" for other formats.
• Making a change to a Template that had an Objects based on it that were checked-out failed to work. The change now works and the new object has the modified template reapplied on check-in.
• When creating HTML Help files, every second one was twice as big as it should have been. They are now all the proper size.
• When publishing Word output, if the header or footer in the Word template contained text much of the published output would end up in the offending header or footer. Text in the headers and footers are now cleared automatically.
• When publishing any HTML output HTM files would appear in random directories (and be lost from the output). Files were incorrectly being created "in the current directory" rather than in the publishing directory.
• When publishing, errors occured in the publishing log that a style didn't exist. The style was marked to not appear in that output. (i.e. When publishing to Word errors that the style "HTML Only" didn't exist).
• When pasting a picture into a Topic, or importing a picture into your library, the default Word caption was being set to the name of the File object. The default Word caption is now blank.
• When importing a document that had blank lines with a heading style (that caused a new Topic to begin) the text following the heading style would be lost. For example: