Completed
Last Updated: 19 Apr 2023 08:43 by ADMIN
Release R2 2023
When opened in Adobe Reader it says that the file "claims compliance". However, when verifying the compliance with some validation tools there seem to be some issues mainly related but not limited to fonts. 
Completed
Last Updated: 02 Jul 2025 11:25 by ADMIN
Release 2025.2.701
Completed
Last Updated: 27 Mar 2020 10:46 by ADMIN
Release R2 2020
ADMIN
Created by: Tanya
Comments: 4
Category: PdfProcessing
Type: Bug Report
9
When merging, only the widgets are copied but not their fields. This can lead to ArgumentNullException when exporting the document. Implement copying the fields and consider cases which include collision of names of the fields.

Workaround:
Repair the generated document using the following code:
foreach (Widget widget in this.pdfDocument.Annotations.Where(annot => annot.Type == AnnotationType.Widget))
{
    if (!this.pdfDocument.AcroForm.FormFields.Contains(widget.Field.Name))
    {
        this.pdfDocument.AcroForm.FormFields.Add(widget.Field);
    }
}
In case of Name collision, you can use the attached project or the attached project to the following feedback item to rename the duplicate fields: Provide a way to rename FormFields.
Completed
Last Updated: 10 Feb 2023 07:14 by ADMIN
Release LIB 2023.1.220 (20 Feb 2023)
After signing a document using the PdfProcessing library and the document is loaded in Adobe Acrobat an error is shown when the signature widget is clicked:
Error during signature verification.  

Adobe Acrobat error.
Expected a dict object.
Completed
Last Updated: 14 Mar 2024 09:00 by ADMIN
Release 2024.1.305 (2024 Q1)
For example exporting the text "\uD83D\uDE0A" with "Segoe UI Symbol" font family should export a single smiling face. Instead the characters are skipped during the export as PdfProcessing is trying to export them as separate char values ("\uD83D" and "\uDE0A") and the font does not contain glyphs corresponding to these char codes.
Completed
Last Updated: 24 Feb 2023 13:41 by ADMIN
Release R1 2023 SP1
The current implementation relies on valid cross-reference offsets in the PDF documents so that PDF objects are easily found and parsed. However, we may implement a mechanism for importing documents with invalid offsets for the objects inside the table.
Completed
Last Updated: 28 Jun 2021 10:19 by ADMIN
Release R3 2021
When importing a document containing a specific image stream an exception is thrown.
Completed
Last Updated: 02 Jul 2020 13:13 by ADMIN
Release R3 2020
Table and table cell borders are not evaluated according to inheritance and conflict resolution rules. A conflict will occur when different borders from the table and table cell are overlapping. 

The GetActualValue method of the TableBorders and TableCellBorders could potentially return an incorrect value in some of the following scenarios:

Scenario 1:
A table has cell spacing set to 0. Meaning that the table and table cell borders will overlap.
The table borders have defined all of its borders with border style "Single".
The table cell borders have all of its borders defined with border style "None".

Expected result: the resulting borders should have the border style set to "None" for the location where the table and the cell borders are overlapping.

Scenario 2:
A table has explicitly defined that its right border is with border style "None".
The table has a table style applied with defined border style of type "Single" for all table borders.

Expected result: All of the table borders except the right border should have border style of "Single".

The problem is mostly visible when exporting to PDF and RTF format.
Completed
Last Updated: 08 May 2023 14:18 by ADMIN
Release R2 2023

TableRow which has defined an only val attribute of the trHeight is imported as a row with auto height. By the specification, this is right, but MS Word takes the val value as row height. Also MS Word exports "At Least" row height with only 'val' set.

Workaround: Iterate through the table rows and set them HeightType to Exact or AtLeast:

foreach (var row in this.document.EnumerateChildrenOfType<TableRow>())
{
    row.Height = new TableRowHeight(HeightType.AtLeast, row.Height.Value);
}

Completed
Last Updated: 15 Jul 2020 10:57 by ADMIN
Release R3 2019
This is reproducible with specific PDF files which use custom Encoding for the fonts of the field widgets. 

WORKAROUND: Change the font of VariableContentWidgets before editing the field value. You should additionally call RecalculateContent() method of these widgets if the value of their corresponding fields is not edited. The following method may be used for changing the font of all existing widgets in the document:

private static void FixEncodingIssues(RadFixedDocument document)
{
    foreach(Annotation annotation in document.Annotations)
    {
        VariableContentWidget widget = annotation as VariableContentWidget;

        if(widget != null)
        {
            widget.TextProperties.Font = FontsRepository.Helvetica;
        }
    }
}
Completed
Last Updated: 22 May 2025 13:36 by ADMIN
Release 2025.2.520 (2025 Q2)
Wrong glyph rendering due to incorrectly parsed Type1Font glyph data.
Completed
Last Updated: 22 May 2025 13:36 by ADMIN
Release 2025.2.520 (2025 Q2)

Incorrect timestamp of a DateTime with custom number format.

Expected:

Actual:

Completed
Last Updated: 24 Jun 2021 10:24 by ADMIN
In the document produced by the mail merge, the date time and numeric formatting applied are not respected and the value is in its default format. 
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: 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.'

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: 24 May 2023 08:10 by ADMIN
Release R2 2023
When the last element in a table cell is an empty paragraph, the latter is skipped and not imported. It should be imported even if it's the only paragraph in the cell, as its properties could affect the layout and presentation (borders, colors, spacings).
Completed
Last Updated: 29 Sep 2020 09:03 by ADMIN
Release LIB 2020.3.1005 (05/10/2020)
When xlsx/docx document is imported, and its main story is with non-default name ('workbook. xml'/'document.xml'), e.g. workbook2.xml/document2.xml, NullReferenceException is thrown and the document is not imported.

Note: Such documents are usually produced after conversion from a template dotx/xlsm.
1 2 3 4 5 6