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.

Documents can be signed using the end certificate of a certificate chain, instead of the whole chain. This improves the performance of the signing.

The COUNTIFS function returns the count of cells that meet one or more criteria.

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.

Allow the customers to insert DWG files in the PDF documents.

Sometimes the customers need to obtain the result of a formula without adding it as a value to a specific cell.

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

Implement API for adding document outline (a.k.a bookmarks).

Provide an API used to recalculate all formulas in the document similar to the Excel Interop Calculate function

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 exporting, an option of how to create the PDF bookmarks should be provided:
- Using the RadFlowDocument bookmarks
- Using document Headings

Add support for preserving and exporting the macros in a macro-enabled workbook.

Macros are pieces of code written in Visual Basic for Applications (VBA) which are used to automate repetitive tasks in excel. The macros are part of the excel file. When a file contains a macro its extension becomes xlsm.

SpreadProcessing should be able to import and export xlsm files and edit the macros in them.

Line annotation displays a single straight line on the page. When opened, it displays a pop-up window containing the text of the associated note.

A free text annotation displays text directly on the page. Unlike an ordinary text annotation, a free text annotation has no open or closed state; instead of being displayed in a pop-up window, the text is always visible.

Add support for exporting content with strikethrough font effect.

Add support for setting and exporting document metadata, like Title, Author and similar.

Add support for shapes, and especially for shapes with textual content. 
In OOXML, shapes are represented by the wps:wsp element, and shapes with textual content by <wps:txbx>, <w:txbxContent>.
Such shape can be added to a Word document using the Insert -> Text -> Text Box -> Draw Text Box, or through a shape's context menu -> Add Text.

Do not confuse these shapes with Text/Rich Text content controls (see https://feedback.telerik.com/Project/184/Feedback/Details/190057 )

This request is to ask that the development team review the code inside the Documents for refactoring to see if certain things can be reduced (like Generics).

 

When using the Telerik UI for Xamarin and referencing the UI.for.Xamarin NuGet package, the assembly reference for the Telerik.Documents.Fixed.dll is added to the project. This increases the amount of code that is compiled when the Linker is only set to SDK only, thus breaking AOT compilation with LLVM enabled.

 

A few addition insights:

 

- When the project cannot set the Linker to SDK and User Assemblies

- When individually referencing DLLs for only what the project uses is an insufficient solution

- When installing sub-packages like Telerik.UI.for.Xamarin.DataGrid is an insufficient solution.

 

 

Thank you.

At this point the PdfFormatProvider does not support floating images and these elements are skipped when exporting to PDF.

The feature is trivial for floating images with "Behind Text"/"In Front of Text" settings, but otherwise floating images are affecting the text layout in complex ways.

The AlternateContent element is used to store content which is not defined by the specification.