Negotiate and resolve language selection with fallback rules #61

New issue

Open

opened 2026-07-01 00:59:32 +00:00 by manlycucumber · 0 comments

manlycucumber commented

2026-07-01 00:59:32 +00:00

(Migrated from github.com)

Problem

Text may be available in several languages (e.g. Latin and a vernacular), and clients need predictable rules for which language(s) they receive, including bilingual output and fallbacks when a translation is missing.

Acceptance criteria

Requests can select a single language or a bilingual pairing.
A documented fallback applies when a requested language is unavailable for a string.
The chosen/effective language is echoed in the response.
Language resolution is covered by tests including the fallback path.

Notes

Bilingual selection foreshadows the Mass and Breviary endpoints.

## Problem Text may be available in several languages (e.g. Latin and a vernacular), and clients need predictable rules for which language(s) they receive, including bilingual output and fallbacks when a translation is missing. ## Acceptance criteria - [ ] Requests can select a single language or a bilingual pairing. - [ ] A documented fallback applies when a requested language is unavailable for a string. - [ ] The chosen/effective language is echoed in the response. - [ ] Language resolution is covered by tests including the fallback path. ## Notes Bilingual selection foreshadows the Mass and Breviary endpoints.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

Directorium/Api#61

No description provided.

Rows
Columns