Comments on: Translating Columns

By: Trond Lossius

Trond Lossius — Fri, 28 Nov 2008 08:18:50 +0000

Have you looked into the Globalize2 preview app? It is constructing the database differently, more in the way recommended by the chapter in the beta version of Agile Development ed.3 in internationalization.

By: Jan

Jan — Mon, 24 Nov 2008 05:32:50 +0000

1) since the named_scope uses a value that may change during requests (I18n.locale) it should read:
named_scope :localized, lambda { { :conditions => { :locale => I18n.locale } } }
2) With your own example (Post.localized.find(params[:id])) you gave a good reason to use the first variant. To find the same Post in another language params[:id] would have to be different. Which means you need to find out this other id for linking to the post in another language (common task). Which sucks.

By: Iain Hecker

Iain Hecker — Tue, 16 Sep 2008 15:23:20 +0000

@Dmitry: Rails tries to be more lean… Only features that are really really handy and often used get into the rails core.

By: Dmitry

Dmitry — Tue, 16 Sep 2008 14:02:52 +0000

@Iain Hecker: Thank you! Interesting post.

But why rails will not support this future in it’s own core? How do you think?

By: Plugin: translatable_columns • iain.nl

Plugin: translatable_columns • iain.nl — Sat, 06 Sep 2008 18:19:37 +0000

[...] 6th • Plugins, Ruby on Rails Category It was just three days ago when I discussed how to translate columns. At the moment I was writing it, I was already thinking: “this should be a plugin”. So [...]