I don't understand why you specify I18n in the view_form generator.
Rails can handle this. It causes some problem for me, because it doesn't use the standard api in rails 3, ie. human_attribute_name.
In my case I have a model inside a module, so the code is looking for module/model in my yml file when rails is looking for module.model. I can override the translation module/model but I will translate my attribute twice, which is not DRY.
It can even look into views.labels.model.attribute, so I don't think you need to specify i18n manually.
I don't understand why you specify I18n in the view_form generator.
Rails can handle this. It causes some problem for me, because it doesn't use the standard api in rails 3, ie. human_attribute_name.
In my case I have a model inside a module, so the code is looking for module/model in my yml file when rails is looking for module.model. I can override the translation module/model but I will translate my attribute twice, which is not DRY.
It can even look into views.labels.model.attribute, so I don't think you need to specify i18n manually.