Paratext checks in Aquilla
If you check translations in Paratext, you already know most of what Aquilla checks. The difference is when the checks run. In Paratext you run a check over a book and work through the list it produces. In Aquilla most checks run on every cell as you type, so a problem is flagged the moment it appears, and Check file gives you a full list for one file when you want it.
Aquilla’s checks also need far less setup. Paratext’s checks read inventories and settings that someone fills in first. Aquilla’s built-in checks run as soon as a project has text, judging the translation against its source and against the target language’s own conventions.
Paratext checks and their Aquilla equivalents
Section titled “Paratext checks and their Aquilla equivalents”| In Paratext | In Aquilla | Where it runs |
|---|---|---|
| Chapter/verse numbers | Missing, duplicate and out-of-order chapters and verses are listed under “Structure problems found in this file” when you import USFM. | Import preview |
| Markers | USFM markers: a marker USFM doesn’t define, or a paired marker left open. | Every cell |
| Unmatched pairs | Unpaired brackets and Unpaired quotes. Check file also finds a quotation that opens in one cell and never closes. | Every cell, and Check file |
| Numbers | Number integrity (a number from the source is missing) and Extra numbers (a number the source doesn’t have). Number format checks digits and separators against the target language. | Every cell |
| References | Scripture references: a book name the project doesn’t use, a chapter the Bible doesn’t have, or a mix of chapter–verse separators. | Every cell |
| Footnote quotes | Footnote quote: text a footnote or cross-reference quotes must appear in the verse. | Every cell |
| Capitalization, mixed capitalization, punctuation followed by lowercase | Capitalization flags a lowercase letter that should be a capital. Check file adds words like “tHe” and headings that start in lowercase. | Every cell, and Check file |
| Repeated words | Repeated word, unless the source repeats it too. | Every cell |
| Punctuation | End punctuation and Punctuation integrity compare the translation’s punctuation with the source’s. To forbid a sequence such as :,, write your own check. |
Every cell |
| Spelling, similar words | The Spelling section of Check file builds a wordlist from your translation and flags a rare spelling of a word the text usually writes another way. | Check file |
| Biblical terms | Terminology flags a cell that doesn’t use an approved rendering, and Check file counts how consistently each term is rendered. | Every cell, and Check file |
| Relatively long or short verses | Length mismatch flags a translation under 40% or over 250% of its source’s length. | Every cell |
| Characters | Not yet. Corrupted characters catches garbled text and Untranslated words catches words left in the source’s script, but there is no character inventory. | Every cell |
The names in bold are the check names you see in Aquilla. Built-in checks describes each one in full.
Turning on the checks that start off
Section titled “Turning on the checks that start off”Most checks are on from the start. Three are off, because each one needs something from your project to give useful results:
- Scripture references needs the book names your project uses.
- Number format needs the project’s target language, so it knows which digits and separators that language uses.
- Length mismatch is off because normal length varies between language pairs.
Switch them on in the Checks list of Living Memory. Each check there has an on/off switch and a severity menu. On a project with several target languages, the switches apply to one language at a time.
Running checks on a whole file
Section titled “Running checks on a whole file”The checks that run on every cell need no action from you. To review a file the way you would review a Paratext check list, open the file and choose Check file from the editor’s ⋯ menu. The File check panel groups what it finds: Rule violations, Term consistency, Capitalization and Spelling. Click a finding to jump to its cell.
In the Spelling section, a flagged word names the spelling the text usually uses, for example “Sounds like “Yesu”, which this text writes 14 times.“ If the rare spelling is correct, Approve clears every place it occurs. A word the text writes often enough is treated as correct and listed as not flagged.
See Checking a file on demand for the rest of the panel.
Accepting a finding that is correct
Section titled “Accepting a finding that is correct”Paratext lets you deny a check result you have judged correct. In Aquilla you Waive it. Open the cell’s Issues tab, or click the flagged words, and choose Waive. When a cell has the same kind of finding more than once, each one gets its own row, so waiving one leaves the others flagged. Text you add later is checked again.
Adding checks of your own
Section titled “Adding checks of your own”When your project has a rule Aquilla doesn’t check, such as a punctuation sequence that is never allowed or a word that must always be spelled one way, write it as a check. Choose Add check in Living Memory’s Checks list. A check can carry an automatic fix, and Try to fix all proposes that fix for every cell that breaks it, so you can review the changes before any are written. See Rule flags & fixes.
What Aquilla does not do yet
Section titled “What Aquilla does not do yet”Aquilla is in beta and its checks are still growing. This page changes as they do.
Help assistant
AI answers from the Aquilla docs — may make mistakes.