The appearance of a form field button is lost after import-export.

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.

 

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

When importing a document with an invalid creation or modification date, an exception is thrown:

• FormatException: 'The input string '' was not in a correct format.'
• ArgumentOutOfRangeException: 'Year, Month, and Day parameters describe an unrepresentable DateTime.'

Implement GetColor method for IndexedColorSpaceObject.

When applying MultipleSubstFormat1, an exception is thrown: "NullReferenceException: 'Object reference not set to an instance of an object.'"

SMask.Matte is not applied correctly when exporting to an image.

The issue is not reproducible in Q1 2025 (2025.1.205).

In Q2 2025 we introduced the MarkedContent in a RadFixedDocument.

Currently the DocumentInfo property is for export purposes only and meta information about documents is stripped when importing.

According to the PDF specification (ISO 32000), the document info dictionary (often called "metadata" or "Info" dictionary) can include the following standard fields:

• Title: The document’s title.
• Author: The name of the person who created the document.
• Subject: The subject of the document.
• Keywords: Keywords associated with the document.
• Creator: The application that created the original document.
• Producer: The application that converted the document to PDF.
• CreationDate: The date and time the document was created.
• ModDate: The date and time the document was last modified.
• Trapped: Indicates whether the document has been trapped (a printing term).

These fields are stored in the PDF’s Info dictionary and are used by PDF viewers for display, search, and indexing.

 

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 

When exporting a PDF page to an image with the SkiaImageFormatProvider the following error occurs: 

System.IndexOutOfRangeException: 'Index was outside the bounds of the array.'

Handle documents with mismatched font Subtype and FontFile type when exporting PDF to image with SkiaImageFormatProvider.

Import-export changes the color of the shading object.

Add support for "AcroSendMail:SendMail" named action.

Such a document can be considered as invalid. However, it would be good to provide functionality to handle it.  

Part 3 of the standard, published on October 15, 2012, differs from PDF/A-2 in only one regard: it allows embedding of arbitrary file formats (such as XML, CSV, CAD, word-processing documents, spreadsheet documents, and others) into PDF/A conforming documents.

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)

PdfProcessing: ArgumentException is thrown when importing a document with a duplicated filed names.

Wrong clipping order when exporting a document with MarkedContent leads to a missing content.

A shading dictionary specifies details of a particular gradient fill, including the
type of shading to be used, the geometry of the area to be shaded, and the geometry of the gradient fill. Various shading types are available, depending on the value of the dictionary’s ShadingType entry:

• Coons patch meshes (type 6) construct a shading from one or more color
  patches, each bounded by four cubic Bézier curves.