Implement repeating header row for tables when exporting with PdfFormatProvider.

A similar functionality can be achieved using the editing API of RadPdfProcessing. There is attached a project showing a sample implementation. More details are available in the forum post at http://www.telerik.com/forums/repeat-table-heading-after-page-break#kH616fyAKUiDl6WAknUILg

These file formats are very similar to DOCX, and can be easily imported with loss of some information (e.g. macros).

Implement import of PDF to RadFlowDocument, using PdfFormatProvider. This would require text recognition (including determining where paragraphs end as opposed to new line inserted because of the layout) and table recognition.

This will allow conversion of PDF documents to docx, RTF and HTML.

Introduce new section properties which are responsible for defining columns in the section.

Both properties table cell padding and table cell spacing are not exported to PDF format.

Form fields are the legacy way to insert an editable controls in a document (text boxes, checkboxes, dropdowns) by using the FORMTEXT, FORMCHECKBOX and FORMDROPDOWN fields.

Do not confuse with content controls (structured document tags) (see https://feedback.telerik.com/Project/184/Feedback/Details/190057 ) and with ActiveX controls.

Take into account the table row's CanSplit property when exporting to PDF from RadFlowDocument model. Is set to false, the table row should not be split between two pages, if possible.

This property could be set to false, for example, when importing MS Word documents with "Allow row to break across pages" unchecked for some table rows.

The custom document properties enable the users to define their own properties to the document or use one of the predefined. 

In most of the cases, the document variables can be used instead. More information about them you can find at http://docs.telerik.com/devtools/document-processing/libraries/radwordsprocessing/concepts/fields/document-variables

Support for table styles with different properties for first/last row and column, row bandings.

Add support for horizontal lines in documents.

In DOCX, such lines are defined using the legacy VML definitions:
The definitions above and the <hr/> HTML tag are currently not supported and skipped on import, leading to missing horizontal lines in the document.

Add support for import and export of floating tables.

There should be an option allowing users to embed fonts in their documents.

Seems to be applicable for DOCX and RTF, MS Word has such option in File -> Options -> Save.

Add support for INCLUDEPICTURE fields. Such fields should work with nested MERGEFIELD, as this is common scenario.

Workaround: Manually insert images over specific placeholder
RadFlowDocument document = new RadFlowDocument();
RadFlowDocumentEditor editor = new RadFlowDocumentEditor(document);
  
editor.InsertText("1");
editor.InsertText("EXAMPLE_IMAGE");
editor.InsertText("2");
  
foreach (var run in editor.Document.EnumerateChildrenOfType<Run>().ToArray())
{
    if(run.Text == "EXAMPLE_IMAGE")
    {
        Paragraph paragraph = run.Paragraph;
        int indexOfCurrentRun = paragraph.Inlines.IndexOf(run);
        paragraph.Inlines.RemoveAt(indexOfCurrentRun);
  
        ImageInline imageInline = new ImageInline(document);
        imageInline.Image.ImageSource = newTelerik.Windows.Documents.Media.ImageSource(imageData, "png");
        paragraph.Inlines.Insert(indexOfCurrentRun, imageInline);
    }
}

The Indent property of Table is not respected by PdfFormatProvider.

Add support for the All Caps and Small Caps properties of the runs. These properties are currently ommitted on import.

Add support for TextBox shapes.

The property controls whether a paragraph should be rendered at least partially on the same page with the following paragraph when the document is shown in page view mode.

Text frames are paragraphs of text in a document which are positioned in a separate region or frame in the document and can be positioned with a specific size and position relative to non-frame paragraphs in the current document. More information about it is available in section 22.9.2.18 ST_XAlign (Horizontal Alignment Location) of Open Office XML.

When exporting hyperlink pointing to a bookmark, the resultant PDF document should contain Link annotation with destination pointing the bookmark's destination.

One important scenario to cover is the ability to import HTML with hyperlinks to anchors in the documents, and export them as working hyperlinks in the PDF document.