Implement import of bullets and numbering which use the old Word 6.0/Word 95 format from RTF. This includes, but is not limited to, the following RTF tags: \pnlvlN, \pnlvlblt, \pnlvlbody, \pnlvlcont. See RTF specification, "Word 6.0 and Word 95 RTF" heading for full description.

WordPad and some legacy systems export lists with this formatting, so the construction is relatively widespread.

According to the specification, if RTF reader doesn't support specific bullets/numbering tags, it can use the \pntext tag to read the bullets/numbering as plain text; but currently RadRichTextBox always ignores the \pntext tag. Because of this, the bullets or numbers of lists in the old format are missing after import.

When text is using fonts with defined ligatures (e.g. Calibri, Gabriola, etc.) and contains character groups with defined ligature for it, the text width is measured incorrectly (shorter that it should be). As caret and selection navigates on positions computed by this measuring system, they are not synchronized with what is shown in the UI (which correctly respects the ligatures), and there is slight offset from the real character positions and/or clipping of part of the letters at the end of the line.

Examples of such groups are (depending on the font) "tt", "ff", "ffi".

Importing a document with block-level content controls from XAML causes them to become corrupt. If you scroll to a position in which the said control is only partially visible a NullReferenceException is thrown.

A possible workaround would be to initially save the document as a DOCX (just exporting it to DOCX will not fix the issue as the information is already corrupt).

Another way to reproduce this issue:

1. Create a new document and insert a Rich Text Content Control.

2. Save the document as a XAML file.

3. Reopen the XAML file.

4. Move the caret inside the Content Control.

5. Try to insert a new line by hitting Enter - no new line is added as the content control is marked as Inline Level after the import in step 3.

Case 2: 

Create a document with TOC where the content control of the TOC contains some other inlines.

 

When there is a table with permission range outside the table (for instance the line above the table) and the user deletes it, then performs undo>>redo>>undo operation, then this leads to a NullReferenceException.

An extra line is added when an HTML document with <br> tag inside a <div> is imported.

When using Crystal/Green/Material/Office2016/Windows11 Theme, the header text of PasteOptionsPicker is not localized.

Current date in Date Picker Content Control cannot be selected.

InvalidOperationException: “Invalid drawing color type.” when importing a color with a null value. 

If you start a selection from the end of a line and go back down (at least one line) and go back to the initial position and release the mouse button, then if you press any of the keyboard arrow keys you will see that the caret's new position is shifted with one line downwards. This is reproducible inside the R1 2023 QSF Examples. You can check the attached video for a demonstration.

Simulate selection when caret is inside a field just like in MS Word.

RichTextBox: Add Word like selection where the entire word is selected when moving forward. When moving backward only the characters are deselected. 

In MS Word,create a new docx file,  insert a table, select the whole table, insert a bookmark.

Open the docx file with RadRichTextBox, the bookmark is missing.

This is because the bookmarkStart is in the first tc, while the bookmarkEnd is after the last tr, TableImporter failed to import the bookmarkEnd.

 

Here is my fix.

When exporting Run fonts (<rFonts>) the East Asian Font attribute (<eastAsia>) is not supported.

Using advanced selection over a line break also selects the first word on the following line.

Extension method GetValueOrNull is exists in two assemblies. 

Clicking over an already selected word is not clearing the selection.

German localization for Automatic color is wrong in the Table border dialog.

The issue is hard to reproduce as it seems to depend on a specific combination between a resolution and text scaling.

When importing a DOCX file, the SdtType of  Rich Text Content Controls is not recognized correctly

As shown in the attached video