Default locales about route_translator HOT 9 CLOSED

Hi,

route_translator translates routes inside a localized call for each available locales, as declared in I18n configuration with I18n.available_locales.

If translations for a path part are not available in a locale, the exact result of the routes translation process depends on the way you handle missing translations in your app (fallback to another locale, fallback to humanized key name or exception).

from route_translator.

Basically, you have [:es, :en, :de] as the result of your I18n.available locales call. If that's not ideal for you, maybe we could add an option for whiltelisted_locales or something like that. It seems reasonable. If you want to contribute that change, please go ahead.

What do you think @gi-lunaweb?

from route_translator.

What happens if I just edit this in the application.rb - for example to:

I18n.available_locales = [:de]

Shouldn´t that do the trick already?

from route_translator.

yeah, it should, but what I meant is that maybe you want to use some locales for the routes and have some others for the content translations we would need a special option.

If you don't wan that, just setting the availabe_locales should work fine.

from route_translator.

Ah okay I understand. In my current project I only use one locale for the routes and the content.

But in general your idea is good. I will think about a possible pull request.

from route_translator.

@enriclluelles

The default behavior in Rails is to enable fallbacks for translations in production environment. If you don't want to provides full translations for all your views and routes in a specific locale, you can just set up correct fallback to a default one.
I don't think we need any additional option for that in route_translator.

from route_translator.

@gi-lunaweb that's right but even if it fallbacks, the translated route is still generated and maybe the user doesn't want that. But anyway, it looks like @mattherick doesn't need that so let's not clutter the app until we feel it's needed

from route_translator.

👍 thanks guys for your help!

from route_translator.

@enriclluelles : This has a great potential to becomes a real code nightmare for us and/or an incomprehensible mess for gem users if we one day need to implement it 😃

from route_translator.