Yes well, I am waiting for the latest release. As according to Michal we are to wait. SO I really hope it will be available very soon, as I am loosing more and more members every day.
Yes well, I am waiting for the latest release. As according to Michal we are to wait. SO I really hope it will be available very soon, as I am loosing more and more members every day.
Also please note that in Google Translation API v2 you can set your limits yourself. Just as Radek wrote - newest vBET version have solution for blocked API by provider - we switch to another and if all limits are reached then dummy translator shows original text. We suppose to release yesterday new version, but because of issues with internet it was rescheduled (I know it is trivial, but it was weekend, on the trip and cellophane internet didn't work as suppose to). This week we will release another version which corrects issue with marking providers as unavailable too often. Last version marks as not available when any error comes from translation provider. This is not necessary - we discovered that Microsoft Translation API sends different communicates for issues like "server too busy", "timeout". For such errors we do not have to consider that limits are reached. So next release will fix it and consider translation provider unavailable only for special messages which clearly says that limit is reached.
Answering you question about paid Google Translation API v2. Please just go to Admin CP -> vBET -> Translation Providers and you will find there description how to start with Google Translation API v2 (there is link and explanation how to get API key). Please remember that v2 is paid so you can consider to check the limits, maybe remove some languages, and ignore some pages to make it cheaper. The prices are controlled by Google so we cannot change it.
Do you need more help here?![]()
I just hope that I will be able to use the new version with the free API's! I don't have a problem with going to paid but google needs a credit card for that, and I live and work in China, and they do not accept any Chinese credit card for payment. So I am screwed. I tried to find out about microsoft paid API, but could not find out where to apply for that.
The next releases will still support Google Translation API v1 (as long as it exists) and free Microsoft Translation API (as long as it exists).
If you have questions about payments for Microsoft Translation API please ask here: mtcont@microsoft.com
According to information which we got from Microsoft after 30 March 2012 anyone will be forced to use paid version of Microsoft Translation API EVEN if you will use only 2 millions free characters/month. That means that Microsoft will be still free for this quota. Still it will be necessary to use Microsoft Azure Marketplace:
Do you need more help here?Originally Posted by Mail from Microsoft
![]()
Last edited by vBET; 19-10-11 at 21:18.
Thanks for the info Michal. So people without credit cards will not be able to use google or Microsoft. So therefore vBET will be of no use for me. This is truly the worst news ever!
I'm not sure about Microsoft payments methods now. And of course we have no idea does Google will add new payment methods - this is out of our influence. Please ask Google for more payment methods.
Also according to this information from one of our users: http://www.vbenterprisetranslator.co...id-ms-api.html
Microsoft has subscription (not like Google which charges on the fly) - so it should be available to pay with many methods. I understand that Google must be allowed to charge automatically. But Microsoft has just a subscription so it should be allowed to pay by any method (upfront). Please just check it. We will go there after next release of vBET 4.x. At this moment we do not know details yet.
Do you need more help here?![]()
I just upgraded to 4.4.4 and after 2 minutes I have no Translation providers available. Reached the limit for google and Microsoft. Bot of these require a credit card to go for paid API's, whether you go for a subscription or not. (Microsoft) So now vBET is of no use to me, and I am sure there are many forum owners without credit cards, or that cannot afford paid translations. This is a nightmare!!
If you reached limits then you just have to wait until it is available again. Please note that Microsoft has monthly and hourly limit, so if you didn't reach your monthly limit yet, then you will have new translations soon (vBET checks every 10 minutes does provider is available again).
Google has for sure second limit (we do not know what else).
Please note that Microsoft even after March 2012 will provide API for free with monthly limit of 2 millions characters (now is 4). We have no idea will it be cut or not. At this moment it is known that there will be available free limit.
About prices and payments methods - once again please contact with translation providers - what do you expect us to do about it?... :/
We will add support for more APIs when possible. Still we have no influence on terms of 3rd party translation providers. Please direct issues directly to places where those can be solved.
Last edited by vBET; 21-10-11 at 03:04.
I am not blaming you for this Michal, I know it is not your fault. The facts are just that I will not be able to use vBET with free API's! My forum is too big, and the limits are reached within 30 seconds. So what good does that do me? And I already contacted the translation providers. There is no other way to pay. SO again, not your fault, but it renders vBET obsolete for big forums.(If you don't have a credit card) And that is a fact!About prices and payments methods - once again please contact with translation providers - what do you expect us to do about it?... :/
We will add support for more APIs when possible. Still we have no influence on terms of 3rd party translation providers. Please direct issues directly to places where those can be solved.
As long as you can please stay with vBET - we are looking for other translation providers, market is changing all the time...
Also - if you are not using Google v1 anymore please turn off cache cleaning. Let the cache fill up. I know you have big forum, but assuming that you have it cached maybe free limits will be enough to cover new messages. Also you can set vBET to ignore some pages which you consider are not important for translation. For Example - RSS channels are changing all the time. Maybe you will give up translations on archive... Maybe other places...
Shortly - we encourage you to consider how to still use vBET with new limitations put by 3rd party translation providers. And again - we want to support more.
Do you need more help here? Or can we set the issue as solved?