-
Notifications
You must be signed in to change notification settings - Fork 0
Cascading Backend for Ruby/Rails i18n
License
clemens/i18n-cascading-backend
Folders and files
Name | Name | Last commit message | Last commit date | |
---|---|---|---|---|
Repository files navigation
Cascading Backend for Ruby i18n =============================== The Cascading Backend allows for, well, cascaded lookups. This is especially useful if you want to have some general translations that you only want to override for some locales in more concrete uses. Example ======= Say, you have the following structure in your locale file: :en => { :title => 'Title', :article => { :title => 'Article title' }, :topic => {} }, :de => { :title => 'Titel', :article => {}, :topic => { :title => 'Thema' } } You have some general translation for :title that you usually want to use. The English locale then defines a custom translation for article titles and the German translation defines one for topic titles. With the Cascading backend, you get the following results: I18n.translate(:title, :locale => :en) # => "Title" I18n.translate(:title, :locale => :de) # => "Titel" I18n.translate(:'article.title', :locale => :en) # => "Article title" I18n.translate(:'article.title', :locale => :de) # => "Titel" I18n.translate(:'topic.title', :locale => :en) # => "Title" I18n.translate(:'topic.title', :locale => :de) # => "Thema" If you make use of I18n's :default mechanism, your own defaults take precedence over the cascaded ones: I18n.translate(:'topic.title', :default => 'Topic title', :locale => :en) # => "Topic title" Feedback ======== Feel free to send me any feedback you might have and also feel free to fork away! ;-) Copyright (c) 2009 Clemens Kofler <[email protected]>, www.railway.at, released under the MIT license
About
Cascading Backend for Ruby/Rails i18n
Resources
License
Stars
Watchers
Forks
Releases
No releases published
Packages 0
No packages published