Paratext

  • Registration
  • Downloads
  • Support
  • Features
  • News
You are here: Home / Support / Learning about Paratext / Project Plans / Biblica Base Plan

Biblica Base Plan

Rev 1.02
 Stage 1: Setup and Drafting
  • Prerequisites* Research and Development done* Translation/Revision Brief approved* Translation/Revision team recruited* Translation training* Paratext training* ICA signed1) Translation Technology Director or designee creates and registers the Paratext Working Project (WP): – Sets up Project Plan based on approved project brief and style guide – Adds Paratext project plan – Adds standard custom.sty and custom.vrs – Adds autocorrect.txt – Adds standard metatext template – Sets up language settings – Creates Back translation project and tasks if needed – Creates “Consultant Check” note type – Adds personnel and grants Roles and Permissions2) Global Project Manager initiates Project plan 3) Translation team drafts/revises translation, introductions, and metatext
  •  ▒ P Initiate Project Increment, [1000, 1000, 1000, 1000]
    Global Project ManagerSets the Working Project progress parameters for the increment in the Paratext Registry – Scope: (Current Increment) – Status: Active – Expected Completion Date: (Current Increment)
  •  ↑ C First Draft Editing, [14, 12, 10, 8]
    Area Project Manager – Sets Scope of the increment in Project Properties – Assigns tasks to team members – Sets task due datesAfter thorough exegesis, Translators: – draft/revise chapters assigned to them: – resolve issues found by basic checks – use the Wordlist tool to check spelling – approve Major Biblical Terms using the Biblical Terms tool – use Parallel Passage tool – draft/revise book introductionsLinguist/Translator – Approves spelling and hyphenation using Wordlist tool
  •  ↑ C Technical Check, [1000, 1000, 1000, 1000]
    Technical Manager – Verifies checks are correctly done – Verifies markup is correctly applied – Cleans up any errors or inconsistencies
  •  ∞   Basic Checks
    ChapterVerse; Marker; Character; Punctuation; Reference; QuotedText; RepeatedWord; MatchedPairs; Quotation; Numbers; Capitalization
  •  ∞   Spelling Checks
    Words with Unknown spelling status; Words with Incorrect spelling status
  •  ∞   Notes Checks
    Notes Assigned to Me; Project Notes (Conflict)
  •  ∞   Biblical Term Renderings Checks
    Biblical Terms renderings found
 Stage 2: Internal Review
  • Text is updated based on:1) Language Expert review2) Team review3) Community feedback
  •  Ξ B Grammar and Spelling Review, [1000, 1000, 1000, 1000]
    Language Expert – Reads through text – Flags grammatical, clarity, and naturalness errors with “To Do” notesUsing Wordlist tool: – runs advanced spelling checks – marks misspelled word as incorrect – creates or comments on Spelling Discussion Notes
  •  Ξ B Co-translator Review, [42, 36, 30, 24]
    Co-translator – Makes suggestions using “To Do” Notes – Creates or comments on Rendering Discussion Notes (Biblical Terms tool)Suggested activities: – responds to translator notes – reads aloud for naturalness – checks against a model text for accuracy
  •  □ B Oral Testing, [1000, 1000, 1000, 1000]
    Translation team – Organizes oral group reading of the entire text increment – Solicits comments from select members of the language community using “Guidelines for Oral Testing” document – Adds recommendations to the project as “To Do” notes
  •  Ξ C Second Draft Editing, [1000, 1000, 1000, 1000]
    Translator – Reviews Co-translator, Language Expert, and community feedback – Resolves as many “To Do” notes as possible – Changes unresolved notes to “Consultant Check” notes – Edits text as necessary
 Stage 3: External Review
  • Text is updated based on:1) Literary/stylistic check2) Consultant review3) Parallel passage check
  •  Ξ C Literary/Stylistic Check, [1000, 1000, 1000, 1000]
    Third-party Reader – Checks for orthography, punctuation, grammar, and written style using “Guidelines for Literary/Stylistic Check” documentMay use one or more of the following options:A. Flag errors with “To Do” notes in Paratext or Paratext LiteB. Edit the text directly in ParatextC. Comment on a Print Draft printout or PDF of the text
  •  Ξ B Consultant Review, [1000, 1000, 1000, 1000]
    Consultant – Checks text using interlinear tool, parallel passage tool, and back translation if availableCreates or responds to: – “To Do” and “Consultant Check” notes – Rendering Notes in the Biblical Terms tool – Spelling Notes in the Wordlist tool
  •  Ξ C Third Draft Editing, [1000, 1000, 1000, 1000]
    Translator – Does the Parallel passage check with consultant guidance – Resolves “To Do” and “Consultant Check” notes – Resolves Spelling Discussion Notes (Wordlist tool) – Resolves Rendering Discussion Notes (Biblical Terms tool) – Makes changes to text as necessary based on Notes and Parallel Passage check
  •  ∞   Spelling Checks
    Spelling Discussion Notes
  •  ∞   Notes Checks
    Spelling Discussion Notes; Renderings Discussion Notes
  •  ∞   Parallel Passages Checks
    Parallel Passages
 Stage 4: Signoff
  • Text is updated and prepared for publication:1) Metatext completed2) Quality of Paratext checks verified
  •  Ξ B Complete Peripheral Books, [150, 150, 150, 150]
    Translation team – Completes translation of metatext in FRT and BAK books – Writes preface
  •  Ξ C Pre-publication Draft Editing, [1000, 1000, 1000, 1000]
    Translators – Resolve any issues found by the Project Manager, Technical Manager, and Technical Director – Make changes to text as necessary
  •  ↑ B Project Manager Signoff, [1000, 1000, 1000, 1000]
    Area Project Manager or Translation Consultant – Verifies all tasks and checks have been done and all Notes resolved – If necessary, sends project back to the translation team to resolve outstanding issues
  •  ↑ B Technical Manager Signoff, [1000, 1000, 1000, 1000]
    Project Technical Manager – Verifies that errors have not been denied inappropriately – Verifies that checking inventories have been marked correctly – Looks for additional issues that might need to be addressed using advanced checks and tools – Resolves as many checking issues as possible – If necessary, sends project back to the translation team to resolve outstanding issues
  •  ↑ B Technical Director Signoff, [1000, 1000, 1000, 1000]
    Translation Technology Director or designee: – Approves the quality of all Paratext checks – If necessary, sends project back to Technical Manager to resolve outstanding issues – Creates/Updates Publishing Project (PP) – Sets Paratext Registry Status to Typesetting (WP&PP) – With Global Project Manager input, authorizes the Project Manager to set the Scope in Project Properties and begin First Draft Editing of the next increment (Task 1.2)
 Stage 5: Typesetting and Publication
  • Issues discovered during typesetting resolved:1) Preliminary typeset review2) Final typeset proofreadPublished to DBL
  •  Ξ P Preliminary typeset review, [1000, 1000, 1000, 1000]
    Community members review the Preliminary Typeset using “Guidelines for Preliminary Typeset Review” document
  •  Ξ C Preliminary Text Editing, [1000, 1000, 1000, 1000]
    Translation Technology Director or designee, in consultation with designated member of the translation team: – Resolves issues discovered during Preliminary typeset review – Corrects the Publishing ProjectTranslation team member – Updates the Working Project
  •  Ξ P Final Typeset Proofread, [1000, 1000, 1000, 1000]
    Translation team proofreads the Final Typeset to correct inadvertent typesetting errors using “Guidelines for Final Typeset Proofread” document
  •  ↑ C Final Text Editing, [1000, 1000, 1000, 1000]
    Translation Technology Director or designee – Resolves any errors in the Publishing ProjectTranslation team member – Verifies corrections – Updates the Working Project
  •  Ξ P Final Translation Signoff, [1000, 1000, 1000, 1000]
    VP, Global Translation – Signs off on the translation project – Indicates completed status on the translation dashboard
  •  Ξ P Publish, [1000, 1000, 1000, 1000]
    Translation Technology Director – Submits completed books to the Digital Bible Library (DBL) – Sets Paratext Registry Status to Published (PP) – Authorizes the Global Project Manager to set the progress parameters for the next Project Increment in the Paratext Registry (WP) (Task 1.1)

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)

Quick Support Links

  • Paratext FAQ
  • Paratext Training Videos
  • Scripture Markup (USFM)
  • Paratext Training Plans
  • Paratext Supporter Forum

Upcoming Events

There are no upcoming events at this time.

News and Updates

  • Collaboration through Project Sharing February 15, 2021
  • New Tool for Printing from Paratext January 11, 2021
  • Paratext 9.1 has now been released! December 17, 2020
  • Expand your Team with Paratext Lite October 28, 2020
  • Paratext 9.1 Beta is Now Available August 25, 2020

Privacy/Terms

  • Paratext Terms of Use
  • Privacy Policy

Development Partners

  • United Bible Societies
  • SIL International

Supporting Tools

  • Paratext Registry
  • Publishing Assistant
  • The Digital Bible Library

Copyright © 2016, United Bible Societies & SIL International, All Rights Reserved.