When an action is executed, say delete, and you perform undo, the text that is inserted back in the control is selected. In RadRichTextBox the end position of the selection is brought into view.

Add support for the following RTF tags (crop from top, bottom, left, right):

\picropt, \piccropb, \piccropl, \piccropr 

Comments are getting collapsed and clipped when there is not enough vertical space to display all of them.

Expose TableOfContentsField.TabStopLeader property which will allow changing the leaders of the tab stops used within the field result. Currently such property exists, but it's internal.

Docx format can encode symbol characters using the <sym> element. Currently this concept is not supported in the document model, and the element is converted to normal character on import. Add support for similar element in the document model, and for its export to Docx.

Add support for TIME field. More information here:
https://support.office.com/en-us/article/Field-codes-Time-field-6cb8fcef-310a-4646-ae6b-886d88335c90?ui=en-US&rs=en-US&ad=US

Local properties are not exported to HTML when style is applied over document element (paragraphs, spans, tables) in case the HtmlExportSettings.StyleExportMode is set to Inline and HtmlExportSettings.StylesRepositoryExportMode is ExportStylesAsCssClasses (which is the default value).

Workaround: Set HtmlExportSettings.StylesRepositoryExportMode to DontExportStyles. This way properties are exported as local properties.

Steps to reproduce:

- Using the Styles dialog, create new "character" style.
- Apply the style over a span with a text.
- Set some local properties to the span - font size or fore color.
- Set HtmlExportSettings.StylesExportMode = StylesExportMode.Inline
- Set HtmlExportSettings.StyleRepositoryExportMode = StyleRepositoryExportMode.ExportStylesAsCssClasses
- Export to HTML.

Expected: Both style and local properties are exported.
Actual: Only the style will be exported.

When document model is used in multi-threaded scenario, all image sources need to be frozen. Expose a method that does that out of the box.

Workaround: Solution with the public API available is in the attached freezeImagesInRadDocument.zip. 

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. 

Implement API for hiding built-in styles from StylesGallery. This should be useful, as currently all built-in styles are visible by default, and the only way to hide them is to include them in the document as set Primary to false.

When creating a hyperlink from selected text using the InsertHyperinkDialog, trailing spaces shouldn't be included in the hyperlink, as in MS Word.

RadRichTextBox always shows more than one page when there is enough space on the screen to render them next to each other. Expose an option to show one page view.

Currently exported DOCX document may be visualized by MS Word with different highlight colors. There is a limitation in the document format which RadRichTextBox doesn't respect, and this could be avoided by unifying the palette in RichTextBox's UI with the one in MS Word.

In RadRichTextBox, the highlight color picker has more colors than the one in MS Word. That is why when exporting paragraph with one of the additional colors, MS Word (the DOCX format) won't use it but will fallback to one of the available colors.

Some customers are complaining that when the mini toolbar is shown, it is semi-transparent - they expect to be fully shown. Currently, this behavior cannot be customized. Think of adding some setting about how this toolbar will be visualized.

ContextMenu holds a reference to last RadRichTextBox it's shown for. Since ContextMenu is cached by MEF, this leads to memory leak. 

Workaround: There are two options:

- manually set different instances of ContextMenu to all your RadRichTextBox-es
this.radRichTextBox.ContextMenu = new Telerik.Windows.Controls.RichTextBoxUI.ContextMenu();

- Create custom context menu that will be non-sharable. MEF will automatically load different instances of it for all RadRichTextBoxes on demand:
[PartCreationPolicy(CreationPolicy.NonShared)]
[CustomContextMenu]
public class NonSharedContextMenu : ContextMenu
{
}

Using any of the options will prevent MEF from creating cached instance of the ContextMenu.

When there isn't space for the first non-repeated row to be drawn on the page, the repeated rows should not be repeated on each page where the table spans - they should be drawn only on the first page (the page where the table begins). 
 
However, currently the requirement described above is not satisfied and the first repeated row is drawn on every page, where the table spans, which is not correct according to the Office Open XML specification. 

Provide option for configuring the measurement units (centimeters [cm], inches [in]) used throughout RadRichTextBox UI, including:
- Ruler (currently supported and configurable through DocumentRuler.MeasurementUnit property which is of type UnitTypes)
- Table dialogs - for indents, widths and heights
- Paragraph indentation (currently shown only in points [pts])
- Section properties - header from top and footer from bottom
- Page setup - columns width in Columns dialog
- Page Margins and Page Size in Ribbon UI

Currently parts of the dialogs and controls shows measures in pixels (actually DIPs), other in inches (e.g. ruler).

Provide option for exporting InlineUIContainer and FloatingUIContainer as images to docx and RTF format.

When text with Code 128 font is rendered in RadRichTextBox, there are some unexpected behaviours:
- Spaces are not rendered (they have special representation in Code 128). This issue will be reproduced for all fonts which define special (non-empty) representation of the space character.
- During rendering, UI inserts  "Left-to-Right Mark" character and "Right-to-Left Mark" character, which are not defined in the font and appear as .notdef glyph, which is white rectangle. This issue will be reproduced for all fonts which do not define these characters.