Posts: 1,321
Threads: 21
Joined: Jan 2014
Reputation:
70
What exactly are you proposing? "URI language identifier in core" is too vague.
The article you reference seems to suggest changing the routing (which would not work for everyone) and enhancing the Lang class.
Are you suggesting that something like this be built in so that all CI sites should do this?
Posts: 35
Threads: 2
Joined: Feb 2015
Reputation:
3
I prefer the usual url layout example.com/class/function/ID (where class is the controller) and work with resource files.
So no need for a 'language segment'.
I am curious what others think. What are the advantages of this approach?
Posts: 421
Threads: 24
Joined: Oct 2014
Reputation:
18
1 SEO tip
if
/ - is english
/en must not exists - else you will have duplicate content (you can handle this case with canonicals but its not a good option..)
For the thread - yes there is a need of supporting locale inside the router by default.
There is always locale - 1 default or many it doesn't matter. Even if its not displayed (if its 1 only) you again have language which you will output.
So CI must provide fast and easy way to catch and handle language/locale by its routers..
Posts: 1,062
Threads: 42
Joined: Mar 2015
Reputation:
73
I voted No, because I do not want the framework to dictate how I choose to handle multi-language implementations.
It depends so much on the site itself, that I have used several approaches in the past with CI, all of them easy enough to implement.
There is no clear or set answer as to how to handle multi language implementations. It depends on the needs of the client.
Paul.