Add support for shapes, and especially for shapes with textual content. In OOXML, shapes are represented by the wps:wsp element, and shapes with textual content by <wps:txbx>, <w:txbxContent>. Such shape can be added to a Word document using the Insert -> Text -> Text Box -> Draw Text Box, or through a shape's context menu -> Add Text. Do not confuse these shapes with Text/Rich Text content controls (see https://feedback.telerik.com/Project/184/Feedback/Details/190057 )
Allow to password-protect a workbook, so that it cannot be shown (read) without the password.
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.
With the current implementation when exporting a Stitching function all the containing functions are exported as Sampled functions even if they originally have been imported as Exponential interpolation functions, which leads to an increase in the size of the document.
More information can be found in the PDF Specification.
When this type of section break is used, the next section should start on the same page instead on the next one.
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.
Implement support for cell references to columns and rows, e.g. $1:$2, A:D, etc. Currently, CellSelection.SetValue throws ParseException, and CellSelection.SetValueAsFormula throws InvalidOperationException.
12 0 obj ( Brillig ) endobj
2545 0 obj << /Type /Page /Parent 2537 0 R /Contents 8 0 R /Resources 2538 0 R >> 2546 0 obj ....
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.