Add support for annotations with custom Subtype.

Support for FileAttachment annotations. 

A file attachment annotation contains a reference to a file, which typically is embedded in the PDF file.

Missing spaces from TextFragments when exporting to plain text.

Usually, the object references are expected to be stored in the following format: "5 0 obj". However, if the format is "0000005 0 obj", the document can't be parsed successfully. As a result the document is not displayed in RadPdfViewer.

Currently we skip these images in the import for PdfProcessing.

StackOverflowException is thrown when applying filter for SVG.

RadPdfProcessing currently supports interactive forms whose data is defined directly in the document. To preserve them when importing and exporting documents, add support for import-export interactive forms based on the Adobe XML Forms Architecture (XFA).

From PDF 2.0 the XFA forms are depreciated.

"An error exists on this page. Acrobat may not display the page correctly." error in Adobe when inspecting a page with DeviceGray ColorSpace image after import-export.

When importing a document, the following error message is observed when reading the Arial, Italic font: System.InvalidCastException: 'Unable to cast object of type 'Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Types.PdfLiteralString' to type 'Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Types.PdfName'.'

Add support for Arrange Options (level placement):

• Bring to Front
• Send to Back
• Bring Forward
• Send Backward

When a PDF document is being imported, some of the characters may experience unexpected results while reading the font.

NOTE: the document is displayed in the MAUI/WPF/WinForms PdfViewer controls with missing parts of the text.

Wrong font loading when FontFile2 is CFF (Compact Font Format).

The PDF/A-1 standard uses the PDF Reference 1.4 and specifies two levels of compliance:

- PDF/A-1b - Its goal is to ensure reliable reproduction of the visual appearance of the document.

- PDF/A-1a - Its objective is to ensure that documents content can be searched and re-purposed. This compliance level has some additional requirements:

• Document structure must be included.
• Tagged PDF.
• Unicode character maps
• Language specification.

Since the PdfProcessing and its PdfFormatProvider is compliant with the PDF Reference 1.7. , the produced documents are created with this version as well: 

Handle the import of documents with null elements in the Associated Files (/AF) collection.

Purpose: Long-term archiving of electronic documents with full semantic structure.

• "A" for Archiving

• Level "1a" ensures:

  • Tagged PDF (with proper logical structure and reading order)

  • Unicode text for proper text extraction and searchability

  • Embedded fonts (for consistent rendering)

• Restrictions:

  • No audio/video

  • No encryption

  • No JavaScript

  • No external content (everything must be self-contained)

• Based on: PDF 1.4 (Acrobat 5)

Add support for "AcroSendMail:SendMail" named action.

It would be great if the SkiaImageExportSettings offer a DocumentUnhandledException event allowing the developer to handle specific errors when exporting to image formats.

This would be an essential improvement in the existing Exception handling mechanism and would enable exporting PDF documents to images even though some parts of the image may not be completely supported: https://docs.telerik.com/devtools/document-processing/libraries/radpdfprocessing/features/handling-document-exceptions 

Manually set form field values are not preserved when opened in Adobe Acrobat.

When you register a font in an ASP.Core project and in a static constructor, the generated PDF document will have this font only the first time you load the web page. Refreshing the page will generate the PDF document but the fonts will be lost.

Note: This worked in the previous version  2025.2.701.

 

PDF content:

Exported text content: