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 underline style is already applied to a text, the style cannot be changed from the Font Properties dialog.

Workaround: Use the dropdown button in the ribbon.

Steps to reproduce:
- Select text.
- Open FontPropertiesDialog (or use ribbonButton for Undelinetext) and set underline style "Line".
- Submit the dialog.
- Right-click on the selected text again.
- Choose "Font..." from the context menu to open FontProperties dialog again.
- Change the underline style.
- Submit the dialog.
Expected: The selected underline style should be applied.
Actual: There is no applied underline style on the text.

Fix available in R3 2018 SP1 release.

When the focus gets in RadRichTextBox, AutomationProperties.Name is not pronounced by screen readers (for example by Windows Narrator).

Workaround: the automation name could be set to the caret as demonstrated in the attached project.

Images nested in merge fields are imported as raw RTF text which leads to slow performance.

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.

If style is applied to some document elements and this style is deleted through the Change Styles dialog, currently visible document elements (paragraph, spans) are not affected and retain the formatting as if the style is still applied.

Steps to reproduce:
- Add some text
- Select the text and create new style with distinguishable formatting, e.g. red forecolor. The style is applied to the selected text.
- Delete the style
Expected: the paragraph gets Normal style, and its forecolor becomes the default black one.
Actual: the Paragraph has still the custom paragraph styling

Adding a style with a specific name through the dialog, removing it and adding it again through the dialog causes an error. 

When a RadDocument is created programmatically and its layout mode is set to Flow, the export to PDF doesn't respect section properties.

The tab is inserted from the wrong side when the paragraph is with RTL direction.

The invalid document can't be measured and IndexOutOfRangeException/NullReferenceException will be thrown.

Currently, exporting to HTML serializes the containers by exporting them to XAML and adding them in a comment in the HTML. There are InlineUIContainerImporting and InlineUIContainerImported events, but the Handled property of the importing event arguments is read-only. This prevents users from creating their own serialization/deserialization logic.

Steps to reproduce:
1. Subscribe to events of the format provider:

            HtmlFormatProvider prov = DocumentFormatProvidersManager.GetProviderByExtension("html") as HtmlFormatProvider;
            prov.ExportSettings.InlineUIContainerExporting += ExportSettings_InlineUIContainerExporting;
            prov.ImportSettings.InlineUIContainerImporting += ImportSettings_InlineUIContainerImporting;
            prov.ImportSettings.InlineUIContainerImported += ImportSettings_InlineUIContainerImported;

2. Insert inline UI container in the document and export it to HTML. InlineUIContainerExporting event is raised and you can set the CommentContent property of the args to custom value.
3. Import the document back in the control

Expected: It should be possible to set the Handled property of the importing event args to true, and assign your desired value to the InlineUIContainer property.
Actual: InlineUIContainerImporting event is raised, but all properties of the event arguments have private setters.

When a paragraph is styled in HTML format  with line-height it should be with AtLeast line spacing type instead of Exact. 

The same thing happens when the line-height is specified as normal: style="line-height: normal;". 

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

If the main document part of a DOCX document is with name different than "document.xml", for example "document2.xml", the content of the document is not imported. 

Such documents are created by OpenXML SDK, if for example this tutorial is followed:
How to: Convert a word processing document from the DOCM to the DOCX file format - http://tpdogfood.telerik.com/msdn.microsoft.com/en-us/library/office/gg188063(v=office.15).aspx.

RadDocument instance leaks through StylesGallery when RadDocument is set multiple times in a sequence to RadRichTextBox - for example by setting RadRichTextBox.Document property multiple times.

Steps to reproduce:

- Start application containing RadRichTextBox with StylesGallery

- Execute this code on a button click: 

            this.radRichTextBox.Document = new RadDocument();
            this.radRichTextBox.Document = new RadDocument();


Observed: RadDocument leaks through the styles gallery.


Available in LIB version: 2017.1.227

When document is Web layout mode (LayoutMode = Flow), table with LayoutMode = AutoFit is exported to RTF with wrong column widths. MS Word visualize such table splashed, and WordPad extremely large.

Workaround: Performing layout on the document in Paged layout mode seems to fix the issue:

            var doc = new XamlFormatProvider().Import(file);
            doc.LayoutMode = Telerik.Windows.Documents.Model.DocumentLayoutMode.Paged;
            doc.EnsureDocumentMeasuredAndArranged();
            doc.LayoutMode = Telerik.Windows.Documents.Model.DocumentLayoutMode.Flow;

The label for Decimal alignment is truncated.