A docx document containing a table with a single cell on the first row and some columns with preferred width set, is exported to pdf file with incorrect cell widths of the table.
The fix will be available in our latest LIB release (v. 2015.1.0323).

The fix will be available in the next official release Q3 2014.

The fix will be available in next official release Q3 2014

The fix is available in our latest LIB release (v. 2015.1.0316)

The fix will be available in our official release Q2 2015 SP.

The fix is available in our latest LIB release (v. 2015.1.0316)

The fix is available in our latest LIB release (v. 2015.1.0316)

The fix will be available in our next LIB release (v. 2016.01.125).

In the XML all merged cells have the same content, instead of only the one visible having content and the rest being empty. This sometimes causes all cells to be visible in editors.

The fix will be available in our LIB release (v. 2016.01.0312).

The fix will be available in the next official release Q1 2015.

When image is added with size Size.Empty, it is exported to HTML with the following invalid syntax:
width="-Infinity" height="-Infinity"

Exporting to Docx throws exception. 

Consider exposing an API for suppressing the export of 'width' and 'height' attributes to HTML, for example in the ImageExportingEventArgs.

The fix is available in our latest LIB release (v. 2015.1.0316)

The value will be skipped when importing the document (<table width=200>). If the size is defined (px or %) as follows <table width=200px> or <table width=200%> then the width value will be respected.

The fix is available in our latest LIB release (v. 2015.1.0316).

The fix is available in our latest LIB release (v. 2015.1.0316).

When document contains field element without the optional separator character, the import fails.