Unsupported annotations are rendered on top of other content. When there is a form field that appears inside the annotation, it cannot be clicked or interacted with as the annotation is capturing the mouse gestures.

WPF controls are used to visualize the form fields in PdfViewer. However, these controls inherit the background defined in the PdfViewer's theme instead of a background of the form field control. This leads to wrong visualization mostly in the dark themes as the content inside the form field might get unreadable.

RadPdfViewer does not read image resources defined in Form XObject elements.

Documents containing large images are slow to decompress and decode.

The character is visualized as '3'. The same issue is also reproducible when the content is copied from Adobe.

Loading document containing link with no destination leads to ArgumentNullException in PdfElementToFixedElementTranslator.CreateDestination method.

When importing a document with empty pages collection an ArgumentNullException: 'Value cannot be null.
Parameter name: page', is thrown, which leads to application crash.

Workaround: Import the document using the PdfProcessing library and add an empty page:

 

The CIDFont dictionary may contain an array, describing the widths of the glyphs. If the width has a negative value an ArgumentException: 'Width and Height must be non-negative.', is thrown when the document is imported in RadPdfViewer, which leads to application crash.

By specification, the InteractiveForm fields can have the same name if they are descendants of a common ancestor. Such fields are different representations of the same underlying field; they should differ only in properties that specify their visual appearance. When such a document is imported an ArgumentException: 'An item with the same key has already been added.' is thrown, which leads to non-editable fields in RadPdfViewer.

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.

The offset of the CropBox is not respected and is always treated as 0.

Workaround: Import the document with PdfProcessing, change the CropBox offsets of the pages to 0, export the modified document and then import it in PdfViewer.

Telerik.Windows.Zip.InvalidDataException for unknown (0xAD) compression method is thrown for some object streams.

We should implement the logic for getting character codes from Unicode when using CFFFontSource.
Workaround: The font may be changed by creating a similar font with FontsRepository.TryCreateFont(...) method.

In the PDF document model, the Annotation appearances refer to an external resource using the Resources dictionary. When the Resources dictionary is defined as an Indirect Object an InvalidCastException: 'Unable to cast object of type 'Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Types.PdfDictionary' to type 'Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Elements.DocumentStructure.PdfResource'.', is thrown.

Workaround for documents generated with PdfProcessing: When drawing lines using the FixedContentEditor the IsFilled graphic property should be set to false:

RadFixedDocument document = new RadFixedDocument();

Rect rect = new Rect(0, 0, 50, 50);
FixedContentEditor editor = new FixedContentEditor(document.Pages.AddPage());
editor.GraphicProperties.IsFilled = false;
editor.GraphicProperties.IsStroked = true;

editor.Position.Translate(50, 50);
editor.GraphicProperties.StrokeColor = new RgbColor(255, 0, 0);
editor.DrawText("Lines");
editor.DrawLine(rect.TopLeft, rect.TopRight);
editor.DrawLine(rect.TopRight, rect.BottomRight);
editor.DrawLine(rect.BottomRight, rect.BottomLeft);
editor.DrawLine(rect.BottomLeft, rect.TopLeft);

This is reproducible for images with FlateDecode and predictor value in the range between 10 and 15. As an example you may take a look at the DecodeParms property in the following image PDF dictionary:

<< /BitsPerComponent 8 /ColorSpace /DeviceRGB /DecodeParms << /BitsPerComponent 8 /Colors 3 /Columns 1024 /Predictor 15 >> /Filter /FlateDecode /Height 2868 /Subtype /Image /Type /XObject /Width 1024 /Length 1236707 >>

When importing document containing a destination which points to invalid page reference, KeyNotFoundException is thrown.

This is caused by an incorrect order of applying the TextMatrix and the glyph stroking operation.

OverflowException is thrown while importing document using Helvetica font with custom encoding.

When a PDF document contains images compressed with CCITTFaxDecode with applied BlackIs1 parameter, black color is visualized as white and white as black.