Completed
Last Updated: 23 Apr 2018 07:06 by ADMIN
Run's default constructor creates it with Text = null. When document with such run is exported to PDF, NullReferenceException is thrown.

Workaround: Create the Run and immediately set its Text property to string.Emtpy.

Available in LIB Version 2018.1.423.
Completed
Last Updated: 17 May 2018 08:04 by ADMIN
KeyNotFoundException is thrown on import. The number formats with id 5, 6, 7 and 8 are missing in the built-in number formats.

Available in R2 2018 Official Release version.
Completed
Last Updated: 25 Jan 2018 13:59 by ADMIN
This happens only in cases when the Radio flag is not set and there are multiple widgets with different "ON" state names.

Available in R1 2018 SP2 version.
Completed
Last Updated: 30 Apr 2018 13:36 by ADMIN
Some field values are initially not visible when opening file exported with RadPdfProcessing in Adobe Reader. The field value becomes visible once you click (focus) the field in Adobe Reader. The setting which causes this UI rendering issue may be found in "Edit" -> "Preferences" -> "Forms" -> "Highlight Color" -> "Show border hover color for fields". On the attached screenshots you may compare the rendering result when this setting is On and when it is Off.

Fix available in LIB Version 2017.2.710.
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: 07 Aug 2019 10:57 by ADMIN
Release LIB 2019.2.812 (08/12/2019)
When the document contains an image that is defined as an external resource but is not available in the specified location and cannot be found, a KeyNotFoundException is thrown. Handle this exception and replace the missing image with a default one for such cases. Consider exposing an option to notify the user about this error.
Completed
Last Updated: 06 Aug 2019 13:26 by ADMIN
Release LIB 2019.2.812 (08/12/2019)
When the imported html contains an attribute of the type width="", Wordsprocessing throws ArgumentException and does not import the document. 
Completed
Last Updated: 14 Dec 2017 15:49 by ADMIN
Although this is not a valid table scenario we should not throw an exception when measuring and exporting such table.

Fix available in LIB Version 2017.3.1218.
Completed
Last Updated: 11 Jun 2019 12:46 by ADMIN
Release R2 2019 SP1
The data validation rule should have values for formula1 and formula2 elements, which define the start and end values for a range to validate between. When such values are missing, a NullReferenceException is thrown on import and the document cannot be imported.

Details:

System.NullReferenceException: Object reference not set to an instance of an object.
   at Telerik.Windows.Documents.Spreadsheet.FormatProviders.OpenXml.Xlsx.Model.Elements.Worksheets.DataValidationElement.CopyPropertiesToSingleArgumentContext(SingleArgumentDataValidationRuleContext context)
   at Telerik.Windows.Documents.Spreadsheet.FormatProviders.OpenXml.Xlsx.Model.Elements.Worksheets.DataValidationElement.CopyPropertiesToDataValidationRuleContext(DataValidationRuleContextBase context)
   at Telerik.Windows.Documents.Spreadsheet.FormatProviders.OpenXml.Xlsx.Model.Elements.Worksheets.DataValidationElement.ListRuleFactory(IXlsxWorksheetImportContext context)
   at Telerik.Windows.Documents.Spreadsheet.FormatProviders.OpenXml.Xlsx.Model.Elements.Worksheets.DataValidationElement.OnAfterRead(IXlsxWorksheetImportContext context)
...
   at Telerik.Windows.Documents.Spreadsheet.FormatProviders.WorkbookFormatProviderBase.Import(Stream input)
Completed
Last Updated: 13 Dec 2018 15:23 by ADMIN
ArgumentException with clarification similar to  "'\u001f', hexadecimal value 0x1F, is an invalid character." is thrown when trying to export document containing characters which are not supported in XML document - such as some control characters like 0x00, 0x1F, 0x1B, etc. Such characters are described in the XML specification here: https://www.w3.org/TR/xml/#charsets.
Although the escaped strings are not supported (see related 181318), the library could prevent the exception and export the document successfully by skipping such characters.
Workaround: remove such characters before the export. Check the following StackOverflow answer for some ideas on code for replacing the characters: http://stackoverflow.com/a/14323524/259206


Completed
Last Updated: 27 Feb 2019 09:31 by ADMIN
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.
Completed
Last Updated: 19 Oct 2018 11:08 by ADMIN
ADMIN
Created by: Polya
Comments: 0
Category: SpreadProcessing
Type: Bug Report
1
Incorrect calculation of Round function returns wrong results in some cases. For example, test Microsoft Excel and Spreadsheet results of: ROUND(1.365, 2) to see the discrepancy.

Available in R3 2018 SP1 release.
Completed
Last Updated: 14 Jun 2018 13:23 by ADMIN
Importing document containing content with DeviceN color space causes System.InvalidCastException when the color components contain integer values

Fix available in R2 2018 SP1 release version.
Completed
Last Updated: 01 Oct 2018 14:00 by ADMIN
When the values that were copied have formatting both on the cell and on the column, the pasted values get the formatting of the column, instead of that of the cell. The same applies to rows.
Completed
Last Updated: 14 Jun 2018 12:07 by ADMIN
The  FunctionType property is required according to PDF specification and we should always export it.

Fix available in R2 2018 SP1 release version.
Completed
Last Updated: 23 May 2019 13:14 by ADMIN
When the worksheet contains many formulas which use large ranges (e.g. covering 50000 cells) as arguments and these formulas have to be calculated, this causes OutOfMemoryException. 
Completed
Last Updated: 30 Mar 2017 14:21 by ADMIN
When a cell value contains commas or new lines, they are not escaped on export to CSV and single value is exported as multiple values.

Workaround: Escape the value manually. For example, use the following extension method to set string cell values:
internal static class CellExporterExtensions
{
    public static void SetValue(this ICellExporter cell, string value, SpreadDocumentFormat format)
    {
        if (format == SpreadDocumentFormat.Csv)
        {
            if (value.Contains(","))
            {
                // escape all quotes with double quotes
                value = value.Replace("\"", "\"\"");

            }

            // enclose all values within quotes
            value = string.Format("\"{0}\"", value);
        }

        cell.SetValue(value);
    }
}

Available in LIB version: 2017.1.403
Completed
Last Updated: 16 Mar 2017 13:32 by ADMIN
This leads to keeping a lot of memory when exporting pages from multiple PdfFileSource instances which are created from MemoryStream.

Available in LIB version: 2017.1.320
Completed
Last Updated: 15 Feb 2018 16:07 by ADMIN
ADMIN
Created by: Deyan
Comments: 0
Category: PdfProcessing
Type: Bug Report
1
These images are defined directly in the PDF page content stream with BI and EI operators. Currently InvalidCastException is thrown when document with such images is imported.

Available in R1 2018 SP2 release version.
Completed
Last Updated: 08 Aug 2017 14:45 by ADMIN
System.Uri constructor throws UriFormatException when the text is some http address.

Available in LIB Version 2017.2.814.