The tblGrid property should be exported in order to visualize properly the documents in some viewers. For example, LibreOffice doesn't visualize properly tables without specified width.
Take into account the table row's CanSplit property when exporting to PDF from RadFlowDocument model. Is set to false, the table row should not be split between two pages, if possible. This property could be set to false, for example, when importing MS Word documents with "Allow row to break across pages" unchecked for some table rows.
Implement repeating header row for tables when exporting with PdfFormatProvider. A similar functionality can be achieved using the editing API of RadPdfProcessing. There is attached a project showing a sample implementation. More details are available in the forum post at http://www.telerik.com/forums/repeat-table-heading-after-page-break#kH616fyAKUiDl6WAknUILg
Add support for INCLUDEPICTURE fields. Such fields should work with nested MERGEFIELD, as this is common scenario. Workaround: Manually insert images over specific placeholderRadFlowDocument document =
new
RadFlowDocument();
RadFlowDocumentEditor editor =
new
RadFlowDocumentEditor(document);
editor.InsertText(
"1"
);
editor.InsertText(
"EXAMPLE_IMAGE"
);
editor.InsertText(
"2"
);
foreach
(var run
in
editor.Document.EnumerateChildrenOfType<Run>().ToArray())
{
if
(run.Text ==
"EXAMPLE_IMAGE"
)
{
Paragraph paragraph = run.Paragraph;
int
indexOfCurrentRun = paragraph.Inlines.IndexOf(run);
paragraph.Inlines.RemoveAt(indexOfCurrentRun);
ImageInline imageInline =
new
ImageInline(document);
imageInline.Image.ImageSource = newTelerik.Windows.Documents.Media.ImageSource(imageData,
"png"
);
paragraph.Inlines.Insert(indexOfCurrentRun, imageInline);
}
}
The vertical alignment of the table cells is not exported to PDF. The values are always exported with top alignment.
When table cell preferred width is smaller than the first word in the cell the actual exported width should fit the word width when exporting to PDF. Currently in such case the word is split into two lines. The width has to be equal to the word width so the word stays on a single row.
The property controls whether a paragraph should be rendered at least partially on the same page with the following paragraph when the document is shown in page view mode.
Add support for import and export of floating tables.
In case table cell doesn't have directly applied background, it should inherit the background of its parent table.
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.
At this point only styling through CSS is supported. The below code does not align the paragraph to the center string import = "<html><body><p align=\"center\">centered??</p></body></html>"; RadFlowDocument document = provider.Import(import);
This is only reproducible when the Run contains an empty string. If the paragraph is empty or the Run contains a space, everything is working correctly. Workaround: Remove all empty runs from the document.
This is done due to wrong column widths weights calculations.
Implement support for content controls (a.k.a. Structured document tags), which will allow inserting editing controls in the document: - Rich Text - Plain Text - Check Box - Combo Box - Drop-down list - Date picker Do not confuse this feature with form fields support (see https://feedback.telerik.com/Project/184/Feedback/Details/219850 ).
At this point the PdfFormatProvider does not support floating images and these elements are skipped when exporting to PDF. The feature is trivial for floating images with "Behind Text"/"In Front of Text" settings, but otherwise floating images are affecting the text layout in complex ways.
These file formats are very similar to DOCX, and can be easily imported with loss of some information (e.g. macros).
ArgumentException with 'Invalid value' message is thrown when importing invalid font sizes from docx, e.g. <w:sz></w:sz> (the 'val' attribute should be specified according to the OOXML specification). Instead, such documents could be imported as the w:sz is not specified, similar to the behavior of MS Word.
Add support for smart tags (described in the OOXML using the smartTag element). As currently smart tags are not supported, the content inside them is not imported from docx.
Now headings are imported with default heading styles. Introduce an option for Heading styles to be exported as <h1> - <h6> tags. Consider whether this should be the default behavior, because MS Word exports Headings with H tag and additionally adds styling so the resulting HTML will visually look the way it does in MS Word.