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: |
Heiko.Klein [...] gmx.net
|
Cc: |
|
AdminCc: |
|
|
Severity: |
Normal |
Broken in: |
|
Fixed in: |
(no value)
|
|
Fri Jan 20 08:11:51 2006
Guest - Ticket created
Thank you for providing the very useful spreadsheet::parseexcel module.
The attached file is modified from 2602 and adresses some issues still
valid in 2603.
a) s::pe reads by default all formatting information of the excelfile
into a large hashtable. On large excel-files, this uses huge amounts of
memory (in my case: 260MB on a (3 Sheets, 5000x50 Cells) workbook). An
option is provided to read only the data, but not the formatting. This
reduces the memory consumption to 95MB, and thus, increases speed by a
factor 8.
b) s::pe doesn't handle protected workbooks. The patch to 2603 addresses
only 'external' file protection, but not workbook-protection. The
attached file croaks when detecting a protected workbook.
The current versions of s::pe give a 'Out of memory' on perl5.6.1 (not
catchable by eval) or simply fail on perl5.8
c) s::pe creates a circular reference. When using s::pe in a persistent
environment, you have to use (even with the attached file):
$sspe = Spreadsheet::ParseExcel('excel.xml');
...
# removing circular reference (bug in ParseExcel??)
foreach my $wks (@{$sspe->{Worksheet}}) {
delete $wks->{_Book};
}
Best regards,
Heiko
Message body is not shown because it is too large.
Tue Jan 24 09:29:19 2006
HEIKOK [...] cpan.org - Correspondence added
I updated my last patch to include the difference between 0.2602 and
0.2603. In addition, I re-enabled reading of protected pages with empty
password (thus not crypted).
Heiko
Message body is not shown because it is too large.
Tue Jan 24 09:29:28 2006
The RT System itself - Status changed from 'new' to 'open'
Wed Mar 05 16:42:36 2014
DOUGW [...] cpan.org - Correspondence added
All of these issues are resolved...closing ticket.
Wed Mar 05 16:42:37 2014
DOUGW [...] cpan.org - Status changed from 'open' to 'resolved'