marcel/familienarchiv
1
0
Fork 0
Code Issues 119 Pull Requests 2 Actions Packages Projects Releases Wiki Activity

feat: implement i18n — extract static texts, add EN + ES-MX translations, add language selector #2

New Issue
Closed
opened 2026-03-17 19:39:54 +01:00 by marcel · 0 comments
marcel commented 2026-03-17 19:39:54 +01:00
Owner
Copy Link

Summary

All UI text is currently hardcoded in German. Paraglide.js is already set up in the project but not yet used. This issue covers the full i18n rollout: text extraction, translation, and a language selector in the header.

Scope

1. Text extraction

Go through every .svelte file and extract all visible German strings into messages/de.json. This includes:

  • Navigation labels (Dokumente, Personen, Konversationen, Admin, Abmelden)
  • Page headings and subheadings
  • Form labels, placeholders, helper text
  • Button labels (Speichern, Abbrechen, Bearbeiten, Zusammenführen, …)
  • Status badges (UPLOADED, PLACEHOLDER, …)
  • Empty state messages
  • Error messages (already partially in src/lib/errors.ts)
  • Section titles (Details, Personen, Inhalt, Absender, Empfänger, …)

2. Translations

Provide translations for all extracted keys in:

  • messages/en.json — English
  • messages/es.json — Spanish (Mexico, es-MX)

3. Language selector

Add a compact language switcher to the header (top-right, next to the logout button). Suggested appearance:

DE | EN | ES

The active language is bold/highlighted. Uses Paraglide's setLanguageTag() and persists the choice (cookie or localStorage).

Technical notes

  • Paraglide.js is already configured (src/lib/paraglide/, vite.config.ts)
  • The messages/ directory already exists with a de.json stub
  • Follow the existing Paraglide usage pattern from src/routes/demo/paraglide/+page.svelte if present
  • Use m.key() call syntax throughout components — do not use string interpolation inside translation keys
  • Date/number formatting already uses Intl — that stays as-is

Acceptance criteria

  • All visible UI text is driven by Paraglide message keys, no hardcoded German strings remain in .svelte files
  • Switching language updates all text immediately without a full page reload
  • Selected language persists across navigation and page reloads
  • messages/de.json, messages/en.json, messages/es.json are all complete and consistent
## Summary All UI text is currently hardcoded in German. Paraglide.js is already set up in the project but not yet used. This issue covers the full i18n rollout: text extraction, translation, and a language selector in the header. ## Scope ### 1. Text extraction Go through every `.svelte` file and extract all visible German strings into `messages/de.json`. This includes: - Navigation labels (Dokumente, Personen, Konversationen, Admin, Abmelden) - Page headings and subheadings - Form labels, placeholders, helper text - Button labels (Speichern, Abbrechen, Bearbeiten, Zusammenführen, …) - Status badges (UPLOADED, PLACEHOLDER, …) - Empty state messages - Error messages (already partially in `src/lib/errors.ts`) - Section titles (Details, Personen, Inhalt, Absender, Empfänger, …) ### 2. Translations Provide translations for all extracted keys in: - `messages/en.json` — English - `messages/es.json` — Spanish (Mexico, `es-MX`) ### 3. Language selector Add a compact language switcher to the **header** (top-right, next to the logout button). Suggested appearance: ``` DE | EN | ES ``` The active language is bold/highlighted. Uses Paraglide's `setLanguageTag()` and persists the choice (cookie or localStorage). ## Technical notes - Paraglide.js is already configured (`src/lib/paraglide/`, `vite.config.ts`) - The `messages/` directory already exists with a `de.json` stub - Follow the existing Paraglide usage pattern from `src/routes/demo/paraglide/+page.svelte` if present - Use `m.key()` call syntax throughout components — do not use string interpolation inside translation keys - Date/number formatting already uses `Intl` — that stays as-is ## Acceptance criteria - All visible UI text is driven by Paraglide message keys, no hardcoded German strings remain in `.svelte` files - Switching language updates all text immediately without a full page reload - Selected language persists across navigation and page reloads - `messages/de.json`, `messages/en.json`, `messages/es.json` are all complete and consistent
marcel added the feature label 2026-03-17 19:42:03 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
P0-critical
Blocks a core user journey, causes data loss, or is a security/accessibility barrier. Work on this before P1+.
 P1-high
Significant friction on a main user journey; workaround exists but is non-obvious. Next up after P0.
 P2-medium
Noticeable improvement; doesn't block anything; schedule opportunistically.
 P3-later
Cosmetic or parking-lot work; fine to stay open indefinitely.
 audit
Read-only audit / assessment work; produces a report rather than changing code
 bug
Something isn't working
 cleanup
Removal of dead code, vague comments, naming violations, and scratch artifacts
 collaboration
We want to extend the family archive to have more collaboration tools
 conversation
descoped
We will do that later
 devops
documentation
README, ARCHITECTURE, GLOSSARY, CONTRIBUTING, per-domain docs
 epic
Marker for epic-level issues that group multiple child issues
 feature
file-upload
legibility
Codebase Legibility Refactor — preparing the codebase for human evaluation and bus-factor reduction
 notification
person
phase-1: security
Security hygiene — must be done first
 phase-2: container-images
Production-ready multi-stage Docker images
 phase-3: prod-compose
Production compose overlay + Caddy reverse proxy
 phase-4: spring-prod-profile
Spring Boot production configuration profile
 phase-5: backups
Database and object storage backup strategy
 phase-6: deployment-docs
.env.example, DEPLOYMENT.md, runbook
 phase-7: monitoring
Prometheus, Loki, Grafana, Alertmanager
 refactor
Code restructuring without behaviour change
 security
test
ui
UI/UX and accessibility issues
 user
No Label feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Jens marcel
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: marcel/familienarchiv#2
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?