The font size in the table does not respect the CSS for the corresponding class. There is similar issue with <li /> element. 

Style properties defined in an element style selector are evaluated with higher priority over properties in a CSS class when importing from HTML.

For example if we have the following CSS style:

.sectionheading {
border: 10px solid red;
        }
td {
border: 10px solid black;
        }
and the class (.sectionheading) is applied on a table cell:

<td class="sectionheading">...</td>

The result in WordsProcessing after import of such HTML will be that the table cell has 10px black border. In MS Word and in the browsers (Chrome, Firefox...) the result will be that the cell has 10px red border.

KeyNotFoundException is thrown when importing RTF document where single font info is not declared in group, for example the following RTF doesn't work:
{\rtf1\ansi\ansicpg1250\deff0{\fonttbl\f0\fswiss Helvetica;}\f0\pard test\par}

while the following works:
{\rtf1\ansi\ansicpg1250\deff0{\fonttbl{\f0\fswiss Helvetica;}}\f0\pard test \par}

This is valid according to RTF specification, which allows omission of the group when only:
<fonttbl>  '{' \fonttbl (<fontinfo> | ('{' <fontinfo> '}'))+ '}'

The paragraphs in RadFlowDocument can have paragraph borders. These borders are not exported when exporting the document to PDF. 

Table's 'cellspacing' and 'cellpadding' are not imported from HTML when the unit is not specified, e.g. <table cellpadding="25">. According to the HTML Specification (https://www.w3.org/TR/REC-html40/struct/tables.html#adef-cellspacing), the only permitted values are:
- only number
- number followed by percent.

MS Word imports it according to the specification (like WordsProcessing), but all of the browsers successfully imports values even with the px suffix, e.g. '25px'.

If the Table's TableCellSpacing property is not divided by 2 when the document is exported to Docx or Rtf, this leads to incorrect rendering after the exported document is opened with another editor (RadRichTextBox, MS Word).

Workaround: Divide by two the Table's table cell spacing property value before export to Docx, RTF formats:
foreach (Table table in document.EnumerateChildrenOfType<Table>())
{
    table.TableCellSpacing /= 2;   
}

When a document produced with WordsProcessing is validated with OpenXML Validator from OpenXML SDK, errors are found.

While documents are valid according to the specification, Open XML SDK Validation shows errors related to the order of elements, etc. Resolve all errors, so DOCX documents pass validation.

The item is closed as duplicate. Please, submit your votes and subscribe for notifications to the item at https://feedback.telerik.com/Project/184/Feedback/Details/190053-wordsprocessing-support-for-importing-dotm-dotx-and-docm-files.

The item is duplicated. Please, follow the item at https://feedback.telerik.com/Project/184/Feedback/Details/203066

Span or paragraph style properties are not evaluated correctly when the paragraph is inside a table and there are no other local values than the one applied in the table style.

This could lead to different rendering of the document when exporting to RTF, PDF and HTML formats.

Table's layout type is imported as FixedWidth when it should be imported as AutoFit. The following RTF tags are not respected:

trftsWidthN
trwWidthBN
trftsWidthBN
trwWidthAN
trftsWidthAN
trwWidthtrftsWidthN

The AltChunk element is responsible for embedding external content into documents.

When an image is moved to a location, different than the default one, this setting is not respected due to the missing margin property.

All character formatting (font size, font family, etc.) applied to empty cell is lost when:

- document with such formatting applied is exported to RTF

- document with such formatting is imported from RTF.

In MS Word, decimal tab stops affect paragraph layout in table cells even if tab character is not present. The reasoning is that it's hard to insert tab symbol in table cell, as pressing Tab navigates to the next cell (Ctrl+Tab should be used). 

When decimal tab stop is present for a Paragraph, and the paragraph is in a TableCell, the content of the paragraph should be aligned to the decimal tab stop (analogically to the case when the Paragraph is not in a table cell and it contains tab character.

The text of the watermark is exported with the default font family due to incorrect escaping while writing the OpenXML.

Bookmark starts and ends that are not the child of a paragraph or table cannot be imported.