2008.2 Release

Fixed Issues

Defect Number Description Workaround Status
WWEP2514

FrameMaker: Unresolved links in certain foreign language documents

Index is generated as garbled characters and changing the Encoding and the Locale doesn't have any effect in the output for index. Please see the attached sample.

None.

Fixed.
WWEP2609

WebWorks Help 5.0: Two anchors (pound signs) breaks context-sensitive references to subtopics on a page

Changes to address security and bookmark issues in WWHelp 5.0 result in situations which browsers do not scroll to the appropriate paragraph in a displayed page.

None.

Fixed.
WWEP2620

FrameMaker: Some filename markers are not being recognized

Filename markers immediately following an anchored frame are not recognized. Instead, WW substitutes a generic filename based on the project name.

Invalid

Invalid
WWEP2621

Word: Bookmark not created when heading follows a page break

When a heading follows a page break, ePublisher Express is not picking up the heading when creating the PDF bookmarks. This is not an issue for headings following a section break.

None.

Fixed.
WWEP2622

Word: Bookmarks don't link to anything if landscape page exists

When a Word document contains portrait and landscape pages, PDF bookmarks exist but don't link to correct destinations. If I remove the landscape pages or change their orientation to portrait, bookmarks are created correctly. This is not an issue when I create PDFs directly in Acrobat.

None.

Fixed.
WWEP2623

ePublisher documentation reports WebDAV implementation

The ePublisher platform does not support WebDAV deployment at this time.

None.

Fixed.
WWEP2624

FrameMaker: Adapter may not resolve cross-references within text insets

Customer has documents with many text insets. Those insets have cross-references to other documents in the project. Those links are not resolved in the output.

In the MIF, the path to the referenced document is not relative to the copied file in the Data folder, but rather it is relative to the original document location. So, the file is not found and the link is not resolved.

PARTIAL WORKAROUND:

Place all text insets and FrameMaker documents within the same directory. Other layouts are possible.

Fixed.
WWEP2630

Some Helper applications are loooong outdated

With 2008.1 the following Helper apps are installed:

  1. Oracle Help 4.2.0 BETA from Dec 26, 2005 - the current release is 4.2.7 from May, 4, 2004.
  2. Java Help 2.0_02 - the current release is 2.0_05.

Manually update the correct files in the "Helpers" directory.

Fixed.
WWEP2631

Formatting in variables not converted correctly in some cases

In version 2008.1, we found that the formatting tags defined in variables are not converted correctly. For example, if the value of a variable is defined as "Microsoft<Superscript>®<Default Font> Windows<Superscript>®", in the converted HTML help, the variable is displayed as "Microsoft® Windows®", with the registered trademark ® symbols displayed as regular text, instead of superscript characters.

None.

Fixed.
WWEP2632

WebWorks Help 5.0: Fix for browsers "back/forward" behavior breaks topic links to specific document locations

In version 2008.1, changes implemented to support the correct function of browser Back/Forward buttons in FireFox with WebWorks Help 5.0 can trigger page reloads which reset all viewed pages to the top of the page.

Comment out all calls to:

WWHFrame.WWHHelp.mCheckHashTimeoutID = setTimeout...

in an override for file:

Formats\WebWorks Help 5.0\Files\wwhdata\common\wwhpagef.js

Fixed.
WWEP2633

Fatal error in Conditional Expressions dialog

This was in ePub Pro 20396. I have a project with documents which contain expressions. If I view the Expressions dialog and click in a blank area of the expressions list, I get an unrecoverable error. So, if expressions exist in a project, you can't click on a blank entry in the list box or you get this error:

Exception: System.NullReferenceException Object reference not set to an instance of an object.

None.

Fixed.
WWEP2634

Word: Links inside images do not always work

I have some hyperlink in the attached document and these images are inside a table and any of these links are not working after the generation.

None.

Fixed.
WWEP2635

FrameMaker: Disconnected text flows on body pages get ignored

ePublisher is unable to make a complete copy of the original FM document, and so only the first page of the file is converted to HTML output.

Connect text flows and manually insert page breaks.

Fixed.
WWEP2636

Style Report incorrectly lists non-existant style overrides

This situation occurs when conditions show up in generated output and the Style Report fails to distinguish between the application of a condition and style block overrides.

None.

Fixed.
WWEP2644

FrameMaker: [Error] Unable to create WIF document

FrameMaker source documents which make use of "Combined Fonts" may fail in circumstances where ePublisher does not properly map FrameRoman font ranges.

None.

Fixed.
WWEP2654

FrameMaker: Image maps failing with marker only text boxes

Image maps from FrameMaker work fine if the text boxes contain read-able text. However, if a user attempts to create an image map without introducing visible text, then the content is "optimized" away and the marker value is dropped.

None.

Fixed.
WWEP2659

WebWorks Help 5.0: Problem with viewing highlighted text on WebWorks Help

Current method for highlighting search results in IE can result in highlight colors which match the source text as well as font size/style alternations.

None.

Fixed.
WWEP2660

WebWorks Help 5.0: TOC collapses and then re-expands

Closing TOC entries in WebWorks Help 5.0 with TOC synchronization and accessibility both enabled can result in a "studder" effect. Any closed folder immediately reopen.

PARTIAL WORKAROUND:

Disable accessibility.

Fixed.
WWEP2661

AutoMap: AutoMap email notification does not attach log file

AutoMap is configured to email me and attach the log. However, the email says:

The job has successfully completed. Unable to attach file.

None.

Fixed.
WWEP2669

DITA: Ditamap scan not recognizing nested <topicrefs>

My ditamap contains nested topicrefs. When I generate output (HTML Help) via OTK 1.4, the TOC reflects the nested structure perfectly. For example, a top-level topicref in the map becomes a "book" in the CHM's TOC pane; any "child" (i.e. nested) topicrefs become child topics of that book.

However, when I add the ditamap to a WebWorks master project and scan the map file, parent and child topicrefs in the map are tagged with the same style (i.e. Heading 1). If I generate a CHM (or any other output format, for that matter), the TOC does not reflect the hierarchy in the ditamap.

This behavior is not global for the ditamap--some parent-child topicrefs get translated to "book"-"child topic" in the TOC. However, there seems to be no rhyme nor reason, and as I stated, the problem is not with the ditamap, since it generates as expected via the OTK.

None. Fix involves correct a defect in the DITA-OT "topicmerge.xsl".

Fixed.
WWEP2671

DITA: DITA attributes with multiple, whitespace delimited values not processed correctly

As per the DITA language specification, we can assign multiple values for an attribute. For example, <dt otherprops="abc xyz">. It is given that multiple we have to use spaces to separate multiple attribute values. When I generate the online help, these spaces are concatenated with an underscore character (_). I tried using two help IDs for the same topic. I assigned two values to the otherprops attribute, but in the generated online topic IDs, these are concateneated with an underscore.

None.

Fixed.
WWEP2672

FrameMaker: GraphicStyle marker inside table, inside frame results in wrong WIF stylename

Testing confirms that we scan the style properly, but the generated WIF tags the <Frame> as <Frame stylename="Default"> instead of <Frame stylename="NoOutput">.

None.

Fixed.

ePublisher 2008

2008 Release