In Development
Last Updated: 20 Jan 2026 08:22 by ADMIN

The unexpected border array:

14 0 obj
<< /A 16 0 R /Border [ 10 10 10 60 ] /Rect [ 411 36 565 48 ] /Subtype /Link /Type /Annot >>
endobj
According to the PDF Specification:

"In PDF 1.0, the array consists of three numbers defining the horizontal corner radius, vertical corner radius, and border width, all in default user space units. If the corner radii are 0, the border has square (not rounded) corners; if the border width is 0, no border is drawn. (See implementation note 81 in Appendix H.)

In PDF 1.1, the array may have a fourth element, an optional dash arraydefining a pattern of dashes and gaps to be used in drawing the border."

Unplanned
Last Updated: 09 Jan 2026 09:59 by David
InvalidOperationException is thrown when the parser incorrectly interprets delimiter characters within literal strings as structural tokens instead of string data.
Completed
Last Updated: 21 Jan 2026 14:56 by ADMIN
Release 2025.4.1319 (2025 Q4)
Specific characters (" ' ") are not properly resolved from the Encoding differences table.
Completed
Last Updated: 21 Jan 2026 14:56 by ADMIN
Release 2025.4.1319 (2025 Q4)

Introduced in version 2025.4.1104.

Works OK in the previous version.

StackTrace: 

   at Telerik.Windows.Documents.Utilities.Guard.ThrowExceptionIfTrue(Boolean condition, String message)
   at Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Types.IndirectObject.get_Content()
   at Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Export.PdfExportContext.BeginExportIndirectObject(IndirectObject indirectObject, Int64 offset)
   at Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Types.IndirectObject.Write(PdfWriter writer, IPdfExportContext context)
   at Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Export.PdfExporter.WritePendingIndirectObjects(IPdfExportContext context, PdfWriter writer)
   at Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Export.PdfExporter.WriteFontsFromContext(PdfWriter writer, IPdfExportContext context)
   at Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Export.PdfExporter.Export(IRadFixedDocumentExportContext context, Stream output)
   at Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.PdfFormatProvider.<>c__DisplayClass21_0.<ExportOverride>b__0()
   at Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.ExceptionHandling.ExecutionHandler.TryHandleExecution[E](Action operation)
   at Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.PdfFormatProvider.ExportOverride(RadFixedDocument document, Stream output, CancellationToken cancellationToken)
   at Telerik.Windows.Documents.Common.FormatProviders.FormatProviderBase`1.Export(T document, Stream output, Nullable`1 timeout)

Completed
Last Updated: 21 Jan 2026 14:56 by ADMIN
Release 2025.4.1319 (2025 Q4)
Handle the import of documents with invalid offset and no space before dictionary keys.
Completed
Last Updated: 21 Jan 2026 14:56 by ADMIN
Release 2025.4.1319 (2025 Q4)
Created by: Jan
Comments: 0
Category: PdfProcessing
Type: Feature Request
3
Add support for Border annotation property.
Unplanned
Last Updated: 19 Dec 2025 14:40 by Vitalii
SkiaImageFormatProvider: Blacked out images due to incorrectly resolved clipping.
Duplicated
Last Updated: 22 Dec 2025 15:24 by ADMIN
Created by: Vitalii
Comments: 3
Category: PdfProcessing
Type: Feature Request
2

Hello support team,

We faced an exception that ShadingType 1 is not supported. Can you please confirm that this is expected?

Regards,
Vitalii

Completed
Last Updated: 18 Dec 2025 10:14 by ADMIN
Handle the import of incrementally updated documents with invalid cross-reference offsets.
Unplanned
Last Updated: 03 Dec 2025 14:24 by Domenico

This is the code for reproducing the incorrect PDF document. If the step with changing the font is commented, the document is exported properly:

 //Step 1: Create an instance of XlsxFormatProvider to import the Excel file
            XlsxFormatProvider xlsxFormatProvider = new XlsxFormatProvider();
            Telerik.Windows.Documents.Spreadsheet.FormatProviders.Pdf.PdfFormatProvider pdfFormatProvider = new Telerik.Windows.Documents.Spreadsheet.FormatProviders.Pdf.PdfFormatProvider();

            Workbook workbook;
            using (FileStream input = new FileStream("Input.xlsx", FileMode.Open))
            {
                workbook = xlsxFormatProvider.Import(input, TimeSpan.FromSeconds(10));
            }

            //Step 2: Export the workbook to PDF RadFixedDocument to modify fonts
            Telerik.Windows.Documents.Spreadsheet.FormatProviders.Pdf.PdfFormatProvider spread_pdf_provider = new Telerik.Windows.Documents.Spreadsheet.FormatProviders.Pdf.PdfFormatProvider();
            RadFixedDocument fixedDocument = spread_pdf_provider.ExportToFixedDocument(workbook, TimeSpan.FromSeconds(10));

            foreach (var page in fixedDocument.Pages)
            {
                foreach (var content in page.Content)
                {
                    if (content is TextFragment text)
                    {
                        // Replace the font with Helvetica or HelveticaBold based on the original font style
                        text.Font = text.Font.Name.ToLower().Contains("bold")
                            ? FontsRepository.HelveticaBold
                            : FontsRepository.Helvetica;
                    }
                }
            }

            //Step 3: Save the modified RadFixedDocument back to PDF
            string outputFileName = "ExportedWorkbook.pdf";
            Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.PdfFormatProvider fixed_pdf_provider = new Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.PdfFormatProvider();
            using (FileStream output = new FileStream(outputFileName, FileMode.Create))
            {
                fixed_pdf_provider.ExportSettings.DocumentUnhandledException += ExportSettings_DocumentUnhandledException;
                fixed_pdf_provider.ExportSettings.FontEmbeddingType = Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Export.FontEmbeddingType.Subset;
                fixed_pdf_provider.Export(fixedDocument, output, TimeSpan.FromSeconds(10));
            }
            Process.Start(new ProcessStartInfo() { FileName = outputFileName, UseShellExecute = true });

Declined
Last Updated: 10 Dec 2025 12:40 by ADMIN
Created by: Alexandr
Comments: 2
Category: PdfProcessing
Type: Bug Report
4
Please check the attached pdf document showing incorrect stamp processing.
Unplanned
Last Updated: 27 Nov 2025 12:52 by Vitalii

When importing a large document (e.g. 2.3GB) , the library fails to parse int value that exceeds the limit which leads to endless importing:

Completed
Last Updated: 21 Jan 2026 14:56 by ADMIN
Release 2025.4.1319 (2025 Q4)
Handle the import of documents with a negative cross-reference stream offset.
In Development
Last Updated: 09 Dec 2025 10:25 by ADMIN

During export operation of a document that contains signature fields the following error occurs: 

System.InvalidOperationException: 'The signature was not properly initialized for external signing. The signing delegate is missing.'
Completed
Last Updated: 21 Jan 2026 14:56 by ADMIN
Release 2025.4.1319 (2025 Q4)

Setting the ComplianceLevel to PdfA3B and the TaggingStrategy to UseExisting when exporting a PDF document leads to the following Error reported by VeraPdf:

Specification: ISO 19005-3:2012, Clause: 6.2.11.5, Test number: 1
For every font embedded in a conforming file and used for rendering, the glyph width information in the font dictionary and in the embedded font program shall be consistent.
Glyph width 274.4140625 in the embedded font program is not consistent with the Widths entry of the font dictionary (value 272)
In Development
Last Updated: 09 Dec 2025 10:24 by ADMIN

Resaving a document with Acrobat throws an error due to invalid Info dictionary in document trailer.

Unplanned
Last Updated: 12 Nov 2025 10:43 by Scott
Created by: Scott
Comments: 0
Category: PdfProcessing
Type: Feature Request
10
Add support for ShadingType 1.
Completed
Last Updated: 21 Jan 2026 14:56 by ADMIN
Release 2025.4.1319 (2025 Q4)

You need to explicitly set the correct MIME type when embedding the file into the PDF. This is especially important for standards like PDF/A-3 and Factur-X, which require strict metadata and MIME type declarations for embedded files.

The default value /application/octet-stream is too generic and not compliant for XML attachments.

 

Unplanned
Last Updated: 10 Nov 2025 15:01 by Foxy
Handle the import of documents with an invalid cross-reference stream offset.
Completed
Last Updated: 21 Jan 2026 14:56 by ADMIN
Release 2025.4.1319 (2025 Q4)
When import-export a document with embedded font(s) and FontEmbeddingType.Subset set, the subset collection is not updated, and the originally imported font is exported unmodified.
1 2 3 4 5 6