Hi Tim, Your first proposal makes a lot of sense, and should be easier if we add a SUPPORTED_LANGUAGES = [ 'en', 'es' ] type constant. We're thinking of adding something like that anyway for other features.
I didn't understand your second question. Why do you need to have actual records in globalize_translation for a model if there's no translation for that model in the given language? What's the connection to view translations? Best, Josh On 10/22/06, Tim Alexeevsky <[EMAIL PROTECTED]> wrote: > Hello! > > I'm going to use Globalize in my app. While playing with Globalize I > tried translation view example from globalize-rails.org. I like the way > those things work -- text appears in translator's view (and also in > globalize_translations table) after it is first time requested by app. > Anyway there are some rough edges. Here are the ones that bother me > more: > 1. When a text is requested by application record dedicated to it's > translation is put for current language only. My application should use > only 5 languages and it seem reasonable for me to create empty > translations for all languages simultaneously. > 2. Model translations seem to be created only when such translation is > saved. I think it will be useful to have empty model translations > created automatically as view translations or to be created > simultaneously for all languages after a record in translatable table is > created. > My questions are: > What is supposed/prefered/recomended way to organize translators > workplace with Globalize? Is it supposed to manage already created > records in globalize_translations or it should create records by itself > based on translatable tables? > Can described behaviors be achieved using current version of > Globalize? If not, probably someone could give me some hints of how to > fix Globalize to work this way? > > Tim > > -- > Posted via http://www.ruby-forum.com/. > _______________________________________________ > Railsi18n-discussion mailing list > Railsi18n-discussion@rubyforge.org > http://rubyforge.org/mailman/listinfo/railsi18n-discussion > _______________________________________________ Railsi18n-discussion mailing list Railsi18n-discussion@rubyforge.org http://rubyforge.org/mailman/listinfo/railsi18n-discussion
