When exporting a document with the .NET Framework implementation, only subsets of the used fonts are embedded in the document.

RadPdfProcessing currently supports interactive forms whose data is defined directly in the document. Add support for interactive forms based on the Adobe XML Forms Architecture (XFA). The entry is defined inside the interactive forms dictionary and refers to an XML stream containing the information of the form. More information is available on page 722 from Pdf Reference, version 1.7.

By default, MS Word separates two consecutive tables with a paragraph element. Otherwise, they are being merged.

Optical character recognition or optical character reader (OCR) is the electronic or mechanical conversion of images of typed, handwritten, or printed text into a machine-encoded text from a scanned document.

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 a strikethrough property or strikethrough-related properties in the TextProperties class.

To bring RadPDFProcessing to the next level you should support XMP metadata. This would extremely help to use pdf files from RadPDFProcessing in digital workflows.

Reference: http://www.adobe.com/devnet/xmp.html

You can convert the document to PDF and use the approach bellow:

Currently, silent async printing may be achieved by using RadPdfViewer WPF control. Sample demo showing how to achieve this may be seen at the following forum post:
http://www.telerik.com/forums/pdfviewer-print-makes-ui-unresponsive#js0YdzFWc0Oa8C3g6a18lg

The RadPdfViewer WPF control used does not need to be displayed, making this demo a good workaround for ASP.NET AJAX clients.

From the PDF specification: "The current stroking alpha constant, specifying the constant shape or constant opacity value to be used for stroking operations in the transparent imaging model."

Not respecting it leads to lost image transparency.

Introduce API for setting Image opacity.

The attached Workaround demonstrates how to change the opacity of the image before inserting it into the document.

Currently, PdfStreamWriter writes only PDF pages.

If we implement API for merging multiple pages or whole documents we would be able to preserve links between pages (which are currently being corrupted).

Merging whole documents would also allow preserving document properties (bookmarks, interactive forms, ...). For a more detailed list of the unsupported document properties you can refer to our documentation: https://docs.telerik.com/devtools/document-processing/libraries/radpdfprocessing/formats-and-conversion/pdf/pdfstreamwriter/features.

We may also implement API for adding initial document properties from some existing PDF file.

When trying to convert Image XObject encoded with FlateDecode and with no ColorSpace defined to a DCTDecoded image it is fallbacking to preserve the original FlatDecode filter and the image is not converted.

At this point, the justify alignment is not supported.

When encoding an image with Indexed color space an exception is thrown: NotSupportedException: 'Not supported colorspace: Indexed'

Introduce API for setting the 'Application' property of a document.

Allow authentication of documents with OwnerPassword. The user can use the OwnerPassword instead of the UserPassword to open the file.

Introduce support for UnShrinking - Method 1.

Expose the fallback mechanism so the fallback fonts can be changed 

The auto-size fields are not correctly imported/exported this setting is lost during export 

Introduce support for reading barcodes from images.