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.
Owner: |
Nobody in particular
|
Requestors: |
motoplux [...] gmail.com
|
Cc: |
|
AdminCc: |
|
|
Severity: |
Normal |
Broken in: |
|
Fixed in: |
(no value)
|
|
Wed Oct 15 05:46:05 2008
http://motoplux.myopenid.com/ - Ticket created
While trying to parse cells with the euro symbol € I get a wrong parsed
value like € instead
Tested on: Spreadsheet-ParseExcel-0.33 and Spreadsheet-ParseExcel-0.32
Perl version: v5.8.8 built for i386-linux-thread-multi
Operating system:
CentOS release 5.2 (Final)
Linux 2.6.18-92.1.13.el5PAE #1 SMP Wed Sep 24 20:07:49 EDT 2008 i686
i686 i386 GNU/Linux
Wed Oct 15 11:42:36 2008
jmcnamara [...] cpan.org - Correspondence added
On Wed Oct 15 05:46:05 2008,
http://motoplux.myopenid.com/ wrote:
Show quoted text> While trying to parse cells with the euro symbol € I get a wrong parsed
> value like € instead
Hi,
The Euro symbol isn't stored in Excel as a single character. It is
stored as a UTF-16 character and is returned by Spreadsheet::ParseExcel
as a Perl utf8 character.
This is what you are seeing and in terms of the way
Spreadsheet::ParseExcel handles Unicode it is the correct behaviour.
How you should handle the utf8 string from there depends on what you
want to do with it.
John.
--
Wed Oct 15 11:42:39 2008
The RT System itself - Status changed from 'new' to 'open'
Tue Oct 28 12:44:16 2008
jmcnamara [...] cpan.org - Correspondence added
Hi,
I'm going to close this issue. If you still think it is a bug you can
open it again or else discuss it on the Spreadsheet::ParseExcel Google
group:
http://groups.google.com/group/spreadsheet-parseexcel
John.
--
Tue Oct 28 12:44:19 2008
jmcnamara [...] cpan.org - Status changed from 'open' to 'resolved'