They are exported with the /EmbeddedFiles switch. This would allow adding external files to the PDF document.

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.

Implement importing and exporting the javascript actions associated with push button fields so that they can be executed when the exported document is opened with Adobe Acrobat. Javascript actions are also used by text fields for text validation (for instance for date input).

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

Add support for documents containing RTL (right-to-left) text.

Add support for a strikethrough property or strikethrough-related properties in the TextProperties class.

At this point, the justify alignment is not supported.
Note: When implementing this functionality, ensure that there an is appropriate public API for setting the text alignment to Justify

This would allow to encrypt documents only with Owner Password and not showing password dialog when disabling some PDF features permissions. The customer should be able to disable printing, text and graphic selection and extraction, page rotations and others. The full specification of all permission bits may be seen in Table 3.20 on page 124 in PdfReference 1.7. On page 120 in PdfReference 1.7 are described the User and Owner passwords.

This API should provide a method for removing all fields and widgets in the document and draw the default widget appearance in place of the removed widgets.

WORKAROUND: Sample implementation for flattening form fields may be seen in the FlattenFormFields method from the attached demo project.

According to PDF specification, all fonts should be embedded except from 14 Standard PDF fonts. This guarantees that the PDF file is self-contained and will be rendered successfully on different devices and operation systems.

However, some clients prefer not to embed fonts in order to reduce file size. That is why we may provide such API.

Currently, NotSupportedException is thrown when trying to import a document that uses Type 3 fonts.
Update: With Release R1 2021 the import of Type 3 fonts is already developed but the export is still not supported.

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.

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, 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.

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

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).