Automated page translation with Google

[Unknown W. Brackets]

Actually, this was true of my project as well.  Not all of it, of 
course, and we used versioning to see what had changed... but large 
segments could change between releases and things always had to be 
retranslated.

Of course, we tried to minimize this... but the volunteers were always 
willing to keep at it!

Effortless is as effortless does, in the end.

-[Unknown]


> The real problem is that the documentation changes regularly, 
> invalidating the translation work.
> 
>> Even so, automatic translation just cannot compare to the real thing. 
>> Not without smarter routines than we have now.
> 
> I know. But it's:
> 
> 1) effortless
> 2) always in sync with the constant changes to the documentation
> 3) reasonable to expect google will get better at it over time, and such 
> improvements will be automatically incorporated