Approved
Last Updated: 19 Jun 2019 11:03 by ADMIN
ADMIN
Created by: Tanya
Comments: 2
Category: WordsProcessing
Type: Feature Request
13
Form fields are the legacy way to insert an editable controls in a document (text boxes, checkboxes, dropdowns) by using the FORMTEXT, FORMCHECKBOX and FORMDROPDOWN fields.

Do not confuse with content controls (structured document tags) (see https://feedback.telerik.com/Project/184/Feedback/Details/190057 ) and with ActiveX controls.
Approved
Last Updated: 18 Jun 2019 14:44 by ADMIN
HTML heading elements (<h1>-<h6>) are imported with the default heading styles (Heading 1 - Heading 6) for RadFlowDocument, which is unexpected, as the browsers and MS Word import them with different styling. 

For example, <h1> is imported as Heading 1 with font the following properties:

Font: Cambria
Font color: Accent 1
Spacing before: 14 pt
Spacing after: 14 pt

While MS Word imports it as:

Font: Times New Roman
Font color: not set (black)
Character spacing: Kern at 18 pt
Spacing before: Auto
Spacing after: Auto
Approved
Last Updated: 18 Jun 2019 14:39 by ADMIN
"bolder" font weight is imported as regular font weight in the RadFlowDocument model. Instead, it should be imported as bold.
Approved
Last Updated: 18 Jun 2019 12:10 by ADMIN
Documents can be signed using the end certificate of a certificate chain, instead of the whole chain. This improves the performance of the signing.
Approved
Last Updated: 18 Jun 2019 08:40 by ADMIN
Created by: olivier legaignoux
Comments: 0
Category: SpreadProcessing
Type: Feature Request
1
The COUNTIFS function returns the count of cells that meet one or more criteria.
Approved
Last Updated: 17 Jun 2019 17:02 by ADMIN
According to the HMTL specification, the width and height attributes of an img tag has unsigned long values. When a width or height values with a unit suffix is imported, e.g.: 50%, FormatException: 'Input string was not in a correct format.' is thrown.
Approved
Last Updated: 10 Jun 2019 20:49 by ADMIN
ADMIN
Created by: Tanya
Comments: 61
Category: Telerik Document Processing
Type: Feature Request
53

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.
Approved
Last Updated: 05 Jun 2019 15:18 by ADMIN

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.
Approved
Last Updated: 05 Jun 2019 11:18 by ADMIN
Created by: Blane Bunderson
Comments: 0
Category: WordsProcessing
Type: Bug Report
1
Hyperlinks created via HtmlFormatProvider are not properly exported to PDF and cannot be clicked.
Approved
Last Updated: 04 Jun 2019 07:56 by ADMIN
Created by: Nelson
Comments: 2
Category: PdfProcessing
Type: Feature Request
1
Allow the customers to insert DWG files in the PDF documents.
Approved
Last Updated: 03 Jun 2019 10:52 by ADMIN
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.
Approved
Last Updated: 28 May 2019 14:42 by ADMIN
After signing a document using the PdfProcessing library and the document is loaded in Adobe Acrobat an error is shown when the signature widget is clicked:
Error during signature verification.  

Adobe Acrobat error.
Expected a dict object.
Approved
Last Updated: 28 May 2019 06:20 by ADMIN
By specification, the InteractiveForm fields can have the same name if they are descendants of a common ancestor. Such fields are different representations of the same underlying field; they should differ only in properties that specify their visual appearance. When such a document is imported an ArgumentException: 'An item with the same key has already been added.' is thrown.
Approved
Last Updated: 27 May 2019 15:48 by ADMIN
Sometimes the customers need to obtain the result of a formula without adding it as a value to a specific cell.
Approved
Last Updated: 23 May 2019 14:48 by ADMIN
Created by: Grinden
Comments: 2
Category: WordsProcessing
Type: Feature Request
2

The non-breaking hyphen element is currently not supported in the model and is stripped when importing the document.


Approved
Last Updated: 17 May 2019 14:00 by ADMIN
ADMIN
Created by: Boby
Comments: 5
Category: PdfProcessing
Type: Feature Request
11
Implement API for adding document outline (a.k.a bookmarks).
Approved
Last Updated: 07 May 2019 10:50 by ADMIN
Provide an API used to recalculate all formulas in the document similar to the Excel Interop Calculate function
Approved
Last Updated: 25 Apr 2019 14:22 by ADMIN
When importing color space defined as an external resource name, a NotSupportedColorSpaceException: 'CS0 color space is not supported.' is thrown.
Approved
Last Updated: 15 Apr 2019 14:56 by ADMIN
For example, importing URI Action with invalid mailto URL scheme - mailto:***@***.**(E-mail), throws UriFormatException: 'Invalid URI: The hostname could not be parsed.'
Approved
Last Updated: 12 Apr 2019 14:45 by ADMIN
Created by: David
Comments: 7
Category: Telerik Document Processing
Type: Feature Request
1

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.

1 2 3 4 5 6