#1
Hello everyone,

I'm considering using Trongate, and the first project I'd like to use it for is one that requires some basic localization.

I've found some old help bar discussions about this. One from 2018 says this would important to do, but it's mostly about calendar stuff (https://trongate.io/help_bar_threads/display/8EkVrPL38erz). Another one from this year is about setting the language using a specific URL and a cookie (https://trongate.io/help_bar_threads/display/awSsdpyqwcBLvBby). There is a pull request to setting the locale (https://github.com/trongate/trongate-framework/pull/115/files). But these don't really help me.

Is there a best way to have UI elements in a language resource (buttons, labels, menu items)? Currently, I have an array for each language with and ID for each ui element. I could do that if I switch to Trongate.

Also, is there a best way to get the language from the url? I suppose I would have to over ride the routing which would work by default for each controller, so change the first segment to be the language. And just use (:any) or (:alpha) to get the language as a variable and pass it. So I'd have to setup the routing, rather than using the default setup.

So since this is a translation dictionary, it would be a routing like



And define it as

#2
I think the Steinberg website is a great example of this being done right. The URL is:

https://www.steinberg.net/

Personally speaking, I haven't done many sites with that kind of need - however - if I was working on something like that then I'd use the Steinberg site as a reference.
#3
Hi Shawn,

I was wondering how you are getting on with your localisation issue?

Also noticed you have forgotten to include a $data['view_module'] in your custom route example, without it the rout will not work:


Not sure if this helps but Mario was working on some localisation solutions - his repo is here https://github.com/Marlintt/trongate-framework