LineInfo objects are not cleared when there are tables in the document being exported to PDF which leads to OutOfMemoryException.

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 table with table border without color set is created (the color is null), and the document is exported to PDF, ArgumentNullException is thrown. 

Workaround: Explicitly set a color where the color is null.
private void PdfExport()
{
	var tables = this.document.EnumerateChildrenOfType<Table>();

	foreach (var table in tables)
	{
		TableBorders coloredClone = this.CopyTableBorders_SetColorWhenOmitted(table);
		table.Borders = coloredClone;
		
		using (Stream output = new FileStream(fileName, FileMode.OpenOrCreate))
		{
			provider.Export(this.document, output);
		}
	}
}

private TableBorders CopyTableBorders_SetColorWhenOmitted(Table table)
{
	var leftBorder = new Border(table.Borders.Left.Thickness,
				  table.Borders.Left.Style,
				  table.Borders.Left.Color ?? new ThemableColor(Colors.Transparent),
				  table.Borders.Left.Shadow,
				  table.Borders.Left.Frame,
				  table.Borders.Left.Spacing);

	var rightBorder = new Border(table.Borders.Right.Thickness,
				  table.Borders.Right.Style,
				  table.Borders.Right.Color ?? new ThemableColor(Colors.Transparent),
				  table.Borders.Right.Shadow,
				  table.Borders.Right.Frame,
				  table.Borders.Right.Spacing);

	var bottomBorder = new Border(table.Borders.Bottom.Thickness,
				table.Borders.Bottom.Style,
				table.Borders.Bottom.Color ?? new ThemableColor(Colors.Transparent),
				table.Borders.Bottom.Shadow,
				table.Borders.Bottom.Frame,
				table.Borders.Bottom.Spacing);

	var topBorder = new Border(table.Borders.Top.Thickness,
				table.Borders.Top.Style,
				table.Borders.Top.Color ?? new ThemableColor(Colors.Transparent),
				table.Borders.Top.Shadow,
				table.Borders.Top.Frame,
				table.Borders.Top.Spacing);

	var insideHorizontalBorder = new Border(table.Borders.InsideHorizontal.Thickness,
			 table.Borders.InsideHorizontal.Style,
			 table.Borders.InsideHorizontal.Color ?? new ThemableColor(Colors.Transparent),
			 table.Borders.InsideHorizontal.Shadow,
			 table.Borders.InsideHorizontal.Frame,
			 table.Borders.InsideHorizontal.Spacing);

	var insideVerticalBorder = new Border(table.Borders.InsideVertical.Thickness,
			table.Borders.InsideVertical.Style,
			table.Borders.InsideVertical.Color ?? new ThemableColor(Colors.Transparent),
			table.Borders.InsideVertical.Shadow,
			table.Borders.InsideVertical.Frame,
			table.Borders.InsideVertical.Spacing);

	var tableBorders = new TableBorders(leftBorder, topBorder, rightBorder, bottomBorder, insideHorizontalBorder, insideVerticalBorder);

	return tableBorders;
}

It would be nice to have the ability to search text in documents.

Use case:
I needed to replace some keywords with images. I can insert image at the current position, but there is no way to insert it after some text.

StackOverflowException is thrown during PDF export of a document with a Header/Footer containing a page break.

Workaround: Remove page break from all header/footer paragraphs, or from a specific paragraph.

Header defaultHeader = section.Headers.Default;

if (defaultHeader != null)
{
    foreach (var item in defaultHeader.Blocks)
    {
        if (item is Paragraph paragraph)
        {
            paragraph.PageBreakBefore = false;
        }
    }
}

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>

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>

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

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 });

 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.