Hey Raul, On 20.09.2008, at 19:14, Raul Murciano wrote: > 2008/9/20 Sven Fuchs <[EMAIL PROTECTED]>: >> Although there are a couple of partial solutions [1] all of them have >> some kind of annoying shortcoming, be it that one can not use non- >> named, old-school routes with it or even has to pass lots of >> parameters to url_for in certain cases and none of them gave me the >> flexibility i wanted. > > Hi Sven, > > Please excuse my insistence - I wrote a message about this just > yesterday -
Apparently I've failed to read it thoroughly. I thought it's about translating path segments. Sorry about that. > but there is another solution which, as you propose, wraps > around the routing system and manages helpers on a very confortable > way: > > http://github.com/raul/translate_routes/ > > During the last months I've received some feedback from european and > latin-american developers and they are using it succesfully on > production environments, so it's a bit more mature than your > experimental suggestion. Maybe it could be a more solid base to build > on, what do you think about it? Very cool! :) I'll have to have a closer look at it. From what I grasp from the README one would use named route url_helpers like home_es_path to generate urls? Does this also work with the url_for helper? I've added this to the wiki (see http://rails-i18n.org/wiki) Thanks! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "rails-i18n" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rails-i18n?hl=en -~----------~----~----~----~------~----~------~--~---
