NidaMAP — Modular Aggregation of Principles for Bible Translation

Outline - finding errors using Paratext checking tools

BRBrian Renes · Mar 18, 2014, 9:58 PM · Last modified: Sep 28, 2026, 11:37 AM
♡ 0

Extracted text from Day_4_checking_I_outline.pdf:

Checking Text Outcome:

  1. have properly configured project and perfect rules defined in Paratext 2. when you transition the text to the next stage, it will have fewer errors

What you will learn:

  1. which rules can be defined in Paratext {see section: Know Study} 2. how to perfect your language rules in Paratext {see section: Skill Practice} 3. how to run the checks, understand the results and fix when necessary {see: Skill...}

Focus:

You can teach Paratext a few things about your language and the rules you establish for your project.

KNOW - STUDY Team (representing language community) must discuss and decide which versification model you follow exact chapter/verse structure (Gen31.55 = 32.1) if your translation has verse segments, which ones are possible and order (CEV: Mat 1.2-6a, 6b-11) if you have footnotes or cross references, the characters and order in notes (a b d e f h j k...) which letters or characters are word-forming characters (abc, and other special characters) words that can be repeated proper capitalization of words correct spelling of all words (Word List tool) correct spelling of Biblical Names (Biblical Terms tool) proper use of all punctuation marks...

SKILL - PRACTICE input the rules in the proper place (project properties and settings, language rules, inventories) know how to run checks which verify if my work follows the rules we established

Apply: Review your rules, run the checks and fix problems. (Refine rules if necessary)

Summary of desired outcome: Who does the checking? When? How? At the end of every stage: Stage 1: Draft, translate clean Stage 2: Internal review clean Stage 3: External review clean Stage 4: Final checking clean

0 comments

Sign in to join the conversation.