DocConverter Release Notes 5.4.1.14032
DocConverter 2010 R4.1 Release Notes Build 5.4.1.14032
This article contains the release notes for ActivePDF DocConverter Enterprise 2010 R4.1 (Build 5.4.1.14032).
- Operating System Requirements
- Hardware Requirements
- Additional Software Requirements
- Bug Fixes
- Known Issues
Operating System Requirements
The following software is required for full use of DocConverter Enterprise.
- Windows Server® 2003, x86 or x64, OR
- Windows Server® 2008, x86 or x64
Hardware Requirements
The following are minimum hardware requirements for DocConverter Enterprise.
- 512 MB of RAM
- 90 MB of Disk Space (for application)
Additional Software Requirements
The following are additional software requirements for DocConverter Enterprise.
- Microsoft Word®,Excel®,PowerPoint® (2003 minimum, 2007 or 2010 recommended)
- Microsoft® .NET Framework 3.5, or higher (if not detected, will be installed automatically)
- LibreOffice 3.6.2 (installed automatically by DocConverter; recommended this version be used for best results)
Note: ActivePDF does not support running DocConverter Enterprise in Remote Desktop Services (Microsoft® Windows Server 2008) or Citrix environments. DocConverter Enterprise can be run in a Terminal Services (Microsoft® Windows Server 2003 and prior) environment only in Administrative mode.
Bug Fixes
The following table lists fixes made in DocConverter Enterprise R4.1.
ID # | Description | Resolution |
29 | Text missing after conversion. | The LibreOffice converter resolved the issue. |
3013 | .DOC file won't convert properly with PDFPrint. | A PostScript subsystem of DocConverter was updated. |
3045 | DocConverter hangs indefinitely when attempting to convert a Microsoft Office document that contains macros. | DocConverter was updated to improve handling of macros in Microsoft Word. |
3096 | When the PostScript file is converted with DocConverter Enterprise, bold characters are lighter than when using Adobe. | A PostScript subsystem of DocConverter was updated. |
3164 | PDF to Text does not convert text in white, hidden font. | Text is now converted from PDF, regardless of color and hidden quality. |
3359 | A Microsoft Word document converted via the Microsoft Office converter shows "There is a problem Reading this Document (40)." | A PostScript subsystem of DocConverter was updated. |
3594 | .PPT file under Windows 2003 32-bit English with French Regional settings fails to convert when the PDFPrint option is used. | DocConverter was updated to handle French Regional settings. |
3597 | FILE SPECIFIC: File generates Error -10270. | A shared Toolkit component was updated. |
3650 | Bookmarks are stripped when Compatibility Level is set to 1.5. | Fixed the manner in which bookmarks were transferred. |
Known Issues
The following table lists known issues with DocConverter Enterprise R4.1. When a known issue is fixed, it is moved to the Bug Fixes table. Note: The availability of a workaround does not imply that a particular issue will not be fixed.
ID # | Issue | Workaround |
2914 | .DOC fails to convert to PDF/A. | PDF/A-1b does not support transparent images. Documents containing transparent images were failing on conversion to PDF/A. Therefore, PDF/A-2b support has been introduced to accommodate these files. A workaround was added to optionally force DocConverter to use the PDF/A-2b standard, which supports transparent images. Note: Using this workaround, all PDF/A outputs generated will adhere to PDF/A-2b standard, rather than to PDF/A-1b. See Conversion of Word and Powerpoint Using PDFExport Could Result in a PDF/A Error for workaround details. |
2919 | Selecting the Personal hot folders option for How to Handle Sub Directories in the CUI results in the error, "Invalid value for HowToHandleSubDirectories[3]." | The option for Personal hot folders is not functional. Select a different option for Watch Folders. See Invalid Value for HowToHandleSubDirectories when Configuring Watch Folders for workaround details. |
3304 | Excel files with workbook protection are failing due to an issue within Microsoft Office 2007 and Microsoft Office 2010. | Upgrading Microsoft Office 2007 to Service Pack 3 (SP3) resolves this issue. See Converting Workbook Protected Excel Files Using MS Office 2007 Converter Results in Errors for workaround details. |