Strength in Numbers: The Internet Freedom Movement Must Be Localized
This post is one in a series of blogs to complement our 2018 crowdfunding campaign, Strength in Numbers. Anonymity loves company and we are all safer and stronger when we work together. Please contribute today, and your gift will be matched by Mozilla.
The Tor Project is an umbrella for many different projects. Some have a user interface and others are running in the background. Our aim is to make Tor and Tor Browser usable all over the world, and to do that we need to localize our tools and resources. In July, I joined as the Localization Coordinator and have been working on localization with the rest of the Tor team.
What is the difference between localization and translation? The aim of localization is much broader than just translating strings of words. To localize an application means to ensure that the application stays relevant in the local context, is understandable, and is usable.
In this, I am helped by Tor’s UX and Community teams. They work with groups of users around the globe, conducting user tests and identifying problems that have made Tor difficult to use in certain contexts; for example, when a user does not have a reliable internet connection. If we develop applications that only work with good connections, a lot of people will not be able to use them, or their experience will be frustrating. Tor developers have since worked on those issues, and now Tor performs better when the connection is poor.
Working on localization is more interesting when you consider what you learned in History class back at school: the current situation of localization on the internet reflects how colonialism and cultural imposition have shaped the language landscape around the world. English is the most common language used on the internet. Sadly, people that have been colonized by the English or Spanish and have lost their original language have it easier on the internet than others. Even as a native Spanish speaker, I felt like an underdog on the internet. Little did I know what being an underdog on the internet meant. At least we can write most of our language in ASCII code, the character encoding standard for electronic communication which helps display the right letter, so we can communicate even when there is no possibility of writing in correct Spanish, and at least Spanish is written from left to right! But other languages have it harder. Moroccans and other Arabic speakers must often resort to French when online because the local dialects have no written standards, and forms and websites do not support Arabic well. Some languages have characters that are not even part of UTF-8 yet, so their letters cannot be displayed on the computer. In some countries with lower reading levels, icons and drawings play a much bigger role on delivering a message. We don’t want these differences to be a barrier to using tools that protect people from tracking, surveillance, and censorship on the web. Localizing technology can even play a role in ensuring a native language survives. When more and more contributors join the movement to localize the internet, the stronger and more sustainable this work becomes.
Translating for local contexts takes a world of considerations
For the actual translations, I am helped by an army of volunteer translators from around the globe who donate time and skills to translate open source software to their local languages. This is also done with the support of Localization Lab. When it's sunny outside, volunteers sit behind their computers and translate strings like 'Accept,' 'There was an error,' etc., for free. The reasons why individuals volunteer to do translations vary as much as their personal circumstances, but in the end we all benefit from their work, and I want to use this opportunity to thank them again: thank you!
The work can become more complicated based on what has come before. Some volunteers are working on translation projects in languages that have an existing collection of text on Tor and censorship circumvention; these volunteers must integrate their work into previously translated material. But others are translating many terms for the first time, and so they debate about which local term will make the different metaphors, such as bridges, make sense in their language and context. This process often involves terms related to other applications or general internet security terms that have not been previously translated. It is a long process, but it brings the apps closer to the local people. Some translators argue against anglicisms, or the direct use of an English word in another language, but then the users may complain about not understanding the translation because they are used to the English terms. Each situation is different and requires careful attention.
Translation and localization require many volunteers, many minds, and lots of time. When we do this work together, we can do more research, hear more voices, and finalize our work faster. In our mission to localize the internet freedom movement, there's strength in numbers.
What we’ve done so far
- Tor Browser now supports 25 languages, and 4 additional languages are supported in alpha
- We started tweeting more often in languages besides English
- We published additional subtitles for the Tor Animation
- Now we have better statistics about our language support
- We are working on localizing our user support website and the Tor Browser User Manual, with more languages added every month
We have decided on a priority list for localization, and we would like to eventually release all our software (more than just Tor Browser) in at least these 12 languages: English, Farsi, Spanish, Russian, Simplified Chinese, Portuguese, French, German, Korean, Turkish, Italian, and Arabic. To decide on this list, we took several circumstances into account: the countries that are more likely to endure censorship events, the most downloaded locales, and the countries our users come from--especially the bridge users.
My main goal is to have our content, including the user documentation, relay guide, and more, in these languages. If you want to lend a hand, here’s how. We’ve also been working with the developers and sysadmins on ways to make it easier to add even more locales to all related Tor projects, so if you can help with another language, we welcome your help.
We’ve also been working on a glossary of Tor related terms we want to translate into as many languages as possible and offer it as a resource for other internet security projects to use.
If you’re not able to offer a hand with translations, you can support our work financially by making a donation. Language barriers are holding back the internet freedom movement, but there is strength in numbers: your support can play a critical role in making sure that Tor software can be localized for everyone who needs it. Plus, the more people that use Tor in different contexts and communities, the stronger it becomes for everyone.
Your donation will support a global community of people giving their time and resources to strengthen the internet freedom movement, and with Mozilla matching every donation through 2018, your impact will be doubled. Join us.
Following up on the suggestion of localizations for Navajo and Yanomaman languages/cultures, the linguistic part might be easiest, because plenty of people are fluent in one of these languages and English or Spanish/Portuguese--- I guess that Anthropology Departments in US/BR universities could put you in touch with some of them. The hard part--- this might be a question for the Googlers--- would be figuring out how to bring networking to remote areas without expensive and environmentally damaging conventional infrastructure projects. We certainly don't want to bring the horrendously exploitative Comcast model to the Amazon or to the American Southwest! Tor for sat phones maybe?
Oops, forgot to say that Bolsonaro has apparently vowed to eradicate the Yanomaman language, so this speaks directly to your point about preserving threatened languages (and cultures), not to mention discouraging outright genocide.