If you make a website multiple language, currently the page names still cannot be translated. So in effect the website is still only 1 language.
The solution is to turn on the full localization option in DNN, but this in effect creates a copy of the site. This creates a large amount of complexity and work for the developer, integrator and website manager. (Probably easier to make another portal for the language!)
I currently use Apollo Localization to solve this problem which allows me to change Page Names and meta data based on the language.
I suggest two options should be included in the DNN core code as soon as a language is turned on:
1 - The Page Name and Meta Data related to the page are localizable. (Much the same as Apollo Localization allows)
2 - Modules can be hidden/shown based on language.
Just these 2 simple options will deal with 80% of localization need.