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.

When the preferred width of the table is set to a percentage value and the columns inside have preferred width values in pixels, the bigger width should take precedence when showing the table. At this point, the table column widths are with higher priority.

When the main container of a window is ScrollViewer, the caret is not kept in the view while users move it with the arrow keys.

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. 

When typing in RadRichTextBox, the characters appear in the document with slight delay.

If the font applied to text doesn't contain Bold or Italic typefaces, the text at the end of the line is clipped.

Workaround: Switch to the old rendering mode (which is somewhat slower):
this.radRichTextBox.TextRenderingMode = TextBlockRenderingMode.TextBlockWithPropertyCaching;

 ArgumentException is thrown when a missing image with no width and height is imported from HTML format.

Steps to reproduce:
1. Import the attached HTML.
2. Wait for a few second for loading the image.

Actual: An ArgumentException is thrown for setting the width or height of an image to an infinity.

Fix available in LIB Version 2017.2.522.

DocumentRuler.CreateHorizontalRuler and DocumentRulerCreateVerticalRuler properties are not always changing the visibility of the horizontal and vertical ruler when set to false. If the properties are set to false in XAML, the corresponding ruler parts are still visible.

The problem is that the values of the properties are reset internally during the controls creation, and after the layout mode of the document is changed.

Workaround: Set the properties in code behind, and reset them after layout mode change:

        public MainWindow()
        {
            InitializeComponent();

            this.ruler.CreateHorizontalRuler = false;
            this.radRichTextBox.DocumentLayoutModeChanged += (sender, e) => this.ruler.CreateHorizontalRuler = false;
        }

Bullet with a big font-size applied is not horizontally aligned with the rest of the bullets of the same level.

Steps to reproduce:
1. Add several paragraphs.
2. Apply a list to the paragraphs.
3. Select a paragraph in the middle.
5. Apply a big font-size, like 24.
6. Export to HTML.

Actual: The bullet with the bigger font-size is not horizontally aligned with the rest of the paragraphs.
Expected: All paragraphs should be horizontally aligned

A custom list applied to several paragraphs is not exported to HTML format with the required font-family and font-size.

Steps to reproduce:
1. Create a custom list with custom font-size and custom font-family. (different from the default).
2. Apply the list to several paragraphs.
3. Set the StylesExportMode property of the ExportSetting of the HtmlFormatProvider to StylesExportMode.Inline (fp.ExportSettings.StylesExportMode = StylesExportMode.Inline)
4. Export to HTML.

Actual: The bullets are exported with the default font-family Verdana and the default font-size.
Expected:  The bullets to be exported with the custom value for the font-family and font-size.