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;
        }

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;

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;
    }

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

Available in LIB Version 2017.2.619.

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

Please check the attached screenshot.

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.

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

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.

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.

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

Currently, the document won't be imported due to an exception when decoding the base64 string image source. The expected behavior is the document to be imported and the image to be shown as a missing image.

Available in LIB Version 2017.2.731.

When word contains non-letters symbols at its start and/or end, it's always considered incorrect by the spell checker, even when it's present in the spell checking dictionary. The most common case is with abbreviations like "dr.", which should be invalid when are typed without the period ("dr"), but valid otherwise ("dr.")

Partial workaround: add the word without the punctuation to the dictionary. The problem is that the word without the punctuation will also be considered correct.

Hi Team,
              I am sending one html body to outlook 2013 which contain bulletedlist, till my desktop app its bullets are looking ok. but after sending it to outlook new email body, there are too much space between bullet and inline text, please provide input, how can i handle it.
I think my bullets having different pattern which outlook 2013 doesn't support.
Do i need to add any other property background position : inside; something like.


Please find the attachments,
Thanks
Deepak

The MoveToCurrentWordEnd will move to a character before the last position when called from the last position in a word and the word is surrounded by annotations.
The MoveToCurrentWordStart will move to the previous word when called from the first position in a word and the word is surrounded by annotations

The behavior is also unexpected for MoveToFirstPositionInParagraph, MoveToLastPositionInParagraph. 

There is no translation in the different languages.

Available in LIB Version 2017.2.828.

ChangeFontHighlightColorCommand, ChangeParagraphBackgroundColorCommand, ChangeFontForeColorCommand and ChangeUnderlineColorCommand does not apply the color when invoked with string containing the name of the color as parameter, e.g. 'red'.

Available in LIB Version 2017.2.828.

An OutOfMemoryException is thrown on export to PDF when the compression mode is set to Deflate.


Regression, introduced in R1 2017.

Workaround: Change the ImagesCompressionMode to one of the other available options to avoid using the Deflate

Empty paragraphs are always exported with one empty span containing   When you apply styling like highlight color the span with   will be with background. Which is not the behavior in RTB.

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