qTranslate 3.0

[Qian Qin]

Hi guys,

qTranslate has become quite more than I expected it to be when I first coded it. I'm so happy that so many people are using it and I feel bad for not answering a lot of mails I get about qTranslate. But I finally found time to continue my development on qTranslate. So instead of bugfixing the old qT, which is still a lot of code for Generations of Wordpress', I started from scratch to fully support the latest WordPress. You'll probably ask what difference will it make and why I should bother rewriting everything if the old version is still running. Well, let me list what changes the new qT will have:

• Object oriented code
• (Much much) better performance through WP3 optimized code
• translated slugs (finally!)
• documented code with lots of filters and actions so qT can be extended easily (yay plugin compatibility)
• Better WPMU support
• Extending WordPress to support multiple languages instead of hacking it (finally possible with WP3)

I'm trying to do all this while keeping and improving some of the greatness of the old qT

• No extra Database or database modifications
• Do more things automatically, so even less configuration is needed out-of-the-box
• qTranslate Editor (will most probably work very differently from the old one)

Feature Requests

• None yet

If you have a request for a specific feature, please post it in this thread. I'll update the list once in a while with features that I'll include.

To focus on the development, I'd really love to have some testers (please send me an email to mail@qianqin.de if you want to help test, svn needed) to get all bugs fixed quickly.

Finally, if you would like to support me or want the new plugin to be finished faster, consider helping out by getting a better keyboard or a pizza for a hungry developer, so he doesn't need to take any cooking breaks

[jokerwho]

At this moment, something I would really need is knowledge about how to integrate qtranslate
with every label area (like the excerpt) or editor (the quickpress, for example) in the backend of WP,
so I think I would ask functions to easily do this.
thanks

P.S.: do you have a release date already or are you starting now?

[Qian Qin]

3.0 will store post and page translations via custom-type-posts. Languages tags will be still supported for other simple fields. I will write up a documentation this time to explain how 3.0 works so it can be extended very easily.

No release date yet, but the frontend is already 50% done. Feel free to take a look at the svn repository for the current development state.

[jokerwho]

Wait... do you mean that I will have to write each article once for each language? or will it be like the actual version (language tabs in the same editor)?

[Qian Qin]

3.0 will combine optimized storing (custom post types) with usability (qTranslate Editor), basically the best of both worlds.

[jokerwho]

In English ( ) does that mean that the language tab switchers will still be there?
In other terms, I don't like the wpml approach

[julien.fs]

That's a pretty exciting news. Just to clear one of my worries, the new version will be 100% compatible with the content created on the version 2.5.9 right?

[Qian Qin]

yes, the switcher will stay.

there will be an importer to get the data from the old version.

[theycallmediddy]

This is amazing news! I know this is still work in progress, but roughly when do you think you'll release this? End of 2011? Maybe even earlier?
Just asking as my clients always want to know dates for new features.
I will however donate some money in the future and put it on their invoice.

[jokerwho]

yes, the switcher will stay.

Great!! I really hope that it will be possible to include it "anywhere" in the backend...