This queue is for tickets about the Spreadsheet-ParseExcel CPAN distribution.
Maintainer(s)' notes
If you are reporting a bug in Spreadsheet::ParseExcel here are some pointers
1) State the issues as clearly and as concisely as possible. A simple program or Excel test file (see below) will often explain the issue better than a lot of text.
2) Provide information on your system, version of perl and module versions. The following program will generate everything that is required. Put this information in your bug report.
#!/usr/bin/perl -w
print "\n Perl version : $]";
print "\n OS name : $^O";
print "\n Module versions: (not all are required)\n";
my @modules = qw(
Spreadsheet::ParseExcel
Scalar::Util
Unicode::Map
Spreadsheet::WriteExcel
Parse::RecDescent
File::Temp
OLE::Storage_Lite
IO::Stringy
);
for my $module (@modules) {
my $version;
eval "require $module";
if (not $@) {
$version = $module->VERSION;
$version = '(unknown)' if not defined $version;
}
else {
$version = '(not installed)';
}
printf "%21s%-24s\t%s\n", "", $module, $version;
}
__END__
3) Upgrade to the latest version of Spreadsheet::ParseExcel (or at least test on a system with an upgraded version). The issue you are reporting may already have been fixed.
4) Create a small example program that demonstrates your problem. The program should be as small as possible. A few lines of codes are worth tens of lines of text when trying to describe a bug.
5) Supply an Excel file that demonstrates the problem. This is very important. If the file is big, or contains confidential information, try to reduce it down to the smallest Excel file that represents the issue. If you don't wish to post a file here then send it to me directly: jmcnamara@cpan.org
6) Say if the test file was created by Excel, OpenOffice, Gnumeric or something else. Say which version of that application you used.
7) If you are submitting a patch you should check with the maintainer whether the issue has already been patched or if a fix is in the works. Patches should be accompanied by test cases.
Asking a question
If you would like to ask a more general question there is the Spreadsheet::ParseExcel Google Group.
Owner: |
Nobody in particular
|
Requestors: |
greg [...] warnes.net
|
Cc: |
|
AdminCc: |
|
|
Severity: |
(no value)
|
Broken in: |
(no value)
|
Fixed in: |
(no value)
|
|
Thu Apr 23 18:22:53 2015
greg [...] warnes.net - Ticket created
I maintain the 'gtools' package for the R statistical software system (
http://r-project.org), and I provide a function that uses
Spreadsheet::ParseExcel to convert .xls files to csv.
One of my users has a file ('87Fire.xls', attached) that generates 'Use of
uninitialized value' errors when it is parsed with Spreadsheet::ParseExcel
0.65, but reads properly in Microsoft Excel and other spreadsheet tools.
-Greg
Message body not shown because it is not plain text.
Thu Apr 23 18:54:41 2015
jmcnamara [...] cpan.org - Correspondence added
Hi,
The bug tracker for Spreadsheet::ParseExcel has moved to here:
https://github.com/runrig/spreadsheet-parseexcel/issues
The issue seems to be that the file format is very old, possibly Excel 1 or 2 format and the XF record is much shorter than in later versions. Hence the errors when the module tries to parse out the XF sub-properties.
A simple workaround would be to change the following line in _subXF() from:
if ( $oBook->{BIFFVersion} == verBIFF4 ) {
to
if ( $oBook->{BIFFVersion} <= verBIFF4 ) {
Report the issue on GitHub and refer to my answer here.
Regards,
John
Thu Apr 23 18:54:41 2015
The RT System itself - Status changed from 'new' to 'open'