If it is a small rails app then it might be worth porting it to rails 3.1. The asset pipeline makes it simple to stick a .erb on the end of the file and get the file preprocessed to include your I18n tag values. If the shift to 3.1 is too much you could look at bringing in just sprockets.
Cheers, Adam On 19/09/2011, at 9:11 AM, Ben Taylor wrote: > Hey Guys, > > I've just been tasked with internationalising a small Rails app. It's > intended for use by users on mobile devices and is very client side heavy. > The Rails server acts as an API to some backbone code which does most of the > work. > > I'm about to read through http://guides.rubyonrails.org/i18n.html which I > think will help, but my bigger problem is that I have strings hard coded into > the JS. Any ideas/thoughts/pro tips? > > Cheers, > - Ben > > -- > You received this message because you are subscribed to the Google Groups > "Ruby or Rails Oceania" 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/rails-oceania?hl=en. -- You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" 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/rails-oceania?hl=en.
