Rev 2.28
Stage 1: Drafting
- (no description)
-
□ C Study the passage (exegesis), [14, 12, 10, 8]
The first translation task is to study the text carefully, using Bible versions and commentaries. This is called “doing the exegesis”. There should be at least one person on each translation team who is a skilled exegete. -
↑ C Draft text, [14, 12, 10, 8]
The first draft of the text, whether written out by hand or directly typed into the computer, is entered into Paratext. -
↑ C Draft section headings, [14, 12, 10, 8]
(no description) -
↑ C Draft footnotes, [14, 12, 10, 8]
It is best to draft these when you decide that a footnote is needed. You can add another footnote anytime you feel it needs to be added. -
↑ C Read the draft aloud, [14, 12, 10, 8]
A mother-tongue speaker of the receptor language reads the draft aloud to the team, and possibly other mother tongue speakers of the language to check for naturalness and clarity. Then adjust the text based on comments from the group. -
↑ C Enter revisions from the readthrough, [14, 12, 10, 8]
Revisions to the text based off of reading the text out loud should be entered into Paratext during the reading or as soon as possible after the readthrough is completed. -
□ B Do back translation or interlinear, [42, 36, 30, 24]
A back-translation is a translation into the major national or trade language of the area. It should be done by a speaker of the language other than the translator. It helps to show whether the translation is communicating effectively and accurately. Consultants usually require a back translation or an interlinear. If an interlinear is required instead of a back translation, complete the glossing of the interlinearization of the text to help guide the consultant on a word-by-word basis of looking at the text. -
□ B Draft book introductions, [14, 12, 10, 8]
Be careful to use the same key terms in the introduction as in the text. -
□ B Run basic checks, [150, 150, 150, 150]
After drafting a book of the Bible, run basic checks and resolve any issues found with chapter and verse numbers, markers, etc. -
∞ Notes Checks
Notes Assigned to Me
Stage 2: Exegetical Checking
- (no description)
-
Ξ C Exegetical check: text, [42, 36, 30, 24]
This check is done by the translation advisor/exegetical specialist with the rest of the translation team. -
Ξ C Exegetical check: parallel passages, [42, 36, 30, 24]
Open Parallel Passage tool and confirm all parallel passages. Review the wording of the text in these parallel passages and decide if wording in one text would be better if harmonized with the wording in another text. (This check is not simply that parallel passages have check marks, it is meant to read the verses and see if the appropriate words are green or yellow in each passage.) -
Ξ C Exegetical check: introduction, section headings, footnotes, [42, 36, 30, 24]
This check is done by the translation team with the translation advisor/exegetical specialist. -
□ C Check spelling, [42, 36, 30, 24]
You can do a spell check in a variety of ways. If you want to use the Paratext tool, under the Checking Menu is “Spell Check Current Book”, Click on this and accept or correct the spelling of all of the words present. For those that need more discussion open the wordlist tool and add a spelling discussion note. -
□ C Check proper nouns & names, [42, 36, 30, 24]
Verify that proper nouns and names have been transliterated according to agreed upon rules, and are consistent. Verify that capitalization has been done correctly and consistently. For languages with word level and grammatical honorifics, verify that they are used correctly. Note: The Biblical terms tool can help with the verification of names if the list is filtered for the “Names” category. The Biblical terms tool will not find instances of a name in book introductions, section headings, footnotes, illustration captions and glossary entries. You will have to find the proper names in these locations manually. -
□ C Enter Biblical terms renderings, [42, 36, 30, 24]
Identify the Biblical key terms in the passage. (Not every term in the “All Biblical terms list” but the terms deemed significant for consistency sake.) Keyboard the renderings into the Biblical terms Tool. Check the consistency of the Biblical key terms used in the passage with the terms documented in the Biblical terms tool. -
Ξ B Exegetical checking: run basic checks, [150, 150, 150, 150]
After making changes to the text during exegetical checking, run basic checks and resolve any issues found with chapter and verse numbers, markers, etc.
Stage 3: Comprehension Checking
- (no description)
-
Ξ C Prepare text for group checking, [42, 36, 30, 24]
Open the “Assignments and Progress” window and correct all errors/issues shown there. Once all errors are corrected and open notes are resolved, you can print a copy of the books or chapters to be reviewed by community group. The two simplest ways to print text from Paratext are found under the “File” menu. They are “Print Draft” and “Save as RTF”. There are other methods available for more advanced formatting, such as “Export to Pathway”. Use the method specified by your project administrator or translation consultant. -
↑ C Comprehension check with a group, [42, 36, 30, 24]
Translators read aloud to a group of people who are fresh to the text, Ask comprehension questions. Check for clarity and naturalness. Make note of any places where revisions need to be made which will later be entered into Paratext. -
↑ C Enter revisions from comprehension checks, [42, 36, 30, 24]
Type revisions.While supplementary helps are specifically mentioned in the drafting section, it is assumed that all other checks will also be completed on supplementary materials and that these are a part of the final text. -
↑ C Update back translation or interlinear, [210, 180, 150, 120]
After making changes to the text during exegetical checking and comprehension checking, update the back translation or interlinear to reflect those changes. This is a critical step to complete before making the text available to the consultant. -
Ξ C Update Biblical terms, [42, 36, 30, 24]
Open Biblical terms tool and filter for chapter(s) being prepared for consultant check. Verify that your list of Biblical terms have approved renderings. Update any that are missing, or need to be changed because of a better understanding of what the Greek or Hebrew means. It is likely some are out-of-date, because of the revisions made after comprehension testing. -
Ξ B Comprehension checking: run basic checks, [150, 150, 150, 150]
After making changes to the text during comprehension checking, run basic checks and resolve any issues found with chapter and verse numbers, markers, etc.
Stage 4: Consultant Checking
- (no description)
-
Ξ C Make text available to consultant, [210, 180, 150, 120]
The team needs to make the translated text available to the consultant who will evaluate the text for accuracy, clarity, naturalness, and acceptability of the translation including all supplementary materials and illustrations used. This can be done by adding the consultant as a user to the project if they are not already listed as a user. Be sure to let the consultant know that the text (and interlinear or back translation) is ready for checking. -
↑ C Review/respond to Consultant Notes, [210, 180, 150, 120]
Once the consultant has evaluated the text and placed notes with observations in the text (or back translation) the translation team may use these notes to review the text themselves and respond to the notes. Translation teams should not resolve the notes of a consultant. The consultant should resolve the notes once the consultant is satisfied that the team has answered whatever question was raised. If there is not time to review and respond to the Consultant Notes before the consultant checking session begins, then these notes should be dealt with in the checking session. -
↑ C Checking session: text, [210, 180, 150, 120]
Consultant interacts with the translation team concerning his observations about the text and supplementary materials, and gives assistance and advice as requested. The project administrator should give one team member (that could be himself) editing permission in the Assignments and Progress window for the “Consultant Checking session” task. It is best to enter revisions to the text into Paratext during the checking session. If the translation team needs to hold more discussion about a possible revision to the text after the checking session is completed, the consultant should put a Note at that verse. The team will respond to that Note later and if the consultant is satisfied with the answer he will resolve the Note. -
↑ C Checking session: section headings, footnotes, [210, 180, 150, 120]
Consultant interacts with the translation team concerning his observations about the text and supplementary materials, and gives assistance and advice as requested. The project administrator should give one team member (that could be himself) editing permission in the Assignments and Progress window for the “Consultant Checking session” task. It is best to enter revisions to the text into Paratext during the checking session. If the translation team needs to hold more discussion about a possible revision to the text after the checking session is completed, the consultant should put a Note at that verse. The team will respond to that Note later and if the consultant is satisfied with the answer he will resolve the Note. -
↑ B Checking session: introduction, [210, 180, 150, 120]
Consultant interacts with the translation team concerning his observations about the text and supplementary materials, and gives assistance and advice as requested. The project administrator should give one team member (that could be himself) editing permission in the Assignments and Progress window for the “Consultant Checking session” task. It is best to enter revisions to the text into Paratext during the checking session. If the translation team needs to hold more discussion about a possible revision to the text after the checking session is completed, the consultant should put a Note at that verse. The team will respond to that Note later and if the consultant is satisfied with the answer he will resolve the Note. -
↑ C Respond to consultant’s input, [210, 180, 150, 120]
The translation team will respond to all Consultant Notes that remain in the text after the Consultant Checking session has been completed or any other input provided by the Consultant. If the consultant is satisfied with the answer he will resolve the Notes in Paratext. -
↑ B Final consultant approval, [210, 180, 150, 120]
Consultant gives approval of the text at the end of checking session if all questions are answered to his satisfaction, or once any follow-up tasks which the consultant has clearly defined have been taken care of. -
↑ B Consultant report distributed, [210, 180, 150, 120]
Consultant report shared with the translation team and the team’s leadership (e.g. DLA or programs director). -
↑ B Review significant changes with community, [210, 180, 150, 120]
Community reviews, to make sure that all significant changes done in consultant check are natural and clear. -
Ξ B Consultant checking: run basic checks, [150, 150, 150, 150]
After making changes to the text during consultant checking, run basic checks and resolve any issues found with chapter and verse numbers, markers, etc.
Stage 5: Pre-publication
- (no description)
-
Ξ B Draft the Title Page and Verso Page, [150, 150, 150, 150]
These pages are mandatory and need to be approved by Branch or Field Directors as they contain copyright statements. -
Ξ B Draft other front & back matter, [150, 150, 150, 150]
This can include the preface, the glossary, an introduction to the Bible/NT, and spine text. -
Ξ B Consistency check: Biblical terms, [150, 150, 150, 150]
Open Biblical terms tool and review all renderings for consistency, and make any last changes needed. -
Ξ B Consistency check: wordlist, [150, 150, 150, 150]
The team goes through the entire wordlist together, to make sure there are no words spelled multiple ways, and to make sure they are all in final agreement on all spelling decisions. Make sure to look at “Find Similar Words” and “Find Incorrectly Joined or Split Words” under the “Checking” tab. -
Ξ B Final check: proper names, [150, 150, 150, 150]
In the Biblical terms tool, create a new filter for the “Names” category. Check for proper capitalization, and confirm that any transliteration of a name conforms to the natural rules and conventions of the local/receptor language. -
Ξ B Final check: numbers & money, [150, 150, 150, 150]
Select the list “Numbers” as the Biblical terms list in the Biblical terms tool to find all the numbers. Make sure there is consistency in the formatting of all the numbers. Verify that words such as money, coin, silver, gold, denarii, and shekel are adequately differentiated and rendered consistently. -
Ξ B Final check: weights & measures, [150, 150, 150, 150]
Verify that words such as talent, mina, shekel, pim, beka, gerah etc., are adequately differentiated and rendered consistently. Verify that words such as cubit, span, handbreadth, orgyia, stadion, milion, cor, lethech, ephah, seah, omer, cab, bath, hin, log, etc., are adequately differentiated and rendered consistently. -
Ξ B Format check: section breaks and section headings, [150, 150, 150, 150]
If another translation is used as a base then this check can be done using Tools > Checklists > Compare Section Headings -
Ξ B Format check: paragraph breaks, [150, 150, 150, 150]
If another translation is used as a base then this check can be done using Tools > Checklists > Compare Markers and look for the new paragraph markers such as \p, and \m. -
Ξ B Format check: special formatting, [150, 150, 150, 150]
See list of special formatting issues such as genealogies, words on the cross, letters, etc. Verify that text is marked using the correct standard format markers (USFM). See https://paratext.org/about/usfm for latest guide to using USFMs. -
Ξ B Format check: layout and indents, [150, 150, 150, 150]
Verify other layout issues such as poetry. Particular attention should be given to poetry indentations. If another translation is used as a base then this check can be done using Tools > Checklists > Compare Markers and look for the new paragraph markers such as \q, \q1 and \q2. -
□ B Finalize illustrations; write captions, [150, 150, 150, 150]
Make final decisions on illustrations. -
□ B Choose maps; label place names, [150, 150, 150, 150]
Make final decisions on maps. -
□ B Develop glossary, [150, 150, 150, 150]
Determine if the glossary for your project will be solely in the local language or a diglot or a triglot. Some teams choose to include a trade language (language of wider communication – LWC) in addition to an official world language. Arrange the glossary entries in alphabetical order in the local language. -
□ P Develop cover design, [1000, 1000, 1000, 1000]
Communicate with the person designated as the typesetter for your project and ask that person to help you choose colors for your cover, how many colors, what kind of material to make the cover out of, and many more aspects that you might not be aware of. -
Ξ B Add cross references, [150, 150, 150, 150]
If cross references have not been added to the receptor language project yet, now is the time to add them. If there are verse spans in the text, there is a possibility that the Scripture references will be shown double in the cross reference section as the bottom of hte page. For example, Matt 6:14-15 may show up twice down in the cross reference section. If this is the cae, then all the verses which are referred to from Matt 6:14-15 will need to be listed under only one reference, i.e. joined, and the second cross reference should be deleted. To find all occurances of span verses, use the following RegEx in the “Find” box: regex:\\v \d+- -
↑ B Format check: footnotes & cross references, [150, 150, 150, 150]
Read all footnotes and cross references looking for inconsistencies in how they are formatted. The goal is to have a consistent look and feel across all footnotes, and not merely the absence of marker errors in the footnotes. It may be helpful to go to Tools–>Checklist–>Footnotes. This checklist will compare the footnotes in your text to other resources that you specify. -
↑ B Final read through/approval with church/community, [150, 150, 150, 150]
After all final checks have been done, the translation team should print off the NT book(s) and do a complete oral read-through together with church and community leaders who will offer any final suggestions for revisions to the text. -
↑ B Revise text based on final read through/audio, [150, 150, 150, 150]
Make any final changes to the text based on feedback given during the oral read through and/or the listening to the audio recording of the Scriptures. -
Ξ B Pre-publication: run basic checks, [150, 150, 150, 150]
After making changes to the text during pre-publication stage, run basic checks and resolve any issues found with chapter and verse numbers, markers, etc. -
↑ B Received final publication approval, [1000, 1000, 1000, 1000]
After every check has been run, after every revision has been made, and when the team says they are ready to go to the final typesetting, then the team must ask for the final approval from whoever is the person in authority over your language project. -
↑ B Do final typesetting, [150, 150, 150, 150]
This task is not done by the translation team. It is done by a typesetter. But you need to be ready to interact with the typesetter at anytime as they run other various Paratext Checks. As the typesetter finds questions to ask the team, they may put them as Notes in the text or can send questions to the team by email.
Symbols used on this page
▒ – When project starts
Ξ – When previous stage is complete
□ – When Book Starts
↑ – After Previous Task
∞ – Automatic Check
C – Once per chapter
P – Once per project
B – Once per book
[numbers in square brackets] – represent the effort levels for each task measured in verses per day. The four numbers are for Easiest, Easy, Moderate, and Difficult books (as defined in Paratext)