> Not sure. I think this largely depends on how many views you want to > translate. If there are only some (e.g. ActionMailer notification > views) that you want to translate as a whole while everything else > uses the usual way of translating with I18n.t then having an extra > directory seems like overkill to me ... and the current implementation > much nicer. > > Why not ship the current implementation as a simple way with Rails > core and still have José's plugin available for people who want to > rely on this approach for most of their views? Do these approaches > necessarily clash?
Agree with Sven. The current approach is an extraction from how I was translating Basecamp. The vast majority of pages would be translated inline with <%= t %> calls, but a handful of pages, like a help screen or a blank slate, was easier to translate in its entirety. The current approach is meant as a companion for an application that's mostly using the <%= t %> approach to translation, but just has a few complete translations. If that pattern doesn't fit your translation style and you'd rather translate every single view in its entirety, then I think the localized templates plugin is a fine approach to continue using. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
