The exception is thrown during "Put" operator execution.
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.
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.
Currently, all images are decoded and preserved in RGBA format (32 bits for each pixel). However, there are files that optimize their images by preserving them with 1 bit for each pixel. In WPF we may create monochrome System.Windows.Media.ImageSource that would optimize the performance and memory consumption when rendering such images. Available in R1 2018 Official Release Version.
FixedDocumentPresenter could be TemplateBound to PDFViewer's Background property. Available in LIB version: 2016.3.1205
When there is no ToUnicode CMap, the text from the Simple Font instance should be extracted by mapping the glyph name to its corresponding charcode according to Adobe Glyph List. Additionally, the Differences array should be included in these calculations when there is custom encoding. The current implementation of RadPdfViewer makes ToString to the original char id byte value which leads to wrong characters.
The instances are kept in GeometryRenderer cache and each time the content stream is parsed new PathGeometry instances are added to GeometyRenderer store Dictionary field. Available in R1 2017 Official Release Version.
"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.
This is not quite a valid PDF file scenario according to PDF file specification. However, we may try handling it in order to show the correct number of pages. When the kid is of type Pages, it should be added to the pages traversal recursion only the first time it is met.
Implement import and export of content with Type0Font with GBK-EUC-H encoding.
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.
Default RadPdfViewer presenters load image sources async which allows to render the rest PDF content faster. However, FixedDocumentSinglePagePresenter loads images syncrhonously and all page content is rendered right after all images on the page are loaded.
Setting DocumentSource throws NullReferenceException when PdfViewer is hosted in ElementHost. When setting the DocumentSource, the Application.Dispatcher is used, but in Winforms app, the Application is not instantiated. Steps to reproduce: 1. Host PdfViewer in ElementHost in a WinForms application 2. Set the DocumentSource property 3. Run Expected: The document is opened Actual: NullReferenceException is thrown Workaround: the document could be set to the Document property of PdfViewer. Or instead hosting the PdfViewer for WPF in ElementHost, use WinForms version of the control.
Tint transformation function is used to transform Device N color in Alternate colorspace.
By using "Auto Detect Hyperlink" functionality RadPdfViewer should detect URLs and email addresses and turn them into hyperlinks. For instance if the PDF file contains text http://www.telerik.com/ this text should become a hyperlink.
Represents Free text PDF content. Since LIB Version 2017.3.925 annotations of type FreeText can be visualized.
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.
There is a similar question in FAQ for FontForge (https://fontforge.github.io/faq.html#mingliu) where it is described that kaiu.ttf (and probably mingliu.ttf) font does not store the correct outlines and its outlines need special treatment in order to be rendered correctly. The Chinese glyphs are rendered wrong in RadPdfViewer as well. However, Adobe Reader, FoxitReader and ChromeViewer render the glyphs correctly.
Currently, the disabling of the scrolling functionalities in PdfViewer is pretty tricky. Expose an API that allows users to control this functionality easier (hiding the scroll bars, disabling horizontal and/or vertical scrolling). A sample of how the scrolling could be completely disabled is attached to this item.
The text appears disordered due to wrong calculations of the glyph geometries.