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

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).

When a workbook (xlsx) contains a worksheet where some of the columns have width, bigger than the value written in the SpreadsheetDefaultValues (2000) an exception during the import is thrown.

A Link annotation must have an associated action, destination, or named destination specifying what should happen when the annotation is activated. When merging documents with invalid Link annotations, an ArgumentException is thrown with the message 'Value cannot be null. Parameter name: namedDestination'

Workaround: Remove the invalid annotations:

foreach (var annotation in document.Annotations.ToList())
{
    var link = annotation as Link;
    if (link != null && link.Action == null && link.Destination == null && link.NamedDestination == null)
    {
        (annotation.Parent as RadFixedPage).Annotations.Remove(annotation);
    }
}

The missing feature leads to this unwanted behavior:

• When there is content control, which generates content on interaction, and it has some custom run properties set to it, they are lost when the user modifies it.

As a workaround, you need to apply a custom style (with the desired run properties) and apply it to the content control.