The CID font may define a description of the glyph widths. By specification, the widths can be defined in two ways - with start and end CID codes or with and an array of CID codes. However, the current implementation supports only CID arrays as direct property and not as an indirect object. This leads to incorrectly imported glyph widths and text positioning issues.

To reproduce:

  doc.Pages[0].CropBox = new Rect(150, 150, doc.Pages[0].Size.Width - 30, doc.Pages[0].Size.Height - 30);

RadPdfViewer partially supports CCITTFaxDecode (that is basically TIFF). There are some limitations that are not supported at this stage like EncodedByteAlign = true or Group 3, 2-D encoding.

When a pdf/a compliant document is opened in Adobe, there is a bar saying that the document is compliant with the standard. Expose such functionality in PdfViewer as well.

The current implementation relies on valid cross-reference table offsets in the PDF documents so that PDF objects are easily found and parsed. However, a mechanism for importing documents with invalid cross-reference table offsets may be implemented.

The attached project shows how to repair such documents.

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

An implementation of JPXDecoder should be created to allow the decompression of data encoded using the wavelet-based JPEG2000 standard.

I am using the PDFViewer control in a VisualStudio VB.NET application. The PDF is not showing all the details as it appears in Adobe PDF Reader. In particular, the text is not showing up (but is highlighted when selected) and there is gray shading that is not visible. See attached sample file. Please advise.

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.

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.

A remote go-to action is similar to an ordinary go-to action but jumps to a destination in another PDF file instead of the current file.

To reproduce:

Open a large document and start scrolling fast. 

The pages a blank when scrolling and are rendered after scrolling stops.

When the Interactive Form Fields are in read-only mode, the user should not be able to change the value of the field. The associated Form Field widgets should not interact with the user, e.g. they should not respond to mouse clicks or change their appearance in response to mouse motions.

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

Please refer to the attached sample screenshot demonstrating how the document look in Adobe and in RadPdfViewer.

Currently, RadPdfViewer uses WPF DrawingContext class for drawing page elements to a Canvas.  When PDF page has many content elements (usually geometries) drawing the page may be time-consuming and freezes the UI. 

Instead, we should consider implementing another approach for rendering the content asynchronously which would improve the user experience. 

Some files when opened with PdfViewer will throw a KeyNotFoundException which will be handled. Parts of the text in the file might or might not be missing.

When the file has an annotation with a destination and this destination is missing from the destinations (Dests) collection of the catalogue, KeyNotFoundException is thrown when you try to scroll to the page where the annotation is located. A better behavior would be for nothing to happen when trying to click on the annotation leading to the destination.