Exception when trying to import a file generated with the PdfProcessing library from HTML

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

This issue is regression it works with R2 2020.

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

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

They are exported with the /EmbeddedFiles switch. This would allow adding external files to the PDF document.

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.

Add support for documents containing RTL (right-to-left) text.

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

A free text annotation displays text directly on the page. Unlike an ordinary text annotation, a free text annotation has no open or closed state; instead of being displayed in a pop-up window, the text is always visible.

Images are decompressed during import/export which result in significantly larger files

The image stream is not compressed resulting in a bigger size of the generated file.

Wrong text appearance when editing field because of the wrong FieldFlag ("Ff") exported.

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'

When opened in Adobe Reader it says that the file "claims compliance". However, when verifying the compliance with some validation tools there seem to be some issues mainly related but not limited to fonts. 

Add a setting that allows enabling printing of protected documents.

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.