comment on

Spreadsheet::Read just uses what is available to parse the source given, and prefers Spreadsheet::ParseXLSX over Spreadsheet::XLSX unless specifically told to use the buggy module, which is supported because it can be supported (and because the better module did not yet exist when the buggy module was readily available when I started Spreadsheet::Read. It so only relies on (bad) modules if there are no better alternatives available.

If you find bugs, real bugs, in the parser, make a ticket. If you find bugs in the wrapper as it does not deal with the parser correctly, let me know.

I am working with Corion to get his new parsers for ODS supported too, but that is currently too unstable.

As I use XLSX for quite a number of (big) jobs, I am fairly certain it behaves well. I must admit that I never had to deal with buggy custom formats, so I never hit any trouble.

Enjoy, Have FUN! H.Merijn

In reply to Re^5: Looking for assistance for proper fix for Spreadsheet::XLSX bug(?) by Tux
in thread Looking for assistance for proper fix for Spreadsheet::XLSX bug(?) by nysus

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


The stupid question is the question not asked
	PerlMonks