You can hijack it to transparently translate your own webpages for users without crediting Google, I suppose. If you do it wrong (that is, issuing the request FOR EVERY PAGE VIEW and doing no caching at all) it could definitely be considered abuse.

You can hijack it to transparently translate your own webpages for users without crediting Google, I suppose. If you do it wrong (that is, issuing the request FOR EVERY PAGE VIEW and doing no caching at all) it could definitely be considered abuse.

Most of the Android translation apps are really just a wrapper around Google translate. There are hundreds of the blasted things and they have the audacity to charge you for it when Google is doing most of the work for free. I wouldn't be overly surprised if those apps were a large part of the reason Google is shutting the service down.

Google has been clamping down on low-quality aggregation sites, as we all know. One way to avoid looking like a low-quality aggregation site is to (a) create a vast farm of low-quality aggregation sites, (b) harvest high-quality articles from other sites, (c) run those articles through Google translate, (d) repost them to your farm. Because they don't look like the originals (being translations) they get around Google's "recognize repeat content" filters. Google uptakes them as original content.

Delicious has been filled with links to these in recent weeks, mostly because Delicious once had a decently high reputation as a site of quality linkage, and lots of people had trust in it.

One example is if you are in charge of the company website and the boss tells you, "We need all the pages to be available in espanol, because we're getting more non-English-speaking customers"

An easy way to accomplish this with minimal work is to output buffer everything, send to a translation service, and then turn around and spit out the translated HTML instead of the original HTML.

I can't remember which service, Babelfish I think, but you could send all your HTML to them and it was smart enough to not translate HTML tags and only the content itself. Then, they realized that everybody was using them in such a manner so they added a character length limit to translations, I believe.

You were then faced finding another service, such as Google Translate, or actually set up an official integration with Systran and pay them for translation services.

I suspect the era of finding workarounds and piggybacking off of free translation services are coming to an end.

People think Google's business model for everything (except their search engine, which is supported by advertising) should be to run huge expensive server farms for the purpose of giving away stuff for free so that... um... money will rain from the skies or something. Now, granted, to all outward appearances this seems to be their business plan 95% of the time... XD

How the hell can you abuse a translating service ? To rickroll people of different cultures ?

Google Translate also provided a TTS (Text To Speech) module that would provide a high quality playback of audio in many languages. This type of a service typically costs many hundreds or thousands of dollars commercially and often requires dedicated servers for concurrency support...or could be leeched from Google for free if you knew the right URLs to hit.

but has thus far declined to provide details or a sensible alternative for users of the API

Just because they used to offer a free service, and will soon stop doing so, people aren't just offended at that but are also attacking them for not recommending a competitive service? Again, all with absolutely no compensation?

I know they're doing well, but that doesn't mean we (as a society) should start assuming that they owe us.

They do owe us. Every bit of their success as a monster advertizing company comes from us using their services (a.k.a. ad bait). To the extent they reduce services, to at least the same extent they should lose revenue. In this case I'd argue that they should lose more than a proportional amount since they have harmed people through encouraging reliance on the service and by shading out and stunting competing translation services. Other free translation services lost a huge amount of traffic because of Googl

You can take harvested content, translate it into lots of other languages and present it back to Google. I would imagine that the translation both makes the copying harder to detect and messes with the translation engine itself. There are modules for wordpress that make automatic translation easy to add to any blog so it might be that a decent chunk of the properly tagged translations on the web are automatic Google efforts harmfully feeding back into the algorithm.

Aw, this is a bummer. We had a plugin that would autodetect the language and auto-translate in-game chat in the correct language to each user individually, based on geo-ip data. Since we have a pretty diverse group of players (Finland, Germany, Egypt, Sweden, French-Canadian, American) this can be quite helpful.

I suppose that if stories here had links that were foreign sources being run through Google, they'd get hit pretty hard. But instead of killing something like that I'd rather see a little header added at the top of the translated page with a "donation to thank Google" button. Disabling that functionality, or things like the "powered by Google" 3rd party OS X translation widget, would feel very much like censorship, and perhaps stir negative feelings towards Google in some..

Google Translate was abused several times in Taiwan. The most famous one was during the Asia Games, when one Taiwanese player got disqualified due to the already examined equipment. People used the translation suggestion link to submit false translations. When translating 'Koreans are ****' in Chinese to Korean and back it becomes "Actually we won".

I really like the idea of an open source, community content, translation system. Maybe, at some point in the future, Apertium might develop to the point it can be compared with Google Translate. Right now, it is no near.

Google supports nearly 60 languages, including all the most important languages worldwide. It can usually automatically identify the input language and provide understandable translations in any of the 58 supported languages. Apertium supports a handful of European languages, and canno

Absolutely right. I'm a translator. Google Translate can now be set to feed into memoQ, SDL Trados and probably other CAT software automatically. I don't know what the terms of service are on Google Translate but perhaps the 'abuse' they're talking about is partially related to the several hundred times per day that I and many other Trados and memoQ users hit the site via the API for a translation. The irony is, I blow the Google translation out without even reading it about 90% of the time. But since Trado

That's not at all the same. The old service was an API usable from any program. This new thing is a component that can be used on web sites. You can't use the new component in applications the same way the API could. Google also did the same thing with another service; the search API. They've removed the search API and are calling a custom search box for websites the replacement. No Google, that is not a replacement. They're fools if they think they're fooling anybody.

They are getting paid for my attention, and I am not. That's not "free". The cost of thing they give me is their payment for my attention, and yet it can not be worth what my attention is worth. So I'm still out something uncompensated.

What they're doing with search APIs is instructive.
Google closed down their SOAP search API years ago. They've deprecated their "AJAX search API" as well; that has two years of life left. There's still a search API for searching your own site: "Google Custom Search". But there's no API for searching other sites.

Translation is getting the same treatment. Translation will be available for your own site, but there will be no API for using it generally.

Seriously. I had just written the automatic string internationalizer last month for a new language & IDE (to be released as FLOSS). You set your locale/language, and the locales/languages you want to support, then as you are coding you can enter a string followed by an 'I' -- then the IDE will automatically build the language table section of the code for you, and depending on the chosen language of the other readers and/or coders they will see the correct text in their language. eg:

I'm actually using the API for a purpose for which I believe it was intended. People who send me messages on my site get the message filtered through the API and if it's in a language other than English, it automatically translates it to English so 1. I can understand it without manually copy/pasting it into Google Translate, 2. cusswords and other abusive language will get translated into English prior to being run through my abuse filter, and 3. it's just awesome to see your messages automatically transl

Well, given that they have an alternate way to use their service (their translate element), how long do you think it's going to take someone to wrap that in a externally accessible api, that opens the code, and clicks the button for us, then processes the resulting text. Screen scraping has been around for a long, long time.

You mean like the automatic translation of Android app descriptions in the Android Market (done, horribly badly, by Google)? I want my app descriptions in English, not in some horrible literal translation to a language Translate can't handle. Even worse is the translation of web pages going through up to three different translations (ie Hakku Chinese -> Mandarin -> English -> Swedish, or Nynorsk -> Bokmål -> English -> Dutch).