> Here the translation itself contains no html, but the developer are
> still required to name it welcome_html to make it work.
>
> In this context, the reasoning mentioned above does not make sense
> anymore.
>
>
> Should I just add "_html" to translations that I assume I might use
> for interpolation, or am I solving the problem (of showing "Hello
> [user_link])" the wrong way? Or should t() be changed to accommodate
> this problem?
You could also wrap your translate call in raw:
raw(t('welcome_message', :user => link_to(user.name, user)))
I don't think there's a nicer fix to this without making the i18n stuff
deeply aware of the xss escaping. Calling raw or using _html in the key
name seems like a reasonable solution.
--
Cheers,
Koz
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" 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/rubyonrails-core?hl=en.
