| User | Thread poster: JMonte Google MT v2 not working with Wordfast Anywhere |
|---|
JMonte
Germany
|
Hello,
I am using the web based Wordfast Anywhere coupled with Google MT v2.
The automatic translation will not work and a message is shown
"Machine Translation did not Respond".
I checked the MT configurations of Wordfast anywhere and it is ok. I changed my Google MT v2 API key, the new key will not work too.
any help is welcome!
| | | |
Dominique Pivard 
Finland
Local time: 10:12
Finnish to French
| | Ask for help on the WFA list | Dec 1, 2011 |
JMonte wrote:
I am using the web based Wordfast Anywhere coupled with Google MT v2.
The automatic translation will not work and a message is shown
"Machine Translation did not Respond".
I checked the MT configurations of Wordfast anywhere and it is ok. I changed my Google MT v2 API key, the new key will not work too.
|
|
I suppose you already watched these?
http://youtu.be/-KHq094SeWU?hd=1
http://youtu.be/19gBOO5xT58?hd=1
If you just opened an account with Google, it may take a few hours before it's operational. There could be a problem with the WFA server, but you should ask about it on the WFA list (http://tech.groups.yahoo.com/group/Wordfast_Anywhere/).
| | | |
Dallas Cao
China
Local time: 15:12
  Member (2007)
English to Chinese
+ ...
| | Something goes wrong | Dec 2, 2011 |
I received tons of reports this morning from GT4T users.
It looks like all Google Translate 2.0 api keys stop working this morning. Only the Google guys can help. Unfortunately with a giant company like google, it could take a long time before it could respond to a user's inquiry.
| | | |
Dominique Pivard
Finland
Local time: 10:12
Finnish to French
| | strange, no problem here! | Dec 2, 2011 |
Dallas Cao wrote:
I received tons of reports this morning from GT4T users.
|
|
This is strange, I have had no problems here, with Wf Classic. But I started working quite late (European time), so maybe the problem has been already fixed?
| | | |
Maria Hoskins
United Kingdom
Local time: 08:12
Member (2011)
Spanish to English
+ ...
| | OK here but... | Dec 2, 2011 |
Just got a Google Api key seems to be working fine with WF now, but how much is this going to cost me? Google charges $20 per million characters, is that correct?
| | | |
Dominique Pivard
Finland
Local time: 10:12
Finnish to French
| | It's based on real usage | Dec 2, 2011 |
Maria Hoskins wrote:
Just got a Google Api key seems to be working fine with WF now, but how much is this going to cost me? Google charges $20 per million characters, is that correct? |
|
It's based on real usage, so only time will tell how much you will end up paying. You are correct about the price ($20 for 1 million characters). Please note that there may be some overhead introduced by your CAT tool. For instance, when expanding or shrinking a segment, you'll probably end up querying twice the same data. If you close a translation session in Wordfast Classic, then reopen it at the same point, the same segment will probably be queried twice. This is because Wordfast queries ahead: when you're at segment n, it has already queried a translation for segment n+1. I've taken the stance that whatever Google ends up charging, it will be far less than the value of the benefit I get from it, even if 90% of what it suggests is useless.
| | | |
Dallas Cao
China
Local time: 15:12
Member (2007)
English to Chinese
+ ...
|
Hi JMonte,
I found out a solution:
It looks like those users who enabled both api key and OAuth 2.0, the api key would stop working today.
And there is no way to disable OAuth once enabled:(
So I created another Google account using my wife's email and reapplied for Google Translate API key. Problem solved!
I wasted a whole day trying to figure out how to use OAuth. GT4T users are still flooding my email box!
Dallas
| | | |
Maria Hoskins
United Kingdom
Local time: 08:12
Member (2011)
Spanish to English
+ ...
| | Thanks M Pivard | Dec 2, 2011 |
Same here. I use Google as a pointer, in my view it's the best of the bunch...
| | | |
JMonte
Germany
TOPIC STARTER |
Hello Didier, Dallas, Pivard,
Thank you for your help. Concerning the OAUTH issue with the API key, in my case I did not activate the OAUTH client ID. I contacted the support, as soon as I have a reply I will post to share if any solution available.
| | | |
Maria Hoskins
United Kingdom
Local time: 08:12
Member (2011)
Spanish to English
+ ...
| | MT stopped responding this morning | Dec 3, 2011 |
Started translating about an hour ago took a break and now MT has stopped working... Help!!!
| | | |
usta
Turkey
Local time: 10:12
Member (2010)
English to Turkish
+ ...
| | Machine Translation Did not Respond | Jan 19 |
I am getting "Machine Translation Did not Respond" error for one of two segments. Sometimes it responds, then it stops again. I need urgent help.
| | | |
Dominique Pivard
Finland
Local time: 10:12
Finnish to French
| | The problem is with Google, not Wordfast | Jan 19 |
usta wrote:
I am getting "Machine Translation Did not Respond" error for one of two segments. Sometimes it responds, then it stops again. I need urgent help. |
|
The same problem (Code 403: Serving Limit Exceeded) has been reported by users of several different tools (Wordfast, Trados, Déjà Vu). It's with Google, not Wordfast, so you'll have to turn to Google, or wait until it is solved.
| | | |
Yasmin Moslem
Egypt
Local time: 09:12
Member (2011)
English to Arabic
|
You can use MS Translator also for FREE. Go to: http://www.bing.com/developers/appids.aspx It requires you to login using a valid Windows Live ID (e.g. Hotmail email address).
Click "Add" and fill in the details. When you finish, click "Save".
Now, you can see your key. Click it to load a page where you can copy the key.
Here is the way: http://youtu.be/On-n0bw1iIA
HTH,
Yasmin
| | | |
The translation workplace 
Translation news related to Wordfast