Comments on: Google AJAX Translation API

By: Translator

Translator — Sat, 06 Jun 2009 01:56:03 +0000

Nice one thanks for posting this. Such a simple implimentation for language translation. All we need now is for the mechanical translation to improve but i’m sure google is working on that.

By: cutouttranslations

cutouttranslations — Sun, 18 May 2008 11:07:20 +0000

Languages with different word order like Japanese will never be accurate using this method. If you want to learn almost any language in the world so you can understand them properly, my site helps you to do it the easy way.
http://www.google.co.jp/search?q=cutout+japanese+english+cutouttranslations&btnG=%E6%A4%9C%E7%B4%A2&hl=ja&lr=lang_ja&client=firefox-a&rls=org.mozilla%3Aja%3Aofficial&hs=k5L

By: ThomasSturm

ThomasSturm — Tue, 01 Apr 2008 15:51:37 +0000

There seems to be indeed a limit on the text chunks that can be translated. We've implemented the new API for MapSkip and we simply break the text into paragraphs and run those through the API individually. From our experiments, the limit seems to be roughly 1400 characters.

By: Afraithe

Afraithe — Mon, 24 Mar 2008 11:24:58 +0000

Nice, now if only the google toolbar spellchecker would be available as a good API…

By: aleksraiden

aleksraiden — Sun, 23 Mar 2008 11:15:58 +0000

Of couse, the Google API have limitation – only up to 500 char are translated at onse, but no limit to translate request’s from one site/page

By: aleksraiden

aleksraiden — Sun, 23 Mar 2008 11:11:40 +0000

By: choonkeat

choonkeat — Sun, 23 Mar 2008 07:30:34 +0000

Wonderful! I've updated my previously-server-side app to fully JS. Tryanslator is probably the least fuss, user-friendly translation service :-)

By: michaelhart

michaelhart — Sat, 22 Mar 2008 21:59:23 +0000

Err, “translates the”, not “translates to”. My own writing sounds like it was run through Google translation too many times…

By: michaelhart

michaelhart — Sat, 22 Mar 2008 21:57:36 +0000

@minimalmedia — very nicely done, except for one thing: you’re not caching the source text. If I click, say, “es” to translate a paragraph to Spanish, then click “en” to go back to English, instead of restoring the original English text, it translates to Spanish translation back into English, introducing translation artifacts. Eg. “Put to work on his own blog, or better yet, somehow better” instead of the original, “Put it to work on your own blog, or better yet, improve it somehow.”

By: kadnan

kadnan — Sat, 22 Mar 2008 12:12:28 +0000

I wish there is support for Urdu as well.

By the way, is there anyway to detect whether the language is RTL or not?

By: minimalmedia

minimalmedia — Sat, 22 Mar 2008 11:31:52 +0000

@Cory, there is a script here to make arbitrary html elements translatable.

By: MadeByChad

MadeByChad — Sat, 22 Mar 2008 02:49:42 +0000

I played that 138 times… it’s addicting!

By: ingdir

ingdir — Fri, 21 Mar 2008 21:24:55 +0000

For English-Russian translations, the demo above provides strange results: words are translated mostly correctly but some of them appear in the wrong case (genitive instead of nominative, which are spelled differently in Russian), and some have their first letter capitalized for no obvious reason.

By: Cory

Cory — Fri, 21 Mar 2008 20:24:49 +0000

I’m interested in trying out the performance for entire pages, such that I can let a user select a language on screen, and the content is automatically translated.

By: SchizoDuckie

SchizoDuckie — Fri, 21 Mar 2008 20:03:31 +0000

Naaaaais! Now for the optional translational-correction api so that we can all improve their services. EN => DUT translation *SUCKS* big time!

By: leftist

leftist — Fri, 21 Mar 2008 19:29:48 +0000

This is awesome!