- Localization for "Simple text" in the Define New List Style dialog and Define New Style dialog at RadRichTextBox.
- Levels (from 1st to 9th) are hardcoded in dialog's code behind and cannot be localized. (these are the items in the 'Apply Formatting to' comboBox)

When the background is defined for a table or a cell, it should be inherited by the paragraphs inside. Currently, the paragraphs are with the background defined in the default style.

When the position on which the users right-click is an annotation start or end marker, the context menu doesn't provide suggestions about spellcheck errors.

Steps to reproduce:

1. Type "The greater the better" in RadRichTextBox with enabled spellchecking
2. Turn on track changes
3. Move the caret to the 't' of "greater"
4. Insert 't' so the word becomes wrong
5. Right-click on the 't' letter inserted in step 4

Observed: The context menu doesn't show suggestions for fixing the misspelled word
Expected: The context menu should suggest a fix

Paragraph spacing from table style is not exported for each paragraph inside the table. The table style defines paragraph properties which should be respected when exporting the styles to HTML.

Workaround: Apply the paragraph settings coming from the table style directly to the elements.
foreach (var table in radRichTextBox.Document.EnumerateChildrenOfType<Table>())
{
    foreach (var paragraph in table.EnumerateChildrenOfType<Paragraph>())
    {
        paragraph.LineSpacing = table.Style.ParagraphProperties.LineSpacing;
        paragraph.LineSpacingType = table.Style.ParagraphProperties.LineSpacingType;
 
        paragraph.AutomaticSpacingAfter= table.Style.ParagraphProperties.AutomaticSpacingAfter;
        paragraph.AutomaticSpacingBefore = table.Style.ParagraphProperties.AutomaticSpacingBefore;
 
        paragraph.SpacingAfter = table.Style.ParagraphProperties.SpacingAfter;
        paragraph.SpacingBefore = table.Style.ParagraphProperties.SpacingBefore;
    }
}

The customers need to customize the dialogs for opening and saving a file. For example, they need to set a default path or extension. With the current implementation, this can be achieved by customizing the commands. Expose an API allowing them to achieve that easily.

Font weight, size and other current editing style properties are not preserved when Shift + Enter key combination is used and the user continues typing.

Note: this is true not only for font weight but for other styling properties such as size, italic etc.

"Win32Exception (0x80004005): Not enough storage is available to process this command" is thrown when multiple RadDocument instances are created in background threads. 

This is due to the fact that RadDocument contains MailMergeDataSource object, which is DependencyObject. When multiple dependency objects are created in different threads, they are not property freed by thread's Dispatcher.

Workaround 1: Microsoft provided workaround in a bug report here:
https://connect.microsoft.com/VisualStudio/feedback/details/620588/system-componentmodel-win32exception-0x80004005-not-enough-storage-is-available-to-process-this-command , namely:
------------------------------
Put the following code:

Dispatcher dispatcher = Dispatcher.CurrentDispatcher;
dispatcher.BeginInvokeShutdown(DispatcherPriority.Normal);
Dispatcher.Run();

anywhere in the background thread processing the RadDocument.
-----------------------------

Workaround 2: Use pooling of the used threads. The problem is that Task Parallel Library (which has built-in pooling) does not use STA threads by default, but this can be achieved by using custom TaskScheduler (attached, the code is get from here: https://code.msdn.microsoft.com/ParExtSamples ):

            var parallelOptions = new ParallelOptions()
            {
                TaskScheduler = new StaTaskScheduler(Environment.ProcessorCount)
            };

            Parallel.For(0, 10000, parallelOptions, cc =>
            {
                    var document = new DocxFormatProvider().Import(data);
                    byte[] pdfBytes = new PdfFormatProvider().Export(document);

            };

When a table in HTML document has width set to 0 (through an attribute or CSS style),  the table is imported with 0 width in the document model. This makes the content unreadable. 

Instead, such width should be treated as if width is not set at all - this way the layout will use only the widths set to the cells.

Workaround: Clear the PreferredWidth property if it is 0.
var tables = this.radRichTextBox.Document.EnumerateChildrenOfType<Table>();
foreach (var table in tables)
{
    if (table.PreferredWidth.Value == 0)
    {
        table.PreferredWidth = null;
    }
}

Fix available in LIB Version 2018.1.326.

Add support for FILENAME field. The field could be evaluated using the last opened/saved file name.

Description:https://support.office.com/en-us/article/field-codes-filename-field-a2946f1b-d822-47dc-ba32-4482aece26bc?ui=en-US&rs=en-US&ad=US

Add support for CREATEDATE field. The field is evaluated using the document metadata.

Description: https://support.office.com/en-us/article/field-codes-createdate-field-440080d1-2d34-494f-bdca-9d451d659d46?ui=en-US&rs=en-US&ad=US

Add support for USERNAME field. The field is evaluated using the document metadata.

Description: https://support.office.com/en-us/article/field-codes-username-field-f564f516-823f-4fb9-9da8-9b6312148053?ui=en-US&rs=en-US&ad=US

An additional line should be inserted between the inner div and the span where the first <br> is inserted.

In Windows 10 1709 Falls creators update there is an upgrade to Microsoft Edge, with which the copy from edge is changed:

1) no longer it is copied in "Rich Text Format"

2) the "HTML Format" data is formatted differently than before - different line separators and the whole html is placed into a single line (unlike before).

A specific combination of document elements causes an infinite measure loop.

Implement support for the SET field.

When the width of the tab stop is set to a negative value, an ArgumentOutOfRangeException is thrown on import. Other applications handle this case and convert the value to a positive number.

Fix is available in LIB Version 2018.1.326.

The content of a page can be aligned vertically. In DOCX, this is a property of the section and is defined with the vAlign element.

<w:sectPr>
…
<w:vAlign w:val="center" />
</w:sectPr>

Currently, the underline is always exported as single. Add support for the other types that can be used in RadRichTextBox.

Currently, paragraphs that have applied a list style but their list level is set to -1 or another invalid value, cannot be imported due to an ArgumentOutOfRangeException. According to the specification, the scenario is invalid, though, in MS Word and WordPad, similar values are not respected.

A document contains a field in result mode different that the one specified in the export settings in the format providers (i.e. a field that need to be updated during the export), and this field is in a header/footer, and another header/footer contains a table with AutoFit to Window size. When this document is exported to docx or RTF, the table is exported with 0 width. The table is visualized splashed in RadRichTextBox, and MS Word behaves strangely and/or doesn't visualize the table at all.

The bug is regression in 2018 R1.

Workaround 1: Change the result mode of all fields in the headers/footers to match the one set in format provider export settings (Result by default) just prior the export.

Workaround 2: Set DocxFormatProvider.ExportSettings.FieldResultMode to null. For the default format provider used from the default Save command, use the following:
((DocxFormatProvider)DocumentFormatProvidersManager.GetProviderByExtension("docx")).ExportSettings = new DocxExportSettings() { FieldResultMode = null };

Fix available in LIB Version 2018.2.723.