Globalize2 advice needed

Rails Rails I18n
1

Hey all

I’m doing my first i18n app in rails 2.3.4. I installed the globalize2
plugin and am now struggling to understand what’s going on - there’s not
much documentation i can see for globalize2 besides the home page
(GitHub - joshmh/globalize2: The second incarnation of Globalize for Rails) which isn’t very in-depth.

Does most of the documentation for globalize (eg
http://globalize-rails.org/wikipages/getting-started#install) apply?
Globalize2 says it hooks into i18n which comes shipped with rails post
2.2, so should i just be following the i18n documentation instead?
(Rails Internationalization (I18n) API — Ruby on Rails Guides)

Do i even need to use globalize2? Is it better to just stick with rails
built in i18n? Globalize doesn’t seem to be compatible with rails 2.2.

Kind of confused, basically, grateful for any advice.

thanks, max

2

On Mon, Feb 8, 2010 at 13:57, Max W. [email protected] wrote:

Hey all

I’m doing my first i18n app in rails 2.3.4. I installed the globalize2
plugin and am now struggling to understand what’s going on - there’s not
much documentation i can see for globalize2 besides the home page
(GitHub - joshmh/globalize2: The second incarnation of Globalize for Rails) which isn’t very in-depth.

The built-in i18n does a lot. I think all Globalize2 adds is model
translations (translating attributes like item.description or
whatever). I prefer GitHub - iain/translatable_columns: Provides proxies for localized columns, depending on the locale set by I18n for
that. For translations in controllers, views, mailers, helpers etc,
i18n is all you need.

3

Henrik — wrote:

On Mon, Feb 8, 2010 at 13:57, Max W. [email protected] wrote:

Hey all

I’m doing my first i18n app in rails 2.3.4. �I installed the globalize2
plugin and am now struggling to understand what’s going on - there’s not
much documentation i can see for globalize2 besides the home page
(GitHub - joshmh/globalize2: The second incarnation of Globalize for Rails) which isn’t very in-depth.

The built-in i18n does a lot. I think all Globalize2 adds is model
translations (translating attributes like item.description or
whatever). I prefer GitHub - iain/translatable_columns: Provides proxies for localized columns, depending on the locale set by I18n for
that. For translations in controllers, views, mailers, helpers etc,
i18n is all you need.

Thanks Henrik. I ended up ditching globalize2 and just using I18n. I’m
currently looking at the translate routes plugin
(GitHub - raul/translate_routes: Rails plugin to translate your URLs and routing helpers on an clean way.) for handling my urls. Looks
good.

cheers, max

4

My advise is: First learn I18n and then learn Translate routes o
Globalize.
Step by step. I’m newbe too

2010/2/8 Max W. [email protected]

translations (translating attributes like item.description or
–
http://groups.google.com/group/rails-i18n?hl=en.

–
Experiencia es lo que obtienes, cuando no obtienes lo que quieres.

5

Yes, totally. Globalize2 just messed up things for me when I tried it
a year ago, so I successfully rolled with

instead which together with I18n and minor tweaks do what Globalize 2
do. Globalize 1 made sense, Globalize 2 is not - I would state.

grimen

6

Hi Andres, i think you’re right. The translate_routes plugin is great
btw. Not only does it seamlessly prefix the country code into the url
but also it translates the url if it finds a translated section. So you
would have

/my-account

in english, and

/de/mein-konto

in german, with no work required other than putting an entry for
my-account into your strings file. In your code you still just refer to
it as “account_path” or whatever.

7

Thanks grimen!