i18n: translate Electron main-process menus
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 432
- Forks
- 51
- PR merge metrics
- No merged PRs in 30d
Description
Part of the frontend internationalization effort (see Epic). Depends on language selector + persistence.
The Electron main process is separate from React and has ~40 hardcoded label:/title: strings (tray menu, app menu, tooltips) in src/frontend/src/electron/electron-main.js.
Tasks
- Load standalone
i18nextin the main process, sharing the same locale JSON files - Read the persisted locale on startup
- Translate tray menu, app menu, and tooltips
- Rebuild the menu on a language-change IPC event (renderer → main)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in src/frontend/src/electron/electron-main.js, then inspect the existing React locale JSON files, language selector, and persistence flow. Trace how renderer-to-main IPC is handled before implementing the listed menu and tooltip translations. Done means startup uses the persisted locale, all main-process labels are translated, and menus rebuild after a language-change event.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- electron, javascript, react
- Domain
- desktop, frontend, internationalization
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100