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.
At the moment when a Floating Image is exported to HTML, it is exported as inline and its position is lost.
Implement import of bullets and numbering which use the old Word 6.0/Word 95 format from RTF. This includes, but is not limited to, the following RTF tags: \pnlvlN, \pnlvlblt, \pnlvlbody, \pnlvlcont. See RTF specification, "Word 6.0 and Word 95 RTF" heading for full description. WordPad and some legacy systems export lists with this formatting, so the construction is relatively widespread. According to the specification, if RTF reader doesn't support specific bullets/numbering tags, it can use the \pntext tag to read the bullets/numbering as plain text; but currently WordsProcessing always ignores the \pntext tag. Because of this, the bullets or numbers of lists in the old format are missing after import.
When paragraph contains only merge fields (and eventually whitespaces), and all of these fields are evaluated to empty string for particular data record, the paragraph could be removed from the merged document. Example: The document contains two paragraphs: <<FirstName>> <<LastName>> <<Address>> For particular data record, LastName and Address are empty, so the merged document for this data record will contain only one paragraph (the first one). This behavior is expected from customers, as it's implemented by MS Word.
Currently, this property is exported only for Run and Paragraph elements.
The table height is currently not respected when applied to a table element through an attribute or through a CSS style. This setting is not respected in the flow document model, but we could import it and calculate the value to distribute it to the rows.
Currently, this property is implemented only in DOCX and RTF exports.
The tag is currently not supported and skipped on import, leading to missing horizontal line in the document.
This setting should allow setting the content between the list level bullet and the paragraph text to some of the following options: "tab", "space", "nothing".
Form fields are the legacy way to insert an editable controls in a document (text boxes, checkboxes, dropdowns) by using the FORMTEXT, FORMCHECKBOX and FORMDROPDOWN fields. Do not confuse with content controls (structured document tags) (see https://feedback.telerik.com/Project/184/Feedback/Details/190057 ) and with ActiveX controls.
Add support for the All Caps and Small Caps properties of the runs. These properties are currently ommitted on import.
This property allows the user to set the transparency of the image watermark. In the XML, the property is written using the 'blacklevel' attribute of the image.
The API should allow the client to navigate to an empty block container and manipulate it. The block containers are Section, TableCell, Header, Footer, Comment. The API should also include manipulation methods for a table like: Add a row to a table. Add a cell to a row. Add a table to an empty cell. Add a paragraph to an empty cell. Add a run to an empty cell. add a text to an empty cell. Move to a next/previous cell. Move to a next/previous row. The API should use the currently applied editor formatting when creating the specified document elements.
Currently the PageOrientation property is used to determine the actual size of the paper to use on the printer and does not reflect document's visualization. In order to affect Section's appearance the user should change the PageSize and PageMargin properties. For convenience the Rotate method is introduced in order to update the properties simultaneously. However the usage of the Section.Rotate(PageOrientation) method is confusing since the properties are not updated when Section.PageOrientation is already set to the same value as the parameter. Also, Rotate method is useful only for rotating already created sections, and to create section with specified pages size and margins the user should set all Section's PageSize, PageMargin, PageOrientation properties anyway. More convenient API must be provided to create Section instances with correctly set properties for the desired page orientation.
This element specifies that the nearest ancestor structured document tag shall be of a document part type. <w:sdt> <w:sdtPr> … <w:docPartObj> … </w:docPartObj> </w:sdtPr> … </w:sdt> The docPartObj element in this structured document tag's properties specify that the type of structured document tag is a document part. The child elements must specify the gallery and category semantics for this part, if any. Currently, such elements are skipped on import.
The custom document properties enable the users to define their own properties to the document or use one of the predefined. In most of the cases, the document variables can be used instead. More information about them you can find at http://docs.telerik.com/devtools/document-processing/libraries/radwordsprocessing/concepts/fields/document-variables
Add support for the <w:sym /> element, e.g.: <w:r> <w:sym w:font="Wingdings" w:char="F0FC"/> </w:r> From the specification: "This element specifies the presence of a symbol character at the current location in the runs content. A symbol character is a special character within a runs content which does not use any of the run fonts specified in the rFonts element (126.96.36.199) (or by the style hierarchy). Instead, this character shall be determined by pulling the character with the hexadecimal value specified in the char attribute from the font specified in the font attribute." Currently such symbols are skipped during DOCX import. Possible workaround: These tags are inserted from MS Word when the Symbol dialog in used. If the document is created with MS Word, the user could insert the symbol using the keyboard, in this case the character is inserted as a normal run.
In OOXML, table row can define table properties named 'table level property exception' using 'tblPrEx' element. These properties shall be respected by the row instead of the table properties defined on table level. Add similar property in the TableRow model and respect it in the corresponding exports.