Field code fragment is added to the result fragment and exported to PDF/HTML format. The problem is observed when the code fragment is divided into multiple inlines.

For example we have PAGE field. If 'A' is bold we would have 3 inlines (runs) in the instruction text and the issue would be observed.

An empty paragraph is exported with different font size than the one coming from its style. The character properties should come from the style system.

Workaround: Add at least one space in each empty paragraph.

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.

Implement import and export of bookmarks to HTML format.

When creating a field with local run properties, those properties are not applied to the field characters and they are left with the default properties.

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.

This is caused by hasSize field in ShapeBase class which is set when decoding the image size. However, when SetWidth and SetHeight methods are called before the size is initialized the value of hasSize is false which causes the issue.

Workaround: Call the Size property getter before calling SetWidth/SetHeight method. See the code below:

// This line workarounds the issue with SetWidth method which does not get the correct size when locking aspect ratio. 
Size size = imageInline.Image.Size;
imageInline.Image.SetWidth(true, width);

Importing shape with missing id attribute leads to NullReferenceException. 

 <v:shape type="#_x0000_t202" filled="false" stroked="false">

The properties applied to the paragraph marker are not respected when evaluating the style of the child elements. That leads to exporting the bullets in a list with their default settings when they are applied to the paragraph properties. The issue is reproducible when exporting to PDF and RTF.


Workaround, applicable when the style of all the bullets in the specific list is the same:

Change the style of the list level:
foreach (var paragraph in this.document.EnumerateChildrenOfType<Paragraph>())
{
    if (paragraph.ListId > -1)
    {
        this.document.Lists.GetList(paragraph.ListId).Levels[paragraph.ListLevel].CharacterProperties.CopyPropertiesFrom(paragraph.Properties.ParagraphMarkerProperties);
    }
}

Importing a document containing a bookmark located in a  structured document tag (sdt) will lead to ArgumentNullException.

When exporting to PDF a paragraph in a list, whose first run is longer than the line, the bullets are rendered with wrong baseline and not aligned with the text.

The default table style is not respected from the style system for character or paragraph properties when exporting to PDF format. It looks only into the default paragraph style.

Steps to reproduce:
1. Create new Table style and set it as default.
2. Apply foreground themeable color with a value from the document theme. Like Accent1
3. Insert a table with some text in it.
4. Export to PDF.
Observed: The text inside the table is not with the color from the document theme.

Importing an image from HTML with URI as a source, which has applied only width or height and exporting it to PDF (which forces getting the image data so it can be drawn) leads to an incorrect value of 1 (a default value) for the dimension that is not specified.

When the document contains an image that is defined as an external resource but is not available in the specified location and cannot be found, a KeyNotFoundException is thrown. Handle this exception and replace the missing image with a default one for such cases. Consider exposing an option to notify the user about this error.

This is happening because the cell with preferred width 100% takes all the available width and all other columns are rendered with no available width which causes the height of the table to grow big.

WORKAROUND: Either clear the cell PreferredWidth property or set it to value which is smaller than 100%.

When the imported html contains an attribute of the type width="", Wordsprocessing throws ArgumentException and does not import the document. 

Although this is not a valid table scenario we should not throw an exception when measuring and exporting such table.

Fix available in LIB Version 2017.3.1218.

HtmlFormatProvider treats <script type="text/javascript"> as document elements and inserts the content (js code) as text in the document.

The issue is observed when CDATA is used as well.

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.

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}".