The current implementation relies on valid cross-reference offsets in the PDF documents so that PDF objects are easily found and parsed. However, we may implement a mechanism for importing documents with invalid offsets for the objects inside the table.

Add a setting that allows enabling printing of protected documents.

Exception when publishing with ReadyToRun option and manually registering fonts.

Missing content when converting a specific PDF to images (mostly text and shapes).

Provide a consistent API for cloning document elements. Currently, we have a public API for cloning documents but not their elements. 

Currently, when users need to add content to an existing page that is rotated, they should manually calculate the positions of the new content if they need to align it with the appearance of the page. Add API allowing them to easily transform the position respecting the top left edge of the page after its rotation.

According to the PDF Specification: The definition of an indirect object in a PDF file consists of its object number and generation number, followed by the value of the object bracketed between the keywords obj and endobj. For example, the definition:
An invalid case:

ArgumentException when the font box contains negative width or height 

When importing documents with more than one cross-reference table that have not Prev tables specified the incorrect table is processed.

After signing a document using the PdfProcessing library and the document is loaded in Adobe Acrobat an error is shown when the signature widget is clicked:
Error during signature verification.  

Adobe Acrobat error.
Expected a dict object.

Wrong matrix calculations lead to incorrect image (Form XObject) during export

For example, when some PDF file has uncompressed contents we may import it and apply better compression to the stream objects. Ensure that all the content inside the document is compressed.

Currently, we have the following options for PDF export optimizations:

• ImageQuality
  

  pdfFormatProvider.ExportSettings.ImageQuality = ImageQuality.Low;

• ImageCompression
  

  pdfFormatProvider.ExportSettings.ImageCompression = new ImageFilterTypes[] { ImageFilterTypes.FlateDecode };

• StreamCompression
  

  pdfFormatProvider.ExportSettings.StreamCompression = new StreamFilterTypes[] { StreamFilterTypes.FlateDecode };

• FontEmbeddingType (Q2 2024)
  

  pdfFormatProvider.ExportSettings.FontEmbeddingType = FontEmbeddingType.Subset;

  We introduced an option of exporting subsets of True Type Fonts (*.ttf) for the .NET Standard version of the library.

The images inside form sources are not correctly positioned and might be invisible.

This issue is regression it works with R2 2020.

After merging documents with PdfStreamWriter the JavaScript actions are broken and not working.

Wrong matrix calculations lead to incorrect image (Form XObject) size.

In specific cases when importing a document containing an Indirect Reference keyword ("R") within an image data an exception is thrown: InvalidCastException: 'Unable to cast object of type 'Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Operators.State.SetLineDashPattern' to type 'Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Types.PdfInt'.'

InvalidCastException is thrown when importing a document containing Byte order marks (BOM) at the beginning of the file. The bytes are read as part of the document content and this changes all the document`s offsets.

Importing a document containing an EI keyword within the image stream leads to an endless loop and the document is not imported successfully.

The import freezes due to a lot of checks in the HandleInvalidClippingPathOperatorPosition method.

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

Currently, when invoking the Signature`s TryValidate() method an exception is thrown: NotSupportedException: 'No signature validation handler was found for the subfilter: ETSI.RFC3161'