stouset/twitter_bootstrap_form_for — Issue #26: Support for i18n?
Author: derekprior
Created: 2011-11-17 18:46:42+00:00
State: open

It seems that the standard form builder methods support i18n just fine. The `inputs` and `inline_inputs` methods do not, however. Would it be worth adding some i18n to those methods inside the gem, or should the user be forced to call t() in the view? I'm still becoming familiar with the i18n API myself, so I'm not sure how this is usually handled.

If tackle it in the gem is desired, I think the simplest way might be to just call translate when those methods try to throw down a label. That works fine if you pass, say, a symbol as the label. That'd be a clear indication that you'd want translation done. What about the case where the user passes a string as the label (i.e. `'fieldsets.user_information'`)? How would we know if they want that translated or if they want to render that string directly?

Is there a standard practice for this? simple_form leverages the existing standard location for label translations (helpers.label.model.field) but they do not introduce new elements.