osCommerce 2.3.1 is a bit messy when it comes to the new introduction of UTF-8 character set. In older versions, everything was ISO-8859-1 <\/p>\n
* Core source code (ISO-8859-1)
\n* Language pack source code (ISO-8859-1)
\n* Mysql tables (ISO-8859-1)
\n* Mysql I\/O (ISO-8859-1)
\n* The html output (ISO-8859-1)
\n* HTML charset for browser decoding (ISO-8859-1)
\n* Incoming HTML form data (ISO-8859-1)<\/p>\n
In the new version it’s different:<\/p>\n
* Core source code (ISO-8859-1)
\n* Language pack source code (ISO-8859-1)
\n* Mysql tables (UTF-8)
\n* Mysql I\/O (UTF-8)
\n* The html output (ISO-8859-1)
\n* HTML charset for browser decoding (UTF-8)
\n* Incoming HTML form data (UTF-8)<\/p>\n
WHAT’S THE PROBLEM?<\/span><\/strong> Then you say, why not convert the language file contents to UTF-8 WHAT’S THE GUIDELINE THEN?<\/strong><\/span> BUT CAN’T I JUST DEFINE OUTPUT AS ISO-8859-1 LIKE BEFORE?<\/strong><\/span> SO WHAT DO I DO?<\/strong><\/span> # 1.1 In {catalog}\/{admin}\/includes\/application_top.php<\/p>\n *** On line ~166, find ***<\/p>\n *** After that, add ***<\/p>\n # 1.2 In {catalog}\/{admin}\/includes\/classes\/email.php<\/p>\n *** On line ~148, find ***<\/p>\n *** After that, add ***<\/p>\n ______________________________________________________________________<\/p>\n *** On line ~161, find ***<\/p>\n *** After that, add ***<\/p>\n # 2.1 In {catalog}\/includes\/application_top.php<\/p>\n *** On line ~258, find ***<\/p>\n *** After that, add ***<\/p>\n # 2.2 In {catalog}\/includes\/classes\/email.php<\/p>\n *** On line ~148, find ***<\/p>\n *** After that, add ***<\/p>\n ______________________________________________________________________<\/p>\n *** On line ~161, find ***<\/p>\n *** After that, add ***<\/p>\n CHECKLISTS<\/strong><\/p>\n Full ISO-8859-1 Language Pack Full UTF-8 Language Pack osCommerce 2.3.1 is a bit messy when it comes to the new introduction of UTF-8 character set. In older versions, everything was ISO-8859-1 * Core source code (ISO-8859-1) * Language pack source code (ISO-8859-1)...<\/p>\n","protected":false},"author":1,"featured_media":2841,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[18,182,5],"tags":[],"youtube_video":null,"_links":{"self":[{"href":"https:\/\/www.extradrm.com\/index.php?rest_route=\/wp\/v2\/posts\/13"}],"collection":[{"href":"https:\/\/www.extradrm.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.extradrm.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.extradrm.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.extradrm.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=13"}],"version-history":[{"count":0,"href":"https:\/\/www.extradrm.com\/index.php?rest_route=\/wp\/v2\/posts\/13\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.extradrm.com\/index.php?rest_route=\/wp\/v2\/media\/2841"}],"wp:attachment":[{"href":"https:\/\/www.extradrm.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=13"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.extradrm.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=13"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.extradrm.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=13"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\nThis of course causes terrible problems if you upload a language pack
\nthat is ISO-8859-1 source code and contains foregin characters like
\n\u00e5\u00e4\u00f6.<\/p>\n
\nthen? Well PHP 5.3 does not fully support UTF-8 encoded files so
\nthe source code should more effectively remain in ISO-8859-1 format.<\/p>\n
\nWell, I am told to use entities for special characters such as
\n\u00e4 => ä and so on… Becasue all non-foreign ASCII characters are
\nsupported in both UTF-8 and ISO-8859-1. That way your language pack is
\nuniversal for both charsets. But this messes up any non-HTML output.
\nSo you’re still going to have some unpleasent results.<\/p>\n
\nNo! Because when the customer is passing HTML form data that has
\nforegin characters, these will not be displayed correctly when
\nswapping to a UTF-8 language pack for example English. Neither
\nwill the data be saved correctly in the database.<\/p>\n
\nWe implement dual support for both ISO-8859-1 and UTF-8 language packs.<\/p>\n\/\/ include the language translations\r\nrequire(DIR_WS_LANGUAGES . $language . '.php');\r\n$current_page = basename($PHP_SELF);\r\nif (file_exists(DIR_WS_LANGUAGES . $language . '\/' . $current_page)) {\r\ninclude(DIR_WS_LANGUAGES . $language . '\/' . $current_page);\r\n}<\/pre>\n\/\/ BOF: [osC Solutions] ISO-8859-1\/UTF-8 dual support\r\nswitch (strtolower(CHARSET)) {\r\ncase 'utf-8':\r\ntep_db_query(\"SET character set utf8\");\r\nbreak;\r\ncase 'iso-8859-1':\r\ntep_db_query(\"SET character set latin1\");\r\nbreak;\r\n}\r\n\/\/ EOF: [osC Solutions] ISO-8859-1\/UTF-8 dual support<\/pre>\n function add_text($text = '') {<\/pre>\n\/\/ BOF: [osC Solutions] ISO-8859-1\/UTF-8 dual support\r\nif (strtolower(CHARSET) != 'utf-8') $text = utf8_encode($text);\r\n\/\/ EOF: [osC Solutions] ISO-8859-1\/UTF-8 dual support\r\n<\/pre>\n
function add_html($html, $text = NULL, $images_dir = NULL) {<\/pre>\n\/\/ BOF: [osC Solutions] ISO-8859-1\/UTF-8 dual support\r\nif (strtolower(CHARSET) != 'utf-8') $html = utf8_encode($html);\r\nif (strtolower(CHARSET) != 'utf-8') $text = utf8_encode($text);\r\n\/\/ EOF: [osC Solutions] ISO-8859-1\/UTF-8 dual support<\/pre>\n
\/\/ include the language translations\r\nrequire(DIR_WS_LANGUAGES . $language . '.php');<\/pre>\n
\r\n\/\/ BOF: [osC Solutions] ISO-8859-1\/UTF-8 dual support\r\nswitch (strtolower(CHARSET)) {\r\ncase 'utf-8':\r\ntep_db_query(\"SET character set utf8\");\r\nbreak;\r\ncase 'iso-8859-1':\r\ntep_db_query(\"SET character set latin1\");\r\nbreak;\r\n}\r\n\/\/ EOF: [osC Solutions] ISO-8859-1\/UTF-8 dual support\r\n<\/pre>\nfunction add_text($text = '') {<\/pre>\n\/\/ BOF: [osC Solutions] ISO-8859-1\/UTF-8 dual support\r\nif (strtolower(CHARSET) != 'utf-8') $text = utf8_encode($text);\r\n\/\/ EOF: [osC Solutions] ISO-8859-1\/UTF-8 dual support<\/pre>\n
function add_html($html, $text = NULL, $images_dir = NULL) {<\/pre>\n\/\/ BOF: [osC Solutions] ISO-8859-1\/UTF-8 dual support\r\nif (strtolower(CHARSET) != 'utf-8') $html = utf8_encode($html);\r\nif (strtolower(CHARSET) != 'utf-8') $text = utf8_encode($text);\r\n\/\/ EOF: [osC Solutions] ISO-8859-1\/UTF-8 dual support<\/pre>\n
\n[ ] Source code saved in ANSII\/ISO-8859-1
\n[ ] {languagename}.php states define(‘CHARSET’, ‘iso-8859-1’);<\/p>\n
\n[ ] Source code saved in UTF-8 without BOM
\n[ ] {languagename}.php states define(‘CHARSET’, ‘utf-8’);
\n[ ] {languagename}.php includes mb_internal_encoding(‘utf-8’);<\/p>\n","protected":false},"excerpt":{"rendered":"