Completed
Last Updated: 26 May 2020 09:05 by ADMIN
Release LIB 2020.2.525 (05/25/2020)
Completed
Last Updated: 15 May 2020 08:58 by ADMIN
Release LIB 2020.2.518 (18.05.2020)
The image size of EMF/WMF images is wrongly exported when exporting to PDF.
Completed
Last Updated: 06 May 2020 06:49 by ADMIN
Release R2 2020
Created by: David
Comments: 2
Category: PdfProcessing
Type: Feature Request
13
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.
Completed
Last Updated: 06 May 2020 06:49 by ADMIN
Release R2 2020
Created by: Pierre
Comments: 0
Category: PdfProcessing
Type: Feature Request
0
Currently adding an Image content element with ImageSource instantiated with a GIF 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 GIF images and exporting to PDF should be implemented for PdfProcessing for .NET Standard scenario.
Completed
Last Updated: 06 May 2020 06:47 by ADMIN
Release R2 2020
Currently adding an Image content element with ImageQuality different from High leads to NotSupportedException: 'Can not export other than Jpeg and Jpeg2000 and ImageQuality different than High', when exporting the document.
Completed
Last Updated: 15 Apr 2020 11:16 by ADMIN
Release R2 2020
HtmlFormatProvider treats <script type="text/javascript"> as document elements and inserts the content (js code) as text in the document.

The issue is observed when CDATA is used as well.
Completed
Last Updated: 15 Apr 2020 11:13 by ADMIN
Release R2 2020
The link element should not have style. HtmlFormatProvider doesn't skip the style but instead tries to evaluate and apply it. As a result, the error is thrown.
Completed
Last Updated: 14 Apr 2020 14:32 by ADMIN
Release R2 2020
Some documents result in glyphs with wrong widths after import-export. Widths are mixed making some of them to overlap and others to have bigger distance.
Completed
Last Updated: 14 Apr 2020 12:51 by ADMIN
Release R2 2020
Completed
Last Updated: 14 Apr 2020 12:21 by ADMIN
Release R2 2020
When inserting row or column before cell containing reference to another worksheet the reference should not be translated.
Completed
Last Updated: 14 Apr 2020 12:10 by ADMIN
Release R2 2020
Created by: Stephen
Comments: 1
Category: SpreadProcessing
Type: Bug Report
0
If the lookup_value parameter and lookup_vector parameters refer cells containing text values, the function returns a Not available error ("#N/A").
Completed
Last Updated: 13 Apr 2020 13:37 by ADMIN
Release R2 2020

ArgumentException is thrown while importing a choice field whose value is an empty string. Instead, the empty string should be imported.

Completed
Last Updated: 13 Apr 2020 12:49 by ADMIN
Release R2 2020
Completed
Last Updated: 08 Apr 2020 10:39 by ADMIN
Release R2 2020
When images are added to the document with non-default quality (PdfExportSettings.ImageQuality different that ImageQuality.High) , they are re-encoded, which uses a lot of memory and may cause OutOfMemoryException for large images.
Workaround (works when inserting big JPEG images): In this case ImageQuality.High may be used and RadPdfProcessing will decode only the image headers to insert the image into the PDF file. As image pixels are not decoded with ImageQuality.High, there will be no OutOfMemoryException.
Completed
Last Updated: 30 Mar 2020 13:24 by ADMIN
Release R2 2020

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.
Completed
Last Updated: 30 Mar 2020 06:57 by ADMIN
Release R2 2020
Currently, the Line breaks <br> are not exported to plain text format.

Workaround:
Replace <br> tags in the HTML document with a marker
string html = File.ReadAllText("Source.html");
string newHtml = html.Replace("<br>", "[br]");
File.WriteAllText("NewSource.html", newHtml);
Then import the edited HTML and export it as plain text, then replace the markers with "\r\n"
using (Stream stream = File.OpenRead("NewSource.html"))
{
	HtmlFormatProvider htmlFormatProvider = new HtmlFormatProvider();
	flowDocument = htmlFormatProvider.Import(stream);
	
	TxtFormatProvider txtFormatProvider = new TxtFormatProvider();
	string text = txtFormatProvider.Export(flowDocument);
	string newText = text.Replace("[br]", "\r\n");
}

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: 30 Mar 2020 06:33 by ADMIN
Release R2 2020
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;
}

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: 27 Mar 2020 12:39 by ADMIN
Release LIB 2020.1.330 (03/30/2020)
When a document is imported the FontsRepository caches the created font instances for performance reasons. API should be provided for clearing the cached instances in order to reduce memory consumption.
1 2 3 4 5 6