By specification this is a sample RTF color table group:

{\colortbl;\red0\green0\blue0;\red0\green0\blue255;\red0\green255\blue255;}


Currently , if there is a whitespace separator (" ") before the tag delimiter (";") an RtfColorTableFormatException is thrown, for example:

{\colortbl ;\red255\green255\blue255 ;\red79\green79\blue79 ;}


Instead, such documents could be easily imported by trimming the whitespace.

Implement export of RadDocument's Bookmarks to PDF's bookmarks.

Currently text in table cell can be oriented only left to right, with horizontal lines flowing from top to bottom. Add support for more text directions - the most common are vertically oriented, i.e. rotated to 90 or 270 degrees.

Implement commands and UI for producing labels using Mail Merge. 

Behind the scenes this is implemented as Table with the proper number of table columns and rows, and eventually (depending on the setup) NEXT field (https://support.office.com/en-us/article/Field-codes-Next-field-3862fad6-0297-411a-a4e7-6ff5bcf178fd?ui=en-US&rs=en-US&ad=US) - so this will eventually require implementing NEXT field.

Note: In MS Word, this is in Mailings -> Start Mail Merge -> Labels...

Add dialog previewing how the content of the RadRichTextBox would be printed according to the current settings.

Workaround: Currently this could be implemented with the public API using separate RadRichTextBox in a window.

This should be similar to the one in HtmlFormatProvider and RtfFormatProvider: Html/RtfImportSettings.FontSubstituting event.

When TrackChanges is disabled and a text is changed, the Copy command should copy the content as all changes are accepted. So, for example, deleted text is not copied.

In MS Word there is a combo box for display mode of the track changes under Review tab. There is a No Markup option which hides the revisions and shows how the document will look in his final variant. Similar to accepting all revisions.

RadRichTextBox should have API allowing to set which user can accept or reject the changes. Currently all users can do this.

When exporting RadDocument to HTML comments are omitted. 

MS Word, for example, adds comments as end notes using JavaScript.

Form fields are the legacy way to insert an editable controls in a document (text boxes, checkboxes, dropdowns) by using the FORMTEXT, FORMCHECKBOX and FORMDROPDOWN fields.

This includes the legacy Frames (described in OOXML with 'framePr' element).

Do not confuse with content controls (structured document tags) (see http://feedback.telerik.com/Project/143/Feedback/Details/113730 ) and with ActiveX controls.

When an action is executed, say delete, and you perform undo, the text that is inserted back in the control is selected. In RadRichTextBox the end position of the selection is brought into view.

Add a way to convert between RadRichTextBox's RadDocument and RadWordsProcessing's RadFlowDocument. 

This will enable integration scenarios between the two products, including using RadWordsProcessing's format providers for import and export.

Add support for the following RTF tags (crop from top, bottom, left, right):

\picropt, \piccropb, \piccropl, \piccropr 

Consider raising an event when the images are finished loading, or an option for loading the images synchronously. 

Implement Mirror margins similar to the option in MS Word.

In MS Word, this is controlled using Page Setup dialog -> Margins -> Pages -> Multiple pages: -> Mirror margins. Another possible options are 2 pages per sheet and Book fold.

Add support for nested track changes revisions. Currently, when a user tries to delete text added by another user, RadRichTextBox simply removes it and does not mark it as a change.

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.

When FlowDirection is set to RightToLeft:

<telerik:RadRichTextBox FlowDirection="RightToLeft" />

RadRichTextBox could work as system's RichTextBox - to layout the text correctly and swap the vertical scrollbar on the left side. Another option to consider is to change the default paragraph style (or 'Normal' style?) to have RTL flow.

Currently, when this property is set, the text gets reversed and the vertical scrollbar stays on the right side.

There is already Author property but it is not filled automatically. It should be filled using the RequestCurrentUserInfo event of the RadDocument, which is currently only used for track changes revisions.