Proposal: i18n / localization support (starting with Simplified Chinese)

Aperta
  • Qualcosa non va?
#18 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
22/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
go, javascript
Ambito
backend, frontend, internationalization

Direzione di ricerca

Start by reading the proposal's Current state section, then the frontend components under frontend/src/lib/ and the Go strings in tray_desktop.go, tray_status.go and app.go. The open question is the i18n approach (svelte-i18n or a zero-dependency dictionary), so agree that with the maintainer before writing code. Done means an accepted skeleton PR with the Settings language dropdown and one view extracted to en.json.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

help wanted
Motivation

OpenSave is a fantastic tool, but its UI is English-only. For many users
(especially in the Chinese gaming community, where save-syncing for emulators,
GOG/Epic, and repacks is a very common pain point), an English UI is a real
adoption barrier. The project's own docs say it is "written for people who
have never done this before" — localization would extend that to people who
have never done this before in English.

Current state

I audited the v2.4.0 codebase:

  • The frontend (~83 .svelte components, ~81 modules in frontend/src/lib/)
    has no i18n framework — all user-facing strings are hardcoded inline
    in templates and JS.
  • The Go side also hardcodes user-visible strings (tray menu in
    tray_desktop.go / tray_status.go, dialogs and messages in app.go,
    notifications).
  • No existing issue/PR mentions i18n or translations.
Proposal
  1. Frontend: adopt a lightweight i18n layer (e.g. svelte-i18n) with
    locale JSON files (en.json as source of truth, plus one file per
    language). Extract strings incrementally, view by view, to keep PRs
    reviewable.
  2. Go side: a small message catalog (e.g. go-i18n or a simple map) for
    the handful of tray/notification/dialog strings.
  3. Settings: a "Language" dropdown in Settings (default: system locale).
  4. Ship built-in en + zh-CN first; the structure makes community
    translations (ja, ko, de, ru…) drop-in easy afterwards.
Why this is tractable
  • As a proof of feasibility, I have already produced a complete working
    Simplified Chinese version (direct string replacement, ~1,100 strings across
    views/components/lib/Go side). All frontend tests pass
    (249/249 after adapting test assertions). So the translation content
    is done and validated — the remaining work is the mechanical extraction
    into locale files.
  • The extraction can be done in small batches (per view), so no single PR
    is overwhelming.
About me / offer

I'd be happy to contribute this: I can start with (a) an issue-accepted i18n
skeleton PR (frontend infra + Settings dropdown + en.json extraction of one
view as the pattern), then (b) follow-up PRs per view, and (c) the complete
zh-CN catalog.

Happy to discuss alternative approaches (e.g. if the maintainer prefers a
zero-dependency dictionary module over svelte-i18n).

Built and tested against v2.4.0 (f9bb679). Windows 11, Wails v2.12.

Lingua principale
Go
Stelle
225
Fork
9
Merge medio
1g 21h
PR unite (30g)
72

Preparare l'ambiente

  • Include un Dockerfile o un file Docker Compose
  • Nessun modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di Liquid-co/OpenSave

Tutte le issue di Liquid-co/OpenSave

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.