DocConverter Release Notes 2015 R2.0

This software release for ActivePDF DocConverter 2015 R2.0  (2015.2.0.17047) includes new features and bug fixes.

Software Requirements

The following software is required to successfully use DocConverter.

  • Windows Server® 2008 (32- or 64-bit edition) OR

  • Windows Server® 2008 R2 OR

  • Windows Server® 2012R2

  • Microsoft® .NET Framework 4.0 (If it is not detected, it will be installed automatically)

Optional Software Applications

  • (Recommended) Default converter: LibreOffice® 4.2 (if not installed, DocConverter can install it automatically)

  • Install these applications if you want to use their native converters instead of the default converter:

    • Microsoft Word®, Excel®, PowerPoint®, Visio®, Publisher (DocConverter currently supports Versions 2007, 2010, or 2013)

    • Fuji® Xerox® DocuWorks™ Viewer Light 7.2.1 minimum

    • Corel® WordPerfect®, X5, X6, and X7 (WordPerfect 15, 16, 17)

Note: Install the applications before installing DocConverter.

Hardware Requirements

The minimum hardware requirements for DocConverter are:

  • 512 MB of RAM

  • 150 MB of hard disk space (for application)


  • Additional hard disk space is needed to meet the requirements of the installed applications and the volume of files being processed.

  • ActivePDF does not officially support running DocConverter in a Remote Desktop Services (RDS), Terminal Services or Citrix® environment.

New Features

  • You can now add the current datetime to a text stamp setting used by Watch Folders.

To add the current datetime into the text stamp, wrap the standard .NET Custom Date and Time Format String with <d> and </d> tags.
For more details, refer to the .NET Framework Custom Date and Time Format String article:

For more information about text stamping, see Adding Stamps to PDF Conversions in the DocConverter API Reference manual.

  • New behavior for email conversions: Attachments to .msg files can now retain their filenames after conversion (API only).
    When calling ConvertToPDF, if you pass an empty string into the outputPDF parameter, the original filename for the attachment will be used.

  • New behavior for Microsoft Excel conversions: When converting Excel files, if the Excel sheet has a user-defined print area, DocConverter now uses that layout in the output PDF.

Bug Fixes

The following bugs were resolved since the last release.

ID #




File specific: After conversion, the .tiff image in the output file was a mirror image of the original.

This issue was resolved after a general update to the code base.


File specific: After converting the PDFs to PowerPoint or Microsoft Word, bullets and tables in the output files did not display correctly.

This issue was resolved after a general update to the code base.


When an Excel file with multiple sheets was converted, if the active page was blank, DocConverter moved the file to the error folder.

DocConverter now checks for content on other pages and performs the conversion if content is found.


File specific: An end-user defined Chinese character in the input file was missing in the output PDF.

This issue was resolved after a general update to the code base.


File specific: After converting the .TIFF file, when the output PDF is opened an error is returned: "insufficient data for an image".

This issue was resolved after a general update to the code base.


When Microsoft Word files have images added using both the IncludePicture field code and by copy and pasting in the images, after conversion, the output PDF does not always include all the images.

A change made to code related to how the looping of an inline shape is handled resolved this issue.


When using FromPDF_ToExcel with ConvertFromPDF, the commas used in the numbering were not included in the output Excel file.

The ToExcelAutoDetectSeparatorsproperty can be used to include commas.


File specific: Barcode fonts are installed and used in this .rtf file, but after conversion to PDF, text displayed instead of the barcode.

Windows is not allowing access to the fonts during conversion.


Microsoft Publisher: Files cannot be converted using the Print option.

A change to code related to default Settings resolved this issue.


File specific: When DocConverter attempted to convert this .txt file, the conversion failed.

A change to the code relating to limits for drawing characters resolved this issue.


When specifying an OutputDirectory without also specifying a NewDocumentName, the output file was placed in the same location as the input file.

This issue was resolved with a code edit.


When Greek characters where used in a PostScript filename, the conversion failed.

The files are now assigned a temporary name until the conversion process is completed, and now files convert as expected.


When a source file included text with a hyperlink, and the PrintToPDF enumerator was used with UseIIntelligentPDF turned off, the text displayed in the output file contained an error message about a missing reference.

A change to the code relating to how hyperlinks are handled resolved this issue.


File specific: When DocConverter attempted to convert this PostScript file, the conversion failed, returning an error message that it was unable to find the LTArial font.

A change to the code relating to how the font path is set resolved this issue.


When a multi-page .tif file was dropped in the Watch Folder, only the first page of the file was converted.

This issue was resolved after a general update to the code base.


If the source file included parenthesis in the filename, when PDFPrint was used, the conversion failed.

The code was updated to handle files names that include parenthesis.


When using DocConverter under an evaluation license, stamping failed.

The evaluation version now includes stamping.


File specific: When this .msg file that includes unclosed HTML tags was converted, the HTML tags were displayed in the output PDF.

The code was updated to handle invalid HTML code, and the email now converts as expected.


COM: When performing remote conversions, if the source file included "#" or "%" in the filename, the conversion failed.

The code was updated to escape any special characters encountered in filenames, and now files convert as expected.


File specific: When attempting to convert the files to PDF/A 2-B, the conversion failed.

This issue was resolved after a general update to the code base.


Even though the ConvertFromPDF function was set to PDF/A, Format had to also be set to PDF/A and called in order to create a PDF/A output.

This issue was resolved with a code edit.

Note: For a list of Known Bugs, see:

Installation instructions and API Reference

Installation and API information is available in the DocConverter Legacy documentation section at: