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.

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.

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

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.

Currently, similar scenario may be achieved by converting Tiff images to BitmapSource and inserting them to RadFixedPage as images by using FixedContentEditor.
Note: A sample approach how to achieve such functionality is demonstrated in the Converting Multi-page TIFF Images to PDF KB article.

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.

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.

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.

Exported protected document containing SignatureField can not be opened even if the correct password is used. The same behavior is reproduced with empty document (without pages).

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).

Support conversion of XPS documents to PDF using RadPdfProcessing.

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.

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.

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.

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.

 This is content stream operator that is used to close, fill and then stroke a PDF path geometry.

Available in R3 2018 SP1 release.

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.

When the string contained in a PdfHexString instance is empty, invoking ToString() leads to IndexOutOfRangeException.

Available in R3 2018 SP1 release version.

A font descriptor can be used by several fonts. However, when first a TrueType font is imported, later trying to import a Cid font leads to InvalidCastException with the message: "Unable to cast object of type 'Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Elements.Fonts.FontDescriptor' to type 'Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Elements.Fonts.CidFontDescriptor'."

Fix available in R3 2018 SP1 release.

The hierarchical document structure is a means to describe the PDF document structure, which is currently not supported. See 10.6.1 Structure Hierarchy on 856 page of the PDF specification for details.
This document structure is an alternative to the standard PDF structure and most non-Adobe software does not support it.

The document might have been created with Adobe software like Adobe LiveCycle Designer. Very often the document contains some fallback text in the standard PDF structure like:
"Please wait... If this message is not eventually replaced by the proper contents of the document, your PDF viewer may not be able to display this type of document."
"The document you are trying to load requires Adobe Reader 8 or higher. You may not have the Adobe Reader installed or your viewing environment may not be properly configured to use Adobe Reader. For information on how to install Adobe Reader and configure your viewing environment please see  http://www.adobe.com/go/pdf_forms_configure."
"For the best experience, open this PDF portfolio in Acrobat X, Reader X, or later."