How to have both {{ and %{ placeholders replaced?
30 views
Skip to first unread message
StuFF mc (.com)
Jul 31, 2011, 12:13:05 PM7/31/11
to rails-i18n
Hi,
I'm working on a Rails app I didn't touched since a year ;) It's a
2.3.8 app, and my first surprise was to see things like
{{count}} errors prohibited this {{model}} from being saved
There were problems with the following fields:
{{attribute}} {{message}}
Apparently {{ aren't replaced anymore since %{ is the newer syntax.
Turns out I used %{ as well, probably because I red about having to
use it as the "new standard", but most of those {{ are from Rails
itself. Is there an option to have both replaced or should I use an
older gem, or, or or, ...
I'm working on a Rails app I didn't touched since a year ;) It's a
2.3.8 app, and my first surprise was to see things like
{{count}} errors prohibited this {{model}} from being saved
There were problems with the following fields:
{{attribute}} {{message}}
Apparently {{ aren't replaced anymore since %{ is the newer syntax.
Turns out I used %{ as well, probably because I red about having to
use it as the "new standard", but most of those {{ are from Rails
itself. Is there an option to have both replaced or should I use an
older gem, or, or or, ...
StuFF mc (.com)
Jul 31, 2011, 1:04:19 PM7/31/11
to rails-i18n
Folks, FYI... Using 2.3.11 instead of 2.3.8 seems to solve the
problem. What's also totally unclear for me is *how* the i18n gem is
"required". I removed it, and it still works. One of my idea was to
use and old i18n gem, but I didn't even have to do so, as using Rails
2.3.11 seems to fix the problem.
I need to mention that it's not a "production" app, it's an app I have
to have running in the state in which it was a year ago, so it's
really not a bad thing (actually a good one) if I'm running with an
old i18n gem - or for that matter with rails 2
On Jul 31, 6:13 pm, "StuFF mc (.com)" <mc
problem. What's also totally unclear for me is *how* the i18n gem is
"required". I removed it, and it still works. One of my idea was to
use and old i18n gem, but I didn't even have to do so, as using Rails
2.3.11 seems to fix the problem.
I need to mention that it's not a "production" app, it's an app I have
to have running in the state in which it was a year ago, so it's
really not a bad thing (actually a good one) if I'm running with an
old i18n gem - or for that matter with rails 2
On Jul 31, 6:13 pm, "StuFF mc (.com)" <mc
Henrik Nyh
Jul 31, 2011, 1:10:18 PM7/31/11
to rails...@googlegroups.com
As I understand it, i18n is bundled in Rails, but if you have a newer
i18n gem outside Rails, it picks that one up instead.
i18n gem outside Rails, it picks that one up instead.
> --
> You received this message because you are subscribed to the Google Groups "rails-i18n" group.
> To post to this group, send email to rails...@googlegroups.com.
> To unsubscribe from this group, send email to rails-i18n+...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/rails-i18n?hl=en.
>
>
Reply all
Reply to author
Forward
0 new messages