I'm trying to use RadWordsProcessing

to replace text in .docx documents.

when i try to open a document i have an error:

BadImageFormatException: Could not load file or assembly 'PresentationCore, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'. Reference assemblies should not be loaded for execution.  They can only be loaded in the Reflection-only loader context. (0x80131058)

I need to print a series of docx and pdf documents automatically to a printer from a web page directly on the server-side.

If there is a location that has only a page, but no left, top, and zoom an ArgumentOutOfRangeException.

Charts containing marker definition, even its symbol and fill properties are set to none are drawn.

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.