By specification the explicit destinations define a required page property. However, some documents contain definition for destinations with null page value, which causes an ArgumentNullException on import.

Handle the case where the catalog starts with value other than 0

When importing an embedded Type 1 Font with custom encoding an InvalidCastException is thrown.

This exception corrupts the whole document import. Instead, we should provide Exception handling mechanism which allows the user to import the rest of the content.

More information is available in the Pdf Reference 1.7. Page 442 lists all predefined CMaps that should be imported and exported as PdfName objects. At this point, trying to import a document with such encoding, a NotSupportedException is thrown with message Encoding type is not supported.

Currently Type0Font class has CMap that can only be Identity-H. The Identity-V is a vertical version of Identity−H. The mapping is the same as for Identity−H.

After a PDF document is imported, decoding large images with a CCITTFaxDecode filter leads to OutOfMemoryException.

When importing color space defined as an external resource name, a NotSupportedColorSpaceException: 'CS0 color space is not supported.' is thrown.

NullReferenceException is thrown when importing a PDF document containing InlineImage with missing parameters

The EI keyword defines an operator for ending the image data. When the stream contains the same sequence, the parser treats that as an end of the image data. As a result, the image and the following content cannot be properly parsed and there is missing content when the document is visualized.

When importing document with predefined ToUnicode CMaps (e.g. Identity-H), an InvalidCastException is thrown with cause: 

Unable to cast object of type 'Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Types.PdfName' to type 'Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Elements.CMaps.ToUnicodeCMap'.

Currently this exception crashes the whole PDF document import. Instead we should simply skip the unsupported Action and import the rest of the PDF content correctly.

When importing a document containing an invalid PDF object dictionary key an exception is thrown.

 

Exception when merging file that contains notdef characters with PdfStreamWriter

For example, importing URI Action with invalid mailto URL scheme - mailto:***@***.**(E-mail), throws UriFormatException: 'Invalid URI: The hostname could not be parsed.'

System.ArgumentException when setting a password to a document with form fields

This is reproducible with specific PDF files which use custom Encoding for the fonts of the field widgets. 

WORKAROUND: Change the font of VariableContentWidgets before editing the field value. You should additionally call RecalculateContent() method of these widgets if the value of their corresponding fields is not edited. The following method may be used for changing the font of all existing widgets in the document:

private static void FixEncodingIssues(RadFixedDocument document)
{
    foreach(Annotation annotation in document.Annotations)
    {
        VariableContentWidget widget = annotation as VariableContentWidget;

        if(widget != null)
        {
            widget.TextProperties.Font = FontsRepository.Helvetica;
        }
    }
}

Currently Type0Font class has CMap that can only be Identity-H.

According to the specification, the startfref keyword must be followed by the offset the xref table start on, defined on a new line. Some documents, however, have both entries defined on the same line, which leads to InvalidOperationException with message "Stack empty" while importing. Make sure this case is handled in PdfProcessing as well.

This is not a valid scenario, but Adobe Acrobat handles it and we should too.