Approved
Last Updated: 28 Dec 2018 12:13 by ADMIN
Exported protected document containing be opened even if the correct password is used. The same behavior is reproduced with document(without pages).
Approved
Last Updated: 28 Dec 2018 11:55 by ADMIN
ADMIN
Created by: Tanya
Comments: 2
Category: PdfProcessing
Type: Bug Report
3
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 project attached to the following feedback item to rename the duplicate fields: Provide a way to rename FormFields.
Approved
Last Updated: 28 Dec 2018 10:00 by ADMIN
Created by: Lazar
Comments: 0
Category: PdfProcessing
Type: Feature Request
1
Implement functionality to support scenario when a document which already has a signature to be signed again or add two or more signatures.
Approved
Last Updated: 21 Dec 2018 07:01 by ADMIN
The appearance dictionary specifies how the annotation is presented visually on the page. If the appearance missing or is empty in PDF document NullReferenceException is thrown on import. 

Completed
Last Updated: 17 Dec 2018 12:59 by ADMIN
When documents are exported to PDF, the creation date and modification date are not expected, or, when the time zone is with negative offset, the documents are invalid (detected by validation tools).
Approved
Last Updated: 05 Dec 2018 11:20 by Miguel
Created by: Tanya
Comments: 8
Category: PdfProcessing
Type: Feature Request
2

Currently, signature flags, represented by the 'SigFlags' optional entry, are not imported and exported, and there is no API for setting them.
As a result, documents signed with RadPdfProcessing (or with RadPdfViewer) appear in Adobe Reader without the blue 
document message bar at the top (the analogue of the RadPdfViewer's SignaturePanel).

If the API is supported, setting the flag to 1 or 3 would ensure that the message bar would be visualized in Adobe Reader.

Approved
Last Updated: 03 Dec 2018 06:18 by ADMIN
ADMIN
Created by: Deyan
Comments: 7
Category: PdfProcessing
Type: Feature Request
19
Support conversion of XPS documents to PDF using RadPdfProcessing.
Approved
Last Updated: 30 Nov 2018 14:24 by Jan
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;
        }
    }
}
Approved
Last Updated: 23 Nov 2018 12:48 by ADMIN
ADMIN
Created by: Polya
Comments: 2
Category: PdfProcessing
Type: Feature Request
2
Provide a way to change the Name of a FormField from the RadDocument.AcroForm.FormFields collection.

As a workaround, you could create a new instance of a FormField with the desired name, add the new field in the document and remove the old one. You can use the following approach:
   1) Create a new instance of FormField (with the desired name, passed in the constructor), which will play the role of a copy of a specific FormField
   2) Copy all properties from the original field (they all vary, depending on the concrete type of the FormField, for example CheckBoxField, etc.)
   3) Create a new widget for the new field, and copy all properties from the original field's widget into the new one.
   4) Remove the original field from the RadDocument.AcroForm.FormFields collection and add the new field.
   5) Remove the original widget from the corresponding page's annotation and add the new one.

Attached is a project demonstrating this approach for a CheckBoxField.
Approved
Last Updated: 19 Nov 2018 18:44 by ADMIN
ADMIN
Created by: Deyan
Comments: 4
Category: PdfProcessing
Type: Feature Request
15
They are exported with the /EmbeddedFiles switch. This would allow adding external files to the PDF document.
Approved
Last Updated: 09 Nov 2018 09:24 by ADMIN
Trying to clone the Signature of a SignatureField leads to InvalidOperationException as the FieldName of the cloned signature is already set.
Approved
Last Updated: 06 Nov 2018 17:51 by Brian
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. 
Approved
Last Updated: 06 Nov 2018 14:39 by Georgi
When importing document with predefined ToUnicode CMaps (e.g. Identity-H), an InvalidCastException is thrown with cause: 

Unable to cast object of type 'Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Types.PdfName' to type 'Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Elements.CMaps.ToUnicodeCMap'.
In Development
Last Updated: 31 Oct 2018 16:08 by Georgi
ADMIN
Created by: Deyan
Comments: 0
Category: PdfProcessing
Type: Feature Request
3
The CropBox is currently not supported by RadFixedPage class and is not preserved on an Import-Export scenario with PdfFormatProvider. CropBox is also not supported by PdfPageSource class and it is not preserved by using PdfStreamWriter as well. This property should be implemented in both scenarios.
Approved
Last Updated: 29 Oct 2018 12:36 by ADMIN
Some customers need to export a single page of the PDF document to plain text. Expose such a possibility so the customers don't need to export the whole document.
Completed
Last Updated: 26 Oct 2018 14:46 by ADMIN
Stencil color has to be preserved for images with ImageSource when ImageMask property set to true. Not preserving it results in wrong colors (for instance the image may be visualized as a black rectangle).

Available in R1 2019 Official Release Version.
Completed
Last Updated: 22 Oct 2018 20:11 by ADMIN
The tj operator is responsible for drawing text content. When such operator is left empty, the import throws NullReferenceException because of the missing operands.

Available in LIB Version 2018.3.1022.
Completed
Last Updated: 19 Oct 2018 07:13 by ADMIN
ADMIN
Created by: Deyan
Comments: 0
Category: PdfProcessing
Type: Feature Request
1
This operator modifies the current clipping path by intersecting it with the current path, using the even-odd rule to determine which regions lie inside the clipping path.

Available in R3 2018 SP1 release.
Completed
Last Updated: 19 Oct 2018 07:12 by ADMIN
ADMIN
Created by: Deyan
Comments: 0
Category: PdfProcessing
Type: Feature Request
0
 This is content stream operator that is used to close, fill and then stroke a PDF path geometry.

Available in R3 2018 SP1 release.
Completed
Last Updated: 15 Oct 2018 14:04 by ADMIN
This type of fields is currently not supported: https://feedback.telerik.com/Project/184/Feedback/Details/249205 . However, the fields can be skipped and the other content can be imported without throwing an exception.

Fix available in R3 2018 SP1 release.
1 2 3 4 5 6