Currently Run.Shading is not exported to PDF. Note: This scenario is common when converting HTML to PDF, as Run.Shading is set when construct like <span style="background-color:#ffcc00;"> is used. Workaround: Iterate all the Runs in the already imported HTML document and set their HighlightColor to Shading.BackgroundColor.LocalValue. Check this code snippet:
foreach (Run run in document.EnumerateChildrenOfType<Run>())
{
if (!run.Properties.HighlightColor.HasLocalValue)
{
run.HighlightColor = run.Shading.BackgroundColor.LocalValue;
}
}
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.
Enable the customers to work with .dot files.
This field allows performing a mail merge operations with labels representing different source items on the same page.
This property will control whether a table row may start on one page and end on the next page. Declined: Duplicate with https://feedback.telerik.com/Project/184/Feedback/Details/190081-wordsprocessing-respect-tablerow-cansplit-property-when-exporting-to-pdf.
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 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.
This element specifies the settings for the document grid, which enables precise layout of full-width East Asian language characters within a document by specifying the desired number of characters per line and lines per page for all East Asian text content in this section.
If Latin text is interspersed on this line, then it is placed across the number of grid units needed to fit the
content, but all other grid positions are unaffected.
The mail merge should support conditional fields. Here is an example:
{ IF [Condition] [Display Result 1] [Display Result 2] }
List indent is not correct when exported to PDF. All indents start from the same position.
Exception when there are merge fields in the header/footer and one performs mail merge:
Unable to cast object of type 'Telerik.Windows.Documents.Flow.Model.Header' to type 'Telerik.Windows.Documents.Flow.Model.BlockBase
Make it possible to link files (read: excel table) into word documents, so the editing experience in e.g. word allows to navigate to the linked file. Ms Word and OOXML allow insertion of files in a docx document. This results in OLEOobject referring to the embedded file.