今天公司一个项目又出现乱码,开始以为是ajax的问题导致乱码,因为那个ajax框架cpaint2很不熟悉,化了一些时间去了解,结果一无所获,无谓浪费了时间
于是再从程序post入手发现问题,原来是函数htmlentities引起的乱码,晕
发现直接输出依然是乱码
<?php
echo $_POST['name'];
?>
使用函数mb_internal_encoding()检测发现编码为ISO-8859-1
于是设置编码为UTF-8 mb_internal_encoding('UTF-8');
输出正常了
但是数据库接收到的还是乱码
发现有用函数htmlentities对$_POST['name']处理
查了一下htmlentities的用法,没有指定编码的时候,默认编码居然是ISO-8859-1,加上UTF-8后,乱码消失.记录一下
(PHP 3, PHP 4 )
htmlentities -- Convert all applicable characters to HTML entities
Description
string htmlentities ( string string [, int quote_style [, string charset]])
This function is identical to htmlspecialchars() in all ways, except with htmlentities(), all characters which have HTML character entity equivalents are translated into these entities.
表格 1. Available quote_style constants
| Constant Name | Description |
|---|---|
| ENT_COMPAT | Will convert double-quotes and leave single-quotes alone. |
| ENT_QUOTES | Will convert both double and single quotes. |
| ENT_NOQUOTES | Will leave both double and single quotes unconverted. |
表格 2. Supported charsets
| Charset | Aliases | Description |
|---|---|---|
| ISO-8859-1 | ISO8859-1 | Western European, Latin-1 |
| ISO-8859-15 | ISO8859-15 | Western European, Latin-9. Adds the Euro sign, French and Finnish letters missing in Latin-1(ISO-8859-1). |
| UTF-8 | ASCII compatible multi-byte 8-bit Unicode. | |
| cp866 | ibm866, 866 | DOS-specific Cyrillic charset. This charset is supported in 4.3.2. |
| cp1251 | Windows-1251, win-1251, 1251 | Windows-specific Cyrillic charset. This charset is supported in 4.3.2. |
| cp1252 | Windows-1252, 1252 | Windows specific charset for Western European. |
| KOI8-R | koi8-ru, koi8r | Russian. This charset is supported in 4.3.2. |
| BIG5 | 950 | Traditional Chinese, mainly used in Taiwan. |
| GB2312 | 936 | Simplified Chinese, national standard character set. |
| BIG5-HKSCS | Big5 with Hong Kong extensions, Traditional Chinese. | |
| Shift_JIS | SJIS, 932 | Japanese |
| EUC-JP | EUCJP | Japanese |
注: Any other character sets are not recognized and ISO-8859-1 will be used instead.
这次产生乱码的原因分析的时候走了不少弯路,浪费了不少的时间...
这该死的htmlentities,该死的乱码
(142)
(131)
(311)
(236)
(70)
(24)
(6)
(162)
(44)
(24)
(24)
(6)
(2)
(3)
(16)
(11)
(3)