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(

    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;


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:

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

Owner: Nobody in particular
Requestors: netz [...]

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

Subject: prerequisite Jcode
Date: Fri, 16 Feb 2007 11:25:22 +0100
To: bug-Spreadsheet-ParseExcel [...]
From: Steffen Netz <netz [...]>
Download (untitled) / with headers
text/plain 716b
Please include prereq: Jcode in your Makefile.PL Solaris 5.8 perl v5.8.3 Txs, Steffen -- -------------------------------------------------------------------- | Fraunhofer Institut Photonische Microsysteme | | | | Fraunhofer Institute for Photonic Microsystems ( Germany ) | | | | Steffen Netz | phone : ( +49 ) (0)351/8823-212 | | Maria-Reiche-Str. 2 | fax : ( +49 ) (0)351/8823-266 | | 01109 Dresden | email : | --------------------------------------------------------------------
Download (untitled) / with headers
text/plain 323b
On Fri Feb 16 05:26:03 2007, wrote: Show quoted text
> > > Please include prereq: Jcode > in your Makefile.PL > > > Solaris 5.8 > perl v5.8.3 > > Txs, > Steffen
This is not really a prereq just one of the tests needed it. Since v0.29 we try to skip tests that need additional modules such as Jcode. Gabor

This service is sponsored and maintained by Best Practical Solutions and runs on infrastructure.

Please report any issues with to