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: 62073
Status: resolved
Priority: 0/
Queue: Spreadsheet-ParseExcel
People
Owner: Nobody in particular
Requestors: j.novak [...] netsystem.cz
Cc:
AdminCc:
Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)
Attachments
x.pl
x.xls

History Show all quoted text
  Tue Oct 12 07:41:17 2010 j.novak [...] netsystem.cz - Ticket created
Subject: Apostrophe issue in cell
Date: Tue, 12 Oct 2010 13:40:53 +0200
To: bug-Spreadsheet-ParseExcel [...] rt.cpan.org
From: Jirka Novak <j.novak [...] netsystem.cz>
Hi, I found problem with processing cell where apostrophe is used to mark cell as text. It looks similar to http://rt.cpan.org/Public/Bug/Display.html?id=61299, but version 0.58 om module doesn't solve my problem. I attached sample x.xls file to demonstrate it. File was extracted from larger file where I found the problem. File was edited in MS Excel and OpenOffice Calc. There are two cells with text "100065". First one has format Date, but it is written as "'100065" so spreadsheet shows it as string. Second one is same text and format of cell is Text. When I use Spreadsheet::ParseExcel in latest version 0.58, I see, that first cell is parsed as date and I get value "18.12.2173". Second one is processed correctly and I get value "100065". I made small program to demonstrate it (it is attached - x.pl). I tried to find the problem in code (ParseExcel.pm). I checked solution used in bug 61299 - it is based on Lotus123 flag ($i123). But this flag is not set in my file. So I don't know how MS Excel/OO Calc recognize that cell should be showed as text. Can any one help? Sincerely yours, Jirka Novak Summary of my perl5 (revision 5 version 10 subversion 1) configuration: Platform: osname=linux, osvers=2.6.32-44.1.el6.x86_64, archname=x86_64-linux-thread-multi uname='linux x86-04.phx2.fedoraproject.org 2.6.32-44.1.el6.x86_64 #1 smp wed jul 14 18:51:29 edt 2010 x86_64 x86_64 x86_64 gnulinux ' config_args='-des -Doptimize=-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -Dccdlflags=-Wl,--enable-new-dtags -DDEBUGGING=-g -Dversion=5.10.1 -Dmyhostname=localhost -Dperladmin=root@localhost -Dcc=gcc -Dcf_by=Red Hat, Inc. -Dprefix=/usr -Dvendorprefix=/usr -Dsiteprefix=/usr/local -Dsitelib=/usr/local/share/perl5 -Dsitearch=/usr/local/lib64/perl5 -Dprivlib=/usr/share/perl5 -Dvendorlib=/usr/share/perl5 -Darchlib=/usr/lib64/perl5 -Dvendorarch=/usr/lib64/perl5 -Dinc_version_list=5.10.0 -Darchname=x86_64-linux-thread-multi -Dlibpth=/usr/local/lib64 /lib64 /usr/lib64 -Duseshrplib -Dusethreads -Duseithreads -Duselargefiles -Dd_dosuid -Dd_semctl_semun -Di_db -Ui_ndbm -Di_gdbm -Di_shadow -Di_syslog -Dman3ext=3pm -Duseperlio -Dinstallusrbinperl=n -Ubincompat5005 -Uversiononly -Dpager=/usr/bin/less -isr -Dd_gethostent_r_proto -Ud_endhostent_r_proto -Ud_sethostent_r_proto -Ud_endprotoent_r_proto -Ud_setprotoent_r_proto -Ud_endservent_r_proto -Ud_setservent_r_proto -Dscriptdir=/usr/bin -Dotherlibdirs=/usr/local/lib64/perl5/site_perl/5.10.0/x86_64-linux-thread-multi:/usr/local/lib/perl5/site_perl/5.10.0:/usr/lib64/perl5/vendor_perl/5.10.0/x86_64-linux-thread-multi:/usr/lib/perl5/vendor_perl:/usr/lib/perl5/site_perl' hint=recommended, useposix=true, d_sigaction=define useithreads=define, usemultiplicity=define useperlio=define, d_sfio=undef, uselargefiles=define, usesocks=undef use64bitint=define, use64bitall=define, uselongdouble=undef usemymalloc=n, bincompat5005=undef Compiler: cc='gcc', ccflags ='-D_REENTRANT -D_GNU_SOURCE -fno-strict-aliasing -pipe -fstack-protector -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64', optimize='-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic', cppflags='-D_REENTRANT -D_GNU_SOURCE -fno-strict-aliasing -pipe -fstack-protector -I/usr/local/include' ccversion='', gccversion='4.4.4 20100630 (Red Hat 4.4.4-10)', gccosandvers='' intsize=4, longsize=8, ptrsize=8, doublesize=8, byteorder=12345678 d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=16 ivtype='long', ivsize=8, nvtype='double', nvsize=8, Off_t='off_t', lseeksize=8 alignbytes=8, prototype=define Linker and Libraries: ld='gcc', ldflags =' -fstack-protector' libpth=/usr/local/lib64 /lib64 /usr/lib64 libs=-lresolv -lnsl -lgdbm -ldb -ldl -lm -lcrypt -lutil -lpthread -lc perllibs=-lresolv -lnsl -ldl -lm -lcrypt -lutil -lpthread -lc libc=, so=so, useshrplib=true, libperl=libperl.so gnulibc_version='2.12' Dynamic Linking: dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags='-Wl,--enable-new-dtags -Wl,-rpath,/usr/lib64/perl5/CORE' cccdlflags='-fPIC', lddlflags='-shared -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic' Characteristics of this binary (from libperl): Compile-time options: MULTIPLICITY PERL_DONT_CREATE_GVSV PERL_IMPLICIT_CONTEXT PERL_MALLOC_WRAP USE_64_BIT_ALL USE_64_BIT_INT USE_ITHREADS USE_LARGE_FILES USE_PERLIO USE_REENTRANT_API Built under linux Compiled at Sep 7 2010 12:15:40 @INC: /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5 /usr/share/perl5 /usr/lib64/perl5 /usr/share/perl5 /usr/local/lib64/perl5/site_perl/5.10.0/x86_64-linux-thread-multi /usr/local/lib/perl5/site_perl/5.10.0 /usr/lib64/perl5/vendor_perl/5.10.0/x86_64-linux-thread-multi /usr/lib/perl5/vendor_perl/5.10.0 /usr/lib/perl5/vendor_perl /usr/lib/perl5/site_perl .

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

Download x.xls
application/vnd.ms-excel 6k

Message body not shown because it is not plain text.

  Tue Oct 12 08:32:38 2010 jmcnamara [...] cpan.org - Correspondence added
Hi, Thanks for the detailed bug report. I'll take a look at the issue and let you know. John. --
  Tue Oct 12 08:32:38 2010 The RT System itself - Status changed from 'new' to 'open'
  Tue Oct 12 19:07:51 2010 jmcnamara [...] cpan.org - Correspondence added
Hi, The problem appears to be that the cell contained a string that looked like a number and also contained a numeric format so ParseExcel formatted it as a number. This behaviour isn't consistent with Excel which leaves the string as a string until it is edited by the user when it then converts it to a number. I've changed the way that ParseExcel handles these cases to reflect Excel's behaviour. You can try it out the changes from GitHub: http://github.com/jmcnamara/spreadsheet-parseexcel Let me know how you get on and if you encounter any other issues. John. --
  Wed Oct 13 05:38:37 2010 j.novak [...] netsystem.cz - Correspondence added
Subject: Re: [rt.cpan.org #62073] Apostrophe issue in cell
Date: Wed, 13 Oct 2010 11:38:11 +0200
To: bug-Spreadsheet-ParseExcel [...] rt.cpan.org
From: Jirka Novak <j.novak [...] netsystem.cz>
Hi, Show quoted text
> The problem appears to be that the cell contained a string that looked like a number and also > contained a numeric format so ParseExcel formatted it as a number. > > This behaviour isn't consistent with Excel which leaves the string as a string until it is edited > by the user when it then converts it to a number. > > I've changed the way that ParseExcel handles these cases to reflect Excel's behaviour. > > You can try it out the changes from GitHub: > > http://github.com/jmcnamara/spreadsheet-parseexcel
I tried it and it works correctly now. Thank you for your help. Sincerely yours, Jirka Novak
  Thu Apr 07 10:34:23 2011 jmcnamara [...] cpan.org - Correspondence added
Fixed in version 0.59, now on CPAN. Thanks. John. --
  Thu Apr 07 10:34:23 2011 jmcnamara [...] cpan.org - Status changed from 'open' to 'resolved'