A broad overview of localisation progress in Africa, focusing on the history and progress made so far. Looking at the contribution of open source, Microsoft, Google and other players over the years.
The aim of the talk was to inform attendees to the ICANN International Domain Name workshop on the area of localisation. As well as to highlight how IDNs are part of the area of enabling localisation.
2. Speak to a person in a language that they
understand and you speak to their head.
Speak in their language and you speak
to their heart.
Nelson Mandela
4. What we do
Strategy – helping governments and
organisations build localisation strategies
Enabling localisation – can you type and see
the web
Tools – building simple localisation tools for
communities with low skills and poor
connectivity
Training – increasing localisation skills
5. How we go about it
We help organisations to localise their software
using community resources.
We build software such as Pootle, and share
our skills and experience that make this
possible.
We’re helping Mozilla, LibreOffice and others to
grow their long tail localisations.
7. Back localisation - Tools
Pootle – online translation. Used to localise +50%
of Firefox localisations.
Virtaal – desktop translation tool for the majority of
the world that has very poor connectivity
Translate Toolkit – localisation engineers swiss
army knife
AmaGama – very large open source translation
memory
8. Looking at Africa
Unless a language is active in the intellectual
domains of the day, it is a dead language
Neville Alexander
9. Where have we come from
✔Missionaries transcribing
✔Inventors of scripts and orthographies
✔Often rich publishing histories
10. Generations of localisation
✔ 80s - 8 bit encoding. Ironically an age of
innovation, N’ko custom layout software
✔ 90s - Windows 95, seems like we forgot how to
localise
✔ 00s - open source communities, Microsoft LLP.
Cost isn’t all of it.
✔ 10s - phones and mobile. Twitter, Facebook
and a real age of communities. But maybe a
loss in terms of ownership and influence
11. The areas of localisation
•Enabling technology
• Encoding, Font, keyboard, locales and I’ll
include IDNs
•Localization/Translation
•Resource creation
•Support services
• Machine Translation, Spell checkers
12. Why are IDNs critical?
The feeling of belonging
Mechanical imperialism
13. African Network for
Localisation (Anloc)
●
Worked to create a list of characters needed
for Latin-based African languages
●
Made various keyboard layouts
●
Built free localisation tools
●
Provided training across the continent
●
Built terminology for the ICT domain
14. How are things looking in
Africa
From almost nothing
Enabling technology in a good state for consumption
Active localisation of Microsoft products
Google is an active localiser starting with their four
core languages and now moving on.
Machine translation (however bad you think it is) in a
number of languages
Firefox and Firefox OS - growing number of languages
in Southern Africa and West Africa.
15. Where are we headed
We shouldn’t be worried about IDN use right now but
rather ensuring future use.
Use soon that will be critical as without IDNs we won’t be
able to make domains that are properly reflective.
We have issues of local language literacy now.
But if we can’t type names correctly now then solving it
later will be problematic
We already have poor data for Venda and Yoruba
because people don’t use diacritics because their
software failed them
16. Call to arms
IDNs aren’t going to help people type
They aren’t going to create new content
But they are going to eliminate a barrier that
prevents the internet just feeling like its
always been a home for African languages
We have an opportunity now to change that
before its too late.
Editor's Notes
Dwayne Bailey is the Director of Translate. Translate focuses on a number of priority areas designed to assist other to localise software.
The difference between a mechanical understanding and a passion.
In Africa, certainly in Latin, we can get away with not doing African languages. But that is like the head. If we do African languages, that is the heart. It is the feeling that the Internet fully understands who you are and that you are at home.
We have a long history of working with Mozilla and Firefox.
Through Translate.org.za we helped to localise Firefox into the 11 Official languages of South Africa.
Work that Translate lead within Anloc allowed us to assist other languages.
We have been contracted by Mozilla to help with amongst other things, other African and other long tail labguages.
Our areas of focus are designed to create an enabling environment for local languages.
Our aim is to work with local institutions, governments and people to address enabling issues and to skill local volunteers and professionals.
When working in the long tail we’re often faced with communities of one person.
Sometimes when we think communities we think of rather large Facebook and Twitter localisation teams.
Our work and effort is designed to recognise and empower such small teams so that even one person can impact their language.
Our traditional view of localisation is translating something from a dominant European language (usually English) into a local language.
Back localisation is where solutions designed in the target market are valuable to the wider world
The tools that Translate created for addressing African localisation needs, e.g. poor technical skills and poor connectivity are useful in the developed world. Thus these tools designed for South Africa have become much more useful to a wider audience.
The late Neville Alexander was an educator, linguist, language activist and political prisoner. He spent time on Robin Island with Nelson Mandela, famously starting the university on the island to educate political prisoners.
This rather stark comments raises the concern that if a language is not active in IDNs, Science, Maths, the Internet then it will be relegated to a language of tradition, culture but won’t be used for real work.
Africa has a rich tradition of caring and promoting our languages. They have coped quite well in previous year. We’re simply trying to make sure they operate in the present connected world.
Looking at the various focus areas of localisation, expanded slightly from the traditional view of what localisation would be.
Not listed here are efforts the reflect advancements in each of these areas as they impact African languages.
When our language can be expressed n domain names then we feel as if the internet was built for us.
Mechanical imperialism is where failures in technology force languages to adjust. A more correct approach is the address the limitation of the technology to accommodate our languages.
Some of the positive contributions of the African Network for Localisation that impact IDNs and are of the same level of concern as IDNs.
Reflecting on how things have changed over the last 15 years in terms of representing African languages in ICT.
Raising the importance of addressing IDNs now. If we don’t, as happened with keyboard, then the long term damage is quite severe.
So even though we might not see users or a demand it needs to be addressed to allow the language to operate properly.