Re^3: Convert XLSX to TSV and remove CRLF in cells

Tux I agree that Spreadsheet::XLSX is buggy. However, it is my experience that XML::Twig segfaults due to a perl bug in Windows perls prior to 5.15. Since Spreadsheet::ParseXLSX is built on that it makes both of these packages buggy for a certain population of users. (Which is partly why I wrote my package on XML::LibXML.)

On the other hand I have run into a lot of implementations of both of these packages where people are quite happy with them. Additionally for small spreadsheets where you are only extracting data and not formats, Spreadsheet::XLSX tends to be faster.

update:I think Spreadsheet::ParseXLSX also fails to open Excel sheets that contain dedicated chartsheets (not worksheets). The XML::Twig RT que is a bit daunting, and the current release on CPAN testers has open fails. Otherwise I agree that Spreadsheet::ParseXLSX is a really great module.

Comment on Re^3: Convert XLSX to TSV and remove CRLF in cells

Replies are listed 'Best First'.
Re^4: Convert XLSX to TSV and remove CRLF in cells by Tux (Canon) on Jun 18, 2015 at 06:51 UTC
Did you file tickets against Spreadsheet::ParseXLSX for those failing situations? The author is very responsive to bugs! Enjoy, Have FUN! H.Merijn	[reply]
Re^5: Convert XLSX to TSV and remove CRLF in cells by jandrew (Chaplain) on Jun 18, 2015 at 13:32 UTC
Tux I have not filed any tickets for Spreadsheet::ParseXLSX as you well know since I am not on the list, but my personal reason for not using Spreadsheet::ParseXLSX is it's dependency on XML::Twig. I see that you do file tickets against Spreadsheet::ParseXLSX and I applaud that. As a fellow module author I think we both know how much that is appreciated. The XML::Twig segfault issue was already filed as ticket #20 then closed as un-reproduce-able by the author (not fixed). Since it was a perl bug and not an XML::Twig bug or a Spreadsheet::ParseXLSX bug is it a bug or just a design choice? (choice is good) Other than that Spreadsheet::ParseXLSX emulates Spreadsheet::ParseExcel mostly seamlessly and very well. I have chosen not to file the chartsheet bug on Spreadsheet::ParseXLSX because I am only peripherally aware of the possibility. I heard of it because it was filed against the Spreadsheet parser I maintain. I have been fairly busy and have not done the necessary validation work to write up a solid issue for doy. I would invite you to work up the validation of the chartsheet fail and file an issue if you feel passionate about it.	[reply]