Currently, for .NET Framework scenarios, this could be achieved using RadPdfViewer's WPF control ThumbnailFactory class. Sample code may be seen at this forum post: http://www.telerik.com/forums/pdf-thumbnail-returns-transparent-images#jO33X-E8Cki_qLh_KsToWg.
The feature should be implemented for .NET Standard as well.
The method should create deep copy of the current page.
The NotImplementedException is thrown while getting the color from unsupported color space (for example ICC). This exception occurs during the import of shading patterns with gradient stops using this color space or during the import of tiling pattern with underlying color space. Available in R2 2018 Official Release Version.
Implement API for adding document outline (a.k.a bookmarks).
As some other decoders, JBIG2 may also handle different parameters in order to correctly decode the stream. Currently, decode parameters are not supported for this decoder.
This may cause either big distance between some glyphs, or overlapping glyphs.
Currently this operator is interpreted correctly only for Pattern colorspace. It also partially supports the rest of the colorspaces from R1 2018. Available in R2 2018 Official Release Version.
The "g" and "G" operators are used for setting color with a single component. Available in R1 2017 Release
For details: https://www.adobe.com/devnet-docs/acrobatetk/tools/DigSig/Acrobat_DigitalSignatures_in_PDF.pdf This feature is a must have for every business or enterprise! Available in R2 2017 Release
OutOfMemoryException is thrown when generating PDF with many pages each of which contains images, as all of the document model data is in-memory. The issue is fixed with the new PdfStreamWriter API. As an example, you may see the attached demo to the following feedback item: https://feedback.telerik.com/Project/184/Feedback/Details/213503-pdfprocessing-optimize-pdfstreamwriter-cache-in-order-to-reduce-memory-when-writ Available in LIB version: 2017.1.320
Implement Find methods which enable the users to search for a concrete string/content/text in a Pdf document (RadFixedDocument).
Add support for ToUnicode CMap stream. A side effect of not supporting it is the following: exporting PDF document which, for example, contains German umlauts, to plain text, leads to wrong characters in the resulting text. As possible workaround, the PdfFormatProvider instance of RadPdfViewer can be used to import the document. For example:FormatProviderSettings settings =
new
FormatProviderSettings(ReadingMode.OnDemand);
PdfFormatProvider pdfViewerFormatProvider =
new
PdfFormatProvider(stream, settings);
RadFixedDocument document = pdfViewerFormatProvider.Import();
TextFormatProvider textFormatProvider =
new
TextFormatProvider();
String text = textFormatProvider.Export(document);
This would allow creating documents with preferences such us HideToolbar, HideMenubar, FitWindow, PrintScaling and all other viewer preferences specified in PDF format specification.
When images are added to the document with non-default quality (PdfExportSettings.ImageQuality different that ImageQuality.High) , they are re-encoded, which uses a lot of memory and may cause OutOfMemoryException for large images. Workaround (works when inserting big JPEG images): In this case ImageQuality.High may be used and RadPdfProcessing will decode only the image headers to insert the image into the PDF file. As image pixels are not decoded with ImageQuality.High, there will be no OutOfMemoryException.
Measuring big paragraphs is time consuming and may be optimized.
Currently every text fragment is exported by specifying all its properties. When there are many fragments one after another we may skip specifying the properties for every single fragment. This will improve both memory and time consumption performance.
Highlight annotations appear as highlights in the text of a document. When opened, they display a pop-up window containing the text of the associated note.
The issue is reproducible only with nested tables - tables positioned inside some other table cell. When using simple tables the text is always wrapped and rendered correctly. This may be used as a workaround for scenarios which allow replacing nested tables with simple ones.