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.

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

According to the PDF specification (Adobe® Portable Document Format Version 1.7), the appearance dictionary is optional and it is specifying how the annotation is presented visually on the page.

Exceptions thrown:

InvalidCastException: 'Unable to cast object of type 'Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Types.PdfNull' to type 'Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Elements.Annotations.Appearance'.'

NullReferenceException: 'Object reference not set to an instance of an object.'

When the document contains Simple Font with predefined encoding and no ToUnicode mapping the text should be extracted with the following algorithm:

• Map the character code to a character name according to the font’s Differences array.
• Look up the character name in the Adobe Glyph List to obtain the corresponding Unicode value. 
  

Currently, the PdfProcessing library doesn't map the character code properly which leads to wrongly encoded text content.

Writing a page to a stream with resources, defined with names including space or dash characters, are not exported using an escape sequence.

This API should provide a method for removing all fields and widgets in the document and draw the default widget appearance in place of the removed widgets.

WORKAROUND: Sample implementation for flattening form fields may be seen in the FlattenFormFields method from the attached demo project.

Adding a table with the same code leads to different results 

When adding 10 identical tables onе or more have missing rows at the bottom. The seems to be caused by the text measurement. 

The executing of the PostScriptReader`s Read method takes a lot of time when iterating content streams with many Path geometries.

When exporting TextBoxField with a Simple font and a Differences array defined in the Encoding, the CharCodes covered by this array are incorrectly mapped to glyph indices.

When a TrueType font is defined, the mapping of character codes to glyph indices depends on the built-in cmap table mappings defined in the font and the Encoding property defined in the PDF dictionary.

However, the current implementation maps all characters with cmap tables for Microsoft Symbolic and Macintosh Roman, which causes incorrect mapping results, e.g. space characters are mapped to an Ê glyph.

The issue is also described in the following public item: TryGetCharCode for OpenTypeFont uses wrong cmap and returns wrong charcode.

Workaround: Change the font  of the TextBoxField's widget appearance:
foreach (var widget in field.Widgets)
{
    widget.TextProperties.Font = FontsRepository.Helvetica;
}

There are many instances of the internal Transition, State and ImageXObject classes.

Currently, RadFixedDocumentInfo is used only for the export of Author, Title, and Description document metadata properties.

Currently, this missing functionality may be workaround by either drawing the headers and footers with FixedContentEditor or by using RadWordsProcessing PDF export.

Provide an API for externally signing the document hash.

The PDF model allows actions to be defined for widgets using the optional /A entry. 

Implement GetColor method for Indexed color space

Add support for Lab color space to allow clients to import and export documents with Lab color space.

When exporting a document referencing PdfProcessing`s .NET Standard assemblies with PdfComplianceLevel set an exception is thrown.

The common annotation properties are described in table "Entries common to all annotation dictionaries" of the Pdf specification.

Declined: Handling a partial annotation import-export could lead to exporting invalid PDF documents.

When merging or splitting files that contain the "159 '\u009f'" char, ArgumentException("The encoding is not supported.") is thrown.

This issue can also result in ArgumentException in client applications with the message: currentIndirectObject should be null.

Workaround:

Use PdfFormatProvider or reflection to register the char (check the comments).