Skip to content

Backlog: Accept-Language on public label landing pages (/t/{code}) #60

Description

@sliptonic

What to build

Deferred marker — not scheduled. The four Jinja templates behind /t/{code} (label landing, owner, blank, public spec page) are the only core-owned prose surface facing anonymous end users — no client sits in between, so the core itself must eventually localize them. When a non-English audience materializes: Accept-Language negotiation + gettext/Babel over the templates (~110 lines total; roughly a day including tests).

Deliberately out of scope everywhere else in the core:

Acceptance criteria

  • Accept-Language negotiation on /t/{code} routes with English fallback
  • Template strings externalized via gettext; at least one non-English locale shipped as proof
  • Record-supplied strings (tool names) remain untranslated user data; autoescape assumptions unchanged (SECURITY_ASSUMPTIONS.md)

Blocked by

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions