Edit report at https://bugs.php.net/bug.php?id=61354&edit=1
ID: 61354 Comment by: goodwaiter at gmail dot com Reported by: hufeng1987 at gmail dot com Summary: htmlentities and htmlspecialchars doesn't respect the default_charset Status: Not a bug Type: Bug Package: Strings related Operating System: Linux/Windows/ PHP Version: 5.4.0 Block user comment: N Private report: N New Comment: another fix way in code is that: use htmlspecialchars($text,NULL,"") not need to add "utf8" "cp936", or other in "", just leave "" blank, it will use the current page's encoding like no this bug. Previous Comments: ------------------------------------------------------------------------ [2012-08-27 16:24:39] goodwaiter at gmail dot com the post above is wrong,change from "Non Thread Safe" to "Thread Safe" cant fix it. right fix way: so guys above can change to windows + iis + isapi module + php, or windows + Apache + fastcgi/isapi module + php, can fix this bug. I just test, only windows + iis + fastcgi + php will show the bug. in isapi module or windows + Apache + fastcgi + php works fine. and I test that,the bug maybe because of iis fastcgi. in this case, Zend Multibyte Support allways be "provided by mbstring", even if I change zend.multibyte to off or on, it still "provided by mbstring". in phpinfo() show below: mbstring Multibyte Support enabled Multibyte string engine libmbfl HTTP input encoding translation disabled libmbfl version 1.3.2 mbstring extension makes use of "streamable kanji code filter and converter", which is distributed under the GNU Lesser General Public License version 2.1. Multibyte (japanese) regex support enabled Multibyte regex (oniguruma) version 4.7.1 and I use this code to test on windows + iis6 + fastcgi + php: echo(mb_internal_encoding());// show ISO-8859-1, right $text = "ææ¯æµè¯";//use cp936 chinese chars $ary[] = "ASCII"; $ary[] = "JIS"; $ary[] = "CP936"; $ary[] = "UTF-8"; echo mb_detect_encoding($text, $ary);//show cp936, right mb_detect_order($ary);//set detect order echo(htmlspecialchars($text));//show enmty, wrong !!!!!!!!!!! echo mb_detect_encoding(htmlspecialchars($text), $ary);//show ASCII(not the guy think is utf8), wrong !!!!!!!! echo(mb_internal_encoding());// show ISO-8859-1, not change, right this test can show us that, all things goes right except htmlspecialchars(), where is the "ASCII" from? maybe iis6 + fastcgi cause this bug. but it's really a php bug. ------------------------------------------------------------------------ [2012-08-27 13:17:48] goodwaiter at gmail dot com è½ç¶æ´æ¢å°é线ç¨å®å ¨çæ¬è½è§£å³é®é¢ï¼ä½æ¯é¾ä¿ä¸æ¬¡çæ¬ï¼PHPä¸ä¼æé线ç¨å®å ¨çæ¬çæ£å¸¸è¡¨ç°å½ä½ BUGæ´æ°æï¼æ以æ们è¦è®©PHPç¥éè¿ç¡®å®æ¯ä¸ä¸ªBUGã BUGçä¸æ表述å¾ç®åï¼ php.iniçDefault encodingæè mb-internal-encodingç设置ï¼å¯¹htmlspecialchars, htmlentitiesæ æï¼è¿ä¸¤ä¸ªå½æ°é¡½å¼ºç使ç¨èªå·±çutf-8ï¼èªä»¥ä¸ºæ¯ã æ´æµè¡ç表述æ¯ï¼ htmlspecialchars, htmlentitiesç¬ç«ä½¿ç¨èªå·±çç¼ç ï¼è¿è¿åç»ä¸å¤§å±ï¼PHPè¯å®ä¸è½å®¹å¿è¿æ ·çå å¨ï¼å¿ é¡»è¦é²é¤è¿ä¸ªBUG ------------------------------------------------------------------------ [2012-08-27 12:54:07] goodwaiter at gmail dot com It's really a bug. but we can fix this by a easy way(I'm use Windows): just change you php from "Non Thread Safe" to "Thread Safe" And everythings will be ok now. ------------------------------------------------------------------------ [2012-08-23 06:31:15] hufeng1987 at gmail dot com though php 5.4.6 released, but these problem still exists. do you really care the php developers? ------------------------------------------------------------------------ [2012-08-08 12:16:25] giodev at panozzo dot it Yes, this is a HUGE problem for us also. We migrate a single server with a single homemade application and we lost 3-4 hours to fix all htmlspecialchars() and htmlentities() to force encoding back to ISO-8859-1. And really, under these conditions we will never migrate other apps/servers to PHP 5.4. Too much work to be done not only by us, but also by external contractors and customer of hosting services. It's a big cost both for us and for our customers. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at https://bugs.php.net/bug.php?id=61354 -- Edit this bug report at https://bugs.php.net/bug.php?id=61354&edit=1