I also agree with PowerKiki on this one, and I'll be using this patch.
Qian Qin wrote:this will not be included because of several reasons. As I have written may times before:
1. pages are marked with a language, which you violate when showing a different language then defined.
2. you will have duplicate content on different urls. bad for seo.
3. people dont want to see other language content if they chose one language.
Here are my thoughts:
1. I think only machines and geeks really care about that. I'm a geek too, but I recognize that most people don't care that much about misclassification when the benefits of having content -- any content -- are greater than having no content at all.
2. This is easily solved with Canonical URLs: http://googlewebmastercentral.blogspot.com/2009/02/specify-your-canonical.html
. @PowerKiki Can your plugin handle that? Another solution would be to output an iframe which contains the content in the default language. Further research would have to be done to confirm that the displaying URL doesn't get search-engine credit for the iframe content, but from what I read on the internet, it would work.
3. This is not a problem. For example, when you Google, you end up with hits in all sorts of languages. (Most people do not change their Google language settings and just get this default behavior.) Do people hate Google for it? I don't think so. In fact, if you click on a link, Chrome (and browsers with the proper extensions) will offer to auto-translate the page for you. The internet is multilingual and people are definitely not afraid of hitting a page in a foreign language, especially if that language default is English.
In general, it's nice to have a qTranslate in github because it's awesome to have a way to fork and make our own modifications that won't be accepted into the main release. That way, when the main qTranslate changes, it's easy to merge changes. I would also like to have my own modifications because I'm not sure my fix about browser detection
was ever integrated.