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.

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.

Implement Replace method(s) which enable the users to replace a concrete string/content/text in a Pdf document (RadFixedDocument).

Hello Telerik,

Last time we attempted this the <Viewbox> contents would not render and were empty upon xaml to pdf output. It would be great if you had this feature and we could move completely away from raster output to PDF for controls that contain Viewboxes. Otherwise we have really liked the PDF's created by the tool, the vector output is sharp as expected.

Thank you,

Patrick

Add support for movie annotations.

Add support for R16 color space

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

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

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.

This operator is used for drawing shading patterns.

PDF/UA (PDF/Universal Accessibility) is the informal name for ISO 14289, the International Standard for accessible PDF technology.

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.

Implement GetColor method for Indexed color space

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.

Support for validating signature fields signed with signatures that are encoded in ETSI.CAdES.detached encoding should be added.

Import/export and API for creating page ArtBox should be added.

When a document is imported the FontsRepository caches the created font instances for performance reasons. API should be provided for clearing the cached instances in order to reduce memory consumption.

We would like to search a PDF document for specific text and returns its position. We generate PDF reports using Telerik Reporting which contain placeholders that are replaced with images and text at run-time. It appears the logic has already been implemented, but the implementing classes (e.g., TextSearch, TextRecognizer) aren't accessible. Please consider making this capability available.

By specification when a form field is merged with the dictionary of the widget annotation, a Kids parameter can be existent if there are more than one widget annotations for that field. Support for importing such a fields should be added. 

These permissions are defined on a document level and apply permission handlers. The permission handlers are similar to the security handlers but do not require the document to be encrypted. They are also used to determine which objects are to be included in the digest calculation used for the digital signature functionality.