Rationale: the I18n::Backend part of this library is designed to provide various modules that can be included into the I18n::Backend::Simple backend or other compatible backend implementations and thereby extend their functionality in an optional manner. Thus, both code and documentation have been cluttered with lots of calls sending :include to the Simple backend class. It seems that we in fact treat sending include as a public API of the Simple backend class and therefor should make it public.
…mount of methods required to implement a functional backend.
…easier to overwrite methods in Base from included modules
… Simple from Base. (making it easier to include modules to overwrite parts of the functionality) (inspired by http://github.com/abriening)
…ry. (thanks to http://github.com/abriening)
…nArgument exception to wrap Ruby 1.9's KeyError
…nterpolate is more self-contained)
…nary otherwise. Signed-off-by: Sven Fuchs <firstname.lastname@example.org>
…sub! instead of gsub)
…m scope separator (e.g. I18n.t(:'foo|bar', :separator => '|')
…d which made the backend break on Ruby 1.9.
…ations are available)
…able to store false values (and not confuse them with nil) http://github.com/rails/rails/commit/d69b4b7bea28fcab04f61afe381e06fa8e37b429
…move #load_translations from public api