> This view is shared by all of us, and as you can see, the patch by no > means forces you to do anything, > since you can override the method completely.
That's exactly my point, I should not have override anything, that's exactly what we are doing with Rails atm and the whole purpose of this patch is to add a no-op method as mentioned by Koz. I'm super busy at the moment and it's hard for me to find the time to write a no-op translation method covering all of 2.0 Since 2.0 PR is out, I would expect that until 2.0 final is released, the main focus would be on stabilizing and fixing the core, not adding new features. In the mean time, I'd love to hear from other people such as Chris Wanstrath from errtheblog author of Gibberish, Jeremy Voorhis (Globalize), DHH (author of a simple localization plugin ;)) and other developers using localization plugins / gettext. I don't see a big rush to get that api/hook implemented since most plugins work well, but maybe I'm wrong. -Matt --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
