> The end user could then choose to use any i18n > plugin he wants, and everything would be available for translation > with no monkey-patching needed. This in itself would be a huge step, > and I don't see a lot of downside. Localizing dates and countries > could also be done much the same way.
I don't quite follow how adding a String#t no-op helps the localization plugins? Could you explain that a bit more please? -- Cheers Koz --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
