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

People
Owner: Nobody in particular
Requestors: guillaume.yziquel [...] citycable.ch
Cc:
AdminCc:

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



MIME-Version: 1.0
In-Reply-To: <49B66438.2090904 [...] yziquel.homelinux.org>
X-Spam-Status: No, hits=0.0 required=8.0 tests=
References: <OFAFE4CFB4.FF8ADB9D-ONC1257574.006D6802-C1257574.006DB216 [...] swissre.com> <49B66438.2090904 [...] yziquel.homelinux.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Reply-To: guillaume.yziquel [...] citycable.ch
Message-ID: <4A608C65.4040308 [...] citycable.ch>
Received: from la.mx.develooper.com (x1.develooper.com [207.171.7.70]) by diesel.bestpractical.com (Postfix) with SMTP id BE1074D8127 for <bug-Spreadsheet-ParseExcel [...] rt.cpan.org>; Fri, 17 Jul 2009 10:40:26 -0400 (EDT)
Received: (qmail 14477 invoked by uid 103); 17 Jul 2009 14:40:26 -0000
Received: from x16.dev (10.0.100.26) by x1.dev with QMQP; 17 Jul 2009 14:40:26 -0000
Received: from emailfrontal2.citycable.ch (HELO emailfrontal2.citycable.ch) (85.218.0.121) by 16.mx.develooper.com (qpsmtpd/0.80) with SMTP; Fri, 17 Jul 2009 07:40:19 -0700
Received: from localhost (emailfrontal2.citycable.ch [127.0.0.1]) by emailfrontal2.citycable.ch (Postfix) with ESMTP id 2F5E88343E1 for <bug-Spreadsheet-ParseExcel [...] rt.cpan.org>; Fri, 17 Jul 2009 16:40:11 +0200 (CEST)
Received: from [192.168.0.10] (unknown [85.218.98.58]) (Authenticated sender: guillaume.yziquel [...] citycable.ch) by emailfrontal2.citycable.ch (Postfix) with ESMTPA id 90C01834344; Fri, 17 Jul 2009 16:40:09 +0200 (CEST)
Delivered-To: cpan-bug+Spreadsheet-ParseExcel [...] diesel.bestpractical.com
User-Agent: Mozilla-Thunderbird 2.0.0.19 (X11/20090103)
Subject: Cannot parse password-protected Excel files.
Return-Path: <guillaume.yziquel [...] citycable.ch>
X-Original-To: bug-Spreadsheet-ParseExcel [...] rt.cpan.org
X-Spam-Check-BY: 16.mx.develooper.com
Date: Fri, 17 Jul 2009 16:36:21 +0200
X-Spam-Level: *
To: bug-Spreadsheet-ParseExcel [...] rt.cpan.org
Content-Transfer-Encoding: 7bit
From: Guillaume Yziquel <guillaume.yziquel [...] citycable.ch>
X-RT-Original-Encoding: utf-8
Content-Length: 541
Download (untitled) / with headers
text/plain 541b
Hello. I have tried to use Spreadsheet::ParseExcel to parse password-protected Excel files. The module was unable to parse the spreadsheet. Unfortunately, I am not allowed to give out the spreadsheet, and I do not have Excel to make a password-protected file. By password-protected, I mean that I can read the file in OpenOffice, but not write to the file. Spreadsheet::ParseExcel version: 0.4900 perl -v: perl, v5.10.0 built for x86_64-linux-gnu-thread-multi x86_64 GNU/Linux, Debian distribution. All the best, Guillaume Yziquel.
MIME-Version: 1.0
In-Reply-To: <4A608C65.4040308 [...] citycable.ch>
X-Mailer: MIME-tools 5.427 (Entity 5.427)
Content-Disposition: inline
Charset: utf8
References: <OFAFE4CFB4.FF8ADB9D-ONC1257574.006D6802-C1257574.006DB216 [...] swissre.com> <49B66438.2090904 [...] yziquel.homelinux.org> <4A608C65.4040308 [...] citycable.ch>
Content-Type: text/plain
Message-ID: <rt-3.6.HEAD-26882-1249517206-578.47978-0-0 [...] rt.cpan.org>
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
Content-Length: 485
Download (untitled) / with headers
text/plain 485b
On Fri Jul 17 10:40:45 2009, guillaume.yziquel@citycable.ch wrote: Show quoted text
> Hello. > > I have tried to use Spreadsheet::ParseExcel to parse password-protected > Excel files. The module was unable to parse the spreadsheet.
Hi Guillaume, Password protected files cannot be parsed by WriteExcel. A future release will indicate that the file in password protected and return an appropriate error code but it is unlikely that the module will ever be able to read protected files. John. --
MIME-Version: 1.0
In-Reply-To: <4A608C65.4040308 [...] citycable.ch>
X-Mailer: MIME-tools 5.427 (Entity 5.427)
Content-Disposition: inline
Charset: utf8
References: <OFAFE4CFB4.FF8ADB9D-ONC1257574.006D6802-C1257574.006DB216 [...] swissre.com> <49B66438.2090904 [...] yziquel.homelinux.org> <4A608C65.4040308 [...] citycable.ch>
Content-Type: text/plain
Message-ID: <rt-3.6.HEAD-26882-1249517207-693.47978-0-0 [...] rt.cpan.org>
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
Content-Length: 485
Download (untitled) / with headers
text/plain 485b
On Fri Jul 17 10:40:45 2009, guillaume.yziquel@citycable.ch wrote: Show quoted text
> Hello. > > I have tried to use Spreadsheet::ParseExcel to parse password-protected > Excel files. The module was unable to parse the spreadsheet.
Hi Guillaume, Password protected files cannot be parsed by WriteExcel. A future release will indicate that the file in password protected and return an appropriate error code but it is unlikely that the module will ever be able to read protected files. John. --
MIME-Version: 1.0
X-Spam-Status: No, hits=0.0 required=8.0 tests=
In-Reply-To: <rt-3.6.HEAD-26882-1249517207-693.47978-6-0 [...] rt.cpan.org>
References: <RT-Ticket-47978 [...] rt.cpan.org> <OFAFE4CFB4.FF8ADB9D-ONC1257574.006D6802-C1257574.006DB216 [...] swissre.com> <49B66438.2090904 [...] yziquel.homelinux.org> <4A608C65.4040308 [...] citycable.ch> <rt-3.6.HEAD-26882-1249517207-693.47978-6-0 [...] rt.cpan.org>
Message-ID: <4AA5FA4A.2010207 [...] citycable.ch>
Reply-To: guillaume.yziquel [...] citycable.ch
Content-Type: text/plain; charset=UTF-8; format=flowed
X-RT-Original-Encoding: utf-8
Received: from la.mx.develooper.com (x1.develooper.com [207.171.7.70]) by diesel.bestpractical.com (Postfix) with SMTP id 6015019B81D7 for <bug-Spreadsheet-ParseExcel [...] rt.cpan.org>; Tue, 8 Sep 2009 02:36:34 -0400 (EDT)
Received: (qmail 24310 invoked by uid 103); 8 Sep 2009 06:36:33 -0000
Received: from x16.dev (10.0.100.26) by x1.dev with QMQP; 8 Sep 2009 06:36:33 -0000
Received: from emailfrontal2.citycable.ch (HELO emailfrontal2.citycable.ch) (85.218.0.121) by 16.mx.develooper.com (qpsmtpd/0.80) with SMTP; Mon, 07 Sep 2009 23:36:27 -0700
Received: from [192.168.0.10] (unknown [85.218.92.99]) (Authenticated sender: guillaume.yziquel [...] citycable.ch) by emailfrontal2.citycable.ch (Postfix) with ESMTPA id 57498834319; Tue, 8 Sep 2009 08:36:08 +0200 (CEST)
Delivered-To: cpan-bug+Spreadsheet-ParseExcel [...] diesel.bestpractical.com
Subject: Re: [rt.cpan.org #47978] Cannot parse password-protected Excel files.
User-Agent: Mozilla-Thunderbird 2.0.0.19 (X11/20090103)
Return-Path: <guillaume.yziquel [...] citycable.ch>
X-Spam-Check-BY: 16.mx.develooper.com
X-Original-To: bug-Spreadsheet-ParseExcel [...] rt.cpan.org
Date: Tue, 08 Sep 2009 08:31:38 +0200
X-Spam-Level: *
To: bug-Spreadsheet-ParseExcel [...] rt.cpan.org
Content-Transfer-Encoding: quoted-printable
From: Guillaume Yziquel <guillaume.yziquel [...] citycable.ch>
RT-Message-ID: <rt-3.6.HEAD-27252-1252391803-246.47978-0-0 [...] rt.cpan.org>
Content-Length: 911
Download (untitled) / with headers
text/plain 911b
John McNamara via RT a écrit : Show quoted text
> <URL: https://rt.cpan.org/Ticket/Display.html?id=47978 > > > On Fri Jul 17 10:40:45 2009, guillaume.yziquel@citycable.ch wrote:
>> Hello. >> >> I have tried to use Spreadsheet::ParseExcel to parse password-protected >> Excel files. The module was unable to parse the spreadsheet.
> > Hi Guillaume, > > Password protected files cannot be parsed by WriteExcel. > > A future release will indicate that the file in password protected and return an appropriate > error code but it is unlikely that the module will ever be able to read protected files. > > John.
Hello. Thank you for your answer. Just to be sure that we're talking about the same thing: I'm simply concerned about reading with ParseExcel. Not about WriteExcel. By the way, what is the reason behind this 'unlikely'? Just to know. All the best, -- Guillaume Yziquel http://yziquel.homelinux.org/
MIME-Version: 1.0
In-Reply-To: <rt-3.6.HEAD-27252-1252391803-246.47978-0-0 [...] rt.cpan.org>
X-Mailer: MIME-tools 5.427 (Entity 5.427)
Content-Disposition: inline
Charset: utf8
References: <RT-Ticket-47978 [...] rt.cpan.org> <OFAFE4CFB4.FF8ADB9D-ONC1257574.006D6802-C1257574.006DB216 [...] swissre.com> <49B66438.2090904 [...] yziquel.homelinux.org> <4A608C65.4040308 [...] citycable.ch> <rt-3.6.HEAD-26882-1249517207-693.47978-6-0 [...] rt.cpan.org> <4AA5FA4A.2010207 [...] citycable.ch> <rt-3.6.HEAD-27252-1252391803-246.47978-0-0 [...] rt.cpan.org>
Content-Type: text/plain
Message-ID: <rt-3.6.HEAD-27252-1252418350-686.47978-0-0 [...] rt.cpan.org>
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
Content-Length: 1060
On Tue Sep 08 02:36:43 2009, guillaume.yziquel@citycable.ch wrote: Show quoted text
> > Thank you for your answer. Just to be sure that we're talking about > the > same thing: I'm simply concerned about reading with ParseExcel. Not > about WriteExcel.
Hi Guillaume, WriteExcel was a typo due to muscle memory. I am the author of that module and the maintainer of ParseExcel. Show quoted text
> By the way, what is the reason behind this 'unlikely'? Just to know.
It probably would be possible to decrypt the input Excel file if the user supplied the password. At least for some of the Excel encryption schemes. It may also be possible to read weakly (XOR) encrypted Excel files without a password. However, there is a reasonable amount of technical difficulty associated with this as well as a the time required to implement and test the feature. In addition, it isn't a frequently requested feature. At the moment there are more pressing, and far more basic, issues that need to be resolved in ParseExcel. So for those reasons, I would say that it is unlikely. John. --
MIME-Version: 1.0
X-Spam-Status: No, hits=0.0 required=8.0 tests=
In-Reply-To: <rt-3.6.HEAD-27252-1252418350-686.47978-6-0 [...] rt.cpan.org>
References: <RT-Ticket-47978 [...] rt.cpan.org> <OFAFE4CFB4.FF8ADB9D-ONC1257574.006D6802-C1257574.006DB216 [...] swissre.com> <49B66438.2090904 [...] yziquel.homelinux.org> <4A608C65.4040308 [...] citycable.ch> <rt-3.6.HEAD-26882-1249517207-693.47978-6-0 [...] rt.cpan.org> <4AA5FA4A.2010207 [...] citycable.ch> <rt-3.6.HEAD-27252-1252391803-246.47978-6-0 [...] rt.cpan.org> <rt-3.6.HEAD-27252-1252418350-686.47978-6-0 [...] rt.cpan.org>
Message-ID: <4AA95467.2000205 [...] citycable.ch>
Reply-To: guillaume.yziquel [...] citycable.ch
Content-Type: text/plain; charset=UTF-8; format=flowed
X-RT-Original-Encoding: utf-8
Received: from la.mx.develooper.com (x1.develooper.com [207.171.7.70]) by diesel.bestpractical.com (Postfix) with SMTP id 192F119B8274 for <bug-Spreadsheet-ParseExcel [...] rt.cpan.org>; Thu, 10 Sep 2009 15:38:05 -0400 (EDT)
Received: (qmail 27859 invoked by uid 103); 10 Sep 2009 19:38:05 -0000
Received: from x16.dev (10.0.100.26) by x1.dev with QMQP; 10 Sep 2009 19:38:05 -0000
Received: from emailfrontal1.citycable.ch (HELO emailfrontal1.citycable.ch) (85.218.0.120) by 16.mx.develooper.com (qpsmtpd/0.80) with SMTP; Thu, 10 Sep 2009 12:37:59 -0700
Received: from [192.168.0.10] (unknown [85.218.92.99]) (Authenticated sender: guillaume.yziquel [...] citycable.ch) by emailfrontal1.citycable.ch (Postfix) with ESMTPA id 4D9B512C2C5; Thu, 10 Sep 2009 21:37:43 +0200 (CEST)
Delivered-To: cpan-bug+Spreadsheet-ParseExcel [...] diesel.bestpractical.com
Subject: Re: [rt.cpan.org #47978] Cannot parse password-protected Excel files.
User-Agent: Mozilla-Thunderbird 2.0.0.19 (X11/20090103)
Return-Path: <guillaume.yziquel [...] citycable.ch>
X-Spam-Check-BY: 16.mx.develooper.com
X-Original-To: bug-Spreadsheet-ParseExcel [...] rt.cpan.org
Date: Thu, 10 Sep 2009 21:32:55 +0200
X-Spam-Level: *
To: bug-Spreadsheet-ParseExcel [...] rt.cpan.org
Content-Transfer-Encoding: quoted-printable
From: Guillaume Yziquel <guillaume.yziquel [...] citycable.ch>
RT-Message-ID: <rt-3.6.HEAD-27252-1252611498-1632.47978-0-0 [...] rt.cpan.org>
Content-Length: 1303
Download (untitled) / with headers
text/plain 1.2k
John McNamara via RT a écrit : Show quoted text
> > Hi Guillaume, > > WriteExcel was a typo due to muscle memory. I am the author of that > module and the maintainer of ParseExcel. >
>> By the way, what is the reason behind this 'unlikely'? Just to know.
> > It probably would be possible to decrypt the input Excel file if the > user supplied the password. At least for some of the Excel encryption > schemes. It may also be possible to read weakly (XOR) encrypted Excel > files without a password.
OK. My issue was much simpler: It was a password protected file that forbid people to modify areas on the sheets. But one could read them transparentyl in, say, OpenOffice.org. The encryption wasn't meant to stop the worksheet from being read. At all... and that's why I was disappointed with ParseExcel on this specific issue. Show quoted text
> However, there is a reasonable amount of technical difficulty associated > with this as well as a the time required to implement and test the feature. > > In addition, it isn't a frequently requested feature. At the moment > there are more pressing, and far more basic, issues that need to be > resolved in ParseExcel.
OK. Show quoted text
> So for those reasons, I would say that it is unlikely. > > John.
Thanks for your work. -- Guillaume Yziquel http://yziquel.homelinux.org/
MIME-Version: 1.0
In-Reply-To: <rt-3.6.HEAD-27252-1252611498-1632.47978-0-0 [...] rt.cpan.org>
X-Mailer: MIME-tools 5.427 (Entity 5.427)
Content-Disposition: inline
Charset: utf8
References: <RT-Ticket-47978 [...] rt.cpan.org> <OFAFE4CFB4.FF8ADB9D-ONC1257574.006D6802-C1257574.006DB216 [...] swissre.com> <49B66438.2090904 [...] yziquel.homelinux.org> <4A608C65.4040308 [...] citycable.ch> <rt-3.6.HEAD-26882-1249517207-693.47978-6-0 [...] rt.cpan.org> <4AA5FA4A.2010207 [...] citycable.ch> <rt-3.6.HEAD-27252-1252391803-246.47978-6-0 [...] rt.cpan.org> <rt-3.6.HEAD-27252-1252418350-686.47978-6-0 [...] rt.cpan.org> <4AA95467.2000205 [...] citycable.ch> <rt-3.6.HEAD-27252-1252611498-1632.47978-0-0 [...] rt.cpan.org>
Content-Type: text/plain
Message-ID: <rt-3.6.HEAD-27252-1252678743-1304.47978-0-0 [...] rt.cpan.org>
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
Content-Length: 516
Download (untitled) / with headers
text/plain 516b
On Thu Sep 10 15:38:18 2009, guillaume.yziquel@citycable.ch wrote: Show quoted text
> > OK. My issue was much simpler: It was a password protected file that > forbid people to modify areas on the sheets. But one could read them > transparentyl in, say, OpenOffice.org.
Hi Guillaume, Hmm, ParseExcel should be able to read files like that. Could you send me an example file? Send it to the email address in the docs. If it contains sensitive data you can delete it. Just leave enough data to demonstrate the problem. John. --
MIME-Version: 1.0
In-Reply-To: <4A608C65.4040308 [...] citycable.ch>
X-Mailer: MIME-tools 5.427 (Entity 5.427)
Content-Disposition: inline
Charset: utf8
References: <OFAFE4CFB4.FF8ADB9D-ONC1257574.006D6802-C1257574.006DB216 [...] swissre.com> <49B66438.2090904 [...] yziquel.homelinux.org> <4A608C65.4040308 [...] citycable.ch>
Content-Type: text/plain
Message-ID: <rt-3.6.HEAD-9877-1260449810-547.47978-0-0 [...] rt.cpan.org>
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
Content-Length: 416
Download (untitled) / with headers
text/plain 416b
As of version 0.56 you can now trap parse errors as follows: my $parser = Spreadsheet::ParseExcel->new(); my $workbook = $parser->parse('Book1.xls'); if ( !defined $workbook ) { die $parser->error(), ".\n"; } This will allow you to check for encrypted files. It won't let you read them however. Parsing an encrypted Excel is beyond the current scope of Spreadsheet::ParseExcel. 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.