Skip Menu |
 

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the Devel-Cover CPAN distribution.

Report information
The Basics
Id: 43054
Status: open
Priority: 0/
Queue: Devel-Cover

People
Owner: Nobody in particular
Requestors: jpl [...] plosquare.com
Cc:
AdminCc:

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



Subject: Wrong charset / encoding in the generated HTML page
Download (untitled) / with headers
text/plain 255b
My *.pm files contain characters encoded in iso-8859-1 (German umlauts). The generated HTML coverage report also contains iso-8859-1 characters, but the charset is specified as utf-8 in the meta tag, which prevents the characters from displaying properly.
Download (untitled) / with headers
text/plain 686b
Le 2009-02-05 08:28:11, jploski a écrit : Show quoted text
> My *.pm files contain characters encoded in iso-8859-1 (German umlauts). > The generated HTML coverage report also contains iso-8859-1 characters, > but the charset is specified as utf-8 in the meta tag, which prevents > the characters from displaying properly.
Devel::Cover will never be able to detect which encoding you are using. Also if you are using 8bits characters without specifying the encoding (use encoding/use utf8) your module is not portable to other platforms. It would be safer to convert your script to UTF-8 and add the "use utf8" pragma. -- Olivier Mengué - http://search.cpan.org/~dolmen/ http://github.com/dolmen/
From: jpl [...] plosquare.com
Download (untitled) / with headers
text/plain 942b
I cannot change encoding in these files at will (stored under version control, worked upon by different people using different editors). I suggest that an option is added to Devel::Cover which declares the encoding of (all) processed files if it cannot be detected. On Wed Oct 27 21:31:16 2010, DOLMEN wrote: Show quoted text
> Le 2009-02-05 08:28:11, jploski a écrit :
> > My *.pm files contain characters encoded in iso-8859-1 (German umlauts). > > The generated HTML coverage report also contains iso-8859-1 characters, > > but the charset is specified as utf-8 in the meta tag, which prevents > > the characters from displaying properly.
> > Devel::Cover will never be able to detect which encoding you are using. > Also if you are using 8bits characters without specifying the encoding > (use encoding/use utf8) your module is not portable to other platforms. > > It would be safer to convert your script to UTF-8 and add the "use utf8" > pragma.


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.