An InvalidCastException is thrown when importing documents containing outlines with an invalid destination set:

The exception:

System.InvalidCastException: 'Unable to cast object of type 'Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Types.PdfReal' to type 'Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Types.PdfName'.'

ArgumentOutOfRangeException is thrown when importing a document because of wrongly parsing to Unicode mapping.

System.ArgumentOutOfRangeException: 'Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index'

According to the PDF specification:
A clipping path operator (W or W*) may appear after the last path construction operator and before the path-painting operator that terminates a path object.

Invalid:

W                          % clipping path operator
0 0 m                     % start of the path construction
596 0 l
596 842 l
0 842 l
h                            % end of the path construction
n                            % path-painting operator

0 0 m
596 0 l
596 842 l
0 842 l
h
W
n

Currently (in the invalid cases), the path construction is skipped on import.

When using the Telerik.Documents.ImageUtils.JpegImageConverter default implementation in Blazor WebAssembly application the Magick.NET library doesn't load all of its assemblies.

Workaround:
Create a custom implementation of the JpegImageConverterBase class: Create Custom JpegImageConverter in .Net Standard.

When importing a document containing an invalid PDF object dictionary key an exception is thrown.

When importing a not embedded TrueType Font defined as Type 1 subtype Font an InvalidCastException is thrown.

In PDF document:

<< /BaseFont /Arial /Encoding 21 0 R /Name /F13 /Subtype /Type1 /Type /Font >>

In Adobe Reader: