Unplanned
Last Updated:
04 Oct 2023 07:02
by ADMIN
Created by:
Dimitar
Comments:
4
Category:
PdfProcessing
Type:
Feature Request
Expose the fallback mechanism so the fallback fonts can be changed
Completed
Last Updated:
09 Feb 2023 07:41
by ADMIN
Release R1 2023 SP1
Created by:
Dimitar
Comments:
7
Category:
PdfProcessing
Type:
Bug Report
The images inside form sources are not correctly positioned and might be invisible.
This issue is regression it works with R2 2020.
This issue is regression it works with R2 2020.
Completed
Last Updated:
27 May 2021 14:56
by ADMIN
Release R2 2021 SP1
Created by:
William
Comments:
1
Category:
PdfProcessing
Type:
Feature Request
According to the PDF specification (Adobe® Portable Document Format Version 1.7), the appearance dictionary is optional and it is specifying how the annotation is presented visually on the page.
Exceptions thrown:
InvalidCastException: 'Unable to cast object of type 'Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Types.PdfNull' to type 'Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Elements.Annotations.Appearance'.'
NullReferenceException: 'Object reference not set to an instance of an object.'
Unplanned
Last Updated:
09 Aug 2023 08:14
by ADMIN
Created by:
Charles
Comments:
4
Category:
PdfProcessing
Type:
Feature Request
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:
03 Feb 2023 09:27
by ADMIN
Release LIB 2023.1.206 (6 Feb 2023)
Created by:
Dennis
Comments:
3
Category:
PdfProcessing
Type:
Bug Report
Wrong matrix calculations lead to incorrect image (Form XObject) size.
Unplanned
Last Updated:
06 Dec 2021 14:26
by ADMIN
ADMIN
Created by:
Tanya
Comments:
0
Category:
PdfProcessing
Type:
Feature Request
This type of shading is not supported in the current version and a NotSupportedException is thrown when importing documents containing it.
The exception can be suppressed using the Exception Handling mechanism of PdfProcessing.
The exception can be suppressed using the Exception Handling mechanism of PdfProcessing.
Completed
Last Updated:
16 Feb 2022 15:37
by ADMIN
Release R1 2022 SP1
Created by:
Jean-Christian
Comments:
0
Category:
PdfProcessing
Type:
Bug Report
The block measures with high bigger than expected. This is a regression introduced in version 2022.1.106.
Unplanned
Last Updated:
04 Oct 2022 09:15
by Johann
Created by:
Johann
Comments:
0
Category:
PdfProcessing
Type:
Feature Request
WordsProcessing: Add support for TextDirection of table cell when exporting to pdf
Completed
Last Updated:
31 Mar 2023 10:51
by ADMIN
Release R2 2023
Created by:
Pierre-Yann
Comments:
1
Category:
PdfProcessing
Type:
Bug Report
When the document contains an encrypted Hex string in Bookmark titles the strings are not decrypted and they are wrongly displayed.
The observed result using the WPF PdfViewer:
The observed result using the WPF PdfViewer:
Completed
Last Updated:
15 May 2024 06:30
by ADMIN
Release 2024.2.426 (2024 Q2)
Created by:
Abhi
Comments:
1
Category:
PdfProcessing
Type:
Bug Report
I have the following form:
From the screen shot above you can see that the line above 75 is perfectly ok i.e. it doesn't go and intersect with the lines of the 72
but when i perform the following code
var finaldPDFName = "C:\\Users\\Abhishek.Shrestha\\Downloads\\TestABCPDF\\output2322.pdf";
List<byte[]> filledupForms = new List<byte[]>();
PdfFormatProvider provider = new PdfFormatProvider();
RadFixedDocument document = provider.Import(File.ReadAllBytes(InputFileWithInteractiveForms));
var formfields = document.AcroForm.FormFields;
var formFieldsCopy = new List<FormField>(document.AcroForm.FormFields);
// Iterate over the copied form fields and replace the dot character in their names for solving merging issue
foreach (var field in formFieldsCopy)
{
field.Name = field.Name.Replace(".", "");
}
//added this as the values were being hidden by editable fields
document.AcroForm.ViewersShouldRecalculateWidgetAppearances = true;
filledupForms.Add(provider.Export(document));
File.WriteAllBytes(finaldPDFName, provider.Export(document));
I get the following output:
Unplanned
Last Updated:
16 Oct 2024 13:05
by ADMIN
Created by:
SATHEESH KUMAR
Comments:
2
Category:
PdfProcessing
Type:
Feature Request
Support for exporting WEBP images should be implemented.
Completed
Last Updated:
24 Oct 2023 08:50
by ADMIN
Release R3 2023 SP1
Created by:
Eugene
Comments:
2
Category:
PdfProcessing
Type:
Bug Report
Importing a document containing an EI keyword not followed by space or return leads to an endless loop and the document is not imported successfully.
Expected:
Actual:
Unplanned
Last Updated:
07 Nov 2023 11:53
by Mateusz
Created by:
Mateusz
Comments:
0
Category:
PdfProcessing
Type:
Bug Report
After the import-export of a specific document, the paths are thinner and the corners of the path figure are not rounded:
Completed
Last Updated:
12 Feb 2025 15:20
by ADMIN
Release 2025.1.205 (2025 Q1)
Created by:
Eugene
Comments:
0
Category:
PdfProcessing
Type:
Bug Report
This exception was originally thrown at this call stack:
Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Elements.DocumentStructure.PageTreeNode.EnumeratePages(Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Import.Parser.PostScriptReader, Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Import.IPdfImportContext) in PageTreeNode.cs
Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Elements.DocumentStructure.PageTreeNode.EnumeratePages(Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Import.Parser.PostScriptReader, Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Import.IPdfImportContext) in PageTreeNode.cs
Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Elements.DocumentStructure.DocumentCatalog.CopyPagePropertiesTo(Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Import.Parser.PostScriptReader, Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Import.IRadFixedDocumentImportContext) in DocumentCatalog.cs
Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Elements.DocumentStructure.DocumentCatalog.CopyPropertiesTo(Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Import.Parser.PostScriptReader, Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Import.IRadFixedDocumentImportContext) in DocumentCatalog.cs
Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Import.RadFixedDocumentImportContext.BeginImportOverride() in RadFixedDocumentImportContext.cs
Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Import.BaseImportContext.BeginImport(System.IO.Stream) in BaseImportContext.cs
Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Import.PdfImporter.Import(System.IO.Stream, Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Import.IPdfImportContext) in PdfImporter.cs
Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.PdfFormatProvider.ImportOverride.AnonymousMethod__0() in PdfFormatProvider.cs
Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.ExceptionHandling.ExecutionHandler.TryHandleExecution<E>(System.Action) in ExecutionHandler.cs
Completed
Last Updated:
12 Feb 2025 15:20
by ADMIN
Release 2025.1.205 (2025 Q1)
Created by:
Eugene
Comments:
0
Category:
PdfProcessing
Type:
Bug Report
This exception was originally thrown at this call stack:
System.ThrowHelper.ThrowKeyNotFoundException()
System.Collections.Generic.Dictionary<TKey, TValue>.this[TKey].get(TKey)
Telerik.Windows.Documents.Core.PostScript.Data.PostScriptDictionary.GetElementAs<T>(string) in PostScriptDictionary.cs
Telerik.Windows.Documents.Core.Fonts.Type1.Type1Format.Dictionaries.Type1Font.ReadGlyphData(string) in Type1Font.cs
Telerik.Windows.Documents.Core.Fonts.Type1.Type1Format.Dictionaries.Type1Font.GetGlyphDataInternal(string) in Type1Font.cs
Unplanned
Last Updated:
14 Jan 2025 13:52
by ADMIN
Created by:
Desislava
Comments:
0
Category:
PdfProcessing
Type:
Bug Report
It seems the font that is rendered in Adobe is not the same. The document does not contain the font and Adobe and PdfViewer are fallbacking to different fonts.
Completed
Last Updated:
10 Jan 2018 11:41
by ADMIN
ADMIN
Created by:
Deyan
Comments:
0
Category:
PdfProcessing
Type:
Feature Request
Encryption Algorithm 4 is implemented for R1 2018 official release. This includes all encryptions except AES 256 which is related to Encryption Algorithm 5. For AES 256 you may vote and follow this feedback item: https://feedback.telerik.com/Project/184/Feedback/Details/240154-pdfprocessing-support-encryption-algorithm-5-with-aes-256
Unplanned
Last Updated:
28 Mar 2018 13:09
by ADMIN
ADMIN
Created by:
Deyan
Comments:
2
Category:
PdfProcessing
Type:
Feature Request
This would ensure preserving the existing PDF file pages and document properties untouched and additionally would allow making a few modifications to the file. By appending bytes to existing PDF file one may achieve: - Modifying specific pages content and properties. - Adding new pages to pages collection. - Modify some document properties (such as Bookmarks). - Edit interactive forms field values. - Add digital signatures to existing documents.
Completed
Last Updated:
24 Sep 2019 13:40
by ADMIN
Release R3 2019
ADMIN
Created by:
Tanya
Comments:
0
Category:
PdfProcessing
Type:
Feature Request
This type of destinations is not supported and leads to InvalidCastException when importing such elements.
Unplanned
Last Updated:
19 Sep 2017 19:31
by Vasim
Created by:
Vasim
Comments:
4
Category:
PdfProcessing
Type:
Feature Request
Currently, there is no way to know when a new page is created when content "overflows" to the next page This event may be needed in order to generate the header and footer based on the currently generated content. In simple header/footer scenarios, however, this event may not be needed and the headers and footers may be drawn after all pages are generated as described in the comments below.