When HTML is imported it may contain invalid images. In such case show the alternative text if there is such text.

The CSS styling for the "p" selector is not imported as a "NormalWeb" style. For example the following:

<style type="text/css">p {margin-top:0; margin-bottom:0;}</style>

should be imported as SpacingBefore and SpacingAfter set to 0 in Normal (Web) style.

TabStopsProperties dialog is non-modal dialog, but it should be modal.

Implement Mirror margins similar to the option in MS Word.

In MS Word, this is controlled using Page Setup dialog -> Margins -> Pages -> Multiple pages: -> Mirror margins. Another possible options are 2 pages per sheet and Book fold.

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.

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

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

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.

"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 exporting RadDocument to HTML comments are omitted. 

MS Word, for example, adds comments as end notes using JavaScript.

The fix will be available in the next official release Q1 2015.

This should be similar to the one in HtmlFormatProvider and RtfFormatProvider: Html/RtfImportSettings.FontSubstituting event.

When floating image is anchored to the first position of the first paragraph on a page, and there are some empty paragraph on the previous page, sometimes the image is positioned on the previous page instead of along the paragraph.

When a custom list is created and applied over different parts in the text (which are separated from text without list), the export to DOCX and RTF format is wrong as the list numbering is not correct. Instead of having several lists starting from index 1, there is only one list with continuing numbering in the exported document.

When the table's background is set, a few lines next to borders appearing in white.