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.

If the spell checking dialog is opened when the caret is at the end of the paragraph, the spell check stops after the fist span in the paragraph after which there is a punctuation (e.g. comma or a dot).

However, if the caret is at the beginning of the paragraph (on the first misspelled word for example), everything works as expected.

The layout of the document goes to infinite cycle and the whole application freezes when specific combination (it's not exactly identified) of sections and section column breaks is present in the document. Sometimes UI may freeze when the document is trying to render for first time.

When a document is imported from HTML, we set locally to the span elements Times New Roman as a font family nevertheless it is not declared anywhere. The same applies for the font size as well - it is set to 12.

Workaround: Clear the FontFamily property after import

foreach (Span span in this.radRichTextBox.Document.EnumerateChildrenOfType<Span>())
{
    span.GetStyleProperty(Span.FontFamilyProperty).ClearValue();
    span.GetStyleProperty(Span.FontSizeProperty).ClearValue();
}

"http://" prefix is automatically added by the Insert Hyperlink Dialog when the provided URI is to local path or mapped drive, e.g. "Z:\temp".

Workaround 1: Set HyperlinkPattern to something that matches file paths, e.g.:
(this.radRichTextBox.InsertHyperlinkDialog as RadInsertHyperlinkDialog).HyperlinkPattern = ".*";

Workaround 2: Insert such paths with the "file://" prefix.

When there is a Section with columns layout and it is separated with continuous section break, inserting column break in some of the columns doesn't get into account when the calculations of the available height are made.

When one column section is selected, "Line between" and "Equal column width" checkboxes should be disabled.

Improve measure and arrange of a document and its child document elements respectively - Span, Paragraph, Table, Section and etc. This will also improve the import time for large documents.

Improve the performance when a document is printed.

When documents containing images (e.g. few JPEGs with size of 5 MB) are loaded, the memory usage of the process goes up pretty quickly and eventually OutOfMemoryException is thrown.

This is not conventional memory leak, as managed types are not leaking. After some investigation, we believe that GC cannot collect some MemoryStream objects (used for the conversion of the image from Base64 to PNG) from the Large Object Heap fast enough, or LOH becomes fragmented.



Available in LIB version: 2017.1.213

Text in a section before continuous section break is not evenly distributed among columns when Left column type is applied.  
As a result the first column's height is bigger than the height of the second column. 

Performing Undo of bolded selection when the selection includes two tables separated by a paragraph is nesting the tables which were siblings.

When a conditional table style is applied to a table and the document is exported to RTF format, when the exported document is opened in MS Word, the FontWeight and ForeColor properties are not respected.

Examples:
If Grid Table 4 style from the gallery is applied and the document is exported and opened in MS Word, the FontWeight property is not respected and the text is not bolded.
If Grid Table 5 Dark style from the gallery is applied and the document is exported and opened in MS Word, the FontWeight and ForeColor properties are not respected.

The ImagesDeflaterCompressionLevel and ContentsDeflaterCompressionLevel in the PdfFormatProvider's export settings have 0 for default value instead of -1.

Workaround: Change the settings's properties to -1 explicitly.

When there is applied a local font family, the font family of the theme should be set to none. Otherwise, the font family of the elements that have a local value will be changed.

Workaround: Reset the theme font family after import: 

this.radRichTextBox.Document.Style.SpanProperties.ThemeFontFamily = Telerik.Windows.Documents.Model.Themes.ThemeFontsEnum.none;

Each time the Styles Gallery becomes visible it triggers an update of each style which leads to increased CPU usage. Significant performance delay is not experienced as the update is executed in dispatcher and with delayed execution. However, a blink of the styles could be noticed.

This includes everything related to:

- Navigation of the controls only with keyboard (Tab, Shift+Tab, arrows, Alt+<Letter>)

- Correct Screen Reader pronunciation when entering into/navigating in the control, including RadRichTextBox itself. 

If an Rtf document is imported and then exported to a Docx file, every single paragraph has associated list when the document is opened in MS Word.

Workaround: Before the document export, clear the ListId property:
if (this.radRichTextBox.Document.Style.ParagraphProperties.ListId == -1)
{
    var property = this.radRichTextBox.Document.Style.ParagraphProperties.GetStyleProperty(Paragraph.ListIdProperty);
    property.ClearValue();
}

When exporting to HTML, each two consequent spaces in a run are treated as  . However, when a style is applied to one of the spaces, the span is split and the two spaces are not considered as a pair, therefore, the HtmlFormatProvider exports them as normal spaces.

When the two spaces are the whole content of a paragraph, this paragraph is not visible when the HTML is visualized in a browser.