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:
Implement API for adding document outline (a.k.a bookmarks).
The CropBox is currently not supported by RadFixedPage class and is not preserved on an Import-Export scenario with PdfFormatProvider. CropBox is also not supported by PdfPageSource class and it is not preserved by using PdfStreamWriter as well. This property should be implemented in both scenarios.
This operator modifies the current clipping path by intersecting it with the current path, using the even-odd rule to determine which regions lie inside the clipping path. Available in R3 2018 SP1 release.
This is content stream operator that is used to close, fill and then stroke a PDF path geometry. Available in R3 2018 SP1 release.
CMYK color may be set using SCN, scn, K and k operators. Available support for import of CMYK colors in R3 2018 Official 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
Implemented import and export of IccBased, Indexed, Cmyk color spaces. Available in Q3 2015. Available in R2 2018 Official Release version.
This is content stream operator used for setting color in Device, CIE-based or Indexed color space. Available in R2 2018 Official Release version.
Currently, when writing RadFixedPage the page instance reference is cached, as well as its content resources (images and fonts). This cache is important as it allows to reuse pages, images and fonts without writing them multiple times in the result PDF document. However, it needs to be optimized in order to consume less memory. The attached demo shows how to create 2500 pages with big images (different image on each page). With the current version, this demo consumes about 3 GB memory which may lead to OutOfMemoryException. With the optimization that will be introduced in LIB version, the same demo will consume about 20 MB memory for writing this big PDF document. Available in LIB version: 2017.1.320
Currently, NotSupportedEncryptionException is thrown when PdfFileSource is initialized with an encrypted PDF file. Available in R2 2018 Official Release Version.
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.
Implement the "k" and "K" color operators, which sets the color in DeviceCMYK color space. Currently graphics with color set with these operators are imported with incorrect colors. Available in R2 2018 Official Release Version.
Support for forms. The feature is named 'Interactive forms' in the PDF specification. Main scenarios to consider: - Reading of the data in the forms. - Writing data to the forms. Available in R2 2017 Release
Encryption Algorithm 4 is implemented for R1 2018 official release. This includes all encryptions except AES 256 which is related to Encryption Algorithm 5. For AES 256 you may vote and follow this feedback item: https://feedback.telerik.com/Project/184/Feedback/Details/240154-pdfprocessing-support-encryption-algorithm-5-with-aes-256
Paint content stream operator ("Do" in PDF specification) currently draws only Image XObjects. We should implement support for Form XObjects. Available in R2 2017 Release
Currently, only images without transparency may be created with this class. Available in LIB version 2017.1.410.
This new API will not read/delete the existing PDF pages content and this would allow performance and memory efficient realization of the following scenarios: - Merge PDF document pages from different PDF files. - Split PDF document pages to separate PDF files. - Append/Prepend PDF content to existing PDF pages. Moreover, as this approach will not require reading/deleting existing PDF page content, it will not depend on complex PDF features and will depend only on the PDF file structure. This will allow processing of PDF documents which use less common PDF features which are currently not supported by the existing PdfProcessing API. Available in R1 2017 Release