The fix will be available in our official release Q1 2015.
The fix will be available in our official release Q1 2015.
Add support for the following RTF tags (crop from top, bottom, left, right): \picropt, \piccropb, \piccropl, \piccropr
Consider raising an event when the images are finished loading, or an option for loading the images synchronously.
Exporting document containing Hebrew text to PDF results in correct text (letter-by-letter), but with wrong text flow: letters in the words are inverted and flow left-to-right instead of right-to-left.
Implement Mirror margins similar to the option in MS Word. In MS Word, this is controlled using Page Setup dialog -> Margins -> Pages -> Multiple pages: -> Mirror margins. Another possible options are 2 pages per sheet and Book fold.
Tab leader (dots) are calculated based on the available space between the end of the text in the entry and the page number. Workaround: to change rendering mode to TextBlockWithPropertyCaching: this.radRichTextBox.TextRenderingMode = TextBlockRenderingMode.TextBlockWithPropertyCaching;
The issue is sporadic. Updating the UI resolves it. Workaround: manually call this.radRichTextBox.ActiveEditorPresenter.RecreateUI(); just after the acception.
The following parts are with hard coded strings and cannot be localized: - Insert Caption (InsertCaptionDialog): Combo boxes for label and separator - Paragraph Properties (ParagraphPropertiesDialog): Units of spacing and indentation values (pt) - Tab Stops Properties (TabStopsPropertiesDialog): The text of the tabStopsToBeClearedTextBloc - Cross references: reference types Figure and Table - TOC and TOF: Heading and Figure, Caption labels - Document Ruler: Tooltips - FormattingColorPicker: The "No Color" string Available in R1 2018 SP2 Release Version.
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.
In some complex script languages, like Telugu and Thai language, some characters are grouped (e.g. consonants + vowels) in new grapheme. For example, type 'p' in Telugu - 'జ', followed by 'ో' - they are combined in new grapheme - 'జో', or paste the following Thai grapheme: ชื UI correctly visualizes this, but: - Text measuring assumes that the grapheme width is equal to the sum of the widths of its parts (characters), which is not correct. Selection and caret position are scrambled because of this. - There are document positions between the grapheme parts (characters), but shouldn't. - When the caret is before the grapheme, deleting with "Delete" key deletes the grapheme in multiple steps (character by character), but should delete it in single step. Deleting with "Backspace" works correctly. - There are some unsupported combinations in some languages. For example in Thai, typing 'z' then 'y' will produce grapheme, but typing 'w' then 'y' will not produce grapheme, and the 'y' should be ignored.
When FlowDirection is set to RightToLeft: <telerik:RadRichTextBox FlowDirection="RightToLeft" /> RadRichTextBox could work as system's RichTextBox - to layout the text correctly and swap the vertical scrollbar on the left side. Another option to consider is to change the default paragraph style (or 'Normal' style?) to have RTL flow. Currently, when this property is set, the text gets reversed and the vertical scrollbar stays on the right side.
When document with field in header/footer is imported from RTF, and subsequently exported to RTF from web layout mode, the formatting of the field is lost.
There is already Author property but it is not filled automatically. It should be filled using the RequestCurrentUserInfo event of the RadDocument, which is currently only used for track changes revisions.
Comments are getting collapsed and clipped when there is not enough vertical space to display all of them.
Currently saving to an .rtf document with footnotes strips the footnotes and endnotes.
TabStopsProperties dialog is non-modal dialog, but it should be modal.
Add a property that can control whether a table row is allowed to break across pages or not.