Generate a document with the following approach: https://docs.telerik.com/devtools/document-processing/knowledge-base/populate-table-data-mail-merge
Before calling MailMerge, add two document variables with the editor: https://docs.telerik.com/devtools/document-processing/libraries/radwordsprocessing/concepts/fields/document-variables
When the document is encoded in two-byte encoding using Little-Endian, the CsQuery HTML parser provides the entire document as FirstChild of the <body> tag, which leads to incorrect import. This seems to be occurring with MS Outlook messages saved as HTML. Workaround: convert the file to Big-Endian encoding before importing.
The item is closed as duplicate. Please, submit your votes and subscribe for notifications to the item at https://feedback.telerik.com/Project/184/Feedback/Details/190053-wordsprocessing-support-for-importing-dotm-dotx-and-docm-files.
Hyperlinks should support this property in order to describe where they should be opened (in the same frame/tab or in a new one). It is described in the OOXML specification as tgtFrame (Hyperlink Target Frame). It will be useful for setting the target as _blank.
When importing from HTML, all successive spaces in a spans are trimmed. Instead, in some cases one space should be left, e.g. between words. For example, the importing the following HTML should leave one space after the hyperlink: <p><a href="www.telerik.com" target="_blank"><span>test</span></a> and more.</p> Workaround: After importing, check if the runs after the hyperlinks start with space: foreach (var hyperlinkEnd in this.document.EnumerateChildrenOfType<FieldCharacter>().Where(f => f.FieldCharacterType == FieldCharacterType.End)) { Paragraph currentParagraph = hyperlinkEnd.Paragraph; int indexOfNextRun = currentParagraph.Inlines.IndexOf(hyperlinkEnd) + 1; if (currentParagraph.Inlines.Count > indexOfNextRun) { Run run = currentParagraph.Inlines[indexOfNextRun] as Run; if (run != null && run.Text[0] != ' ') { run.Text = " " + run.Text; } } }
When paragraphs in list and with hanging indent set are imported from RTF, unexpected values for hanging indent and left indent are imported. The problem is most visible when the document is exported to HTML and visualized in browser, as bullets of the list appear over the content.
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.
This is done due to wrong column widths weights calculations.
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.
According to the OOXML specification the shading color can be defined only in RRGGBB hex color, but MS Word also supports colors defined with their names - e.g. "Red".
The font size in the table does not respect the CSS for the corresponding class. There is similar issue with <li /> element.
'thead' HTML element represents table row that should be repeated at the top of each page. MS Word maps this to TableRow with RepeatOnEveryPage set to true. This works for both export and import.
Paragraph with a negative left indent and positioned in the header or footer gets clipped when exported to PDF. The same behavior is also observed for paragraphs in tables. Instead, the paragraph should be rendered without clipping.
ParagraphMarkerProperties of a Paragraph element are not cloned and this leads to incorrect list numbering (bullets) rendering after export since the numbering styles (bullets, numbers and etc.) copy the style properties from there. This affects Clone() method of the Paragraph and ergo RadFlowDocumentEditor.InsertDocument() method and DocumentElementImporter.Import() methods since they're using Clone() method internally.
The document default style properties are not cloned on document.Clone(). There is a workaround by using the following code: var cloning = this.document.Clone(); ClearPropertiesWithoutValueAndSetLocalValues(this.document.DefaultStyle.CharacterProperties, cloning.DefaultStyle.CharacterProperties); ClearPropertiesWithoutValueAndSetLocalValues(this.document.DefaultStyle.ParagraphProperties, cloning.DefaultStyle.ParagraphProperties); private void ClearPropertiesWithoutValueAndSetLocalValues(DocumentElementPropertiesBase propertiesFrom, DocumentElementPropertiesBase propertiesTo) { foreach (var stylePropertyFrom in propertiesFrom.StyleProperties) { var stylePropertyTo = propertiesTo.GetStyleProperty(stylePropertyFrom.PropertyDefinition); stylePropertyTo.ClearValue(); if (stylePropertyFrom.HasLocalValue) { object value = stylePropertyTo.GetLocalValueAsObject(); stylePropertyTo.SetValueAsObject(value); } } }
When document model contains styles with names containing characters which usage is not valid in CSS (e.g. '['), those characters must be escaped. Currently HTML documents containing invalid CSS are produced.
Currently tabs are always exported to HTML using two -s. But tabs could have different length depending on Paragraph's tab stops and document's default tab stop width.