Currently, NotSupportedEncryptionException is thrown when PdfFileSource is initialized with an encrypted PDF file. Available in R2 2018 Official Release Version.
Add support for a strikethrough property or strikethrough-related properties in the TextProperties class.
Currently this operator is interpreted correctly only for Pattern colorspace. It also partially supports the rest of the colorspaces from R1 2018. Available in R2 2018 Official Release Version.
Implement the "k" and "K" color operators, which sets the color in DeviceCMYK color space. Currently graphics with color set with these operators are imported with incorrect colors. Available in R2 2018 Official Release Version.
Currently, we support inserting png, jpg and other raster graphic images. Provide a way to insert image from SVG (vector graphic image format), by creating a FormSource from its parsed XML.
PDF/A-1a is with conformance level A (for "accessibility"), and must adhere to all of the requirements of the PDF Reference as modified by the ISO 19005 specification. It requires structural and semantic properties to be preserved. Level 1a uses “Tagged PDF” and Unicode character maps to preserve the document's logical structure and content text stream in natural reading order. The following features are used: - Language specification - Hierarchical document structure - Tagged text spans and descriptive text for images and symbols - Character mappings to Unicode The purpose is to improve accessibility and make the content accessible for screen readers.
This would ensure preserving the existing PDF file pages and document properties untouched and additionally would allow making a few modifications to the file. By appending bytes to existing PDF file one may achieve: - Modifying specific pages content and properties. - Adding new pages to pages collection. - Modify some document properties (such as Bookmarks). - Edit interactive forms field values. - Add digital signatures to existing documents.
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
For example when some PDF file has uncompressed contents we may import it and apply better compression to the stream objects.
Currently RadFixedDocumentInfo is used only for export of Author, Title and Description document metadata properties. This should be extended to support custom properties. We should also implement the import of RadFixedDocumentInfo.
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.
Currently, 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
In business or enterprises there is more and more demand for PDF/A-3. In Germany it is Zugferd for hybrid invoices, in Brazil Nota Fiscal Eletronica 2.0, in France FACTUR-X. Also for longterm preservation it is import to support PDF/A-3. If I would be the PM of this library this would be my number one priority!
Currently, NotSupportedEncryptionException is thrown.
Currently, Standard fonts are exported always with StandardEncoding. This does not allow export of some special characters which do not fit in the first 255 glyph definitions in the font. Most of these characters are the ones with an accent such as "Eacute" glyph (É) which is with position number 303 in Times Roman font. The list of all standard fonts may be found in this documentation section: https://docs.telerik.com/devtools/document-processing/libraries/radpdfprocessing/concepts/fonts#standard-fonts
Square annotation displays a rectangle on the page. When opened, it displays a pop-up window containing the text of the associated note.
Encryption Algorithm 4 is implemented for R1 2018 official release. This includes all encryptions except AES 256 which is related to Encryption Algorithm 5. For AES 256 you may vote and follow this feedback item: https://feedback.telerik.com/Project/184/Feedback/Details/240154-pdfprocessing-support-encryption-algorithm-5-with-aes-256
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.