User Tools

Site Tools


tutorials:using_different_character_sets:start

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
tutorials:using_different_character_sets:start [2010/04/21 20:55]
jonyo wording
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> <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 default templates, as well as the charset used in the admin panel.  This does not include the charset used for "filtering inputs", see 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 ====== ====== Charset in config.php file ======
Line 13: Line 16:
 If you do not see that line, then you may need to add it. This setting controls **filtering** of user-input from PHP into the auction and classified software for use.  It is also used for what is known as AJAX, when content on the page is updated without re-loading the entire page, the updated content will use the above setting for the charset.  To change the setting, you would change **ISO-8859-1** to whatever charset you want to use, but it **must be a compatible charset** listed [[http://us3.php.net/htmlspecialchars|on this page]]. If you do not see that line, then you may need to add it. This setting controls **filtering** of user-input from PHP into the auction and classified software for use.  It is also used for what is known as AJAX, when content on the page is updated without re-loading the entire page, the updated content will use the above setting for the charset.  To change the setting, you would change **ISO-8859-1** to whatever charset you want to use, but it **must be a compatible charset** listed [[http://us3.php.net/htmlspecialchars|on this page]].
  
-For most sites and languages, the setting above is the only one that needs to be changed.  If the charset you need to use is **not** one of the [[http://us3.php.net/htmlspecialchars|compatible charsets]], you may be one of the few that need to make changes to other charset related settings in the config.php file.  In the **config.php** file itself, it gives a thorough explanation of the different charset settings used for filtering user input, and how each setting is used, and what it should be set to.  For your reference, below is the entire section pertaining to charsets, as it appears in the default **config.php** file distributed with the latest version, refer to it for an explanation if you do need to use a charset that is not in the [[http://us3.php.net/htmlspecialchars|compatible charsets list]]:+For most sites and languages, the setting above is the only one of the charset settings that needs to be changed in the **config.php** file.  If the charset you need to use is **not** one of the [[http://us3.php.net/htmlspecialchars|compatible charsets]], you may be one of the few that need to make changes to other charset related settings in the config.php file.  In the **config.php** file itself, it gives a thorough explanation of the different charset settings used for filtering user input, and how each setting is used, and what it should be set to.  For your reference, below is the entire section pertaining to charsets, as it appears in the default **config.php** file distributed with the latest version, refer to it for an explanation if you do need to use a charset that is not in the [[http://us3.php.net/htmlspecialchars|compatible charsets list]]:
  
 <code php config.php charset section>/* <code php config.php charset section>/*
Line 84: Line 87:
  //instead.  Valid settings are 'mb_convert_string'  //instead.  Valid settings are 'mb_convert_string'
  //and 'iconv' See notes above (steps 1 and 3)</code>  //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 line below:
 +
 +<code php>#$force_db_connection_charset = 'charset_name';</code>
 +
 +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 ====== ====== Charset in Admin Panel ======
Line 89: 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: 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. 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.
tutorials/using_different_character_sets/start.1271883324.txt.gz · Last modified: 2014/09/25 16:55 (external edit)