
Originally Posted by
JasMate
Are you sure it's just google?
Google made the change and now we need to adjust to it.
So, you could blame Google or you could blame us. Either way, the two are not working together.

Originally Posted by
JasMate
I just added the code from the yahoo file and get this error when I click the link:
I haven't used the Yahoo translations in a long time. My current feeling is that the Google translations are so significantly superior that I am not going to invest any time with the other translation engines unless Google Translate becomes permanently unavailable.
Do you have shell access to your server? If so, you can try to access Yahoo Babelfish from the server using `lynx` or `elinks`.
Last I worked with it, Babelfish was doing some impressively sneaky things to block automated access. They were blocking requests that came from the same IP as the IP of the web site being requested. This effectively blocked every webmaster whose web site was hosted on a server with just one IP. I think Yahoo may have stopped doing that though.
Instead, more people seem to have trouble with the Babelfish IP addresses not working from their servers. You may have to run some `nslookup` commands from your server to find the proper Babelfish IP addresses from your servers location.
You then have to change the IP on this line from translate/index.php:
Code:
'trans_url' => 'http://72.30.186.56/babelfish/translate_url_content?lp=en_$lang&trurl=$url',
Bookmarks