Telerik Document Processing Feedback Portal
Recently Updated
New Items
Most Popular
Status Info
Recently Updated
Request a Feature Report a Bug
Unplanned
Last Updated: 02 Jul 2026 14:22 by Jérémie
PdfProcessing: InvalidOperationException is thrown when exporting a PDF document with a set compliance that processes Type3 font glyphs
Created by: Jérémie
Comments: 0
Category: PdfProcessing
Type: Bug Report
1
PdfProcessing: InvalidOperationException is thrown when exporting a PDF document with a set compliance that processes Type3 font glyphs

InvalidOperationException is thrown when exporting a PDF document with a set compliance that processes Type3 font glyphs.

Workaround: Before export, set compliance to None.

var provider = new PdfFormatProvider();
provider.ExportSettings.ComplianceLevel = PdfComplianceLevel.None;

 

Completed
Last Updated: 02 Jul 2026 07:33 by ADMIN
Release Scheduled For = 2026.2.624 (2026 Q2)
PdfProcessing: Unable to obtain the value of incrementally updated fields
Created by: Michael
Comments: 2
Category: PdfProcessing
Type: Bug Report
7
PdfProcessing: Unable to obtain the value of incrementally updated fields
Unable to obtain the value of incrementally updated fields. The original value of the fields is resolved instead.
In Development
Last Updated: 01 Jul 2026 19:57 by ADMIN
PdfProcessing: MethodAccessException is thrown when exporting documents using .NET Standard references in a .NET Framework environment
Created by: Tony
Comments: 0
Category: PdfProcessing
Type: Bug Report
0
PdfProcessing: MethodAccessException is thrown when exporting documents using .NET Standard references in a .NET Framework environment
MethodAccessException is thrown when exporting documents using .NET Standard references in a .NET Framework environment.
In Development
Last Updated: 01 Jul 2026 07:47 by ADMIN
ADMIN
PdfProcessing: StackOverflowException caused by an infinite parent-child loop in the StructureTree
Created by: Martin
Comments: 0
Category: PdfProcessing
Type: Bug Report
0
PdfProcessing: StackOverflowException caused by an infinite parent-child loop in the StructureTree

The stack shows 1070 repeated frames of:

  • StructElementObject.ProcessChildPrimitive(...)
  • StructElementObject.CopyPropertiesTo(...)


The StructureTree import is traversing a cyclic StructElement graph (or equivalent re-entrant child chain) without a recursion guard.

During this recursion, indirect object resolution repeatedly re-enters the same compressed object:

  • reference.ObjectNumber = 554
  • context.CurrentIndirectReference.ObjectNumber = 554
  • TryGetIndirectObject(554, ...) == false at re-entry
In Development
Last Updated: 30 Jun 2026 14:31 by ADMIN
PdfProcessing: PdfStreamWriter: Duplicated pages when merging documents with identical page content streams but different per-page Resources
Created by: Ian
Comments: 0
Category: PdfProcessing
Type: Bug Report
0
PdfProcessing: PdfStreamWriter: Duplicated pages when merging documents with identical page content streams but different per-page Resources

PdfStreamWriter: Duplicated pages when merging documents with identical page content streams but different per-page Resources.

Workaround: Use the RadFixedDocument.Merge() method instead of the PdfStreamWriter.

In Development
Last Updated: 30 Jun 2026 14:28 by ADMIN
PdfProcessing: NullReferenceException is thrown when importing a document with missing Owner (O) in tagged structure attributes
Created by: Jan
Comments: 0
Category: PdfProcessing
Type: Bug Report
1
PdfProcessing: NullReferenceException is thrown when importing a document with missing Owner (O) in tagged structure attributes
NullReferenceException is thrown when importing a document with missing Owner (O) in tagged structure attributes.
Unplanned
Last Updated: 29 Jun 2026 12:11 by Paulo
PdfProcessing: Signature validation reports file as "modified" while Adobe Acrobat reports "not modified"
Created by: Paulo
Comments: 0
Category: PdfProcessing
Type: Bug Report
1
PdfProcessing: Signature validation reports file as "modified" while Adobe Acrobat reports "not modified"
PdfProcessing: Signature validation reports file as "modified" while Adobe Acrobat reports "not modified".
Completed
Last Updated: 24 Jun 2026 11:22 by ADMIN
WordsProcessing: PdfFormatProvider: NotSupportedImageFormatException is thrown during DOCX to PDF conversion in Linux
Created by: Graeme
Comments: 0
Category: WordsProcessing
Type: Bug Report
0
WordsProcessing: PdfFormatProvider: NotSupportedImageFormatException is thrown during DOCX to PDF conversion in Linux
NotSupportedImageFormatException is thrown during DOCX to PDF conversion in Linux.
Completed
Last Updated: 24 Jun 2026 10:48 by ADMIN
Release 2026.2.624 (2026 Q2)
SpreadProcessing: ArgumentException thrown when file contains format string with modificator [Color]
Created by: Mandip Kaila
Comments: 4
Category: SpreadProcessing
Type: Bug Report
2
SpreadProcessing: ArgumentException thrown when file contains format string with modificator [Color]
Opening a file where there is a format string with modificator [Color11] causes an ArgumentException "Invalid modificator" This prevents the file from opening.
Completed
Last Updated: 24 Jun 2026 10:31 by ADMIN
Release Scheduled For = 2026.2.624 (2026 Q2)
WordsProcessing: PdfFormatProvider: StackOverflowException is thrown during PDF export of a document with a Header/Footer containing a page break
Created by: Jonas
Comments: 0
Category: WordsProcessing
Type: Bug Report
0
WordsProcessing: PdfFormatProvider: StackOverflowException is thrown during PDF export of a document with a Header/Footer containing a page break

StackOverflowException is thrown during PDF export of a document with a Header/Footer containing a page break.

Workaround: Remove page break from all header/footer paragraphs, or from a specific paragraph.

Header defaultHeader = section.Headers.Default;

if (defaultHeader != null)
{
    foreach (var item in defaultHeader.Blocks)
    {
        if (item is Paragraph paragraph)
        {
            paragraph.PageBreakBefore = false;
        }
    }
}

Completed
Last Updated: 24 Jun 2026 10:31 by ADMIN
Release Scheduled For = 2026.2.624 (2026 Q2)
WordsProcessing: PdfFormatProvider: OutOfMemoryException is thrown during PDF export of a document that has floating shapes whose wrap zones block vertical progress
Created by: Jonas
Comments: 0
Category: WordsProcessing
Type: Bug Report
0
WordsProcessing: PdfFormatProvider: OutOfMemoryException is thrown during PDF export of a document that has floating shapes whose wrap zones block vertical progress
PdfFormatProvider: OutOfMemoryException is thrown during PDF export of a document that has floating shapes whose wrap zones block vertical progress.
Completed
Last Updated: 24 Jun 2026 10:31 by ADMIN
Release Scheduled For = 2026.2.624 (2026 Q2)
WordsProcessing: Width property defined in style is not respected in the <colgroup> <col> element
Created by: Babu
Comments: 2
Category: WordsProcessing
Type: Bug Report
1
WordsProcessing: Width property defined in style is not respected in the <colgroup> <col> element

When imported in the WordsProcessing model, the current HTML doesn't respect the defined column width and all columns have identical width:

    <colgroup>
        <col span="1" style="width: 33.3302%;">
        <col span="1" style="width: 17.5658%;">
        <col span="1" style="width: 49.104%;">
    </colgroup>

Observed result:

Expected result:

Workaround: use the width property as follows: 

    <colgroup>
        <col span="1" width="33.3302%">
        <col span="1" width="17.5658%">
        <col span="1" width="49.104%">
    </colgroup>
Completed
Last Updated: 24 Jun 2026 10:31 by ADMIN
Release Scheduled For = 2026.2.624 (2026 Q2)
WordsProcessing: HtmlFormatProvider: HtmlFormatProvider: Multiple CSS classes on an element are not correctly resolved when converted to inline styles
Created by: Kruparao
Comments: 0
Category: WordsProcessing
Type: Bug Report
0
WordsProcessing: HtmlFormatProvider: HtmlFormatProvider: Multiple CSS classes on an element are not correctly resolved when converted to inline styles

Multiple CSS classes on an element are not correctly resolved when converted to inline styles.

Before:

.TelerikNormal {font-family: Calibri;font-size: 14.6666666666667px;margin-top: 0px;margin-bottom: 0px;line-height: 100%;color: #000000;}
.TelerikHeading3 {font-family: Calibri Light;font-size: 22.6666666666667px;}
<p class="TelerikNormal TelerikHeading3"><span>Test</span></p>

Due to order priority, the TelerikHeading3 values override the TelerikNormal values. The font-size becomes 22.6666666666667px.

Convert:

provider.ExportSettings.StylesExportMode = StylesExportMode.Inline;
After:
<p style="font-family: Calibri;font-size: 14.6666666666667px;margin-top: 0px;margin-bottom: 0px;line-height: 100%;color: #000000;"><span>Test</span></p>
Result: TelerikHeading3 and its properties are ignored and not applied during the conversion to inline styles. The font-size is now 14.6666666666667px.

 

Completed
Last Updated: 24 Jun 2026 10:31 by ADMIN
Release Scheduled For = 2026.2.624 (2026 Q2)
ADMIN
WordsProcessing: HtmlFormatProvider: Cell background is not inherited from table background
Created by: Deyan
Comments: 0
Category: WordsProcessing
Type: Bug Report
2
WordsProcessing: HtmlFormatProvider: Cell background is not inherited from table background 
In case table cell doesn't have directly applied background, it should inherit the background of its parent table.
Completed
Last Updated: 24 Jun 2026 10:31 by ADMIN
Release Scheduled For = 2026.2.624 (2026 Q2)
WordsProcessing: DocxFormatProvider: Arabic text's Font size and font family changes after export
Created by: ismayil
Comments: 0
Category: WordsProcessing
Type: Bug Report
0
WordsProcessing: DocxFormatProvider: Arabic text's Font size and font family changes after export

This is the code for import/export which result is illustrated below:

            string inputFilePath = "test1.doc";
            Telerik.Windows.Documents.Flow.Model.RadFlowDocument document;
            Telerik.Windows.Documents.Flow.FormatProviders.Doc.DocFormatProvider doc_provider = new Telerik.Windows.Documents.Flow.FormatProviders.Doc.DocFormatProvider();
            using (Stream input = File.OpenRead(inputFilePath))
            {
                document = doc_provider.Import(input, TimeSpan.FromSeconds(10));
            }

            Telerik.Windows.Documents.Flow.FormatProviders.Docx.DocxFormatProvider docx_provider = new Telerik.Windows.Documents.Flow.FormatProviders.Docx.DocxFormatProvider();
            string outputFilePath = "Exported.docx";
            using (Stream output = File.OpenWrite(outputFilePath))
            { 
                docx_provider.Export(document, output, TimeSpan.FromSeconds(10));
            }

            Process.Start(new ProcessStartInfo() { FileName = outputFilePath, UseShellExecute = true });

Completed
Last Updated: 24 Jun 2026 10:31 by ADMIN
Release Scheduled For = 2026.2.624 (2026 Q2)
WordsProcessing: PdfFormatProvider: OutOfMemoryException is thrown during PDF export of a document that has paragraph indent larger than cell width
Created by: Jonas
Comments: 0
Category: WordsProcessing
Type: Bug Report
0
WordsProcessing: PdfFormatProvider: OutOfMemoryException is thrown during PDF export of a document that has paragraph indent larger than cell width
PdfFormatProvider: OutOfMemoryException is thrown during PDF export of a document that has paragraph indent larger than cell width.
Completed
Last Updated: 24 Jun 2026 10:31 by ADMIN
Release Scheduled For = 2026.2.624 (2026 Q2)
SpreadProcessing: System.InvalidOperationException: 'The axes are incorrectly paired.'
Created by: Eric Moreau
Comments: 0
Category: SpreadProcessing
Type: Bug Report
1
SpreadProcessing: System.InvalidOperationException: 'The axes are incorrectly paired.'

An error occurs while importing an XLSX document with charts. Here is the stack trace:

   at Telerik.Windows.Documents.Spreadsheet.FormatProviders.OpenXml.Xlsx.Contexts.XlsxWorkbookImportContext.PairSeriesGroupsWithAxes()
   at Telerik.Windows.Documents.FormatProviders.OpenXml.Model.Elements.Chart.PlotAreaElement.CopyPropertiesTo(IOpenXmlImportContext context, DocumentChart chart)
   at Telerik.Windows.Documents.FormatProviders.OpenXml.Model.Elements.Chart.ChartElement.CopyPropertiesTo(IOpenXmlImportContext context, DocumentChart chart)
   at Telerik.Windows.Documents.FormatProviders.OpenXml.Model.Elements.Chart.ChartSpaceElement.OnAfterRead(IOpenXmlImportContext context)
   at Telerik.Windows.Documents.FormatProviders.OpenXml.Model.Elements.OpenXmlElementBase.Read(IOpenXmlReader reader, IOpenXmlImportContext context)
   at Telerik.Windows.Documents.FormatProviders.OpenXml.Model.Parts.ChartPart.Import(IOpenXmlReader reader, IOpenXmlImportContext context)
   at Telerik.Windows.Documents.FormatProviders.OpenXml.Model.Parts.OpenXmlPartBase.Import(Stream stream, IOpenXmlImportContext context)
   at Telerik.Windows.Documents.FormatProviders.OpenXml.OpenXmlImporter`1.ImportPartFromArchive(ZipArchiveEntry zipEntry, PartBase part, IOpenXmlImportContext context)
   at Telerik.Windows.Documents.FormatProviders.OpenXml.OpenXmlImporter`1.Import(Stream input, IOpenXmlImportContext context)
   at Telerik.Windows.Documents.Spreadsheet.FormatProviders.OpenXml.Xlsx.XlsxFormatProvider.ImportOverride(Stream input, CancellationToken cancellationToken)
   at Telerik.Windows.Documents.Spreadsheet.FormatProviders.WorkbookFormatProviderBase.Import(Stream input, Nullable`1 timeout)

Completed
Last Updated: 24 Jun 2026 10:31 by ADMIN
Release Scheduled For = 2026.2.624 (2026 Q2)
SpreadProcessing: Empty number format for the chart axis is lost on import/export
Created by: Rory
Comments: 0
Category: Telerik Document Processing
Type: Bug Report
1
SpreadProcessing: Empty number format for the chart axis is lost on import/export

Workaround: this is the missing part after the export:

Completed
Last Updated: 24 Jun 2026 10:31 by ADMIN
Release Scheduled For = 2026.2.624 (2026 Q2)
SpreadProcessing: XlsxFormatProvider: System.NullReferenceException: 'Object reference not set to an instance of an object.' when importing a worksheet with images in .NET Standard
Created by: Joon-Sae
Comments: 0
Category: SpreadProcessing
Type: Bug Report
1
SpreadProcessing: XlsxFormatProvider: System.NullReferenceException: 'Object reference not set to an instance of an object.' when importing a worksheet with images in .NET Standard
This is the stack trace: 
   at Telerik.Windows.Documents.Spreadsheet.Utilities.SpreadsheetHelper.UpdateFloatingImageSize(FloatingShapeBase shape)
   at Telerik.Windows.Documents.Spreadsheet.Utilities.SpreadsheetHelper.CalculateRotatableShapeBoundingRect(Point position, FloatingTransformableShape shape)
   at Telerik.Windows.Documents.Spreadsheet.Layout.RadWorksheetLayout.CalculateShapeBoundingRect(FloatingShapeBase shape)
   at Telerik.Windows.Documents.Spreadsheet.Layout.RadWorksheetLayout.UpdateShapesSizeAndPosition()
   at Telerik.Windows.Documents.Spreadsheet.Layout.RadWorksheetLayout.Measure(CancellationToken cancellationToken)
   at Telerik.Windows.Documents.Spreadsheet.Layout.RadWorksheetLayout.Measure(CellIndex frozenCellIndex, CancellationToken cancellationToken)
   at Telerik.Windows.Documents.Spreadsheet.Model.Workbook.UpdateWorksheetLayout(RadWorksheetLayout worksheetLayout, Worksheet worksheet, Boolean isForPrinting, CancellationToken cancellationToken)
   at Telerik.Windows.Documents.Spreadsheet.Model.Workbook.GetWorksheetLayout(Worksheet worksheet, Boolean isForPrinting, CancellationToken cancellationToken)
   at Telerik.Windows.Documents.Spreadsheet.Model.Workbook.GetWorksheetLayout(Worksheet worksheet, Boolean isForPrinting)
   at Telerik.Windows.Documents.Spreadsheet.FormatProviders.OpenXml.Xlsx.Contexts.XlsxWorksheetImportContext.ImportShapesSizes()
   at Telerik.Windows.Documents.Spreadsheet.FormatProviders.OpenXml.Xlsx.Contexts.XlsxWorksheetImportContext.EndImport(XlsxWorkbookImportContext workbookContext)
   at Telerik.Windows.Documents.Spreadsheet.FormatProviders.OpenXml.Xlsx.Contexts.XlsxWorkbookImportContext.EndImport()
   at Telerik.Windows.Documents.FormatProviders.OpenXml.OpenXmlImporter`1.Import(Stream input, IOpenXmlImportContext context)
   at Telerik.Windows.Documents.Spreadsheet.FormatProviders.OpenXml.Xlsx.XlsxFormatProvider.ImportOverride(Stream input, CancellationToken cancellationToken)
   at Telerik.Windows.Documents.Spreadsheet.FormatProviders.WorkbookFormatProviderBase.Import(Stream input, Nullable`1 timeout)
Completed
Last Updated: 24 Jun 2026 10:31 by ADMIN
Release Scheduled For = 2026.2.624 (2026 Q2)
PdfProcessing: Page content is corrupted when merging pages whose content is an array of content streams
Created by: Craig
Comments: 0
Category: Telerik Document Processing
Type: Bug Report
1
PdfProcessing: Page content is corrupted when merging pages whose content is an array of content streams
When using the PdfStreamWriter to write a PdfPageSource whose content is an array of content streams, the resultant content stream contains concatenated graphic state operators. This results in error when loading the document in Acrobat Reader and corrupted page content.
1 2 3 4 5 6
Create an account Log In
View
Type
Status
Category