Terminology
Consistency matters in translation: a key term like LORD or covenant should be rendered the same way everywhere. Aquilla’s terminology system helps your team agree on preferred renderings and keep to them.
Termbases and concepts
Section titled “Termbases and concepts”- A termbase is a project’s dictionary of concepts — the meanings you care about (for example “God’s covenant” or “forgiveness”).
- Each concept records its preferred rendering in your target language, along with definition and related concepts.
- A project can use its own termbase and also subscribe to org-wide termbases shared across projects.
Rendering status
Section titled “Rendering status”A concept can list more than one target rendering, and each one carries a status that says how it should be treated:
| Status | Meaning |
|---|---|
| Preferred | The rendering to reach for — what Aquilla nudges you toward. |
| Admitted | An acceptable alternative; allowed without a nudge. |
| Forbidden | This rendering should not be used; flagged as a violation. |
A concept itself also has a lifecycle — active, draft, or deprecated. Only active concepts are compiled into the checks you see while translating; draft and deprecated concepts sit in the termbase without being enforced.
How enforcement feels while translating
Section titled “How enforcement feels while translating”Terminology in Aquilla is advisory by design — it guides without blocking:
- As you type, Aquilla checks your text against the active concepts in the termbase.
- If a cell should use a concept’s preferred rendering, you’ll see an advisory highlight — a nudge, not a wall. You can still override it when the context calls for something different.
- If a cell uses a forbidden rendering, that’s treated more firmly: it shows up both in the violations inbox and on the cell’s severity stripe.
Sharing terminology in and out
Section titled “Sharing terminology in and out”Terminology can be imported and exported in standard formats — TBX (the industry terminology-exchange standard) and CSV — so you can round-trip your termbase with other translation tools. See Exporting your work.