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

People
Owner: Nobody in particular
Requestors: bitcard [...] ch.pkts.ca
Cc:
AdminCc:

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



Subject: Rewriting a spreadsheet turns numbers(general format) into text format
I wrote a program that opens an existing Excel file and writes a new Excel file. For some reason, the format of the cells is changed from General to Text. This messes up the appearance of the spreadsheet, especially for numbers with more than a few significant digits. Attached to this message are three files: test2 -- an extremely short program that demonstrates the problem test2-in.xls -- a very small spreadsheet test2.xls -- the output of the program The entire program consists of: ----- my $parser = new Spreadsheet::ParseExcel::SaveParser; my $excel = $parser->Parse($INFILE); $excel->SaveAs($OUTFILE); ----- This is perl 5.8.8 on Fedora 8 linux. Spreadsheet::WriteExcel version 2.18. Other than that, fine program!
Subject: test2-in.xls
Download test2-in.xls
application/vnd.ms-excel 7.5k

Message body not shown because it is not plain text.

Subject: test2.xls
Download test2.xls
application/vnd.ms-excel 5.5k

Message body not shown because it is not plain text.

Subject: test2
Download test2
application/octet-stream 326b

Message body not shown because it is not plain text.

From: bitcard [...] ch.pkts.ca
This test file was created with Gnumeric, but this happens with files created by Excel as well.
This issue appears to have been fixed in version 0.44 or perhaps an earlier version. At least the example program you provided now produces the correct results. Thanks, John. --