diff options
| author | Victor Costan <costan@gmail.com> | 2012-10-01 13:54:48 -0300 |
|---|---|---|
| committer | Victor Costan <costan@gmail.com> | 2012-10-01 15:15:09 -0400 |
| commit | c7d39f2a2e377c020e57747b70502c51fd0b6349 (patch) | |
| tree | 958f360c0d6729c98db9ca6ad70ae8b218453a95 /guides/source/i18n.md | |
| parent | 07a3c2103c0db8f960ea2ba2a8748a2fe2bed206 (diff) | |
| download | rails-c7d39f2a2e377c020e57747b70502c51fd0b6349.tar.gz rails-c7d39f2a2e377c020e57747b70502c51fd0b6349.tar.bz2 rails-c7d39f2a2e377c020e57747b70502c51fd0b6349.zip | |
Fix truncated line in the i18n edge guide
Diffstat (limited to 'guides/source/i18n.md')
| -rw-r--r-- | guides/source/i18n.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/guides/source/i18n.md b/guides/source/i18n.md index a3c6b514a4..e18a0278bc 100644 --- a/guides/source/i18n.md +++ b/guides/source/i18n.md @@ -94,7 +94,7 @@ This means, that in the `:en` locale, the key _hello_ will map to the _Hello wor The I18n library will use **English** as a **default locale**, i.e. if you don't set a different locale, `:en` will be used for looking up translations. -NOTE: The i18n library takes a **pragmatic approach** to locale keys (after [some discussion](http://groups.google.com/group/rails-i18n/browse_thread/thread/14dede2c7dbe9470/80eec34395f64f3c?hl=en), including only the _locale_ ("language") part, like `:en`, `:pl`, not the _region_ part, like `:en-US` or `:en-GB`, which are traditionally used for separating "languages" and "regional setting" or "dialects". Many international applications use only the "language" element of a locale such as `:cs`, `:th` or `:es` (for Czech, Thai and Spanish). However, there are also regional differences within different language groups that may be important. For instance, in the `:en-US` locale you would have $ as a currency symbol, while in `:en-GB`, you would have £. Nothing stops you from separating regional and other settings in this way: you just have to provide full "English - United Kingdom" locale in a `:en-GB` dictionary. Various [Rails I18n plugins](http://rails-i18n.org/wiki) such as [Globalize2](ht) +NOTE: The i18n library takes a **pragmatic approach** to locale keys (after [some discussion](http://groups.google.com/group/rails-i18n/browse_thread/thread/14dede2c7dbe9470/80eec34395f64f3c?hl=en), including only the _locale_ ("language") part, like `:en`, `:pl`, not the _region_ part, like `:en-US` or `:en-GB`, which are traditionally used for separating "languages" and "regional setting" or "dialects". Many international applications use only the "language" element of a locale such as `:cs`, `:th` or `:es` (for Czech, Thai and Spanish). However, there are also regional differences within different language groups that may be important. For instance, in the `:en-US` locale you would have $ as a currency symbol, while in `:en-GB`, you would have £. Nothing stops you from separating regional and other settings in this way: you just have to provide full "English - United Kingdom" locale in a `:en-GB` dictionary. Various [Rails I18n plugins](http://rails-i18n.org/wiki) such as [Globalize2](https://github.com/joshmh/globalize2/tree/master) may help you implement it. The **translations load path** (`I18n.load_path`) is just a Ruby Array of paths to your translation files that will be loaded automatically and available in your application. You can pick whatever directory and translation file naming scheme makes sense for you. |