Some customers need to export a single page of the PDF document to plain text. Expose such a possibility so the customers don't need to export the whole document.

Stencil color has to be preserved for images with ImageSource when ImageMask property set to true. Not preserving it results in wrong colors (for instance the image may be visualized as a black rectangle).

Available in R1 2019 Official Release Version.

The tj operator is responsible for drawing text content. When such operator is left empty, the import throws NullReferenceException because of the missing operands.

Available in LIB Version 2018.3.1022.

This operator modifies the current clipping path by intersecting it with the current path, using the even-odd rule to determine which regions lie inside the clipping path.

Available in R3 2018 SP1 release.

 This is content stream operator that is used to close, fill and then stroke a PDF path geometry.

Available in R3 2018 SP1 release.

This type of fields is currently not supported: https://feedback.telerik.com/Project/184/Feedback/Details/249205 . However, the fields can be skipped and the other content can be imported without throwing an exception.

Fix available in R3 2018 SP1 release.

When the string contained in a PdfHexString instance is empty, invoking ToString() leads to IndexOutOfRangeException.

Available in R3 2018 SP1 release version.

A font descriptor can be used by several fonts. However, when first a TrueType font is imported, later trying to import a Cid font leads to InvalidCastException with the message: "Unable to cast object of type 'Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Elements.Fonts.FontDescriptor' to type 'Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Elements.Fonts.CidFontDescriptor'."

Fix available in R3 2018 SP1 release.

The hierarchical document structure is a means to describe the PDF document structure, which is currently not supported. See 10.6.1 Structure Hierarchy on 856 page of the PDF specification for details.
This document structure is an alternative to the standard PDF structure and most non-Adobe software does not support it.

The document might have been created with Adobe software like Adobe LiveCycle Designer. Very often the document contains some fallback text in the standard PDF structure like:
"Please wait... If this message is not eventually replaced by the proper contents of the document, your PDF viewer may not be able to display this type of document."
"The document you are trying to load requires Adobe Reader 8 or higher. You may not have the Adobe Reader installed or your viewing environment may not be properly configured to use Adobe Reader. For information on how to install Adobe Reader and configure your viewing environment please see  http://www.adobe.com/go/pdf_forms_configure."
"For the best experience, open this PDF portfolio in Acrobat X, Reader X, or later."

CMYK color may be set using SCN, scn, K and k operators.

Available support for import of CMYK colors in R3 2018 Official Release.

In this case, we should use a default alpha source value which is the opacity source.

The signature field preserves information about the time of signing through the TimeOfSigning property of Signature.Properties. However, the DateTime object doesn't keep info about the time zone the document has been signed in. Some customers need to obtain this information.

While signing a document in Adobe Reader, the users can lock the document fields from editing. Expose a similar functionality.

The feature is described by the FieldMDP transform method, described on page 736 from the Pdf Reference 1.7

This happens only in cases when the Radio flag is not set and there are multiple widgets with different "ON" state names.

The issue may be reproduced by opening the attached PDF in Adobe Reader. Although the viewer initially shows the characters correctly, when you start typing in the TextBox, the umlaut/diacritics characters get corrupted. In other PDF viewers, the umlaut characters are handled correctly, so the issue seems to related to concrete Adobe Reader encoding handling implementation. The diacritic characters are handled incorrectly in other viewers as well (e.g. Chrome).

For details: https://www.adobe.com/devnet-docs/acrobatetk/tools/DigSig/Acrobat_DigitalSignatures_in_PDF.pdf

This feature is a must have for every business or enterprise!



Available in R2 2017 Release

For instance, we may implement WritePageAsync method in addition to the existing WritePage method. This is a similar scenario as in System.IO.StreamWriter class which has WriteLine and WriteLineAsync methods.

Add ability to create, import and modify layers (optional content) in a PDF document.

The exception is reproduced only with specific custom fonts and is thrown by the ComputeSubset() method of the GlyphTypeface class with the following message: "file does not conform to the expected file format specification". However, we can handle the exception and export the font data using the base class.

Fix available in LIB Version 2018.2.828.

The exception is thrown by System.Linq.Enumerable.Max method during the CidSet calculations.

Fix available in LIB Version 2018.2.730.