Currently, NotSupportedEncryptionException is thrown.

Currently adding an Image content element with ImageSource instantiated with a PNG file format leads to NotSupportedException: 'Can not export other than Jpeg and Jpeg2000 and ImageQuality different than High', when exporting the document.

Support for adding PNG images and exporting to PDF should be implemented for PdfProcessing for .NET Standard scenario.

Support conversion of XPS documents to PDF using RadPdfProcessing.

Current implementation relies on valid cross-reference offsets in the PDF documents so that PDF objects are easily found and parsed. However, we can implement a mechanism for repairing documents with invalid cross-reference tables.

The attached project shows how to repair the simplest case of cross-reference table by using RepairDocumentWithSimpleCrossReferenceTable method.

Enable the customers to work with annotations of type Stamp

Currently, similar scenario may be achieved by converting Tiff images to BitmapSource and inserting them to RadFixedPage as images by using FixedContentEditor.
Note: A sample approach how to achieve such functionality is demonstrated in the Converting Multi-page TIFF Images to PDF KB article.

To bring RadPDFProcessing to the next level you should support XMP metadata. This would extremely help to use pdf files from RadPDFProcessing in digital workflows.

Reference: http://www.adobe.com/devnet/xmp.html

Currently, Standard fonts are exported always with StandardEncoding. This does not allow export of some special characters which do not fit in the first 255 glyph definitions in the font. Most of these characters are the ones with an accent such as "Eacute" glyph (É) which is with position number 303 in Times Roman font. The list of all standard fonts may be found in this documentation section:
https://docs.telerik.com/devtools/document-processing/libraries/radpdfprocessing/concepts/fonts#standard-fonts

This feature is currently supported only for .NET Framework and WPF .NET Core for Windows assemblies.

Add a PDF document validator to validate (before the import of the document) an existing PDF document.

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

Currently, PdfStreamWriter writes only PDF pages.

If we implement API for merging multiple pages or whole documents we would be able to preserve links between pages (which are currently being corrupted).

Merging whole documents would also allow preserving document properties (bookmarks, interactive forms, ...). For a more detailed list of the unsupported document properties you can refer to our documentation: https://docs.telerik.com/devtools/document-processing/libraries/radpdfprocessing/formats-and-conversion/pdf/pdfstreamwriter/features.

We may also implement API for adding initial document properties from some existing PDF file.

Add ability to create, import and modify layers (optional content) in a PDF document.

RadPdfProcessing currently supports interactive forms whose data is defined directly in the document. Add support for interactive forms based on the Adobe XML Forms Architecture (XFA). The entry is defined inside the interactive forms dictionary and refers to an XML stream containing the information of the form. More information is available on page 722 from Pdf Reference, version 1.7.
Updates:
November 2024
From PDF 2.0 (ISO 32000-2) the XFA forms are depreciated. For this reason, we are changing our plans and declining this item, but we will provide import-export support to avoid losing existing XFA content. Please, subscribe to the following public item: PdfProcessing: Add support for XFA fields import-export.

When exporting a document with the .NET Framework implementation, only subsets of the used fonts are embedded in the document. 

This is currently not available in the Silverlight implementation, and it most probably won't be available in the .NET Standard implementation, as the current implementation is dependent on the WPF font classes.

Provide API to plug similar logic when using different platforms as well.
This item wil handle the TrueType OpenType Font format. For the Compact Font Format (CFF) please follow: Export subset of Compact Font Format (CFF) fonts for platforms different than .NET Framework

Implement Find methods which enable the users to search for a concrete string/content/text in a Pdf document (RadFixedDocument).

Currently, when registering *.otf font file with FontsRepository.RegisterFont method an exception is thrown during the font creation. 

WORKAROUND:  The font file may be converted to TTF format (*.ttf) which is successfully registered. This conversion may be achieved with FontForge by opening the font file and then choosing File -> Generate Fonts -> TrueType -> Generate. More information on FontForge program may be found here: https://fontforge.github.io/en-US/

At this point, the import logic cannot automatically repair such documents and a NullReferenceException is thrown while reading them. You could repair the invalid file using the project from the attachment.

It will be possible to add an SVG element in a RadFixedPage so that it can be exported to PDF via the RadPdfProcessing library.

Export should take into account JavaScript and produce PDF similar to the original page.