Supernotes Languages

Community-contributed translation files for Supernotes, the collaborative note-taking and knowledge management app.

Available Languages

Flag	Language	Code	Status	Translator
🇬🇧	English	en	Source	@supernotes
🇬🇧	English (UK)	en-gb	Complete	@supernotes
🇩🇪	German	de	Complete	@supernotes
🇪🇸	Spanish	es	Complete	@supernotes
🇫🇷	French	fr	Complete	@supernotes
🇮🇩	Indonesian	id	Complete	@supernotes
🇮🇹	Italian	it	Complete	@supernotes
🇵🇹	Portuguese	pt	Complete	@supernotes
🇧🇷	Portuguese (Brazil)	pt-br	Complete	@supernotes
🇨🇳	Chinese (Simplified)	zh-cn	Complete	@hildxd
🇰🇷	Korean	ko	Complete	@supernotes

File Structure

Each locale is a single JSON file named <locale-code>.json. Files use a nested key structure:

{
  "_lang_code": "fr",
  "_lang_english": "French",
  "_lang_native": "Français",
  "_lang_flag": "🇫🇷",
  "actions": {
    "archive": "Archiver",
    "cancel": "Annuler",
    ...
  },
  ...
}

The _lang_* metadata keys at the top of each file define the locale's display name, native name, and flag emoji.

Contributing

We welcome translations for new languages and improvements to existing ones!

Context File

There is a context.json file that can be used to help understand the usage of the actual strings within the codebase. If you encounter any expected translations that seem to be a result of misunderstood usage of a string, please also update the context file to help translations across all languages!

Improving an Existing Translation

1. Open the relevant <locale-code>.json file
2. Find the key(s) you'd like to improve
3. Submit a pull request with your changes

Adding a New Language

1. Copy en.json as a starting point
2. Rename it to your BCP 47 language tag (e.g. ja.json, ko.json, zh-cn.json)
3. Update the _lang_code, _lang_english, _lang_native, and _lang_flag metadata fields
4. Translate all values (keys must stay the same)
5. Submit a pull request

Translation Guidelines

• Preserve placeholders like {{count}}, {{name}}, {{price}} exactly as they are
• Preserve HTML tags like <bold>, <red>, <italic>, <b>, <kbd> exactly as they are
• Keep product names in English: Supernotes, Anti-Procrastin, Noteboard
• Keep technical terms where appropriate: markdown, JSON, PDF, API, LaTeX
• Empty strings should stay empty (e.g. "tips.empty": "")
• All keys present in en.json must be present in your translation (100% coverage required)

License

These translations are provided for use with Supernotes. All rights reserved by Supernotes Ltd.