Approved
Last Updated: 22 Nov 2019 08:08 by ADMIN
By specification, the InteractiveForm fields can have the same name if they are descendants of a common ancestor. Such fields are different representations of the same underlying field; they should differ only in properties that specify their visual appearance. When such a document is imported an ArgumentException: 'An item with the same key has already been added.' is thrown.
Approved
Last Updated: 20 Nov 2019 13:58 by ADMIN
Support for validating signature fields signed with signatures that are encoded in ETSI.CAdES.detached encoding should be added.
Approved
Last Updated: 13 Nov 2019 15:06 by ADMIN
When a document is imported the FontsRepository caches the created font instances for performance reasons. API should be provided for clearing the cached instances in order to reduce memory consumption.
Approved
Last Updated: 14 Oct 2019 17:31 by ADMIN
Created by: Narendra
Comments: 0
Category: PdfProcessing
Type: Feature Request
0
These permissions are defined on a document level and apply permission handlers. The permission handlers are similar to the security handlers but do not require the document to be encrypted. They are also used to determine which objects are to be included in the digest calculation used for the digital signature functionality.
Approved
Last Updated: 10 Oct 2019 14:09 by ADMIN
By specification the destination string can be a string of up to 512 bytes. However, the current implementation supports strings of up to four bytes which leads to: ArgumentOutOfRangeException: 'bytes should be less or equal than 4.Parameter name: bytes'.
Approved
Last Updated: 09 Oct 2019 13:11 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: 04 Oct 2019 13:36 by ADMIN
Created by: Rick Kauwen
Comments: 0
Category: PdfProcessing
Type: Feature Request
1
This feature is currently supported only for the .NET Framework and .NET Core applications for Windows.
Approved
Last Updated: 01 Oct 2019 11:43 by ADMIN
If ImageInline's size is set through its Size property and not through Height or Width, the given size is not respected on export.
Approved
Last Updated: 23 Sep 2019 17:19 by ADMIN
When there is a destination object in a RadFixedDocument and it doesn't have page set (it is null), an exception is thrown. However, this is supported by Adobe and it is not forbidden in the Pdf specification.
Approved
Last Updated: 20 Sep 2019 14:43 by ADMIN
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.
Approved
Last Updated: 20 Sep 2019 10:16 by ADMIN
Created by: Marc
Comments: 2
Category: PdfProcessing
Type: Feature Request
3
Add support for Lab color space to allow clients to import and export documents with Lab color space.
Approved
Last Updated: 17 Sep 2019 13:46 by ADMIN

Exporting document with a missing image is caused by handled Exception on import for DecodeParms containing null or stream object. Currently, PdfProcessing supports only decode parameters containing simple types. The case when some dictionary value is null or stream object should be implemented.

Another case is when the whole dictionary/stream is null. In this case, an ArgumentNullException is thrown.
Approved
Last Updated: 09 Sep 2019 17:18 by ADMIN

When a TrueType font is defined, the mapping of character codes to glyph indices depends on the built-in cmap table mappings defined in the font and the Encoding property defined in the PDF dictionary.

However, the current implementation maps all characters with cmap tables for Microsoft Symbolic and Macintosh Roman, which causes incorrect mapping results, e.g. space characters are mapped to an Ê glyph.

The issue is also described in the following public item: TryGetCharCode for OpenTypeFont uses wrong cmap and returns wrong charcode.

Workaround: Change the font  of the TextBoxField's widget appearance:
foreach (var widget in field.Widgets)
{
    widget.TextProperties.Font = FontsRepository.Helvetica;
}

Approved
Last Updated: 07 Aug 2019 11:06 by ADMIN
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.
Approved
Last Updated: 05 Aug 2019 14:51 by ADMIN
When the content of a page is rotated, each glyph is exported on a new line.
Approved
Last Updated: 02 Aug 2019 08:21 by ADMIN
ADMIN
Created by: Polya
Comments: 4
Category: PdfProcessing
Type: Feature Request
5
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: 01 Aug 2019 15:32 by ADMIN
Sometimes customers need to create documents using the CMYK colors to meet specific requirements for printing. Expose such functionality in PdfProcessing.
Approved
Last Updated: 01 Aug 2019 07:57 by ADMIN
Importing document containing TextBox widgets with NormalContentSource defining text properties, such as FontSize and Position, are exported with incorrect appearance when the value of the field is modified.
Approved
Last Updated: 30 Jul 2019 12:32 by ADMIN
ADMIN
Created by: Deyan
Comments: 4
Category: PdfProcessing
Type: Feature Request
11
This API should provide a method for removing all fields and widgets in the document and draw the default widget appearance in place of the removed widgets.

WORKAROUND: Sample implementation for flattening form fields may be seen in the FlattenFormFields method from the attached demo project.
Approved
Last Updated: 26 Jul 2019 13:19 by ADMIN
Created by: David
Comments: 0
Category: PdfProcessing
Type: Feature Request
5
Currently adding an Image content element with ImageSource instantiated with a PNG file format leads to NotSupportedException: 'Can not export other than Jpeg and Jpeg2000 and ImageQuality different than High', when exporting the document.

Support for adding PNG images and exporting to PDF should be implemented for PdfProcessing for .NET Standard scenario.
1 2 3 4 5 6