A NullReferenceException is thrown when importing a hyperlink that doesn't contain any run elements. Similar hyperlinks could be skipped so the document can be successfully imported. 

Available in R3 2018 SP1 release.

In the current implementation, the parent of a hyperlink must be a paragraph. Otherwise, a NullReferenceException is thrown.

Currently the PageOrientation property is used to determine the actual size of the paper to use on the printer and does not reflect document's visualization. In order to affect Section's appearance the user should change the PageSize and PageMargin properties. For convenience the Rotate method is introduced in order to update the properties simultaneously. However the usage of the Section.Rotate(PageOrientation) method is confusing since the properties are not updated when Section.PageOrientation is already set to the same value as the parameter. Also, Rotate method is useful only for rotating already created sections, and to create section with specified pages size and margins the user should set all Section's PageSize, PageMargin, PageOrientation properties anyway.

More convenient API must be provided to create Section instances with correctly set properties for the desired page orientation.

Implement support for footers in HtmlFormatProvider.

TC field has special tag - \tc, which is currently not supported and is skipped during import. Because of this, the argument of the field, which is hidden in MS Word, becomes part of the document content.

Enable the customers to add digital signatures to the documents and read signed documents.

Currently, the align attribute is supported only for a table and when applied to a cell or row is omitted on import.

LineInfo objects are not cleared when there are tables in the document being exported to PDF which leads to OutOfMemoryException.

When the table borders are None, and each cell has custom set borders, when cells are merged, only borders of the cell that has <w:vMerge w:val="restart"/> are imported.

The Indent property of Table is not respected by PdfFormatProvider.

Add support for importing HTML with syntax <img style="width: 300px; height: 300px;" /> At the moment only HTML attributes are supported.

There are multiple tags and attributes in the Open XML model which define the formatting of the complex script characters and are not implemented in the WordsProcessing model. 

Such tags are:
szCs: Complex script font size;
bCs: Complex script bold;
iCs: Complex script italic;

Attributes:
cstheme: Complex Script Theme Font;

The cs (Complex Script Font) attribute is implemented in the export, but it is not preserved in the model on import.

When exporting a nested table, which is inside a table with cells whose sum of widths is more than 100%, the last cells are missing from the exported with PdfFormatProvider document.

The issue is not observable in the other format providers.

The issue is reproducible only in a specific setup with a specific document. It is related to the calculations of the line spacing when the table row should be split between two pages.

Workaround: Change the line spacing:
foreach (var paragraph in this.document.EnumerateChildrenOfType<Paragraph>())
{
    paragraph.Properties.LineSpacingType.LocalValue = HeightType.Auto;
    paragraph.Properties.LineSpacing.LocalValue = 1;
}

Applying border="1" to a table element, should set table cells borders to the same value. Currently, only the table borders are set.

When the RowSpan value is bigger than the available rows, a ArgumentOutOfRangeException is thrown while exporting the document.

Workaround: Change the value of RowSpan after importing:

foreach (var cell in document.EnumerateChildrenOfType<TableCell>())
{
    while (cell.RowSpan > cell.Row.Table.Rows.Count)
    {
        cell.RowSpan--;
    }
}

Add support for the <w:sym /> element, e.g.:

<w:r>
   <w:sym w:font="Wingdings" w:char="F0FC"/>
</w:r> 


From the specification:
"This element specifies the presence of a symbol character at the current location in the runs content. A symbol character is a special character within a runs content which does not use any of the run fonts specified in the rFonts element (17.3.2.26) (or by the style hierarchy).

Instead, this character shall be determined by pulling the character with the hexadecimal value specified in the char attribute from the font specified in the font attribute."

Currently such symbols are skipped during DOCX import.

Possible workaround: These tags are inserted from MS Word when the Symbol dialog in used. If the document is created with MS Word, the user could insert the symbol using the keyboard, in this case the character is inserted as a normal run.

When a document with ordered list is exported to RTF and opened with WordPad or WinForms' system RichTextBox the numbers of the list are replaced by "{0}".

When a table cell has a smaller width set and inside there is a paragraph with larger indent set or bullets, the table does not expand in order to show the text and the text becomes invisible.

Run's default constructor creates it with Text = null. When document with such run is exported to PDF, NullReferenceException is thrown.

Workaround: Create the Run and immediately set its Text property to string.Emtpy.

Available in LIB Version 2018.1.423.