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

When the document instance is changed (setting RadRichTextBox.Document property to new RadDocument instance), the old document is not released from the memory. There are UI providers, which are not properly removed from the layer's collection.

The issue is regression, introduced in R3 2016.

Workaround 1: Subscribe to DocumentChanging and set the layout mode of RadRichTextBox to Paged. Reset it back to Flow on DocumentChanged.

void radRichTextBox_DocumentChanged(object sender, EventArgs e)
{
    this.radRichTextBox.LayoutMode = DocumentLayoutMode.Flow;
}

void radRichTextBox_DocumentChanging(object sender, EventArgs e)
{
    this.radRichTextBox.LayoutMode = DocumentLayoutMode.Paged;
}

Workaround 2: Remove the WatermarkUILayer. You can achieve that by creating a custom UILayersBuilder. For more information on this approach, check the help article at http://docs.telerik.com/devtools/wpf/controls/radrichtextbox/how-to/features-custom-ui-layers

protected override void BuildUILayersOverride(Telerik.Windows.Documents.UI.IUILayerContainer uiLayerContainer)
{
    base.BuildUILayersOverride(uiLayerContainer);
    uiLayerContainer.UILayers.Remove(DefaultUILayers.WatermarkLayer);
}

Fix available in LIB Version 2017.2.724.

EMF images cannot be natively parsed by the WPF framework and are not supported in RadRichTextBox. Stop the exception so the document can be imported.

Fix available in LIB Version 2017.2.724.

When the LayotMode of RadRichTextBox is set to Flow and a Table is inserted as the first element in this document, the adorner icon is cut off by the document edge and cannot be used.

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.

When the control is used in NoXaml scenario and the required resources are merged in the resources of the Window/UserControl containing RadRichTextBox, XamlParseException is thrown at runtime with a message "Cannot find resource named 'thumbStroke'."
or
the App.Current.Resources.MergedDictionaries is cleared.

Workaround: Merge Telerik.Windows.Documents.xaml and Telerik.Windows.Controls.RichTextBoxUI.xaml in App.xaml.
or
Merge the resourced before initializing RadRichTextBox:
 App.Current.Resources.MergedDictionaries.Add(new ResourceDictionary()
            {
                Source = new Uri("/Telerik.Windows.Documents;component/Themes/Styles/ImageAdornerUIResourcesDictionary.xaml", UriKind.RelativeOrAbsolute)
            });


Fix available in R3 2017 Official Release version.

When some cells are merged in one cell and context menu is displayed for the merged cell, "Merge Cells" option is still available in the menu. However it should not be available for a merged cell.

Selection doesn't work as expected at the end of a Paragraph. If the user holds down the mouse button down and drags just after the paragraph end (in the free space after the last line), the end of paragraph symbol is unexpectedly selected when the mouse hovers the end of paragraph symbol.

Instead, the first letter before the paragraph end should be selected, but only after the mouse hovers it.

Steps to reproduce: 
- Add two paragraphs.
- Click in the empty space just after the end of the last line of the first paragraph, and start moving in direction of opposite to the text flow (left in LTR text case).
Expected: Text is selected only after the mouse passes the first symbol before the paragraph end.
Actual: Paragraph end symbol is selected as soon as the mouse hovers it.

Hyperlink tooltip is not changed when the HyperlinkNavigationMode property of RadRichTextBox is changed.

Workaround: Invoke radRichTextBox.ActiveEditorPresenter.RecreateUI() method just after the property value change:
this.radRichTextBox.HyperlinkNavigationMode = HyperlinkNavigationMode.Click;
this.radRichTextBox.ActiveEditorPresenter.RecreateUI();

Steps to reproduce:
1. Insert a hyperlink in RTB.
2. On button click change the HyperlinkNavigationMode.

Observe: The tooltip is not changed from Click to ... Ctrl + Click to .. and vise versa.

The vertical text alignment in repeated table header row is not consistent with the first row.

Please check the attached screenshot.

Bullets of a list are exported with a character which is not proper for plain text.
The indentation of the bullet is also not exported.

As a workaround, the incorrect bullet character could be replaced with something more suitable. Here is an example:
TxtFormatProvider textFormatProvider = new TxtFormatProvider();
exportedText = textFormatProvider.Export(this.radRichTextBox.Document);
string newText = exportedText.Replace((char)61623, (char)8226);

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.

RadRichTextBox/RadDocumentEditor's MailMerge(bool) method doesn't respect the startEachRecordOnNewPage parameter. When the parameter is set to 'false', records are still merged on different pages, instead of on one.

Workaround: Use RadDocumentMerger to append the resultant documents:
http://docs.telerik.com/devtools/wpf/controls/radrichtextbox/features/merge-documents/append

Available in LIB Version 2017.2.619.

The InsertTable command should copy the current style to all paragraphs in the new table.

Tabs button in Paragraph Properties dialog is visible even when RadRichTextBox.TabStopsPropertiesDialog is not set. In addition, pressing the button in this scenario closes the Paragraph Properties dialog itself.

As this property is automatically set using MEF, this situation could happen if the tabs dialog is missing in the the composition container.

Workaround: Check whether the TabStopsPropertiesDialog is null and if true, then hide the TabsButton:

    var windowTabStopsPropertiesDialog = (this.radRichTextBox.TabStopsPropertiesDialog as RadWindow);
    var windowParagraphPropertiesDialog = (this.radRichTextBox.ParagraphPropertiesDialog as RadWindow);
    if (windowTabStopsPropertiesDialog == null)
    {
        (windowParagraphPropertiesDialog.FindName("TabsButton") as RadButton).Visibility = Visibility.Collapsed;
    }

Words separated by certain punctuation symbols are treated as single word by the "spell check as you type" real-time spell checker.

Steps to reproduce:
Case 1:
1. Type 'testt/mest'.
Expected: The two wrong words should be underlined separately
Actual: The whole text is underlined.

Case 2:
1. Type 'test/mest'.
Expected: Only the second word is underlined
Actual: The two words are underlined

Case 3:
1. Type 'testt/mest
2. Show the context menu by clicking on the second word, and choose spell checking suggestion.
3. Show the context menu by clicking again on the second word.
4. Show the context menu for the first word.
Expected: Context menu contains spell checking suggestions
Actual: Context menu doesn't contain spell checking suggestion

Case 4:
1. Type 'test'mest'.
2. Shown context menu by clicking on 'test'
Expected: Context menu contains suggestion for the whole word - 'testament'
Actual: Context menu contains suggestion for the 'mest'

Case 5:
1. Type 'test.mest'.
2. Shown context menu by clicking on 'mest'
Expected: Context menu contains suggestion for the whole word - 'testament' (this happens if the context menu is shown by clicking on the 'test')
Actual: Context menu contains suggestion for the 'mest' only. Clicking on the suggestion replaces only 'mest' with the suggestion.

Case 6: (the same as Case 2, but with non-breaking space)
1. Copy and paste this text in RadRichTextBox 'testt mest' (the white space in non-breaking space)
Expected: only the second word is underlined.
Actual: both words are underlined as one.

Instead of moving to the same horizontal location in the previous line the caret moves to a location further to the left. If you move the caret with the mouse or arrow keys then the up arrow key works correctly, but if you are actively typing on the current line and hit up arrow the caret usually ends up in the wrong location.

Steps to reproduce:
1. Type line and a half of text in the editor.
2. Without using the mouse, hit the Up arrow key

Expected: The caret moves to the location directly above the current caret position (with the almost the same x-coordinate on the first line).
Actual: The caret moves to the location at the beginning of the first line.

When an application is built with .net version 4.7, the paragraph dialog is clipped in the bottom.