Add Borders property for a Run element and in CharacterProperties. The same is implemented for Paragraph, but in OOXML it could be applied over a Run element as well.
Import styling properties from HTML for elements without DocumentElementProperties. For example, for ImageInline: the image has width and height and currently they could not be applied through CSS styling as the styling mechanism works only for document elements with DocumentElementPropertiesBase (RadFlowDocument, Section, Table, Paragraph, etc.)
Introduce an option to implement custom field in RadFlowDocument model (one which is not supported by the document model). In the current implementation the abstract Field class has internal abstract method which is responsible for the GetFieldResult() method and this leads to an issue when a customer wants to implement a field which we currently do not support (CustomCodeField which returns null as a result fragment).
Implement import and export of bookmarks to HTML format.
The <font> tag has a 'size' attribute that can be set to a number from 1 to 17. This is currently not supported and is just ignored.
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.
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.
'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.
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.
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.
Implement API allowing to add watermarks without specifying its width and the height. The size could be automatically calculated using the text, its font size and font family.
CSS style property with a numeric value will not be imported from HTML when the unit type is not specified. Example: .td{padding-bottom: 200;} This is invalid according to the HTML spec (value is optional only after 0), though web browsers and MS Word open such HTML's correctly.
Importing a document containing a bookmark located in a structured document tag (sdt) will lead to ArgumentNullException.
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);
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.
When importing a simple table from HTML in Ms Word, it gets applied table cell spacing and margin. This makes it look more in the manner it does in a browser, i.e. the content of cells is vertically centered. Check for TableCell, TableRow, and Table.
Page breaks can be exported and subsequently imported using the "page-break-before: always; " property set of some elements.
Introduce support for break-[before/after] and page-break-[before/after].This can eventually be extended to support "page-break-before: avoid" to preserve the value of the Paragraph.KeepWithNextParagraph property.
Attached to this item is a sample project demonstrating how an HTML file is imported into a RadFlowDocument, the custom page break string are replaced with Break elements of type PageBreak and then the RadFlowDocument is exported to PDF and DOCX files.
Page breaks can be exported and subsequently imported using the "page-break-before: always; " property set of some elements.