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

People
Owner: jmcnamara [...] cpan.org
Requestors: jon.tankersley [...] eds.com
Cc:
AdminCc:

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



Subject: POD links for Microsoft samples for cell formatting appear to have gone bad.
The links referenced in set_num_format in the pod for support.microsoft.com/support/Excel/Content/Formats appear to have gone bad. I haven't found default.asp or codes.asp or any replacement yet. Their search page hasn't been very helpful either.
[guest - Thu Apr 21 11:01:55 2005]: Show quoted text
> The links referenced in set_num_format in the pod for > support.microsoft.com/support/Excel/Content/Formats appear to have > gone bad.
I cannot find where the links have been moved to so I will remove the links in the next version. However, if you are interested there are copies from the docs directory of the distro: http://search.cpan.org/src/JMCNAMARA/Spreadsheet-WriteExcel-2.13/doc/number_formats1.html http://search.cpan.org/src/JMCNAMARA/Spreadsheet-WriteExcel-2.13/doc/number_formats2.html John. --
From: jon.tankersley [...] eds.com
[guest - Fri Apr 22 10:18:15 2005]: No prob. I noticed those, once I was using the distribution HTML files. You might consider an additional page putting any 'user found' variations to those. I just posted one 'yyyy/mm/dd ddd' making '2005/04/21 Fri' print in the cell, etc. Show quoted text
> [guest - Thu Apr 21 11:01:55 2005]: >
> > The links referenced in set_num_format in the pod for > > support.microsoft.com/support/Excel/Content/Formats appear to have > > gone bad.
> > I cannot find where the links have been moved to so I will remove the > links in the next version. > > However, if you are interested there are copies from the docs > directory > of the distro: > > http://search.cpan.org/src/JMCNAMARA/Spreadsheet-WriteExcel- > 2.13/doc/number_formats1.html > > http://search.cpan.org/src/JMCNAMARA/Spreadsheet-WriteExcel- > 2.13/doc/number_formats2.html > > John.
Show quoted text
> You might consider an additional page putting any 'user found' > variations to those. I just posted one 'yyyy/mm/dd ddd' > making '2005/04/21 Fri' print in the cell, etc.
Spreadsheet::WriteExcel lets you use any format that Excel accepts. However, it doesn't aim to document all of the possible variations. That is what the Excel on-line help is for. :-) Another useful variation is 'yyyy/mm/dd dddd' which would give you '2005/04/21 Friday'. See also: http://office.microsoft.com/en-gb/assistance/HP051995001033.aspx John. --
From: jon.tankersley [...] eds.com
I may have missed this link in the POD.... Or maybe that link is sufficient to replace the bad links. I'd been looking for something like this. I just 'tried' the 'ddd' to get a three character day. [JMCNAMARA - Fri Apr 22 10:45:49 2005]: Show quoted text
>
> > You might consider an additional page putting any 'user found' > > variations to those. I just posted one 'yyyy/mm/dd ddd' > > making '2005/04/21 Fri' print in the cell, etc.
> > Spreadsheet::WriteExcel lets you use any format that Excel accepts. > However, it doesn't aim to document all of the possible variations.
That Show quoted text
> is what the Excel on-line help is for. :-) > > Another useful variation is 'yyyy/mm/dd dddd' which would give you > '2005/04/21 Friday'. > > See also: > > http://office.microsoft.com/en-gb/assistance/HP051995001033.aspx > > John.
Fixed in version 2.16.