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: 20526
Status: resolved
Worked: 3 hours (180 min)
Priority: 0/
Queue: Spreadsheet-ParseExcel

People
Owner: Nobody in particular
Requestors: brayst [...] uk.ibm.com
Cc:
AdminCc:

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



CC: kwitknr [...] cpan.org
Subject: Bugs in Spreadsheet-ParseExcel-0.2603
Date: Tue, 18 Jul 2006 11:51:09 +0100
To: bug-Spreadsheet-ParseExcel [...] rt.cpan.org
From: Steven Bray <BRAYST [...] uk.ibm.com>
Download (untitled) / with headers
text/plain 854b
Dear Kawai Takanori, I'm using Microsoft Excel 2000 SR-1 on Windows 2000 SP4. I've got some cells where the value is not interpreted correctly. Here are two examples, showing what is in the spreadsheet and then what Spreadsheet-ParseExcel puts in the cell attributes: 1. Value: 09/06/2006 Format: Custom, dd/mm/yyyy $cell->Value: 09/MM/2006 $cell->{Val}: 38877 $cell->{Type}: Numeric 2. Value: 30.62 Format: Custom, #,##0.00[$%-809] $cell->Value: 3,062.00[$%0809] $cell->{Val}: 30.62 $cell->{Type}: Numeric 3. One more thing. The documentation for Spreadsheet::ParseExcel says: Cell class has these properties: Value Val Type It doesn't explain that you have to put curly brackets around the Val and Type properties. Thanks very much. Steven Bray.
Download (untitled) / with headers
text/plain 1.2k
On Tue Jul 18 06:49:57 2006, brayst@uk.ibm.com wrote: Show quoted text
> > Dear Kawai Takanori, > > I'm using Microsoft Excel 2000 SR-1 on Windows 2000 SP4. > > I've got some cells where the value is not interpreted correctly. > Here are two examples, showing what is in the spreadsheet and then > what Spreadsheet-ParseExcel puts in the cell attributes: > > 1. Value: 09/06/2006 > Format: Custom, dd/mm/yyyy > > $cell->Value: 09/MM/2006 > $cell->{Val}: 38877 > $cell->{Type}: Numeric > > > 2. Value: 30.62 > Format: Custom, #,##0.00[$%-809] > > $cell->Value: 3,062.00[$%0809] > $cell->{Val}: 30.62 > $cell->{Type}: Numeric > > 3. One more thing. The documentation for Spreadsheet::ParseExcel says: > > Cell class has these properties: > Value > Val > Type > > It doesn't explain that you have to put curly brackets around the > Val and Type properties. > > Thanks very much. > Steven Bray. >
Hi Steven, do you happen to have a small example Excel file and the relevant script that would trigger this problem? If yes, please send them to me so I can add them to the regression tests of the module. thanks Gabor Szabo <szabgab@gmail.com>
Subject: Wrong Data-Type for Date-Cells
From: cpan [...] tobias-tacke.de
Download (untitled) / with headers
text/plain 595b
Hi, I'can reproduce this bug with GNumeric v1.7.8 and OpenOffice v2.2. under Ubuntu v7.04. Here is a small example. Coloumn "Two" contain dates, but in perl you only get "Text" as type. If I open this file in MS-Excel (the date is correct there) and save it, then the type for dates are correct. Regards Tobiwan Show quoted text
> Hi Steven, > > do you happen to have a small example Excel file and the relevant > script that would trigger this problem? If yes, please send them to > me so I can add them to the regression tests of the module. > > thanks > Gabor Szabo <szabgab@gmail.com> > >
Download date_example.xls
application/vnd.ms-excel 5.5k

Message body not shown because it is not plain text.

Subject: Details für the date-bug
Download (untitled) / with headers
text/plain 133b
Sorry, I forgot some details: If I get the $cell I can ask for {Type} and {Val}. Type is "Numeric" and Val is "33911" for example.
Hi, This issue has been fixed in Spreadsheet::ParseExcel version 0.48. Thanks, 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.