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 : 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)
on 2010-04-07 12:31
on 2010-04-07 15:19
The README of your plugin could use some examples ;-) Greetings, Juergen
on 2010-04-07 15:30
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" <jfesslme...@googlemail.com>
on 2010-04-07 15:54
Looks great!! 2010/4/7 Kwi <firstname.lastname@example.org> > > 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.
on 2010-04-12 19:19
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 : 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.
on 2010-04-12 23:16
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 http://guides.rubyonrails.org/i18n.html#lazy-lookup ? Regards, KK 2010/4/12 Kwi <email@example.com>:
on 2010-04-13 13:59
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
on 2010-04-13 18:37
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 Knapik <krzysztof.kna...@gmail.com>