At this point the PdfFormatProvider does not support floating images and these elements are skipped when exporting to PDF.

The feature is trivial for floating images with "Behind Text"/"In Front of Text" settings, but otherwise floating images are affecting the text layout in complex ways.

Add support for shapes, and especially for shapes with textual content. 
In OOXML, shapes are represented by the wps:wsp element, and shapes with textual content by <wps:txbx>, <w:txbxContent>.
Such shape can be added to a Word document using the Insert -> Text -> Text Box -> Draw Text Box, or through a shape's context menu -> Add Text.

Do not confuse these shapes with Text/Rich Text content controls (see https://feedback.telerik.com/Project/184/Feedback/Details/190057 )

At this point, the justify alignment is not supported. Provide the ability to export text with this setting.
This functionality is dependent on PdfProcessing: Provide API for setting the text alignment to Justify

Implement nested mail merge and master-detail scenario.

This feature includes: table of figure, table of tables etc.

TOC field contains PageRef fields inside it. To update it, we will need pagination (layout) support and PageRef fields implementation. Also TOC update can be influenced by TC fields presence in the document.

Implement export to PDF.

Implement support for content controls (a.k.a. Structured document tags), which will allow inserting editing controls in the document:

- Rich Text
- Plain Text
- Check Box
- Combo Box
- Drop-down list
- Date picker

Do not confuse this feature with form fields support (see https://feedback.telerik.com/Project/184/Feedback/Details/219850 ).

The API should allow you to perform a text-based search and return the parent element(s) of the result(s) or directly the found element(s).

The attached sample project below demonstrates a possible workaround for PAGE and NUMPAGES fields when exporting to PDF. The demo shows how to generate document from scratch containing PAGE and NUMPAGES fields and export it to PDF.

Enable the customers to work with .doc files.

In WordsProcessing you could set 

table.Alignment = Telerik.Windows.Documents.Flow.Model.Styles.Alignment.Center;

But when the document is exported to PDF, this is not respected.

Introduce an option to replace a Run text with line breaks and/or new lines or with other document elements such as Table, Image, Paragraph and etc. 

The following code snippet shows how a Run can be replaced with another inline element:

RadFlowDocument document = new RadFlowDocument();
RadFlowDocumentEditor editor = new RadFlowDocumentEditor(document);
 
editor.InsertText("text");
editor.InsertText("REMOVE");
editor.InsertText("text");
 
foreach (Run run in document.EnumerateChildrenOfType<Run>().ToList())
{
    if (run.Text == "REMOVE")
    {
        Paragraph paragraph = run.Paragraph;
        int childIndex = paragraph.Inlines.IndexOf(run);
 
        ImageInline image = new ImageInline(document);
        using (Stream stream = File.OpenRead("example_image.png"))
        {
            image.Image.ImageSource = new Telerik.Windows.Documents.Media.ImageSource(stream, "png");
        }
 
        paragraph.Inlines.Insert(childIndex, image);
        paragraph.Inlines.Remove(run);
    }
}

Respect the Height property of TableRow when exporting with PdfFormatProvider.

The vertical alignment of the table cells is not exported to PDF. The values are always exported with top alignment.

When this type of section break is used, the next section should start on the same page instead on the next one.

Currently some properties are supported only in their shorthand forms, and others - only in their longhand forms:
- 'background' shorthand is not supported.
- 'margin' shorthand is not supported.
- 'padding' shorthand is not supported.
- 'border' shorthand is supported, but 'border-bottom-color', 'border-bottom-style', 'border-bottom-width', 'border-left-color', 'border-left-style', 'border-left-width', 'border-right-color', 'border-right-style', 'border-right-width', 'border-style', 'border-top-color', 'border-top-style', 'border-top-width', 'border-width' are not supported.
IMPORTANT: This feature is available in .NET Core, .NET 6 and above.

Currently, the text is exported but the strikethrough line is not drawn in the exported PDF.

Enable the customers to import SVG images and use them in their documents.

Table and table cell borders are not evaluated according to inheritance and conflict resolution rules. A conflict will occur when different borders from the table and table cell are overlapping. 

The GetActualValue method of the TableBorders and TableCellBorders could potentially return an incorrect value in some of the following scenarios:

Scenario 1:
A table has cell spacing set to 0. Meaning that the table and table cell borders will overlap.
The table borders have defined all of its borders with border style "Single".
The table cell borders have all of its borders defined with border style "None".

Expected result: the resulting borders should have the border style set to "None" for the location where the table and the cell borders are overlapping.

Scenario 2:
A table has explicitly defined that its right border is with border style "None".
The table has a table style applied with defined border style of type "Single" for all table borders.

Expected result: All of the table borders except the right border should have border style of "Single".

The problem is mostly visible when exporting to PDF and RTF format.

TableRow which has defined an only val attribute of the trHeight is imported as a row with auto height. By the specification, this is right, but MS Word takes the val value as row height. Also MS Word exports "At Least" row height with only 'val' set.

Workaround: Iterate through the table rows and set them HeightType to Exact or AtLeast:

foreach (var row in this.document.EnumerateChildrenOfType<TableRow>())
{
    row.Height = new TableRowHeight(HeightType.AtLeast, row.Height.Value);
}

In the document produced by the mail merge, the date time and numeric formatting applied are not respected and the value is in its default format.