Implement nested mail merge - creating mail merge reports using master-detail tables in a data source.

Typical example of this is creating an invoices with mail merge, where each invoice contains a list of items.

Workaround: for some scenarios creating custom merge field which evaluates to Table could simulate this behavior:
http://www.telerik.com/forums/merge-reports#lUdH39ww00SnEhTLLlrXwA

When a table cell contains nested table, and the paragraph after the nested table is empty, this paragraph could be collapsed, as in MS Word. This gives better look to nested tables, similar to how browsers visualize nested HTML tables.

Note that the paragraph should be visualized when the caret moves the position inside the paragraph.

Currently the paragraph is visualized with its full height, making the layout different than MS Word - it appears that there are redundant space after the nested table.

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.

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".

Add support for importing of imaged defined with VML's v:imagedata inside v:image or v:shape. Currently such images are just skipped.

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.

A custom list has numbered list, which refer style and the style refer numbered list. If the second numbered list is not imported before importing the first the import will fail.

ArgumentException ("referenced document list does not exist."); is thrown and handled internally. It is caused by linked list styles. The style which refers other is imported before the referenced style. The RichTextBox expects that referred styles are imported before the styles that refer them.

Available in R3 2018 Official Release Version.

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

Adding support for exporting font style as font tag. Android's TextView for example support styling only using tags.

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.

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.

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

Add ability to combine revisions from different authors into a single document.

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.

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 }

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.

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

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 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.