When a paragraph doesn't have applied a style, the Normal style should be automatically applied. Currently, similar paragraph obtains its style from the parent.

This is reproducible when exporting to PDF and RTF.

Workaround: Check if there is a paragraph without style ID and if so, set it to Normal:

foreach (var paragraph in this.document.EnumerateChildrenOfType<Paragraph>())
{
    var value = paragraph.StyleId;
    if (string.IsNullOrEmpty(value))
    {
        paragraph.StyleId = "Normal";
    }
}

Available in LIB Version 2017.2.731.

In scenarios when center and right tabs are used for aligning the paragraph content to both left and right the text content in the exported PDF is not positioned as expected.

If Paragraph has applied style, and this style has associated list, and the paragraph is removed from the list locally, then on import the paragraph is added to the list.

The additional numbering could be removed from the paragraph by changing its style:

foreach (var p in this.document.EnumerateChildrenOfType<Paragraph>())
{
    if (p.ListLevel == 0)
    {
        var style = new Telerik.Windows.Documents.Flow.Model.Styles.Style("NoListStyle", StyleType.Paragraph);
        style.ParagraphProperties.CopyPropertiesFrom(this.document.StyleRepository.GetStyle(p.StyleId).ParagraphProperties);
        style.ParagraphProperties.ListId.LocalValue = null;
        style.ParagraphProperties.ListLevel.LocalValue = null;
        p.StyleId = "NoListStyle";
    }
}

This setting should allow setting the content between the list level bullet and the paragraph text to some of the following options: "tab", "space", "nothing".

This property allows the user to set the transparency of the image watermark. In the XML, the property is written using the 'blacklevel' attribute of the image.

Add support for shapes with textual content. These are described in OpenXML specification - txbx (Textual contents of shape). 

Such shape can be added to a Word document using the Insert -> Text -> Text Box

The item is closed as duplicate. Please, follow the feature request for shapes at https://feedback.telerik.com/Project/184/Feedback/Details/190116

Add support for character spacing. Currently, such spacing cannot be set and are not imported.

The API should allow the client to navigate to an empty block container and manipulate it.

The block containers are Section, TableCell, Header, Footer, Comment.

The API should also include manipulation methods for a table like:

Add a row to a table.
Add a cell to a row.
Add a table to an empty cell.
Add a paragraph to an empty cell.
Add a run to an empty cell.
add a text to an empty cell.
Move to a next/previous cell.
Move to a next/previous row.

The API should use the currently applied editor formatting when creating the specified document elements.

Introduce support for East Asia fonts.

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.

When paragraphs in list and with hanging indent set are imported from RTF, unexpected values for hanging indent and left indent are imported. The problem is most visible when the document is exported to HTML and visualized in browser, as bullets of the list appear over the content.

Paragraph with a negative left indent and positioned in the header or footer gets clipped when exported to PDF. The same behavior is also observed for paragraphs in tables. Instead, the paragraph should be rendered without clipping.

When a paragraph has defined tab stops in its style and has the same tab stops locally cleared, the tab stops are still respected when exporting to PDF. Instead, cleared tab stops should not be respected.

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> '}'))+ '}'

When list level items are empty - <li></li> - they are not imported as empty paragraphs in list. The expected is that a Paragraph, associated to a list to be imported.

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'.