Implement import of documents containing Type 3 fonts.

Loading a document that contains big images could lead to OutOfMemory exception.

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.

They are used by the page and the XObjects drawn on it and deal with the overlaying of the colors. These groups are described on page 556 of PdfReference 1.7. 

Add PrintPreview dialog visualizing the way the document is going to be printed.

Bitonal image scaling algorithms which improve the readability of bitonal, black and white images. Due to the lack of colors within the palette of 1-bit black and white images, they become splotchy and distorted when zoomed in or out

Dialog for inputting the password should be implemented in order to be able to decrypt the file content.

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

Guidelines of how to provide a custom implementation of the JPXDecode filter can be found in the Customize Rendering section of the documentation and a sample implementation can be found in the SDK examples.

Import documents that use this type of encryption. Currently, a handled NotSupportedEncryptionException is thrown while importing such a document and it cannot be opened in RadPdfViewer.

Available in R1 2018 Official Release version.

In Adobe and Foxit readers, the user can draw different shapes, which are later saved as images in the document.

Add built-in localization for the UI control and its tooltips. Currently they can be localized by expanding the XAML of RadPdfViewerToolBar and adding the required resources to the code.

The feature was implemented for Q2 2014.

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. 

XObejcts with indirect reference to an image are not rendered.

Images hosted inside multiple Form XObjects are not rendered.

Support for images used as brush.

The fix will be available in our official release Q1 2016.

Available in R2 2017 Release

Add UI for adding comments and ability to save them. Comments are represented in the document model as text annotations (annotations with Subtype Text). 

Scanned image is not visible with the new engine