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: |
yokota [...] res.otaru-uc.ac.jp
|
Cc: |
|
AdminCc: |
|
|
Severity: |
(no value)
|
Broken in: |
(no value)
|
Fixed in: |
(no value)
|
|
Wed Jul 25 14:23:55 2007
yokota [...] res.otaru-uc.ac.jp - Ticket created
Recent Unicode::Map includes "CP932.map", so users don't need to install
any more a custom file for code CP932 which was previously named
"CP932Excel.map".
So, FmtJapan2.pm must be fixed as follows, otherwise it raises an error.
Cheers,
-----------
--- FmtJapan2.pm.orig Thu Jul 26 03:10:04 2007
+++ FmtJapan2.pm Thu Jul 26 03:10:04 2007
@@ -16,9 +16,9 @@
#------------------------------------------------------------------------------
sub new {
my($sPkg, %hKey) = @_;
- my $oMap = Unicode::Map->new('CP932Excel');
- die "NO MAP FILE CP932Excel!!"
- unless(-r Unicode::Map->mapping("CP932Excel"));
+ my $oMap = Unicode::Map->new('CP932');
+ die "NO MAP FILE CP932!!"
+ unless(-r Unicode::Map->mapping("CP932"));
my $oThis={
Code => $hKey{Code},
Wed Jul 25 20:56:28 2007
GCD00051 [...] nifty.ne.jp - Correspondence added
CP932.map has been included in Unicode::Map before I made
CP932Excel.map.
There are a few characters that converted from Unicode incorrectively.
Anyway I thought we should use Encode not Unicode::Map.
On 水曜日 7月 25 14:23:55 2007, yokota@res.otaru-uc.ac.jp wrote:
Show quoted text> Recent Unicode::Map includes "CP932.map", so users don't need to
> install
> any more a custom file for code CP932 which was previously named
> "CP932Excel.map".
>
> So, FmtJapan2.pm must be fixed as follows, otherwise it raises an
> error.
Wed Jul 25 20:56:36 2007
The RT System itself - Status changed from 'new' to 'open'
Thu Jul 26 12:40:17 2007
yokota [...] res.otaru-uc.ac.jp - Correspondence added
川合 孝典 via RT wrote:
Show quoted text> <URL:
http://rt.cpan.org/Ticket/Display.html?id=28476 >
>
> CP932.map has been included in Unicode::Map before I made
> CP932Excel.map.
> There are a few characters that converted from Unicode incorrectively.
> Anyway I thought we should use Encode not Unicode::Map.
>
> On 水曜日 7月 25 14:23:55 2007, yokota@res.otaru-uc.ac.jp wrote:
>
>> Recent Unicode::Map includes "CP932.map", so users don't need to
>> install
>> any more a custom file for code CP932 which was previously named
>> "CP932Excel.map".
>>
>> So, FmtJapan2.pm must be fixed as follows, otherwise it raises an
>> error.
>>
>
>
I see. Since CP932Excel.map was not included in my distribution, I had
no idea where it is. Now, I could find it on CPAN.
Thank you.
Thu Jan 08 07:49:13 2009
jmcnamara [...] cpan.org - Correspondence added
On Thu Jul 26 12:40:17 2007, yokota@res.otaru-uc.ac.jp wrote:
Show quoted text> 川合 孝典 via RT wrote:
> > <URL:
http://rt.cpan.org/Ticket/Display.html?id=28476 >
> >
> > CP932.map has been included in Unicode::Map before I made
> > CP932Excel.map.
> > There are a few characters that converted from Unicode incorrectively.
> > Anyway I thought we should use Encode not Unicode::Map.
> >
> > On 水曜日 7月 25 14:23:55 2007, yokota@res.otaru-uc.ac.jp wrote:
> >
> >> Recent Unicode::Map includes "CP932.map", so users don't need to
> >> install
> >> any more a custom file for code CP932 which was previously named
> >> "CP932Excel.map".
> >>
> >> So, FmtJapan2.pm must be fixed as follows, otherwise it raises an
> >> error.
> >>
> >
> >
> I see. Since CP932Excel.map was not included in my distribution, I had
> no idea where it is. Now, I could find it on CPAN.
>
> Thank you.
Hi,
Has this issue been resolved or is it still open?
John.
--