At this point, only background-color is supported. Add support for bgcolor attribute as well. It could be used with the following tags: body, marquee, table, tBody, td, tFoot, th, tHead, tr.
There are 27 types of border styles in the Open XML specification and they are implemented in RadFlowDocument. Part of the borders are already supported (eg. None, Single, Dotted) when exporting to HTML, all others are treated as None and stripped.
The HTML format doesn't support all types of border styles OOXML format supports.
Such objects are defined as oleObject elements in the XML:
<w:object w:dxaOrig="3795" w:dyaOrig="3555">
<v:shape id="_x0000_i1026" type="#_x0000_t75" style="width:32.85pt;height:30.55pt" o:ole="" fillcolor="window">
<v:imagedata r:id="rId9" o:title=""/>
</v:shape>
<o:OLEObject Type="Embed" ProgID="PBrush" ShapeID="_x0000_i1026" DrawAspect="Content" ObjectID="_1647182330" r:id="rId10"/>
</w:object>
Currently, they are skipped on import.
Wrongly imported/exported table cells from nested tables (see the picture below).
The exception is thrown because the AltChunk element is added for import, but we currently do not have implementation for importing of AltChunk elements: https://feedback.telerik.com/Project/184/Feedback/Details/190095-wordsprocessing-add-support-for-altchunk-element
There is a discrepancy between RadWordsProcessing and MS Word:
row.Height = new TableRowHeight(HeightType.Exact, image.Image.Height);
editor.InsertField("PAGE", "1")
foreach (ImageInline image in document.EnumerateChildrenOfType<ImageInline>().ToList())
{
UriImageSource uriImageSource = (UriImageSource)image.Image.ImageSource;
if (uriImageSource != null && !IsValid(uriImageSource.Uri.OriginalString))
{
image.Paragraph.Inlines.Remove(image);
}
}
private static bool IsValid(string uri)
{
try
{
Path.GetExtension(uri);
}
catch (ArgumentException)
{
return false;
}
return true;
}
Importing shape with missing id attribute leads to NullReferenceException. <v:shape type="#_x0000_t202" filled="false" stroked="false">
Table and table cell borders are not evaluated according to inheritance and conflict resolution rules. A conflict will occur when different borders from the table and table cell are overlapping. The GetActualValue method of the TableBorders and TableCellBorders could potentially return an incorrect value in some of the following scenarios: Scenario 1: A table has cell spacing set to 0. Meaning that the table and table cell borders will overlap. The table borders have defined all of its borders with border style "Single". The table cell borders have all of its borders defined with border style "None". Expected result: the resulting borders should have the border style set to "None" for the location where the table and the cell borders are overlapping. Scenario 2: A table has explicitly defined that its right border is with border style "None". The table has a table style applied with defined border style of type "Single" for all table borders. Expected result: All of the table borders except the right border should have border style of "Single". The problem is mostly visible when exporting to PDF and RTF format.