(04-20-2015, 09:33 PM)ivantcholakov Wrote: I appeal to natural English speakers to think twice before saying "No", because this feature usually is not important for them.
Honestly, the language I speak has nothing to do with the importance of this feature. No matter how much (or how little) I want to support multiple languages on my website(s), it only happens if my employer/client can supply their content in multiple languages. I happen to know enough of two foreign languages to know that I have no business attempting a full translation of content into either of them.
This feature is based on a practice which has changed over time and is likely to continue to do so. What is the advantage of putting this functionality into the core? What are the disadvantages? Should the various potential language identifiers be reserved routes? Which standards should be followed? (How do you distinguish between versions of English, French, Spanish, and Portuguese, since those of us in North/South America don't tend to use the original versions of these languages?)
The issues of identifying languages and their variants aren't well handled by the Lang class itself, in my opinion, so I do tend to take issue with the idea that we should just jump right in and add language identifiers to the core routing.
