Add support for setting and exporting document metadata, like Title, Author and similar.

The issue is reproducible only in a specific setup with a specific document. It is related to the calculations of the line spacing when the table row should be split between two pages.

Workaround: Change the line spacing:
foreach (var paragraph in this.document.EnumerateChildrenOfType<Paragraph>())
{
    paragraph.Properties.LineSpacingType.LocalValue = HeightType.Auto;
    paragraph.Properties.LineSpacing.LocalValue = 1;
}

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 importing the text values of the input element. They could be imported as a simple text to preserve the content.

The exception is thrown because the AltChunk element is added for import, but we currently do not have implementation for importing of AltChunk elements: https://feedback.telerik.com/Project/184/Feedback/Details/190095-wordsprocessing-add-support-for-altchunk-element

The theme xml element (root of the theme.xml part) has a name property which is optional. However, WordsProcessing throws an exception when it doesn't find a name.

When a document has a deleted text as part of track changes and there is a comment on the deletion, the document throws InvalidOperationException upon import.

In addition to the values containing numbers, the font-size property can have one of the following values as well: medium|xx-small|x-small|small|large|x-large|xx-large|smaller|larger|initial|inherit;
At this point, HtmlFormatProvider skips these values and applies default font-size to the content.


To import similar content with the proper styling, the customer can replace the CSS keywords with their equivalents in px.

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.

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

When a document with ordered list is exported to RTF and opened with WordPad or WinForms' system RichTextBox the numbers of the list are replaced by "{0}".

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.

A NullReferenceException is thrown when importing a hyperlink that doesn't contain any run elements. Similar hyperlinks could be skipped so the document can be successfully imported. 

Available in R3 2018 SP1 release.

HtmlFormatProvider treats <script type="text/javascript"> as document elements and inserts the content (js code) as text in the document.

The issue is observed when CDATA is used as well.

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.

When MergeField is present in the document, and this merge field is evaluated to an empty string - this, for example, happens when the property in the data source is set to null, empty string, or is missing at all - the result fragment remains in the result document. Instead, it should be removed.

Steps to reproduce: 
- Create document with merge field, the field should contain result fragment, and set data source which contains null or string.Empty value for the field:

            RadFlowDocument document = new RadFlowDocument();
            RadFlowDocumentEditor editor = new RadFlowDocumentEditor(document);

            editor.InsertField("MERGEFIELD FirstName ", "«FirstName»");

            List<Person> source = new List<Person>()
            {
                new Person() { FirstName = string.Empty }
            };

            RadFlowDocument mergedDocument = document.MailMerge(source);
Expected: The result document is empty.
Actual: The result document contains "«FirstName»" string.

Available in LIB Version 2017.3.1120.

Currently, this property is exported only for Run and Paragraph elements.

The table height is currently not respected when applied to a table element through an attribute or through a CSS style. This setting is not respected in the flow document model, but we could import it and calculate the value to distribute it to the rows.

When importing paragraphs with negative text-indent from HTML, e.g. 
<p style="text-indent:-12px;">
test
</p>

they should be imported with HangingIndent + the same value with negative sign for LeftIndent, e.g. HandingIndent: 12 AND LeftIndent: -12.

Also, margin-left should be combined with the text-indent, e.g.
<p style="margin-left: 16px;text-indent: -16px;">
test
</p>
should be imported as HandingIndent: 16 AND LeftIndent: 0.