Completed
Last Updated: 15 Jan 2020 12:34 by ADMIN
Release R1 2020
ADMIN
Created by: Tanya
Comments: 77
Category: Telerik Document Processing
Type: Feature Request
68

Currently, Telerik Document Processing is available only for .NET Framework and (partially) for Silverlight. Create version targeting .NET Core.

Update: There is a version of Telerik Document Processing compatible with .NET Core 3.0 in the UI for WPF suite. You can use this version in .NET Core projects running on Windows. The assemblies can be downloaded from telerik.com, the Downloads section of UI for WPF -> Betas tab. Please, note that you should have a valid license for UI for WPF in order to be able to see this version. In case you don't, you can use the Trial license by downloading a trial version of the suite. More information about this version of UI for WPF and how it can be used is available in the related blog post.
Completed
Last Updated: 28 Mar 2018 10:44 by ADMIN
ADMIN
Created by: Deyan
Comments: 15
Category: PdfProcessing
Type: Feature Request
35
Support for forms. The feature is named 'Interactive forms' in the PDF specification.

Main scenarios to consider:

- Reading of the data in the forms.

- Writing data to the forms.


Available in R2 2017 Release
Completed
Last Updated: 27 Feb 2019 13:20 by ADMIN
ADMIN
Created by: Deyan
Comments: 9
Category: SpreadProcessing
Type: Feature Request
19
Add APIs for creating and manipulating Chart objects.
Completed
Last Updated: 17 Aug 2018 06:27 by Ivo
ADMIN
Created by: Tanya
Comments: 7
Category: SpreadProcessing
Type: Feature Request
18
This will enable printing with the following printing options: 

- Fit Sheet on One Page

- Fit All Columns on One Page

- Fit All Rows on One Page

- Custom automatic scaling


A possible implementation of a similar behavior is to use the PageSize property of WorksheetPageSetup and subtract the corresponding margin values (from the Margins property) from the width to calculate how many columns are fitting in some particular page size with 100% scale factor. 

Available in R2 2018 Official Release version.
Completed
Last Updated: 30 Aug 2018 06:42 by Wen
Created by: Mi
Comments: 6
Category: PdfProcessing
Type: Feature Request
16
For details: https://www.adobe.com/devnet-docs/acrobatetk/tools/DigSig/Acrobat_DigitalSignatures_in_PDF.pdf

This feature is a must have for every business or enterprise!



Available in R2 2017 Release
Completed
Last Updated: 08 Aug 2019 07:24 by ADMIN
Release R3 2019
ADMIN
Created by: Boby
Comments: 5
Category: PdfProcessing
Type: Feature Request
13
Implement API for adding document outline (a.k.a bookmarks).
Completed
Last Updated: 03 May 2017 06:37 by ADMIN
ADMIN
Created by: Deyan
Comments: 2
Category: PdfProcessing
Type: Feature Request
11
Paint content stream operator ("Do" in PDF specification) currently draws only Image XObjects. We should implement support for Form XObjects. 


Available in R2 2017 Release
Completed
Last Updated: 27 Mar 2020 10:46 by ADMIN
Release R2 2020
ADMIN
Created by: Tanya
Comments: 4
Category: PdfProcessing
Type: Bug Report
8
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 attached project or the attached project to the following feedback item to rename the duplicate fields: Provide a way to rename FormFields.
Completed
Last Updated: 24 Apr 2018 11:14 by ADMIN
Currently this operator is interpreted correctly only for Pattern colorspace. It also partially supports the rest of the colorspaces from R1 2018.

Available in R2 2018 Official Release Version.
Completed
Last Updated: 17 Sep 2019 07:30 by ADMIN
Release R3 2019
ADMIN
Created by: Deyan
Comments: 0
Category: PdfProcessing
Type: Feature Request
7
Add support for ToUnicode CMap stream.

A side effect of not supporting it is the following: exporting PDF document which, for example, contains German umlauts, to plain text, leads to wrong characters in the resulting text.

As possible workaround, the PdfFormatProvider instance of RadPdfViewer can be used to import the document. For example:

FormatProviderSettings settings = new FormatProviderSettings(ReadingMode.OnDemand);
PdfFormatProvider pdfViewerFormatProvider = new PdfFormatProvider(stream, settings);
 
RadFixedDocument document = pdfViewerFormatProvider.Import();
 
TextFormatProvider textFormatProvider = new TextFormatProvider();
String text = textFormatProvider.Export(document);
Completed
Last Updated: 17 Sep 2019 13:01 by ADMIN
Release R3 2019
This is reproducible with specific PDF files which use custom Encoding for the fonts of the field widgets. 

WORKAROUND: Change the font of VariableContentWidgets before editing the field value. You should additionally call RecalculateContent() method of these widgets if the value of their corresponding fields is not edited. The following method may be used for changing the font of all existing widgets in the document:

private static void FixEncodingIssues(RadFixedDocument document)
{
    foreach(Annotation annotation in document.Annotations)
    {
        VariableContentWidget widget = annotation as VariableContentWidget;

        if(widget != null)
        {
            widget.TextProperties.Font = FontsRepository.Helvetica;
        }
    }
}
Completed
Last Updated: 03 Oct 2018 11:38 by ADMIN
CMYK color may be set using SCN, scn, K and k operators.

Available support for import of CMYK colors in R3 2018 Official Release.
Completed
Last Updated: 25 Jan 2017 09:00 by ADMIN
This new API will not read/delete the existing PDF pages content and this would allow performance and memory efficient realization of the following scenarios: 

 - Merge PDF document pages from different PDF files.

 - Split PDF document pages to separate PDF files.

 - Append/Prepend PDF content to existing PDF pages.

Moreover, as this approach will not require reading/deleting existing PDF page content, it will not depend on complex PDF features and will depend only on the PDF file structure. This will allow processing of PDF documents which use less common PDF features which are currently not supported by the existing PdfProcessing API.


Available in R1 2017 Release
Completed
Last Updated: 17 May 2018 08:00 by ADMIN
ADMIN
Created by: Deyan
Comments: 8
Category: PdfProcessing
Type: Feature Request
5
Implemented import and export of IccBased, Indexed, Cmyk color spaces. Available in Q3 2015.

Available in R2 2018 Official Release version.
Completed
Last Updated: 27 Mar 2020 15:17 by ADMIN
Release R2 2020
The current implementation uses System.Windows.Media.Imaging.BitmapImage class in order to take the image pixels for the PDF export. However, BitmapImage class throws NotSupportedException when being initialized with a WMF or EMF image.

WORKAROUND: WMF and EMF images may be converted to PNG images before the PDF export. The following code snippet shows how to convert all inline WMF image to PNG images by using System.Drawing.Image class:

private static void ConvertInlineWmfImagesToPng(RadFlowDocument document)
{
    foreach (ImageInline image in document.EnumerateChildrenOfType<ImageInline>())
    {
        if (image.Image.ImageSource.Extension.Equals("wmf", StringComparison.InvariantCultureIgnoreCase))
        {
            using (MemoryStream wmfImageStream = new MemoryStream(image.Image.ImageSource.Data))
            {
                using (MemoryStream pngImageStream = new MemoryStream())
                {
                    var imageDrawing = System.Drawing.Image.FromStream(wmfImageStream);
                    imageDrawing.Save(pngImageStream, ImageFormat.Png);
                    byte[] pngBytes = pngImageStream.ToArray();
 
                    image.Image.ImageSource = new ImageSource(pngBytes, "png");
                }
            }
        }
    }
}
Completed
Last Updated: 30 Mar 2020 06:39 by ADMIN
Release R2 2020
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.
Completed
Last Updated: 15 Feb 2018 16:53 by ADMIN
The issue is observed with tables that have a specific width (in inches or percents) but whose columns do not have width specified. MS Word renders such tables expanded to their full width. For tables with 100% width, they have to expand to the entire width of the page. The same behavior is expected in the PDF export.

As a common side effect, when specific text alignment (e.g. center or right) is applied to a paragraph within a table cell, and the table is with specified width, but the column is auto-sized (without set width), then the text alignment seems as not respected. Actually the problem is that the column table is shrunk to the text width.

Workaround: this may be used before exporting the RadFlowDocument instance to PDF:

foreach (Table table in document.EnumerateChildrenOfType<Table>())
{
    table.LayoutType = TableLayoutType.FixedWidth;
}


Workaround 2:

Set specific width to the auto-sized columns (to any of the cells in the columns):

cell.PreferredWidth = new Telerik.Windows.Documents.Flow.Model.Styles.TableWidthUnit(500);

Available in R1 2018 SP2 release version.
Completed
Last Updated: 13 Mar 2017 09:04 by ADMIN
Formulas like =0.0001/10 or formulas that produce small values results in 0 instead of exponential numbers.


Available in LIB version: 2017.1.313
Completed
Last Updated: 12 Aug 2019 11:54 by ADMIN
Release LIB 2019.2.812 (08/12/2019)
Although Lab color space is currently unsupported, the provider should not throw exceptions that break the whole file import.
Completed
Last Updated: 16 Jan 2017 14:29 by ADMIN
The "g" and "G" operators are used for setting color with a single component.


Available in R1 2017 Release
1 2 3 4 5 6