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.
| Owner: |
Nobody in particular
|
| Requestors: |
bm [...] ariva.de
|
| Cc: |
|
| AdminCc: |
|
|
| Severity: |
(no value)
|
| Broken in: |
(no value)
|
| Fixed in: |
(no value)
|
|
Wed Apr 16 05:58:16 2014
bm [...] ariva.de - Ticket created
Hello,
iam trying to use WriteExcel in an utf8 perl script. It's important for
me to set "use encoding 'UTF-8'", but if I do that iam getting malformed
UTF-8 character warnings when writing formulars. See example below.
Example
=======
use strict;
use warnings;
use encoding 'UTF-8';
use Spreadsheet::WriteExcel;
my $s = Spreadsheet::WriteExcel->new('test.xls');
my $w = $s->add_worksheet('foo');
$w->write('A1', '=SUM(B1:B4)'); # this throws errors when "use utf8;" or
"use encoding 'UTF-8'" enabled
$w->write('A1', 'SUM(B1:B4)'); # this won't throw errors at all
Produced warnings:
================
Malformed UTF-8 character (unexpected non-continuation byte 0x2d,
immediately after start byte 0xc0) at (eval 413) line 3.
Malformed UTF-8 character (unexpected non-continuation byte 0x5f,
immediately after start byte 0xdc) at (eval 413) line 3.
Malformed UTF-8 character (unexpected non-continuation byte 0x2d,
immediately after start byte 0xc0) at (eval 414) line 3.
Malformed UTF-8 character (unexpected non-continuation byte 0x5f,
immediately after start byte 0xdc) at (eval 414) line 3.
Malformed UTF-8 character (unexpected non-continuation byte 0x2d,
immediately after start byte 0xc0) at (eval 415) line 3.
Malformed UTF-8 character (unexpected non-continuation byte 0x5f,
immediately after start byte 0xdc) at (eval 415) line 3.
Malformed UTF-8 character (unexpected non-continuation byte 0x2d,
immediately after start byte 0xc0) at (eval 445) line 565.
Malformed UTF-8 character (unexpected non-continuation byte 0x5f,
immediately after start byte 0xdc) at (eval 445) line 565.
Malformed UTF-8 character (unexpected non-continuation byte 0x2d,
immediately after start byte 0xc0) at (eval 445) line 671.
Malformed UTF-8 character (unexpected non-continuation byte 0x5f,
immediately after start byte 0xdc) at (eval 445) line 671.
Malformed UTF-8 character (unexpected non-continuation byte 0x2d,
immediately after start byte 0xc0) at (eval 445) line 835.
Malformed UTF-8 character (unexpected non-continuation byte 0x5f,
immediately after start byte 0xdc) at (eval 445) line 835.
Best regards
Björn Müller
--
Björn Müller, Datenbankentwicklung, E-Mail:bm@ariva.de
Tel. (+49)431 97108-273, Fax (+49)431 97108-29, Web:www.ariva.de
ARIVA.DE AG, Registergericht Kiel HRB 5521, Neufeldtstr. 9, 24118 Kiel,
Vorstand: Matthias Vogelsang-Weber (Vorsitzender), Paul Mallach, Jochen Pape,
Markus Tiedt, Aufsichtsratsvorsitzender: Tim Sichting
Wed Apr 16 06:46:04 2014
The RT System itself - Status changed from 'new' to 'open'
Wed Apr 16 13:28:58 2014
bm [...] ariva.de - Correspondence added
Thank you John. This solved my problem. We'll migrate to
Excel::Writer::XLSX now.
Björn
Am 16.04.2014 12:46, schrieb John McNamara via RT:
Show quoted text
Wed Apr 16 20:05:05 2014
jmcnamara [...] cpan.org - Correspondence added
On Wed Apr 16 13:28:58 2014, bm@ariva.de wrote:
Show quoted text> Thank you John. This solved my problem. We'll migrate to
> Excel::Writer::XLSX now.
Hi,
Good work.
I'll close this issue for now.
Regards,
John
Wed Apr 16 20:05:40 2014
jmcnamara [...] cpan.org - Status changed from 'open' to 'resolved'
