Google Translate API shut off or will be paid? Doesn't matter - vBET supports other APIs

[Jncocontrol]

This is good news - at least there still will be way to have so many translations. Lets hope the price will be appropriate... Anyway we will made investigation about other solutions since this is more gossip than news.

Thanks for any info you give If anyone have anything to add - even what you think about actual situation - just write.

I don't think it should be a problem, Google products aren't meant for millionaires.

[MOGmartin]

Michal,

sorry for the delayed response - I was on holiday last week.

I seem to remember that wp-robot autotranslates using either google, yahoo or bablefish (available options in the config) so take a look at their implementation mate.

best regards

martin

[vBET]

Thanks - I will investigate this. Right now we have 'new hope' - Google claims that translation API will not be closed, just changed to paid one. This is important, because no other API gives so many languages. Still we will investigate other possibilities, because now there are no details about new Google strategy.

[tavenger5]

It would be great if VBET could still use Google's API along with the ability to use a secondary free translator if needed. For me a paid google API would be worth it.

[vBET]

As I wrote we will check other possibilities too. You can always use Google for some translations not supported by others and other service where you can have it for free. This is where we will go.

[vBET]

Next idea how to handle additional translation API is to add simple parameter where you can decide do you want have everything translated by Google, or by other API where it is possible.

Such solution will still allow you to use all languages and made lower costs (Google Translation API will be paid). Also configuration will be trivial - just one parameter. And for those who would like to choose specific translation service (when some translation will have more than 2 options) we will have simple php array with mapping translation to provider. There where will be possible to use more than 1 provider different than Google we will note this in php comment. So you can open configuration file there you will see what must be translated by Google (no other providers for such language) and what will be translated by other provider - which one and what else supports specific translation. Simply for each language there will be map where key will be language code and value will be provider.

Who doesn't care about details just want to have cheaper translations – just turn on one option. Who wants details and make detailed choices just changes one string to another in appropriate php table.

This is actual idea how to add support for other translation APIs.

Any comments appreciated

[vBET]

MS has one as well: Microsoft® Translator Tools

This seems like great alternative. As I see there is 35 languages supported. And it seems to be all to all translation. Will have to look closer - also in Terms of Service.

[vBET]

Michal,

sorry for the delayed response - I was on holiday last week.

I seem to remember that wp-robot autotranslates using either google, yahoo or bablefish (available options in the config) so take a look at their implementation mate.

best regards

martin

Yes I found information that wp-robot can use yahoo bablefish (this is one solution) for translations. I made note about it in my workplace for this issue and I will investigate it more. If you have any additional information in this area please provide here or by PM. Thanks

[vBET]

It would be great if VBET could still use Google's API along with the ability to use a secondary free translator if needed. For me a paid google API would be worth it.

Please see here: http://www.vbenterprisetranslator.co....html#post8865
This seems to be great alternative. Still we have to check license details. It is free, but there is some additional note about contact them, so we will make contact and clarify will it be possible to use Microsoft API for free with vBET as adapter layer.

[vBET]

We just send mail with few questions to mail address given by Microsoft on Microsoft Translation API page. We checked license and found no limitation, but we want to be sure we was looking in right place and didn't miss something. So at this moment we are waiting for clarification will it be legal to use Microsoft Translation API in vBET.

We will keep you informed