Implement support for content controls (a.k.a. Structured document tags), which will allow inserting editing controls in the document:

- Rich Text
- Plain Text
- Check Box
- Combo Box
- Drop-down list
- Date picker

Do not confuse this feature with form fields support (see http://feedback.telerik.com/Project/143/Feedback/Details/146869 ).

Add support for shapes, and especially for shapes with textual content. 
In OOXML, shapes are represented by the wps:wsp element, and shapes with textual content by <wps:txbx>, <w:txbxContent>.
Such shape can be added to a Word document using the Insert -> Text -> Text Box -> Draw Text Box, or through a shape's context menu -> Add Text.

Note: Do not confuse with Text/Rich Text content controls (https://feedback.telerik.com/Project/143/Feedback/Details/113730 ).

- There should be a formatting symbol for the character

- Pressing Ctrl+Shift+Space should insert the character (standard MS Word shortcut)

- Import from docx should be implemented

- The symbol should be treated as a separator between words when spell-checking

It should be possible to have several columns in a section of the document. These columns should also be persisted on export/import.

Add support for line numbering in paged layout mode, similar to MS Word.

RadRichTextBox doesn't support most used Chinese IMEs - QQ Pinyin and Sogou Pinyin.

Support for file formats other than .TDF is required, so that a broader range of dictionaries can be used. Consider adding support for OpenOffice dictionaries.

This will reduce the resulting PDF documents' size drastically.

Create different options for pasting(keep formatting, merge formatting, use destination styles). At this point, the document default styles are not copied in the document fragment, thus their loss is observed. 

When DocumentInheritsDefaultStyleSettings is true and the font settings are like set to different font size/font family, copied text is pasted to MS Word with Verdana font, size 12. Loss of formatting is also observed when copying from RadRichTextBox and pasting in MS Word - the default styles differ.

Copy formatting from one place in the document and apply it to another.

Available in R2 2018 Official Release version.

When the caret is positioned in the beginning of a paragraph and a table is inserted, an additional paragraph before the table should not be added. This also includes the case with a blank document.

Special case: When there is a table in the document, inserting another just after it should be disabled.

This field retrieves a character through a code value specified in the field-argument. Such documents are common and are created when symbols (e.g. with font Windings through Insert -> Symbol dialog) are inserted in RTF documents in MS Word. 
This functionality is also used when content containing <sym> element is copied from DOCX and pasted in RadRichTextBox - as the content is converted to RTF containing SYMBOL field during the operation.

Workarounds: 
- Implement such field with the API, see the documentation article (http://docs.telerik.com/devtools/wpf/controls/radrichtextbox/features/fields-and-document-variables/custom-fields ) and the SDK example (https://github.com/telerik/xaml-sdk/tree/master/RichTextBox/CustomField/ ). Note that MS Word doesn't show field menus for these fields in RTF documents.
- If RTF format is used and you have control over document creation, save the documents initially as docx, and then save them to RTF. This way the symbols will be encoded without the SYMBOL field construct, and are successfully imported in RadRichTextBox.

Available in R3 2018 Official Release.

Select current style (the style in the selection or under the caret) in styles gallery when selection or caret position is changed. 

Currently HtmlFormatProvider does not export/import tables with alignment (left, center, right).

Currently, when a page break is added to the document, the paragraph is not split in two. 
It will be better to split the paragraph and add one additional paragraph in order to achieve a more consistent look of the document when applying a style, adding one of the paragraphs to a list or having different first line/hanging indentation of the paragraphs.

Currently, ParagraphDefaultSpacingAfter and ParagraphDefaultSpacingBefore are not applied to paragraphs in tables. This should be changed for consistency with the rest of the document.

When a color property has default (auto) value, do not export a tag which points to omitted defintion in the color table. For example, if a span has transparent highlight (the default one), do not export the \highlight tag since this might lead to some incorrect rendering of the document from other readers - WordPad for example.

Some customers need special annotations to determine that the content between them should not be spell checked and they should/shouldn't be treated as word separators.