Guidelines for Foreign Teams

1. A good understanding of how "English ideas" are translated into "German ideas." In order to do this, you need to have a strong cross-cultural experience between English and German (i.e. lived in a German-speaking country for the first part of your life, and lived in a cross-cultural environment in the US for many years.)

2. The translator's choice of the "Sie" (formal) rather than the "Du" (informal) form to do the translation. This is the most appropiate way to do it.

3. An excellent word choice. In German, you can choose many words to say the same thing. When you are confronted with a situation in which you must repeat an idea over and over again, the amount of different words the translator chooses, tells us the educational level he/she has.

4. Avoidance of "tricky" words, both in German and English. There are some English words that sound like German ones. Many untrained translators mistakenly use those words at the time of making a translation. They also fall into the trap of translating "literally" some American expressions.

5. The general "feeling" of the translation. It flows easily, with words that are "common ground" for all Germans, and it sounds like it's coming from somebody with the backgound and experience of David Wilkerson.

(tips from a professional translator)

---

Previous | Next | Top

D. Please Translate the Copyright Statement

Please assign the following Copyright Statement for translation and have your top translator do the final polishing:

COPYRIGHT/REPRODUCTION LIMITATIONS:
This data file is the sole property of World Challenge. It may not be altered or edited in any way. It may be reproduced only in its entirety for circulation as "freeware," without charge. All reproductions of this data file must contain the copyright notice [i.e., "Copyright (c) 2013 by World Challenge"]. This data file may not be used without the permission of World Challenge for resale or the enhancement of any other product sold. This includes all of its content with the exception of a few brief quotations. Please give the following source credit: Copyright (c) 2013 by World Challenge, Lindale, Texas, USA.

This material is solely for personal use and is not to be posted publicly on other web pages. The Lorain County Free-Net Chapel holds exclusive rights from World Challenge, Inc. to publicly post these messsages on its web page. You are free to download, copy, print and distribute this material, so long as you do not post it on a different Internet site. You may, however, link this site to reference these messages.

---

Previous | Next | Top

E. Giving assignments

Find out if ministry team members may have already-translated sermons or know of others who do. If you find a source for already-translated sermons, have your team pray for the volunteer who will be making the contact for the release of these sermons to David Wilkerson's multilingual web site. Ask that God will give you favor and wisdom in communication.

Work on these already-translated sermons first. Each ministry team member will need you to give him an assignment if he hasn't already selected a sermon for translation. Your job is to see that there is no duplication of effort. There's no sense in two people translating the same sermon and no sense in someone translating an already-translated sermon that is being prepared for viewing on the web.

Please send the a list of all sermons (titles/dates in your language) which are being worked on so they can be listed under "Coming Soon" on your language sermon index page. Be certain you have the correct dates for the sermons. If you're not sure, please check the sermon index:

Chronological Index

To sort sermon titles alphabetically, click the word "Date" at the top of the date column on the above link.

Once assignments are given, track their progress (date started, date completed, date transferred to another person, etc.). See that all assignments are being actively worked on, offering encouragement, support, listening to concerns, dealing with problems, answering questions and concerns.

Important! Never send the next assignment until the current assignment is finished and ready to be sent to your top translator for final polishing.

---

Previous | Next | Top

F. Sermon Polishing

Once an assignment has been completed, it needs to be reviewed by your team's top translator for final polishing and then released for public viewing. (See point "C" above.)

---

Previous | Next | Top

G. Reporting Concerns

Please be sure to all concerns, problems, or questions, that you cannot resolve among yourselves or that you believe I need to know about. Please alert me to growth concerns. We will need to divide and delegate as we grow.

---

Previous | Next | Top

H. Stay in Touch!

Send out period reports of encouraging news, guestbook and e-mail feedback from sermons, progress, concerns, prayer needs, etc. to your ministry team members.

How are you doing on your e-mail communications between yourself and the other members of your team? If e-mail communication is not one of your strengths or if you find yourself just too pressed for time to communicate as often as you feel you should, here's a suggestion for you.

Why not appoint one of your team members as e-mail secretary for your team? Perhaps you have a team member who really enjoys sending e-mail or who's better expressing himself/herself with words than you are. Don't hesitate to monopolize on that person's strength.

E-mail communication is a vital part of team ministry. I see it as the "glue" that holds the team together. Good communication can help dispel misunderstandings and frustrations. It can bring unity, motivation, excitement, and even new life to an entire team.

Use whatever means you need to accomplish this:

1. Foremost, communicate with God about your team members.
2. Appoint an e-mail secretary for the team.
3. Free chat
4. Free Internet phone software - MediaRing: http://www.mediaring.com
5. E-mail
6. A normal telephone
7. Letters
8. Faxes
9. E-cards

It would be good to use a combination of all of the above, if you're able to do that.

BIRTHDAYS
You might want to find out your team members' birthdays and send them an e-card on their special day.

PICTURES
I recommend that you collect pictures of your team members. Ask them to scan a picture of themselves and e-mail them to you. That way you can get to know your team in a more personal way.

Be sure to let the director of David Wilkerson's multilingual teams know what's happening with your team by a copy of your reports.

---

Previous | Next | Top

I. Your Own Mailing List

You can manage your own TSPS Mailing List in your language. Create a new Mailing List - it's a fast and simple operation if you follow these instructions:

1. Go to the eGROUPS home page: http://www.egroups.com
2. In the left panel, click on the "Start a List" link.
3. If you are already registered with eGROUPS, insert your e-mail and password or else follow the instructions to register yourself.
4. Insert data about your Mailing List (follow notes about specific fields):
• Name for the mailing list: Use "tsps-<yourlanguage>" - i.e. the Italian name is  "tsps-italian"
• Informational link: Enter the TSPS home page of your own language.
• Do you want this list to be moderated? No
• Do you want this list to be a restricted list? No
• Do you want this list to be an announcement list? Yes
• Type of Archives: Public
• Do you want e-mail notification? Yes (So you know when people register for your list.)
• Replies to list messages are sent to The Sender (That's you, not your subscribers.)
• Do you want your list to be unlisted? No
5. Once you've inserted these data, you can click on Create and follow the remaining online instructions.
6. Once your list is created, you can change the parameters, invite people to subscribe, edit a welcome message, manually add people to the list, display and unsubscribe users, etc.
7. Modify your "subscrib.htm" page by inserting the instruction for subscribing to your Mailing List. I suggest you keep both the English link and your language link to the mailing list.
8. Modify your sermon index home page by inserting a link to your subscrib.htm page. See an example on the Italian home page: http://www.tscpulpitseries.org/italian.html
9. To create a message to be sent to the Mailing List, follow the English "tsps" list layout, translating the information into your language.
10. To post the sermon to the mailing list, send it to "tsps-<yourlanguage>@egroups.com"
11. Now advertise your list by sending an e-mail to new-list@cs.wisc.edu. Follow New List's submission instructions, which can be found at http://scout.cs.wisc.edu/scout/new-list/format.html. You may use the advertisement sample taken from the German team by simply searching and replacing "German" with your language name:

    To: new-list@cs.wisc.edu
    Cc: pulpitseriesteam @ misslink.org
    Subject: NEW: TSPS-DEUTSCH - German translations of David Wilkerson's sermons

    TSPS-DEUTSCH on www.egroups.com

    TSPS-DEUTSCH is a one-way mailing list where German translations of the "World Challenge Pulpit Series" sermons of David Wilkerson are published. David Wilkerson is internationally known as the author of the book "The Cross & the Switchblade", which was published in German unter the title "Das Kreuz und die Messerhelden". These sermons are an excellent resource for your personal spiritual growth, great sermon material, and a wonderful springboard for all kinds of Bible studies.

    FREE online subscriptions are available from
    http://www.egroups.com/subscribe.cgi/tsps-deutsch

    Back issues are available from
    http://www.tscpulpitseries.org/german.html

    List-Servant: Norbert Bollow <nb @ thinkcoach.com>

If you have any problem creating or managing the mailing list, send an e-mail to . He will be happy to help you!

---

Previous | Next | Top

J. Overview of How the Translation Teams Work

Here is an overview of how the translation teams work. Team members are free to choose sermons which they feel are best suited to their culture but must notify team leaders of their sermon title/date choice. Otherwise, the team leader assigns a sermon title for translation. Some team leaders prefer to divide one sermon among all team members to produce a faster translation. The team leader monitors all assignments and the progress of team members, making sure there is no duplication of effort.

Translation Software
Some team members use computer software for partial translation. They find the translation software gives them more variety of word choices. If you don't have translation software, you may ask your team leader to have another team member run your sermon through their translation software and forward the results to you. This way each team member does not have to purchase expensive translation software. This is one of the benefits of team ministry. Other team members prefer to do the whole translation without the aid of translation software, because they find it too confusing. When in doubt about a particular phrase or colloquialism, send it up to the team for their input.

Saving the Sermon File
After the translator is finished with the sermon, it is saved as a word processing document and e-mailed to their team leader. Saving the sermon as a document (.doc) or Rich Text Format (.rtf) word processing file type preserves accent marks. Write your team leader for specific instructions regarding this.

Final Polishing
The team leader then sends the sermon to the finish editor on his team, who does final polishing at this time.

HTML Conversion
Next, the team leader sends the polished sermon either back to the original translator or to another team member, who converts the file to HTML (HyperText Markup Language) for viewing on the web and inserts the new HTML text into the template (sermon example) for their language. If no team member knows how to convert to HTML format, the polished sermon is sent to the for conversion.

Final Double Check
Then the person who adds the HTML carefully checks his work against the layout in that language template (sermon example), to be sure all links carefully match the example laid out in the template for that language. When he is sure his work has been properly checked for errors, the web designer returns the polished HTML sermon to the team leader. The team leader then gives the sermon a final check for errors.

Plain Text Files
Then the team leader opens the HTML polished sermon in his Netscape browser and saves it as a plain text file, using the File/Save As command.

Uploading to the Server
Next, the team leader uploads the completed HTML file and its accompanying plain text file to its specific language directory on the ministry teams' server. can give instructions for doing this.

Notifying the Webmaster
At that point, the team leader notifies the Pulpit Series which sermon title/date is waiting in which language directory on the ministry teams' server, for retrieval and uploading to the Pulpit Series website.

Checking Your Website
Last of all, the team leader asks a team member to check the sermon on the website to be sure it is properly indexed and all links are functioning as they should. The team leader then notifies the if there are any problems.

Miscellaneous Instructions
These are very general guidelines. Each team may have to make changes according to their resources or preferences.

• When a sermon is sent by e-mail, don't assume that it was received. Establish some kind of follow-up to prevent lost working time or misunderstandings.
• Do not translate Bible verses. Use the version agreed upon by the team for your language. David Wilkerson prefers the version which is closest to the King James Version.
• Try to keep as close as possible to David Wilkerson's words. Do not allow private interpretation to influence translations.
• Check team policy for adding your name to the bottom of the document to give credit for translating or editing the sermon. Suggestion: "To God be the glory, translated by <name>. Edited by <name>."
• All filenames will begin with "ts" with the year, month, and day following (except for the undated ones). Example: ts980330. Undated sermons will begin with "ts" and finish with the first six characters of the sermon title.
• Check with the team leader to see what kind of document a file should be saved as. For example: rtf, doc, txt, or something else.
• Please save a copy of any files that you send. Files can get lost and hard drives can crash!
• Notify your team leader of any problems that you may have. Don't contact Barbara Haas unless you are not getting the help you need from the team leader. She has a tremendous amount of e-mail, so please go through your team leader first.
• Send any prayer requests to . (See here) When you send a prayer request include your full name, team position, and e-mail address at end of message. Be careful what you write, everything will be posted.

---

Previous | Top

Your Input Is Needed!

We value your comments and suggestions. Help us polish these guidelines and make them more user friendly. Be sure to refer to the section letter and paragraph number when making comments. your comments. Remember, we all have a lot to learn from each other. That's what team ministry is all about!

---

This web site is a service of
The Missing Link, Inc.^®
Linking Troubled Youth and Adults with Life-Changing Programs
Web site - misslink.org
Chapel Site - misslink.org/chapel2.html
Home of David Wilkerson's World Challenge Pulpit Series Multilingual Web Site
www.tscpulpitseries.org