The bullet should be aligned next to the paragraph unless another setting is explicitly applied.

Making headers and footers read-only or invisible is possible, but there is no way to prevent focusing them.

Add support for Eastern Arabic Numerals in list level bullet text: https://en.wikipedia.org/wiki/Eastern_Arabic_numerals

Allow the custom fields inserted in a child document, like header/footer/comment etc, to access properties from the main document of RadRichTextBox.

RadRichTextBox always shows more than one page when there is enough space on the screen to render them next to each other. Expose an option to show one page view.

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.

Add support for associated character properties when importing from RTF. Such properties are 
\rtlch, \ltrch, and the associated control words like \afN, \loch, \hich, and \dbch.
Currently, runs/bullets with such properties set could be imported with different character properties.

Workaround: Use the supported \f tag for the most common low-ANSI characters, for example by:
- doing the following replaces in the source document:
\loch\af -> \loch\f
\dbch\f -> \dbch\af
- (Possible workaround) Re-saving the document with MS Word

The bullets can have their own alignment. Implement import and export of this setting.

Current implementation of Text UI automation pattern doesn't support obtaining the attributes of the selection, e.g. bold, italic, etc.

The API allows returning custom ITextRangeProvider where the behavior could be implemented , but this requires a lot of work. 

If this is built-in, the API will allow getting the attributes as follows:

            var automationPeer = (RadRichTextBoxAutomationPeer)FrameworkElementAutomationPeer.FromElement(this.radRichTextBox);
            TextPattern textPattern = (TextPattern)automationPeer.GetPattern(PatternInterface.Text);

            object isItalic = textPattern.GetSelection()[0].GetAttributeValue(TextPattern.IsItalicAttribute);
            if (isItalic == TextPattern.MixedAttributeValue)
            {
                // mixed
            }
            else
            {
                bool italic = (bool)isItalic;
            }

Currently, AutomationElement.NotSupported is always returned.

Currently exported DOCX document may be visualized by MS Word with different highlight colors. There is a limitation in the document format which RadRichTextBox doesn't respect, and this could be avoided by unifying the palette in RichTextBox's UI with the one in MS Word.

In RadRichTextBox, the highlight color picker has more colors than the one in MS Word. That is why when exporting paragraph with one of the additional colors, MS Word (the DOCX format) won't use it but will fallback to one of the available colors.

Some customers are complaining that when the mini toolbar is shown, it is semi-transparent - they expect to be fully shown. Currently, this behavior cannot be customized. Think of adding some setting about how this toolbar will be visualized.

Implement hyphenation in RadRichTextBox for different languages. 

Some fonts doesn't include bold and italic font styles. Currently text formatted with such fonts and with applied bold or italic formatting is exported without the italic or bold effect. Instead, the default typeface can be exported, and additional transformation could be applied to the letters itself - e.g. skew transform for the italic.

Implement an option for controlling how the list-style-type of a list will be exported to the HTML format.

MS Word clears the character style property of a span when a new value equal to the default value is applied. This is applicable only when the span or the parent paragraph does not have associated style which has a local property defined for the same style property.

The normal hyphen should break the line and the non-breaking hyphen (inserted with: alt+0173) should not break the line

Handwriting keyboard allows you to enter text with a pen or other stylus. This is currently not implemented in RichTextBox and when you are using handwriting keyboard, the text is inserted more than once when the stylus is lifted while writing.

The dialog should match the strings contained in the different document parts (headers, footers, footnotes, endnotes, comments).

In Office Open XML documentation there is element named "AlternateContent" which can contain image. Currently the content inside the AlternateContent element is skipped. 

The customers need to convert the position to an integer number representing the offset of the current position from the first position in the document. A method returning the position at a specified offset would be useful as well.