Implement support for content controls (a.k.a. Structured document tags), which will allow inserting editing controls in the document: - Rich Text - Plain Text - Check Box - Combo Box - Drop-down list - Date picker Do not confuse this feature with form fields support (see http://feedback.telerik.com/Project/143/Feedback/Details/146869 ).
Add support for shapes, and especially for shapes with textual content. In OOXML, shapes are represented by the wps:wsp element, and shapes with textual content by <wps:txbx>, <w:txbxContent>. Such shape can be added to a Word document using the Insert -> Text -> Text Box -> Draw Text Box, or through a shape's context menu -> Add Text. Note: Do not confuse with Text/Rich Text content controls (https://feedback.telerik.com/Project/143/Feedback/Details/113730 ).
It should be possible to have several columns in a section of the document. These columns should also be persisted on export/import.
In MS Word there is a combo box for display mode of the track changes under Review tab. There is a No Markup option which hides the revisions and shows how the document will look in his final variant. Similar to accepting all revisions.
- There should be a formatting symbol for the character - Pressing Ctrl+Shift+Space should insert the character (standard MS Word shortcut) - Import from docx should be implemented - The symbol should be treated as a separator between words when spell-checking
RadRichTextBox doesn't support most used Chinese IMEs - QQ Pinyin and Sogou Pinyin.
Currently, caret continues to blink even when typing or navigation is in progress (e.g. arrow key is pressed and held), which is inconvenient for the end users. Instead, the caret should stop blinking during these operations, similarly to industry standard apps like MS Word and OpenOffice.
Splitting table cells is currently not supported and it would be a nice addition to the functionality related to tables. Menu item should be added to the default table context menu.
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. This includes the legacy Frames (described in OOXML with 'framePr' element). Do not confuse with content controls (structured document tags) (see http://feedback.telerik.com/Project/143/Feedback/Details/113730 ) and with ActiveX controls.
Add support for nested track changes revisions. Currently, when a user tries to delete text added by another user, RadRichTextBox simply removes it and does not mark it as a change.
Add a way to convert between RadRichTextBox's RadDocument and RadWordsProcessing's RadFlowDocument. This will enable integration scenarios between the two products, including using RadWordsProcessing's format providers for import and export.
Add a way to restrict page breaks in paragraphs or page breaks between paragraphs. In MS Word, these options are named "Keep lines together", "Keep with next" and "Page break before".
Support for file formats other than .TDF is required, so that a broader range of dictionaries can be used. Consider adding support for OpenOffice dictionaries.
Add ability to select last paragraph symbol in Section and TableCell. Currently there is no document position after the last paragraph symbol in a document/section/table cell. This means it cannot be part of a DocumentSelection.
When the focus gets in RadRichTextBox, AutomationProperties.Name is not pronounced by screen readers (for example by Windows Narrator). Workaround: the automation name could be set to the caret as demonstrated in the attached project.
Page field in header (or footer) of document created with mail merge is always evaluated to 1, instead of the number of the current page. Possible workaround (attached): - Do mail merges one by one - Set header/footers anew to contain PAGE fields in each document - Set FirstPageNumber = 1 to each first section in each document - Merge with RadDocumentMerger
Create different options for pasting(keep formatting, merge formatting, use destination styles). At this point, the document default styles are not copied in the document fragment, thus their loss is observed. When DocumentInheritsDefaultStyleSettings is true and the font settings are like set to different font size/font family, copied text is pasted to MS Word with Verdana font, size 12. Loss of formatting is also observed when copying from RadRichTextBox and pasting in MS Word - the default styles differ.