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

People
Owner: Nobody in particular
Requestors: SREZIC [...] cpan.org
Cc:
AdminCc:

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



Subject: ucs2 issues
Download (untitled) / with headers
text/plain 598b
I think it would be nice if Spreadsheet::ParseExcel would convert ucs-2 characters from an Excel file automatically in perl characters. Now, only the "Code" member is set to "ucs2" and the user has to write Encode::decode("UCS-2", $cell_value); to get the correct cell value. A change like this could be problematic for older perls (no unicode support at all or no Encode bundled with core perl), and may also break older scripts, so maybe it should be only done per option. At least it would be nice if the ParseExcel documentation contained a line like the one above. Regards, Slaven
Subject: ucs2 issues adn perl
From: divanov [...] creditreform.bg
Download (untitled) / with headers
text/plain 1.2k
Hi, Slaven, Kawai, Show quoted text
> I think it would be nice if Spreadsheet::ParseExcel would convert > ucs-2 characters from an Excel file automatically in perl characters. > Now, only the "Code" member is set to "ucs2" and the user has to write > > Encode::decode("UCS-2", $cell_value); > > to get the correct cell value. > > A change like this could be problematic for older perls (no unicode > support at all or no Encode bundled with core perl), and may also > break older scripts, so maybe it should be only done per option. At > least it would be nice if the ParseExcel documentation contained a > line like the one above.
May I propose the following change in FmtDefault.pm (original also here, commented)? It just adds support for perl5.8's native utf-8 characters. For older perls it works as before. Thanks for considering. sub TextFmt($$;$) { my($oThis, $sTxt, $sCode) =@_; return $sTxt if((! defined($sCode)) || ($sCode eq '_native_')); # Handle utf8 strings in newer perls. if ($] >= 5.008) { require Encode; return Encode::decode("UTF-16BE", $sTxt, 1); } return pack('C*', unpack('n*', $sTxt)); } #sub TextFmt($$;$) { # my($oThis, $sTxt, $sCode) =@_; # return $sTxt if((! defined($sCode)) || ($sCode eq '_native_')); # return pack('C*', unpack('n*', $sTxt)); #}
Download (untitled) / with headers
text/plain 255b
On Mon Feb 14 06:44:58 2005, SREZIC wrote: Show quoted text
> > Encode::decode("UCS-2", $cell_value); >
... Show quoted text
> return Encode::decode("UTF-16BE", $sTxt, 1);
I'm wondering if there is any advantage/disadvantage of this over the current: pack('U*', unpack('n*', $sTxt));
Download (untitled) / with headers
text/plain 420b
On 2014-03-07 16:00:49, DOUGW wrote: Show quoted text
> On Mon Feb 14 06:44:58 2005, SREZIC wrote:
> > > > Encode::decode("UCS-2", $cell_value); > >
> ...
> > return Encode::decode("UTF-16BE", $sTxt, 1);
> > I'm wondering if there is any advantage/disadvantage of this over the > current: > pack('U*', unpack('n*', $sTxt));
I am not sure. "U" is handling utf-8, but it should probably be either utf-16be or ucs-2. Regards, Slaven
Download (untitled) / with headers
text/plain 292b
On Sat Mar 08 07:55:06 2014, SREZIC wrote: Show quoted text
> > I am not sure. "U" is handling utf-8, but it should probably be either > utf-16be or ucs-2.
Thanks. I think I am going to go with "it seems to be working now, so don't fix it", at least until someone comes up with a case where it doesn't work.


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

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.