Skip Menu |
 

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

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.

Report information
The Basics
Id: 67056
Status: open
Priority: 0/
Queue: Spreadsheet-ParseExcel

People
Owner: Nobody in particular
Requestors: info [...] heyer-it.de
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: Problem with use Spreadsheet::ParseExcel::SaveParser;
Date: Tue, 29 Mar 2011 13:43:01 +0200
To: bug-Spreadsheet-ParseExcel [...] rt.cpan.org
From: Florian Heyer <info [...] heyer-it.de>
Download (untitled) / with headers
text/plain 2.6k
Hello, i've got the following problem with SaveParser: There are some cases where cells are blacked, e.g. the cells are filled with black and thus aren't readable (black font on black background). This is the case when viewed in Excel 2010 and LibreOffice. I'm afraid i can't provide test files as they contain sensitive information. After editing out sensitive data the bug disappears. I tracked the problem down to following code: - Spreadsheet::ParseExcel::SaveParser::Workbook::SaveAs copies foreground and background of all cells in the editied excel document - during processing get_xf() is called in Spreadsheet::WriteExcel::Format with the following code snippet (starting in line 240): # The following 2 logical statements take care of special cases in relation # to cell colours and patterns: # 1. For a solid fill (_pattern == 1) Excel reverses the role of foreground # and background colours. # 2. If the user specifies a foreground or background colour without a # pattern they probably wanted a solid fill, so we fill in the defaults. # if ($self->{_pattern} <= 0x01 and $self->{_bg_color} != 0x41 and $self->{_fg_color} == 0x40 ) { $self->{_fg_color} = $self->{_bg_color}; $self->{_bg_color} = 0x40; $self->{_pattern} = 1; } if ($self->{_pattern} <= 0x01 and $self->{_bg_color} == 0x41 and $self->{_fg_color} != 0x40 ) { $self->{_bg_color} = 0x40; $self->{_pattern} = 1; } As i unterstand it these rules are applied with direct use of Spreadsheet::WriteExcel in mind. Though with SaveParser sometimes colors are swapped because the source excel contains cells without fill pattern (_pattern == 0) but with colors set. I changed the conditions above ($self->{_pattern} <= 0x01) to ($self->{_pattern} == 0x01) and the problem disappears. As is see it when used with SaveParser the 2 rules above should be completely disabled as we want a 1:1 copy of the edited excel file. Please correct if i'm wrong. Please keep up the good work with SpreadSheet::*, i like it a lot! Best regard -- Florian Heyer - info@heyer-it.de My environment: Perl version : 5.012002 OS name : MSWin32 Module versions: (not all are required) Spreadsheet::ParseExcel 0.58 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
Download (untitled) / with headers
text/plain 157b
On Tue Mar 29 07:43:14 2011, info@heyer-it.de wrote: Show quoted text
> i've got the following problem with SaveParser:
Hi, Thanks for that, I'll look into it. John. --


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.