added 'url_segments' namespace in yaml input translations file

[cawel]

Old way:

es:
  products: productos
  contact: contacto

New way (now wrapped into a namespace):

es:
  url_segments:
    products: productos
    contact: contacto

I had to introduce a namespace because I had a I18n translation in my app which collided with one of my url segment translations.

On another topic, I'm willing to write a few tests, but right now I have errors when I try to run ruby test/test_rails-translate-routes.rb :(

[francesc]

Hey, seems ok to me. Thanks! I'll try to add and documentate it this week.

I'll be quite busy making it work with rails 3.2, I just started but still have to see how the new engine works. After I have a new version for it next step will be to add some testing. ;)

[cawel]

I'm curious, when do you think you'll have a Rails 3.2 compatible version?

[francesc]

Hey Martin,

I spend some hours this week trying to make it work and pulling my hair out XD I got how to retrieve the regular, named & engine routes from Journey but still have to figure out how to remove routes and add them.

[corneverbruggen]

Just ran into the same collision problem as @cawel, so found this issue. Is this going to be merged soon?

[cawel]

francesc: I have recently upgraded a personal project from Rails < 3.2 to Rails 3.2.3 and I found no problem with that commit (which I put on top of your latest master branch) which allows us to introduce a namespace into our url segment translations.

Any plans to integrate it into the main repo?

[morgoth]

Same problem.

My workaround:
Put routes translations in: config/routes.yml
and in router.rb:

ActionDispatch::Routing::Translator.translate_from_file("config/routes.yml")

[francesc]

Hey. Sorry for the delay, I'll release a new version today to fix this and other small improvements. It will use a :routes namespace on the yaml.

en:
routes:

you can leave empty locales, for example the default one, don't forget the routes namespace

es:
routes:
products: productos
contact: contacto