Register the i18n text domain and wrap all user-facing strings #22

New issue

Closed

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

manlycucumber commented

2026-07-01 01:05:05 +00:00

(Migrated from github.com)

Problem

The plugin must be fully translatable. Every user-facing string needs to go through the text domain, and the domain must load correctly.

Acceptance criteria

The text domain is loaded on the appropriate init hook.
All front-end and admin strings are wrapped in translation functions with the correct text domain.
A generated .pot template covers every translatable string.
A lint/CI check fails on un-wrapped translatable strings.

Notes

Liturgical Latin tokens that must not be translated are documented and excluded.

## Problem The plugin must be fully translatable. Every user-facing string needs to go through the text domain, and the domain must load correctly. ## Acceptance criteria - [ ] The text domain is loaded on the appropriate init hook. - [ ] All front-end and admin strings are wrapped in translation functions with the correct text domain. - [ ] A generated .pot template covers every translatable string. - [ ] A lint/CI check fails on un-wrapped translatable strings. ## Notes Liturgical Latin tokens that must not be translated are documented and excluded.

manlycucumber referenced this issue from a commit

2026-08-05 19:02:32 +00:00

feat: tabbed settings, i18n, filemtime assets & readme (Epic #20) (#108)

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/Ordo#22

No description provided.

Rows
Columns