Last Updated: 02 Dec 2019 11:57 by ADMIN
RadPDfProcessing: Exception when parsing a Tiling pattern with non-rgb color.
Last Updated: 28 Nov 2019 08:07 by ADMIN
When the bookmarks are declared as objects instead of a string they are not visible.
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.
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'.
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.
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.
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.
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.
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;

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.
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.
Last Updated: 19 Jul 2019 06:49 by ADMIN
When importing color space defined as an external resource name, a NotSupportedColorSpaceException: 'CS0 color space is not supported.' is thrown.
Last Updated: 03 Jun 2019 10:52 by ADMIN
Some documents result in glyphs with wrong widths after import-export. Widths are mixed making some of them to overlap and others to have bigger distance.
Last Updated: 28 May 2019 14:42 by ADMIN
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.
Last Updated: 15 Apr 2019 14:56 by ADMIN
For example, importing URI Action with invalid mailto URL scheme - mailto:***@***.**(E-mail), throws UriFormatException: 'Invalid URI: The hostname could not be parsed.'
Last Updated: 07 Mar 2019 08:39 by ADMIN
When creating a GradientStop, an alpha channel of the color could be applied. However, this setting is not respected it the result document and the gradient is with full opacity.

Steps to reproduce:
1. Create a gradient with an alpha channel:

RadFixedDocument document = new RadFixedDocument();
RadFixedPage page = document.Pages.AddPage();
FixedContentEditor containerEditor = new FixedContentEditor(page);

LinearGradient linearGradient = new LinearGradient(new Point(0, 0), new Point(30, 30));
linearGradient.GradientStops.Add(new GradientStop(new RgbColor(10, 0, 207, 0), 0));
linearGradient.GradientStops.Add(new GradientStop(new RgbColor(10, 0, 102, 204), 1));

containerEditor.GraphicProperties.FillColor = linearGradient;
containerEditor.DrawRectangle(new Rect(10, 10, 48, 29));

2. Export the document to PDF

Observed: The alpha channel is not respected and the gradient is with full opacity
Last Updated: 28 Feb 2019 13:55 by ADMIN
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. 
Last Updated: 07 Feb 2019 13:23 by ADMIN
By specification the explicit destinations define a required page property. However, some documents contain definition for destinations with null page value, which causes an ArgumentNullException on import.
Last Updated: 31 Jan 2019 16:26 by ADMIN
When a document is exported with a cross-reference stream, the stream is missing the required according to the specification Length property. Although most of the viewers open the document without any issues, some cannot. Such documents cannot be opened in MS Edge.
Last Updated: 31 Jan 2019 13:30 by ADMIN
Created by: Tanya
Comments: 4
Category: PdfProcessing
Type: Bug Report
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.

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))
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.
1 2 3