The image in the header is not exported to pdf.

Workaround: Use version R1 2022 where this is working.

Currently some properties are supported only in their shorthand forms, and others - only in their longhand forms:
- 'background' shorthand is not supported.
- 'margin' shorthand is not supported.
- 'padding' shorthand is not supported.
- 'border' shorthand is supported, but 'border-bottom-color', 'border-bottom-style', 'border-bottom-width', 'border-left-color', 'border-left-style', 'border-left-width', 'border-right-color', 'border-right-style', 'border-right-width', 'border-style', 'border-top-color', 'border-top-style', 'border-top-width', 'border-width' are not supported.
IMPORTANT: This feature is available in .NET Core, .NET 6 and above.

When table row is empty, it's exported to PDF with incorrect height - depending on the type of height set with 0 or with the height of an empty paragraph.

TableRow which has defined an only val attribute of the trHeight is imported as a row with auto height. By the specification, this is right, but MS Word takes the val value as row height. Also MS Word exports "At Least" row height with only 'val' set.

Workaround: Iterate through the table rows and set them HeightType to Exact or AtLeast:

foreach (var row in this.document.EnumerateChildrenOfType<TableRow>())
{
    row.Height = new TableRowHeight(HeightType.AtLeast, row.Height.Value);
}

First Footer of a section overrides the First Footer of another section after the merge. After merging 'Parent' document (with a different First Footer which is empty) with 'Child' document (with explicitly set First Footer), the First Footer of 'Child' overrides the First Footer of 'Parent' after PDF export.

Workaround 1: Disable 'Child' document's 'HasDifferentFirstPageHeaderFooter' and clear its First Footer's value:

Telerik.Windows.Documents.Flow.Model.Section section = child.Sections.First();
section.HasDifferentFirstPageHeaderFooter = false;
section.Footers.First.Blocks.Clear();

parent.Sections.First().Footers.Add(HeaderFooterType.First);

Line spacing is not preserved when exporting RTF to HTML and the lines are exported with the default line spacing.

Similar to https://feedback.telerik.com/reporting/1356710-rendering-to-xlsx-should-not-add-bom-to-xml-files :

DOCX files exported with DocxFormatProvider contain a BOM in every exported XML file. Some programs fail to load those DOCX files.

Please remove the BOM, or add a toggle in DocxExportSettings.