Many Pies

Many Pies
Showing posts with label translation. Show all posts
Showing posts with label translation. Show all posts

Wednesday, January 27, 2016

Emojis are a serious matter

Emojis are increasingly popular. ✏ If you can see a pencil before the word "If" then the device you're using has some support for them. They may seem like a bit of fun, but the fact that they have been included in the Unicode standard since 2010 means they are actually pretty serious. Or rather, that they are a valid means of communication which the Unicode Consortium has recognised.

😁 I don't see an emoji Bible coming anytime soon though (someone did have a go at creating a Kickstarter project for one).
🚀
The Unicode standard has new characters introduced at every revision, and for some revisions this includes new emojis. If you can see a chilli pepper here then you're up to date: 🌶. If you're wondering how they decide whether to include emojis then they've written a document on that.

There is a review process to introduce characters, and often some of the preparatory work in Bible Translation will feed into this review process. One of the early things in Bible Translation is to work out which script should be used. Some languages have never been written down before, and so there's a process involving the people who speak the language to see what they want to do. If it has been written down and some of the characters which aren't in Unicode then they will be submitted to this review process.

SIL, who do a lot of work on language technology have a group called the Non-Roman Script Initiative (NRSI) which has been working on technical issues do with fonts and writing systems. They recently celebrated their 20th anniversary.

Thursday, October 02, 2014

Translating tech jargon

A tech-related post on our Wycliffe blog - cookies, caches and cows - made my metaphorical ears prick up. It's about translating tech jargon into many different languages. The Economist article that it quotes says Firefox uses 40,000 words, but that sounds too high for me. I dug a bit into the Mozilla website to check it out. The process of translating words used in interfaces is called localisation or localization, depending on your locale, or l10n (that's L ten N as there are ten letters between the l and the n) to keep everyone happy. I suspect that figure is either the number of strings of words that need translating for Firefox, or for all the Mozilla products (including websites).

Thursday, August 08, 2013

Bible translation and copyright

Disclosure - I work for Wycliffe Bible Translators in the UK and we second people to other organisations to work on Bible Translation. I don't do translation, but I work in IT. I don't speak for Wycliffe Bible Translators UK.

I've had a draft post on copyright and the Bible sat around for ages, and today I came across this post by Michael Johnson, Bible Copyright vs. the Churchwhich describes many of the issues, and does it a whole lot better than I could. I'm not sure I agree with everything he says, but I do with most of it. So I suggest you read it.

I won't discuss the issue of making money, but there is also an issue about quality of translation. If a group of people put a lot of effort into a translation and then relinquish copyright and make it available digitally then someone else could take their translation, change the bits they don't like and republish it under the same name of the original translation. They may produce a "worse" translation, but someone's standards. Then there are two versions of this Bible. If the worse translation gets a lot of coverage people may blame the original group of translators for producing a bad translation, whereas they've done nothing wrong. 
Creative Commons may give ways of making the Bible available, whilst making sure it doesn't get changed, so those who actually publish copyright bibles could consider this.

What got me started on the original article was this post on Google+, which I post without comment. 

Update: There is the Every Tribe Every Nation project which is working to get Bible texts distributed in digital form. So those who own the copyright aren't necessarily holding onto the texts but are releasing them for use. It involves Wycliffe, Biblica and the American Bible Society. Youversion are one of the consumers of the texts.

Monday, February 11, 2013

CheckITOut - IT in Wycliffe

I'm involved in an event called CheckITOut - a couple of hours of info about IT in Wycliffe on 6 April 2013 in Coventry. We've got a number of speakers covering some interesting areas. I did a Prezi to advertise it.


Friday, February 08, 2013

Interesting Bible Translation and tech snippets

I was talking to someone this week who is working on various technical things that help Bible Translation. One is LanguageForge, which is like SourceForge, but for data on languages. So it could be used for translation projects when it's released.

Another is Graphite - "a free and open rendering engine for complex scripts". It's really useful when it comes to working on minority languages, may of which have complex scripts. It's now available in Firefox 11, LibreOffice 3.4+, Fieldworks and other software. So with support for translation tools, typesetting and web browsers you have end to end support for these scripts. Mobile devices are in their sights too...

Wednesday, October 17, 2012

Why analysing a hung SQLServer database helps Bible Translation

Our Executive Director sometimes tweets something like "Today I am helping the task of Bible Translation by writing papers for the board". (I can't find a recent example to embed.)

I just tweeted
Actually, I'm not doing that, but I'll tell you why at the end.

I thought I'd bridge the gap between the two parts of the sentence.

  • The SQLServer database hung while I was adding a new linked database.
  • The linked database connects to our worldwide personnel database.
  • (Although we're an  autonomous UK charity, we work in partnership with many other organisations, many of whom are also called Wycliffe. We send people to many of those other organisations, so we need a common personnel database.)
  • If you're working on Bible Translation then it's good to know who's working for you so you can look after them.
There are other links too:
  • The SQLServer has our Raiser's Edge database on it. That's the system we use to keep track of donations and mailings.
  • We send mailings to our supporters so they can hear about what's going on and pray for us.
  • We need to keep track of who gave us money, so we can thank them and Gift Aid (where appropriate) their donations.
  • We need to keep track of where the money's going to, so that it goes to the right place and so that we can keep to the legal principle that you have to give the money for the purpose with which it was given.
  • Money pays for translators salaries, amongst other things, so the translation can happen.
If the database keeps on hanging then that stuff can't happen, so I need to find out why.

Actually, I'm not finding out why it hung, I'm writing a blog post about it. That's because one of the unstated (until now) reasons I write this blog is so that IT people can see how they can use their skills in Bible Translation!

Tuesday, June 14, 2011

Comprehensive site on fonts, scripts and writing systems

One of the organisations that I follow the work of is the Non Roman Scripts Initiative (NRSI) of SIL. Getting Bibles into all the languages of the world that need them often means getting the Bible into all the writing systems of those languages, and the people at NRSI do a lot of work on getting complex scripts to work on modern technology.

They've recently launched their ScriptSource website. There's actually been something there for a few years, but only a few pages. However I can now see why it took so long to launch it properly - there's so much there - 181 scripts, nearly 7000 languages, 100,000 Unicode symbols (including the snowman). It's not just a site for information though, they invite contributions and advertise software needs.

I'm impressed.

Friday, September 21, 2007

Translation via Google groups

Here's a new thing:
Kusaal is a language of Burkina Faso (West Africa). A Google group has been created to help with the translation of Kusaal.

"We are inviting interested linguists worldwide to help with the analysis of Kusaal, using the Internet as a networking tool and this site as a collaborative working platform. Not only will your involvement lead to the development of an orthography and literacy materials for the Kusassi people, but you can help make significant contributions to the corpus of linguistic knowledge through write-ups of Kusaal phonology, grammar, and more (as we get the necessary data collected)."

Monday, May 14, 2007

Sign language project details

More details on the sign language project I mentioned earlier.

It's called WoSP which stands for World Sign Processor. It's "an attempt to
provide software to help the Deaf and others as they work on recording
sign-language data".

The WoSP notation will be a computer readable notation which contains the
component parts of signs, and also allows computers to generate rough 3d
animation and SignWriting ready for final editing. It needs to capture the
essence of signs, without missing out on detail, such as facial movements
and body movement, and without over-complicating things, such as capturing
the position of every finger to the micrometre.
Getting signs into the encoding is another challenge. "Just use motion
capture" I said to a colleague when discussing it. The trouble is motion
capture isn't a simple technology and converting lots of motion capture data
to the sign encoding is another challenge. The preferred method may be a
combination of choosing an existing sign plus some keyboard input, though
things are at an early stage.

Getting the information out again is the third challenge. Ideally you want
- static diagrams, maybe with arrows
- animated diagrams
- computer animated figures
all from the same source of signs.

There are other, smaller, challenges on the way, such as how you move from
one sign to another without the hands suddenly jerking.

Here are some more relevant links:

There's an excerpt from our prayer DVD on the subject of sign language
translations of the Bible
.

For analysing sign languages for translation purpose there is Elan
- "a professional tool for the creation of
complex annotations on video and audio resources "

tags:

Monday, January 15, 2007

Lausanne Bible Translation special

Lausanne, the people who brought you the First International Congress on World Evangelisation, have a Bible Translation focus in their current edition of Lausanne World Pulse. (If it's not there it will probably be in the archives.)

Very nice of them.

Monday, October 02, 2006

Support Bible Translation via eBay

During October you can donate part of all of the money you make on eBay to us via MissionFish.

tags: