The color transformations of DrawingML colors are not imported, leading to the chart series having different colors compared to the original document.

NullReference exception is thrown when importing document with docx AltChunk element.

Importing an XLS file containing many merged cells is slow.

Importing an XLS document containing header/footer definition without a specific placement causes an endless loop. 

OpenDocument Format is an open format for many software supported like OpenOffice, I hope the Telerik Document Processing libraries could support for import/export format.

We would like to have image formats like JPG, PNG and TIFF supported in addition to the PDF and Office document support in DPL.

Based on how Excel works, VLookup doesn't need to be sorted, if the 4th parameter is FALSE.  The 4th Parameter determines whether an approximate search is used or an exact match is used.  by default true is used and an approximate search requires a sorted range.  However, if set to FALSE,  then the range doesn't need to be sorted.  the value is checked against the entire column of cells and can be unsorted. 

We process spreadsheets that use VLOOKUP with 4th parameter set to FALSE and unsorted data in range.  These work in Excel, but not in Telerik Spreadsheet processing.

thanks, 

The auto row height is not working when the row is merged. This is only valid if the merged cell range contains a single row.

Even without flattening the form the Barcode font gets lost.

Noticed that manually setting the font using the font name with spaces seems to work.

Other custom fonts on our form appear to work, however the Free 3 of 9 does not.

Attached a project to demonstrate some issues we're seeing that need resolving in order to use the component.

1. When using a font like Tahoma on a form field, the value no longer displays or contains garbled text.

2. Input file is 24KB, output is 2MB!

3. Rotated field lose their rotation after being flattened.

4. Simulate merging with other files, 100 times the file is now 150MB! It's as though it's not re-using the fonts, but keeps adding the same ones.

5. when merging, but not flattening, the form fields are all lost on pages after page 1

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.

When xlsx/docx document is imported, and its main story is with non-default name ('workbook. xml'/'document.xml'), e.g. workbook2.xml/document2.xml, NullReferenceException is thrown and the document is not imported.

Note: Such documents are usually produced after conversion from a template dotx/xlsm.

The align property is not respected when importing HTML

Allow to export the documents to image.

Being able to generate a thumbnail for example.

Exception when using multiple instances of RtfFormatProvider

The NuGet packages don't differ .Net Core projects from .Net Core with Desktop Compatibility Pack. This leads to incorrect resolving of the dependencies and the .Net Core projects targeting .Net Core 3.0 cannot be built.

Workaround: An option applicable for all the libraries is to extract the assemblies from the .nupkg files. For PdfProcessing and ZipLibrary you can use the assemblies directly from the pdfviewer installation folder.

Testing Tracked Forum

I'm working on a project that has a service component that will be generating Excel xlsx documents for distribution.  While there is a UI for administrative tasks, the service itself will run without an interface.  I'm using the Documents.Core, and several other associated libraries to accomplish this.  Two issues I've encountered, one is setting up the project with the appropriate libraries and keeping the version in sync with the Admin application, second is protecting those libraries once they are packaged for release.  I had a support ticket open to determine how to accomplish the latter, but the first is still a manual issue.  

So the feature request is to include the ability in the project templates and/or Convert to Telerik WPF Application to support a headless document solution.  It would ideally include (only) the required libraries and maintain their linkage to the appropriate library version with the rest of the solution which occurs with a full Telerik WPF UI app.  It would also include the necessary boilerplate code and references to properly protect the libraries.  I was referred to another feedback request on improving the overall library protection build process, but while related, what I'm asking for here is not exactly the same.

When using the PdfStreamWriter to write a PdfPageSource whose content is an array of content streams, the resultant content stream contains concatenated graphic state operators. This results in error when loading the document in Acrobat Reader and corrupted page content.