RTF import loses the font applied once at paragraph/body level and falls back to a default font instead, when the  \fonttbl  uses flat, non-grouped font entries rather than individually braced  {\fN ...}  fonts.

Workaround: Re-save the document in MS Word.

 

PDF export places fixed-position images on the wrong page.

Missing table row content due to incorrect measurements after PDF export of a specific document.

PdfFormatProvider: Paragraph-style tab stops are not fully ignored during export, causing unexpected tab positions.

PDF export fails after HTML blocks containing empty or named anchors are imported and inserted into a RadFlowDocument through ReplaceText.

HTML importer creates hyperlink field markers for <a name="...">. During block replacement, cloned FieldCharacter instances lose FieldInfo, leaving orphan field markers. PDF exporter later dereferences FieldInfo and throws a NullReferenceException.

Internally, the WebClient class is used to load external resources. This class is not supported in Blazor and WordsProcessing should provide a mechanism for loading the resource.

Hello

Calling MailMerge on a document with a nested repeating group throws NullReferenceException when a merged value contains a line terminator.

All of the following are required to reproduce the crash:

• The group («BeginGroup:Items» … «EndGroup:Items») is nested inside an outer group
• The field whose value contains the newline sits in a later table cell than the group's begin marker
• The value belongs to a non-last record

I have attached a minimal repro demonstrating the bug.

Empty paragraphs are exported to PDF with a bigger font size.

When a paragraph has defined tab stops in its style and has the same tab stops locally cleared, the tab stops are still respected when exporting to PDF. Instead, cleared tab stops should not be respected.

Removing/adding rows/columns inside a worksheet requires all the data after them to be translated according to the change. This operation is slow and affects editing performance.

InvalidDataException is thrown when importing an XLS document with malformed compressed picture data in the drawing layer.

Center alignment is not respected for list numbering.

Expected:

Actual:

The values of rotated widgets on a rotated page are invisible after exporting them. The value can be seen only while editing a field.

Wrapped table cell text is incorrectly split by hyphens ("-").

This is a regression introduced in version 2026.3.826. Use an older version to avoid this issue.

Currently, font registration APIs accept only byte[], requiring callers to load the entire font file into memory before passing it to the library. This can be problematic for large font files, especially CJK fonts, which can significantly increase application memory usage.

When the text is long and AllowScroll is false, the text will be visible, but will be misplaced. The issue is caused by the length of the text because the same field with a shorter text that can fit in the widget's rectangle will be displayed correctly.

There are many instances of the internal Transition, State and ImageXObject classes.

InvalidOperationException: 'isContentReleased' is thrown when appending pages with shared image content to a new document using the PdfStreamWriter.

When two PDFs containing AcroForm fields are merged with PdfStreamWriter, the generated PDF contains page widget annotations whose parent field dictionaries are not correctly registered in the document-level /AcroForm/Fields tree.

The issue is reproducible by merging the same four-page form twice. The resulting PDF contains all widget annotations, but PDF viewers do not resolve the second form’s interactive fields correctly.

Endless loop on PDF export when an empty string is assigned to text fields with no source /V and auto-sized default appearance (/DA with 0 Tf).

Workaround: Instead of an empty string (""), set the value to null. Or don't set it at all and leave it unmodified.