As an effect of this, characters, which are not contained in the StandardEncoding names, e.g. umlauts, are measured with incorrect glyph widths. This leads to incorrect glyph positioning in RadPdfViewer.
By specification the explicit destinations define a required page property. However, some documents contain definition for destinations with null page value, which causes an ArgumentNullException on import.
By specification, names are an atomic symbol uniquely defined by a sequence of characters. However, when importing a document with names defined as an empty sequence a handled InvalidCastException is thrown which leads to missing page content.
Error message is: "One or more errors occurred. (Unable to cast object of type 'Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Types.PdfName' to type 'Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Types.PdfInt'.)"
The current implementation relies on valid cross-reference offsets in the PDF documents so that PDF objects are easily found and parsed. However, we may implement a mechanism for importing documents with invalid offsets for the objects inside the table.
When User changes LayoutMode the ZoomLevel property changed event should also be fired. I have a Numeric Textbox to adjust viewer ZoomLevel and would like to see its text update on a LayoutMode change. However when LayoutModeChanged fires the ZoomLevel has not yet changed nor does ZoomLevelChanged later fire.