Add the following code to an application with a RadRichTextBox in it:

for (var i = 0; i < 1000; i++)
{
    var doc = radRichTextBox.Document.CreateDeepCopy();
}

If your document does not contain any lists it behaves as expected: memory usage increases until the next GC when it is collected. If there are lists in your document the RadDocument instances created by CreateDeepCopy are never collected and your app will run out of memory.

Fix available in LIB Version 2018.3.1029.

The RtfFormatProvider does not take the fonts from the Font.Manager

Workaround: 

Unregister all custom fonts and the use the FontSubstituting event to supply the correct fonts:

private void ImportSettings_FontSubstituting(object sender, Telerik.Windows.Documents.FormatProviders.FontSubstitutingEventArgs e)
{
    var fonts = Wpf.Fonts.Fonts.GetAllAvailableFonts();
    var ff = fonts.Where(x => x.Source == e.OriginalFontName).FirstOrDefault();
    e.SubstitutionFontFamily = ff; 

}

After the import is complete you can register the fonts again.

The caret gets a wrong size when positioned on annotation start/end.

Seems that the algorithm is not showing the appropriate results when a word has apostrophe. For example typing "etre" does not suggest "être".

A custom third-party spell checker library - NHunspell can be used. 
SDK Example demonstrating this approach can be found in our XAML-SDK portal:
https://github.com/telerik/xaml-sdk/tree/master/RichTextBox/NHunspellSpellChecking

The fix will be available in the next official release Q1 2015.

If I setup the richtextbox content through the UI as shown in P1.png and try to restore it by pasting the generated html, I get instead P2.png. Expected to be the same. 

I attached the sample project. We're using the recommended settings to use the same html in telerik reports, but can't find the reference on your site, it used on the on this link http://docs.telerik.com/devtools/wpf/controls/radrichtextbox/import-export/features-import-export-settings#htmlformatprovider

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.

Steps to reproduce:
1. Insert a table into the document with borders enabled
2. Zoom out so the zoom level is below 100%
Expected behavior: The borders are always rendered at a minimum of 1px width, even if the calculated size is below 1 at the current zoom level (This is what Word does)
Actual behavior: Some of the borders do not render.

Finding text with regex for the last paragraph is not possible. This is caused by the fact that the search treats the last paragraph symbol as the last paragraph.

Switching between bulleted and numbered lists only affects current paragraph instead of changing the list for all paragraphs currently included in it.

Steps to reproduce
1. Create a numbered list with several items
2. Click the bulleted list button
Expected behavior: The entire list switches from numbered to bulleted
Actual behavior: The current list item switches to bulleted but the rest of the list remains numbered.


Workaround: When the ToggleBulletsCommand is executed, traverse the PreviousSiblings and NextSiblings of the current paragraph and change their list properties if they belong to the same list. Sample code attached. Note: the workaround will change the list properties only for the consecutive paragraphs of the same list and will create a selection to do so.

"Increase Indent" and "Decrease Indent" buttons in the Ribbon (the same commands are invoked when Tab is pressed in specific situations) apply different indent step to the selected paragraphs, depending on the number of selected paragraphs: 
- when applied on one paragraph, the indentation is changed with 18.0 px. 
- when applied on two paragraphs, the indentation is changed with 36.0 px.
- and so on.

Some dialogs like ParagraphPropertiesDialog and SectionColumnsDialog have dependency properties for defining the width of the numerics. When creating implicit style, the value of these custom properties results in 0 and they are invisible in the UI.

Workaround: Set the value of the property in the custom style. For paragraph properties dialog:

<Style TargetType="rtb:RadParagraphPropertiesDialog" BasedOn="{StaticResource CustomStyle}" >
    <Setter Property="NumericWidth" Value="85"/>
</Style>