Currently, signature flags, represented by the 'SigFlags' optional entry, are not imported and exported, and there is no API for setting them.
As a result, documents signed with RadPdfProcessing (or with RadPdfViewer) appear in Adobe Reader without the blue document message bar at the top (the analogue of the RadPdfViewer's SignaturePanel).
If the API is supported, setting the flag to 1 or 3 would ensure that the message bar would be visualized in Adobe Reader.
When exporting a document with the .NET Framework implementation, only subsets of the used fonts are embedded in the document. This is currently not available in the Silverlight implementation, and it most probably won't be available in the .NET Standard implementation, as the current implementation is dependent on the WPF font classes. Provide API to plug similar logic when using different platforms as well.
The signature field preserves information about the time of signing through the TimeOfSigning property of Signature.Properties. However, the DateTime object doesn't keep info about the time zone the document has been signed in. Some customers need to obtain this information.
Currently, there is internal API which is used by RadWordsProcessing PDF export functionality. We should consider making appropriate public API which would expose tab stops editing functionality.
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, there is no way to know when a new page is created when content "overflows" to the next page This event may be needed in order to generate the header and footer based on the currently generated content. In simple header/footer scenarios, however, this event may not be needed and the headers and footers may be drawn after all pages are generated as described in the comments below.
Some PDF files have an additional content added before the file header (before %PDF-1.4 for example). This additional content makes all byte offsets in the document invalid, which causes the format provider to throw an exception. At this point, to import a similar document it should be pre-processed so the content before the version header is removed before importing it.
The public API may be implemented as property of PdfExportSettings. Implementing this feature would help to easily workaround issue with PdfProcessing documents that cannot be opened on devices with iOS version 10.2 (due to the default FlateDecode compression).
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.
As some other decoders, JBIG2 may also handle different parameters in order to correctly decode the stream. Currently, decode parameters are not supported for this decoder.
Highlight annotations appear as highlights in the text of a document. When opened, they display a pop-up window containing the text of the associated note.
Square annotation displays a rectangle on the page. When opened, it displays a pop-up window containing the text of the associated note.
Add a setting that allows enabling printing of protected documents.
This is content stream operator used for setting color in Device, CIE-based or Indexed color space. Available in R2 2018 Official Release version.