I think the point was not to have machine translated garble, as it's not 100% foolproof and sometimes technical things can be erroneous. :) Not a bad idea if we can tag it with something like "tr-needs-verification-de" or whatever language it is and clean it up afterwards, whether that be a native speaker or English.
On Wed, 2010-10-13 at 05:24 -0500, Jordon Bedwell wrote: > On Wed, 2010-10-13 at 11:18 +0100, Roy Jamison wrote: > > Actually, I've just had a thought and it incorporates both ideas. > > There is no reason why we couldn't do both, i.e. if someone *only* > > speaks English, there is no reason why they couldn't translate it > > themselves. Use Google translate or Babelfish or whatever, and translate > > the "broken English" output from that into something legible. > > > > Then everyone can do a bit and play their part. Obviously obscure > > languages with <100 Ubuntu users would need to be done manually by a > > human. > > > > Just an idea :) > > Or... automatically: http://code.google.com/apis/ajaxlanguage recently I > had the chance to work with a company that was using that exact API to > do on the fly translations of their entire website. Mixing Google Ajax > API with JQuery you get some pretty powerful results. > -- Roy Jamison (xteejx) Ubuntu Bug Squad Ubuntu Bug Control www.ubuntu.com _______________________________________________ Mailing list: https://launchpad.net/~ubuntu-bugcontrol Post to : [email protected] Unsubscribe : https://launchpad.net/~ubuntu-bugcontrol More help : https://help.launchpad.net/ListHelp
