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: |
tlhackque [...] yahoo.com
|
Cc: |
|
AdminCc: |
|
|
Severity: |
(no value)
|
Broken in: |
0.59 |
Fixed in: |
0.61 |
|
Tue Feb 25 23:55:33 2014
tlhackque [...] yahoo.com - Ticket created
One more item missing from the API: Tab color.
This one is easier; it's a completely new record type.
Here's the change, again as an overlay. For real, add the table entry, and paste in the two subroutines.
Adds get_tab_color as a worksheet function. Returns a color index (or undef if the tab hasn't had a color applied.)
Reference: The openoffice.org document. Tested against MS Excel 2003.
package ExcelToHtml::Parser;
# Hacks to get additional information from the spreadsheets
#
# These use the Spreadsheet::ParseExcel routines for everything
# else to ensure that any bugs there aren't replicated.
our @ISA = (qw/Spreadsheet::ParseExcel/);
sub new {
my $class = shift;
$Spreadsheet::ParseExcel::ProcTbl{0x862} = \&_subSheetLayout;
return $class->SUPER::new(@_);
}
# Record type 0x862 SHEETLAYOUT
sub _subSheetLayout {
my ( $oBook, $bOp, $bLen, $sWk ) = @_;
my @iUnused;
(
my $iRc,
@iUnused[ 1 .. 10 ],
@iUnused[ 11 .. 14 ],
my $iColor, @iUnused[ 15, 16 ]
) = unpack( "vC10C4vC2", $sWk );
return unless ( $iRc == 0x0862 );
$oBook->{Worksheet}[ $oBook->{_CurSheet} ]->{TabColor} = $iColor;
}
package Spreadsheet::ParseExcel::Worksheet;
=head2 get_tab_color()
Return color index of tab, or undef if not set.
=cut
sub get_tab_color {
my $worksheet = shift;
return $worksheet->{TabColor};
}
Tue Mar 04 19:02:57 2014
DOUGW [...] cpan.org - Correspondence added
Tue Mar 04 19:02:57 2014
The RT System itself - Status changed from 'new' to 'open'
Tue Mar 04 19:02:58 2014
DOUGW [...] cpan.org - Status changed from 'open' to 'resolved'