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 invalid. However, it would be good to provide functionality to handle it.

Update: After reviewing the case, we concluded that the issue is caused by the document being linearized. Therefore, this item is being marked as a duplicate. Please follow the related public item to receive notifications about future status updates.

 

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.

This error happens when importing a document.

Error message: 

System.InvalidCastException: 'Unable to cast object of type 'Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Elements.Forms.FormFieldsTree' to type 'Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Types.PdfArray'.'

Error message:

System.InvalidCastException: 'Unable to cast object of type 'Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Types.PdfArray' to type 'Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Elements.Functions.FunctionObject'.'

Multiple graphic state objects are lost on import.

When importing a document with a missing "endobj" operator, an exception is thrown: InvalidCastException: 'Unable to cast object of type 'Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Types.PdfInt' to type 'Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Types.IndirectObject'.'

InvalidCastException is thrown due to incorrectly parsed stream dictionary.

ArgumentOutOfRangeException is thrown when creating a CapPathRound for an SVG element.

Exporting a specific PDF file generates large amounts of ExtGState entries, which results in large file sizes.

When exporting the PDF content to plain text, the form fields and their values are not extracted. It would be nice to have an option to include the content in the form fields as well.