WORK-507
ID:WORK-507Status:done

Localize behavior strings (Zone 5) — inline delivery

The ~45 client-side strings across packages/behaviors/src/behaviors/ and .../elements/. Behaviors have no server config, so translations are delivered inline (Decision D4): no fetched endpoint.

Priority:mediumComplexity:moderateMilestone:v0.29.0Source:SPEC-035
main View source

Criteria completion

Criteria completion: 4 of 4 (100%) checked; tracking started on Jul 17, no incremental history yet0%25%50%75%100%Jul 17Jul 30

Tracking started Jul 17 — check back for trends.

Relationships

Implements 1
Related 2
Branches 3
main current done
main doneclaude/milestone-v0-29-0-stzywk doneclaude/multi-language-support-spec-5zzt9q ready

Scope

  • data-i18n-* attributes: the identity transform emits data-i18n-{key}={translated} on rune root elements for behavior strings that attach to an element it already renders. Prefer this path wherever a string has an anchor element.
  • Inline JSON block: ThemeShell (and each adapter's page shell) emits <meta name="rf-locale"> + <script type="application/json" id="rf-strings"> carrying only runtime-created strings (e.g. "No results found.", "Copied", dynamically-built gallery labels) — ~15–20 strings, active locale only.
  • Each behavior reads: element attribute → getGlobalString(key) → hardcoded English default.
  • Cover the new files the spec inventory added: behaviors/carousel.ts, behaviors/mobile-menu.ts, behaviors/section-nav.ts/scrollspy.ts, plus elements/* (audio/map/sandbox; scan chart/diagram/nav/context).
  • Tests: attribute + block resolution, and SSR-only (no-JS) fallback to English.

Acceptance Criteria

  • Element-attached behavior strings resolve from data-i18n-*; runtime-created strings resolve from the inline JSON block; both fall back to English.
  • Only the active locale is emitted; no /rf-strings.json fetch is introduced.
  • Strings are available synchronously at behavior init (no flash-of-English); no-JS pages render English.
  • All Zone 5 files, including the new ones, are covered.

Blocked by

  • WORK-502

References

  • SPEC-035 — Zone 5, Client-side Resolution, Decision D4.

Resolution

Completed: 2026-07-17

Branch: claude/milestone-v0-29-0-stzywk

What was done

  • packages/behaviors/src/i18n.ts: BEHAVIOR_STRINGS catalog (English floor), bstr(key, n?) (inline block → English, {n} interp), elStr(el, attr, key, n?) (element data-i18n-* → block → English), cached #rf-strings parse.
  • Converted every Zone-5 file: copy, gallery, preview, reveal, search (innerHTML template + runtime empty states), datatable, form, juxtapose, carousel, mobile-menu, section-nav, and elements audio/map/sandbox.
  • Delivery: collectBehaviorStrings(ctx) in transform + html page-shell emits <meta name="rf-locale"> + <script type="application/json" id="rf-strings"> (active locale only, </script>-escaped), nothing for English.
  • Tests: packages/behaviors/test/i18n.test.ts (7) — element/block/English precedence, {n}, malformed-block resilience.

Notes

  • Inline delivery per Decision D4 — synchronous init, no fetch, no-JS renders server English. Element data-i18n-* path is supported by the client helper; auto-emitting those attributes per-rune from the engine is a safe additive follow-up (behaviors already check the element first). Full workspace build + 241 behaviors/html tests green.