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: 48831
Status: resolved
Worked: 1 hour (60 min)
Priority: 0/
Queue: Spreadsheet-ParseExcel

People
Owner: Nobody in particular
Requestors: alan [...] alanjames.org
Cc:
AdminCc:

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



Subject: Invalid date causes hang
Date: Wed, 19 Aug 2009 13:46:51 +0100
To: bug-Spreadsheet-ParseExcel [...] rt.cpan.org
From: Alan James <alan [...] alanjames.org>
Download (untitled) / with headers
text/plain 590b
I'm often given excel files containing product lists and people format the cells containing barcodes in various ways in order to stop Excel from treating them like numbers (removal of leading zeroes, scientific format etc). In this case I was given a file where the barcodes were formatted as dd/mm/yyyy dates. In Excel a barcode like 4030433048023 would be displayed as text, since it cant be converted to a sensible date. Workbook->Parse hangs when it encounters one of these cells. I've attached an example file that demonstrates the problem. Spreadsheet-ParseExcel v0.46 Perl v5.10.0
Download Book1.xls
application/vnd.ms-excel 13.5k

Message body not shown because it is not plain text.

Download (untitled) / with headers
text/plain 495b
On Wed Aug 19 08:47:37 2009, alan@alanjames.org wrote: Show quoted text
> In this case I was given a file where the barcodes were > formatted as dd/mm/yyyy dates. In Excel a barcode like 4030433048023 > would be displayed as text, since it cant be converted to a sensible > date.
Hi, It seems to be stuck recursively performing the same formatting operation. The fix is fairly easy in the case of dates. I'll put it in the next release (0.51). Thanks for the clear bug report and example file. John. --
Download (untitled) / with headers
text/plain 224b
Hi, This issue has been fixed in version 0.51 of Spreadsheet::WriteExcel. http://cpansearch.perl.org/src/JMCNAMARA/Spreadsheet-ParseExcel-0.51/Changes Thank you for your help in identifying/fixing this issue. 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.