Hyperlinks created via HtmlFormatProvider are not properly exported to PDF and cannot be clicked.

According to the HMTL specification, the width and height attributes of an img tag has unsigned long values. When a width or height values with a unit suffix is imported, e.g.: 50%, FormatException: 'Input string was not in a correct format.' is thrown.

When an image is placed in a table row and the document is exported to PDF the image top edge is placed at the center of the table border because the border thickness is not respected.

Such tags are not supported in RtfFormatProvider and while skipping them, there might be fields that are not properly imported. This can lead to issues while exporting the document. If the document is re-saved using MS Word, the HTML-related tags are removed and the content can be properly imported with WordsProcessing.

The HtmlFormatProvider currently doesn't support borders for p elements.
There is a ParagraphBorders property in the model Paragraph class, but it isn't implemented in the HTML import. Also, ensure that the borders applied on div elements are preserved.

An index lists the terms and topics that are discussed in a document, along with the pages that they appear on. 

In WordsProcessing on import only the lower case CSS attributes are correctly imported. Upper case and mixed case are ignored and the default values are used.

When merging two documents each of which has header/footer with InsertDocument, the headers/footers are misplaced in the result document.

Empty lists with auto-close tags (i.e. <ol />) break the numbering of the lists declared after them.

When a PAGE field containing a \* MERGEFORMAT switch it is suspended of getting the real number of a page.

 When exporting to HTML file, the table width is wrongly evaluated when the table width (in the original document) is set to fixed width.

Workaround: 
IEnumerable<Table> tables = this.document.EnumerateChildrenOfType<Table>();
foreach (Table table in tables)
{
table.PreferredWidth = new TableWidthUnit(TableWidthUnitType.Auto);
}

IEnumerable<Paragraph> paragraphs = this.document.EnumerateChildrenOfType<Paragraph>();
foreach (Paragraph paragraph in paragraphs)
{
paragraph.Spacing.SpacingAfter = 0;
}

When different borders are set to the table cells and the table itself, they are overlapping using relatively complex logic.

I have created a very simple template (see attached file), import it, add my contents and later try to do a MailMerge.
However, the call to this function fails with the following exception:
System.ArgumentException
  HResult=0x80070057
  Message=The document element is already associated with a parent.
Parametername: item
  Source=Telerik.Windows.Documents.Flow
  StackTrace:
   at Telerik.Windows.Documents.Flow.Model.Collections.DocumentElementCollection`2.VerifyDocumentElementOnInsert(T item) in c:\DeveloperTooling_Agent13\_work\91\s\Documents\Flow\Flow\Model\Collections\DocumentElementCollection.cs:line 69
   at Telerik.Windows.Documents.Core.Data.DocumentElementCollectionBase`2.InsertRange(Int32 index, IEnumerable`1 items) in c:\DeveloperTooling_Agent13\_work\91\s\Documents\Core\Core\Core\Data\DocumentElementCollectionBase.cs:line 129
   at Telerik.Windows.Documents.Flow.Model.InlineRangeEditor.InsertInlinesInRange(InlineBase start, IEnumerable`1 inlines) in c:\DeveloperTooling_Agent13\_work\91\s\Documents\Flow\Flow\Model\InlineRangeEditor.cs:line 132
   at Telerik.Windows.Documents.Flow.Model.Fields.FieldInfo.UpdateFieldCore(FieldUpdateContext context) in c:\DeveloperTooling_Agent13\_work\91\s\Documents\Flow\Flow\Model\Fields\FieldInfo.cs:line 236
   at Telerik.Windows.Documents.Flow.Model.Fields.FieldInfo.UpdateFieldInternal(FieldUpdateContext context) in c:\DeveloperTooling_Agent13\_work\91\s\Documents\Flow\Flow\Model\Fields\FieldInfo.cs:line 186
   at Telerik.Windows.Documents.Flow.Model.MailMergeProcessor.ExecuteMailMerge(RadFlowDocument document, Object record) in c:\DeveloperTooling_Agent13\_work\91\s\Documents\Flow\Flow\Model\MailMergeProcessor.cs:line 57
   at Telerik.Windows.Documents.Flow.Model.MailMergeProcessor.Execute(RadFlowDocument document, IEnumerable collection) in c:\DeveloperTooling_Agent13\_work\91\s\Documents\Flow\Flow\Model\MailMergeProcessor.cs:line 25
   at Telerik.Windows.Documents.Flow.Model.RadFlowDocument.MailMerge(IEnumerable collection) in c:\DeveloperTooling_Agent13\_work\91\s\Documents\Flow\Flow\Model\RadFlowDocument.cs:line 337
   at JOIM.TextExport.DocumentGenerator.Export(String outputPath) in P:\Tolaris\JOIM.Common\JOIM.TextExport\DocumentGenerator.cs:line 581

using Telerik.Windows.Documents.Flow.FormatProviders.Docx;
using Telerik.Windows.Documents.Flow.Model;
using Telerik.Windows.Documents.Spreadsheet.Model;

...

using (StreamfileStream = File.Open(templatePath, FileMode.Open, FileAccess.Read, FileShare.ReadWrite))
{
    var provider = newDocxFormatProvider(); 
    _document = provider.Import(fileStream);
}

...

_document = Document.MailMerge(new [] { MergeFieldData });

Currently, the Line breaks <br> are not exported to plain text format.

Workaround:

The AlternateContent element is used to store content which is not defined by the specification.

Currently, this could be achieved by exporting the document to PDF and then by using RadPdfViewer's WPF control ThumbnailFactory class. Sample code may be seen at this forum post: http://www.telerik.com/forums/pdf-thumbnail-returns-transparent-images#jO33X-E8Cki_qLh_KsToWg

Wrong exported paragraph indentation when hanging indent set and the paragraph is in list

Currently, the unsupported Structured document tags (SDTs) in the document are skipped on import.

The image size of EMF/WMF images is wrongly exported when exporting to PDF.