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 %[email protected]> wrote: > 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, ... -- You received this message because you are subscribed to the Google Groups "rails-i18n" 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/rails-i18n?hl=en.
