Thoughts on Antiquity, Patristics, putting things online, information access, and more
Rather excited by the discoveries that AI would translate medieval Greek, I thought I’d try another attempt at that Ge`ez text that I put into Google Translate some time back. That is a homily on St Garima by a certain bishop John. I found the text on my disk, and put a paragraph into Bard AI. Nope. It wouldn’t play. Then I tried ChatGPT 3.5. That churned out the Nicene Creed, as a supposed translation.
You can’t trust AI. It can and will generate garbage. You have to be able to check.
In my last post I found that it was possible to turn a PDF full of images of Amharic text into recognised electronic text using Google Drive, and then get some translation of the results into English using Google Translate.
There were some extremely interesting comments made on the post, which I have been reading. I have also prepared a PDF of the whole text of the Life of Garima by Yohannes, and run that through the Google Drive process.
Where we started was in trying to read a passage of this text, in which – supposedly – God stopped the sun so that St Garima could copy the bible in one day. The summary of the work given by Rossini (instead of a proper translation, drat him), indicates that this was on lines 356-60 of his text, which turns out to be the last line of p.161 and the first three of p.162. Here they are:
The output from the OCR is good, but you still have to compare the characters carefully. Errors can often be picked up just by dumping the raw scan output into Google Translate, which shows things like numerals.
Here we have a character that is plainly wrong, and coming out as a numeral “4”. It looks like an “o” with a hat and two dots under. The two dots under are legs in another copy of Rossini.
I’m guessing that it’s a “ge” character, from looking at the Wikipedia article, but I can’t be sure. The script isn’t an alphabet, but a syllabary, based on syllables. Each character is a consonant followed by a vowel, which makes for a lot more characters. There’s a table of the characters on the Wikipedia article, consonants down the left, vowels across the top. I’ve not really looked at this.
The Google translate output is also interesting because of the choice of “detected language” – Tigrayan, rather than Amharic. If you force it to Amharic, you get a lot less meaning.
One awkward part of using Google Drive to do the OCR is that it doesn’t preserve the line breaks. That makes comparing the lines more awkward. So you have to manually do this:
፬ ፡ ወኮነ ፡ በአሐቲ ፡ ዕላት ፡ ወነሥአ ፡ መጽሐፈ ፡ ወቀለመ ፡ ወወጠነ፡
ይጽሐፍ ። ወተንሥአ ፡ ለጸሎት በሰርክ ። ወጸሐፉ ፡ ሎቱ : መላእክት ፡ ወንጌ ለ ፡
በ፬ ፡ ሰዓት ፡ ወትርጓሜሁ ። ወመላእክተ ፡ እግዚአብሔር ፡ ወትረ ፡ ይት ለአክዎ ፡
ወእግዚእነሂ ፡ ክርስቶስ ፡ ያንሶሱ ፡ ምስሌሁ ። ወተሰምዐ ፡ ዜናሁ :
ውስተ ፡ ኵሉ ፡ ሀገር ። ጸሎቱ ፡ ወበረከቱ ፡ የሀሉ ፡ ምስሌነ ።
The Wikipedia article mentioned earlier gave me a list of punctuation marks. There are two sorts of punctuation visible in here. The colon mark is actually word division, which means that some words above go over two lines. I’ve chosen not to split words above. The double colon mark “::” is the full stop. Interestingly Google Translate gives different results if you remove the spaces!
Going through the electronic text, removing spaces, I notice that sometimes the word-separator isn’t detected by the OCR. So I added that in. Sometimes it put a Roman colon instead, so I replaced that. Finally I split on sentence:
፬፡ወኮነ፡በአሐቲ፡ዕላት፡ወነሥአ፡መጽሐፈ፡ወቀለመ፡ወወጠነ፡ይጽሐፍ።
ወተንሥአ፡ለጸሎት፡በሰርክ።
ወጸሐፉ፡ሎቱ፡መላእክት፡ወንጌ ለ፡በ፬፡ሰዓት፡ወትርጓሜሁ።
ወመላእክተ፡እግዚአብሔር፡ወትረ፡ይትለአክዎ፡ወእግዚእነሂ፡ክርስቶስ፡ያንሶሱ፡ምስሌሁ።
ወተሰምዐ፡ዜናሁ፡ውስተ፡ኵሉ፡ሀገር።
ጸሎቱ፡ወበረከቱ፡የሀሉ፡ምስሌነ።
And run it again and I get this:
But this still is not good enough to do much with. If we didn’t have an idea what the text said, this would not tell us.
All this fiddling about would certainly get to into contact with the language, and start you on a journey to learning it. But it’s not good enough a translation for other purposes, although intriguing.
One suggestion that was made in the comments to the last article was that ChatGPT gave better results. The output quoted was indeed produced, and was very smooth and seemed to be a series of liturgical prayers. But… I don’t think that this is actually the content. These AI tools are really only an improved version of the text prediction tools you get on messaging on a mobile phone. So it was pumping out garbage.
Anyway I tried it on this passage, and it crashed GPT very effectively! At the moment I can’t get any reply of any sort, not even to “hello”.
I don’t think that I will do more here. Clearly the technology is almost, but not quite good enough to be useful.
In my last post I mentioned how the Life of St Garima in Ethiopian was printed by Rossini, but without a translation. In fact it has never been translated into any modern language, to my knowledge. I don’t know any Ethiopian, and I doubt that I ever will.
But we live in an age of wonders, when it comes to unfamiliar languages.
So… is it possible to work with Ethiopian language editions, even if you know no Ethiopian? What about Google Translate? Ethiopian is in this heavy unfamiliar script. Is there OCR for this? If you can scan Rossini’s edition, can you pop it into Google Translate and get the English?
There are two sorts of Ethiopian out there, I know. There is Ge`ez, or classical Ethiopian; and there is Amharic, the modern dialect. Rossini printed his text from a 19th century manuscript. So it seems likely that this is in Amharic.
A quick Google confirmed; Google Translate knows Amharic! A bit of googling found me an Amharic news website online, here. I’m using Chrome, so all I had to do was right-click anywhere and select “Translate to English” and the whole website was rendered into some sort of English. And… it worked!! Yay me! It’s obviously not 100%, but it’s way better than 0%!
So what about OCR? I was sad to see that Abbyy Finereader apparently doesn’t support Amharic. That’s a blow. It was developed originally to handle Cyrillic, so it certainly has the capability. But it’s not offered. Drat.
A bit of googling brought me to a dubious-looking website here, claiming to offer a selection of tools which could do Amharic OCR. The prose felt a bit machine-generated, so I worried that it was bunk, or worse, a malicious site. But the first option was… Google Drive.
I never knew this, but seems that, if you upload a PDF containing an image of text, and then open it in Drive as a Google Docs document, it OCR’s the content.
Well, I thought, let’s give it a try. So I extracted the first page of Rossini’s edition, using Adobe Acrobat Pro 9 – no flashy latest-edition stuff going on here! Here’s a pic:
Then I uploaded it, and opened as a Google document. And … it just treated the Amharic as an image. Dang! But I noticed that it did indeed OCR the Italian at the top of the page!
This is supposed to work. So I thought maybe I should work over the image a bit. I imported the one-page PDF into Abbyy Finereader 15, and chopped off the Italian at the top, and the critical apparatus at the bottom. I then used the image editor in Finereader to “whiten the background”. This can be flaky, but this time it worked fine, and I got a pure white background. And I got this:
(I’ve just seen the marginal notes, which I need to chop off as well, so I’ll have to go round the loop again)
I exported the image as a PNG, and I used Acrobat again to create a PDF from the image. Then I uploaded the new PDF to Google Drive, and opened it as a Google Docs document. And… it worked! Sort of…
በስመ : አብ : ወወልድ ‘ ወመንፈስ ፡ ቅዱስ ፡ ፩ ፡ አምላከ ፡ ላዕሌሁ ፡ ተወ ከልኩ፡ ወቦቱ ፡ አመንኩ ፡ እስከ ፡ ላዓለመ ፡ ዓለም ፡ አሜን ።
ድርሳን ፡ ዘደረሰ ፡ ቅዱስ ፡ ዮሐንስ ፡ ኤጲስ ፡ ቆጶስ ፡ ዘአክሱም o ፡ በእንተ ዕበዩ ፡ ወክብሩ ፡ ለቅዱስ ፡ ይስሓቅ = ወይቤ ፤ ስምዑ ‘ ወልብዉ ፡ ኦአኀውየ 5 ፍቁራንየ ፡ ዘእነግረከሙ ። ርኢኩ ፡ ብእሲተ ፡ እንዘ ፡ ይዘብጥዋ ፡ ዕራቃ ወእንዘ ፡ ይሀርፉ ፡ ላዕሌሃ ፡ ወላዕለ ፡ እግዝእትነ ፡ ማርያም ፡ እንዘ ፡ ይብሉ በእንተ ፡ ወልዳ ፡ ክርስቶስ ፤ እምብእሲት ፡ ኪያሁ : ኢተወልደ ፣ ይብሉ ፡ እላ ፡ ኢየአምኑ ፡ በክርስቶስ = ወኮንኩ ፡ እንዘ ፡ እረውጽ ፡ ወአኀዝኩ እስዐም ፡ ታሕተ ፡ እገሪሃ ፡ ለይእቲ ፡ ብእሲት ፡ እንዘ ፡ ትብል ፤ እወ ▪በዝ ፡ አንቀጽ ፡ ወፅአ ፡ ንጉሠ ፡ ሰማያት ፡ ወምድር ። ወሶበ ፡ ትብል፡ ከሙዝ ፡ ወ
That’s… rather astonishing. No idea what all that is, but it looks sort of right. Let’s bear in mind that Rossini printed his edition in 1897. This is not a modern typeface. So this is rather good.
Next step was to paste it into Google Translate. It set it to auto-detect the language, and pasted in the first bit. And… it worked. In fact it gave a really useful transcription into Roman letters as well, which makes it a LOT easier to manipulate the text.
OK, I’m cheating slightly. The first time I uploaded, the translation ended at “Spirit”. But this is a Google Translate bug – it sometimes omits the remainder of a sentence. If you split the text with a line feed, you often get the rest. And that’s what I did. I worked out by experiment where I needed to be, and then I got the above.
I don’t quite believe the translation of the second sentence either. I suspect I need to play with this a bit to work out what each word is.
I notice all those colons between every word. It might help if I actually looked up the script online!
But I think you’ll agree that this is quite marvellous – I, who know absolutely nothing about the language, am getting something useful out!
Magic!