> My initial db schema simply has a resource table which stores multiple > versions of all text from my product and other tables. So my product > table would simply reference the resource table for the product name, > for example. Language could be stored in a session variable or in the > URL.
Globalize has *one* translation table. You're handling the different languages by switching the locale. You have to specify which model attributes you want to have translated. The original models have the default language as an attribute. Didn't play with fall-back scenarios (in case you don't provide a translation), but I guess that the default language is used for that. Since the translation all go into a generic attribute table (or however you call that) I'm not sure sure about performace impact. Don't know if caching mechanism come into play. Didn't take a look at GLoc yet. But since the authors of both projects reading this list, they can answer more precise. -- Posted via http://www.ruby-forum.com/. _______________________________________________ Railsi18n-discussion mailing list [email protected] http://rubyforge.org/mailman/listinfo/railsi18n-discussion
