When a new document is created and GetStatisticsInfo is called on it, a NullReferenceException is thrown.

The exception is reproduced only with specific custom fonts and is thrown by the ComputeSubset() method of the GlyphTypeface class with the following message: "file does not conform to the expected file format specification". However, we can handle the exception and export the font data using the base class.

Available in LIB Version 2018.2.820.

When a separate file for setting the xaml styles is used and then this file is merged in App.xaml the style cannot be found. 
As a workaround merge the resources directly in the App.xaml.

Fix available in LIB Version 2018.3.1029.

The issue is a regression introduced with another fix, released in R2 2018.

When the first table cell for a table row is vertically merged, the height of the row is exported improperly - instead the height of the row containing the beginning of the merged cell is exported.

Some of the formatting symbols (e.g. space, tab) don't affect the height of the paragraph. With the current implementation, changing the font size of a formatting symbol, which is first in the paragraph, changes its height as well.

The RadNumericUpDown buttons are too small and the selected value is not visible. The issue is not reproducible in NoXaml.

Fix is available in LIB Version 2018.2.716.

Type a few lines in RadRichTextBox.
Double-clicking within a word, holding down the mouse button on the second click, and then drag it. 

Actual: Dragging will move the word instead of extending the selection as it should.
Expected: The selection should be extended. Moving the word shouldn't happen unless you release after the double click and then click and drag. 

Currently RadRichTextBox uses the .NET syntax for the date and time formatting of the code fields. When such strings are exported to or imported from RTF/DOCX, the date and time formatting switch should be converted according to the document format specifications (e.g. 17.16.4.1 Date and time formatting from OOXML specification). Examples of differences:

- 'tt' in .NET is converted to am/pm specifier for the current culture. In DOCX specification, this is denoted as 'am/pm'
- '/' in .NET is converted to date separator for the current culture. In DOCX specification, the symbol doesn't have special meaning, so it's always converted to '/'.

.NET date format strings: https://docs.microsoft.com/en-us/dotnet/standard/base-types/custom-date-and-time-format-strings

MS Word date format strings: 
https://support.office.com/en-us/article/insert-edit-and-view-fields-in-word-c429bbb0-8669-48a7-bd24-bab6ba6b06bb#bm9

Workaround (partial): Modify InsertDateTimeDialog to contain only formats which are compatible with MS Word.

When a table is created, exported to HTML and then imported, the cells become taller. The reason for this behavior is that the table is by default with style TableGrid. When the table is exported to HTML, the style is preserved, however, upon import the style properties are set as local and the style itself is lost. The style by default defines LineSpacing="1" and SpacingAfter="0" for the paragraphs in the table and these are not copied as local. 

This means that if there is a style set to the table that defines paragraph properties as well, these properties will be set.

When inserting a content control (structured document tag) into an empty RadDocument using one of the overloads of the InsertStructuredDocumentTag method accessible from RadRichTextBox and RadDocumentEditor, a NullReferenceException is thrown.

Workaround: Invoke the EnsureDocumentMeasuredAndArranged method before inserting the content control:

document.EnsureDocumentMeasuredAndArranged();

RadDocumentEditor editor = new RadDocumentEditor(document);
editor.InsertStructuredDocumentTag(SdtType.CheckBox);

When inserting a new row using the InsertTableRowBelow below, the expected behavior would be to copy the paragraph styles of the paragraphs in the cells in the existing row. However, the style of the newly created paragraph is initially set to null and at some later point it is set to Normal. This creates an issue when using an HtmlDataProvider, which does not become aware of the change and the source HTML does not become updated with the information that the paragraph has style null.

Workaround: set all paragraphs with style null to have Normal style:

                foreach (var paragraph in RichTextBox.Document.EnumerateChildrenOfType<Paragraph>())
                {
                    if (paragraph.Style == null)
                    {
                        paragraph.StyleName = "Normal";
                    }
                }

Import description lists: <dl>, <dt>, <dd> tags.

Possible way for implementation is with paragraphs with left margin.

When inserting a new row using the InsertTableRowBelow below, the expected behavior would be to copy the paragraph styles of the paragraphs in the cells in the existing row. This works when there is a property set locally, e.g. the text is bold, but the paragraph style, e.g. Heading 1 is lost.