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: 28445
Status: resolved
Priority: 0/
Queue: Spreadsheet-ParseExcel

People
Owner: Nobody in particular
Requestors: soso [...] kol.co.nz
Cc:
AdminCc:

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



Subject: bug report
Date: Tue, 24 Jul 2007 15:16:15 +1200
To: bug-Spreadsheet-ParseExcel [...] rt.cpan.org
From: Sean <soso [...] kol.co.nz>
Download (untitled) / with headers
text/plain 667b
ParseExcel v0.32 I have an Excel column with values like 20000101, 20020925 etc $cell->Value method returns "General" (sic-verbatim) for each of these. I guess "General" is an underlying property or attribute to do with the formatting of some numeric-type cells, such as the ones in question. In other columns the method does seem to return the true value, but I have not tested with a wide range of data types. This variance is probably not intended since ParseExcel::Simple does likewise? Luckily for me $cell->{$Val} accesses the proper value itself, so I am not put out in this case. But I thought you would like to know, perhaps? regards Sean Daly
Download (untitled) / with headers
text/plain 986b
On Mon Jul 23 23:19:56 2007, soso@kol.co.nz wrote: Show quoted text
> ParseExcel v0.32 > > I have an Excel column with values like 20000101, 20020925 etc > > $cell->Value method returns "General" (sic-verbatim) for each of these. > I guess "General" is an underlying property or attribute to do with the > formatting of some numeric-type cells, such as the ones in question. In > other columns the method does seem to return the true value, but I have > not tested with a wide range of data types. > > This variance is probably not intended since ParseExcel::Simple does > likewise? > > Luckily for me $cell->{$Val} accesses the proper value itself, so I am > not put out in this case. But I thought you would like to know, perhaps? > > regards > > Sean Daly
Hi, I can't verify this with the latest release, 0.43, so it may have been resolved. Could you check? And if it hasn't been resolved could you post a small example Excel file that demonstrates the problem. Thanks, John. --
Fixed in version 0.44. 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.