Unplanned
Last Updated: 06 Jun 2018 15:02 by ADMIN
Currently, a default constant value is used for the font size in this scenario.
Unplanned
Last Updated: 12 Mar 2025 08:26 by ADMIN
For instance, we may implement WritePageAsync method in addition to the existing WritePage method. This is a similar scenario as in System.IO.StreamWriter class which has WriteLine and WriteLineAsync methods.
Completed
Last Updated: 01 Sep 2020 08:52 by ADMIN
Release R3 2020
When importing color space defined as an external resource name, a NotSupportedColorSpaceException: 'CS0 color space is not supported.' is thrown.
Completed
Last Updated: 13 Nov 2024 08:50 by ADMIN
Release 2024.4.1106 (Q4 2024)
In principle, the blend function B (Cb , Cs ) is used in the compositing formula to customize the blending operation in Adobe transparency imaging model. The blending mode may define any function which yields another result color from the backdrop and source colors. This will allow overlaying objects on each other forming a transparency stack.

Support for the Blend Mode parameter of the external graphic state should be implemented.
Completed
Last Updated: 07 Jul 2020 08:57 by ADMIN
Release R3 2020
According to the specification, the startfref keyword must be followed by the offset the xref table start on, defined on a new line. Some documents, however, have both entries defined on the same line, which leads to InvalidOperationException with message "Stack empty" while importing. Make sure this case is handled in PdfProcessing as well.
Completed
Last Updated: 27 Feb 2023 12:17 by ADMIN
Release R1 2023 SP1

CryptographicException is thrown when saving with PdfStreamWriter or importing with PdfFormatProvider.

The exception: System.Security.Cryptography.CryptographicException: 'The input data is not a complete block.'

Duplicated
Last Updated: 09 Dec 2021 07:22 by ADMIN
Created by: Maik
Comments: 6
Category: PdfProcessing
Type: Feature Request
6
Type 3 fonts are currently not supported.
Completed
Last Updated: 15 May 2024 06:30 by ADMIN
Release 2024.2.426 (2024 Q2)

According to the PDF specification:
A clipping path operator (W or W*) may appear after the last path construction operator and before the path-painting operator that terminates a path object.

Invalid:

W                          % clipping path operator
0 0 m                     % start of the path construction
596 0 l
596 842 l
0 842 l
h                            % end of the path construction
n                            % path-painting operator
Valid:
0 0 m
596 0 l
596 842 l
0 842 l
h
W
n

Currently (in the invalid cases), the path construction is skipped on import.

Duplicated
Last Updated: 31 Jan 2024 08:08 by ADMIN
Created by: Hugo
Comments: 0
Category: PdfProcessing
Type: Feature Request
6
Represents Highlights in PDF content. While the other annotations are drawn on top of the content, the highlight annotation is behind the text it highlights. The precise place where the highlight should be placed is described in the PDF file with the BDC, MCID and EMC operators. 
Completed
Last Updated: 12 Nov 2025 11:41 by ADMIN
Release 2025.4.1104 (2025 Q4)
Created by: Dimitar
Comments: 0
Category: PdfProcessing
Type: Feature Request
6
Add support for the PAdES-BES signature standard
Completed
Last Updated: 02 Aug 2024 11:09 by ADMIN
Release 2024.3.802 (2024 Q3)
Created by: PBucher
Comments: 0
Category: PdfProcessing
Type: Feature Request
6
A text annotation represents a “sticky note” attached to a point in the PDF document. When closed, the annotation appears as an icon; when opened, it displays a pop-up window containing the text of the note in a font and size chosen by the viewer application.
Completed
Last Updated: 26 Jan 2026 14:32 by ADMIN
Release 2025.2.520 (2025 Q2)
Unplanned
Last Updated: 30 Jul 2024 14:14 by Mathew

This is the code for inserting the image: 

        static void Main(string[] args)
        {
            FixedExtensibilityManager.ImagePropertiesResolver = new ImagePropertiesResolver();

            //Telerik.Windows.Documents.Extensibility.JpegImageConverterBase defaultJpegImageConverter = new Telerik.Documents.ImageUtils.JpegImageConverter();
            //Telerik.Windows.Documents.Extensibility.FixedExtensibilityManager.JpegImageConverter = defaultJpegImageConverter;

            //Output("fyb-64.png", "output-working.pdf");
             Output("fyb.png", "output-broken.pdf");
        }
        private static void Output(string resourceName, string outputFileName)
        {
            var document = new RadFixedDocument();
            using (var editor = new RadFixedDocumentEditor(document))
            {
                Stream image = new FileStream(resourceName, FileMode.Open);

                var table = new Table
                {
                    LayoutType = TableLayoutType.FixedWidth,
                    Margin = new Thickness(10, 0, 0, 0),
                };

                var row = table.Rows.AddTableRow();
                var cell = row.Cells.AddTableCell();
                var block = cell.Blocks.AddBlock();
                block.InsertImage(image);
                editor.InsertTable(table);

                var pdfData = ExportToPdf(document);
                File.Delete(outputFileName);
                File.WriteAllBytes(outputFileName, pdfData);

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

        private static byte[] ExportToPdf(RadFixedDocument document)
        {
            byte[] pdfData;

            using (var ms = new MemoryStream())
            {
                var pdfFormatProvider = new PdfFormatProvider();
                pdfFormatProvider.Export(document, ms);
                pdfData = ms.ToArray();
            }

            return pdfData;
        }

Workaround: Instead of setting the ImagePropertiesResolver, set the JpegImageConverter: 

            Telerik.Windows.Documents.Extensibility.JpegImageConverterBase defaultJpegImageConverter = new Telerik.Documents.ImageUtils.JpegImageConverter();
            Telerik.Windows.Documents.Extensibility.FixedExtensibilityManager.JpegImageConverter = defaultJpegImageConverter;

Completed
Last Updated: 12 Feb 2025 15:20 by ADMIN
Release 2025.1.205 (2025 Q1)

When loading some PDF documents with German culture, part of the text got missing.

Workaround: set English culture before loading the document

Thread.CurrentThread.CurrentCulture = new System.Globalization.CultureInfo("en-US");

Completed
Last Updated: 12 Feb 2025 15:21 by ADMIN
Release 2025.1.205 (2025 Q1)
ArgumentNullException is thrown when importing a document with missing indirect reference object.
Completed
Last Updated: 22 May 2025 13:36 by ADMIN
Release 2025.2.520 (2025 Q2)
IndexOutOfRangeException is thrown due to wrongly processed image data.
Completed
Last Updated: 12 Nov 2025 11:41 by ADMIN
Release 2025.4.1104 (2025 Q4)
Creating a document from an SVG image with a CapPathRound (stroke-linecap="round") adds unexpected lines.
Completed
Last Updated: 12 Nov 2025 11:41 by ADMIN
Release 2025.4.1104 (2025 Q4)
Solid lines appear over dashed lines when generating PDF from SVG diagram.
Completed
Last Updated: 12 Nov 2025 11:41 by ADMIN
Release 2025.4.1104 (2025 Q4)
OutOfMemoryException is thrown when importing a large document with invalid cross-reference table.
Unplanned
Last Updated: 05 Jan 2018 08:06 by ADMIN
Currently RadPdfProcessing allows setting standard fonts using FontsRepository static properties.

However, in RadWordsProcessing font can be set only by specifying FontFamily, FontWeight and FontStyle. As there is no way to set standard fonts this way, API users cannot benefit from using these fonts which may help them achieve smaller PDF size as standard fonts may not be embedded. The same applies to RadSpreadhProcessing as well.