Skip Menu |

This queue is for tickets about the Spreadsheet-WriteExcel CPAN distribution.

Maintainer(s)' notes

If you are reporting a bug in Spreadsheet::WriteExcel 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::WriteExcel
                      Parse::RecDescent
                      File::Temp
                      OLE::Storage_Lite
                      IO::Stringy
                      Spreadsheet::ParseExcel
                      Scalar::Util
                      Unicode::Map
                    );

    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::WriteExcel (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 but complete example program that demonstrates your problem. The program should be as small as possible. At the same time it should be a complete program that generates an Excel file. If the Spreadsheet::WriteExcel section is part of a much larger program then simplify it down to the essentials. Simulate any DB reads with an array.

5) Say if you tested with Excel, OpenOffice, Gnumeric or something else. Say which version of that application you used.

6) If you are submitting a patch you should check with the author 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::WriteExcel Google Group.

Report information
The Basics
Id: 104685
Status: resolved
Priority: 0/
Queue: Spreadsheet-WriteExcel

People
Owner: Nobody in particular
Requestors: binarin [...] yandex-team.ru
Cc:
AdminCc:

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



Subject: write_url() with undef's for url/description results in somewhat bad .xls
Date: Mon, 25 May 2015 15:14:59 +0300
To: bug-Spreadsheet-WriteExcel [...] rt.cpan.org
From: Alexey Lebedeff <binarin [...] yandex-team.ru>

Message body is not shown because sender requested not to inline it.

Hi. Spreadsheet::WriteExcel 2.40 File produced by attached script can be successfuly read by all programs, but when I'm trying to re-save it using Microsoft Office 2010 Excel, the message about corrupted file is being displayed. Saving of the file becomes possible after deletion of offending cell. And while such usage of write_url() is definitely incorrect, module should not produce broken xls file even in this case. Version information Perl version : 5.020002 OS name : linux Module versions: (not all are required) Spreadsheet::WriteExcel 2.40 Parse::RecDescent 1.967009 File::Temp 0.2304 OLE::Storage_Lite 0.19 IO::Stringy 2.110 Spreadsheet::ParseExcel (not installed) Scalar::Util 1.38 Unicode::Map (not installed) Best, Alexey.
Spreadsheet::WriteExcel is deprecated in favour of Excel::Writer::XLSX: http://search.cpan.org/dist/Spreadsheet-WriteExcel/lib/Spreadsheet/WriteExcel.pm#Migrating_to_Excel::Writer::XLSX For cases like this the end user should santise their data. As you say undef isn't a valid url. For both of these reasons this is a "won't fix".