This exception seems to be related to AES algorithm PaddingMode property. 

Text fields should support rich text strings allowing the user to use rich text elements and attributes.

Add support for a strikethrough property or strikethrough-related properties in the TextProperties class.

Automatically.PNG
Please find the attachment.
Sending the info on spelling error

The Matrix property seems to be incorrectly interpreted during the import process.

For some documents, the clippings and colors of the geometries are modified on an import-export scenario.

This includes loading form fields data from FDF file and saving the form fields data to FDF file.

Stencil color has to be preserved for images with ImageSource when ImageMask property set to true. Not preserving it results in wrong colors (for instance the image may be visualized as a black rectangle).

Available in R1 2019 Official Release Version.

Currently, we support inserting png, jpg and other raster graphic images. Provide a way to insert image from SVG (vector graphic image format), by creating a FormSource from its parsed XML.

Currently RadFixedDocumentInfo is used only for export of Author, Title and Description document metadata properties. This should be extended to support custom properties. We should also implement the import of RadFixedDocumentInfo.

Although this is not a valid postscript scenario we should not throw exceptions and we should instead skip the invalid dictionary end characters.

Fix available in LIB Version 2018.1.312.

When merging, only the widgets are copied but not their fields. This can lead to ArgumentNullException when exporting the document. Implement copying the fields and consider cases which include collision of names of the fields.

Workaround:
Repair the generated document using the following code:
foreach (Widget widget in this.pdfDocument.Annotations.Where(annot => annot.Type == AnnotationType.Widget))
{
    if (!this.pdfDocument.AcroForm.FormFields.Contains(widget.Field.Name))
    {
        this.pdfDocument.AcroForm.FormFields.Add(widget.Field);
    }
}
In case of Name collision, you can use the attached project or the attached project to the following feedback item to rename the duplicate fields: Provide a way to rename FormFields.

A NullReferenceException is thrown when trying to clone the Signature property of the field.

Available in LIB Version 2018.1.312.

Trying to clone the Signature of a SignatureField leads to InvalidOperationException as the FieldName of the cloned signature is already set.
Workaround: Remove the signatures before the merging of the document:
private static void RemoveSignatures(RadFixedDocument document)
{
	List<FormField> signatures = document.AcroForm.FormFields.Where(ff => ff.FieldType == FormFieldType.Signature).ToList();
	if (signatures.Count > 0)
	{
		foreach (FormField signature in signatures)
		{
			document.AcroForm.FormFields.Remove(signature);
		}
	}

	List<SignatureWidget> signatureWidgets = document.Annotations.Where(a => a.Type == AnnotationType.Widget && a.GetType() == typeof(SignatureWidget)).Cast<SignatureWidget>().ToList();
	if (signatureWidgets.Count > 0)
	{
		foreach (var signatureWidget in signatureWidgets)
		{
			foreach (RadFixedPage page in document.Pages)
			{
				if (page.Annotations.Contains(signatureWidget))
				{
					page.Annotations.Remove(signatureWidget);
				}
			}
		}
	}
}

In business or enterprises there is more and more demand for PDF/A-3.

In Germany it is Zugferd for hybrid invoices, in Brazil Nota Fiscal Eletronica 2.0, in France FACTUR-X.

Also for longterm preservation it is import to support PDF/A-3.

If I would be the PM of this library this would be my number one priority!

Currently, Standard fonts are exported always with StandardEncoding. This does not allow export of some special characters which do not fit in the first 255 glyph definitions in the font. Most of these characters are the ones with an accent such as "Eacute" glyph (É) which is with position number 303 in Times Roman font. The list of all standard fonts may be found in this documentation section:
https://docs.telerik.com/devtools/document-processing/libraries/radpdfprocessing/concepts/fonts#standard-fonts

This happens only in cases when the Radio flag is not set and there are multiple widgets with different "ON" state names.

Available in R1 2018 SP2 version.

The exception is thrown with the message "Password is not correct" even when the user password is correct. This issue occurs for specific encryption algorithm parameters only.

Currently, NotSupportedEncryptionException is thrown when PdfFileSource is initialized with an encrypted PDF file.

Available in R2 2018 Official Release Version.

Currently, NotSupportedEncryptionException is thrown.