Unplanned
Last Updated: 09 Jul 2025 14:35 by Vitalii

It would be great if the SkiaImageExportSettings offer a DocumentUnhandledException event allowing the developer to handle specific errors when exporting to image formats.

This would be an essential improvement in the existing Exception handling mechanism and would enable exporting PDF documents to images even though some parts of the image may not be completely supported: https://docs.telerik.com/devtools/document-processing/libraries/radpdfprocessing/features/handling-document-exceptions 

Unplanned
Last Updated: 02 Jul 2025 06:41 by ADMIN

The PDF/A-1 standard uses the PDF Reference 1.4 and specifies two levels of compliance:

- PDF/A-1b - Its goal is to ensure reliable reproduction of the visual appearance of the document.

- PDF/A-1a - Its objective is to ensure that documents content can be searched and re-purposed. This compliance level has some additional requirements:

  • Document structure must be included.
  • Tagged PDF.
  • Unicode character maps
  • Language specification.

Since the PdfProcessing and its PdfFormatProvider is compliant with the PDF Reference 1.7. , the produced documents are created with this version as well: 




In Development
Last Updated: 01 Jul 2025 12:01 by ADMIN
Handle the import of documents when the GoToR action`s file specification object is a string.
Unplanned
Last Updated: 30 Jun 2025 14:58 by ADMIN
ADMIN
Created by: Tanya
Comments: 3
Category: SpreadProcessing
Type: Feature Request
10

Provide the ability to work with images in headers/footers of a worksheet. Note that large images put in headers are visualized as watermarks on printing/exporting to PDF.

Watermark in Excel: https://support.office.com/en-us/article/add-a-watermark-in-excel-a372182a-d733-484e-825c-18ddf3edf009

 

Unplanned
Last Updated: 23 Jun 2025 07:53 by Vitalii
Handle documents with mismatched font Subtype and FontFile type when exporting PDF to image with SkiaImageFormatProvider.
Unplanned
Last Updated: 13 Jun 2025 10:08 by ADMIN

In the 2025 version of the Documents packages, "TimeSpan? timeout" were added to a number of interfaces, with the old versions obsoleted, for example: IWorkbookFormatProvider.Import & IWorkbookFormatProvider.Export.

This is a very strange choice, because this limits the flexibility of the interfaces for no reason at all. By only providing the TimeSpan parameter and not a CancellationToken is currently impossible to cancel the operation because e.g. an API request was canceled.

Internally these methods are implemented by first creating a cancellation token using

using CancellationTokenSource cancellationTokenSource = CancelationTokenSourceFactory.CreateTokenSource(timeout);

the token from this CancellationTokenSource is then passed to a protected method. Because this internal method uses a CancellationToken anyway, there is practically 0 development cost to exposing this in the interface, which makes the choice not to do so even more confusing.

The interfaces should expose methods that take a CancellationToken instead of a TimeSpan. This would allow for the same functionality as the TimeSpan parameter, by simply passing a cancellation token with a CancelAfter set with a TimeSpan, and an extension method could be provided for the interface which does exactly that, so users can still call these methods with a TimeSpan parameter if they wish to do so for convenience.

Please, in the next version, make these interfaces methods like this:

Workbook Import(Stream input, CancellationToken cancellationToken = default);
void Export(Workbook workbook, Stream output, CancellationToken cancellationToken = default);

and, for convenience, add extension methods for these like this:

public static class WorkbookFormatProviderExtensions
{
    public static Workbook Import(this IWorkbookFormatProvider workbookFormatProvider, Stream input, TimeSpan? timeout)
    {
        using CancellationTokenSource cancellationTokenSource = CancelationTokenSourceFactory.CreateTokenSource(timeout);
        return workbookFormatProvider.Import(input, cancellationTokenSource.Token);
    }
}

Affected interfaces I've run into so far:

  • Telerik.Windows.Documents.Spreadsheet.FormatProviders.IWorkbookFormatProvider
  • Telerik.Windows.Documents.Common.FormatProviders.IFormatProvider<T>

There may be more with this same pattern, I haven't checked.

Unplanned
Last Updated: 12 Jun 2025 08:44 by Lorenzo
Created by: Lorenzo
Comments: 0
Category: SpreadProcessing
Type: Feature Request
0
Add support for Stock charts (StockChart).
Unplanned
Last Updated: 06 Jun 2025 14:56 by ADMIN
ADMIN
Created by: Deyan
Comments: 10
Category: SpreadProcessing
Type: Feature Request
33
Add support for pivot tables.
Duplicated
Last Updated: 03 Jun 2025 13:56 by ADMIN
Created by: Brian
Comments: 1
Category: SpreadProcessing
Type: Feature Request
2
Charts in excel have support for minor grid lines. This is not supported here.
Duplicated
Last Updated: 03 Jun 2025 13:02 by ADMIN
Created by: Brian
Comments: 1
Category: Telerik Document Processing
Type: Feature Request
1
In charts it should be possible to axis titles.
Unplanned
Last Updated: 03 Jun 2025 10:23 by Rey
Add support for "AcroSendMail:SendMail" named action.
Unplanned
Last Updated: 03 Jun 2025 05:57 by Eli
Such a document can be considered as invalid. However, it would be good to provide functionality to handle it.  
Unplanned
Last Updated: 30 May 2025 08:16 by ADMIN
ADMIN
Created by: Martin
Comments: 0
Category: PdfProcessing
Type: Feature Request
0
Part 3 of the standard, published on October 15, 2012, differs from PDF/A-2 in only one regard: it allows embedding of arbitrary file formats (such as XML, CSV, CAD, word-processing documents, spreadsheet documents, and others) into PDF/A conforming documents.
Unplanned
Last Updated: 28 May 2025 07:54 by ADMIN
ADMIN
Created by: Martin
Comments: 0
Category: PdfProcessing
Type: Feature Request
0

Purpose: Long-term archiving of electronic documents with full semantic structure.

  • "A" for Archiving
  • Level "1a" ensures:

    • Tagged PDF (with proper logical structure and reading order)

    • Unicode text for proper text extraction and searchability

    • Embedded fonts (for consistent rendering)

  • Restrictions:

    • No audio/video

    • No encryption

    • No JavaScript

    • No external content (everything must be self-contained)

  • Based on: PDF 1.4 (Acrobat 5)

Completed
Last Updated: 22 May 2025 13:37 by ADMIN
Release 2025.2.520 (2025 Q2)
Created by: Lazar
Comments: 6
Category: PdfProcessing
Type: Feature Request
27
Implement functionality to support scenario when a document which already has a signature to be signed again or add two or more signatures.
Completed
Last Updated: 22 May 2025 13:37 by ADMIN
Release 2025.2.520 (2025 Q2)
Handle the import of documents with Associated Files (/AF) elements whose content is set to null.
Completed
Last Updated: 22 May 2025 13:37 by ADMIN
Release 2025.2.520 (2025 Q2)
Handle the import of documents with null elements in the Associated Files (/AF) collection.
Completed
Last Updated: 22 May 2025 13:37 by ADMIN
Release 2025.2.520 (2025 Q2)
Created by: João
Comments: 0
Category: PdfProcessing
Type: Feature Request
0
Introduce support for UnShrinking - Method 1.
Completed
Last Updated: 22 May 2025 13:37 by ADMIN
Release 2025.2.520 (2025 Q2)
Created by: Charles
Comments: 4
Category: PdfProcessing
Type: Feature Request
4

This type of action is currently not supported and a NotSupportedActionException is thrown when accessing such an object.

These exceptions can be handled using the Handling Exceptions mechanism.

Completed
Last Updated: 22 May 2025 13:37 by ADMIN
Release 2025.2.520 (2025 Q2)
ADMIN
Created by: Martin
Comments: 0
Category: PdfProcessing
Type: Feature Request
0
Export AdditionalActions of the page when merging pages with PdfStreamWriter.
1 2 3 4 5 6