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.
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.
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.
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
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.
When a preceding paragraph's size is increased, for example - font size is changed, or paragraph is split to two, then the selection of the consequent paragraphs is wrong. When the cursor is on the second line and attempt to select some part of it with the mouse is made, the first or the third line is selected. Steps to reproduce: 1. Create two paragraphs with multiple lines 2. Insert new paragraph after the first paragraph 3. Try to select second line of the third paragraph with the mouse Observed result: First line is selected instead of second line being selected
Characters like 🙋🏻 are not imported correctly and instead result in a series of question marks. Fix available in LIB Version 2018.2.716.
Copy/Paste Adobe Reader snapshots are displayed as blank images.
RadDocument instance leaks through StylesGallery when RadDocument is set multiple times in a sequence to RadRichTextBox - for example by setting RadRichTextBox.Document property multiple times. Steps to reproduce: - Start application containing RadRichTextBox with StylesGallery - Execute this code on a button click: this.radRichTextBox.Document = new RadDocument(); this.radRichTextBox.Document = new RadDocument(); Observed: RadDocument leaks through the styles gallery. Available in LIB version: 2017.1.227
The tab stop defining respective page number alignment correlates to the cell's width where the table of contents entry is positioned.
The pgMar element might be present but the margin information might be missing as shown below: <w:pgMar w:header="720" w:footer="720" /> At the moment this overwrites the section margin information with 0. Instead the margins should remain as is. Fix available in LIB Version 2018.2.820.
RadDocument.StreamFromUriResolving is not raised for the main document when InsertPictureField is included in header or footer.