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

This functionality will decrease the size of the exported document.

Add a property that can control whether a table row is allowed to break across pages or not.

MS Word offers "Go To" option in its Find and Replace dialog:

It is reasonable to add similar scrolling behavior when navigating in document, programatic scrolling and GoTo~() methods.

In MS Word, text is hidden using the Home -> Font -> Font -> Effects -> Hidden.

In the Rtf format, such text is preceded (marked) with a '\v' tag. In OOXML, the tag is <vanish/>. The display: none; style from HTML is mapped to hidden text when document is converted to DOCX.

Add support for importing of imaged defined with VML's v:imagedata inside v:image or v:shape. Currently, such images are just skipped.

A possible workaround is to upgrade the documents to a newer DOCX compatibility setting (by re-saving them with MS Word for example), where such shapes are not allowed and are replaced with more modern constructs which the import of RadRichTextEditor supports.

Import the div border settings from HTML. We can create a span with a border in this case. 

Add an option for users to be able to export embedded images as Content IDs.
CID images work by attaching the image to the email sent and then using standard HTML image tags that reference that image to eventually embed it in the email when the user opens it.

These tags define deleted and inserted content to markup updates and modifications in a document. They can be used to export the revisions of a document when Track Changes is enabled.

In some complex script languages, like Telugu and Thai language, some characters are grouped (e.g. consonants + vowels) in new grapheme. 

For example, type 'p' in Telugu - 'జ', followed by 'ో' - they are combined in new grapheme - 'జో', or paste the following Thai grapheme: ชื

UI correctly visualizes this, but:
- Text measuring assumes that the grapheme width is equal to the sum of the widths of its parts (characters), which is not correct. Selection and caret position are scrambled because of this.
- There are document positions between  the grapheme parts (characters), but shouldn't.
- When the caret is before the grapheme, deleting with "Delete" key deletes the grapheme in multiple steps (character by character), but should delete it in single step. Deleting with "Backspace" works correctly.
- There are some unsupported combinations in some languages. For example in Thai, typing 'z' then 'y' will produce grapheme, but typing 'w' then 'y' will not produce grapheme, and the 'y' should be ignored.

 Import/Export of custom attributes to HTML

RichTextEditor: Lists are always exported to HTML with Verdana font. 

Changing the normal style or setting the DocumentInheritsDefaultStyleSettings has no effect.

Add support for DeletePreviousWord and DeleteNextWord commands, triggered with Ctrl+Backspace and Ctrl+Delete keyboard shortcuts.

 Add support for the cstheme (Complex Script Theme Font) attribute and respect it when evaluating the font precedence. 

Add support for vertical (rotated) text in TableCell

Introduce an option to change the character which follows the list level symbol. By default this is a Tab character, however, they can be the following:

- Tab
- Space
- Nothing (none following character)

In OOXML, this is described using the 'suff' element.
In MS Word, this setting could be changed by selecting the bullet/number of the list item -> Context Menu -> Adjust List Indents -> Follow number with:.

 When importing a table from HTML and the content size is larger than the provided size  the table should be auto-fitted.

Provide an option to scale the watermark like in MS Word