Paratext

You are here: Home / Paratext Training / Tutorial Articles / Project Plans Tutorial / SIL Compact Plan

SIL Compact Plan

SIL Compact Plan

Revision 2 (See Rev 2 Changes)

Stage 1: Drafting
  • View this plan by opening the accompanying SIL_Compact_Plan.html document.This stage involves creating the first draft of the translation.
  •  □ C Exegesis, [42, 36, 30, 24]
    Study the text carefully, using Paratext resources, recommended commentaries, and other recommended resources. The Translator’s Workplace collection of resources contains many recommended resources that are not available in Paratext. To learn more about Translator’s Workplace and to see if you qualify for this collection of resources go to: https://www.sil.org/resources/publications/tw/licensing
    Exegesis may involve:
    ● chunking the text into meaningful units
    ● identifying translation issues including key terms
    ● identifying cultural issues
    ● studying the meaning of key terms in the passage and considering what receptor language rendering would be best for each sense of each term
    ● oral retelling and processing of the text Oral retelling can free the translator’s mind from the form of the model language, creating a more natural translation. The basic process is first to study the text until you completely understand and have internalized the passage, then retelling the passage to other speakers of the receptor language. It is best to retell it in the vernacular without looking at the model text(s). Studying key terms can be done in one of the Enhanced resources in Paratext, looking at the UBS handbook, the SIL translation notes, or a good Bible Dictionary such as those available in the Translator’s Workplace collection or other source recommended by your supervisor.
  •  ↑ C Create the first draft, [14, 12, 10, 8]
    Draft the text in Paratext using the natural patterns of the receptor language. Then re-read it to check for clear logical flow and typographical errors. It is recommended to use the Biblical Terms Rendering window or an Enhanced Resource to see what renderings have been used and to add new renderings as needed.
  •  ∞   Basic Checks
    ChapterVerse; Marker
  •  ∞   Spelling Checks
    Words with Incorrect spelling status
  •  ∞   Notes Checks
    Notes Assigned to Me; Project Notes (Conflict)
Stage 2: Team Check & Comprehension Check
  • The team checks the naturalness and exegesis of the draft, and then tests it with the target audience to make sure that it communicates well. If you add any custom project note tags to your project, you will have to specify which stage(s) the automated checks for those tags will need to begin.
  •    C Exegetical check, [42, 36, 30, 24]
    The exegetical checking should include at least the following:
    ● compare the draft with one or two translations in the national language
    ● identify any missing verses or sentences
    ● discuss exegetical choices that have been made in the translation
    ● identify possible exegetical mistakes in the translation
    ● adjust text as necessary to resolve any issues found
  •    C Naturalness check, [42, 36, 30, 24]
    Read the draft aloud with the team. While reading the text, check the general flow of the discourse, its logic, chronology, participant reference, sentence length & rhythm, language style and register, etc. Adjust the text as necessary to resolve any issues found.
  •  ↑ C Draft supplementary materials, [210, 180, 150, 120]
    These materials may include:
    ● section headings
    ● footnotes
    ● cross-references
    ● illustrations (including captions)
    ● maps
    ● glossary entries
    ● book introductions.
  •    C Format check, [1000, 1000, 1000, 1000]
    The format checking should include at least the following:
    ●Check the layout, indents, and special formatting.
    ●Read the text and verify that the paragraph breaks are in the desired places.
    ●If another translation is used as a base then this check can be done using Tools> Checklists> Markers and look for the new paragraph markers such as \p, and \m.
    ●It may be useful to check the section headings using Tools> Checklists> Section Headings.
    ●Consider verifying other types of formatting in your project, such as poetry, genealogies, other lists, words on the cross or any other special formatting in your project. 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 > Markers and by looking for the new paragraph markers such as \q, \q1, and \q2.
    ●Verify that text is marked using the correct standard format markers (USFMs) for any additional special formatting such as genealogies, lists, words on the cross, letters, etc. For more information on how to correctly use the standard format markers (USFMs), see http://ubsicap.github.io/usfm/v2.5/index.html for the latest guide to the USFM 2.5 standard and https://ubsicap.github.io/usfm/ for the USFM 3.0 standard.
  •    C Prepare for comprehension testing, [210, 180, 150, 120]
    Prepare comprehension testing questions:
    ● Re-read the translation text
    ● Draft general retell questions for comprehension testing
    ● Identify possible issues of misunderstanding
    ● Draft specific questions related to the main events in the passage, participant reference, key terms, foreign concepts, metaphors, rhetorical questions, inferential information, positive or negative associations, etc. This task is different from the community reviewing in stage 5. It uses a set of specific questions and retelling activities to see if the translation is communicating clearly and accurately the meaning of the source text. Often a set of specific individuals who have been trained in comprehension testing are used. Some translation consultants want this check done before they come for the consultant check, while others want to be present when the comprehension checking is performed. You should adjust the project plan according to your team’s workflow.
  •  ↑ C Perform comprehension testing, [100, 85, 70, 60]
    Perform comprehension testing, documenting feedback/answers for later analysis/review. Include supplementary materials in testing. The materials should all be tested with several different members of the language community.
  •  ↑ C Revise from feedback, [42, 36, 30, 24]
    The team reviews the results of the comprehension testing and incorporates changes to the text where appropriate. Repeat comprehension testing for revised passages as necessary.
  •  ∞   Basic Checks
    Character; Punctuation; Capitalization; RepeatedWord; QuotedText; MatchedPairs; Quotation; Numbers
  •  ∞   Spelling Checks
    Words with Unknown spelling status
  •  ∞   Notes Checks
    Project Notes (To Do)
  •  ∞   Biblical Term Renderings Checks
    Biblical Terms renderings found
 Stage 3: Preparing for Consultant
  • The goal of this stage is to prepare the back translation for the consultant. Automatic checks for missing and out of date verses in the back translation must be set to run at this stage. This check requires that the back translation project is associated with your project.Note: The translation consultant may ask that other tasks be completed before the consultant check occurs. For example, the consultant may ask that the renderings for certain Biblical terms be added to the Biblical terms tool, or all project notes be resolved. If additional tasks such as these are part of your team’s process, then add them to your project plan in this stage.
  •    C Draft the back translation, [42, 36, 30, 24]
    The back translation is created by someone who was not involved in the translation. The goal is to show how a reader will understand the text. It must be prepared without looking at any other translation or version or resource. The text is entered into the back translation project.
  •  ↑ C Check back translation, [100, 85, 70, 60]
    The team should verify that back translation is complete, and mark all verses as finished in Paratext. Do not change the words used when checking the text. Minor spelling problems are allowed. The back translation is merely an aid for the consultant and will not be published in most cases. Often it is the parts that appear to be poor grammar in the national language, that are most helpful for the consultant to see. However, spelling errors that are bad enough to prevent the consultant from understanding the back translation should be corrected.
Stage 4: Consultant Check
  • The consultant interacts with the team remotely to prepare for the checking session, and then plans a time when they can meet to review the text together. At the end of the checking session, the team has some work to comply with the consultant’s suggestions. When the consultant is satisfied the improvements have been made, a report or statement is submitted to the team showing the text has been approved.
  •    C Preliminary evaluation of text, [150, 128, 105, 90]
    The consultant receives the text in advance and makes preliminary evaluations. The consultant’s comments for the team are placed in the translation or back translation using project notes. The evaluation should focus on accuracy, clarity, naturalness, and acceptability of the translation. The consultant will also evaluate all supplementary materials and illustrations used. The team may review and implement suggestions made by the consultant prior to the direct interaction, if asked to do so by the consultant.
  •    C Consultant checking session, [150, 128, 105, 90]
    The consultant interacts with the translation team in a physical or virtual session. He or she makes observations about the text and supplementary materials, and gives assistance and advice as requested. This task involves editing, and a member should be assigned to make changes during the session.
  •  ↑ C Revise from consultant feedback, [420, 360, 300, 240]
    If the consultant gave action items during the checking session, these need to be completed and marked as resolved. Some consultants may want to approve and mark as resolved the issues they think are serious, while leaving the team to correct minor issues and marking them as resolved themselves. Some entities may have requirements about who may mark an issue resolved. If your entity has specific requirements in this regard, then customize this plan accordingly.
  •  ↑ C Receive consultant approval, [1000, 1000, 1000, 1000]
    After implementing the changes, get the consultant’s approval via the consultant report or appropriate means. If approval is not granted, follow whatever remaining recommendations to satisfy the consultant.
 Stage 5: Community Review
  • The goal of this stage is to have one or more community groups to review the text and make suggestions and recommendations. Note: If your team’s process requires other community reviewing and testing tasks add them to your plan in this stage. For example, some teams have special community meetings to test key terms, or to resolve issues related to different language variants.
  •  □ C Review Biblical terms and revise, [420, 360, 300, 240]
    Community leaders, church leaders, and other community members discuss how key terms are rendered. The team discusses comments about key terms made at the community review and uses those changes they think are valid.Consider using Paratext lite on an Android tablet to collect information at comprehension testing meetings, and Scripture Forge for situations when the language community is in several different countries.
  •  □ C Review for naturalness and revise, [210, 180, 150, 120]
    The community does a naturalness review of the audio or written text. The team discusses the suggestions from the naturalness review and makes any appropriate changes. Consider using Paratext lite on an Android tablet to collect information at comprehension testing meetings, and Scripture Forge for situations when the language community is in several different countries.
  •  ↑ C Report on community review, [1000, 1000, 1000, 1000]
    The team reports to the consultant on any textual or key terms changes made as a result of the community review. The rationale for the changes should be included. The team should open the Biblical terms tool and consult the notes, and history sections for the terms being reported on. It is best practice to enter this information in the tool as the changes were being discussed and decided on.
  •  ∞   Basic Checks
    Reference
  •  ∞   Spelling Checks
    Spelling Discussion Notes
  •  ∞   Notes Checks
    Spelling Discussion Notes; Renderings Discussion Notes
Stage 6: Final Preparation for Publication
  • The text is finalized for publication and uploaded to the DBL. If a typeset publication is in view, the typesetting requirements will be furnished by the typesetter.
  •  □ B Check and link glossary entries, [420, 360, 300, 240]
    For users to discover your glossary entries, the words must be marked for a print publication, or hyperlinked for digital publication. Use the tools in Paratext to add the necessary markup, which will create hyperlinked entries or other highlighting in print to identify glossary words.
  •  Ξ P Enter Publication Information, [1000, 1000, 1000, 1000]
    Open Project Properties for your project. Click on manage the Project Registration. This will take you to the entry for this project on the web. Go to the Publishing tab on the registration site and complete the information above the horizontal line.
  •  ↑ B Submit to the DBL, [1000, 1000, 1000, 1000]
    Submit the text to the DBL. For Wycliffe Global Alliance partners, the instructions are found at bit.ly/DBL-Submit. This page explains how to prepare the text and has a link to a form to fill for the submission.
  •  ↑ B Publish, [150, 150, 150, 150]
    Publish the translation in the form and media you have chosen: print, audio, digital, etc. You are encouraged to rename this task based on your publishing strategy and add other tasks as needed.
  •  ∞   Parallel Passages Checks
    Parallel Passages

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)

Languages present in project plan: pt, fr, en, es,

Privacy/Terms

Development Partners

Supporting Tools