You have probably come to mix encoding types. For example. A page that is sent as iso-8859-1, but get UTF-8 text encoding from MySQL or XML would typically fail To solve this problem you must keep control on input ecodings type in relation to the type of encoding you have chosen to use internal If you send it as an iso-8859-1, your input from the user is also iso-8859-1 header("Content-type:text/html; charset: iso-8859-1") And if mysql sends latin1 you do not have to do anything But if your input is not iso-8859-1 you must converted it, before it's sending to the user or to adapt it to Mysql before it's store mb_convert_encoding($text, mb_internal_encoding(), 'UTF-8'); // If it's UTF-8 to internal encoding Short it means that you must always have input converted to fit internal encoding and convereter output to match the external encoding This is the internal encoding I have chosen to use mb_internal_encoding('iso-8859-1'); // Internal encoding This is a code I use mb_language('uni'); // Mail encoding mb_internal_encoding('iso-8859-1'); // Internal encoding mb_http_output('pass'); // Skip function convert_encoding($text, $from_code='', $to_code='') { if (empty($from_code)) { $from_code = mb_detect_encoding($text, 'auto'); if ($from_code == 'ASCII') { $from_code = 'iso-8859-1'; } } if (empty($to_code)) { return mb_convert_encoding($text, mb_internal_encoding(), $from_code); } return mb_convert_encoding($text, $to_code, $from_code); } function encoding_html($text, $code='') { if (empty($code)) { return htmlentities($text, ENT_NOQUOTES, mb_internal_encoding()); } return mb_convert_encoding(htmlentities($text, ENT_NOQUOTES, $code), mb_internal_encoding(), $code); } function decoding_html($text, $code='') { if (empty($code)) { return html_entity_decode($text, ENT_NOQUOTES, mb_internal_encoding()); } return mb_convert_encoding(html_entity_decode($text, ENT_NOQUOTES, mb_internal_encoding()), $code, mb_internal_encoding()); }.
You have probably come to mix encoding types. For example. A page that is sent as iso-8859-1, but get UTF-8 text encoding from MySQL or XML would typically fail.To solve this problem you must keep control on input ecodings type in relation to the type of encoding you have chosen to use internal.
If you send it as an iso-8859-1, your input from the user is also iso-8859-1. Header("Content-type:text/html; charset: iso-8859-1"); And if mysql sends latin1 you do not have to do anything. But if your input is not iso-8859-1 you must converted it, before it's sending to the user or to adapt it to Mysql before it's store.
Mb_convert_encoding($text, mb_internal_encoding(), 'UTF-8'); // If it's UTF-8 to internal encoding Short it means that you must always have input converted to fit internal encoding and convereter output to match the external encoding. This is the internal encoding I have chosen to use. Mb_internal_encoding('iso-8859-1'); // Internal encoding This is a code I use.
Mb_language('uni'); // Mail encoding mb_internal_encoding('iso-8859-1'); // Internal encoding mb_http_output('pass'); // Skip function convert_encoding($text, $from_code='', $to_code='') { if (empty($from_code)) { $from_code = mb_detect_encoding($text, 'auto'); if ($from_code == 'ASCII') { $from_code = 'iso-8859-1'; } } if (empty($to_code)) { return mb_convert_encoding($text, mb_internal_encoding(), $from_code); } return mb_convert_encoding($text, $to_code, $from_code); } function encoding_html($text, $code='') { if (empty($code)) { return htmlentities($text, ENT_NOQUOTES, mb_internal_encoding()); } return mb_convert_encoding(htmlentities($text, ENT_NOQUOTES, $code), mb_internal_encoding(), $code); } function decoding_html($text, $code='') { if (empty($code)) { return html_entity_decode($text, ENT_NOQUOTES, mb_internal_encoding()); } return mb_convert_encoding(html_entity_decode($text, ENT_NOQUOTES, mb_internal_encoding()), $code, mb_internal_encoding()); }.
I also recommend to read this entry on encoding in javascripting stackoverflow. Com/questions/60825/… – Diblo Dk Sep 21 at 16:05 Of course the answers below, still have a major impact on html and troubleshooting. – Diblo Dk Sep 21 at 16:35 But this is a big influence on php and encoding.
Dk2.php. Net/manual/en/mbstring.overload. Php dk2.php.Net/manual/en/ref.mbstring.
Php – Diblo Dk Sep 21 at 16:43.
Can you check what is the value of HTTP header Charset in Response Headers. Though the information is old(2009), I don't know if it still holds: the default charset in PHP is UTF-8 if you don't provide the content-type header with charset. Source Hence set the header explicitly: header("Content-type:text/html; charset: iso-8859-1").
Connection:Keep-Alive Content-Type:text/html; charset: iso-8859-1 It's all ok if it's not inside input's (radio) value – Alexander Beninski Sep 21 at 15:14.
Updated I need to get my encode/decode de-confused. When you're in PHP try decoding the string in UTF-8 before output. $str = 'I ãm UTF-8'; echo(utf8_decode($str)); This worked for me: Test: '> Value in Input (via Cut n Paste): I ãm UTF-8: ÖMG!
Seems overly clumsy for something as mature as PHP. – bzlm Sep 21 at 15:03 1) avoid using single quotes for HTML attributes.2) You should probably html encode the value attribute. -1 for posting code that, if used verbatim, is a giant invite for cross-site scripting.
– phooji Sep 21 at 15:23 Sorry for the oversight, it has been updated. – watcher Sep 21 at 15:28 This really seems to be working.Is this the only way? – Alexander Beninski Sep 21 at 15:36.
2 That feels like a compromise. Ö doesn't need entitizing in iso-8859-1 or utf8. – bzlm Sep 21 at 14:56 I tried to use it but when it is like this it displays �.
– Alexander Beninski Sep 21 at 15:01.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.