[Epic] Multi-vernacular translations #294
Labels
No labels
area: build
area: ci
area: compare
area: data
area: engine
area: model
area: provenance
area: rite
area: validation
backport
blocked
breaking
confirmed
dependencies
duplicate
epic
github_actions
invalid
needs-info
needs-triage
php
priority: high
priority: low
priority: medium
regression
type: bug
type: chore
type: correction
type: docs
type: enhancement
type: feature
type: fix
type: perf
type: refactor
type: security
wontfix
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Directorium/Core#294
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Diversity of language: more than Latin+English. Add keyed text variants on the same
textURN so a text can carry several translations. Done when the assembler can serve a text in any available language/translation.Epic — child issues are tracked as sub-issues.
Design of record: docs/design/office-text-layer.md (approved 2026-07-17, PR #494). No engine code until Stage 0 (§9) lands.
Stage 7. Spec §4.6 — keyed multi-vernacular via an additive sibling
variants:field on the part node (NOT nesting a translationKey under the locale key, which would be a forbidden major-bump reshape). Each variant carries its own source/rights/availability; restricted translations (e.g. Knox) resolve tolicence-required, neverfull.