This allows for views to display rather reasonable strings while still
giving developers a way to find missing translations.

If you would prefer missing translations to raise an error, you can opt out
of span-wrapping behavior globally by setting
ActionView::Base.raise_on_missing_translations = true or
individually by passing raise: true as an option to
translate.

Second, if the key starts with a period translate will scope
the key by the current partial. Calling
translate(".foo") from the
people/index.html.erb template is equivalent to calling
translate("people.index.foo"). This makes it less
repetitive to translate many keys within the same partial and provides a
convention to scope keys consistently.

Third, the translation will be marked as html_safe if the key
has the suffix “_html” or the last element of the key is “html”. Calling
translate("footer_html") or
translate("footer.html") will return an HTML safe
string that won't be escaped by other HTML helper methods. This naming
convention helps to identify translations that include HTML tags so that
you know what kind of output to expect when you call translate in a
template and translators know which keys they can provide HTML values for.