Handle documents containing invalid null entries in the optional content groups array.

Culture on generating computer: de-DE

• Format string: #.##0,00  -> Output correct: 1,234,567.89 (on US) and 1.234.567,89 (on German)
• Format string: #,##0.00  -> Output incorrect: 1,234,567.89 (on US) and 1.234.567,89 (on German)
• Format string: #.##0,0  -> Output incorrect: 1234567.8901 (on US) and 1234567,8901 (on German)
• Format string: #,##0.0  -> Output incorrect: 1,234,567.8 (on US) and 1.234.567,8 (on German)

The first string is an in-built string and is exported correctly. The other three strings are custom (not part of the in-built collection), are not converted to invariant culture and do not produce correct results when the file is opened in Excel.

Exporting a file with a Cmap and custom encoding results in an invalid file

When exporting with  TaggingStrategyType.Build, automatic table detection can include surrounding content in the table and generate rows, cells, and header associations that do not match the document’s logical structure. Headings may become table-cell content instead of remaining separate elements.

The exported PDF may pass automated accessibility validation despite having incorrect semantics for screen readers.

If Paragraph has applied style, and this style has associated list, and the paragraph is removed from the list locally, then on import the paragraph is added to the list.

The additional numbering could be removed from the paragraph by changing its style:

foreach (var p in this.document.EnumerateChildrenOfType<Paragraph>())
{
    if (p.ListLevel == 0)
    {
        var style = new Telerik.Windows.Documents.Flow.Model.Styles.Style("NoListStyle", StyleType.Paragraph);
        style.ParagraphProperties.CopyPropertiesFrom(this.document.StyleRepository.GetStyle(p.StyleId).ParagraphProperties);
        style.ParagraphProperties.ListId.LocalValue = null;
        style.ParagraphProperties.ListLevel.LocalValue = null;
        p.StyleId = "NoListStyle";
    }
}

The tblGrid property should be exported in order to visualize properly the documents in some viewers. For example, LibreOffice doesn't visualize properly tables  without specified width.

When the <sectPr> element is not defined as the last child element but appears in different position of the <body> of the document, the content after <sectPr> is not imported. 

Although some applications handle this case, according to the Office Open XML specification, the sectPr element must be the last element inside the <body>.

Provide a public API for setting the Scope attribute on explicitly created table-header (TH) structure elements.

Currently,  StructureElement.Attributes,  StructureElementTableAttributes, and  TableScopeAttribute are internal. Applications can create TH elements but cannot directly specify whether headers apply to a row, column, or both.

This prevents PDF/UA-1 compliance when table relationships are not defined through Headers and IDs.