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.
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.
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.
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.
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.
The text appears disordered due to wrong calculations of the glyph geometries.
The slow performance when creating thumbnail is only reproducible with specific documents.
Document cannot be loaded because the Encrypt property is not set and is null.
The performance of loading the thumbnails is decreased with the removing of the cache in PdfViewer. Possible reason is that the pages are no longer loaded asynchronously. Steps to reproduce: - Open the SDK with the thumbnails for PDFViewer. - Notice that the load of the thumbnails is slow.
When printing a document with multiple pages, the pages that are not currently visible will be printed without content.
If the presenter is changed (for example, by pressing "Fit one full page to window" button) during the inertia of a scroll operation, NullRererenceException is thrown. Fix available in LIB Version 2017.2.627.
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.
All annotations are missing because ArgumentNullException is thrown while importing page annotations. The exception is handled and all non-annotation related pdf content is loaded successfully.