You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using _() (and others) are preferable to I18n.t as you don't have to explicitly set the separator. Currently these methods are provided via FastGettext's helpers, which are included globally.
The problem is these helpers do not really interact with I18n. So if have something like:
# I18n.backend is set to GettextI18nRails::Backend via this gemI18n.backend=I18n::Backend::Chain.new(I18n::Backend::KeyValue.new($redis),I18n.backend)
One must say:
I18n.ttext,:separator=>"|"
To take advantage of the chain.
Instead of including FastGettext::Translation, why not include I18n::Gettext::Helpers instead? Then _() will work out the box for situations like the above.
The text was updated successfully, but these errors were encountered:
Using
_()
(and others) are preferable toI18n.t
as you don't have to explicitly set the separator. Currently these methods are provided viaFastGettext
's helpers, which are included globally.The problem is these helpers do not really interact with
I18n
. So if have something like:One must say:
To take advantage of the chain.
Instead of including
FastGettext::Translation
, why not includeI18n::Gettext::Helpers
instead? Then_()
will work out the box for situations like the above.The text was updated successfully, but these errors were encountered: