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: |
tlhackque [...] yahoo.com
|
Cc: |
|
AdminCc: |
|
|
Severity: |
(no value)
|
Broken in: |
0.59 |
Fixed in: |
0.64 |
|
Tue Feb 18 12:45:20 2014
tlhackque [...] yahoo.com - Ticket created
Same test file as rt #93138 demonstrates this.
This time, the first sheet.
The value of cell D7 is "=TODAY()". $cell->value returns '[$F8], 4, 1687' In Excel, displays as 'Tuesday, February 18, 2014'
The type is reported as numeric and the unformatted value is the date serial number. But there is no obvious way for an application to determine this. But we try this hueristic:
my $ss=Spreadsheet::ParseExcel->new;
my $wb=$ss->parse('file.xls');
my $cell = $wb->worksheet(0)->get_cell(6,3);
my $cellType = $cell->type();
print '"',$wb->worksheet(0)->get_cell(6,3)->value,'"'; # "[$F8], 4, 1687"
if( $cellType =~ /^(Numeric|Date)$/ && (my $fno = $cell->{FormatNo}) ) { # Formatted date
my( $dval, $color, $locale ) = Spreadsheet::ParseExcel::Utility::ExcelFmt( $cell->value, $cell->unformatted, $wb->{Flg1904}, 0, 1 ); # This call dies
}
The call to ExcelFmt fails:
Modification of non-creatable array value attempted, subscript -1 at /usr/lib/perl5/site_perl/5.8.8/Spreadsheet/ParseExcel/Utility.pm line 757.
It appears that the code thinks that the comma in the format is grouping numbers, not part of a date format.
A fix would be appreciated.
Thanks.
Tue Feb 18 12:57:26 2014
jmcnamara [...] cpan.org - Correspondence added
Hi,
Thanks for the bug reports.
Just to let you know, so you get some feedback, I no longer have time to maintain this module and put it up for adoption.
Hopefully the next maintainer can fix some of these issues.
John
Tue Feb 18 12:57:26 2014
The RT System itself - Status changed from 'new' to 'open'
Tue Feb 18 14:11:22 2014
tlhackque [...] yahoo.com - Correspondence added
On Tue Feb 18 12:57:26 2014, JMCNAMARA wrote:
Show quoted text> Hi,
>
> Thanks for the bug reports.
>
> Just to let you know, so you get some feedback, I no longer have time
> to maintain this module and put it up for adoption.
>
> Hopefully the next maintainer can fix some of these issues.
>
> John
Thanks for letting me know. That's too bad; it is a useful module. I hope someone with the right expertise volunteers.
I have (ugly) work-arounds for all but this issue.
If I encounter other issues, I'll still file reports in the hope that someone signs up. I hope that you have enough cycles to advertise vigorously...
Thanks for your past efforts.
Tue Mar 11 17:44:35 2014
DOUGW [...] cpan.org - Correspondence added
Tue Mar 11 17:44:36 2014
DOUGW [...] cpan.org - Status changed from 'open' to 'resolved'