Community-contributed translation files for Supernotes, the collaborative note-taking and knowledge management app.
| Flag | Language | Code | Status |
|---|---|---|---|
| 🇬🇧 | English | en |
Source |
| 🇬🇧 | English (UK) | en-gb |
Complete |
| 🇩🇪 | German | de |
Complete |
| 🇪🇸 | Spanish | es |
Complete |
| 🇫🇷 | French | fr |
Complete |
| 🇮🇩 | Indonesian | id |
Complete |
| 🇮🇹 | Italian | it |
Complete |
| 🇵🇹 | Portuguese | pt |
Complete |
| 🇧🇷 | Portuguese (Brazil) | pt-br |
Complete |
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.
We welcome translations for new languages and improvements to existing ones!
- Open the relevant
<locale-code>.jsonfile - Find the key(s) you'd like to improve
- Submit a pull request with your changes
- Copy
en.jsonas a starting point - Rename it to your BCP 47 language tag (e.g.
ja.json,ko.json,zh-cn.json) - Update the
_lang_code,_lang_english,_lang_native, and_lang_flagmetadata fields - Translate all values (keys must stay the same)
- Submit a pull request
- 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.jsonmust be present in your translation (100% coverage required)
These translations are provided for use with Supernotes. All rights reserved by Supernotes Ltd.
