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.

A font descriptor can be used by several fonts. However, when first a TrueType font is imported, later trying to import a Cid font leads to InvalidCastException with the message: "Unable to cast object of type 'Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Elements.Fonts.FontDescriptor' to type 'Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Elements.Fonts.CidFontDescriptor'."

Fix available in R3 2018 SP1 release.

This type of fields is currently not supported: https://feedback.telerik.com/Project/184/Feedback/Details/249205 . However, the fields can be skipped and the other content can be imported without throwing an exception.

Fix available in R3 2018 SP1 release.

When the string contained in a PdfHexString instance is empty, invoking ToString() leads to IndexOutOfRangeException.

Available in R3 2018 SP1 release version.

The tj operator is responsible for drawing text content. When such operator is left empty, the import throws NullReferenceException because of the missing operands.

Available in LIB Version 2018.3.1022.

When there is long text that is out of the used cell range area, this text should be included in page splitting calculations.

Also, when a cell has text that overflows its width, the text is again clipped by the cell boundaries and is not visible in the exported PDF. In a similar case Excel exports the surrounding cells to ensure that the content is visible.

Workaround: Extend the used cell range to include all the cells which the text content spans.