diff options
| author | karmi <karel.minarik@gmail.com> | 2009-02-04 04:10:08 -0700 |
|---|---|---|
| committer | karmi <karel.minarik@gmail.com> | 2009-02-04 04:10:08 -0700 |
| commit | e0d79fbf041033b5dc97aaf2df8a84fefdb91470 (patch) | |
| tree | 537b4b6f5ad37e8cb3da3d75eeb01480f8e550f2 /railties/guides | |
| parent | 1ca565a16a6f966ba9f434b439c385b492a716df (diff) | |
| download | rails-e0d79fbf041033b5dc97aaf2df8a84fefdb91470.tar.gz rails-e0d79fbf041033b5dc97aaf2df8a84fefdb91470.tar.bz2 rails-e0d79fbf041033b5dc97aaf2df8a84fefdb91470.zip | |
Fixed the wrong currency symbol in the i18n guide
Diffstat (limited to 'railties/guides')
| -rw-r--r-- | railties/guides/source/i18n.textile | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/railties/guides/source/i18n.textile b/railties/guides/source/i18n.textile index ec02c5aeb6..53a0cc2834 100644 --- a/railties/guides/source/i18n.textile +++ b/railties/guides/source/i18n.textile @@ -91,7 +91,7 @@ This means, that in the +:en+ locale, the key _hello_ will map to _Hello world_ The I18n library will use *English* as a *default locale*, ie. if you don't set a different locale, +:en+ will be used for looking up translations. -NOTE: The i18n library takes *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-UK+, which are traditionally used for separating "languages" and "regional setting" or "dialects". (For instance, in the +:en-US+ locale you would have $ as a currency symbol, while in +:en-UK+, you would have €. Also, insults would be different in American and British English :) Reason for this pragmatic approach is that most of the time, you usually care about making your application available in different "languages", and working with locales is much simpler this way. However, nothing stops you from separating regional and other settings in the traditional way. In this case, you could eg. inherit from the default +en+ locale and then provide UK specific settings in a +:en-UK+ dictionary. +NOTE: The i18n library takes *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-UK+, which are traditionally used for separating "languages" and "regional setting" or "dialects". (For instance, in the +:en-US+ locale you would have $ as a currency symbol, while in +:en-UK+, you would have £. Also, insults would be different in American and British English :) Reason for this pragmatic approach is that most of the time, you usually care about making your application available in different "languages", and working with locales is much simpler this way. However, nothing stops you from separating regional and other settings in the traditional way. In this case, you could eg. inherit from the default +en+ locale and then provide UK specific settings in a +:en-UK+ dictionary. 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. |