# I18n\_routing: Easy routes translations for Rails 2.x And Rails3

**URL:** <https://www.ruby-forum.com/t/i18n-routing-easy-routes-translations-for-rails-2-x-and-rails3/186454>\
**Category:** Rails I18n\
**Created:** [April 7, 2010, 12:31pm UTC](https://www.ruby-forum.com/t/i18n-routing-easy-routes-translations-for-rails-2-x-and-rails3/186454 "2010-04-07T12:31:41Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![kwi](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/k/77aa72/32.png) [@kwi](https://www.ruby-forum.com/u/kwi)\
**Post date:** [April 7, 2010, 12:31pm UTC](https://www.ruby-forum.com/t/i18n-routing-easy-routes-translations-for-rails-2-x-and-rails3/186454/1 "2010-04-07T12:31:41Z")

</div>

Hi everyone,

Last week, I have finaly pushed my plugin that do Rails routing  
translation on github.  
It’s based on top of I18n api and it works with Rails 2 and Rails 3 !

I currently use it in production on several Rails 2 projects.

The usage is extremly simple, juste declare your routes in a localized  
block, like this :

localized do  
resources :users  
end

There is a last thing I need to do : making the plugin compatible with  
deep nested resources 😕

The github : [GitHub - kwi/i18n\_routing: I18n routing module for Rails 2.3.x and Rails 3. Translate your routes with ease !](http://github.com/kwi/i18n_routing)

Hope to read your feedbacks, advices, and comments soon ! And for  
sure, feel free to get involve !

Thanks

(It’s have been tested on Rails 2.3.5, Rails3 beta and Rails3 edge)

---

<div class="post-metadata">

**Author:** ![kwi](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/k/77aa72/32.png) [@kwi](https://www.ruby-forum.com/u/kwi)\
**Post date:** [April 7, 2010, 3:19pm UTC](https://www.ruby-forum.com/t/i18n-routing-easy-routes-translations-for-rails-2-x-and-rails3/186454/2 "2010-04-07T15:19:40Z")

</div>

The README of your plugin could use some examples 😉

Greetings,  
Juergen

---

<div class="post-metadata">

**Author:** ![kwi](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/k/77aa72/32.png) [@kwi](https://www.ruby-forum.com/u/kwi)\
**Post date:** [April 7, 2010, 3:30pm UTC](https://www.ruby-forum.com/t/i18n-routing-easy-routes-translations-for-rails-2-x-and-rails3/186454/3 "2010-04-07T15:30:12Z")

</div>

Yes, you got a point here 🙂

But I moved all examples in the Github Wiki, I will add simple  
examples in the README too !

On 7 avr, 15:14, “Jürgen Feßlmeier” [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)

---

<div class="post-metadata">

**Author:** ![kwi](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/k/77aa72/32.png) [@kwi](https://www.ruby-forum.com/u/kwi)\
**Post date:** [April 12, 2010, 7:19pm UTC](https://www.ruby-forum.com/t/i18n-routing-easy-routes-translations-for-rails-2-x-and-rails3/186454/4 "2010-04-12T19:19:02Z")

</div>

Hi again everyone.

Just to tell to interested people that I have finally fixed the nested  
resources issue on Rails2.  
And I have released a gem : i18n\_routing

By the way I have also released a new plugin for auto-scoping  
translations : [GitHub - kwi/i18n\_auto\_scoping: I18nAutoScoping lets you easily add auto-scope in your I18n translations for your Rails' views](http://github.com/kwi/i18n_auto_scoping)  
(i18n\_auto\_scoping gem)  
It’s really useful for your views, with it, you keep your translations  
simple and well organized.

Documentation is on the wiki.

Cheers.

---

<div class="post-metadata">

**Author:** ![kwi](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/k/77aa72/32.png) [@kwi](https://www.ruby-forum.com/u/kwi)\
**Post date:** [April 12, 2010, 11:16pm UTC](https://www.ruby-forum.com/t/i18n-routing-easy-routes-translations-for-rails-2-x-and-rails3/186454/5 "2010-04-12T23:16:08Z")

</div>

Hi Kwi,

I didn’t have to time to look inside your lib, only read github wiki,  
but isn’t that similar to i18n lazy-lookup  
[Rails Internationalization (I18n) API — Ruby on Rails Guides](http://guides.rubyonrails.org/i18n.html#lazy-lookup) ?

Regards,  
KK

2010/4/12 Kwi [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid):

---

<div class="post-metadata">

**Author:** ![kwi](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/k/77aa72/32.png) [@kwi](https://www.ruby-forum.com/u/kwi)\
**Post date:** [April 13, 2010, 1:59pm UTC](https://www.ruby-forum.com/t/i18n-routing-easy-routes-translations-for-rails-2-x-and-rails3/186454/6 "2010-04-13T13:59:28Z")

</div>

Hi  
How to use ParseDate in a localized way so the user can input a date  
in any local format (e.g. in se 3/12/75 or TIsdag, 2:a juni 1965t)  
that still can be parsed by ParseDate

---

<div class="post-metadata">

**Author:** ![kwi](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/k/77aa72/32.png) [@kwi](https://www.ruby-forum.com/u/kwi)\
**Post date:** [April 7, 2010, 3:54pm UTC](https://www.ruby-forum.com/t/i18n-routing-easy-routes-translations-for-rails-2-x-and-rails3/186454/7 "2010-04-07T15:54:12Z")

</div>

Looks great!!

2010/4/7 Kwi [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)

> > Greetings,
> > 
> > > I currently use it in production on several Rails 2 projects.
> > 
> > > You received this message because you are subscribed to the Google

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

---

<div class="post-metadata">

**Author:** ![kwi](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/k/77aa72/32.png) [@kwi](https://www.ruby-forum.com/u/kwi)\
**Post date:** [April 13, 2010, 6:37pm UTC](https://www.ruby-forum.com/t/i18n-routing-easy-routes-translations-for-rails-2-x-and-rails3/186454/8 "2010-04-13T18:37:38Z")

</div>

Hi Krzysztof,

My mistake, you are right, after testing, the lazy-lookup do pretty  
the same as my plugin.  
I need to pay more attention at documentation before spending time  
coding ! Good to know anyway 😕

Thanks

On Apr 12, 11:15 pm, Krzysztof K. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)
