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: |
TNelson [...] manitoulintransport.com
|
Cc: |
|
AdminCc: |
|
|
Severity: |
(no value)
|
Broken in: |
(no value)
|
Fixed in: |
(no value)
|
|
Mon Nov 24 13:08:04 2008
TNelson [...] manitoulintransport.com - Ticket created
Spreadsheet-ParseExcel-0.41
Perl v 5.8.8 for i686-linux?
I'm encountering a problem when parsing an excel spreadsheet containing a
date value 12:15:45 AM in one of its cells. The result of using the Value
method on the cell object is -17:-59:-59 AM/PM, instead of 00:15:45 AM/PM
as expected. I've tried using the Value method on a cell containing
12:15:44 AM and one containing 12:15:46 AM, and recieved the expected
output.
Here is the code I'm using to test this:
#!usr/bin/perl
use Spreadsheet::ParseExcel;
use strict;
my $file = '/var/www/portlets/taryn/ParseSchedule/Book1.xls';
my $excel = Spreadsheet::ParseExcel::Workbook->Parse($file);
my $sheet;
my $cell;
foreach $sheet (@{$excel->{Worksheet}}){
$cell = $sheet->{Cells}[0][0];>
print "\n";
print $cell->Value;
print "\n";
$cell = $sheet->{Cells}[1][0];>
print $cell->Value;
print "\n";
$cell = $sheet->{Cells}[2][0];>
print $cell->Value;
print "\n";
}
Contents of Cell[0][0] : 12:15:44 AM => results 0:15:44 AM/PM
Contents of Cell[1][0] : 12:15:45 AM=> results -17:-59:-59 AM/PM
Contents of Cell[2][0] : 12:15:46 AM=> results 0:15:46 AM/PM
I've also been able to find some other values that give the same incorrect
output: 12:14:51 AM, 12:16:39 AM
I haven't tested all possible values, so others may exist.
Wed Nov 26 18:10:05 2008
jmcnamara [...] cpan.org - Correspondence added
Hi,
Thanks for that. I'll look into it.
John,
--
Wed Nov 26 18:10:07 2008
The RT System itself - Status changed from 'new' to 'open'
Tue Jan 20 04:23:31 2009
jmcnamara [...] cpan.org - Correspondence added
120 min
Hi,
Fixed in version 0.46.
Thanks,
John.
--
Tue Jan 20 04:23:31 2009
jmcnamara [...] cpan.org - Status changed from 'open' to 'resolved'