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

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.

Currently empty paragraphs are exported to HTML with one space inside. Such paragraphs are not rendered by the browser. Such paragraph should be exported to HTML with one non-breaking space (@nbsp;) inside to ensure that they are visible in the browser.

Workaround: manually add nbsp-s in all empty paragraphs:
paragraph.Inlines.AddRun("\u00a0");


Steps to reproduce:
- Create document with empty paragraphs:

                        var document = new RadFlowDocument();
                        Section section = document.Sections.AddSection();
                        section.Blocks.AddParagraph();
                        section.Blocks.AddParagraph();
                        section.Blocks.AddParagraph();
                        section.Blocks.AddParagraph().Inlines.AddRun("test");

- Export it to HTML.

- Load the HTML in a browser.

Expected: The word 'test' is preceded by 3 empty rows.

Actual: The word 'test' is on the first row.

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;   
}

In case table cell doesn't have directly applied background, it should inherit the background of its parent table.

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 tblGrid property should be exported in order to visualize properly the documents in some viewers. For example, LibreOffice doesn't visualize properly tables  without specified width.

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.