This is causing issues when exporting the document to PDF from WordsProcessing - the pdf library tries to create the font, but cannot find it due to a different casing. When importing HTML document, the font-family property is read with small letters. Later, when converting the string containing the value, it is changed to title case. 

This issue will be reproducible with each font containing a name with a letter with casing different than the one of the other letters (exc. first capital letter), for example: Microsoft JhengHei

In case table cell doesn't have directly applied background, it should inherit the background of its parent table.

Multiple CSS classes on an element are not correctly resolved when converted to inline styles.

Before:

.TelerikNormal {font-family: Calibri;font-size: 14.6666666666667px;margin-top: 0px;margin-bottom: 0px;line-height: 100%;color: #000000;}

.TelerikHeading3 {font-family: Calibri Light;font-size: 22.6666666666667px;}

<p class="TelerikNormal TelerikHeading3"><span>Test</span></p>

Due to order priority, the TelerikHeading3 values override the TelerikNormal values. The font-size becomes 22.6666666666667px.

Convert:

provider.ExportSettings.StylesExportMode = StylesExportMode.Inline;

<p style="font-family: Calibri;font-size: 14.6666666666667px;margin-top: 0px;margin-bottom: 0px;line-height: 100%;color: #000000;"><span>Test</span></p>

Provide a way to export filters.

byte[] data = File.ReadAllBytes("verdana.ttf");
FontFamily verdanaRegularFontFamily = new FontFamily("Verdana");
FontsRepository.RegisterFont(verdanaRegularFontFamily, FontStyles.Normal, FontWeights.Normal, data);
FontsRepository.TryCreateFont(verdanaRegularFontFamily, out FontBase verdanaRegularFont);

foreach (RadFixedPage page in mergedDocument.Pages)
{
	foreach (TextFragment textFragment in page.Content.Where(c => c is TextFragment).Cast<TextFragment>())
	{
		textFragment.Font = verdanaRegularFont;
	}
}

When imported in the WordsProcessing model, the current HTML doesn't respect the defined column width and all columns have identical width:

    <colgroup>
        <col span="1" style="width: 33.3302%;">
        <col span="1" style="width: 17.5658%;">
        <col span="1" style="width: 49.104%;">
    </colgroup>

Observed result:

Expected result:

Workaround: use the width property as follows:

    <colgroup>
        <col span="1" width="33.3302%">
        <col span="1" width="17.5658%">
        <col span="1" width="49.104%">
    </colgroup>

 An incorrect file is produced when merging a stream more than 40 times.

Workaround: A possible workaround could be to merge up to 40 times in one file, then continue merging in a new one, and finally merge the newly generated documents.

For example:
Renaming a sheet named "Sheet1" to "Sheet 1", should update formulas references to it to 'Sheet 1!' (notice single quotes), which it does not. The formula =SUM(Sheet1!A2:C2) changes to the invalid expression =SUM(Sheet 1!A2:C2). This breaks formulas referencing that sheet.

Workaround:
Iterate all cells with formulas in the workbook and add single quotes to the beginning and end of sheet name reference. The attached project changes the name of Sheet1 and then fixes all formula references to it by enclosing its name in single quotes.

This is the code for import/export which result is illustrated below:

            string inputFilePath = "test1.doc";
            Telerik.Windows.Documents.Flow.Model.RadFlowDocument document;
            Telerik.Windows.Documents.Flow.FormatProviders.Doc.DocFormatProvider doc_provider = new Telerik.Windows.Documents.Flow.FormatProviders.Doc.DocFormatProvider();
            using (Stream input = File.OpenRead(inputFilePath))
            {
                document = doc_provider.Import(input, TimeSpan.FromSeconds(10));
            }

            Telerik.Windows.Documents.Flow.FormatProviders.Docx.DocxFormatProvider docx_provider = new Telerik.Windows.Documents.Flow.FormatProviders.Docx.DocxFormatProvider();
            string outputFilePath = "Exported.docx";
            using (Stream output = File.OpenWrite(outputFilePath))
            { 
                docx_provider.Export(document, output, TimeSpan.FromSeconds(10));
            }

            Process.Start(new ProcessStartInfo() { FileName = outputFilePath, UseShellExecute = true });

When a chart is created with RadSpreadProcessing, by default it is exported with legend showing category list. If an xlsx file with a chart with legend showing only series is imported and exported, it will be changed to category list as well. API to switch between the two should be added.

Legend showing category list:

Legend showing series: