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.

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.

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 )

For example when some PDF file has uncompressed contents we may import it and apply better compression to the stream objects. Ensure that all the content inside the document is compressed.

At this point, the justify alignment is not supported. Provide the ability to export text with this setting.

Add support for creating Tables and applying tables styles (predefined ones or custom).

They are exported with the /EmbeddedFiles switch. This would allow adding external files to the PDF document.

If a worksheet spans more than one page, you can print row and column headings or labels (also called print titles) on every page to ensure that the data is properly labeled.

Implement nested mail merge and master-detail scenario.

Implement support for content controls (a.k.a. Structured document tags), which will allow inserting editing controls in the document:

- Rich Text
- Plain Text
- Check Box
- Combo Box
- Drop-down list
- Date picker

Do not confuse this feature with form fields support (see https://feedback.telerik.com/Project/184/Feedback/Details/219850 ).

This feature includes: table of figure, table of tables etc.

TOC field contains PageRef fields inside it. To update it, we will need pagination (layout) support and PageRef fields implementation. Also TOC update can be influenced by TC fields presence in the document.

Implement export to PDF.

Currently, this missing functionality may be workaround by either drawing the headers and footers with FixedContentEditor or by using RadWordsProcessing PDF export.

Currently, for .NET Framework scenarios, this could be achieved using RadPdfViewer's WPF control ThumbnailFactory class. Sample code may be seen at this forum post:
http://www.telerik.com/forums/pdf-thumbnail-returns-transparent-images#jO33X-E8Cki_qLh_KsToWg.
The feature should be implemented for .NET Standard as well.

In addition to the fast document generation, the SpreadStreamProcessing can be adapted to import documents significantly faster than SpreadProcessing.

Implement repeating header row for tables when exporting with PdfFormatProvider.

A similar functionality can be achieved using the editing API of RadPdfProcessing. There is attached a project showing a sample implementation. More details are available in the forum post at http://www.telerik.com/forums/repeat-table-heading-after-page-break#kH616fyAKUiDl6WAknUILg

Support for forms. The feature is named 'Interactive forms' in the PDF specification.

Main scenarios to consider:

- Reading of the data in the forms.

- Writing data to the forms.


Available in R2 2017 Release

The API should allow you to perform a text-based search and return the parent element(s) of the result(s) or directly the found element(s).

The attached sample project below demonstrates a possible workaround for PAGE and NUMPAGES fields when exporting to PDF. The demo shows how to generate document from scratch containing PAGE and NUMPAGES fields and export it to PDF.

Add support for documents containing RTL (right-to-left) text.