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: |
patrick.sauve [...] orange-ftgroup.com
|
Cc: |
|
AdminCc: |
|
|
Severity: |
(no value)
|
Broken in: |
0.33 |
Fixed in: |
(no value)
|
|
Thu Dec 11 08:46:52 2008
patrick.sauve [...] orange-ftgroup.com - Ticket created
Hello,
I have a problem using method SaveAs from SaveParser. When cell have
format with rotation, the cell in the file that is saved have a bad
format (90° in the original Xls file and only 3° in the new file).
I fixed it by this way :
I replace :
- if($pFmt->{Rotate}==0) {
- $oFmt->set_rotation(0);
- }
- elsif($pFmt->{Rotate}> 0) { # Mainly ==90
- $oFmt->set_rotation(3);
- }
- elsif($pFmt->{Rotate} < 0) { # Mainly == -90
- $oFmt->set_rotation(2);
- }
=====================================
by
+ $oFmt->set_rotation($pFmt->{Rotate});
Perhaps, the method in WriteExcel had changed.
Thu Dec 11 09:23:25 2008
jmcnamara [...] cpan.org - Correspondence added
On Thu Dec 11 08:46:52 2008, Patobs wrote:
Show quoted text> Hello,
>
> I have a problem using method SaveAs from SaveParser. When cell have
> format with rotation, the cell in the file that is saved have a bad
> format (90° in the original Xls file and only 3° in the new file).
Hi,
I actually had that down on the TODO list. :-)
I'll fix it in the next release.
Thanks,
John.
--
Thu Dec 11 09:23:27 2008
The RT System itself - Status changed from 'new' to 'open'
Thu Jan 08 07:31:12 2009
jmcnamara [...] cpan.org - Correspondence added
10 min
Fixed in version 0.43.
John.
--
Thu Jan 08 07:31:13 2009
jmcnamara [...] cpan.org - Status changed from 'open' to 'resolved'