tonyair/silverstripe-framework
1
0
Fork 0
mirror of https://github.com/silverstripe/silverstripe-framework synced 2024-09-28 04:16:44 +02:00
Code Issues Projects Releases Wiki Activity

Merge pull request #6629 from open-sausages/pulls/4.0/document-setlocale

Browse Source 
Document correct setlocale() use (fixes #6311)
This commit is contained in:
Daniel Hensby 2017-02-17 00:37:55 +00:00 committed by GitHub
commit c1ccf354cb
1 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/en/02_Developer_Guides/13_i18n/index.md
View File

@ -37,6 +37,12 @@ Once we set a locale, all the calls to the translator function will return strin
these translations are available. See [unicode.org](http://unicode.org/cldr/data/diff/supplemental/languages_and_territories.html) these translations are available. See [unicode.org](http://unicode.org/cldr/data/diff/supplemental/languages_and_territories.html)
for a complete listing of available locales. for a complete listing of available locales.
The `i18n` logic doesn't set the PHP locale via [setlocale()](http://php.net/setlocale).
Localisation methods in SilverStripe rely on explicit locale settings as documented below.
If you rely on PHP's built-in localisation such as [strftime()](http://php.net/strftime),
please only change locale information selectively. Setting `LC_ALL` or `LC_NUMERIC` will cause issues with SilverStripe
operations such as decimal separators in database queries.
### Getting the locale ### Getting the locale
As you set the locale you can also get the current value, just by calling [api:i18n::get_locale()]. As you set the locale you can also get the current value, just by calling [api:i18n::get_locale()].