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.

This feature is currently supported only for the .NET Framework and .NET Core applications for Windows.

This type of destinations is not supported and leads to InvalidCastException when importing such elements.

According to the specification, the startfref keyword must be followed by the offset the xref table start on, defined on a new line. Some documents, however, have both entries defined on the same line, which leads to InvalidOperationException with message "Stack empty" while importing. Make sure this case is handled in PdfProcessing as well.

Add support for Lab color space to allow clients to import and export documents with Lab color space.

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

I would like to request an example of the RadPdfProcessing library utilizing a Line Chart similar to how the Bar Chart is drawn in this example. 

Additionally, it would be great if there was an example with multiple charts on one page.

Thank you!

Implement API for adding document outline (a.k.a bookmarks).

In principle, the blend function B (Cb , Cs ) is used in the compositing formula to customize the blending operation in Adobe transparency imaging model. The blending mode may define any function which yields another result color from the backdrop and source colors. This will allow overlaying objects on each other forming a transparency stack.

Support for the Blend Mode parameter of the external graphic state should be implemented.

Provide a way to change the Name of a FormField from the RadDocument.AcroForm.FormFields collection.

As a workaround, you could create a new instance of a FormField with the desired name, add the new field in the document and remove the old one. You can use the following approach:
   1) Create a new instance of FormField (with the desired name, passed in the constructor), which will play the role of a copy of a specific FormField
   2) Copy all properties from the original field (they all vary, depending on the concrete type of the FormField, for example CheckBoxField, etc.)
   3) Create a new widget for the new field, and copy all properties from the original field's widget into the new one.
   4) Remove the original field from the RadDocument.AcroForm.FormFields collection and add the new field.
   5) Remove the original widget from the corresponding page's annotation and add the new one.

Attached is a project demonstrating this approach for a CheckBoxField.

Sometimes customers need to create documents using the CMYK colors to meet specific requirements for printing. Expose such functionality in PdfProcessing.

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.

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 for exporting WMF (Windows Metafile) and EMF (Enhanced Metafile) images should be implemented.

Workaround: Convert the WMF images to PNG before exporting:

When merging files the documents might have the same fonts embedded. Then the PdfProcessing should use only one of the fonts and skip embedding the second font in the resulting document.

Documents can be signed using the end certificate of a certificate chain, instead of the whole chain. This improves the performance of the signing.

Allow the customers to insert DWG files in the PDF documents.