Implement evaluation of = (Formula) fields (https://support.office.com/en-us/article/Field-codes-Formula-field-32d5c9de-3516-4ec3-80ed-d1fc2b5bc21d?ui=en-US&rs=en-US&ad=US ). This will allow export to PDF and HTML.

The alternative text allows setting a description of the information contained inside the table and is useful for people who may not be able to see the content.

Extend the support for em units. Em is calculated relatively to the font-size style property.

There are 27 types of border styles in the Open XML specification and they are implemented in RadFlowDocument. Part of the borders are already supported (eg. None, Single, Dotted) when exporting to HTML, all others are treated as None and stripped.

The HTML format doesn't support all types of border styles OOXML format supports.

When importing a simple table from HTML in Ms Word, it gets applied table cell spacing and margin. This makes it look more in the manner it does in a browser, i.e. the content of cells is vertically centered.

Check for TableCell, TableRow, and Table.

Provide support for import and export of Fields to HTML format.

Currently, the Float property is not supported and it is skipped on import.

Currently, ImportSettings allows importing a single stylesheet only. Users should be able to specify and load several external stylesheets.

Add Mail Merge events.

Preserve Footnotes/Endnotes information.

Create a feature that allows the RadWordsProcessing to split RadFlowDocument.

Workaround: DocumentElementImporter can be used to prepare a document element from the source document for import into the target document

The RowSpan and ColumnSpan properties change the size of the cells so they occupy the desired number of rows/columns but doesn't merge them with other cells. It would be more convenient for the customers to have an option to directly merge or split cells.

Introduce an option to implement custom field in RadFlowDocument model (one which is not supported by the document model).

In the current implementation the abstract Field class has internal abstract method which is responsible for the GetFieldResult() method and this leads to an issue when a customer wants to implement a field which we currently do not support (CustomCodeField which returns null as a result fragment).

The property controls whether all the lines of a paragraph should be rendered on the same page when the document is shown in page view mode.

When an image is moved to a location, different than the default one, this setting is not respected due to the missing margin property.

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

Allow insertion of Equations and Formulas. The feature can have merge fields inside the equations.

Introduce support for East Asia fonts.

In OOXML, table row can define table properties named 'table level property exception' using 'tblPrEx' element. These properties shall be respected by the row instead of the table properties defined on table level.

Add similar property in the TableRow model and respect it in the corresponding exports.

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.