When paragraph contains only merge fields (and eventually whitespaces), and all of these fields are evaluated to empty string for particular data record, the paragraph could be removed from the merged document.

Example: The document contains two paragraphs:
<<FirstName>>
<<LastName>> <<Address>>

For particular data record, LastName and Address are empty, so the merged document for this data record will contain only one paragraph (the first one). This behavior is expected from customers, as it's implemented by MS Word.

Implement import of bullets and numbering which use the old Word 6.0/Word 95 format from RTF. This includes, but is not limited to, the following RTF tags: \pnlvlN, \pnlvlblt, \pnlvlbody, \pnlvlcont. See RTF specification, "Word 6.0 and Word 95 RTF" heading for full description.
WordPad and some legacy systems export lists with this formatting, so the construction is relatively widespread.
According to the specification, if RTF reader doesn't support specific bullets/numbering tags, it can use the \pntext tag to read the bullets/numbering as plain text; but currently WordsProcessing always ignores the \pntext tag. Because of this, the bullets or numbers of lists in the old format are missing after import.

At the moment when a Floating Image is exported to HTML, it is exported as inline and its position is lost.

When the current position is in the middle of a paragraph and the InsertSection() method is invoked, it should automatically split the content at the current position and transfer the content that is on the right side of the position to the new section along with all the following blocks. 

At this point, the method transfers only the content of the current paragraph and, if the section has following paragraphs, they are left in the "old" one.

The exception is thrown because we try to export a tblGrid element, but currently we do not support this: https://feedback.telerik.com/Project/184/Feedback/Details/190082-wordsprocessing-export-tblgrid-table-grid-property-for-table-elements

Add support for exporting hyperlinks which are not valid URIs to PDF. Currently such hyperlink URIs are not exported to the PDF document.

Example of such hyperlink is "mailto:abc%20abc-abc-abc%20%3cabc@abc.com%3e" (mailto:abc abc-abc-abc <abc@abc.com>), but there could be more types. Currently the internal API relies on creating instance of the system Uri class, which is not possible in this case.

Enable the customers to add digital signatures to the documents and read signed documents.

The calculations are wrong, leading to single lines on a page. As a result, the content of the PDF document is laid out on a bigger number of pages.

Workaround: Change the line spacing and its type before exporting to PDF:

foreach (var paragraph in this.document.EnumerateChildrenOfType<Paragraph>())
{
	HeightType? heightType = paragraph.Properties.LineSpacingType.GetActualValue();
	if (heightType == HeightType.Exact || heightType == HeightType.AtLeast) 
	{
		paragraph.Properties.LineSpacingType.LocalValue = Telerik.Windows.Documents.Flow.Model.Styles.HeightType.Auto;
		paragraph.Properties.LineSpacing.LocalValue = 2;
	}
}

Special chars (åäö) with PdfFormatProvider wont work.

Project submitted!

    public void SpecialCharsTest()
        {
            RadFlowDocument document = new RadFlowDocument();

            RadFlowDocumentEditor editor = new RadFlowDocumentEditor(document);

            editor.InsertText("Before text");
            editor.InsertText("åäö ÅÄÖ ☕"); // This line will not appear in the pdf 
            editor.InsertText("After text");
            using (Stream output = new FileStream("specialCharTest.pdf", FileMode.OpenOrCreate))
            {
                PdfFormatProvider provider = new PdfFormatProvider();
                provider.Export(document, output);
            }
        }

Special characters wont work :-/

Borders are not correctly imported from HTML.

Workaround: Set borders in code:

var tables = document.EnumerateChildrenOfType<Table>();

var border = new Border(1, BorderStyle.Single, new ThemableColor(Colors.Black));

foreach (var table in tables)
{
    table.Borders = new TableBorders(border);

    foreach (var row in table.Rows)
    {
        foreach (var cell in row.Cells)
        {
            cell.Borders = new TableCellBorders(border);
        }
    }
}

There is a discrepancy between RadWordsProcessing and MS Word:

row.Height = new TableRowHeight(HeightType.Exact, image.Image.Height);