>> For pluralization there could be a similar helper. This should >> work for all messages that do not contain a dot. I wonder if we >> can get rid of this limitation. Approaches that come to my mind: >> >> 1. Make the scope separator (dot) configurable. That might mean >> that Rails core should not continue using dots as separators (but >> instead just use Arrays for scopes). >> 2. Escape/unescape dots in the helper. >> 3. ? > > Sounds complicated...
Btw I've just pushed some experiments with gettext'ish accessors on top of Rails I18n: http://github.com/svenfuchs/i18n/tree/gettext You might particularly want to look at the helper layer and the tests: http://github.com/svenfuchs/i18n/blob/49220ce667fe542041c97bd38a0190e27a9581d6/lib/i18n/gettext.rb http://github.com/svenfuchs/i18n/blob/49220ce667fe542041c97bd38a0190e27a9581d6/test/gettext_test.rb For a fullstack gettext support that uses the Rails I18n API there seem to be three things missing: - complete the helpers (trivial) - implement a gettext backend (anybody?) - figure out a gettext'ish way to announce expected translations for computed keys Any help and/or feedback would be appreciated! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
