qTranslate 3.0

[robertn]

Let me explain why this isn't done the proposed way:
1) When I visited a website and I choose a language, I want the website to only show that language. It is very irritating to suddenly see for example polish text when I explicitly choose English. This leaves a very unprofessional impression for the user.
2) The Webpage is marked in the user selected language, so SEO will be very angry with you if you do something like this. Not only because you are displaying the wrong language, but also because of showing duplicate content.
So what'S the solution? Well, automated translations with a hint for the original article is one way to go. You can see that Microsoft KB is doing that. I might consider this as a trade-off. But I still don't like Machine Translations.

I've decided that I'll patch qTranslate source code for my needs.
Thank you anyway for considering my proposals.

I have another question, regarding custom-post-type approach in qTranslate 3:
Will it be possible to use qTranslate on blogs that utilize custom-post-types for some other functionality?
For example, if I had a blog that uses custom-post-types: book and event, would it interfere with qTranslate 3?

With posts, why not simply c&p the original text into the other language box (if I understood correctly what you're after)? Looks like this: http://www.fluteofshame.com/fi/category/james.

http://www.fluteofshame.com page works exactly that way I'd like on my page.
However, as a programmer, I really don't like the copy-and-paste solution, and I prefer so-called DRY (Don't Repeat Yourself) principle.

[wikichaves]

Hi Qian,

I would like to test qT 3.0 beta version ! How can I be included in the beta testing list ?

Best,
Wiki

[MikeQue]

Let me explain why this isn't done the proposed way:
1) When I visited a website and I choose a language, I want the website to only show that language. It is very irritating to suddenly see for example polish text when I explicitly choose English. This leaves a very unprofessional impression for the user.
2) The Webpage is marked in the user selected language, so SEO will be very angry with you if you do something like this. Not only because you are displaying the wrong language, but also because of showing duplicate content.

That's a good point about SEO pitfalls. Thanks for pointing that out, as I hadn't realized that.

However, I have wondered why in Wordpress all non-default languages are reflected in the URL with something like "en/" or "lang=en". I have seen in other environments than Wordpress where there is no need to modify the URL, where a cookie is instead used to track the user's language preference. For example, another open source project Zenphoto does this, avoiding specifying the language in the URL. Here is an example of a site I made for a client that works in English and Spanish (Spanish labelled "Castellano"), and no difference in the URL between languages. http://pablogarber.com.ar/ I would think with Wordpress that would also not be too difficult technologically since localizing the entire installation to a particular language is straightforward. But that's more of a hunch than something I could say for sure.

Is this also for SEO reasons that every multi-language tool I have seen for Wordpress depends on modifying the URL to switch languages? Or is getting rid of that in the URL something you are looking at doing in qTranslate 3.0?

(I too would be happy to test and provide feedback on the beta of 3.0.)

[aslaug]

I am very happy with qtranslate, except I can't seem to find a way to get custom fields in the right language.
I use custome fields to get page-title different from menu

I have tried the [:no]Foran tittel [:en]In front of title, this works fine with my problem with widget titles
the <!--:no-->Meir om oss<!--:--><!--:en-->More about us<!--:--> that works with the sidebar menues shows all the text, not only the choosen one, that is: (Jeg vil ha en annen tittel I want a different title)
Is there someone please that knows how to solve this?
PS I a am a designer and not much scholared in koding and php

[andreimc]

Hello!
Two questions please

1. if I upgrade to the latest wordpress version now, the plugin will be disabled (since it doesnt work with 3.x) however will i ALSO completely lose the other translations i have done?
2. in order to not lose the translations in other languages, when you make the plugin compatible with 3.x, should i first install the plugin and after that, WP 3.x? or WP first, and then the plugin?

thank you very much in advance

best regards,

[squrler]

Any idea when 3.0 will get released..? Or is the beta already usable? I'm itching to get it going with WP3.1

[Qian Qin]

I will first release a qT 2.x version for WP3.1 before qT 3 comes.

[brasofilo]

cool news, qian

i'm using 2.5.14 and just patched qtranslate_javascript.php as for fixing extra <p>'s appearing in my posts
[ discussion in this thread ]
[ hope you can contemplate the issue in 2.x or 3 ]

i have the same doubt pointed by robertn,
how will qT3 will interact with other Custom Posts?

and, maybe it's not relevant, but in some sites i use WP as backend and Flash as frontend
- as all the languages are inside a post_content/post_title, I can break it and serve the appropriate language
- so my question is: will be possible to make direct mysql queries and get all the languages of a post?

thx 4 this great plugin

rudolf

[Hedgehog]

Thank you for all your dedication Qian Qin. I just sent you an Amazon-giftcard, but please don't use it to buy any Apple-stuff (although the iPad is cool)!

[Idealien]

I had to re-write an entire site to support an inferior alternative (WPML) instead of qTranslate because of the missing functionality that qTranslate 3.0 will offer. Now I find out instead of continuing in the spirit of open source they are changed their business model to become a commercially focused operation: http://wpml.org/2011/02/wpml-is-becoming-a-commercial-product/.

I have said in this thread before that I would definitely help beta test when it is ready. I'll go further and donate what would have been the $$ to WPML to support qTranslate when I know a working alternative is in place again like it was before WP 3.0 "changed everything". I imagine I'm not the only person who would feel this way.