When the clouds get dark it’s better have our things at hand, on the ground, as our feet …:
==== Why we will have web servers at home ====
http://sinwindows.wordpress.com/2010/12/22/por-que-tendremos-servidores-en-casa/

In the News: AT…

I’m using plugins based on googles API’s for easy translation of my Quebec sites. I will take a look at mygengo and see if that will work.

thanks again for the heads up could have been painful if i didn’t know

Some people have suggested other closed alternatives, like MyGengo, whose founder says “since our startup relies on translation, you can be guaranteed we’ll never deprecate our API ” — but that’s hardly compelling. As soon as they change their business model or get acquired by a larger organization, they may well drop it. And their API is no good if they go bankrupt or close shop for any reason.

What we need is an open API to a library of freely licensed and publicly maintained code — which should include wrappers that interfacing with a spectrum of options from automatic machine translation, to human-assisted translation that updates a free public translation memory, to private human translation.

Tools like those from MyGengo or Babelfish or MS or (for the next 6 months) Google, which are public in a sense but could be killed without warning, could be available as options provided through these public wrapper. But updating a service that uses one of those tools to use a different one should take minimal effort.