Skip to main content

Why we Don't use Google Translate

I often get asked, 'So, why don't you use Google translate? Or, worse, 'I suppose these days you just use Google translate (GT) to translate the Bible.'

Here are several good reasons not to use GT:
1. Most minority languages are not on GT. The one we worked on only became available fairly recently, after the Bible was already translated.
2. GT uses a statistical method, relying on having lots of texts available in the language, and lots of translations of those texts into other languages. It then compares the two and guesses the translation. For minority languages, those don't yet exist in books, let alone online.
3. If you do use it it requires heavy checking and editing of the translation afterwards, which takes time, so you haven't gained anything. This is because it guesses the translation. Google does not, as far as I know employ real translators. The only way of improving the quality of Google translations is for many many people to click 'improve translation' and give Google feedback that way. Since minority groups are small, and often lack internet access, this isn't likely to happen. Bible translations need to be accurate, clear and natural. GT will give you an inaccurate, unclear and unnatural translation.
4. Google can't spot idioms like to 'run a meeting' or euphemisms like 'to pass on'. Nor can it cope with metaphors. A book like Isaiah is about 90% metaphor and 10% not. So Google can't understand Isaiah let alone translate it (you might be thinking you don't understand Isaiah too, but I'm sure you get it better than Google does).
5. The hardest thing about translation is people and cultures. Google is not into relationship building or anthropology 
6. The next hardest thing is linguistics, which is not as predictable or mechanical as people think. Why would it be? Languages vary hugely. Few, even within language groups, are similar to each other. To under the linguistic problems in a text requires a Master's degree or higher. A BA would work for simpler texts. GT doesn't have one of those.
7. GT doesn't understand the differences between audiences. One translation won't usually work for different audiences, hence the plethora of translations of the Hebrew and Greek Bible into English. What we're trying to do is produce the first ever translation of the Bible into a given minority language. It can't choose which audience to translate for, let alone the purpose of that translation i.e. how it might be used. These days we don't start translating until we have got those kinds of answers nailed down, or rather community leaders have.

So, Google translate doesn't work for Bible translation. Guessing just won't cut the mustard.

Comments

Popular posts from this blog

One Person's Contextualisation is Another Person's Syncretism

I was in an interesting discussion full of anthropologists the other day. They were discussing syncretism. Most of them were of the view that outsiders cannot decide which practices are syncretistic and which are not. It has to be a decision made by local believers. This is because only local people can create indigenous theologies, that is, interpret Scripture according to the local worldview(s).  Not only that, some practices need to be tolerated in the short term, as we trust that new believers will gradually mature, and realise that those practices need to be weaned out of their lives. This can take time, perhaps years. Outsiders can, however, help local believers through the process of deciding for themselves which practices need to be rejected, which can be accepted, and which need to be modified according to (local formed) principles from Scripture. For example, ancestor practices, which my PhD thesis was on, are often continued by people after they have come to faith. They...

Scripture Engagement for Translation Advisors

What do translation advisors need to know about Scripture engagement (SE), and why? Let's look at the 'why' first: Translation advisors (TAs) are often involved in day-to-day exegesis. They help mother-tongue translators (MTTs) prepare drafts. The MTTs they work with might not know Hebrew or Greek. The TAs then take part in the team check of that draft, which involves other MTTs in the project as well as the TA. Sometimes they are also involved in the coordination of the translation programme. They are very busy people. So why do they need to know about SE? Because: The translation is ultimately for an audience that has felt needs that are not being addressed by the translation programme. Analysing and meeting (or helping to meet) the felt needs of the audience should be the first priority of any mission worker, including TAs. Only about 30% of completed translations are well used. The initial set up of the programme needs to take SE into consideration (it's no good wai...

Scripture Engagement Training

At a forthcoming workshop, I have the privilege of offering a face-to-face three-day training track about Scripture Engagement (SE), teaching some principles and working together on real life issues you may face in your project or region. There will also be a mini SE training track on SE research. In some Bible translation circles it has been taken for granted that Bible translation on its own, or Bible translation plus literacy, will solve all of a community's Scripture access problems. Unfortunately, this has not always been the case. There are many factors, including illiteracy, multilingualism, fear of persecution by the majority group, lack of knowledge of the background to the Bible, and problems with distribution (or the Bible being distributed in an unhelpful media or format). Specialists in Scripture Engagement help those involved in the wider Bible translation movement such as exegetes and programme managers explore some of the different things that help or hinder people...