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.

Implement repeating header row for tables when exporting with PdfFormatProvider.

A similar functionality can be achieved using the editing API of RadPdfProcessing. There is attached a project showing a sample implementation. More details are available in the forum post at http://www.telerik.com/forums/repeat-table-heading-after-page-break#kH616fyAKUiDl6WAknUILg

It would be nice to have the ability to search text in documents.

Use case:
I needed to replace some keywords with images. I can insert image at the current position, but there is no way to insert it after some text.

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

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.

When table cell preferred width is smaller than the first word in the cell the actual exported width should fit the word width when exporting to PDF. 

Currently in such case the word is split into two lines. The width has to be equal to the word width so the word stays on a single row.

When a style doesn't have explicitly defined font, the font from the default character properties (\defchp) is used when present. Instead, the font used for the style should be the default font for the document, defined with \deffN tag.
The same issue occur when the doesn't contain \defchp at all. In this case, the font for the style is not imported, but instead the defined with  \deffN tag should be used.

The construction is not common, and MS Word for example doesn't produce such documents.

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

Content is moved from the second page to the first after applying styling to the footer and exporting to PDF format

This is done due to wrong column widths weights calculations.

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.