Differences

This shows you the differences between two versions of the page.

--- tutorials:using_different_character_sets:start [2010/04/21 21:09]
jonyo added warning about db connection charset
+++ tutorials:using_different_character_sets:start [2014/09/25 16:55] (current)
@@ Line 3: / Line 3: @@
 <tip c n>**Note:**  We recommend using **UTF-8** charset if that is at all possible for the language you intend to use on your site.  This will ensure your site has as few charset related problems as possible going forward.</tip>
-To use and have **non-english** character sets within our software may need a few different changes, each listed on this page. Our auction and classified software comes to you using **UTF-8** character encoding by default((This includes the charset used in the admin panel, as well as the charset used in the default templates.  This does **not** include the charset used in the **config.php** for "filtering inputs" and AJAX contents, see [[#Charset in config.php file]] section below for more information on that.)). This character encoding is fine for the vast majority of sites, even the majority of non-English language sites.  Using UTF-8 is even more important if your site uses multiple languages, since UTF-8 can be used across almost all the different languages.
+To use and have **non-english** character sets (Charset) within our software may need a few different changes, each listed on this page. Our auction and classified software comes to you using **UTF-8** character encoding by default((This includes the charset used in the admin panel, as well as the charset used in the default templates.  This does **not** include the charset used in the **config.php** for "filtering inputs" and AJAX contents, see [[#Charset in config.php file]] section below for more information on that.)). This character encoding is fine for the vast majority of sites, even the majority of non-English language sites.  Using UTF-8 is even more important if your site uses multiple languages, since UTF-8 can be used across almost all the different languages.
+<tip c n>**Note:**  The search feature in general is not case-sensitive within the software but that does not apply to special and/or accented characters such as ç and Ç. This is a limitation of the system at the database level because of the way the accented characters are represented in the database.  They cannot be searched in a case-insensitive manner.</tip>
 ====== Charset in config.php file ======
@@ Line 85: / Line 88: @@
 												//and 'iconv'.  See notes above (steps 1 and 3)</code>
-<tip c w>**Warning:**  In the **advanced database settings** section in the config.php file, there is another charset setting that will look similar to the code listed below:
+<tip c w>**Warning:**  In the **advanced database settings** section in the config.php file, there is another charset setting that will look similar to the line below:
-<code php>//DB Connection Charset - This charset setting is used when connecting to the database,
-//to force the connection charset to be different than the charset setting used at
-//the server level.  This is not often needed, so before enabling this setting see
-//the documentation from: http://dev.mysql.com/doc/refman/4.1/en/charset-connection.html
-// To use, un-comment the line below (remove the #) and change the 'charset_name' to the
+<code php>#$force_db_connection_charset = 'charset_name';</code>
-// charset needed.
-#$force_db_connection_charset = 'charset_name';</code>
-Most sites **should not change this setting**, it is used for a work-around for a very rare issue on some servers.  If you use this setting when not necessary, or use it incorrectly, it can **corrupt the database data** when the data is being inserted into the database by the software.  Do not change this setting unless you are absolutely certain that it needs to be changed, or if **Geo support has instructed you to change it**.</tip>
+Most sites **should not use or change this setting**, it is used in a work-around for a very rare server configuration issue.  If you use this setting when not necessary, or use it incorrectly, it can **corrupt the database data** when the data is being inserted into the database by the software.  Do not change this setting unless you are absolutely certain that it needs to be changed, or if **Geo support has instructed you to change it**.  If in doubt, do not touch the setting.</tip>
 ====== Charset in Admin Panel ======
@@ Line 102: / Line 98: @@
 You will need to change the character encoding set within the admin tool to set the character encoding used in the admin tool here:
-[[admin_menu/site_setup/general_settings/start#character_encoding|Site Configuration > General Settings > Character Encoding]]
+[[admin_menu/site_setup/general_settings/start#character_encoding|Site Setup > General Settings > Character Encoding]]
 If you do not have this setting we recommend updating to the latest version which will have it. Changing the setting here will allow you to insert characters directly into the browser when making changes in your admin panel, and those characters displayed properly without translation.  This will affect all text controlled by the system and administered through the admin tool like template editing, language text, etc.

Geodesic Solutions Community Wiki

User Tools

Site Tools

Differences

Page Tools