2009.3 Release
| Defect Number | Description | Workaround | Status |
|
EPUB1 |
ePublisher: Installer rollback (after install cancel) fails to removew .wez expanded directories ePublisher may fail to execute clean up commands if the installation process fails for unknown reasons. |
Manually remove any remaining files after cancelling installation. |
Fixed |
|
EPUB27 |
ePublisher: Create default directories and expand evalution materials only once Presently, ePublisher Express and Pro expand evalution materials into a user's My Documents folder any time the programs are launched and the evaluation materials are not present. |
None. |
Fixed |
|
EPUB105 |
ePublisher: Generation fails when output directory set to drive root ePublisher attempts to manage output directory names when the name matched the current target's name. However, the code does not correctly handle this update when teh output folder is set to the root directory of a Windows drive. |
Generate output to a non-root directory and then deploy to the target root directory. |
Fixed |
|
EPUB184 |
WebWorks Help 5.0: Invalid syntax in use for <noframes> elements Syntax was originally correct in ePublisher 2009.1. It was changed for 2009.2 due to insufficient review of feedback from a browser based validation tool. For 2009.3, the syntax was reverted to the 2009.1 markup. |
Modify the necessary frameset .htm files. |
Fixed. |
|
EPUB198 |
ePublisher: Enable "safe" Pro upgrades Provides a smooth upgrade path for Pro users migrating custom code or production projects to newer releases of the ePublisher platform. |
None. |
Fixed. |
|
EPUB204 |
Formats: Image width/height emitted even when option disabled The Style Designer provides an option to suppress width/height settings in generated output. However, the XSL code failed to honor this request for most formats. |
Support assisted customers as necessary. |
Fixed |
|
EPUB222 |
AutoMap: AutoMap reports success despite "duplicate and apply settings" failures This defect was previously addressed in an earlier ePublisher release (2009.1 or 2009.2). |
Invalid |
Invalid |
|
EPUB224 |
FrameMaker 9: Scan fails to update include/exclude status and displayed icons ePublisher correctly captures FrameMaker 9 include/exclude settings from source books during initial scans. However, when those same books are manually scan later on, the include/exclude settings are not updated properly. |
Manually configure include/exclude settings in ePublisher. |
Fixed |
|
EPUB229 |
Wiki - MediaWiki: SVG kills MediaWiki client MediaWiki SVG support is limited out-of-box. ePublisher now rasterizes SVG images. |
Disable SVG support in the Style Designer. |
Fixed |
|
EPUB230 |
ePublisher AutoMap: Missing resource string for Confluence deployment This issue is cosmetic only. |
> None. |
Fixed |
|
EPUB232 |
ePublisher Express: Express installer still says "Format Settings" which should be change to "Target Settings" |
None. |
Fixed |
|
EPUB236 |
Adobe FrameMaker: Cross-references broken in FrameMaker when PDF generation is enabled ePublisher made use of the same cross-reference map for both the designated target and PDF output. As a result, PDFs made use of an incorrect link map. |
Support assisted customers as necessary. |
Fixed |
|
EPUB237 |
Licensing: Licensing fails when MachineID exception is thrown ePublisher licensing may fail when determining machine IDs due to system misconfiguration. |
Support assisted customers as necessary. |
Fixed |
|
EPUB239 |
ePublisher: Duplicate source files are ignored during project generation This issue only occurs when the same document appears more than once within an ePublisher projects. Normally, ePublisher allows such duplication. However, optimizations made to address FrameMaker 9 include/exclude file processing resulted in this defect. |
Support assisted customers as necessary. |
Fixed |
|
EPUB240 |
Licensing: ePublisher unregisters itself and removes keys if server unavailable By design, ePublisher licensing should always preserve working keys on the users system whenever possible. However, due to a combination of system interactions, it is possible for ePublisher to remove active keys and unregister an installation without notifying the user. This issue will appear the generation log as: Unable to process document .... No valid license found for ... support. |
Corrective steps have been taken on WebWorks.com servers to prevent customers from experiencing this issue. If you do experience this issue, you may update your active license keys by selecting Help > License Keys... and clicking on the Update button. |
Fixed |
|
EPUB242 |
ePublisher: Rescan after missing file corrections Once a "missing file" has been relocated by the user, ePublisher should re-scan the file to look for nested books, etc. |
None. |
Fixed |
|
EPUB243 |
JavaHelp: Context-sensitive links fail due to invalid alias entries in map file Work was done to address missing link destinations in the JavaHelp target. However, the change failed to consider link alias markup limitations. |
Please contact Support to address this issue. |
Fixed |
|
EPUB244 |
Microsoft HTML Help 1.x: HTML Help should automatically remap PUA characters Symbolic fonts, such as Webdings and Wingdings, will not display correctly unless they are downmapped from the standard PUA (Private Use Area). |
Please contact Support to address this issue. |
Fixed |
|
EPUB245 |
Unified PDF Production: PDF from WIF via XSL-FO This is a new feature of ePublisher 2009.3 which enables users to define custom formatting for PDF targets through the ePublisher Style Designer. |
None. |
Fixed |
|
EPUB248 |
ePublisher: Workflow broken - Data folder no longer shared between Express and AutoMap Changes were made in ePublisher 2009.1 and 2009.2 to ensure that temporary files are always processed on a user's locale machine. This was done to support environments where ePublisher projects reside on network shares. However, the implementation failed to keep the Data folder location consistent for users who convert project with AutoMap and then troubleshoot them with Express. |
None. |
Fixed |
|
EPUB249 |
DITA: ePublisher should allow for lax link validation DITA content is expected to pass strict link validation when processed by ePublisher. This behavior does not match what is expected by experienced DITA-OT users. Users would like an option for ePublisher to process DITA maps with unresolved links. |
Please contact Support to address this issue. |
Fixed |
|
EPUB250 |
DITA: DITA output not preserving topic filenames For DITA sources, ePublisher automatically emits Filename and Pathname markers in converted files to enable generation of output files which match input topic files one-to-one. Changes made to support DITA's @copy-of attribute in ePublisher 2009.1 broke this functionality. |
Please contact Support to address this issue. |
Fixed |
|
EPUB251 |
Microsoft Word: Duplicate and Apply fails due to WWWORD.DLL load issue On certain systems, ePublisher is unable to export Word source documents due to add-in or template runtime configurations. |
Please contact Support to address this issue. |
Fixed |
|
EPUB252 |
Microsoft Word: Transit menu throwing "index out of range" exception on startup Primarily, this issue only presents itself on Word XP systems. |
Please contact Support to address this issue. |
Fixed |
|
EPUB253 |
DITA: Cannot enable @toc=no for topicref Changes made to support @copy-to attributes in ePublisher 2009.1 prevented propigation of @toc attributes. |
None. |
Fixed |
|
EPUB254 |
ePublisher: Add feed reader to Start Page The ePublisher Start Page guides users to helpful resources and keeps them up-to-date with the latest information regarding the ePublisher platform. |
None. |
Fixed |
|
EPUB257 |
ePublisher: Create default directories and expand evalution materials only once Presently, ePublisher Express and Pro expand evalution materials into a user's My Documents folder any time the programs are launched and the evaluation materials are not present. |
None. |
Fixed |
|
EPUB258 |
FrameMaker: XREFs either fail in output or link to wrong file Due to defects in the FrameMaker 8 and 9 export functionality, we have introduced mechanisms to workaround these shortcomings. However, in doing so, our stategy can match links in circumstances where it should not. |
Please contact Support to address this issue. |
Fixed |
|
EPUB259 |
FrameMaker: Table borders do not match source document ePublisher fails to correctly translate all possible configurations of FrameMaker Table border style rules. |
Please contact Support to address this issue. |
Fixed |
|
EPUB260 |
WebWorks Help 5.0: Incorrect TOC margin display when configured to use right-to-left languages WebWorks Help TOC display renders incorrectly due to missing margin-right and padding-right values. |
Please contact Support to address this issue. |
Fixed |
|
EPUB261 |
ePublisher: Links broken in merged PDFs when viewed in a web browser Links which originated as cross document links fail in the merged PDF when the merged PDF is viewed in a web browser. |
None. |
Fixed |
|
EPUB262 |
ePublisher: Last selected deployment location should be auto-selected in Target Settings dialog Previous behavior was just plain annoying. |
Selected the desired target after exiting the Target Settings dialog. |
Fixed |
|
EPUB263 |
Eclipse Help: Add ability to configure manifest "Bundle-Version" via Target Settings The Eclipse runtime fails to refresh help content if the "Bundle-Version" setting is not incremented on successive deployments. |
Manually expand the .jar file, increment "Bundle-Version", and re-JAR.None. |
Fixed |
|
EPUB265 |
Sun JavaHelp 1.1.3 and 2.0: Topic processed/emitted twice in JavaHelp map Issue can lead to failed help compiles or incorrect behavior when navigation TOC or context-sensitive help links. |
None. |
Fixed |
|
EPUB267 |
Adobe FrameMaker: Tag equation frames in WIF This request came out of WebWorks RoundUp 2009. The capability allows users to perform custom processing on frame which are otherwise treated as standard images. |
None. |
Fixed |
|
EPUB268 |
Wiki - Confluence: Parser blocks broken in Confluence Content emitted into Confluence parser blocks failed to render properly due to an incorrect closing tag. |
None. |
Fixed |
|
EPUB269 |
Adobe FrameMaker: Avoid fatal exception in Frame adapter Rather than reporting failed communications with FrameMaker, ePublisher previously ceased processing and crashed. |
None. |
Fixed |
|
EPUB271 |
ePublisher Express: Improve handling of locked files during Stationery sync ePublisher Express (and AutoMap) previously failed if users attempted to synchronize an Express project which referenced locked files. |
None. |
Fixed |
|
EPUB272 |
DITA: Performance of XML adapter on large DITA maps is not acceptable ePublisher made use of XSL code which was non-performance in marking DITA elements with unique IDs. |
None. |
Fixed |
|
EPUB273 |
ePublisher AutoMap: AutoMap fails to resolve relative job document paths ePublisher AutoMap was resolving relative job document paths if an absolute path to the job file was provided. If a relative job file path was provided, all relative job document paths were unresolved. |
None. |
Fixed |
|
EPUB275 |
Adobe FrameMakerr: Scanned conditional expressions (Frame 8 & 9) failed to show in ePublisher ePublisher showed only a single conditional expression. Now, all current conditional expressions found in a FrameMaker document are scanned and displayed. |
None. |
Fixed |
|
EPUB276 |
Wiki - MediaWiki: MediaWiki client does not complete deployment The MediaWiki deployment client previously failed an entire deployment operation on the first upload error. |
None. |
Fixed |
|
EPUB277 |
ePublisher: Group PDF baggage file references incorrect The link map provided to the PDF merge operation provided incorrect values for referenced baggage files. |
None. |
Fixed |
|
EPUB278 |
Wiki - MediaWiki: Company info logo doesn't work in MediaWiki Markup was incorrect when the MediaWiki page template was processed. |
None. |
Fixed |
|
EPUB279 |
ePublisher: Installers should automatically uninstall previous versions ePublisher installers now remove auto-uninstall an existing product if it is version 2008.1 or later. If an earlier product is detected, e.g. 9.0, 9.1, 9.2, or 9.3, ePublisher will prompt to the user to manually uninstall the old version before proceeding. |
Manually uninstall previous ePublisher version. |
Fixed |
|
EPUB280 |
ePublisher: Enable linked target to enable PDF file sharing Users can request that ePublisher use PDF files generated by another ePublisher target in a particular target. When the current target is generated, the corresponding PDF target is converted first and the generated PDF files are copied into the current target. This feature can be used in conjunction with the existing PDF format or the new XSL-FO based PDF format. |
None. |
Fixed |
|
EPUB281 |
ePublisher AutoMap: Add conditional expression support for AutoMap jobs This feature is not available in the AutoMap UI. It is intended for user who script the creation of AutoMap job files. |
None. |
Fixed |
|
EPUB282 |
ePublisher Formats: Large project fails to complete during image processing The ePublisher image processing pipeline made use of XSL code geared for speed. Unfortunately, it used a large amount of memory. The code was altered to reduce the run-time footprint and speed image generation. |
None. |
Fixed |
|
EPUB283 |
ePublisher: Merged PDF links missing or not working when document generated with Acrobat 9 The ePublisher PDF merge code failed to account for Unicode encoded filename reference which are now generated by Acrobat 9 rather than classic PDF encoded filename references. |
Support assisted customers as necessary. |
Fixed |
|
EPUB285 |
DITA: Ensure all <colspace> elements include @colnum attributes Lack of @colnum attributes lead to PDF generation failures when using the DITA-OT's native PDF generation facility. |
Support assisted customers as necessary. |
Fixed |
|
EPUB286 |
Wiki - Confluence & MoinMoin: Unable to deploy to secure webservers The deployment clients for Confluence and MoinMoin did not accept SSL certificates provided by remote wiki servers. |
None. |
Fixed |

