Lecture 2-4: Many Languages, Many Readers
Contents 31
- Lecture 1-1: Speaking as Witness, Not Marketing
- Lecture 1-2: Our Message and Our Voice
- Lecture 1-3: Choosing Channels: Face to Face, Print, Messages, Web
- Lecture 1-4: Who Is Listening: Members, Neighbours, Newcomers
- Lecture 1-5: Practice Lab: A Communication Walk-Through
- Lecture 2-1: The Website as a First Welcome
- Lecture 2-2: Social Media and the Community's Voice
- Lecture 2-3: Accessibility and Plain Language
- Lecture 2-4: Many Languages, Many Readers
- Lecture 2-5: Practice Lab: Rewriting a Notice
- Lecture 3-1: Online Worship and Streaming: What It Is and Is Not
- Lecture 3-2: Making Things Simply and Well
- Lecture 3-3: People on Camera
- Lecture 3-4: Archives, Storage and the Long Life of Content
- Lecture 3-5: Practice Lab: A Filming Notice and Consent Page
- Lecture 4-1: Respecting Those Who Made It: Copyright Principles
- Lecture 4-2: Music, Images and Licences in Practice
- Lecture 4-3: Quoting, Sources and Honesty
- Lecture 4-4: Tools and AI: General Principles
- Lecture 4-5: Practice Lab: A Source and Permission Check
- Lecture 5-1: Numbers, Staging and Success Stories
- Lecture 5-2: Testimony, Stories and Emotional Appeal
- Lecture 5-3: Fundraising and Mission Reports
- Lecture 5-4: Paid Promotion and the Pull of Algorithms
- Lecture 5-5: Practice Lab: Rewriting a Report and an Appeal
Most communities now have neighbours who read and hear in another language. This lecture asks how a church or agency can welcome them in words, and be honest about how well it does so. It treats translation as a responsibility and not a favour, and machine translation as an aid and not an authority.
It reads Acts 2:6-8 modestly, as a picture of people being addressed in the language of their own home, and does not build a theory of languages on it.
This lecture is not legal advice. Rules differ by country, region and year. Check locally, and consult a qualified person for your own situation.
What these 18 minutes give you
- Find out, by asking, which languages the neighbours of a community would like to be welcomed in.
- Describe a small, correct way to begin, and the habits that make a translation reliable.
- Explain why a machine may help a person understand but a person should check what a church says.
- Say why a language is not a label, and why no member should be asked to speak for a whole group.
When this sound was heard, the multitude came together, and were bewildered, because everyone heard them speaking in his own language." — Acts 2:6
World English Bible
They were all amazed and marveled, saying to one another, “Behold, aren’t all these who speak Galileans?" — Acts 2:7
WEB
How do we hear, everyone in our own native language?" — Acts 2:8
WEB
If then I don’t know the meaning of the sound, I would be to him who speaks a foreigner, and he who speaks would be a foreigner to me." — 1 Corinthians 14:11
WEB
After these things I looked, and behold, a great multitude, which no man could number, out of every nation and of all tribes, peoples, and languages, standing before the throne and before the Lamb, dressed in white robes, with palm branches in their hands." — Revelation 7:9
WEB
Acts 2:6-8 is read here modestly: people heard in their own language and were treated as hearers worth speaking to. Traditions differ on the larger meaning of that day. First Corinthians 14:11 is about the stranger's experience of an unknown sound, and Revelation 7:9 pictures a multitude from every language. None is offered as a rule for translation.
1. The neighbour who reads another language
Almost every community now has neighbours who read and speak other languages. Some are migrants and refugees who have recently arrived. Some are families who have lived in the district for decades and speak a home language in the house. Some are students, workers on a contract or visitors for a season. Some are members of the church itself who do their daily work in one language and pray in another. In some places the whole district is multilingual and nobody thinks about it. In others a single family in a village is the only one who speaks a language that nobody else in the church knows.
Acts 2:6-8 tells of the day when people from many places heard the apostles' message, each in his own language. The crowd was bewildered, and asked, "How do we hear, everyone in our own native language?" Whatever else one makes of that day, which readers will understand in different ways, it shows God speaking to people in the tongue of their home. This lecture reads the passage in a modest way: a person who hears in his own language has been treated as someone worth speaking to. Revelation 7:9 pictures a great multitude from every nation, tribe, people and language before the throne. The church is not meant to be one-tongued. And 1 Corinthians 14:11 names the plain experience of the stranger: if I do not know the meaning of the sound, I am a foreigner to the speaker, and the speaker is one to me.
This lecture asks how a community can speak to its neighbours in languages it may not know well, and be honest about how well it is doing so. It is not legal advice. Rules about what must be translated or provided, and about the use of an official language, differ by country, region and year. Check locally.
2. Whom to write for, and what to start with
Begin with a plain question. Who actually lives and works around us, and in which languages would they like to be welcomed? Do not guess from the map or from a belief about a group of people. Ask. A visit to a shop, a school, a clinic or a neighbour will tell you more than a statistic.
Then begin small. A community that cannot offer a full page in another language can still offer:
- a short welcome, a few lines in the language, with the time and place;
- a printed card with the same facts, to give at the door;
- the name of a person who speaks the language and is glad to be asked;
- a line in your main language saying that you welcome speakers of other languages and how they may ask for help.
It is better to offer a short, correct text than a long uncertain one.
3. Translation is a responsibility
When a church puts out words in a language, it is saying something in that language, with its own name on it. If the words are wrong, the church has said something wrong. If they are rude, it has been rude. If they say something unintended, it has said that too. So translation is a responsibility, not a favour.
Some principles hold in almost any place.
- Ask someone who speaks it as their own language, and who knows the subject. A translator should be someone for whom this is the home language, or very close to it. A person who studied it at school may not hear when a phrase is cold or comic.
- Pay or thank them properly. A translator's time is real work. In a community of volunteers, the translator should be thanked by name if they wish, and should not be asked again and again without rest.
- Have a second reader. Another speaker of the language reads the text as a stranger would. They look for mistakes, for tone and for words that mean something different in a different part of the country or among different generations.
- Keep plain words in the original. A translator can render plain words faithfully. A text full of idioms, church shorthand and wordplay is difficult to translate and easy to distort. The plain-language work of lecture 2-3 helps every translation.
- Say who did it. A line such as "Translated by a member of our community; please tell us if anything is unclear" is honest and invites correction.
- Be most careful with serious texts. A welcome notice may be forgiven a slip. A text on safety, consent, money, a decision of the church or a legal matter is another thing. For anything that carries a duty or a risk, use a qualified translator and ask a qualified person about what is required locally.
4. Machine translation: an aid, not an authority
Tools that translate text automatically can be useful. They can give a rough sense of a message, help a volunteer understand a letter in a language they do not know and help someone begin a reply. They also make errors, sometimes small and sometimes serious, often without any sign that anything has gone wrong. They may miss tone, flatten courtesy into rudeness, mistranslate names and religious words and make a sentence mean the opposite of what was meant.
A fair rule for a church, which names no tool: a machine may help a person understand; a person should check what a church says. Use a machine to prepare a draft or to read what you have been sent, but do not publish its output as the church's words in a language nobody in your team can read. Where a human reader is not available, say plainly that the text was produced with a tool and may contain errors, and give a way to ask a person. In text that carries a duty, a risk or a promise, do not rely on a machine at all.
Never put private information, such as a member's name with their circumstances, a letter containing someone's troubles or any detail about a child, into a tool that sends text elsewhere to be processed. Lecture 4-4 returns to general principles for tools.
5. Speaking so that translation can work
Much of the work happens before the translator is reached. A few habits help.
- Use short sentences with a clear subject.
- Avoid idioms, sayings and jokes that depend on one language's wordplay.
- Give dates and times in a plain way that cannot be misread.
- Keep a short list of terms that you use for the same thing every time: the name of the gathering, the name of the room, the words for baptism and communion. Check with speakers how they say them at home. A word that is "the right church word" in one tradition or one country may be unfamiliar or even loaded in another.
- Do not use a language only for show: a greeting in the wrong dialect, or a flag, is not a welcome.
6. Do not make a language a label
One caution. A person is not "a speaker of X" and nothing else. Many migrants speak several languages. Some second-generation young people read the new country's language better than the old one. Some older people, in any country, read poorly in every language. Ask individuals what they prefer, and do not decide for them. Do not collect or publish lists of members by language or origin, and do not photograph anyone to prove that the church is diverse.
And be careful about asking one person to speak for a whole group. The member who is willing to translate on Sunday does not thereby become the community's representative on every question.
7. Other sizes, other structures
(an invented example) A house church in a town of weavers has a single family from another country. The wife speaks the local language only a little. The host does not know her language. Together with the family they prepare a card with four lines in the family's language (the time, the address, a name to call and "you are welcome"), and the family reads it back to check it. There is no other translation. It is enough to be a real welcome.
(an invented example) A large city church, Saltmarsh Community Church, has a notice board in three languages and a team of volunteer translators. The danger here is carelessness through volume. The team agrees that every text is read by a second speaker, that nobody translates alone for a long period, and that notices on safety and money are done by a qualified translator.
(an invented example) A mission agency with partners abroad writes to supporters in one language and to its partners in another. A letter with a hard decision in it is read by a speaker of the partners' language before it is sent, because a sentence that sounds courteous in one language can sound curt in another.
8. Where to go from here
Words are only one part of what a community puts out. The practice lab for this week asks you to rewrite one real or invented notice so that it is true, plain and open to more people.
Diagram 1. Hearing in one's own language
In short
- Begin with the actual neighbours: ask which languages they would like to be welcomed in.
- Start small and correct: a short welcome, a printed card, a named person to ask.
- Translation is a responsibility: a home-language translator, a second reader, plain source words, and a line saying who did it.
- A machine may help a person understand; a person should check what a church says. Never put private information into a tool.
- A language is not a label: ask individuals, do not publish lists by origin and do not make one member speak for a group.
| Front | Back |
|---|---|
| Where to begin | Ask who lives nearby and in which languages they would like a welcome; offer a short, correct text. |
| Translation habits | Home-language translator, second reader, plain source text, a line saying who did it, a qualified person for serious texts. |
| Machine translation | An aid to understanding, not an authority; a person checks what the church says; no private information. |
| Acts 2:6-8 | Read modestly: people heard in their own language and were treated as worth speaking to. |
One sentence to remember To speak to someone in their own language is to treat them as worth the trouble.
This week's action Write a four-line welcome with the time, place, a contact and "you are welcome", and ask a speaker of another language to read it.
Check yourself
Not "did you read it" but "can you explain it". Ticks are kept on this device only.
Reflection and discussion
- Which languages are spoken within a short walk of your meeting place? How do you know?
- If you had to write a four-line welcome in another language, who would check it? How would you thank them?
- Where could a poor translation in your community's name do harm: a notice on safety, a letter about money, a message of comfort?
- How would your community decide when a machine's draft is good enough to be a first step, and when it is not?
- Who in your community is asked, again and again, to translate? Who asks whether they would like a rest?