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

Check all possible shorthand properties, e.g. border-[left/top/right/bottom]. Also check CSS properties like border-[left/top/right/bottom]-[color/style/width].

Currently HtmlFormatProvider does not export/import tables with alignment (left, center, right).

Add support for All Capitals (All caps) and Small Capitals (Small caps) run property. MS Word has such option in Home -> Font -> Dialog Launcher -> Font -> All Caps/Small Caps.

All letters of such runs are visualized as capital letters.

The corresponding elements in OOXML are <w:caps /> and <w:smallcaps />.

When text is using fonts with defined ligatures (e.g. Calibri, Gabriola, etc.) and contains character groups with defined ligature for it, the text width is measured incorrectly (shorter that it should be). As caret and selection navigates on positions computed by this measuring system, they are not synchronized with what is shown in the UI (which correctly respects the ligatures), and there is slight offset from the real character positions and/or clipping of part of the letters at the end of the line.

Examples of such groups are (depending on the font) "tt", "ff", "ffi".

In MS Word, for example, when you "Save as" PDF, you can choose "options" -> Encrypt the document with a password.

RadDocument instances leak when editing a document containing a field and header/footer. The StyleRepository holds a reference to a style's document element.

Fix available in LIB Version 2017.3.1002.

Handwriting keyboard allows you to enter text with a pen or other stylus. This is currently not implemented in RichTextBox and when you are using handwriting keyboard, the text is inserted more than once when the stylus is lifted while writing.

The default indentation of the list bullets is different when shown in the RadRichTextBox and when exported to HTML and shown in a web browser.
There is a screenshot attached showing how the result is rendered in a web browser.

Implement an option for controlling how the list-style-type of a list will be exported to the HTML format.

After further discussion within the XAML team and more research, we decided that introducing a similar property does not align with the current idea and model of RadRichTextBox. Thus, we are declining this item.

Instead of moving to the same horizontal location in the previous line the caret moves to a location further to the left. If you move the caret with the mouse or arrow keys then the up arrow key works correctly, but if you are actively typing on the current line and hit up arrow the caret usually ends up in the wrong location.

Steps to reproduce:
1. Type line and a half of text in the editor.
2. Without using the mouse, hit the Up arrow key

Expected: The caret moves to the location directly above the current caret position (with the almost the same x-coordinate on the first line).
Actual: The caret moves to the location at the beginning of the first line.

Words separated by certain punctuation symbols are treated as single word by the "spell check as you type" real-time spell checker.

Steps to reproduce:
Case 1:
1. Type 'testt/mest'.
Expected: The two wrong words should be underlined separately
Actual: The whole text is underlined.

Case 2:
1. Type 'test/mest'.
Expected: Only the second word is underlined
Actual: The two words are underlined

Case 3:
1. Type 'testt/mest
2. Show the context menu by clicking on the second word, and choose spell checking suggestion.
3. Show the context menu by clicking again on the second word.
4. Show the context menu for the first word.
Expected: Context menu contains spell checking suggestions
Actual: Context menu doesn't contain spell checking suggestion

Case 4:
1. Type 'test'mest'.
2. Shown context menu by clicking on 'test'
Expected: Context menu contains suggestion for the whole word - 'testament'
Actual: Context menu contains suggestion for the 'mest'

Case 5:
1. Type 'test.mest'.
2. Shown context menu by clicking on 'mest'
Expected: Context menu contains suggestion for the whole word - 'testament' (this happens if the context menu is shown by clicking on the 'test')
Actual: Context menu contains suggestion for the 'mest' only. Clicking on the suggestion replaces only 'mest' with the suggestion.

Case 6: (the same as Case 2, but with non-breaking space)
1. Copy and paste this text in RadRichTextBox 'testt mest' (the white space in non-breaking space)
Expected: only the second word is underlined.
Actual: both words are underlined as one.

Case 1:
Deleting selected part from the beginning of a comment range causes the caret to appear on the next document position than the expected one.
Steps to reproduce:
- Load a document with annotation ranges
- Select from the start of the annotation ranges into the first word in the range
- Hit delete/backspace or call Delete() on the API
- The cursor will end up one position too far to the right after the content is removed

Case 2:
Annotation Ranges where SkipPositionBefore is set to false on the AnnotationRangeEnd cause caret position to jump when deleting content to the right of the Annotation Range.
Steps to reproduce:
- Open a document with Annotation Ranges where SkipPositionBefore is set to false on the AnnotationRangeEnd (the Document Protection sample in the demo app can be used)
- Move the caret to the end of the range.
- Hit the delete key
Expected: The caret remains at the end of the AnnotationRange and content to the right is deleted.
Actual: Content to the right is deleted but eventually the caret will jump to the right by one position and end up outside the Annotation Range.

Permission's range bracket disappears when it is positioned on the last line of the page.

The pgMar element might be present but the margin information might be missing as shown below:
<w:pgMar w:header="720" w:footer="720" />
At the moment this overwrites the section margin information with 0. Instead the margins should remain as is.

Fix available in LIB Version 2018.2.820.

Add "Show Grid Lines" command. The command should visualize all table borders, including the invisible ones.

RadRichTextBox: Add import/export in the following formats: .mht .odt .epub .doc