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: |
RBS [...] cpan.org
|
Cc: |
|
AdminCc: |
|
|
Severity: |
Critical |
Broken in: |
0.59 |
Fixed in: |
(no value)
|
demo.pl
example.xls
example_output.xls
|
Thu Apr 28 10:46:45 2011
RBS [...] cpan.org - Ticket created
Modifying a spreadsheet with SaveParser doesn't copy formulas. Please
see the attached example_output.xls, which was generated from
example.xls (created with Excel) and demo.pl, both of which are also
attached.
Here's the requisite version info (the Perl is strawberry flavored, if
that helps):
Perl version : 5.012001
OS name : MSWin32
Module versions: (not all are required)
Spreadsheet::ParseExcel 0.59
Scalar::Util 1.23
Unicode::Map (not installed)
Spreadsheet::WriteExcel 2.37
Parse::RecDescent 1.965001
File::Temp 0.22
OLE::Storage_Lite 0.19
IO::Stringy 2.110
use strict;
use warnings;
use Spreadsheet::ParseExcel::SaveParser;
my $parser = new Spreadsheet::ParseExcel::SaveParser;
my $wb = $parser->Parse("example.xls");
my $ws = $wb->{Worksheet}[0];
$ws->AddCell( 0, 0, 10 );
$wb->SaveAs( "example_output.xls" );
Message body not shown because it is not plain text.
Message body not shown because it is not plain text.
Fri Apr 29 06:44:04 2011
jmcnamara [...] cpan.org - Correspondence added
On Thu Apr 28 10:46:45 2011, RBS wrote:
Show quoted text> Modifying a spreadsheet with SaveParser doesn't copy formulas.
Hi,
Thanks for your detailed report.
This is a known and (probably not very well) documented limitation of
ParseExcel and SaveParser.
Unfortunately, it is non-trivial to fix, so it is unlikely that it will
ever be implemented.
John.
--