KeyNotFoundException is thrown on import. The number formats with id 5, 6, 7 and 8 are missing in the built-in number formats.

Available in R2 2018 Official Release version.

At this point the culture used by RadSpreadProcessing (in the FormatHelper and internally in SpreadsheetCultureHelper) is determined by the current thread culture on startup. Provide ability to:
- to change the culture at runtime. Currently, when the thread culture is changed, RadSpreadProcessing is "stuck" with the original one.
- set this culture independently of the current thread's one.

When iterating through the rows and cells of an imported Worksheet in at least one of the rows GetValue().Value.ResultValueType for a number cell is set to GetValue().Value.ResultValueType.Text and the value to "error" or "string".

For us this happens in a worksheet with 200 rows max. and columns formated as date, time, time followed by some text and number columns.
In our Tests with different excel files it allways happened once (between line 11 and 16) and only for the first two columns.

Exporting the worksheet back into a new excel file will show all rows and columns types and values OK.

RIGHT returns the last character or characters in a text string, based on the number of characters you specify.

A list of the supported functions is available at http://docs.telerik.com/devtools/document-processing/libraries/radspreadprocessing/features/formulas/functions

This function can be implemented as a custom function. Check the following resources for more details on how to achieve that:

- http://docs.telerik.com/devtools/document-processing/libraries/radspreadprocessing/features/formulas/custom-functions
- https://github.com/telerik/xaml-sdk/tree/master/Spreadsheet/WPF/CustomFunctions

Add support for TEXT function. The TEXT function allows changing the way a number appears by applying formatting to it using format codes.

TEXT(value, format_text)

A list of the supported functions is available at http://docs.telerik.com/devtools/document-processing/libraries/radspreadprocessing/features/formulas/functions 

This function can be implemented as a custom function. Check the following resources for more details on how to achieve that:

- http://docs.telerik.com/devtools/document-processing/libraries/radspreadprocessing/features/formulas/custom-functions 
- https://github.com/telerik/xaml-sdk/tree/master/Spreadsheet/WPF/CustomFunctions 

Add support for VALUE function. VALUE converts a text string that represents a number to a number.

A list of the supported functions is available at http://docs.telerik.com/devtools/document-processing/libraries/radspreadprocessing/features/formulas/functions

This function can be implemented as a custom function. Check the following resources for more details on how to achieve that:

- http://docs.telerik.com/devtools/document-processing/libraries/radspreadprocessing/features/formulas/custom-functions
- https://github.com/telerik/xaml-sdk/tree/master/Spreadsheet/WPF/CustomFunctions

IFERROR returns a value you specify if a formula evaluates to an error; otherwise, returns the result of the formula.

A list of the supported functions is available at http://docs.telerik.com/devtools/document-processing/libraries/radspreadprocessing/features/formulas/functions

This function can be implemented as a custom function. Check the following resources for more details on how to achieve that:

- http://docs.telerik.com/devtools/document-processing/libraries/radspreadprocessing/features/formulas/custom-functions
- https://github.com/telerik/xaml-sdk/tree/master/Spreadsheet/WPF/CustomFunctions

Split allows you to split the window into different panes that each scroll separately. 

This feature is different than the horizontal/vertical split of freeze panes, which is supported.

When there are split panes in a workbook, the topLeftCell property can be omitted. In this case, the format provider throws NullReferenceException.

The ADDRESS function is used to obtain the address of a cell in a worksheet, given specified row and column numbers. For example, ADDRESS(2,3) returns $C$2.

The r attribute of a cell defines the reference the cell is pointing to in a style similar to A1. Setting this attribute is optional but when set to an empty string, it cannot be imported - an ArgumentException is thrown with message "cellName" by the Guard class in NameConverter.ConvertCellNameToIndex().

Here is an example of such a definition:

<row r="1" spans="1:12">
  <c r=""/>
</row>


MS Excel and Libre Office can open such documents.

XLSB is binary format that should theoretically allow fast reading and writing to the file. 

Excel exports shapes as TwoCellAnchor elements, which specifies the top left and the bottom right location of a shape. The size of the shape is recorded in the extents element (a:ext), cx and cy attributes. At the moment, the spreadsheet import first looks at the extents element and if it doesn't find the size there, calculates it from the TwoCellAnchor element. 

However, if an XLSX document has a shape with incorrect size indicated in the extents element, Excel will still be able to open it correctly, probably because it looks at the TwoCellAnchor element. RadSpreadsheet/SpreadProcessing, on the other hand, will show the image with an incorrect size.

Add API for registering custom image decoders, e.g. for .emf and .wmf images.

WorksheetPageSetup.ScaleFactor is limited in the range 0.5 - 4 due to limitations in the UI implementations, but this is not needed in RadSpreadProcessing alone.

Add support for theme effects (format schemes). They are described in OOXML using the 'fmtScheme' element. Thing of providing predefined sets.

In MS Excel the UI for changing is located in Page Layout tab -> Themes -> Effects.

Implement export to XPS file format.

Implement support for form controls (Button, Combo Box, Check Box, Spin Button, List Box, Option Button, Group Box, Label, Scroll Bar).