#Chunk Overrides
Chunk overrides let you force a specific translation for a specific segment or chunk. Use them when a glossary rule is too broad and manual editing needs to be repeatable.
#Glossary Vs Override
Use a glossary when a term should be translated consistently everywhere.
Use a chunk override when a full segment needs exact wording in one place.
| Need | Use |
|---|---|
| A character name should always use the same spelling | Glossary |
| A repeated legal sentence must match approved wording | Chunk override |
| A product term has a required translation | Glossary |
| A subtitle line needs a shorter approved version | Chunk override |
#When To Use Overrides
- Repeated lines with strict wording requirements.
- Sensitive phrases that need approved wording.
- Subtitle lines where timing requires a shorter translation.
- Source segments that repeatedly produce an incorrect result.
- Passages where style matters more than literal structure.
#Override Workflow
- Identify an unstable or high-risk segment.
- Write the approved target text.
- Apply the override in the editor.
- Re-run or review the affected segment.
- Confirm the export uses the approved wording.
#Keep Overrides Maintainable
Overrides are powerful but can become hard to manage if overused.
Best practices:
- Prefer glossary entries for terms that recur across the project.
- Add a short note explaining why the override exists when possible.
- Review old overrides after major glossary changes.
- Remove stale overrides when regular translation produces the right result.