Posts Tagged ‘translation’

Google Translate: Swahili… bado kidogo

Thursday 27 August 2009

In the last couple of days Google has added Swahili to the list of languages supported by its Translate service. On one hand I’m very happy to see this addition as I think it has the potential to be a big step forward for development in east Africa. However, from first impressions the service still has a long way to go.

One of the main problems for Google is that Swahili is an agglutinative language – meaning that it puts morphemes (grammatical parts of words) together to form longer words. So it can be difficult for a machine to know where the morphemes (parts of the word carrying meaning) begin and end.

Here are some very simple examples that I tried putting into Google:

Swahili Morphemes English Google Translate
kupika ku-pika to cook cooking
ninapika ni-na-pika I am cooking I cooked
nilipika ni-li-pika I cooked I cooked
nitapika ni-ta-pika I will cook I cooked
sijapika si-ja-pika I have not cooked I cooked
apike a-pik-e let him cook apike
umepika u-me-pika you have cooked has cooked
tutapika tu-ta-pika we will cook we cooked
watakapopika wa-taka-po-pika when they will cook will kakopika
mlipokuwa mnapika m-li-po-kuwa m-na-pika when you (pl) were cooking as they were cooked
ikipikwa nasi i-ki-pik(w)a na-si if it is cooked by us it be boiled us
bado kidogo bado ki-dogo not quite yet still little

To be fair, from what I’ve seen the translations of single words isn’t bad at all. Where it falls down is in the grammar – translating Swahili past, present, future and negative-perfect tenses all to English past!

Going the other way, here a few English examples I tried:

English Swahili Google Translate English back-translation
many people watu wengi watu wengi many people
many trees miti mingi miti mingi many trees
many elephants tembo wengi wengi tembo many elephants
many cars magari mengi wengi magari many cars
I am cooking ninapika I am kupikia “I am” to cook with
I cooked nilipika mimi kupikwa I to be cooked
To be fair, from what I’ve seen the translations of single words isn’t bad at all. Kwa kweli, kutokana na yale ambayo nimeyaona, utafsiri wa maneno ya pekee siyo mbaya Kuwa na haki, kutokana na yale I’ve amemwona zote maneno ya wimbo sio mbaya wakati wote. In truth, coming from what “I’ve” he has seen all
words of song not bad all the time

At this point it looks to be a decent dictionary (although with nothing like the depth of the excellent Kamusi Project), and actually does ok with set phrases. However once you get past the set phrases that it knows it seems unable to understand the relatively simple grammar and come up with a meaningful translation.

This is obviously a work in progress, as the “Contribute a better translation” option shows. It would be interesting to know whether Google takes these user contributed translations and tries to work out how the grammars and structures of the languages compare, or whether it simply remembers the set translation in case anyone enters the exact same phrase again. The first would be fascinating to investigate, whereas I fear the second would be like trying to empty the ocean with a teaspoon.

Advertisements

Google still has a long way to go

Monday 25 August 2008

Google now has a homepage for its search engine in Swahili: http://www.google.co.tz/

According to this page Google has translated at least 1% of its main site in 152 languages. Not bad, especially considering that these languages are spoken by several billion people worldwide.

According to Wycliffe Bible Translators, the most translated book of all time, the Bible, has been translated into 438 languages. Another 2,016 have at least some of the Bible translated into them.

But that leaves over 2,200 with a need for Bible translation and no project yet started. Many of these languages don’t have a written form, so in order for the Bible, Google or any other text to be translated and written down, an alphabet and writing system must first be developed.

The efforts of Google and others (like Ubuntu, who are currently translating into 189 languages) are to be applauded, and will make their products accessible to the vast majority of people worldwide. But for the Bible, a message from God’s heart to man’s heart, it’s not enough to translate into the 150 or 200 most major languages in the world.

Rather, the message of God’s good news to all nations must be made available to each and every person in the language of their heart, however uneconomical it may seem. No businessman would ever translate his product into a language spoken by 100 people in a village in Papua New Guinea – it just doesn’t make business sense. But then not many shepherds would leave 99 sheep on their own in order to search for the one sheep that wandered astray.

Which is why the Bible will always be the most translated book. God has created each and every person uniquely and loves them just as they are. He will stop at no lengths to draw each person to himself. If we are to reflect God’s character as we join in with his mission to the world, we must make the Bible available to every person in their own heart language.

Translation Services

Saturday 7 June 2008

In the office the other day I received a phone call from a friendly chap from a company that offers translation services. He was offering the services of his company to Wycliffe, wondering if we were interested in outsourcing any of our translation work.

I patiently explained that our translation work is done in cooperation with churches and individuals who are mother-tongue speakers of minority languages, so I didn’t think his company would be able to help us very much. Looking back, I probably should have taken him up on the offer and asked for a quote for translating the Bible into 2,300 unwritten languages