On Mon, May 3, 2010 at 3:06 AM, oren <[email protected]> wrote: > Thanks Walter. > Kete looks like an awesome project.
Thanks. It's been good to work on and useful. > > It looks like the simplest solution for me would be to add language_id > field to my content table and maybe later on > I'll refactor it to other solution. I usually store locale in the table for the content without splitting out to a languages (or locales) table and storing a locale_id. Rails only stores i18n.locale as a symbol. I haven't had a need for tighter constraints on the data for locale than that. > mongo db sounds awesome, but I am > not sure where to start - the github page doesn't explain about > installing/using it. Yep, that's in the works. In the meantime, check out http://github.com/kete/mongo_translatable/tree/master/test/full_2_3_5_app_with_tests which is a full (but simple) Rail 2.3.5 app for testing purposes. You can dig around there, including the tests, to see the basics about how to mongo_translatable works. I'll get to the README before too long. Cheers, Walter -- 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 [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-talk?hl=en.
