In some languages such as German and Swedish, combining correct words into one is a common morphological pattern. Compound words not included in the dictionaries should not be marked as misspelled.

Provide mechanism for selecting an uri from which a dictionary can be downloaded when needed. In this way the client will download only the dictionaries that are in use. If more are needed, they will be downloaded on demand.

Implement import of bullets and numbering which use the old Word 6.0/Word 95 format from RTF. This includes, but is not limited to, the following RTF tags: \pnlvlN, \pnlvlblt, \pnlvlbody, \pnlvlcont. See RTF specification, "Word 6.0 and Word 95 RTF" heading for full description.

WordPad and some legacy systems export lists with this formatting, so the construction is relatively widespread.

According to the specification, if RTF reader doesn't support specific bullets/numbering tags, it can use the \pntext tag to read the bullets/numbering as plain text; but currently RadRichTextBox always ignores the \pntext tag. Because of this, the bullets or numbers of lists in the old format are missing after import.

After further discussion within the XAML team and more research, we decided that introducing a similar property does not align with the current idea and model of RadRichTextBox. Thus, we are declining this item.

RadRichTextBox: Add import/export in the following formats: .mht .odt .epub .doc

Annotation Ranges where SkipPositionBefore is set to false on the AnnotationRangeEnd cause cursor jumps when deleting content to the right of the Annotation Range.

Steps to reproduce:
1. Open a job with Annotation Ranges where SkipPositionBefore is set to false on the AnnotationRangeEnd (I used the Document Protection sample in the demo app)
2. Move your cursor to the end of the range.
3. Hit the delete key
Expected: The cursor remains at the end of the AnnotationRange and content to the right is deleted.
Actual: Content to the right is deleted but eventually the cursor will jump to the right by one position and end up outside the Annotation Range.

In Word I can place text where ever I want, when I use textfields. This should also be possible with RadRichTextBox.

When exporting to PDF this should result in an extra layer for the textfield.

add support for markup "markdown" in my opinion it would be very useful!

After you have inserted a new row from the context menu of the RadRichTextBox, it becomes selected and then if you want to add a new row from the context menu again, the option is disabled. 

You should be able to add a new row, so the insert command must be enabled.

Add support for Widow/Orphan control property of Paragraph. In Open XML specification, this is named "widowControl (Allow First/Last Line to Display on a Separate Page)".

The problem is that as this property is not supported, RadRichTextBox acts as it's 'false' and also doesn't export it, but the default value is actually 'true', which causes layout differences between RadRichTextBox and MS Word.

MS-Word allows a user to toggle the markup and edit the document as final when track changes are enabled. This feature request is allowing something similar in RadRichTextBox.  

We need to support uneditable areas in the document flow. The closes analog in HTML is <div editableContent=false>...</div>.

For now, We can drag or paste Images into RadRichTextBox. But still can't drag or paste files like RichTextBox in Winform. It's very inconvenient！

When adding a comment it should be marked as created from the current user. Layer with tool tips should be added to show this information. Also comment balloons should contain it.

The invalid values should be skipped and the document should be successfully imported.

please add shapes support for radrichtextbox. else support another textbox