Hi, actually this is not supported, the way would be to put the common attribute in _all .
Will try to implement this :) On Dec 2, 5:34 pm, stonefield <[EMAIL PROTECTED]> wrote: > Diego, > > If you mean: > "no-BM": > attributes: > _all: > name: Navn > comment: Kommentar > Is the structure? That is fine! > > - Will it also support this? > class Vehicle < ActiveRecord::Base > end > class Car < Vehicle > end > > "no-BM": > attributes: > vehicle: > name: Navn > > Car.human_attribute_name(:name) => Navn > > On Dec 1, 2:38 pm, Diego Carrion wrote: > > > Hi, now the plugin (thanks to Charles Bedard for the tip) do his work > > at the human_attribute_name method from ActiveRecord::Base. This way > > the I18n.translate method stays intact and don't have to veryfy if the > > key contains activerecord.attributes on every call. > > > Anybody sees a problem with this? > > > At other hand, I have been receiving emails about the common attribute > > and as suggested I changed it to _all . > > > Is that ok for everyone? > > > On Nov 29, 10:38 pm, stonefield <[EMAIL PROTECTED]> wrote: > > > > First thing first. > > > a) It is mandatory that attribute names/translations can be inherited. > > > Secondly... > > > b) It us a good idea that it is possible to define common names that > > > are used across models. Whether default, common or _all is used, is > > > less important than the feature it selves. Personally I would prefer > > > common-attributes: ... > > > > Thanks for bringing up this topic guys. > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "rails-i18n" 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/rails-i18n?hl=en -~----------~----~----~----~------~----~------~--~---
