Toolkit Release Notes 5.5.2.16278
This release includes bug fixes and new features.
- Software Requirements
- Hardware Requirements
- Enhancements
- Bug Fixes
- Additional Solutions
- Known Bugs
- Installation and Getting Started
- API Reference
The following software is required to successfully use Toolkit.
Server
- Windows Server® 2008 (32- or 64-bit edition) 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
- 125 MB of RAM
- 25 MB of hard disk space (for application)
Desktop
- 125 MB of RAM
- 25 MB of hard disk space (for the application)
Enhancements
The TIFFToPDF method has two new parameters that may help some .tiff to .pdf file conversion issues:
- IgnoreCompression
You can choose to ignore the compression defined in the TIFF file, or use the default compression for the TIFF format instead. - IgnoreOrientation
You can choose to ignore the orientation defined in the TIFF file, or use the default orientation for the TIFF format instead.
Bug Fixes
The following bugs were resolved since Interim Release 5.5.1.16225 and Interim release 5.5.1.16195.
| ID # | Description | Resolution |
|---|---|---|
| 311 | PDF files created by iTextSharp can now be used by Toolkit. | After updates to the code base, the issue was resolved. |
| 2554 | Characters were cut off from bottom of the page when a footer Image was added. | After updates to the code base, the issue was resolved. |
3007 4832 | These file specific bugs related to CopyForm issues are resolved. | After updates to the code base, these issues were resolved. |
| 2585 | When using the ü character in a field with Webdings, the Monalisa glyph displays instead of the Webding glyph (a map of Europe). | Updated the code that handles Symbol font. |
| 4442 | When a field is created with Toolkit and the font property is set to "Arial", text manually typed into the field disappeared after moving to the next field. | After updates to the code base, the issue was resolved. |
| 4495 | File Specific: When a PDF was locked with a 128-bit encrypted user password, Toolkit could not open it using the password. | After updates to the code base, the issue was resolved. |
| 4507 | File specific: after using TIFFToPDF, the output PDF displays the error message "Insufficient data for an image" when opened with Acrobat Reader. | The new IgnoreCompression parameter for TIFFToPDF resolves this issue. |
| 4828 | File specific: A checkbox in the source file displayed as a circle with two lines in the output PDF. | After updates to the code base, the issue was resolved. |
| 10242 | When the file path for images included Japanese characters, ImageToPDF and TIFFToPDF conversions failed. | After updates to the code base, the issue was resolved. |
| 12483 | File specific: After using FlattenRemainingFormFields during conversion, the barcode was missing in the output PDF. | After updates to the code base, the issue was resolved. |
| 12669 | File specific; using Microsoft IIS: During conversion, bookmarks caused a stackoverflow exception. | The recursion function that handles bookmarks was updated. |
Additional Solutions
These occurrences may happen when Toolkit is working as expected.
| ID # | Incident | What to do |
|---|---|---|
| 4533 | When using the StitchPDF method to stitch a PDF with populated fields, the data in the fields is missing in the output file. | The stitching process does not transfer form fields. When stitching a PDF with populated fields, flatten the form fields by setting Flag -998 when using SetFormFieldData, and call FlattenRemainingFormFields before calling StitchPDF. |
Known Bugs
When a bug is fixed, it is moved to the Bug Fixes table.
NOTE: Even if a workaround exists, the bug may be fixed in a later release.
| ID # | Known Issue | Workaround |
|---|---|---|
| 2566 | When BarWidthReduction is used to reduce the width of a barcode in the input file, the width of the barcode in the output PDF does not change. | No resolution at this time. |
| 2627 2879 3664 | When digitally signing a PDF containing compressed cross-reference streams, the output file is corrupt. Cause: After a PDF compresses a cross-reference stream, subsequent cross-references must be compressed as well. At this time, Toolkit does not support writing out compressed object streams. | No resolution for this file at this time. |
| 2962 | When StichPDF is used to stitch pages to a PDF with different-sized pages, the CPU run at 90%, and takes a very long time to finish. Cause: The resource replacement code could be optimized when stitching different-sized pages. An enhancement request has been submitted for this. | No resolution for this file at this time. |
| 3082 | When using Barcode.Symbology with the values 125.126,127,128, no barcode is created in the output PDF. | At this time, use alternate symbologies. |
| 3249 | When iteratively merging or form filling the same file from a sample application, Toolkit's memory appears to progressively accumulate. Cause: This is not a memory leak; over successive runs, the memory accumulates proportionately and then stabilizes. This is due to a best fit memory issue with .NET string marshaling and Toolkit's native code interface. An enhancement request has been submitted to improve the string marshaling behavior. | No resolution for this application at this time. |
| 3953 | When the Arial Unicode MS fonts are not embedded, the fields in the output have truncated text. Cause: The rendering supplies a substitute font, and uses metrics that truncate the last character. | Select Use Local Fonts, and embed the fonts used in the original document. |
| 4128 | After a PDF with a logo was merged, the output PDF displays corrupt characters and returns an error "Cannot extract the embedded font". Cause: The PDF has Type 3 fonts which use XObject image resources that are not copied over. | Set DisableFontCache = true. |
| 4618 | After using AddField to add a text form field, the output file size is larger than expected. | No resolution at this time. |
| 4620 | After using AddLogo, the output file displays an error message when opened with Acrobat Version 8 or earlier. | No resolution at this time. |
| 4689 | After calling ParseDataStream, in the output PDF, the data in fields is misaligned and extends outside the field. | No resolution at this time. |
| 4813 | When using StitchPDF to stitch multiple pages, each page is rotated slightly more than the preceding page in the output PDF. | No resolution at this time. |
| 10171 | Microsoft Windows Server 2012 R2 only: When AddLogo is used before CopyForm, Toolkit fails with a c0000005 error (memory address access violation). | Use MergeFile instead of CopyForm. |
| 11884 | After using MergeFile with two PDFs that contain bookmarks, in the output PDF the bookmarks of one file are nested under the bookmarks of the other file, instead of displaying at the root level. | No resolution at this time. |
| 11885 | When using an evaluation key for Toolkit, watermarks are not displayed on all pages. | No resolution at this time. |
| 12427 | When fonts associated with end-user-defined characters (EUDCs) are used in the source file, after using PrintText or SetFont, the text does not display in the output PDF. | No resolution at this time. |
| 12475 | When using PrintImage to add .WMF images to a PDF, the images in the output PDF do not display as expected. | Convert the .WMF image to .PNG or .JPG before using Toolkit. |
| 12784 | When using AddBookmarks and CopyForm(i,i) to copy the source file one page at a time, the output PDF contains duplicate bookmarks that do not function. | Use CopyForm and process all pages at one time. |
2645 | File specific bugs. | Please contact customer support for further information. |
Documentation
The ActivePDF Help documents are not shipped with the product. The manuals listed below are posted online so that the most current and accurate information is always available.
Installation and Getting Started
Installation instructions and general startup information is available in the Legacy documentation section for Toolkit Installation Guide at:
https://www.activepdf.com/support/documentlinks.
API Reference
API information is available in the Legacy documentation section for Toolkit API Reference Guide at:
https://www.activepdf.com/support/documentlinks.