Ideas Bot wrote:browser language detection
Could lead to the wrong language, if somebody uses english software but is a native speaker in russian, spanish or something.
It's not our fault. If the headers say that the user wants the web page in english, why would he get a different page? If he wants in russian, then he should manually change to russian. If you want the web pages with a preference in specific languages, it should be specified like that in the "content-language" header.
For example, I have my browser's set as:
Code: Select all
So I expect that the page where I get to always serves me with the english page unless I explicitly state otherwise afterwards or it already knows that I prefer a different language or it does not have such language. I can say that > 90% of the times, just about any website out there, that's definitely not what happens.
Ideas Bot wrote:language inheritance
What do you mean?
pt-br < pt-pt
en-us < en-gb
If I understood right.
The concept is like style inheritance if there's no specific value for the language chosen, use one of the language that is above that in the "tree". If the user is viewing the website in pt-br (brazilian portuguese), and if a word does not exist in the laguage pack of pt-br, then it would use the one in pt-pt, which is a nice fallback, specially because most words are written the same way in both.
Ideas Bot wrote:
Maybe there is a good solution to translate the content, too?
Want to translate? Use google translator or anything similar. If the forum owner wants that, get an extension to do it for him. That's what I think.
Ideas Bot wrote:language dropdown box
If we solve the one I pointed out in the first idea this is not needed any more and a different thing can be used instead.
As I have a mixed yes/no opinion on those, I'm unable to properly vote.