Approved
Last Updated: 02 Aug 2019 08:21 by ADMIN
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.
Approved
Last Updated: 01 Aug 2019 15:32 by ADMIN
Sometimes customers need to create documents using the CMYK colors to meet specific requirements for printing. Expose such functionality in PdfProcessing.
Approved
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.
Completed
Last Updated: 31 Jul 2019 08:24 by ADMIN
Release LIB 2019.2.805 (08/05/2019)
Importing an image from HTML with URI as a source, which has applied only width or height and exporting it to PDF (which forces getting the image data so it can be drawn) leads to an incorrect value of 1 (a default value) for the dimension that is not specified.
Completed
Last Updated: 31 Jul 2019 07:13 by ADMIN
Release LIB 2019.2.805 (08/05/2019)
When the document contains an image with extension, which is not among the supported ones, a KeyNotFoundException is thrown during Import.
Approved
Last Updated: 30 Jul 2019 12:32 by ADMIN
ADMIN
Created by: Deyan
Comments: 4
Category: PdfProcessing
Type: Feature Request
8
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: 26 Jul 2019 13:19 by ADMIN
Created by: David
Comments: 0
Category: PdfProcessing
Type: Feature Request
4
Currently adding an Image content element with ImageSource instantiated with a PNG file format leads to NotSupportedException: 'Can not export other than Jpeg and Jpeg2000 and ImageQuality different than High', when exporting the document.

Support for adding PNG images and exporting to PDF should be implemented for PdfProcessing for .NET Standard scenario.
Approved
Last Updated: 19 Jul 2019 08:36 by ADMIN
Created by: Bertha
Comments: 0
Category: PdfProcessing
Type: Feature Request
1
Support for exporting WMF (Windows Metafile) and EMF (Enhanced Metafile) images should be implemented.

Workaround: Convert the WMF images to PNG before exporting:
ImageSource imageSource = new ImageSource(new MemoryStream(this.ConvertWmfImageToPng(stream)));
document.Pages.AddPage().Content.AddImage(imageSource);
...
private byte[] ConvertWmfImageToPng(Stream wmfImageStream)
{
    byte[] pngBytes;
 
    using (MemoryStream pngImageStream = new MemoryStream())
    {
        System.Drawing.Image imageDrawing = System.Drawing.Image.FromStream(wmfImageStream);
        imageDrawing.Save(pngImageStream, System.Drawing.Imaging.ImageFormat.Png);
        pngBytes = pngImageStream.ToArray();
    }
 
    return pngBytes;
}

Approved
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.
Approved
Last Updated: 17 Jul 2019 13:18 by ADMIN
Created by: Andres
Comments: 0
Category: WordsProcessing
Type: Feature Request
1
The .bin extension represents a binary file format which can contain images as well. When a document containing such an image is imported and exported using WordsProcessing, the image is lost and the default 'no-image' placeholder is used in its place.
Completed
Last Updated: 08 Jul 2019 10:43 by ADMIN
Release LIB 2019.2.708 (07/08/2019)
An ArgumentException is thrown when importing HTML containing standard and non-standard pseudo classes or pseudo elements. The concreete scenario is the following: 
.myclass::-webkit-scrollbar or .myclass::-ms-expand

The message of the exception is similar to this: "Unexpected character found at position [X]: ".. scrollbar::>>-<<webkit-scrollbar"". 
In Development
Last Updated: 04 Jul 2019 14:19 by ADMIN
If HTML document is imported, and it contains image with invalid URL, then the image is imported with this URL in the document model. On subsequent export to Docx, the library tries to download the image data, which throws WebException. Instead, the image should be replaced with generic 'error' image.

Workaround: Manually test the image URL for correctness on HTML import, and replace the data:

        static void Main(string[] args)
        {
            HtmlFormatProvider htmlFormatProvider = new HtmlFormatProvider();
            htmlFormatProvider.ImportSettings.LoadFromUri += (sender, e) =>
            {
                if (!IsValid(e.Uri))
                {
                    e.SetData(File.ReadAllBytes("no-image.png"));
                }
            };
        }

        private static bool IsValid(string uri)
        {
            try
            {
                using (WebClient client = new WebClient())
                {
                    client.DownloadData(uri);
                }
            }
            catch (WebException)
            {
                return false;
            }

            return true;
        }

The same issue appears when exporting to PDF.
Completed
Last Updated: 01 Jul 2019 07:14 by ADMIN
Release LIB 2019.2.701 (07/01/2019)
When DefaultTabStopWidth of the document is zero, the export to PDF leads to infinite loop which causes the application to freeze.

Workaround
Set the DefaultTabStopWidth with non-zero value:
document.DefaultTabStopWidth = 0.1;
Completed
Last Updated: 01 Jul 2019 07:04 by ADMIN
Release LIB 2019.2.701 (07/01/2019)
By the PDF format specification, CIDToGIDMap is optional. The default value is Identity. However when exporting CID Font with missing CIDToGIDMap property the analyzing tool causes the following warning message:

"PDF/A requires that a Type 2 CIDFont has a stream mapping from CIDs to glyph indices or the name Identity as its value."
Approved
Last Updated: 28 Jun 2019 11:06 by ADMIN
Currently, the chart lines support only solid fill for their outlines.
Approved
Last Updated: 28 Jun 2019 10:07 by ADMIN
The API should be able to provide a way to move the X-axis away from the 0 value on the Y-axis or to the bottom of the chart when there are negative Y-axis values.

In Excel this can be achieved by right click on the axis, then from the context menu select "Format Axis".  Go to the "Labels" group and then in the "Label position" field select the desired value.
Approved
Last Updated: 27 Jun 2019 11:59 by ADMIN
ADMIN
Created by: Georgi
Comments: 2
Category: WordsProcessing
Type: Feature Request
4
Implement support for pictures with references represented with the r:link attribute in the schema.
Approved
Last Updated: 25 Jun 2019 16:05 by ADMIN
When merging files the documents might have the same fonts embedded. Then the PdfProcessing should use only one of the fonts and skip embedding the second font in the resulting document.
Completed
Last Updated: 21 Jun 2019 12:43 by ADMIN
Release LIB 2019.2.624 (06/24/2019)

When there is long text that is out of the used cell range area, this text should be included in page splitting calculations.

Also, when a cell has text that overflows its width, the text is again clipped by the cell boundaries and is not visible in the exported PDF. In a similar case Excel exports the surrounding cells to ensure that the content is visible.

Workaround: Extend the used cell range to include all the cells which the text content spans.

Approved
Last Updated: 19 Jun 2019 11:03 by ADMIN
ADMIN
Created by: Tanya
Comments: 2
Category: WordsProcessing
Type: Feature Request
14
Form fields are the legacy way to insert an editable controls in a document (text boxes, checkboxes, dropdowns) by using the FORMTEXT, FORMCHECKBOX and FORMDROPDOWN fields.

Do not confuse with content controls (structured document tags) (see https://feedback.telerik.com/Project/184/Feedback/Details/190057 ) and with ActiveX controls.