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

Generally, allow more straightforward setters of style related properties without going through 2-4 levels of temporary objects.  For example, when dealing with tables, there is no obvious way to set line spacing or paragraph spacing globally for the table.  Should have TableCell.Blocks.AddText("New Text") instead of AddParagraph, which provides spacing you don't want or need.

Also, when you want to set the FontSize, FontWeight, and FontFamily all at once, there is no easy way to do that.  Also no global way to do that for a section, page, table, etc.

The above would make it a LOT easier to create documents programmatically.  I would like to see more parameterized constructors for common style attributes by type.  You will discover the challenges by creating a richer document from scratch with several tables, styles, left and right justified content on the same line, etc.  Same for easily setting header and footer content.

Thanks!  Great work so far, I love it!

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.

The feature will be available in our official release Q1 2016.

The feature is available in our latest LIB release (v. 2014.3.1124)

Do not hesitate to contact us if any issues or questions arise.

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

The fix will be available in our official release Q3 2015 SP1.

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

This will allow watermarks to be set on the document pages.

The feature will be available in our official release 2015 Q2 .

The feature will be available in our official release 2015 Q2 .

The feature will be available in our official release Q1 2016.