What’s wrong with Google Translate?

Three things you probably shouldn’t say to a translator? Here you go:

  • “Actually, Google Translate is sufficient to get my message across”
  • “Isn’t machine translation going to take all your work in the future?”
  • “You translate? Cool, I’ve got an app for that.”

Everyone in the industry has to endure conversations like these. And I mean everyone. The world prophesises our inevitable future unemployment and it’s nothing new.

The fact is technology is improving; it’s also true for the translation industry. Machine translation (MT) and localisation software will be disruptive for sure. But they are more than likely to aid translators rather than make them redundant.

Time and again, people neglect to check automated translations and the results are posted online for posterity. These MT mistakes range from amusing hotel signs and unappetising menus through to, at their worst – or best if you’re partial to Schadenfreude – awkward tattoos.

Something this bad can’t have come from a human being, surely?

Sure, we’ve all seen examples of translation fails, but what about Google Translate? It can’t be that bad, right?

Well, it’s certainly not the worst machine service out there. In fact, as far as they go, it’s pretty decent. But it never produces any sizeable amount of text you can depend on. And this is a problem. Non-linguists often trust the result and miss errors. Embarrassing errors. But above all, costly errors.

If you want to convey your message abroad, you should hire a professional because, in the end, your brand and bottom-line are at stake. Get in touch, I’ll be happy to hear from you!

 

Have you come across any funny translation fails? Share them in the comments!

Share this:
facebooktwittergoogle_pluslinkedin

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>