Recently Updated
In Development
Last Updated:
14 Aug 2026 09:19
by ADMIN
ADMIN
Created by:
Tanya
Comments:
0
Category:
WordsProcessing
Type:
Feature Request
The Indent property of Table is not respected by PdfFormatProvider.
In Development
Last Updated:
14 Aug 2026 08:33
by ADMIN
ADMIN
Created by:
Deyan
Comments:
0
Category:
WordsProcessing
Type:
Bug Report
When table cell preferred width is smaller than the first word in the cell the actual exported width should fit the word width when exporting to PDF. Currently in such case the word is split into two lines. The width has to be equal to the word width so the word stays on a single row.
In Development
Last Updated:
13 Aug 2026 19:46
by ADMIN
ADMIN
Created by:
Deyan
Comments:
0
Category:
WordsProcessing
Type:
Bug Report
This is done due to wrong column widths weights calculations.
In Development
Last Updated:
13 Aug 2026 19:40
by ADMIN
ADMIN
Created by:
Mihail
Comments:
2
Category:
WordsProcessing
Type:
Bug Report
Exporting to PDF of a table with a first cell having preferred width of 100% and a second cell having preferred width of auto will result in missing the second cell.
In Development
Last Updated:
13 Aug 2026 16:17
by ADMIN
Created by:
Martin
Comments:
0
Category:
WordsProcessing
Type:
Bug Report
When the table width is set to fixed with the value of zero:
<w:tblW w:w="0" w:type="dxa"/>
In Development
Last Updated:
13 Aug 2026 15:48
by ADMIN
Created by:
Jose
Comments:
0
Category:
WordsProcessing
Type:
Bug Report
Importing HTML tables with mixed inline width styles and auto-width cells, then exporting to PDF, can produce missing/narrow columns or wrapped labels.
For example, a 4-cell row with td style="width: 60%" and td style="width: 40%" causes the unlabeled cells to collapse in PDF output, even though the HTML renders correctly in browser.
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<body>
<table>
<tr>
<td align="right">Customer:</td>
<td style="width: 60%;">Angel Popov</td>
<td align="right">Date:</td>
<td style="width: 40%;">4/4/2004</td>
</tr>
</table>
</body>
</html>Expected: all cells keep visible widths and text stays on one line.
Actual: auto columns shrink too much or disappear during PDF export after HTML import.
Unplanned
Last Updated:
12 Aug 2026 13:26
by Tony
Created by:
Tony
Comments:
0
Category:
WordsProcessing
Type:
Bug Report
PDF export places fixed-position images on the wrong page.
In Development
Last Updated:
11 Aug 2026 16:16
by ADMIN
Created by:
Avrohom Yisroel
Comments:
4
Category:
WordsProcessing
Type:
Bug Report
When measuring nested tables and the levels are more than 5 level, the export is very slow.
Completed
Last Updated:
06 Aug 2026 09:48
by ADMIN
Release 2026.2.519 (2026 Q2)
Created by:
Petter
Comments:
0
Category:
WordsProcessing
Type:
Bug Report
HtmlFormatProvider: Styles are not correctly preserved when a <b> tag is applied to the same styled element.
Workaround: Apply bold through CSS instead of using <b>.
Completed
Last Updated:
06 Aug 2026 05:45
by ADMIN
Release 2026.3.805 (2026 Q3)
Created by:
GuiGuiGui
Comments:
7
Category:
WordsProcessing
Type:
Bug Report
When there is an abstractNum defined with the same abstractNumId in word\glossary\numbering.xml and in the word\numbering.xml, a "System.ArgumentException: An item with the same key has already been added." exception is thrown.
In other cases, the import overwrites the styles from the main document part with the ones defined in the glossary or fails to import different parts of the content.
Workaround: Delete the glossary files:
string path = "File.docx";
using (Stream str = new FileStream(path, FileMode.OpenOrCreate, FileAccess.ReadWrite))
{
using (ZipArchive archive = ZipArchive.Update(str, null))
{
foreach (ZipArchiveEntry entry in archive.Entries.ToList())
{
if (entry.FullName.Contains("glossary/"))
{
entry.Delete();
}
}
}
DocxFormatProvider provider = new DocxFormatProvider();
RadFlowDocument flowDocument = provider.Import(str, null);
}
Completed
Last Updated:
06 Aug 2026 05:45
by ADMIN
Release 2026.3.805 (2026 Q3)
ADMIN
Created by:
Peshito
Comments:
0
Category:
WordsProcessing
Type:
Bug Report
LineInfo objects are not cleared when there are tables in the document being exported to PDF which leads to OutOfMemoryException.
Completed
Last Updated:
06 Aug 2026 05:45
by ADMIN
Release 2026.3.805 (2026 Q3)
Created by:
José Carlos
Comments:
0
Category:
WordsProcessing
Type:
Bug Report
Converting table with custom borders to PDF does not work
Unplanned
Last Updated:
05 Aug 2026 14:07
by Babu
Created by:
Babu
Comments:
0
Category:
WordsProcessing
Type:
Bug Report
Missing table row content due to incorrect measurements after PDF export of a specific document.
Completed
Last Updated:
24 Jul 2026 06:10
by ADMIN
Release 2026.2.723 (2026 Q2)
ADMIN
Created by:
Mihail
Comments:
2
Category:
WordsProcessing
Type:
Feature Request
Text frames are paragraphs of text in a document which are positioned in a separate region or frame in the document and can be positioned with a specific size and position relative to non-frame paragraphs in the current document. More information about it is available in section 22.9.2.18 ST_XAlign (Horizontal Alignment Location) of Open Office XML.
Completed
Last Updated:
24 Jul 2026 06:10
by ADMIN
Release 2026.2.723 (2026 Q2)
ADMIN
Created by:
Deyan
Comments:
1
Category:
WordsProcessing
Type:
Bug Report
When table with table border without color set is created (the color is null), and the document is exported to PDF, ArgumentNullException is thrown.
Workaround: Explicitly set a color where the color is null.
private void PdfExport()
{
var tables = this.document.EnumerateChildrenOfType<Table>();
foreach (var table in tables)
{
TableBorders coloredClone = this.CopyTableBorders_SetColorWhenOmitted(table);
table.Borders = coloredClone;
using (Stream output = new FileStream(fileName, FileMode.OpenOrCreate))
{
provider.Export(this.document, output);
}
}
}
private TableBorders CopyTableBorders_SetColorWhenOmitted(Table table)
{
var leftBorder = new Border(table.Borders.Left.Thickness,
table.Borders.Left.Style,
table.Borders.Left.Color ?? new ThemableColor(Colors.Transparent),
table.Borders.Left.Shadow,
table.Borders.Left.Frame,
table.Borders.Left.Spacing);
var rightBorder = new Border(table.Borders.Right.Thickness,
table.Borders.Right.Style,
table.Borders.Right.Color ?? new ThemableColor(Colors.Transparent),
table.Borders.Right.Shadow,
table.Borders.Right.Frame,
table.Borders.Right.Spacing);
var bottomBorder = new Border(table.Borders.Bottom.Thickness,
table.Borders.Bottom.Style,
table.Borders.Bottom.Color ?? new ThemableColor(Colors.Transparent),
table.Borders.Bottom.Shadow,
table.Borders.Bottom.Frame,
table.Borders.Bottom.Spacing);
var topBorder = new Border(table.Borders.Top.Thickness,
table.Borders.Top.Style,
table.Borders.Top.Color ?? new ThemableColor(Colors.Transparent),
table.Borders.Top.Shadow,
table.Borders.Top.Frame,
table.Borders.Top.Spacing);
var insideHorizontalBorder = new Border(table.Borders.InsideHorizontal.Thickness,
table.Borders.InsideHorizontal.Style,
table.Borders.InsideHorizontal.Color ?? new ThemableColor(Colors.Transparent),
table.Borders.InsideHorizontal.Shadow,
table.Borders.InsideHorizontal.Frame,
table.Borders.InsideHorizontal.Spacing);
var insideVerticalBorder = new Border(table.Borders.InsideVertical.Thickness,
table.Borders.InsideVertical.Style,
table.Borders.InsideVertical.Color ?? new ThemableColor(Colors.Transparent),
table.Borders.InsideVertical.Shadow,
table.Borders.InsideVertical.Frame,
table.Borders.InsideVertical.Spacing);
var tableBorders = new TableBorders(leftBorder, topBorder, rightBorder, bottomBorder, insideHorizontalBorder, insideVerticalBorder);
return tableBorders;
}
Completed
Last Updated:
24 Jul 2026 06:10
by ADMIN
Release 2026.2.723 (2026 Q2)
ADMIN
Created by:
Tanya
Comments:
5
Category:
WordsProcessing
Type:
Feature Request
Add support for horizontal lines in documents.
In DOCX, such lines are defined using the legacy VML definitions:
The definitions above and the <hr/> HTML tag are currently not supported and skipped on import, leading to missing horizontal lines in the document.
In DOCX, such lines are defined using the legacy VML definitions:
<w:pict w14:anchorId="324D5836">
<v:rect id="_x0000_i1025" style="width:0;height:1.5pt" o:hralign="center" o:hrstd="t" o:hr="t" fillcolor="#a0a0a0" stroked="f"/>
</w:pict>
Completed
Last Updated:
24 Jul 2026 06:10
by ADMIN
Release 2026.2.723 (2026 Q2)
Created by:
Veselin
Comments:
0
Category:
WordsProcessing
Type:
Bug Report
NullReferenceException is thrown when importing a document with invalid nesting inside <w:t>.
Unplanned
Last Updated:
22 Jul 2026 08:27
by ADMIN
ADMIN
Created by:
Yoan
Comments:
0
Category:
WordsProcessing
Type:
Feature Request
Add support for Text Frame Properties on PDF export.
Unplanned
Last Updated:
22 Jul 2026 08:25
by ADMIN
ADMIN
Created by:
Yoan
Comments:
0
Category:
WordsProcessing
Type:
Feature Request
Add support for a horizontal line on PDF export.
Completed
Last Updated:
08 Jul 2026 07:58
by ADMIN
Release 2026.2.707 (2026 Q2)
Created by:
Maks
Comments:
4
Category:
WordsProcessing
Type:
Bug Report
StackOverflowException is thrown when exporting a document with circular style links when resolving unpopulated style properties.