Hi Team,
              I am sending one html body to outlook 2013 which contain bulletedlist, till my desktop app its bullets are looking ok. but after sending it to outlook new email body, there are too much space between bullet and inline text, please provide input, how can i handle it.
I think my bullets having different pattern which outlook 2013 doesn't support.
Do i need to add any other property background position : inside; something like.


Please find the attachments,
Thanks
Deepak

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

The MoveToCurrentWordEnd will move to a character before the last position when called from the last position in a word and the word is surrounded by annotations.
The MoveToCurrentWordStart will move to the previous word when called from the first position in a word and the word is surrounded by annotations

The behavior is also unexpected for MoveToFirstPositionInParagraph, MoveToLastPositionInParagraph. 

IndexOutOfRangeException is thrown when some JPEG file in the document has Scan Header with fewer components than the Frame Header. The current JpegDecoder implementation requires both JPEG Headers to have the same number of components.

WORKAROUND: PdfImagesCompressionMode.Automatic option may be used in the PdfFormatProvider export settings. This way all JPEG images will be exported to PDF without decoding their pixels and the PDF file will be exported successfully. 

When the document instance is changed (setting RadRichTextBox.Document property to new RadDocument instance), the old document is not released from the memory. There are UI providers, which are not properly removed from the layer's collection.

The issue is regression, introduced in R3 2016.

Workaround 1: Subscribe to DocumentChanging and set the layout mode of RadRichTextBox to Paged. Reset it back to Flow on DocumentChanged.

void radRichTextBox_DocumentChanged(object sender, EventArgs e)
{
    this.radRichTextBox.LayoutMode = DocumentLayoutMode.Flow;
}

void radRichTextBox_DocumentChanging(object sender, EventArgs e)
{
    this.radRichTextBox.LayoutMode = DocumentLayoutMode.Paged;
}

Workaround 2: Remove the WatermarkUILayer. You can achieve that by creating a custom UILayersBuilder. For more information on this approach, check the help article at http://docs.telerik.com/devtools/wpf/controls/radrichtextbox/how-to/features-custom-ui-layers

protected override void BuildUILayersOverride(Telerik.Windows.Documents.UI.IUILayerContainer uiLayerContainer)
{
    base.BuildUILayersOverride(uiLayerContainer);
    uiLayerContainer.UILayers.Remove(DefaultUILayers.WatermarkLayer);
}

Fix available in LIB Version 2017.2.724.

EMF images cannot be natively parsed by the WPF framework and are not supported in RadRichTextBox. Stop the exception so the document can be imported.

Fix available in LIB Version 2017.2.724.

Instead of moving to the same horizontal location in the previous line the caret moves to a location further to the left. If you move the caret with the mouse or arrow keys then the up arrow key works correctly, but if you are actively typing on the current line and hit up arrow the caret usually ends up in the wrong location.

Steps to reproduce:
1. Type line and a half of text in the editor.
2. Without using the mouse, hit the Up arrow key

Expected: The caret moves to the location directly above the current caret position (with the almost the same x-coordinate on the first line).
Actual: The caret moves to the location at the beginning of the first line.

When an enter is pressed the paragraph is split into two parts and does not apply the current editing style to the formatting symbol of the first part.

Steps to reproduce:
Add text to an empty paragraph.
Increase the font-size.
Press enter.

Expected result: If the user starts to write the text should have its font properties from the current editing style. 

Expected result 2: If the client moves the caret around and then return to the beginning of the second paragraph it and start writing, the text should have its font properties from the formatting symbol(which are applied from current editing style when the paragraph has been split). 

When word contains non-letters symbols at its start and/or end, it's always considered incorrect by the spell checker, even when it's present in the spell checking dictionary. The most common case is with abbreviations like "dr.", which should be invalid when are typed without the period ("dr"), but valid otherwise ("dr.")

Partial workaround: add the word without the punctuation to the dictionary. The problem is that the word without the punctuation will also be considered correct.

Uppercase words with non-alphanumeric symbols, e.g. period,  are recognized as spelling errors by the spell checker.

There are two scenarios which we think are related to this.
1. For example, you have  U.N. spell checker is recognized only the U.N and considering the last dot as an end of a sentence. If you add the U.N. to the dictionary the spell checker still recognizes only U.N and the last dot is ignored.
2. The SpellCheckUppercaseWords property of the DocumentSpellChecker is set to false and words with uppercase should be ignored. Nevertheless, this property is set to false the U.N. is not ignored.

The redo command can't be executed if a content outside of a  permission range is selected. For comparison, the undo command can be executed.

Steps to reproduce:
1. Add two paragraphs to the document with text.
2. Select the first paragraph and add permission range.
3. Protect the document.
4. Add text into the permission range.
5. Press Undo (Ctrl+Z).
6. Select text outside of the permission range.
7. Press Redo (Ctrl+R).

Expected: the redo action should be executed.

Fix available in LIB Version 2015.2.515.

When typing in RadRichTextBox, the characters appear in the document with slight delay.

Available in LIB Version 2017.2.619.

When document with large images (the original image cannot fit on the page without resizing) are exported to PDF, the PDF document is visualized distorted by Adobe Reader.

The issue is regression, introduced in 2017 R1 SP1.

Workarounds: 
- Use images that can fit on the page.
- Zoom RadRichTextBox to scale which allows the large images to fit fully on the page.

The fix is available in LIB Version 2017.2.627.

When the LayotMode of RadRichTextBox is set to Flow and a Table is inserted as the first element in this document, the adorner icon is cut off by the document edge and cannot be used.

Tabs button in Paragraph Properties dialog is visible even when RadRichTextBox.TabStopsPropertiesDialog is not set. In addition, pressing the button in this scenario closes the Paragraph Properties dialog itself.

As this property is automatically set using MEF, this situation could happen if the tabs dialog is missing in the the composition container.

Workaround: Check whether the TabStopsPropertiesDialog is null and if true, then hide the TabsButton:

    var windowTabStopsPropertiesDialog = (this.radRichTextBox.TabStopsPropertiesDialog as RadWindow);
    var windowParagraphPropertiesDialog = (this.radRichTextBox.ParagraphPropertiesDialog as RadWindow);
    if (windowTabStopsPropertiesDialog == null)
    {
        (windowParagraphPropertiesDialog.FindName("TabsButton") as RadButton).Visibility = Visibility.Collapsed;
    }

When the preferred width of the table is set to a percentage value and the columns inside have preferred width values in pixels, the bigger width should take precedence when showing the table. At this point, the table column widths are with higher priority.

Bullets of a list are exported with a character which is not proper for plain text.
The indentation of the bullet is also not exported.

As a workaround, the incorrect bullet character could be replaced with something more suitable. Here is an example:
TxtFormatProvider textFormatProvider = new TxtFormatProvider();
exportedText = textFormatProvider.Export(this.radRichTextBox.Document);
string newText = exportedText.Replace((char)61623, (char)8226);

When some cells are merged in one cell and context menu is displayed for the merged cell, "Merge Cells" option is still available in the menu. However it should not be available for a merged cell.

When the main container of a window is ScrollViewer, the caret is not kept in the view while users move it with the arrow keys.