On Wed, Mar 9, 2011 at 8:08 PM, Stefano <stefano....@gmail.com> wrote: > Thank you for your answer. I already have watched that railcast but he > really only talks about changing the backend. He doesnt compare the > options of storing pages in the DB or retrieving them from locale > files, thats what my question is mainly about I guess. > > Is it a good idea to store entire pages so possibly a lot of text in a > redis database or key driven storage? Or is it more to translate > little stuff like buttons, links, etc. >
Just to confuse things, a different Walter jumping in to talk about your questions. On the Kete (http://gitub.com/kete/kete and http://kete.net.nz) project we use a combination of approaches. Translations that are apart of the UI that are specified in templates are handled with the normal I18n backend, but the files themselves are managed via the /translate plugin (https://github.com/newsdesk/translate, though Kete's version is slightly modified) and the web interface. I often refer to these as "static" translations. When Kete is set up to also have content like topic pages be translatable, we store the topic the database and the translation for it in MongoDB using a gem we created call mongo_translatable (http://github.com/kete/mongo_translatable) which in turn uses mongo_mapper to talk to a MongoDB instance. mongo_translatable hasn't been packaged up and put on rubygems.org yet, so if you want to try it out, you'll have to install from source. It is working in production on http://chinesecommunity.org.nz at the moment though. It is meant to hook into existing Rails ActiveRecord backed models where you are already using a relational database as your data store. Now, if I was creating Kete from scratch at this point rather than late 2006, because of Kete's custom fields functionality and translations I would probably store the content models completely in something like MongoDB. If you do that, then something like https://github.com/ahe/mongo_translation might be more up your alley (or the Redis approach, I haven't looked at it). Cheers, Walter McGinnis -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
