With the current implementation, it takes seconds to decode and display JPEG with several megapixels (for example size 4000 x 2000 pixels). The memory consumption when decoding such images also needs improvements.

Workaround: Custom DctDecode filter may be implemented and registered in RadPdfViewer. The attached demo shows how this may be achieved by using BitmapImage class to decode the JPEG images instead of the default RadPdfViewer's JpegDecoder.

Parsing the wrong content stream in RadPdfViewer results in handled exception and this way some of the PDF content is missing when rendering the page.

The text appears disordered due to wrong calculations of the glyph geometries.

The issue is caused by memory optimization that requires loading page content only for the visible pages. 

In order to fix the issue and still benefit from the memory optimization, we are introducing setter in FixedDocumentPresenterBase VisiblePages property. Now this property needs to be set each time the visible pages are changing in custom presenter implementation. Setting VisiblePages ensures that all visible pages content will be loaded correctly.

Even small documents (~30 kb) containing images encoded with CCITTFaxDecode filter can take about 10 seconds to be opened. In 2014 Q1 SP1 such documents load faster.

Implement import and export of content with Type0Font with GBK-EUC-H encoding.

"Save As" is common functionality in most of the popular PDF Viewers. It should save the currently loaded document to a file.

Workaround: Currently there is SDK demonstrating how to add such functionality: https://github.com/telerik/xaml-sdk/tree/master/PdfViewer/PdfViewerCustomSaveCommand

Available in R3 2017 Official Release Version.

Currently, when we parse inline image dictionaries we rely on the assumption that the colorspace will be PdfName. However, there are files with complex colorspaces that are PdfArray and InvalidCastException is thrown. All the content after this exception is lost and not visualized by RadPdfViewer.

When graphic state uses stroking text rendering mode, the glyphs are visualized with bigger stroke thickness than the expected one.

Available in LIB Version 2018.2.521.

The exception is thrown during "Put" operator execution.

Default DctDecode implementation uses System.Windows.Media.Imaging.BitmapImage in order to get the image pixels. However, when the image uses some complex colorspace (for instance Separation based on CMYK) the BitmapImage is initialized with a different format and we use System.Windows.Media.Imaging.FormatConvertedBitmap in order to get the pixels in CMYK colorspace. There seems to be some issue with these calculations as the resulting image has incorrect pixels.

WORKAROUND: You may inherit DctDecode class in order to implement custom decoder and call DecodeWithJpegDecoder method from the base class as mentioned in the note of this documentation article:

http://docs.telerik.com/devtools/wpf/controls/radpdfviewer/customization-and-extensibility/customize-pdf-rendering

A sample implementation of these custom decoder may be seen below:

public class CustomDctDecode : DctDecode
{
    public override byte[] Decode(PdfObject decodedObject, byte[] inputData, DecodeParameters parms)
    {
        return DecodeWithJpegDecoder(inputData);
    }
}

When a page is rotated its annotations are not positioned correctly. 

The Ò symbol is not found in the encoding as is rendered as a ".notdef" glyph.

Available in LIB Version 2017.3.1127.

Enable the customers to directly save the document inside PdfViewer to a file or a stream.

Available in LIB Version 2017.3.1225.

The exception is thrown when the RadioButtonField options array contains nested arrays instead of string values.

Fix available in LIB Version 2018.1.312.

The file contains the following:
68.637 604.561 455.981 -107.996 re
72.237 604.561 l
S
Instead of the more usual
68.637 604.561 455.981 -107.996 re
S
72.237 604.561 l
S
Both are valid but the first seems to create a problem.

Fix available in LIB Version 2018.1.319.

RadPdfViewer's AcroForm property ViewersShouldRecalculateWidgetAppearances should be respected when being set to true. In this case, RadPdfViewer should recalculate all widget appearances and this would resolve the issue with empty form field widgets after opening such PDF document.