Output widget export to CSV - Excel 'ignores' \n ??

[smudgester]

Hi Mottie,

I have been using your fork a while and am now trying to get the output widget working on my site.

I am using the following code:

        $("table.download").tablesorter({
            widthFixed : true,
            widgets: ["output"],
            ignoreCase: false,
            widgetOptions : {
                output_separator            : ',', 
                output_ignoreColumns        : [], 
                output_dataAttrib           : 'data-name', 
                output_headerRows           : true,  
                output_delivery             : 'd', 
                output_saveRows             : 'a'
                output_duplicateSpans   : false,
                output_replaceQuote         : '\u201c;', 
                output_includeHTML          : false, 
                output_trimSpaces           : true, 
                output_wrapQuotes           : true, 
                output_popupStyle           : 'width=580,height=310',
                output_saveFileName         : 'optionsandchoices_report.csv',
                output_saveElement  : "#assignInfo",
                output_callbackJSON  : function($cell, txt, cellIndex) { return txt + '(' + cellIndex + ')'; },
                output_callback      : function(config, data) { return true; },
                // the need to modify this for Excel no longer exists
                output_encoding      : 'data:application/octet-stream;charset=utf8,'
            }
        });

        $('.reportView button.download').click(function(){
          var $table = $(this).siblings('table.download');
          $table.trigger('outputTable');
          return false;
        });

My download button generates the CSV file correctly and I can see \n where expected. However, when I try to open the file in Excel (either via File -> Open or double-clicking on the file) the \n's are still there and haven't been replaced with ALT+ENTER.

Any ideas ?

[Mottie]

Hi @smudgester!

Hmm, yeah I'm seeing this problem too... I know it was working properly before. Did they change Excel or something?

I'll investigate and hopefully find a solution. Thanks for reporting this issue!

[Mottie]

Ok, it should be fixed now!

[smudgester]

Thanks - will give the latest version a try

[smudgester]

Works perfectly. Thanks once again.