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.

When cells with borders are copied from Microsoft Excel and pasted in RadRichTextBox, some of the borders are missing depending on their type - for example double borders, but also some other types.

Inserting carriage returns in table cell until floating UI container is moved to another page causes a crash.

RadDocument.StreamFromUriResolving is not raised for the main document when InsertPictureField is included in header or footer.

The scenario is very common, as in MS Word the option Table -> Layout -> Cell Size -> AutoFit ->  "AutoFit Contents" changes the PreferredWidth of the table and its columns to Auto.
Also the tables imported from HTML have these properties set by default.

Scenarios:
- Auto-sized table occupies minimal space.
- All auto-sized columns in a table (table itself could be, or could be not, auto-sized) should always be sized proportionally to their content length. Currently, such columns are sized equally in the case when there is enough space for all of the content, which is unexpected. (also see the attached images for the scenario with fixed-width table + auto-sized columns).

When applying a bullet/numbered list and track changes are enabled, the change of the bullet/number should be in indicated with the track changes color.

Currently the changes is only visualized as a line left of the paragraph.

Provide functionality allowing a document to be thumbnailed. The customers should be able to export a document to an image.

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.

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.

Workaround is to enumerate the fields and update them separately.
            foreach (var field in this.radRichTextBox.Document.EnumerateChildrenOfType<FieldRangeStart>())
            {
                this.radRichTextBox.UpdateField(field);
            }

Add dialog previewing how the content of the RadRichTextBox would be printed according to the current settings.

Workaround: Currently this could be implemented with the public API using separate RadRichTextBox in a window.

When track changes are enabled, setting very large values for both the Top and Bottom values of Distance from text, causes an exception in ParagraphLayoutBox.

Stack trace:

{System.NullReferenceException: Object reference not set to an instance of an object. at Telerik.Windows.Documents.Layout.ParagraphLayoutBox.ArrangeOverride(SizeF finalSize) at Telerik.Windows.Documents.Layout.LayoutElement.ArrangeCore(RectangleF finalRect) at Telerik.Windows.Documents.Layout.LayoutElement.Arrange(RectangleF finalRect) at Telerik.Windows.Documents.Layout.SectionLayoutBox.ArrangeOverride(SizeF finalSize) at Telerik.Windows.Documents.Layout.LayoutElement.ArrangeCore(RectangleF finalRect) at Telerik.Windows.Documents.Layout.LayoutElement.Arrange(RectangleF finalRect) at Telerik.Windows.Documents.Layout.DocumentLayoutBox.ArrangeOverride(SizeF finalSize) at Telerik.Windows.Documents.Layout.LayoutElement.ArrangeCore(RectangleF finalRect) at Telerik.Windows.Documents.Layout.LayoutElement.Arrange(RectangleF finalRect) at Telerik.Windows.Documents.Model.RadDocument.Arrange(RectangleF arrangeRect) at Telerik.Windows.Documents.UI.DocumentPrintLayoutPresenter.MeasureOverride(Size availableSize) at System.Windows.FrameworkElement.MeasureOverride(IntPtr nativeTarget, Single inWidth, Single inHeight, Single& outWidth, Single& outHeight)} 

Steps to reproduce:
1. Enable track changes

2. Insert an image

3. Open Floating Blocks Layout Dialog

4. Choose Top and Bottom

5. Set "Distance from text" for both Top and Bottom to 2000px and click OK

Result: Exception is thrown

Additional info: Problem is also reproduced with very large images (1000 x 800 px) and small values for Distance from text.

Tab stops with visible tab leader (dot, hyphen, underscore) are not exported to PDF.

Steps to reproduce:
- Start with empty document
- In Paragraph Properties dialog, choose Tabs
- In Tab dialog, enter Tab stop position = 2, Leader = underscore, and press Set. Press OK
- Add a word, press Tab, add another word
- Export the text to PDF

Expected: the words are separated with underscores in the exported PDF.
Actual: the words are separated with blank space in the exported PDF.

Implement support for exact table row height option. By using this option the text should be clipped when the table row height is lower than the height needed for the text to render. 
The current implementation supports only the at least option.

Most of the CJK characters are not defined or don't look good in fonts not specifically designed for CJK.

Because of this it would be convenient the font to be automatically changed to MS Mincho in case the user starts writing CJK characters. 

Note that if the current font supports CJK (for example Arial Unicode MS), the font is not changed to MS Mincho.

The caret (cursor) is drawn over letters. This is unpleasant, especially with small font sizes. The issue is even more noticeable when the zoom factor is bigger than 100%.

Available in LIB Version 2018.1.312.

Improve the performance when multiple paragraphs are selected and deleted.

Implement a Page Setup dialog which allows the users to modify Margins, Layout, Page Size, etc. of the document.