Best practices for Content Translation events
Content Translation is a feature of Wikipedia, which helps editors translate articles between languages.
Content Translation can be a quick and effective introduction to editing Wikipedia for people who know more than one language. With Content Translation, a completely new editor can create a full-fledged Wikipedia article with formatting, images, and references with practically no preparation, in less than an hour. It is also, by its nature, a good contribution to enhancing the knowledge across languages and cultures. Hence, it is quite a good fit for editing workshops.
However, the people who run the workshop should make some preparations so that the event will run more smoothly and efficiently.
Unless noted otherwise, all the best practices for running Wikimedia events in general apply to translation events, so it's strongly recommended to read them and use them. Go to Learning patterns, and select "Events".
People to invite
Anybody who knows at least two languages can participate in such an event. You may choose to focus on translating into one language, but you don't have to: If you are doing a translation workshop as part of an international event such as Wikimania, or if many different languages are spoken in the area where the workshop is help, the participants may translate into different languages.
That said, it is always very useful to have at this event at least one person who is highly proficient in the language into which people are translating, and in the language from which people are translating. It can be a linguist, a language teacher, or a professional translator. It can even be a person who simply loves the language and is good at reading and writing in it and in using dictionaries, grammar books, and style guides. It's OK if this person is also the organizer of the event. If there are several such people, it's even better.
It's OK to invite people who are completely inexperienced with editing Wikipedia, but there should be at least one person who is experienced in writing in Wikipedia. If possible, it should be a person who is experienced in writing in Wikipedia in the language into which most participants will be translating. If it's hard to find such a person, it can be someone who is experienced in writing in Wikipedia in another language. You should have at least one experienced Wikipedian per ten inexperienced people. The more experienced people, the better.
It is less essential, but quite useful to have at least one person who has administrator rights, so that it will be possible to resolve issues with accounts, protected pages, etc. If an administrator cannot be present at the event in person, it is advisable to be in contact with one remotely by phone, instant messaging, or email. Finally, it is also useful to have somebody who is able to analyze, report, and resolve general technical problems with wiki syntax, keyboards, fonts, gadgets, software bugs, etc.
If you want to focus your event on translating articles about a particular topic, such as "The cities of our country", "Famous people from the history of Thailand", "Diseases and vaccines", and so on, you should have at least one person who is knowledgeable about this topic.
Before the event
Make sure you know how to type in your language. Some languages can be easily typed on any computer, but some others have difficulties, especially in India, South East Asia, and some countries in Africa. If people will bring their own laptops, try to learn as much as possible about configuring keyboards for the relevant language on common operating systems, especially Windows, and also Mac, Chromebook, and Linux.
Make sure that you are experienced with Content Translation yourself. Translate at least one article using it, preferably more than one. Test it again a day before the event: it sometimes happens that recent software changes in Content Translation or in the gadgets on the wiki itself change or break some functionality.
Read and re-read the Content Translation user manual, even if you are an experienced user of Content Translation, and even if you had read it already. In addition to the technical description, it includes useful advice that you should pass on to the workshop participants. If the user manual is not translated into the language that most of the participants know, consider translating it by clicking "Translate this page" at the top of the page.
Check whether the Content Translation software itself is translated into the language that most of the participants know. To do this, log into your account on translatewiki.net and check the status of the Content Translation project. If the link says "Nothing to translate", then everything is ready! If you see rows of English strings, then not everything is translated. Even though it is not a requirement, it is highly recommended to translate the user interface of Content Translation before conducting an article translation event. This will make the interface easier and more familiar for the participants, and it will help everybody in the event use consistent terminology for words like "translate", "publish", "link", "template", "reference", etc. For general tips on using translatewiki.net, see the post Translating the software that powers Wikipedia on the Wikimedia blog.
Prepare a list of articles that should be translated. It is usually OK to encourage the participants to decide what they want to write about (see below), but sometimes people don't know what to choose, so it's good to have a list of articles to translate as a fallback.
While translating, people often have questions about translating difficult words, about spelling and grammar, and so on. Bring dictionaries and books about grammar and style to the event, or prepare a list of websites where materials of this kind can be found.
Preparing the computers
Make sure that all the computers that will be used have a keyboard configured for the language that will be used at the event. Sometimes computers are configured only with an English keyboard.
If these computers are in place like a school, a library, or a community center, ask the IT person to do this. If people are bringing their own laptops, tell them to do it.
Ask the participants
Ask all the participants to create Wikipedia accounts. Creating them all on the day of the event will cause unnecessary delays in the beginning of the workshop. Also, creating many accounts from the same network may be blocked.
Ask all the participants to test that their accounts work in the Wikipedia in the source language and in the target language. Occasionally an account can be created in one language, but auto-creation in the other language may be blocked. If anybody has issues with this, contact an administrator.
Ask all the participants to decide which articles do they want to translate, and encourage them to read the whole source article. It is also recommended to pick more than one, because it may happen that an article already exists in the target language, or locked by another translator.
If participants bring their own laptops, tell them to do the things described in the section "Preparing the computers" above: upgrade the web browser and configure the keyboard for the language they'll use. Many people don't know how to do it themselves, so try to learn how to do it on as many operating systems as possible.
During the event
Introducing new editors to Wikipedia
The advantage of Content Translation is that it allows people to skip long introductions about wiki syntax, uploading files, or copyrights.
Nevertheless, it is highly recommended to give the participants a short introduction:
- A brief history of Wikipedia
- What is a wiki
- What is an encyclopedia (as opposed to a blog, a news website, a social network, etc.)
- What are the copyright principles: Free culture is great; translation between languages is allowed; copying text from other websites without an explicit permission is forbidden; uploading photos is allowed only if they are your own or if they are under a compatible license (when using Content Translation, only images that are already on Commons will be auto-adapted, so image copyright shouldn't be an issue)
If the focus of your event is just translation, this introduction shouldn't take more than fifteen minutes.
If all the participants are experienced Wikipedians, you can skip this introduction.
Introducing Content Translation
After the general introduction, do a short demo of Content Translation. Important points to mention:
- Translate paragraph by paragraph.
- Machine translation is available for some languages, but not for all of them. If machine translation is available for the language in question:
- Don't publish machine translation without fixing its mistakes!
- Show how to turn machine translation on and off.
- It's possible to paste the source text into the paragraph, or to start from an empty paragraph.
- Images can be automatically transferred by clicking on them, but you have to translate the caption.
- Links are adapted automatically, and can also be added manually.
- References (footnotes) are adapted automatically.
- Content Translation creates the first revision of the article. After this it can be edited like any other article.
- For experienced Wikipedians: Don't use wiki syntax.
Make sure that you understand all these points yourself, and that you are able to use them and demonstrate them.
You should also explain why translating Wikipedia articles is useful even if many people know major languages like English, French, or Russian. You should adapt this explanation to your country and to the event participants. Some possible points to mention:
- Many people don't know these major languages, and translation will make useful knowledge more accessible.
- For school children it is easier to read Wikipedia in a language that is familiar to them from school or home.
- Even editions of Wikipedia in very large languages don't cover all the topics in the world. It is possible to translate from the local language of your culture into a major language, so that people from other cultures will be able to learn about your culture.
- Increasing the amount of online content in a language will contribute to the language's standardization, and to its development.
Make sure that everybody enables Content Translation in the preferences, show people how to enter the Content Translation dashboard (hover on "Contributions"), and then just tell people to start translating!
Tell people not to translate the same article as you are showing in the demo. If several people want to translate the same article, only one user should open it, and the other people should gather around the same computer. It is technically impossible for several users to translate the same article with Content Translation.
During the translation phase, people will likely need help with certain issues:
- Translating difficult words: Encourage people to talk to each other and give each other friendly tips about the language. Language experts, as well as dictionaries and grammar books will be especially useful at this point.
- Using Content Translation: images, templates, references, etc.
- Publishing: Some wikis are configured to disallow publishing to the main space for new users. If this happens, tell people to publish to the user space by clicking the gear icon.
- Fixing reference formatting: Sometimes reference formatting becomes jumbled or references go missing following publication. This is a known issue with efforts ongoing to fix it as of August 2018. After finishing the translation manually fixes, these issues is required.
If you can, have a board with a list of articles that people have started translating, and mark those that people have completed. It's a fun activity, it encourages participants to complete the translation and publish the page, and after the event it can be posted on blogs and social media.
It's very important to collect as much feedback as possible from the participants:
- What worked well? What did you enjoy?
- Was anything difficult in things like creating an account, logging in, choosing an article to translate, starting the translation, reading the source text, writing the translation, publishing, etc.?
- Are there any particular bugs in the software? When there is doubt whether something is a bug or not a bug, always note it—it's important to report anything that could be a bug to the developers. When noting a possible bug, write down as many details as possible: the username, the language, which article was translated, which operating system and browser were the people using, what did they expect to happen, and what happened instead.
After the event
- Ask the participants for more feedback: What did they enjoy and what worked well? What didn't work well? Do they feel that they achieved something? Did their opinion about Wikipedia change?
- Ask the participants to tell their friends about this.
- Ask the participants to translate more at home.
- Submit all the relevant feedback that you collected to the developers of Content Translation in an email, as bug reports in Phabricator, or using any other means of communication that is convenient for you.
- Content Translation development project page on mediawiki.org
- Getting newcomers into Wikipedia with Content Translation, a post on the Wikimedia blog about one of the first Content Translation workshops
- As of 2018, this feature is only available on Wikipedia. In the future it may also be made available on Wikivoyage and on other Wikimedia projects, but there is not timeline for it yet.
- This may become possible in the future, but there is no target date for this yet.