Special chars (åäö) with PdfFormatProvider wont work.

Project submitted!

    public void SpecialCharsTest()
        {
            RadFlowDocument document = new RadFlowDocument();

            RadFlowDocumentEditor editor = new RadFlowDocumentEditor(document);

            editor.InsertText("Before text");
            editor.InsertText("åäö ÅÄÖ ☕"); // This line will not appear in the pdf 
            editor.InsertText("After text");
            using (Stream output = new FileStream("specialCharTest.pdf", FileMode.OpenOrCreate))
            {
                PdfFormatProvider provider = new PdfFormatProvider();
                provider.Export(document, output);
            }
        }

Special characters wont work :-/

When merging files that contain the "159 '\u009f'" char, ArgumentException("The encoding is not supported.") is thrown.

Workaround:

Use PdfFormatProvider.

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. 

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.

Implement import of PDF to RadFlowDocument, using PdfFormatProvider. This would require text recognition (including determining where paragraphs end as opposed to new line inserted because of the layout) and table recognition.

This will allow conversion of PDF documents to docx, RTF and HTML.

The exception is thrown with the message "Password is not correct" even when the user password is correct. This issue occurs for specific encryption algorithm parameters only.

Expose an easy way to create .xlsx documents from DataTable objects.

When a csv is exported the entire range which has values is exported. When export is done in Excel, the cells of this range which are empty are marked by an additional field, separated by a comma. This comma is present in SpreadProcessing only in places where it is obligatory for example in the middle of the row. Obligatory comma in this context means that without it the file will not be read correctly by Excel or SpreadProcessing. In places where it is not obligatory, like in an empty row or in the end of the row, it is skipped. These non-obligatory commas do not influence how the file will be interpreted by Excel, however, according to the most-popular csv spec, they should be present, which means that there could be parsers which are unable to parse the resulting file. (2.4 Each line should contain the same number of fields throughout the file.) 

Example:
Exported by Excel:
---------------------------------------
Product,Unit Price,Units in Stock,Discontinued
Chai,$18.00 ,39,
Chang,,17,
Chef Anton's Cajun Seasoning,$22.00 ,53,No
,,,
Chef Anton's Gumbo Mix,$21.35 ,0,No
---------------------------------------
Exported by SpreadProcessing:
---------------------------------------
Product,Unit Price,Units in Stock,Discontinued
Chai,$18.00 ,39
Chang,,17
Chef Anton's Cajun Seasoning,$22.00 ,53,No

Chef Anton's Gumbo Mix,$21.35 ,0,No
---------------------------------------
Note the extra commas in the empty row and in the end of the first two rows in the SpreadProcessing sample.

This element serves as a frame and allows the element to be positioned as a floating element. More information about it is available in section 22.9.2.18 ST_XAlign (Horizontal Alignment Location) of Open Office XML.
DECLINED: Duplicate with - Implement support for Text Frame Properties.

At this point the PdfFormatProvider does not support floating images and these elements are skipped when exporting to PDF.

The feature is trivial for floating images with "Behind Text"/"In Front of Text" settings, but otherwise floating images are affecting the text layout in complex ways.

Add support for conditional formatting of cells - allow applying of rules used during visualization of cells to automatically apply formatting depending on their values.