Currently RadPdfProcessing allows setting standard fonts using FontsRepository static properties.

However, in RadWordsProcessing font can be set only by specifying FontFamily, FontWeight and FontStyle. As there is no way to set standard fonts this way, API users cannot benefit from using these fonts which may help them achieve smaller PDF size as standard fonts may not be embedded. The same applies to RadSpreadhProcessing as well.

Paint content stream operator ("Do" in PDF specification) currently draws only Image XObjects. We should implement support for Form XObjects. 


Available in R2 2017 Release

Add a setting that allows enabling printing of protected documents.

Square annotation displays a rectangle on the page. When opened, it displays a pop-up window containing the text of the associated note.

WinAnsiEncoding it is imported as StandardEncoding since WinAnsiEncoding is still not implemented in RadPdfProcessing. 

CMYK color may be set using SCN, scn, K and k operators.

Available support for import of CMYK colors in R3 2018 Official Release.

This would allow to disallow some rows from splitting.

Implement functionality allowing to specify that when a table is split on multiple pages, a specific row should be shown on each page.

Workaround: in the attached demo projects.

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.

When a source RadFixedDocument is merged to a target RadFixedDocument, the content of the source document is cleared.

When trying to create documents simultaneously from different threads (in concurrent scenario), different exceptions are thrown: 

- NullReferenceException in Telerik.Windows.Documents.Core.Fonts.OpenType.OpenTypeFontSource.ReadTableData[T](UInt32 tag, ReadTableFormatDelegate`1 readTableDelegate) method, 

- OverflowException in Telerik.Windows.Documents.Core.Fonts.OpenType.Tables.CMapFormat4Table.Read(OpenTypeFontReader reader) method.


Available in LIB version: 2017.2.814

According to PDF specification, all fonts should be embedded except from 14 Standard PDF fonts. This guarantees that the PDF file is self-contained and will be rendered successfully on different devices and operation systems.

However, some clients prefer not to embed fonts in order to reduce file size. That is why we may provide such API.

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

The standard fonts listed at http://docs.telerik.com/devtools/wpf/controls/radpdfprocessing/concepts/fonts#standard-fonts cannot be embedded in a document. Using one of them prevents the document from complying with PDF/A standard.

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

Some fonts don't include bold and italic font styles. These fonts can be exported with the default typeface, and additional transformation could be applied to the letters itself - e.g. skew transform for the italic.

Note: Make sure that this will also work when exporting to PDF in WordsProcessing.

This property should work similar to PreferredWidth cell property but in vertical direction.

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