Completed
Last Updated: 18 Mar 2019 09:45 by ADMIN
By specification, the document AcroForm contains fields with no parents. However, some documents may have child fields in the AcroForm. This leads to ArgumentException when importing the child and parent fields - 'An item with the same key has already been added.' since the child field is added twice.
Approved
Last Updated: 14 Mar 2019 11:45 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: 13 Mar 2019 14:03 by ADMIN
RadPdfProcessing cannot find startxref keyword at the end of a document if the document contains many zero bytes at its end. NotSupportedException is thrown with "Startxref keyword cannot be found" message. 
Workaround: Trim the ending zero bytes before loading the document to PdfProcessing. Example showing this approach can be found in the following KB article:
http://www.telerik.com/support/kb/winforms/details/notsupportedexception-startxref-keyword-cannot-be-found-when-loading-pdf-file-in-radpdfviewer-for-winforms
Approved
Last Updated: 12 Mar 2019 14:06 by ADMIN
ADMIN
Created by: Deyan
Comments: 2
Category: PdfProcessing
Type: Feature Request
6
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: 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
Approved
Last Updated: 06 Mar 2019 17:39 by ADMIN
ADMIN
Created by: Deyan
Comments: 0
Category: PdfProcessing
Type: Feature Request
10
Implement functionality allowing to specify that when a table is split on multiple pages, a specific row should be shown on each page.

Workaround: in the attached demo projects.
Approved
Last Updated: 06 Mar 2019 15:04 by John Paul
ADMIN
Created by: Deyan
Comments: 5
Category: PdfProcessing
Type: Feature Request
7
Currently, similar scenario may be achieved by converting Tiff images to BitmapSource and inserting them to RadFixedPage as images by using FixedContentEditor.
Approved
Last Updated: 05 Mar 2019 18:39 by ADMIN
Current implementation relies on valid cross-reference offsets in the PDF documents so that PDF objects are easily found and parsed. However, we can implement a mechanism for repairing documents with invalid cross-reference tables.

The attached project shows how to repair the simplest case of cross-reference table by using RepairDocumentWithSimpleCrossReferenceTable method.
Approved
Last Updated: 05 Mar 2019 00:39 by ADMIN
ADMIN
Created by: Polya
Comments: 2
Category: PdfProcessing
Type: Feature Request
3
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: 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. 
Approved
Last Updated: 28 Feb 2019 11:55 by ADMIN
ADMIN
Created by: Deyan
Comments: 6
Category: PdfProcessing
Type: Feature Request
17
They are exported with the /EmbeddedFiles switch. This would allow adding external files to the PDF document.
Completed
Last Updated: 27 Feb 2019 13:23 by ADMIN
ADMIN
Created by: Deyan
Comments: 1
Category: PdfProcessing
Type: Feature Request
4
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.
Completed
Last Updated: 27 Feb 2019 09:31 by ADMIN
By specification the last line of the file contains only the end-of-file marker, %%EOF. When importing document with missing EOF, InvalidOperationException: 'Stack empty', is thrown.
New
Last Updated: 22 Feb 2019 16:47 by ADMIN


This request is to ask that the development team review the code inside the Documents for refactoring to see if certain things can be reduced (like Generics).

 

When using the Telerik UI for Xamarin and referencing the UI.for.Xamarin NuGet package, the assembly reference for the Telerik.Documents.Fixed.dll is added to the project. This increases the amount of code that is compiled when the Linker is only set to SDK only, thus breaking AOT compilation with LLVM enabled.

 

A few addition insights:

 

- When the project cannot set the Linker to SDK and User Assemblies

- When individually referencing DLLs for only what the project uses is an insufficient solution

- When installing sub-packages like Telerik.UI.for.Xamarin.DataGrid is an insufficient solution.

 

 

Thank you.

Approved
Last Updated: 22 Feb 2019 16:27 by ADMIN
ADMIN
Created by: Boby
Comments: 3
Category: PdfProcessing
Type: Feature Request
9
Implement API for adding document outline (a.k.a bookmarks).
Approved
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.
Approved
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.
Approved
Last Updated: 31 Jan 2019 13:30 by ADMIN
ADMIN
Created by: Tanya
Comments: 4
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: 23 Jan 2019 15:26 by ADMIN
ADMIN
Created by: Deyan
Comments: 7
Category: PdfProcessing
Type: Feature Request
6
To bring RadPDFProcessing to the next level you should support XMP metadata. This would extremely help to use pdf files from RadPDFProcessing in digital workflows.

Reference: http://www.adobe.com/devnet/xmp.html
Approved
Last Updated: 22 Jan 2019 16:20 by ADMIN
The case is invalid according to the specification but all readers manage to open the document and allow editing its fields. The document can be also opened in RadPdfViewer but without the fields and the widgets.
1 2 3 4 5 6