Approved
Last Updated: 12 Oct 2018 22:26 by ADMIN
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.
Approved
Last Updated: 12 Nov 2018 15:45 by ADMIN
When there is an abstractNum defined with the same abstractNumId in word\glossary\numbering.xml and in the word\numbering.xml, a "System.ArgumentException: An item with the same key has already been added." exception is thrown.

In other cases, the import overwrites the styles from the main document part with the ones defined in the glossary. 

Approved
Last Updated: 12 Nov 2018 18:41 by ADMIN
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.
Approved
Last Updated: 25 Jan 2019 14:50 by ADMIN
Encrypting document with Interactive forms containing checkboxes exports the checkbox widget with invalid normal caption appearance and name value. After the document is visualized in Adobe Reader DC the exported checkboxes are displayed with different check mark symbol or none.
Declined
Last Updated: 15 May 2019 14:18 by ADMIN
Created by: Hector
Comments: 1
Category: Telerik Document Processing
Type: Bug Report
0
Testing Tracked Forum
Approved
Last Updated: 25 Sep 2019 15:57 by ADMIN

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.

Completed
Last Updated: 17 Dec 2018 13:42 by ADMIN
Created by: Stefan
Comments: 1
Category: Telerik Document Processing
Type: Bug Report
0
When two documents are merged and the source document has watermarks, these are not cloned in the target document.

Approved
Last Updated: 05 Apr 2018 11:52 by ADMIN
Currently EULA requires Telerik assemblies to be protected against unauthorized redistribution, by following specific guidelines for the different types of technology:
- for WPF: https://docs.telerik.com/devtools/wpf/installation-and-deployment/deploying-telerik-ui/protecting-telerik-assembly
- for ASP.NET AJAX: https://docs.telerik.com/devtools/aspnet-ajax/deployment/protecting-the-telerik-asp.net-ajax-assembly
- for WinForms: https://docs.telerik.com/devtools/winforms/installation-deployment-and-distribution/redistributing-telerik-ui-for-winforms

When the guidelines for WinForms or AJAX are followed (namely the call to ValidatePassPhrase() is uncommented in AssemblyProtection.IsValid() method, the following license message is added to the generated documents:
"This document was generated by a copy of Telerik Document Processing licensed for use only by '<MyApp>'."

Workaround: Set the application name as resource in the Application.Current, using the following code:

new System.Windows.Application();
System.Windows.Application.Current.Resources.Add("Telerik.Windows.Controls.Key", "MyApp");
where 'MyApp' should be replaced with the actual application name. References to PresentationFramework and WindowsBase .NET Framework assemblies should be added in order for this approach to work.