Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 1.32.0

Bug #16040 Character encoding incorrect
Submitted: 2009-03-17 17:24 UTC
From: gauthierm Assigned: dufuz
Status: Closed Package: pearweb
PHP Version: Irrelevant OS: Irrelevant
Roadmaps: 1.22.0    

 [2009-03-17 17:24 UTC] gauthierm (Michael Gauthier)
Description: ------------ For the page, the content-type header sent is "text/html; charset=ISO-8859-15". The page content is actually in UTF-8. This causes a certain name to display incorrectly.


 [2009-03-22 21:40 UTC] dufuz (Helgi Þormar Þorbjörnsson)
-Assigned To: +Assigned To: dufuz -Roadmap Versions: +Roadmap Versions: 1.18.0
The database is latin-1 so we have to convert that first before we start outputting the website in UTF-8. The reason why this is happening is because you can have a package.xml file in UTF-8 or ISO8859-15 :-) Tomorrow we will convert the database and fix the output
 [2009-05-07 11:50 UTC] cweiske (Christian Weiske)
As far as I know, the database is in utf8 now.
 [2009-06-21 05:33 UTC] gauthierm (Michael Gauthier)
Page is still display the bug for version PHP_CodeSniffer 1.2.0RC1
 [2009-08-10 06:44 UTC] doconnor (Daniel O'Connor)
-Status: Assigned +Status: Closed
This bug has been fixed in CVS. If this was a documentation problem, the fix will appear on by the end of next Sunday (CET). If this was a problem with the website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better. This was resolved the other day by [286927]
 [2009-08-25 16:44 UTC] cweiske (Christian Weiske)
-Roadmap Versions: 1.18.0, 1.22.0 +Roadmap Versions: 1.22.0
 [2009-09-15 06:52 UTC] gauthierm (Michael Gauthier)
The particular page in this bug report is still broken, though the HTTP header is correctly set to UTF-8. Does database content need to be converted?
 [2009-09-15 08:51 UTC] doconnor (Daniel O'Connor)
 [2009-10-15 23:31 UTC] cweiske (Christian Weiske)
-Status: Assigned +Status: Closed
The bug is actually fixed. Only this particular database entry is in the wrong encoding. I won't fix that.