When header/footer (HeaderFooterPresenterBase) is rendered, the model which corresponds to it (HeaderFooterBase's Body property) is not updated. The result is updated only in the presenter. Thus, when exporting the document or when checking the elements in the model, the value of the inline (span's text) is not updated. Workaround: Update the fields in the headers/footers. RadDocumentEditor.UpdateAllFields() method can be used. Note that it works only for the main document and not its child documents, so different RadDocumentEditors should be created for each header/footer document.
For example for Input Method Editors like Marathi Indic Input, part of MS Indic Language input tool, downloadable from here: http://www.bhashaindia.com/ilit/Marathi.aspx. Workaround: RadRichTextBox currently exposes customization point for implementing custom IMEs, see Custom IME Support: http://docs.telerik.com/devtools/wpf/controls/radrichtextbox/ime-support#custom-ime-support
Add support for All Capitals (All caps) and Small Capitals (Small caps) run property. MS Word has such option in Home -> Font -> Dialog Launcher -> Font -> All Caps/Small Caps. All letters of such runs are visualized as capital letters. The corresponding elements in OOXML are <w:caps /> and <w:smallcaps />.
After resizing the window, the text stays at the same location instead of moving to the next line. The result is overlapping text.
When a span or text is placed in <a> tag, but 'href' and 'name' attributes are missing, then the span/text is not imported from the HTML document. Workaround: preprocess the HTML and add the 'href' attribute to all <a> elements. Steps to reproduce: 1. Import the following HTML: <html> <body> <a target="_blank">Some text</a> </body> </html> Expected: The hyperlink "Some text" is imported in the document. Actual: The span "Some text" is not imported.
Currently, colors with alpha channel defined with 'rgba' function are not supported, for example the following: <span style="background-color: rgba(0, 0, 0, 0.5);">Some text</span> is imported as black color; semi-transparent colors are exported without the alpha channel.
HtmlFormatProvider cannot import a document that contains an image with invalid URI format. An UriFormatException is thrown and the whole import fails. Similar errors should be handled and the document should be imported.
More information: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/tt . Note: this element is obsolete, and has the same meaning as <code>.
If span formatting command (bold, italic, strikethrough) is applied to selection over multiple paragraphs, and tracked with tracked changes; and later this tracked change is rejected, NullReferenceException is thrown. The exception is handled so the visible result for the end user is that the UI stops updating and any subsequent changes are not visible.
All Microsoft Office applications (Outlook, Exchange, Word, Excel) that can produce HTML are creating them with all of the CSS stylings commented with HTML comment, as follows: <style><!-- CSS --></style> This is a problem as RadRichTextBox's HTML parser does not import the CSS when it is commented like that. Workaround: Remove the HTML comment from the CSS style tag.
Currently <big> and <small> tags are not supported and the text inside is not imported.
Currently HtmlFormatProvider does not export/import tables with alignment (left, center, right).
It seems that the characters of Arabic words are reversed on export. Moreover, Arabic letters has different letter forms according to their position in the word (contextual letter forms) - beginning, end, middle, isolated. It seems that same character should be exported to PDF with different charcode depending on the character positioning.
The invalid values should be skipped and the document should be successfully imported.
Check all possible shorthand properties, e.g. border-[left/top/right/bottom]. Also check CSS properties like border-[left/top/right/bottom]-[color/style/width].
Add support for inset borders for tables and table cells (Inset Line Border in OOXML).
Nested tables inherit alignment from its parent table or table cell when importing a document from HTML, but they shouldn't. The paragraphs are also aligned incorrectly when their parent table has its align attribute set.
Currently ignored words are marked only in-memory using internal properties of the document model. Make them persist, similar to what MS Word do. Note: In the DOCX format, the document is marked as "clear" (doesn't contain spell check errors) and all misspelled words are enclosed with an errProof annotation.
The word is temporary marked as correct and when another word is added to the dictionary, the ignored one is highlighted again. As a workaround could be used the Ignore All option.