Mirrors/super-productivity
1
0
Fork 0
mirror of https://github.com/johannesjo/super-productivity.git synced 2026-08-11 00:34:35 +00:00
Code Issues Projects Releases Wiki Activity
Page: 2.18 Contribute Translations
Pages
0.01 Style Guide 0.02 Wiki QA and Maintenance 2.01 Downloads and Install 2.11 Run the Development Server 2.12 Package the App 2.13 Run with Docker 2.14 Build for Android 2.15 Develop a Plugin 2.16 Set Up Development Environment 2.17 Add a New Issue Integration 2.18 Contribute Translations 2.19 Sync Proton Drive via rclone 2.20 Import from Todoist 2.21 Manage Plugins 3.05 Web App vs Desktop 3.06 User Data 3.07 Issue Integration Comparison 3.08 Sync Integration Comparison 3.09 Theming 4.01 The Today View 4.02 Inbox View 4.03 Planner View 4.04 Schedule View 4.05 Board View 4.06 Project View 4.07 Tag View 4.07a Tags_Eat the Frog 4.07b Tags_Ordinal Priorities 4.08 Time Estimates 4.09 Task Attributes 4.10 Task Notes 4.11 Subtasks 4.12 Scheduled Tasks 4.13 Repeating Tasks 4.14 How Time Is Logged 4.15 Timers and Focus Mode 4.16 Break Reminders 4.17 Idle Time 4.18 Reflection 4.19 Metrics 4.20 Task Archiving 4.21 Worklog 4.22 Quick History 4.23 Managing Your Data 4.24 Integrations
2 2.18 Contribute Translations
github-actions[bot] edited this page 2026-07-30 11:32:53 +00:00
Table of Contents

Contribute Translations

How to add or update translations for Super Productivity.

Translations are JSON files in src/assets/i18n/. English (en.json) is the source and fallback: missing or empty values show the English text.

Steps

  1. Add or update the source string in src/assets/i18n/en.json.
  2. Do not edit another locale file directly. Those files are managed through the translation script and direct edits may be overwritten.
  3. Run the app locally (2.11-Run-the-Development-Server) and check the UI.
  4. Follow docs/i18n-script-usage.md if the locale files need to be propagated or a translation work-in-progress file needs to be extracted and merged.
  5. Submit a pull request.

Format and Conventions

  • Keep the existing nested JSON structure and SCREAMING_SNAKE_CASE keys.
  • Prefer short, clear text (UI space is limited).
  • Edit en.json directly; use the script workflow for every other locale.

Translation Tooling

For finding missing keys and keeping files in sync, use the script described in the repo:

docs/i18n-script-usage.md (and tools/add-missing-i18n-variables.js).

Full contributor notes: docs/TRANSLATING.md.

Related

1.00-Quickstarts

2.00-How_To

Using Super-Productivity

Contributing to Super-Productivity

3.00-Reference

4.00-Concepts

Data-and-Integrations

Organizing

Planning

Doing

Reviewing

If you have further questions, please refer to the discussions page.