# Globalize2 advice needed

**URL:** <https://www.ruby-forum.com/t/globalize2-advice-needed/183118>\
**Category:** Rails I18n\
**Created:** [February 8, 2010, 1:57pm UTC](https://www.ruby-forum.com/t/globalize2-advice-needed/183118 "2010-02-08T13:57:58Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![cmaxvv](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/85f322/32.png) [@cmaxvv](https://www.ruby-forum.com/u/cmaxvv)\
**Post date:** [February 8, 2010, 1:57pm UTC](https://www.ruby-forum.com/t/globalize2-advice-needed/183118/1 "2010-02-08T13:57:58Z")

</div>

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](http://github.com/joshmh/globalize2#readme)) which isn’t very in-depth.

Does most of the documentation for globalize (eg  
[http://globalize-rails.org/wikipages/getting-started#install](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](http://guides.rubyonrails.org/i18n.html))

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

---

<div class="post-metadata">

**Author:** ![cmaxvv](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/85f322/32.png) [@cmaxvv](https://www.ruby-forum.com/u/cmaxvv)\
**Post date:** [February 8, 2010, 2:44pm UTC](https://www.ruby-forum.com/t/globalize2-advice-needed/183118/2 "2010-02-08T14:44:04Z")

</div>

On Mon, Feb 8, 2010 at 13:57, Max W. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) 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](http://github.com/joshmh/globalize2#readme)) 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](http://github.com/iain/translatable_columns/) for  
that. For translations in controllers, views, mailers, helpers etc,  
i18n is all you need.

---

<div class="post-metadata">

**Author:** ![cmaxvv](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/85f322/32.png) [@cmaxvv](https://www.ruby-forum.com/u/cmaxvv)\
**Post date:** [February 8, 2010, 4:52pm UTC](https://www.ruby-forum.com/t/globalize2-advice-needed/183118/3 "2010-02-08T16:52:46Z")

</div>

Henrik — wrote:

> On Mon, Feb 8, 2010 at 13:57, Max W. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) 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](http://github.com/joshmh/globalize2#readme)) 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](http://github.com/iain/translatable_columns/) 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.](http://github.com/raul/translate_routes)) for handling my urls. Looks  
good.

cheers, max

---

<div class="post-metadata">

**Author:** ![cmaxvv](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/85f322/32.png) [@cmaxvv](https://www.ruby-forum.com/u/cmaxvv)\
**Post date:** [February 8, 2010, 6:12pm UTC](https://www.ruby-forum.com/t/globalize2-advice-needed/183118/4 "2010-02-08T18:12:28Z")

</div>

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. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)

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

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

---

<div class="post-metadata">

**Author:** ![cmaxvv](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/85f322/32.png) [@cmaxvv](https://www.ruby-forum.com/u/cmaxvv)\
**Post date:** [February 9, 2010, 7:57pm UTC](https://www.ruby-forum.com/t/globalize2-advice-needed/183118/5 "2010-02-09T19:57:18Z")

</div>

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

> **[GitHub - janne/model\_translations: Minimal implementation of Globalize2 style...](https://github.com/janne/model_translations)**
>
> Minimal implementation of Globalize2 style model translations - GitHub - janne/model\_translations: Minimal implementation of Globalize2 style model translations

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

---

<div class="post-metadata">

**Author:** ![cmaxvv](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/85f322/32.png) [@cmaxvv](https://www.ruby-forum.com/u/cmaxvv)\
**Post date:** [February 8, 2010, 6:25pm UTC](https://www.ruby-forum.com/t/globalize2-advice-needed/183118/6 "2010-02-08T18:25:54Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![cmaxvv](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/85f322/32.png) [@cmaxvv](https://www.ruby-forum.com/u/cmaxvv)\
**Post date:** [February 10, 2010, 10:07am UTC](https://www.ruby-forum.com/t/globalize2-advice-needed/183118/7 "2010-02-10T10:07:18Z")

</div>

Thanks grimen!
