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.
This is Unicode (UTF-16BE) encoding for the Adobe-GB1 character collection; contains mappings for all characters in the GB18030-2000 character set. Described on page 443 in Pdf Reference 1.7.
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.
The issue is reproducible only on Windows XP. On newer versions of windows, the images are rendered as expected. WORKAROUND: You may try implementing custom filter that handles the CMYK scenario. How to implement custom DCTDecode filter is described in this documentation article: https://docs.telerik.com/devtools/winforms/pdfviewer/customize-and-extensibility/customize-pdf-rendering
Add a navigation pane to view attachments under a pdf. it is possible to have various attachments under a pdf file, such has another pdf. For example, when converting an email with attachments, the resulting pdf has attachments. RadPdfViewer has no possibility to view those right now. Could be an event and let the calling program manage this. For our needs, I would like an event, because our attached files are also pdfs, so I could open them in a new tab
Overprinting is option in the GraphicState that allows combining colors when drawing one object above another object. It is briefly described on page 284 and page 565 in PdfReference 1.7. However, the result of overprinting is device dependent and there are no strict instructions how the result should look like. This feature also includes support for the different blending modes.
The events should provide information as to when a page is about to be rendered and when it is displayed in the control.
This functionality should be similar to the one provided by Adobe.
According to PDF format specification, there are three valid encoding name values (MacRomanEncoding, MacExpertEncoding and WinAnsiEncoding). There are documents that instead of skipping the optional Encoding property, are writing invalid /NULL name value in the font dictionary. Currently, in this invalid document scenario RadPdfViewer throws and catches Exception and this results in missing text content. We may handle this invalid document scenario by ignoring the invalid Encoding value.