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.

In reply to Re^5: Convert XLSX to TSV and remove CRLF in cells by jandrew
in thread Convert XLSX to TSV and remove CRLF in cells by bulrush

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.