Toolkit Release Notes 2016 R1.1


This software release for ActivePDF Toolkit 2016 R1.1 (Build 2016.1.1.17041) includes bug fixes.



Software Requirements


The following software is required to successfully use Toolkit.


Server



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

  • Windows Server® 2008 R2 OR

  • Windows Server® 2012 R2

  • Microsoft® .NET Framework is required to use Toolkit's .NET component
    (1.1 or 2.0 minimum — if .NET is not detected during installation, you are offered the option to have .NET installed for you.)


Desktop


(32- or 64-bit editions)



  • Microsoft Windows® 8.1; 8; 7; OR

  • Microsoft Windows VistaTM OR

  • Microsoft Windows XP®

  • Microsoft .NET Framework is required to use Toolkit's .NET component
    (1.1 or 2.0 minimum — if .NET is not detected during installation, you are offered the option to have .NET installed for you.)


Hardware Requirements


The minimum hardware requirements for Toolkit are:


Server and desktop



  • 125 MB of RAM

  • 25 MB of hard disk space (for application)


 


Bug Fixes


The following bugs were resolved since the last Toolkit release.




































ID #



Description



Resolution



13086



After inserting Japanese characters into a form field, the form field in the output PDF contains garbled characters.



The code was updated to resolve this issue.



13258



When GetTextWidth was called, it did not calculate the width of Japanese characters correctly.



The internal calculations for font width were updated, which resolved this issue.



13309



File specific: When CopyForm was used after calling FlattenRemainingFields, the form fields displayed question marks instead of the data.



Changes to how the Unicode characters were mapped resolved this issue.



13342



When PrintImage was used with a .png file, an error message displayed when opening the output PDF.



A correction to the code resolved this issue.



13511



File Specific:  When this file was used with MergeFile, Toolkit closed unexpectedly without displaying an error message.



Changes to the code base  resolved this issue and MergeFile now functions as expected.



Note: For a list of Known Bugs, see:


https://www.activepdf.com/support/kb-special/kb-bug-report/toolkit-known-bugs-2016-1-1


 


Installation and API Reference 


ActivePDF manuals are posted online so that the most current and accurate information is always available.


Installation and API information is available in the Legacy documentation section for Toolkit API Reference Guide at:


https://www.activepdf.com/support/documentlinks.