Internationalization in edge Rails and more
Posted by Chu Yeow July 20, 2008 @ 11:38 AM
There won’t be a Living on the Edge this week, but you won’t be starved for info because the Rails community is keeping up.
Ryan Daigle has been keeping up with some of the changes on edge Rails and has done a few awesome explanatory posts on them:
- Easy memoization with ActiveSupport::Memoizable
- Nested model mass assignments
- Metaclass accessor (aka the eigenclass)
Perhaps even more noteworthy is the introduction of I18n (internationalization) support to Rails core. Sven Fuchs explains the technical details and API as well as the history of Rails and I18n. I18n support is scheduled to be fully stable in the Rails 2.2 release. Have an interest in internationalization in Rails? Lend a hand with your ideas, feedback, and patches at the Google Group.
Internationalization in the Rails core is very good news. Maybe I switch to Edge these days…
Is it true, that Rails 2.2 is targeted for September already?
I18n in Rails is really good news. I’m looking for forward to giving it a whirl.
why not Globalize-rails directly?
Hey assente,
although a couple of Globalize devs were involved with this the final result actually could barely be more different from what Globalize is/was … :)
But, taking the question serious. The reason is that we didn’t want a L10n solution in Rails core (at least: not yet, maybe never). We wanted a common I18n api to build on.
2 questions, is this available to us now in the form of a plugin?
and secondly when is a “planned” release of this for rails 2.2, if we cant get in plugin form now, then it would be great to know when we can use it
Awesome news. As a Netherlands-based developer this is something that will be immediately and definitely helpful.
@carlity: The only way to get and use this new functionality is to use edge rails itself
Active Record Single Table Inheritance doesn’t alias tables nicely so that if you’re trying to disambiguate between fieldnames in the conditions hash, it’s impossible. It’d be nice to add that feature. (ie Person and Business inherit from Entity, and habtm each other, trying to do a search on Person name = “henry” and person’s business name include “spock” will fail because of ambiguity of tablenames…. let alone trying to search through included associations as well! (ie both of them have_many addresses, now how do I specify which “addresses” I want when searching??)