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 large image is set as watermark and the document is exported to PDF, the image is with significantly worse quality.

Spaces in the text are disappearing when several tabs key are added (using the Tab key). In some cases, parts of words are missing (off the visible page) or are reordered.

Steps to reproduce: 
1. Write some words in a line inside a paragraph, set with justified alignment.
2. Press Tab few times, until the caret goes to the next line
Result: The spaces are not visible, some parts at the end of the text disappear. Sometimes the words are reordered.

When a hyperlink is inserted near to a full stop, the spans are reordered.

Steps to reproduce:
1. Write some Arabic text  containing full stop.
2. Select the text after the full stop and insert a hyperlink

Expected: The letters and words preserve their order.
Actual: The letters and/or words are reordered.

Mail merge field is inserted with incorrectly placed and inverted first bracket '{' when the paragraph is RTL.

Workaround: Update the field and then toggle it back to code display mode.

Steps to reproduce: 
- Write something in RTL paragraph.
- Insert mail merge field.
Expected: The field is inserted with its normal form: { MERGEFIELD PropertyName }
Actual: The brackets of the field are incorrectly placed: } <some-RTL-text> MERGEFIELD PropertyName }

The icon of "Font Color" button is wrong in Selection Mini Toolbar. It is the same as the icon of "Text Highlight Color" button. The button itself works properly - changes the color of the font of the selected text.

Current editing style properties are not modified by Font dialog. Also applying through methods of RadRichTextBox or RadDocumentEditor does not work.

Comment references - comments without start and end, just a position in the document, are not imported from docx and RTF document.
RTF: such comments don't have their annotation start ('\atrfstart') and end  ('\atrfend'), and only have '\atnid' tag. In the specification such comments are referred as 'annotation is associated without an annotation bookmark".
Docx: such comments are denoted with 'commentReference' element.

Steps to reproduce:
1. In MS Word, add comment without having a selection in the document.
2. Export the document to RTF or docx.
3. Open the exported document in RadRichTextBox.
Expected: The comment is imported.
Actual: The content is not imported.

When hyperlink is within another annotation so that the outer annotation touches the hyperlink annotation, editing the hyperlink with Insert Hyperlink dialog moves parts of the text of the hyperlink, or the outer annotation. Reproducible with Comments and Bookmarks.

Steps to reproduce:

Variant 1:
1. Insert Hyperlink
2. Enter some text after the Hyperlink (eg. ' Test')
3. Select the Hyperlink and the text and Insert Comment
4. Edit the target of the hyperlink with the Insert Hyperlink Dialog

Expected: The text is not changed.
Actual: Space between Hyperlink and the text is moved before the Hyperlink

------------------------------------------------

Variant 2:

1. Insert three words and make the middle hyperlink.
2. Insert comment or bookmark over the hyperlink
3. Edit the target of the hyperlink with the Insert Hyperlink Dialog

Expected: Annotations are not reordered
Actual: Comment (bookmark) annotations change their places.

When floating image is added to empty table cell, it is positioned in a way that overlaps the table border. 

If there is sequence with more than one font info which is not declared in a separate group, they all are concatenated and recorded in the imported fonts as a single one with id from the last one. Here is such a problematic font table group:

{\\fonttbl\\f0\\froman\\fcharset0 Times New Roman;\\f1\\froman\\fcharset0 Times New Roman;\\f2\\froman\\fcharset0 Times New Roman;\\f3\\froman\\fcharset0 Times New Roman;\\f4\\froman\\fcharset0 Times New Roman;\\f5\\froman\\fcharset0 Times New Roman;}

Documents containing <pre> tag and line breaks (CR LF) cause unexpected visual behavior (loss of content) and invalid layout. Sporadically, document positions seem to also get invalid which leads to exceptions.

InvalidOperationException: 'ColumnSpan must be at least 1.' is thrown when importing HTML document with table column containing colspan="0".

The colspan="0" has special meaning according to the HTML specification http://www.w3.org/TR/html401/struct/tables.html:
-------------------
colspan = number [CN]

This attribute specifies the number of columns spanned by the current cell. The default value of this attribute is one ("1"). The value zero ("0") means that the cell spans all columns from the current column to the last column of the column group (COLGROUP) in which the cell is defined.
-------------------
Workaround: Preprocess the HTML, and delete all occurrences of colspan="0".

When the 'font-family' CSS attribute's value contains Chinese, Japanese or Korean symbols, the HTML parser could not parse them correctly, and the applied font families are skipped. As a result, the text is imported with Arial font.

Steps to reproduce:
- Register the following font "HGS明朝B":
FontFamily myCustomFont = new FontFamily("HGS明朝B");
FontManager.RegisterFont(myCustomFont);
- Write some text and apply the font over the text.
- Export to HTML.
- Import the HTML.

Expected: the text should be with the HGS明朝B font family.
Actual: the text is with Arial font family

There is no document position at the end of a line when a single span is flowing to the next line. Therefore, in similar scenarios, the user cannot move the caret at the last position of the line.

The PreferredWidth property has a strange behavior when set to all columns of a table and one of the rows is with ColumnSpan greater than 1. The width is properly set, but seems to be not respected while measuring the table and its children.


Second Scenario using RichTextBox UI: Create a document containing a table with horizontally merged cells and custom set columns` width and export it to HTML. When importing this HTML document back to the RichTextBox the column width value was not preserved.

Applying negative LeftIndent or FirstLineIndent of a paragraph in web layout mode will visualize the paragraph to the left of RadRichTextBox boundaries.

When classes inheriting RadDocument are exported using XamlFormatProvider, XmlException with message "The prefix 't' cannot be redefined from 'clr-namespace:Telerik.Windows.Documents.Model;assembly=WpfApplication1' to 'clr-namespace:Telerik.Windows.Documents.Model;assembly=Telerik.Windows.Documents' within the same start element tag." is thrown

Similar scenario works with inheriting other elements.

Steps to reproduce:
1. Create an object which inherits the RadDocument
2. Pass the created object as a parameter for the XamlFormatProvider.Export() method
Observe: An XmlException is thrown
Expected: The object to be exported

Loading/editing document with large lists (with 1561 or more items) throws IndexOutOfRangeException when incorrectly tries to convert numbering to letters.

Workaround: Change list type to one which does not include letter NumberingFormat in any of its levels, for example Numbered Hierarchical or custom one.

When the caret is positioned at the beginning of a paragraph with hanging indent and the user press Backspace, the left indent is set to a negative value, the text goes out of the bounds of the document. 

Workaround:
Use the editor's method instead of the command:

private void RadRichTextBox_CommandExecuting(object sender, CommandExecutingEventArgs e)
{
    bool? parameter = e.CommandParameter as bool?;
    if (parameter != null && parameter == true)
    {
        DeleteCommand command = e.Command as DeleteCommand;
        if (command != null)
        {
            e.Cancel = true;
            this.radRichTextBox.Delete(true);
        }
    }
}