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.
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.
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.
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.
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
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.
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.
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.
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."
CMYK color may be set using SCN, scn, K and k operators. Available support for import of CMYK colors in R3 2018 Official Release.
The signature field preserves information about the time of signing through the TimeOfSigning property of Signature.Properties. However, the DateTime object doesn't keep info about the time zone the document has been signed in. Some customers need to obtain this information.