When a break element is defined in the middle of a Run, DocxFormatProvider imports it at the end of the same run. For example, the following content: 

<w:r>
  <w:t>This is</w:t>
  <w:br/>
  <w:t xml:space="preserve"> a simple sentence.</w:t>
</w:r>

Results in "This is a simple sentence " + break element after it.

Import of Tables with border style needs improvements. Currently, it takes multiple seconds to import table with 100x6 cells no matter if the border style is defined globally or locally. This may be seen when importing the attached files "table with borders.html" and "table single border style.html". Importing the same table without borders is achieved in less than a second which may be seen with the attached "table without borders.html".

Introduce support for min-height. Currently, this property is skipped. 

If a document has runs with font size larger than the one set in the style of the paragraphs and this document is exported to HTML, the resulting paragraphs overlap.

This is only reproducible when the Run contains an empty string. If the paragraph is empty or the Run contains a space, everything is working correctly.

Workaround: Remove all empty runs from the document.

When exporting to PDF a document containing Table merged into a TableCell an extra empty space below the inner table is added:

Wrongly exported table width when the table preferred width is set to fixed:

<w:tblW w:w="11160" w:type="dxa"/>

and it is greater than the available page width: 

<w:pgSz w:w="12240" w:h="15840"/>
<w:pgMar w:top="630" w:right="1440" w:bottom="540" w:left="1440" w:header="720" w:footer="720" w:gutter="0"/>

Available page width = 12240 - (1440 + 1440) = 9360

A possible workaround is to set the page width to Auto:

IEnumerable<Table> tables = document.EnumerateChildrenOfType<Table>();
foreach (Table table in tables)
{
	if (table.PreferredWidth.Type == TableWidthUnitType.Fixed)
	{
		table.PreferredWidth = new TableWidthUnit(TableWidthUnitType.Auto, table.PreferredWidth.Value);
	}
}

Exporting RTF document to HTML when there is a multilevel numbered list, strips the numbers and leaves only the main number visible (e.g. 2.1 becomes 1). Also, the text overlaps the numbering. 

Workaround: Use numbers with letters instead of numbers only. (e.g. 1 a b c, 2 a b c).

To reproduce: 

-Change the normal style in a document and insert it into another document using RenameSourceStyle option.

The style is renamed and inserted but is not applied to the content.

WordsProcessing: Merging a RadFlowDocument document into the target document over around 130 times breaks formatting when the target document is an empty RadFlowDocument.

The workaround to this issue is to set the target document to an existing RadFlowDocument such as the source before merging.