InvalidCastException is thrown when a name start character is followed by a literal string start character.
System.InvalidCastException: Unable to cast object of type 'Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Types.PdfInt' to type 'Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Types.PdfName'.
When some character is not supported by the font, the fallback mechanism should try finding some other font that is capable of rendering the unsupported character. However, RadPdfProcessing fallback mechanism does not always find the correct font which sometimes result in wrong glyph visualization or in missing glyph. Workaround: Font that supports these special characters may be used. This way the fallback mechanism will not be needed to export the PDF text.
When Separation color space with "name" set as None it is falling back to an "alternateSpace" (color space) instead.
From the Pdf specification:
A Separation color space is defined as follows:
[ /Separation name alternateSpace tintTransform ]
The None value is ignored and the color space fallbacks to the Lab color space.
According to PDF specification, the field value should be specified in the "V" entry of the corresponding PDF dictionary. However, some PDF producers are skipping this entry and are setting only the Widgets appearance states. As most viewers manage to show the radio button and checkbox as selected, we should handle this scenario and import the field values based on the related widgets when this value is not explicitly set with the field's V entry.
For some documents, the clippings and colors of the geometries are modified on an import-export scenario.