How to Use Translation Rules
Translation rules give the AI standing instructions about how to handle specific translation patterns. While glossary terms manage individual words and phrases, rules express broader guidelines — style preferences, formatting conventions, transliteration standards, and register requirements.
What Rules Do#
When you run AI Translate, Lectio includes all active rules in the AI's instructions. The AI follows these guidelines when generating suggestions. Rules let you codify decisions that would otherwise need to be communicated verbally to every translator or caught during review.
Creating a Rule#
-
Navigate to Translation Rules from the main menu.
-
Click Create Rule.
-
Choose the Source and Target languages.
-
Under Describe your translation rule, write what the AI should do in plain language. Be specific.
-
Under Applies to, choose the scope:
- Personal — use the rule for your translations.
- Team — use the rule automatically on projects shared with the selected team or teams.
- Projects — use the rule only on the specific projects you select.
- Public — make the rule available for other Lectio users to enable.
For Team or Projects, select at least one team or project.
-
Click Generate Rule. Lectio drafts the rule, a Rule Name (e.g., "Formal register for doctrinal content" or "Khmer transliteration of biblical names"), and example sentences. Generating a rule uses credits.
-
Review and edit the draft and every example, then click Confirm & Save.
Rules are written in natural language. The more precise your instructions, the more consistently the AI follows them.
Example Rules for Christian Content#
Here are practical examples of rules that teams translating Christian resources commonly use:
Transliteration Conventions
Name: Biblical proper name transliteration — Khmer
Rule: Transliterate biblical proper names into Khmer following the Khmer Bible Society convention. Examples: "Matthew" becomes "មែថាវ," "Jerusalem" becomes "យេរូសាឡឹម," "Paul" becomes "ប៉ូល."
Tip: Including specific examples in the rule definition helps the AI apply the pattern consistently to names not explicitly listed.
Register and Tone
Name: Formal register for theological terms
Rule: Use formal register when translating theological and doctrinal vocabulary. Use standard conversational register for narrative sections, dialogue, and practical application paragraphs and sections.
Formatting Conventions
Name: LORD in small caps
Rule: When the source text contains "the LORD" (with LORD in small caps, representing the divine name YHWH), translate using the target language's standard convention for the divine name rather than translating the word "lord" generically.
Denominational Preferences
Name: Baptism terminology
Rule: Translate "baptism" and related terms using the immersion-oriented vocabulary standard in the target language's Baptist tradition, not the sprinkling-oriented terms used in other traditions.
Audience-Specific Language
Name: Children's vocabulary level
Rule: Use simple, concrete vocabulary suitable for children aged 8-12. Avoid abstract theological jargon. When a theological concept must be included, follow it with a brief parenthetical explanation in child-friendly language.
Enabling and Disabling Rules#
Rules can be toggled on or off without deleting them:
- Open the Translation Rules page.
- Find the rule and click the toggle switch to enable or disable it.
Disabled rules are preserved but not sent to the AI. To keep a rule active on only some work, edit it and choose Projects instead of repeatedly toggling it.
Note: Only enabled rules affect AI suggestions. Disabling a rule does not change any translations that were already generated while the rule was active.
Applying Rules to Your Team#
To ensure consistent AI behavior across your team:
- Edit the rule from the Translation Rules page.
- Under Applies to, choose Team.
- Select one or more teams and save.
The rule appears in each selected team's members' rule list and is managed by the rule owner. It is automatically used whenever AI translation runs on a project shared with that team, so individual translators do not need to enable it separately.
Choose Projects instead when a convention belongs to a particular publication, client, or content series rather than every project a team handles. Only projects with the same source and target language pair are available to select. English, English (American), and English (British) sources count as the same language.
How Rules Work Alongside Other Resources#
Rules, glossary terms, and translation memories each serve a different purpose and work together:
| Resource | Scope | Purpose |
|---|---|---|
| Glossary | Individual terms | Ensures specific words are translated consistently |
| Translation Memory | Full sentences | Reuses past translations for similar content |
| Rules | Style and conventions | Guides the AI's overall approach to translation |
When the AI generates a suggestion, it considers all three. The result reflects your team's accumulated translation decisions.
Writing Effective Rules#
A few guidelines for getting the most out of rules:
- Be specific. "Use formal language" is vague. "Use formal register for doctrinal and theological content; use conversational register for narrative and practical application sections" gives the AI clear guidance.
- Include examples. Concrete examples help the AI generalize the pattern to similar cases.
- Keep rules focused. One rule per convention. A rule that tries to cover transliteration, register, and formatting all at once is harder for the AI to follow consistently.
- Review periodically. As your project evolves, some rules may need updating. Disable outdated rules and create new ones rather than overloading a single rule.
Next Steps#
- Manage Glossaries to pair rules with term-level consistency
- Manage Translation Memories to complement rules with sentence-level reuse
- Translate Segments to see rules in action during AI translation