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

Bug #12375 Can't use UTF-8 chars in a bug report
Submitted: 2007-11-02 18:20 UTC Modified: 2008-02-02 21:12 UTC
From: cwiedmann Assigned: dufuz
Status: Closed Package: pearweb
PHP Version: Irrelevant OS: Irrelevant
Roadmaps: 1.18.0, 1.19.0    
Subscription  


 [2007-11-02 18:20 UTC] cwiedmann (Carsten Wiedmann)
Description: ------------ Hello, if you use UTF-8 chars in a bug report or comment, there is a double encoding. Instead of e.g. a "Л", there is a "Л" in the HTML. This is a problem, because you can't see if a bug reporter is using entities or UTF-8 chars in the report. So you can have a lot of confusion. An Example can be Bug #12362 Regards, Carsten

Comments

 [2007-12-02 20:30 UTC] dufuz (Helgi Þormar Þorbjörnsson)
Not enough information was provided for us to be able to handle this bug. Please re-read the instructions at http://bugs.php.net/how-to-report.php If you can provide more information, feel free to add it to this bug and change the status back to "Open". Thank you for your interest in PEAR. Do you want the actual chars to show up when you do &#1051 ? As in we run no filtering on the text ?
 [2008-02-02 21:00 UTC] dufuz (Helgi Þormar Þorbjörnsson)
Having tracked it down further, removing a htmlspecialchars (it was really really hidden) fixes it but opens up a can of worms, apparently I can't even get that russian text to show up even if I pass UTF-8 or similar to htmlspecialchars so I'm not sure if we can fix this :-/
 [2008-02-02 21:12 UTC] dufuz (Helgi Þormar Þorbjörnsson)
This bug has been fixed in CVS. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net 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. I actually remembered that htmlspecialchars can now take in the double encode = false and thus we can show weird UTF-8 chars and still somewhat protect our selfs :)