The documents produced by WordsProcessing and SpreadProcessing are compliant with the specification. But, Open Office, Numbers and Pages (the default applications for working with .docx and .xlsx on MAC) are unable to open documents where the target attribute of the relationships of the documents is specified as an URI, instead of as a relative reference. According to the specification (Ecma Office Open XML Part 2 - Open Packaging Conventions) both formats are acceptable.

The issue is in the relationships parts, relationship element. The Target attribute can be either a URI (Target="/word/theme/theme1.xml") or a relative reference (Target="theme/theme1.xml") as stated in the specification. The document processing libraries use URI, which OpenOffice is unable to interpret, despite them being allowed by the specification.

The fix will be available in our official release Q2 2016.

The feature will be available in our official release Q2 2016.

The fix is available in our latest LIB release (v. 2015.1.0316)

From a custom function which inherit from FunctionBase it's possible to return some constant expressions like StringExpression or BoolExpression. But It's impossible to return a reference to a Cell or CellRange which will be used by another function by example or which will automatically update it's result.  There is no public constructor.

The feature will be available in our official release 2015 Q2. 

Transparency is not shown when we add png images.

The feature will be available in our official release Q1 2016.

Please add a link to the new TDP library and explain it, so people can find the place to vote for PDFProcessing!
http://feedback.telerik.com/Project/184/Feedback

The feature will be available in our official release 2015 Q2.

The feature will be available in our official release 2015 Q2.

Currently RadPdfProcessing imports Contents only from stream. In some documents Contents property may be PdfArray. 

Provide a way to convert flow formats (docx, HTML, RTF) to PDF.

The feature will be available in our official release Q1 2016.

When encryption is enabled, the streams inside the PDF document are encrypted individually. If the encrypted result contains '{' or '}' symbols, FormatException ("Input string was not in a correct format.") is thrown.