"Increase Indent" and "Decrease Indent" buttons in the Ribbon (the same commands are invoked when Tab is pressed in specific situations) apply different indent step to the selected paragraphs, depending on the number of selected paragraphs: 
- when applied on one paragraph, the indentation is changed with 18.0 px. 
- when applied on two paragraphs, the indentation is changed with 36.0 px.
- and so on.

When a preceding paragraph's size is increased, for example - font size is changed, or paragraph is split to two, then the selection of the consequent paragraphs is wrong. When the cursor is on the second line and attempt to select some part of it with the mouse is made, the first or the third line is selected.

Steps to reproduce: 
1. Create two paragraphs with multiple lines
2. Insert new paragraph after the first paragraph
3. Try to select second line of the third paragraph with the mouse

Observed result: First line is selected instead of second line being selected

When floating images are placed in a header or footer, and are positioned outside of the text editor's area, they are not visualized. 

MS Word visualizes such images as slightly grayed out (similar to watermarks) in normal mode, and always visualizes them in Header/Footer edit mode.

This item is merged with another one concerning the same issue. Please, follow the item at https://feedback.telerik.com/Project/143/Feedback/Details/174624 .

Add support for Widow/Orphan control property of Paragraph. In Open XML specification, this is named "widowControl (Allow First/Last Line to Display on a Separate Page)".

The problem is that as this property is not supported, RadRichTextBox acts as it's 'false' and also doesn't export it, but the default value is actually 'true', which causes layout differences between RadRichTextBox and MS Word.

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.

If nested comments are present in the document, the end users cannot delete the nested one. If they put the caret inside the inner comment, or even inside the balloon associated with the inner comment, and press "Delete Comment", the most outermost comment is deleted instead of the current one.

Workaround is to enumerate the fields and update them separately.
            foreach (var field in this.radRichTextBox.Document.EnumerateChildrenOfType<FieldRangeStart>())
            {
                this.radRichTextBox.UpdateField(field);
            }

Workaround: Caret could be changed with custom implementation. More information could be found in this help article: http://docs.telerik.com/devtools/wpf/controls/radrichtextbox/ime-support#how-to-implement-your-own-ime-support

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.

Text containing mixed Right-to-Left and Left-to-Right parts are visualized incorrectly - some of the punctuation marks swap their places.

Partial workaround: Use RadRichTextBox's TextRenderingMode = TextBlockWithPropertyCaching. This mode also has problems, but it works in some cases.

Performance of scrolling and editing is diminished when Track changes are enabled.  Issue seems to be related to RevisionsToolTipLayer and occurs when more than a couple of paragraphs are inserted in the same revision.

Workaround: remove the UI layer responsible for tooltips of revisions.

    [CustomUILayersBuilder]
    public class CustomLayersBuilder : UILayersBuilder
    {
        protected override void BuildUILayersOverride(IUILayerContainer uiLayerContainer)
        {
            uiLayerContainer.UILayers.Remove(DefaultUILayers.ToolTipLayer);
        }
    }

In Word, slashes, dots, etc. are treated as separate words when moving the caret with Ctrl + Key.Right and Ctrl + Key.Left.

The fix is available in our LIB release (v. 2014.3.1208)

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.

The fix will be available in our official release Q1 2015.

The fix will be available in our official release Q1 2015.

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. 

Exporting document containing Hebrew text to PDF results in correct text (letter-by-letter), but with wrong text flow: letters in the words are inverted and flow left-to-right instead of right-to-left.