This is causing issues when exporting the document to PDF from WordsProcessing - the pdf library tries to create the font, but cannot find it due to a different casing. When importing HTML document, the font-family property is read with small letters. Later, when converting the string containing the value, it is changed to title case. 

This issue will be reproducible with each font containing a name with a letter with casing different than the one of the other letters (exc. first capital letter), for example: Microsoft JhengHei

The current implementation expects the widths to be integer values and InvalidCastException is thrown when a real number is parsed.

Workaround: If the scenario allows, the PdfStreamWriter may be used instead of PdfFormatProvider. More information may be found in the following documentation article:
http://docs.telerik.com/devtools/document-processing/libraries/radpdfprocessing/formats-and-conversion/pdf/pdfstreamwriter/overview

Available in LIB Version 2017.2.731.

This is because PdfProcessing does not export Annotation Flags and this way all annotations has Print flag set to false.

Available in Release Version R2 2017 SP1.

According to PDF specification widget's parent field should always be terminal field and should have FieldType specified. However, there are documents which are generated without fulfulling this rule and we need to consider handling this scenario without any exceptions.

According to PDF specification, the resources used for the dynamic appearance of fields are defined globally in AcroForm "DR" PDF property. However, there are some invalid documents which define these resources locally in the field node which causes exception in PdfProcessing implementation. As there are several such documents we may consider handling such scenario instead of throwing the exception.

Available in R3 2017 SP1 Official Release.

The PDF format includes a general multimedia framework allowing users to insert and play/visualize different media types. The feature is described on page 755 from PDF Reference 1.7.

Implement the Exponential Interpolation Function in PdfProcessing. Currently, NotSupportedFunctionTypeException is thrown with a message "Function type 2 is not supported."

The field name should be preserved on an import-export scenario. However, in some cases when the field name contains non-ASCII characters then the field name is exported with different value compared to the imported one.

Fix available in LIB Version 2017.3.1009.

This operator is used for drawing shading patterns.

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

Available in R2 2018 Official Release Version.

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

Available in LIB Version 2018.1.312.

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.

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.

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

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

In this case, we should use a default alpha source value which is the opacity source.

Usually, the entries are on neighboring rows. However, some producers introduce some extra blank rows between entries and this causes exception in RadPdfProcessing implementation.

Fix available in LIB Version 2018.2.625.

The exception is thrown by System.Linq.Enumerable.Max method during the CidSet calculations.

Fix available in LIB Version 2018.2.730.

The exception is reproduced only with specific custom fonts and is thrown by the ComputeSubset() method of the GlyphTypeface class with the following message: "file does not conform to the expected file format specification". However, we can handle the exception and export the font data using the base class.

Fix available in LIB Version 2018.2.828.

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