Add support for strikethrough font effect for cell formatting. Currently this is not supported by the model and is omitted on import.
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.
This is preserved in the xml once saved from MS Excel:
Implement the Exponential Interpolation Function in PdfProcessing. Currently, NotSupportedFunctionTypeException is thrown with a message "Function type 2 is not supported."
With the current implementation, the compression setting is omitted:
- streamWriter.Settings.StreamCompression
Add support for creating Tables and applying tables styles (predefined ones or custom).
Add support for VML shapes.
Related: Add support for Shape Group.
Shape Group is used to collect shapes and groups so they can be positioned and transformed as a single unit. A group contains group, shapetype, shape, pre-defined shape - arc, curve, image, line, oval, polyline, rect, roundrect - and lock elements.
When the object is serialized out as XML, its qualified name is v:group.
Such a document can be considered invalid. However, it would be good to provide functionality to handle it.
Update: After reviewing the case, we concluded that the issue is caused by the document being linearized. Therefore, this item is being marked as a duplicate. Please follow the related public item to receive notifications about future status updates.
Provide the ability to work with images in headers/footers of a worksheet. Note that large images put in headers are visualized as watermarks on printing/exporting to PDF.
Watermark in Excel: https://support.office.com/en-us/article/add-a-watermark-in-excel-a372182a-d733-484e-825c-18ddf3edf009
Currently, the numbers in a CSV file are parsed as numbers, and the leading zeros are lost. In MS Excel, leading zeros could be preserved when the values are imported as text using the more sophisticated text import wizard (http://www.upenn.edu/computing/da/bo/webi/qna/iv_csvLeadingZeros.html ). Workaround: The values could be extracted using a third-party (or custom) CSV parser, and inserted manually into the model, using CellSelection.SetValueAsText method (http://docs.telerik.com/devtools/document-processing/libraries/radspreadprocessing/working-with-cells/cell-value-types.html ).