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)

History Show all quoted text
  Thu Feb 05 08:28:11 2009 jpl [...] plosquare.com - Ticket created
Subject: Wrong charset / encoding in the generated HTML page
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.
  Wed Oct 27 21:31:16 2010 dolmen [...] cpan.org - Correspondence added
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/
  Wed Oct 27 21:31:17 2010 The RT System itself - Status changed from 'new' to 'open'
  Thu Oct 28 04:25:30 2010 jpl [...] plosquare.com - Correspondence added
From: jpl [...] plosquare.com
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.