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: |
Extern.Guntram.Blohm [...] AUDI.DE
|
Cc: |
|
AdminCc: |
|
|
Severity: |
(no value)
|
Broken in: |
(no value)
|
Fixed in: |
(no value)
|
|
Tue Mar 10 12:35:41 2009
Extern.Guntram.Blohm [...] AUDI.DE - Ticket created
Hello,
i think i found a little but (at least to me) annoying bug in Spreadsheet::ParseExcel Version 0.49 (current version).
When ParseExcel.pm encounters a new workbook of type 0x0020, it sets a flag (_skip_chart):
396 #Worksheeet or Dialogsheet
397 elsif ( $iDt != 0x0020 ) { #if($iDt == 0x0010)
....
428 else {
429 # Set flag to ignore all chart records until we reach another BOF.
430 $oBook->{_skip_chart} = 1;
431 }
432 }
which gets reset when a BOF is encountered:
248 # If the low byte of the BIFF record is 0x09 then it is a BOF record.
249 # We reset the _skip_chart flag to ensure we check the sheet type.
250 if ( ( $bOp & 0xFF ) == 0x09 ) {
251 $oBook->{_skip_chart} = 0;
252 }
The condition (bOp & 0xFF) isn't correct, however. The hex IDs of valid BOF records are 0x0009, 0x0209, 0x0409 and 0x0809 according to microsoft's documentation.
However, there is a MARKERFORMAT record, that has a hex ID of 0x1009, which can occur in charts, and which matches the above condition. This leads to _skip_chart being reset prematurely, which in turn makes cell definitions that belong to the chart overwrite cells in the previous work sheet.
Changing the above line of code to
250 if ( ( $bOp & 0xFF ) == 0x09 ) {
fixes the problem.
Show quoted text> Mit freundlichen Grüßen
>
Guntram Blohm
AUDI AG
I/FP-831
85045 Ingolstadt
Tel +49-841-89-43057
mailto:extern.guntram.blohm@audi.de
http://www.audi.com
Wed Mar 11 04:45:01 2009
Extern.Guntram.Blohm [...] AUDI.DE - Correspondence added
Reviewing my bug on the web site, i see i made a stupid mistake
regarding the fix - i just duplicated the wrong line.
Of course,
250 if ( ( $bOp & 0xFF ) == 0x09 ) {
should be fixed by changing it to
250 if ( ( $bOp & 0xF0FF ) == 0x09 ) {
.
Mon Mar 30 13:30:49 2009
jmcnamara [...] cpan.org - Correspondence added
Hi,
Thanks for that. I'll fix it in the next release.
John.
--
Mon Mar 30 13:30:50 2009
The RT System itself - Status changed from 'new' to 'open'
Thu Aug 20 05:28:46 2009
jmcnamara [...] cpan.org - Status changed from 'open' to 'resolved'