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: 41192
Status: resolved
Worked: 2 hours (120 min)
Priority: 0/
Queue: Spreadsheet-ParseExcel

People
Owner: Nobody in particular
Requestors: TNelson [...] manitoulintransport.com
Cc:
AdminCc:

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



Received: from la.mx.develooper.com (x1.develooper.com [63.251.223.170]) by diesel.bestpractical.com (Postfix) with SMTP id 8E1E919F0001 for <bug-Spreadsheet-ParseExcel [...] rt.cpan.org>; Mon, 24 Nov 2008 13:07:43 -0500 (EST)
Received: (qmail 28830 invoked by uid 103); 24 Nov 2008 18:07:42 -0000
Received: from x16.dev (10.0.100.26) by x1.dev with QMQP; 24 Nov 2008 18:07:42 -0000
Received: from mg.manitoulintransport.com (HELO MG.manitoulintransport.com) (209.105.199.250) by 16.mx.develooper.com (qpsmtpd/0.43rc1) with ESMTP; Mon, 24 Nov 2008 10:07:41 -0800
Received: (mail 27774 invoked from network); 24 Nov 2008 18:07:36 -0000
Received: from bambam.secure.manitoulintransport.com (HELO bambam.manitoulintransport.com) ([10.3.0.11]) (envelope-sender <TNelson [...] manitoulintransport.com>) by MG.manitoulintransport.com with SMTP for <bug-Spreadsheet-ParseExcel [...] rt.cpan.org>; 24 Nov 2008 18:07:36 -0000
Delivered-To: cpan-bug+Spreadsheet-ParseExcel [...] diesel.bestpractical.com
MIME-Version: 1.0
Subject: Possible bug with date values
X-Spam-Status: No, hits=0.0 required=8.0 tests=
Return-Path: <TNelson [...] manitoulintransport.com>
X-Mailer: Lotus Notes Release 7.0 August 18, 2005
X-Spam-Check-BY: 16.mx.develooper.com
X-Original-To: bug-Spreadsheet-ParseExcel [...] rt.cpan.org
Date: Mon, 24 Nov 2008 13:07:38 -0500
X-Spam-Level: *
X-Mimetrack: Serialize by Router on BAMBAM/Manitoulin(Release 8.0.1|February 07, 2008) at 11/24/2008 01:07:39 PM
Message-Id: <OF93AB9D4A.73DD3CF7-ON8525750B.005D9B27-8525750B.00639BB5 [...] manitoulintransport.com>
content-type: text/plain; charset="utf-8"
To: bug-Spreadsheet-ParseExcel <bug-Spreadsheet-ParseExcel [...] rt.cpan.org>
From: Taryn Nelson <TNelson [...] manitoulintransport.com>
X-RT-Original-Encoding: US-ASCII
Content-Length: 1451
Download (untitled) / with headers
text/plain 1.4k
Spreadsheet-ParseExcel-0.41 Perl v 5.8.8 for i686-linux? I'm encountering a problem when parsing an excel spreadsheet containing a date value 12:15:45 AM in one of its cells. The result of using the Value method on the cell object is -17:-59:-59 AM/PM, instead of 00:15:45 AM/PM as expected. I've tried using the Value method on a cell containing 12:15:44 AM and one containing 12:15:46 AM, and recieved the expected output. Here is the code I'm using to test this: #!usr/bin/perl use Spreadsheet::ParseExcel; use strict; my $file = '/var/www/portlets/taryn/ParseSchedule/Book1.xls'; my $excel = Spreadsheet::ParseExcel::Workbook->Parse($file); my $sheet; my $cell; foreach $sheet (@{$excel->{Worksheet}}){ $cell = $sheet->{Cells}[0][0];> print "\n"; print $cell->Value; print "\n"; $cell = $sheet->{Cells}[1][0];> print $cell->Value; print "\n"; $cell = $sheet->{Cells}[2][0];> print $cell->Value; print "\n"; } Contents of Cell[0][0] : 12:15:44 AM => results 0:15:44 AM/PM Contents of Cell[1][0] : 12:15:45 AM=> results -17:-59:-59 AM/PM Contents of Cell[2][0] : 12:15:46 AM=> results 0:15:46 AM/PM I've also been able to find some other values that give the same incorrect output: 12:14:51 AM, 12:16:39 AM I haven't tested all possible values, so others may exist.
MIME-Version: 1.0
In-Reply-To: <OF93AB9D4A.73DD3CF7-ON8525750B.005D9B27-8525750B.00639BB5 [...] manitoulintransport.com>
X-Mailer: MIME-tools 5.426 (Entity 5.426)
Content-Disposition: inline
Charset: utf8
References: <OF93AB9D4A.73DD3CF7-ON8525750B.005D9B27-8525750B.00639BB5 [...] manitoulintransport.com>
Message-Id: <rt-3.6.HEAD-24158-1227741004-1863.41192-0-0 [...] rt.cpan.org>
Content-Type: text/plain
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
Content-Length: 52
Hi, Thanks for that. I'll look into it. John, --
MIME-Version: 1.0
In-Reply-To: <OF93AB9D4A.73DD3CF7-ON8525750B.005D9B27-8525750B.00639BB5 [...] manitoulintransport.com>
X-Mailer: MIME-tools 5.427 (Entity 5.427)
Content-Disposition: inline
Charset: utf8
References: <OF93AB9D4A.73DD3CF7-ON8525750B.005D9B27-8525750B.00639BB5 [...] manitoulintransport.com>
Content-Type: text/plain
Message-ID: <rt-3.6.HEAD-29719-1232443410-38.41192-0-0 [...] rt.cpan.org>
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
Content-Length: 48
Hi, Fixed in version 0.46. 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.