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: |
gstead [...] cox.net
|
Cc: |
|
AdminCc: |
|
|
Severity: |
(no value)
|
Broken in: |
(no value)
|
Fixed in: |
(no value)
|
|
Thu Dec 18 14:07:03 2008
gstead [...] cox.net - Ticket created
First I'd like to say that ParseExcel is way cool, and I use it a lot. I
occasionally cannot parse Excel files, receiving the error: "substr
outside of string at
/usr/lib64/perl5/site_perl/5.8.8/Spreadsheet/ParseExcel.pm line 1672."
I've reduced a test file as much as possible: 1 row, 11 cells. The
attached test.pl script demonstrates the problem [it basically calls
Parse() ]. Is there some possibility you could look at this? I've looked
at ParseExcel.pm but don't understand Excel file internals.
Other information that may be helpful:
Distribution name and version: Spreadsheet::ParseExcel (0.33)
Perl version: v5.8.8 built for x86_64-linux
Operating System vendor and version: Linux snap 2.6.20-gentoo-r8 #3 SMP
Sat Jul 14 11:14:30 PDT 2007 x86_64 Dual Core AMD Opteron(tm) Processor
270 AuthenticAMD GNU/Linux
Please let me know if I can provide anything else.
best regards,
-Graham
use strict;
use Spreadsheet::ParseExcel;
my $file = $ARGV[0] || "test.xls";
print STDERR "Spreadsheet::ParseExcel::Workbook->Parse($file)\n";
my $excel = Spreadsheet::ParseExcel::Workbook->Parse($file);
Message body not shown because it is not plain text.
Wed Dec 31 08:47:25 2008
jmcnamara [...] cpan.org - Correspondence added
On Thu Dec 18 14:07:03 2008, gstead@cox.net wrote:
Show quoted text> First I'd like to say that ParseExcel is way cool, and I use it a lot. I
> occasionally cannot parse Excel files, receiving the error: "substr
> outside of string at
> /usr/lib64/perl5/site_perl/5.8.8/Spreadsheet/ParseExcel.pm line 1672."
Hi Graham,
I haven't seen that bug before.
I'll look into it but it looks a little tricky.
John.
--
Wed Dec 31 08:47:25 2008
The RT System itself - Status changed from 'new' to 'open'
Wed Dec 31 15:50:02 2008
jmcnamara [...] cpan.org - Correspondence added
Hi Graham,
What version of Excel, or other spreadsheet application, was used to produce the test.xls file?
John.
--
Wed Dec 31 15:58:01 2008
gstead [...] cox.net - Correspondence added
Our process goes something like this:
1) An Excel is produced by Spreadsheet::WriteExcel
2) Someone edits that file, either in Excel 2003 or Excel 2007. I can
check if knowing the specific version is important.
3) We read the file with Spreadsheet::ParseExcel, receiving the
aforementioned error
4) I edited the file in Excel 2007 to remove rows/columns that did not
(apparently) cause the problem
Please let me know if this answers your question. I am happy to provide
any additional information that may help.
best regards,
-Graham
John McNamara via RT wrote:
Show quoted text
Wed Dec 31 16:01:33 2008
jmcnamara [...] cpan.org - Correspondence added
On Wed Dec 31 15:58:01 2008, gstead@cox.net wrote:
Show quoted text> Our process goes something like this:
>
Hi Graham,
Show quoted text> 1) An Excel is produced by Spreadsheet::WriteExcel
Do you get the parse error if you process the file at that stage?
Show quoted text> 2) Someone edits that file, either in Excel 2003 or Excel 2007. I can
> check if knowing the specific version is important.
Yes, let me know. It may be significant.
Thanks,
John.
--
Thu Jan 08 07:40:29 2009
jmcnamara [...] cpan.org - Correspondence added
On Wed Dec 31 16:01:33 2008, JMCNAMARA wrote:
Show quoted text> On Wed Dec 31 15:58:01 2008, gstead@cox.net wrote:
> > Our process goes something like this:
> >
>
> Hi Graham,
>
> > 1) An Excel is produced by Spreadsheet::WriteExcel
>
> Do you get the parse error if you process the file at that stage?
>
>
> > 2) Someone edits that file, either in Excel 2003 or Excel 2007. I can
> > check if knowing the specific version is important.
>
> Yes, let me know. It may be significant.
>
> Thanks,
>
> John.
Hi Graham,
Any update on this?
John.
--
Sun Jan 11 09:57:31 2009
jmcnamara [...] cpan.org - Correspondence added
On Thu Dec 18 11:07:03 2008, gstead@cox.net wrote:
Show quoted text>
> I've reduced a test file as much as possible: 1 row, 11 cells. The
> attached test.pl script demonstrates the problem [it basically calls
> Parse() ]. Is there some possibility you could look at this? I've looked
> at ParseExcel.pm but don't understand Excel file internals.
Hi Graham,
I managed to isolate this issue so no further input is required.
There will be a fix in the next release.
John.
--
Tue Jan 13 14:04:38 2009
gstead [...] cox.net - Correspondence added
That's great news! Thanks again for your time.
-Graham
John McNamara via RT wrote:
Show quoted text> <URL:
https://rt.cpan.org/Ticket/Display.html?id=41813 >
>
> On Thu Dec 18 11:07:03 2008, gstead@cox.net wrote:
>
>> I've reduced a test file as much as possible: 1 row, 11 cells. The
>> attached test.pl script demonstrates the problem [it basically calls
>> Parse() ]. Is there some possibility you could look at this? I've looked
>> at ParseExcel.pm but don't understand Excel file internals.
>>
>
> Hi Graham,
>
> I managed to isolate this issue so no further input is required.
>
> There will be a fix in the next release.
>
> John.
>
Wed Jan 14 03:56:29 2009
jmcnamara [...] cpan.org - Correspondence added
Hi,
This issue has been fixed in Spreadsheet::ParseExcel version 0.45.
Thanks,
John.
--
Wed Jan 14 03:56:30 2009
jmcnamara [...] cpan.org - Status changed from 'open' to 'resolved'