More information is available in the Pdf Reference 1.7. Page 442 lists all predefined CMaps that should be imported and exported as PdfName objects. At this point, trying to import a document with such encoding, a NotSupportedException is thrown with message Encoding type is not supported.

OutOfMemoryException has thrown when creating a thumbnail with the ThumbnailFactory.

This behavior is observed with binaries version 2020.2.513 or later.

A StackOverflowException is thrown when cloning documents containing a page containing links to the same page. 

In Adobe Acrobat, if you bring up the "Document Properties" dialog window and then click on the "Advanced" tab, there is a property under the "Print Dialog Presets" section called "Page Scaling". We should preserve the value on import/export and be able to set it in the code behind.

AcroForms are not saved when splitting a document into pages. This leads to forms not being recognized when the file is imported back.

Currently, importing a document with non-embedded TrueType font will result in a font instance with an empty font source. Support should be added for providing custom font data of TrueType fonts during document import.

By specification, the URI property of URI Actions is encoded in 7-bit ASCII string. For this reason, our current implementation relies on that the property will be of type PdfLiteralString. However, in cases such as password-encrypted documents, the property may be encoded with PdfHexString which leads to InvalidCastException: 'Unable to cast object of type Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Types.PdfHexString' to type 'Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Types.PdfLiteralString'.', on document import.

By specification, FitH destinations are defined with page and top position. A null value for top specifies that the current value of that parameter is to be retained unchanged. However, importing such a document with PdfProcessing leads to ArgumentOutOfRangeException:  'Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index'.

When importing document with text containing char code mapped to .notdef glyph name an ArgumentException: 'The encoding is not supported.' is thrown.

NullReferenceException has thrown when importing a form XObject with null Resources in PDF dictionary.

Add a PDF document validator to validate (before the import of the document) an existing PDF document.

 InvalidCastException when importing a file with missing space. The file contains no space between the objects declarations and the page content and this is why the exception occurs.

When importing a VariableContent widget with OpenType font, which fails to read the post table of the font file, a NullReferenceException is thrown when the RecalculateContent() method is called.

Workaround: Change the widget font:

foreach (Widget widget in textBoxField.Widgets)
{
    widget.TextProperties.Font = FontsRepository.Helvetica;
    widget.RecalculateContent();
}

More information is available in the Pdf Reference 1.7. Page 442 lists all predefined CMaps that should be imported and exported as PdfName objects. At this point, trying to import a document with such encoding, a NotSupportedException is thrown with message Encoding type is not supported.

Telerik Pdf Processing Cannot open the attached pdf file and exception occur.

How do i slove it?

Code :
  RadFixedDocument document = new PdfFormatProvider().Import(input);

Exception Message :
   System.UriFormatException  無效的 URI: 無法剖析主機名稱。

Source :
   Telerik.Windows.Documents.Fixed

Stack Trace :

於 System.Uri.CreateThis(String uri, Boolean dontEscape, UriKind uriKind)
   於 System.Uri..ctor(String uriString, UriKind uriKind)
   於 Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Elements.Actions.UriActionObject.ToAction(PostScriptReader reader, IRadFixedDocumentImportContext context)
   於 Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Elements.Annotations.LinkObject.ToAnnotationOverride(PostScriptReader reader, IRadFixedDocumentImportContext context)
   於 Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Elements.Annotations.AnnotationObject.ToAnnotation(PostScriptReader reader, IRadFixedDocumentImportContext context, Double pageHeightInDip)
   於 Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Elements.DocumentStructure.Page.CopyPropertiesTo(PostScriptReader reader, IRadFixedDocumentImportContext context, RadFixedPage fixedPage)
   於 Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Elements.DocumentStructure.DocumentCatalog.CopyPagePropertiesTo(PostScriptReader reader, IRadFixedDocumentImportContext context)
   於 Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Elements.DocumentStructure.DocumentCatalog.CopyPropertiesTo(PostScriptReader reader, IRadFixedDocumentImportContext context)
   於 Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Import.RadFixedDocumentImportContext.BeginImportOverride()
   於 Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Import.BaseImportContext.BeginImport(Stream pdfFileStream)
   於 Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Import.PdfImporter.Import(Stream input, IPdfImportContext context)
   於 Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.PdfFormatProvider.ImportOverride(Stream input)
   於 Telerik.Windows.Documents.Common.FormatProviders.FormatProviderBase`1.Import(Stream input)
   於 Telerik.Windows.Documents.Common.FormatProviders.BinaryFormatProviderBase`1.Import(Byte[] input)

The underline gets over the text when the line spacing is set to exact, spacing after is set to 0, and the font size is less than 12.

The checkbox state is not correctly imported when the value is not specified

A submit-form action transmits the names and values of selected interactive form fields to a specified uniform resource locator (URL), presumably the address of a Web server that will process them and send back a response. Preserve the existing submit-form actions in the document and expose functionality enabling the users to create or modify such actions.

The calculations are wrong, leading to single lines split by the LineSpacing set. As a result, the content of the PDF document is laid out on a bigger number of pages.

Workaround: Change the LineSpacingType to HeightType.Auto.

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.