API key problems in WordFast

[JohnD]

Hi, I just attempted to use my new API key to set up machine translation in WordFast but got the following message: "Error while parsing list of supported languages." The selected languages were English and Spanish, so I can't imagine what the problem might be.  However, the key itself is very complex. Certain characters such as i/I, 1, and l/L are potentially easy to misread. I've tried retyping the key.

Is there a Google tech who can verify my API key to see if I'm reading it correctly?

Thanks in advance,

JohnD

[João Martins]

Which was the error returned by the Translate API?

[JohnD]

The error appeared when I typed the key into WordFast preferences for Google machine translation. I've not tried to communicate with anyone from WordFast (which seems almost impossible!) because I think it's perhaps something dealing with the problematic key characters I mentioned in my first posting. I might just be "reading" them wrong. ???  I can't imagine why I got the message "Error while parsing list of supported languages."

If no one in this forum has any ideas, I'll try to see if I can find a similar forum for WordFast. Also, proZ.com has lots of WordFast users. However, I think the "error" is probably related to the key itself.

Helplessly hoping,

John

[JohnD]

I created another API key but got the same message.  ???

[Jeremy Geerdes]

Just out of curiosity, why are you not copy/pasting the key into WordFast? That would eliminate the problem of mis-reading and/or mis-typing characters. Also, it is possible to obtain a key for the Translate API but still have your billing quota set at 0. If WordFast is sending a quick test to verify the key, and your quota is set at 0, the API will return an error, which may be what WordFast is putting out.

jg

[JohnD]

Jeremy, I'm unable to "paste" the key into WF on my MacPro since there's no drop-down menu, and right-clicking doesn't work. However, I've typed the keys into WF Anywhere and they work fine. The problem I'm having with WF Pro is apparently related to language code confusion, not API keys. At this point, I've tried various things in WF Pro: clarifying codes as EN-US to ES-MX in preferences as well as finding/replacing them in previous WF Classic files; opening new projects and creating new files and TMs from scratch with those language descriptors; and trying to use old Classic files in various ways--but all to no avail. At one pt, I had an error msg related to a faulty header, but it is correct now. . . .  I'm not sure about your "billing" thoughts but don't think that's the issue. I think my MT problems stem from conflicting language codes, which I've tried to identify and correct--as well as to use/create new projects and files with the correct language codes.

Joao, here are the continuing error messages for Google and MS in WF Pro:

"Couldn't detect if languages are supported. Server message: Error while parsing list of supported languages.  Please note that Google MT will not be used." AND

"Couldn't detect if languages are supported. Server message: ACS50012: Authentication failed.  Trace ID . . . .  Please note that Microsoft MT will not be used."

FYI, I have the newest WF Pro version and a MacBook Pro with the newest update of Mountain Lion OS.

Thanks in advance for any help/suggestions.  BTW, I apologize for not getting back sooner. I had been posting on proz.com (see "johndel" in "Wordfast Support" forum.

[JohnD]

Jeremy, I was able to copy/paste the keys into WF Anywhere, which allowed me to right-click and paste. I think the WF Pro developers for Mac just overlooked this capability.  ???

[Jeremy Geerdes]

On a Mac Pro, you should be able to use Cmd-V to paste from the clipboard into just about anything. Does that work?

jg

[JohnD]

Wow, Jeremy, that's all it took!!! I used the Cmd-V command to paste the keys into the Google and MS MTs, and now everything works fine. Now I can move past this issue to other--and probably more important--things since MTs can often take more editing time than they're worth.  ;-)

Thanks!

--JohnD