Re^4: Looking for assistance for proper fix for Spreadsheet::XLSX bug(?)

in reply to Re^3: Looking for assistance for proper fix for Spreadsheet::XLSX bug(?)
in thread Looking for assistance for proper fix for Spreadsheet::XLSX bug(?)

Spreadsheet::Read also uses Spreadsheet::XLSX under the hood. Buggy or not, I found that Spreadsheet::XLSX handled the euro symbol without issue via Spreasheet::BasicRead.

I think the heart of the problem, as I've discovered, is that the modules are trying to applying a custom format improperly and there is really no reason for these modules to try to apply the custom formatting because all it does is insert some padding into the cell. To address this, I'm just going to strip out the weird formatting command in the format: _€, and not worry about this anymore.

All the XLSX modules, with the exception of Spreadsheet::Read, haven't been touched in about 4 years and have long issue queues. But Spreadsheet::Read relies on modules that are not maintained.

$PM = "Perl Monk's";
$MCF = "Most Clueless ~~Friar~~ ~~Abbot~~ ~~Bishop~~ ~~Pontiff~~ ~~Deacon~~ ~~Curate~~ ~~Priest~~ Vicar";
$nysus = $PM . ' ' . $MCF;
Click here if you love Perl Monks

Comment on Re^4: Looking for assistance for proper fix for Spreadsheet::XLSX bug(?) Download Code

Replies are listed 'Best First'.
Re^5: Looking for assistance for proper fix for Spreadsheet::XLSX bug(?) by Tux (Canon) on May 29, 2020 at 17:15 UTC
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	[reply]

Replies are listed 'Best First'.

Re^5: Looking for assistance for proper fix for Spreadsheet::XLSX bug(?)
by Tux (Canon) on May 29, 2020 at 17:15 UTC

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

[reply]

In Section Seekers of Perl Wisdom