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

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

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

Subject: some column widths are truncated
Download (untitled) / with headers
text/plain 797b
Perl version : 5.014000 OS name : MSWin32 Module versions: (not all are required) Spreadsheet::ParseExcel 0.59 Scalar::Util 1.23 Unicode::Map (not installed) Spreadsheet::WriteExcel 2.37 Parse::RecDescent 1.965001 File::Temp 0.22 OLE::Storage_Lite 0.19 IO::Stringy 2.110 Excel 2003 (11.8335.8333) SP3 Problem: Some column widths are truncated. Example code: use Spreadsheet::ParseExcel::SaveParser; Spreadsheet::ParseExcel::SaveParser->new->Parse('d:\1.xls')->SaveAs('d:\2.xls'); Column Widths source->result: A: 5.14->5 B: 4.43->4.43
Subject: 1.xls
Download 1.xls
application/ 13.5k

Message body not shown because it is not plain text.

Download (untitled) / with headers
text/plain 659b
On Tue Aug 23 12:09:19 2011, chacham wrote: Show quoted text
> > Column Widths source->result: > A: 5.14->5 > B: 4.43->4.43
This is not a problem in SaveParser, but in Spreadsheet::WriteExcel. The '5.14' is making it to Spreadsheet::WriteExcel::Worksheet::_store_colinfo(), but it goes through some conversions to pixels and then to 'users units' and ends up as '1462' which shows as '5' in the spreadsheet. Adding 20 to this gives the correct '5.14' in the spreadsheet, but I'm not familiar enough with the conversion to know what's supposed to happen there. Will open a ticket on WriteExcel after checking to see if the issue is fixed already there, but am rejecting here.

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

Please report any issues with to