When importing color space defined as an external resource name, a NotSupportedColorSpaceException: 'CS0 color space is not supported.' is thrown.

To reproduce: 

- Add the following formula to a cell: "=A1=FALSE"

Actual: the result is always false

Expected: the result should be true when the cell is empty

 

Workaround: Use the ISBLANK function.

This is reproducible with specific PDF files which use custom Encoding for the fonts of the field widgets. 

WORKAROUND: Change the font of VariableContentWidgets before editing the field value. You should additionally call RecalculateContent() method of these widgets if the value of their corresponding fields is not edited. The following method may be used for changing the font of all existing widgets in the document:

private static void FixEncodingIssues(RadFixedDocument document)
{
    foreach(Annotation annotation in document.Annotations)
    {
        VariableContentWidget widget = annotation as VariableContentWidget;

        if(widget != null)
        {
            widget.TextProperties.Font = FontsRepository.Helvetica;
        }
    }
}

The Office Open XML model doesn't support the transparency of the colors inside a document. Even if an alpha channel is used for the colors, this should not be respected by SpreadProcessing and the colors should be without any opacity.

Font properties set from RadFlowDocumentEditor`s CharacterFormatting are not taken into account when inserting PAGE field:

A possible workaround could be to remove the image with the invalid Uri from the RadFlowDocument before export:

Importing shape with missing id attribute leads to NullReferenceException. 

 <v:shape type="#_x0000_t202" filled="false" stroked="false">

Table and table cell borders are not evaluated according to inheritance and conflict resolution rules. A conflict will occur when different borders from the table and table cell are overlapping. 

The GetActualValue method of the TableBorders and TableCellBorders could potentially return an incorrect value in some of the following scenarios:

Scenario 1:
A table has cell spacing set to 0. Meaning that the table and table cell borders will overlap.
The table borders have defined all of its borders with border style "Single".
The table cell borders have all of its borders defined with border style "None".

Expected result: the resulting borders should have the border style set to "None" for the location where the table and the cell borders are overlapping.

Scenario 2:
A table has explicitly defined that its right border is with border style "None".
The table has a table style applied with defined border style of type "Single" for all table borders.

Expected result: All of the table borders except the right border should have border style of "Single".

The problem is mostly visible when exporting to PDF and RTF format.

Exception when trying to import symbols with the ZapfDingbats font

When a formula contains new lines, it is parsed incorrectly as follows:

- When it is shared formula it breaks the imported expression and replaces it with #NAME? error.
- In normal case it simply preserves the formula string converting it to StringExpression.

Workaround: Remove the new lines in the formulas.

Have in mind that this code will fix the issue only for the second scenario, when the formula is not shared.

CellRange usedCellRange = workbook.ActiveWorksheet.UsedCellRange;

for (int row = usedCellRange.FromIndex.RowIndex; row < usedCellRange.ToIndex.RowIndex; row++)
{
    for (int column = usedCellRange.FromIndex.ColumnIndex; column < usedCellRange.ToIndex.ColumnIndex; column++)
    {
        CellSelection cell = workbook.ActiveWorksheet.Cells[row, column];
        ICellValue value = cell.GetValue().Value;

        if (value.RawValue.Contains("\n"))
        {
            cell.SetValue(value.RawValue.Replace('\n', ' '));
        }
    }
}

This is not a valid scenario, but Adobe Acrobat handles it and we should too. 

Embedding a TrueType font collection using the FontsRepository.RegisterFont method leads to glyphs with empty outlines collection. The missing outlines are caused due to an empty glyf and loca tables of the TrueType font file.

KeyNotFoundException exception is thrown when the platform type is MacintoshNonSymbolic and the encoding is WinAnsiEncoding.

The chart axes are not correctly imported when there are floating and sheet charts

German umlauts (the characters 'Ä', 'Ö', 'Ü', 'ä', 'ö' and 'ü') will not be printed to a generated pdf file, but the other German "special" character "ß" works.

 

I use the trial version via the Telerik NuGet feed. A test program and my locally generated file are attached.

Currently, the calculation of the actual ScaleFactor is based only on Worksheet`s UsedCellRange.

The content of the merged cells is measured and affects the CenterHorizontally behavior. Only the first cell from the merged range should have content. This is the default behavior in MS excel when cells are merged as well.

Fonts that are not surrounded by curly braces cannot be imported in the RTF format

PdfProcessing: Signature field validation fails if a document is imported from a byte array of CopyStream property is false.

Workaround: Set the CopyStream property of the ImportSettings to true:

PdfFormatProvider formatProvider = new PdfFormatProvider();
formatProvider.ImportSettings.CopyStream = true;

Exported checkbox fields have state "/On " instead of "/Yes ".