Importing a document containing <pre> should interpret it as paragraph with specific (preformatted) style applied.

This results in prompt to save the changes when closing the file.

The fix is available in our latest LIB(v. 2014.3.1222).

"Based on style" combobox is not filled with all linked and paragraph styles in the following cases:
- "Modify style" dialog doesn't display the possible "based on" styles in the combobox when editing linked styles. 
- "Create new style from formatting" dialog doesn't display the possible "based on" styles in the combo box during creation of new linked style.

Steps to reproduce:

Variant 1:
- Click Home -> Styles -> Change Styles in the ribbon UI.
- Expand the the drop down of Heading 1 button and click 'Modify'
Expected: 'Style based on' combobox contains all paragraph and linked styles.
Actual: 'Style based on' combobox is empty.
-------------------
Variant 2:
- Click Home -> Styles -> Change Styles in the ribbon UI.
- Click 'New' button.
- Choose 'Style type:' Linked in the combobox.
Expected: 'Style based on' combobox contains all paragraph and linked styles.
Actual: 'Style based on' combobox is empty.

The fix will be available in our official release Q1 2015.

When inserting text (document fragment) next to a correctly spelled word they get both underlined as incorrect.

When ignoring incorrect words through the Spelling dialog and you reach the last word in the document which is incorrect, only one more word from the beginning of the document is checked prior showing a message that the check is complete. Instead, all incorrect words starting from the beginning of the document should be spellchecked. 

The issue is reproduced when adding the incorrect words to the dictionary. In order to reproduce the issue, only "Ignore" or "Add to Dictionary" action should be applied. When the actions are mixed, the issue is not reproduced.

Workaround: before opening the spellchecking dialog, move caret at the beginning of the document
this.radRichTextBox.Document.CaretPosition.MoveToFirstPositionInDocument();

The issue is reproduced with Marathi IME. Type some letters, press and release shift, then press space. The result is that the current IME text is duplicated. 

Currently, CopyHyperlink command (Context menu over hyperlink -> Copy Hyperlink) puts hyperlink text in plain text format in the clipboard. Instead, it should put the URI. This way when the user pastes in a plaint text editor, they will get the URI.

Workaround: The user could copy the text from the Edit Hyperlink dialog instead. 

Decimal tab stops are aligning numbers to the thousands separator (,) instead of to the decimal point (.).
The fix will be available in the next official release Q3 2014

The fix is available in our latest LIB release (v. 2015.01.0413).

UpdateAllFields method causes StackOverlfowException when:
- there are two TOC fields in the document with specific location (no paragraphs between the two fields)
- when merge fields containing new lines ('\r\n') are updated.

UpdatField method causes StackOverlfowException in the IntervalTree class when:
- A TOC field is updated and the field contains field separator (<w:fldChar w:fldCharType="separate"/>) in its definition. The exception is reproducible when there are section breaks before the TOC. 

Fix available in LIB Version 2017.2.627.

The table preferred width value set to Auto or in percents is ignored and is always exported with fixed value.

Steps to reproduce:
Create a table with two columns in RadRichTextBox.
Set the table preferred width to auto.
Set the table cell preferred width for both columns to 50%.
Export to Docx format.

Observed result: the table has preferred width as fixed value 6.62 inches. The columns have the correct width.
Expected result: the table preferred width to be auto.

Support PDF/A when exporting. 

More information at wikipedia: http://en.wikipedia.org/wiki/PDF/A .

Workaround: Currently, the exported PDF document could be imported with RadPdfProcessing and exported with one of the supported PDF/A levels ( http://docs.telerik.com/devtools/document-processing/libraries/radpdfprocessing/howto/comply-with-pdfa-standard ).

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