I'm getting into this a bit late, but Globalize was designed to handle this. Globalize automatically tries to translate ActiveRecord validation messages, so if you trigger a validation error, that message should show up in the globalize_translations table and be available for translation. Because Globalize's string substitution isn't quite as sophisticated as we want it to be, it can't translate field names separately from the validation message. This means you have to translate all combination of field name/validation type. In many apps this isn't that big a problem, but if it is in your case, let us know. This would be a good thing to write up a ticket for.
-- Josh On 10/19/06, Nicolas Niconoe <[EMAIL PROTECTED]> wrote: > bal wrote: > > Nicolas Noé wrote: > > > > [...] > > > >> As I'm new to rails and have an applic to develop and maintain, I was > >> afraid that maybe gettext could cause other problems later and impeach > >> me of using all rails features...For the moment it's ok, I found another > >> way to solve my problem. > > > > How have You solved that problem? Have You found method to translate > > fields and class names in Globalize? > > No, I continued to used gettext... > > -- > Posted via http://www.ruby-forum.com/. > _______________________________________________ > Railsi18n-discussion mailing list > Railsi18nemail@example.com > http://rubyforge.org/mailman/listinfo/railsi18n-discussion _______________________________________________ Railsi18n-discussion mailing list Railsi18nfirstname.lastname@example.org http://rubyforge.org/mailman/listinfo/railsi18n-discussion