A NullReferenceException is thrown when trying to clone the Signature property of the field.

Available in LIB Version 2018.1.312.

Although this is not a valid postscript scenario we should not throw exceptions and we should instead skip the invalid dictionary end characters.

Fix available in LIB Version 2018.1.312.

In business or enterprises there is more and more demand for PDF/A-3.

In Germany it is Zugferd for hybrid invoices, in Brazil Nota Fiscal Eletronica 2.0, in France FACTUR-X.

Also for longterm preservation it is import to support PDF/A-3.

If I would be the PM of this library this would be my number one priority!

These images are defined directly in the PDF page content stream with BI and EI operators. Currently InvalidCastException is thrown when document with such images is imported.

Available in R1 2018 SP2 release version.

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

Available in R1 2018 SP2 version.

Encryption Algorithm 4 is implemented for R1 2018 official release. This includes all encryptions except AES 256 which is related to Encryption Algorithm 5. For AES 256 you may vote and follow this feedback item:
https://feedback.telerik.com/Project/184/Feedback/Details/240154-pdfprocessing-support-encryption-algorithm-5-with-aes-256

Currently RadPdfProcessing allows setting standard fonts using FontsRepository static properties.

However, in RadWordsProcessing font can be set only by specifying FontFamily, FontWeight and FontStyle. As there is no way to set standard fonts this way, API users cannot benefit from using these fonts which may help them achieve smaller PDF size as standard fonts may not be embedded. The same applies to RadSpreadhProcessing as well.

According to PDF specification, the resources used for the dynamic appearance of fields are defined globally in AcroForm "DR" PDF property. However, there are some invalid documents which define these resources locally in the field node which causes exception in PdfProcessing implementation. As there are several such documents we may consider handling such scenario instead of throwing the exception.

Available in R3 2017 SP1 Official Release.

Some PDF files have an additional content added before the file header (before %PDF-1.4 for example). This additional content makes all byte offsets in the document invalid, which causes the format provider to throw an exception.

At this point, to import a similar document it should be pre-processed so the content before the version header is removed before importing it.

This would allow to disallow some rows from splitting.

If a PDF with a TextBoxField is created with a corresponding Widget, the text is actually long enough to be broken in more than one line and AllowScroll is set to true, upon opening the file in Adobe, the text is not visible. The field actually does have an appearance which can be seen upon inspection of the document but for some reason it is not visualized.

Another issue seems to be a different manifestation of the same problem: When the text is long and AllowScroll is false, the text will be visible, but will be misplaced. The issue is caused by the length of the text because the same field with a shorter text that can fit in the widget's rectangle will be displayed correctly. 

The field name should be preserved on an import-export scenario. However, in some cases when the field name contains non-ASCII characters then the field name is exported with different value compared to the imported one.

Fix available in LIB Version 2017.3.1009.

Currently, there is no way to know when a new page is created when content "overflows" to the next page 

This event may be needed in order to generate the header and footer based on the currently generated content. In simple header/footer scenarios, however, this event may not be needed and the headers and footers may be drawn after all pages are generated as described in the comments below.

Implement the Exponential Interpolation Function in PdfProcessing. Currently, NotSupportedFunctionTypeException is thrown with a message "Function type 2 is not supported."

Implement Viewer related properties in PdfProcessing in order to enable the users to set PrintScaling, PrintClip, and other properties which are written in the Pdf Format specification as Interactive Features. 

ViewerPreferences are written a document's catalog. Check p.577 from pdf reference format specification, version 1.7

When trying to create documents simultaneously from different threads (in concurrent scenario), different exceptions are thrown: 

- NullReferenceException in Telerik.Windows.Documents.Core.Fonts.OpenType.OpenTypeFontSource.ReadTableData[T](UInt32 tag, ReadTableFormatDelegate`1 readTableDelegate) method, 

- OverflowException in Telerik.Windows.Documents.Core.Fonts.OpenType.Tables.CMapFormat4Table.Read(OpenTypeFontReader reader) method.


Available in LIB version: 2017.2.814

System.Uri constructor throws UriFormatException when the text is some http address.

Available in LIB Version 2017.2.814.

The PDF format includes a general multimedia framework allowing users to insert and play/visualize different media types. The feature is described on page 755 from PDF Reference 1.7.

The current implementation expects the widths to be integer values and InvalidCastException is thrown when a real number is parsed.

Workaround: If the scenario allows, the PdfStreamWriter may be used instead of PdfFormatProvider. More information may be found in the following documentation article:
http://docs.telerik.com/devtools/document-processing/libraries/radpdfprocessing/formats-and-conversion/pdf/pdfstreamwriter/overview

Available in LIB Version 2017.2.731.

This is because PdfProcessing does not export Annotation Flags and this way all annotations has Print flag set to false.

Available in Release Version R2 2017 SP1.