Handle import of documents containing Simple fonts with names of entries in the Encoding`s Differences that are not part of the Adobe Glyph List.

According to the PDF Specification (9.10.2 Mapping Character Codes to Unicode Values) if the name is not part of the list: If these methods fail to produce a Unicode value, there is no way to determine what the character code represents.

When importing a document containing a single associated widget annotation merged into the field dictionary the field is skipped on import and an exception is thrown.

According to the PDF Specification: Field Dictionaries: Kids:

An array of indirect references to the immediate children of this field.
In a non-terminal field, the Kids array is required to refer to field dictionaries that are immediate descendants of this field. In a terminal field, the Kids array ordinarily must refer to one or more separate widget annotations that are associated with this field. However, if there is only one associated widget annotation, and its contents have been merged into the field dictionary, Kids must be omitted.

There are missing characters when importing documents containing Standard fonts with a Differences array defined in the Encoding, which contains characters that do not fit in the first 255 glyph definitions in the font. Most of these characters are the ones with an accent such as "ccaron" (č).

Inserting PNG ImageSource into a document and applying the document instance directly to the RadPdfViewer`s Document property (without exporting to stream) leads to a wrong image rendering.

Workaround: Export the document with the PdfFormatProvider:

MemoryStream ms = new MemoryStream();
PdfFormatProvider pdfFormatProvider = new PdfFormatProvider();
pdfFormatProvider.Export(radFixedDocument, ms);

PdfDocumentSource source = new PdfDocumentSource(ms, pdfViewer.DefaultImportSettings);
this.pdfViewer.DocumentSource = source;

The object definitions are split into several lines:

Creating a PdfViewer instance without adding it in the visual tree, leads to leaked document presenter instances when the TouchManager is enabled.

Workaround: Disable the TouchManager:

Telerik.Windows.Input.Touch.TouchManager.IsEnabled = false;

Currently, the PdfProcessing document model is providing support only for a single function in the Function entry.

According to the PDF Specification: Function: A 1-in, n-out function or an array of n 1-in, 1-out functions.

According to the PDF specification (Adobe® Portable Document Format Version 1.7):
Append a rectangle to the current path as a complete subpath, with lower-left corner (x, y) and dimensions width and height in user space.

The operation: 

x y width height re

An invalid case:

0 - 595 -842 re

This leads to an exception thrown: System.NullReferenceException: 'Object reference not set to an instance of an object.'