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

People
Owner: Nobody in particular
Requestors: Greger.Leijonhufvud [...] intecbilling.com
Cc:
AdminCc:

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



Subject: Error in ParseExcel
Date: Wed, 5 Aug 2009 14:33:52 +0100
To: <bug-Spreadsheet-ParseExcel [...] rt.cpan.org>
From: "Greger Leijonhufvud" <Greger.Leijonhufvud [...] intecbilling.com>
Download image001.png
image/png 2.2k
image001.png
Version: 0.49 ParseExcel.pm Subroutine _subRow (lines 827-847) Problem: The following code makes an erroneous assumption: #1. RowHeight if ( $iGr & 0x20 ) { #Height = 0 $oBook->{Worksheet}[ $oBook->{_CurSheet} ]->{RowHeight}[$iR] = 0; } else { $oBook->{Worksheet}[ $oBook->{_CurSheet} ]->{RowHeight}[$iR] = $iHght / 20.0; } $iGr contains the options; value 0x20 indicates that the row is Hidden, not height. As a result, cells in hidden rows are not marked as such. On another topic: the 'Code' undef means that the data is Compressed (BIFF8), i.e. it is Unicode without the zeroes.... (I am using the OpenOffice doc of Excel file formats... http://sc.openoffice.org/excelfileformat.pdf...) Show quoted text
______________________________________________ GREGER LEIJONHUFVUD SENIOR DEVELOPMENT CONSULTANT OFFICE: +353 (0)91 501378 | MOBILE +44 (0)777 0680026 SKYPE: greger.leijonhufvud EMAIL: greger.leijonhufvud@intecbilling.com <mailto:Greger.leijonhufvud@intecbilling.com> | www.intecbilling.com P please consider the environment - do you really need to print this email? This e-mail and any attachments are confidential and may also be legally privileged and/or copyright material of Intec Telecom Systems PLC (or its affiliated companies). If you are not an intended or authorised recipient of this e-mail or have received it in error, please delete it immediately and notify the sender by e-mail. In such a case, reading, reproducing, printing or further dissemination of this e-mail or its contents is strictly prohibited and may be unlawful. Intec Telecom Systems PLC does not represent or warrant that an attachment hereto is free from computer viruses or other defects. The opinions expressed in this e-mail and any attachments may be those of the author and are not necessarily those of Intec Telecom Systems PLC.
Hi Gregor, Thanks for that, the existing code is clearly wrong. I'll look into fixing it in a future release. John. --
Hi, This issue has been fixed in version 0.54 of Spreadsheet::WriteExcel. http://cpansearch.perl.org/src/JMCNAMARA/Spreadsheet-ParseExcel-0.54/Changes Thank you for your help in identifying/fixing this issue. John. --
Subject: RE: [rt.cpan.org #48450] Resolved: Error in ParseExcel (Row Height)
Date: Thu, 27 Aug 2009 10:49:13 +0100
To: <bug-Spreadsheet-ParseExcel [...] rt.cpan.org>
From: "Greger Leijonhufvud" <Greger.Leijonhufvud [...] intecbilling.com>
Download image001.png
image/png 2.2k
image001.png
Richard, What I really wanted was to get the ‘hidden rows’ and ‘hidden columns’ fixed. I updated the source as follows: # TODO. we need to handle hidden rows: line 860 ff # $iGr & 0x20 $oBook->{Worksheet}[ $oBook->{_CurSheet} ]->{RowHidden}[$iR] = ( $iGr & 0x20 ) ? 1 : 0; $oBook->{Worksheet}[ $oBook->{_CurSheet} ]->{RowHeight}[$iR] = $iHght / 20; And (line 992 ff) # TODO. we need to handle hidden cols: $iGr & 0x01. $oBook->{Worksheet}[ $oBook->{_CurSheet} ]->{ColHidden}[$i] = ( $iGr & 0x01 ) ? 1 : 0; I can then, for each row retrieved, do for $row ($row_min .. $row_max) { …… if ($zWorksheet->{RowHidden}[$row]) { ….. Is this an OK solution, or may we run out of array space for a large spreadsheet? The XF hidden is ‘hidden formulae’, not hidden rows/columns Show quoted text
______________________________________________ GREGER LEIJONHUFVUD SENIOR DEVELOPMENT CONSULTANT OFFICE: +353 (0)91 501378 | MOBILE +44 (0)777 0680026 SKYPE: greger.leijonhufvud EMAIL: greger.leijonhufvud@intecbilling.com <mailto:Greger.leijonhufvud@intecbilling.com> | www.intecbilling.com P please consider the environment - do you really need to print this email?
-----Original Message----- From: John McNamara via RT [mailto:bug-Spreadsheet-ParseExcel@rt.cpan.org] Sent: 26 August 2009 11:16 To: Greger Leijonhufvud Subject: [rt.cpan.org #48450] Resolved: Error in ParseExcel (Row Height) <URL: https://rt.cpan.org/Ticket/Display.html?id=48450 > According to our records, your request has been resolved. If you have any further questions or concerns, please respond to this message. This e-mail and any attachments are confidential and may also be legally privileged and/or copyright material of Intec Telecom Systems PLC (or its affiliated companies). If you are not an intended or authorised recipient of this e-mail or have received it in error, please delete it immediately and notify the sender by e-mail. In such a case, reading, reproducing, printing or further dissemination of this e-mail or its contents is strictly prohibited and may be unlawful. Intec Telecom Systems PLC does not represent or warrant that an attachment hereto is free from computer viruses or other defects. The opinions expressed in this e-mail and any attachments may be those of the author and are not necessarily those of Intec Telecom Systems PLC.
On Thu Aug 27 05:49:39 2009, Greger.Leijonhufvud@intecbilling.com wrote: Show quoted text
> Richard, > > What I really wanted was to get the ‘hidden rows’ and ‘hidden columns’ > fixed.
Hi Greger, It will be fixed. Probably as part of the SaveParser refactoring. I'll let you know when that happens. John. --
Subject: RE: [rt.cpan.org #48450] Error in ParseExcel (Row Height)
Date: Thu, 27 Aug 2009 12:05:06 +0100
To: <bug-Spreadsheet-ParseExcel [...] rt.cpan.org>
From: "Greger Leijonhufvud" <Greger.Leijonhufvud [...] intecbilling.com>
John, As I'm moving jobs soon, Could you inform me at Greger@friherr.com Please? Show quoted text
______________________________________________ GREGER LEIJONHUFVUD SENIOR DEVELOPMENT CONSULTANT OFFICE: +353 (0)91 501378 | MOBILE +44 (0)777 0680026 SKYPE: greger.leijonhufvud EMAIL: greger.leijonhufvud@intecbilling.com | www.intecbilling.com  please consider the environment - do you really need to print this email?
-----Original Message----- From: John McNamara via RT [mailto:bug-Spreadsheet-ParseExcel@rt.cpan.org] Sent: 27 August 2009 11:56 To: Greger Leijonhufvud Subject: [rt.cpan.org #48450] Error in ParseExcel (Row Height) <URL: https://rt.cpan.org/Ticket/Display.html?id=48450 > On Thu Aug 27 05:49:39 2009, Greger.Leijonhufvud@intecbilling.com wrote:
> Richard, > > What I really wanted was to get the ‘hidden rows’ and ‘hidden columns’ > fixed.
Hi Greger, It will be fixed. Probably as part of the SaveParser refactoring. I'll let you know when that happens. John. -- This e-mail and any attachments are confidential and may also be legally privileged and/or copyright material of Intec Telecom Systems PLC (or its affiliated companies). If you are not an intended or authorised recipient of this e-mail or have received it in error, please delete it immediately and notify the sender by e-mail. In such a case, reading, reproducing, printing or further dissemination of this e-mail or its contents is strictly prohibited and may be unlawful. Intec Telecom Systems PLC does not represent or warrant that an attachment hereto is free from computer viruses or other defects. The opinions expressed in this e-mail and any attachments may be those of the author and are not necessarily those of Intec Telecom Systems PLC.
On Thu Aug 27 07:05:31 2009, Greger.Leijonhufvud@intecbilling.com wrote: Show quoted text
> John, > As I'm moving jobs soon, > Could you inform me at Greger@friherr.com > Please?
Hi, In that case it may be best to open up a new tracker from the other email address and mark it as a wishlist item. That way it won't be forgotten about. John. --
Subject: RE: [rt.cpan.org #48450] Error in ParseExcel (Row Height)
Date: Tue, 8 Sep 2009 15:04:51 +0100
To: <bug-Spreadsheet-ParseExcel [...] rt.cpan.org>
From: "Greger Leijonhufvud" <Greger.Leijonhufvud [...] intecbilling.com>
OK, thanks! Show quoted text
______________________________________________ GREGER LEIJONHUFVUD SENIOR DEVELOPMENT CONSULTANT OFFICE: +353 (0)91 501378 | MOBILE +44 (0)777 0680026 SKYPE: greger.leijonhufvud EMAIL: greger.leijonhufvud@intecbilling.com | www.intecbilling.com  please consider the environment - do you really need to print this email?
-----Original Message----- From: John McNamara via RT [mailto:bug-Spreadsheet-ParseExcel@rt.cpan.org] Sent: 08 September 2009 15:04 To: Greger Leijonhufvud Subject: [rt.cpan.org #48450] Error in ParseExcel (Row Height) <URL: https://rt.cpan.org/Ticket/Display.html?id=48450 > On Thu Aug 27 07:05:31 2009, Greger.Leijonhufvud@intecbilling.com wrote:
> John, > As I'm moving jobs soon, > Could you inform me at Greger@friherr.com > Please?
Hi, In that case it may be best to open up a new tracker from the other email address and mark it as a wishlist item. That way it won't be forgotten about. John. -- This e-mail and any attachments are confidential and may also be legally privileged and/or copyright material of Intec Telecom Systems PLC (or its affiliated companies). If you are not an intended or authorised recipient of this e-mail or have received it in error, please delete it immediately and notify the sender by e-mail. In such a case, reading, reproducing, printing or further dissemination of this e-mail or its contents is strictly prohibited and may be unlawful. Intec Telecom Systems PLC does not represent or warrant that an attachment hereto is free from computer viruses or other defects. The opinions expressed in this e-mail and any attachments may be those of the author and are not necessarily those of Intec Telecom Systems PLC.
On Thu Aug 27 05:49:39 2009, Greger.Leijonhufvud@intecbilling.com wrote: Show quoted text
> > What I really wanted was to get the ‘hidden rows’ and ‘hidden columns’ > fixed.
This was resolved with RT93367.