It should be possible to have several columns in a section of the document. These columns should also be persisted on export/import.
RadRichTextBox doesn't support most used Chinese IMEs - QQ Pinyin and Sogou Pinyin.
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.
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.
When the caret is positioned in the beginning of a paragraph and a table is inserted, an additional paragraph before the table should not be added. This also includes the case with a blank document. Special case: When there is a table in the document, inserting another just after it should be disabled.
This field retrieves a character through a code value specified in the field-argument. Such documents are common and are created when symbols (e.g. with font Windings through Insert -> Symbol dialog) are inserted in RTF documents in MS Word. This functionality is also used when content containing <sym> element is copied from DOCX and pasted in RadRichTextBox - as the content is converted to RTF containing SYMBOL field during the operation. Workarounds: - Implement such field with the API, see the documentation article (http://docs.telerik.com/devtools/wpf/controls/radrichtextbox/features/fields-and-document-variables/custom-fields ) and the SDK example (https://github.com/telerik/xaml-sdk/tree/master/RichTextBox/CustomField/ ). Note that MS Word doesn't show field menus for these fields in RTF documents. - If RTF format is used and you have control over document creation, save the documents initially as docx, and then save them to RTF. This way the symbols will be encoded without the SYMBOL field construct, and are successfully imported in RadRichTextBox. Available in R3 2018 Official Release.
Currently, when a page break is added to the document, the paragraph is not split in two. It will be better to split the paragraph and add one additional paragraph in order to achieve a more consistent look of the document when applying a style, adding one of the paragraphs to a list or having different first line/hanging indentation of the paragraphs.
Currently, ParagraphDefaultSpacingAfter and ParagraphDefaultSpacingBefore are not applied to paragraphs in tables. This should be changed for consistency with the rest of the document.
When a color property has default (auto) value, do not export a tag which points to omitted defintion in the color table. For example, if a span has transparent highlight (the default one), do not export the \highlight tag since this might lead to some incorrect rendering of the document from other readers - WordPad for example.
Japanese users use distributed text alignment, which justifies all lines including the last one.
When paragraph is in list, the user can choose "Set Numbering Value" which will change the appropriate level Starting Index and will create a new list (or continue the previous one).
Add support for lower-alpha and upper-alpha.
Currently, there is an SDK example (https://github.com/telerik/xaml-sdk/tree/master/RichTextBox/WindowsMetafileFormatImageDecoder) showing how to implement a custom decoder that can import WMF and EMF images. We could integrate this decoder in the source code and enable the users to import their documents that contain such type of images out-of-the-box. Available in R1 2017 Official Release Version.
The InsertTable command should copy the current style to all paragraphs in the new table.
There is no translation in the different languages. Available in LIB Version 2017.2.828.