Thanks for your interest in improving our translations! This document provides details on how to contribute to a translation. This document assumes you can run commandline tools, know how to switch languages within Logseq and basic Clojurescript familiarity. We use tongue, a most excellent library, for our translations.
In order to run the commands in this doc, you will need to install Babashka.
Language translations are under,
src/resources/dicts/ with each language having its own file. For example, the es locale is in es.edn.
First, let's get an overview of Logseq's languages and how many translations your language has compared to others:
$ bb lang:list
| :locale | :percent-translated | :translation-count | :language |
|----------+---------------------+--------------------+------------------------|
| :es | 100 | 492 | Español |
| :tr | 100 | 492 | Türkçe |
| :en | 100 | 492 | English |
| :uk | 95 | 466 | Українська |
| :ru | 95 | 466 | Русский |
| :ko | 93 | 459 | 한국어 |
| :de | 93 | 459 | Deutsch |
| :fr | 92 | 453 | Français |
| :pt-PT | 92 | 453 | Português (Europeu) |
| :pt-BR | 92 | 451 | Português (Brasileiro) |
| :sk | 90 | 445 | Slovenčina |
| :zh-CN | 90 | 441 | 简体中文 |
| :nb-NO | 75 | 370 | Norsk (bokmål) |
| :ja | 75 | 368 | 日本語 |
| :pl | 72 | 353 | Polski |
| :nl | 72 | 353 | Dutch (Nederlands) |
| :zh-Hant | 71 | 349 | 繁體中文 |
| :it | 71 | 349 | Italiano |
| :af | 22 | 106 | Afrikaans |
Total: 19Let's try to get your language translated as close to 100% as you can!
To see what translations are missing for your language, let's run a command using es as the example language:
$ bb lang:missing es
| :translation-key | :string-to-translate | :file |
|---------------------------------------+-------------------------------------------------------+---------------|
| :command.editor/toggle-number-list | Toggle number list | dicts/es.edn |
| :command.whiteboard/bring-forward | Move forward | dicts/es.edn |
| :command.whiteboard/bring-to-front | Move to front | dicts/es.edn |
...Now, manually, add keys for your language to the translation files, save and rerun the above command. Over time you're aiming to have this list drop to zero. Since this process can be tedious, there is an option to print the untranslated strings to copy and paste them to the files:
# When pasting this content, be sure to update the indentation to match the file
$ bb lang:missing es --copy
;; For dicts/es.edn
:command.editor/toggle-number-list "Toggle number list"
:command.whiteboard/bring-forward "Move forward"
:command.whiteboard/bring-to-front "Move to front"
...Almost all translations are small. The only exceptions to this are the keys :tutorial/text and :tutorial/dummy-notes. These translations are files that are part of the onboarding tutorial and can be found under src/resources/tutorials/.
- Some translations may include punctuation like
:or!. When translating them, please use the punctuation that makes the most sense for your language as you don't have to follow the English ones. - Some translations may include arguments/interpolations e.g.
{1}. If you see them in a translation, be sure to include them. These arguments are substituted in the string and are usually used for something the app needs to calculate e.g. a number. See these docs for more examples. - Rarely, a translation is a function that calls code and look like
(fn ... )- The logic for these fns must be simple and can only use the following fns:
str,when,ifand=. - These fn translations are usually used to handle pluralization or handle formatted text by returning hiccup-style HTML. For example, a hiccup style translation would look like
(fn [] [:div "FOO"]). See:on-boarding/main-titlefor more examples.
- The logic for these fns must be simple and can only use the following fns:
There is a lint command to catch common translation mistakes - bb lang:validate-translations. This runs for all contribution pull requests so
you'll need to ensure it doesn't fail. Mistakes that it catches:
- Adding translation entries for nonexistent entries in English.
- Most common mistake is mistyping an entry name
- Adding English entries for translations that don't exist in the UI.
- Adding translation entries that are just duplicates of the English entry.
- This catches contributors copying entries from English and then forgetting to translate. Sometimes you do want to have the translation be the same. For this case, add an entry to
allowed-duplicatesin lang.clj for your language with a list of duplicated entries e.g.:nb-NO #{:port ...}.
- This catches contributors copying entries from English and then forgetting to translate. Sometimes you do want to have the translation be the same. For this case, add an entry to
To add a new language:
- Add an entry to
frontend.dicts/languages - Create a new file under
src/resources/dicts/and name the file the same as the locale e.g. zz.edn for a hypothetical zz locale. - Add an entry in
frontend.dicts/dictsreferencing the file you created. - Then start translating for your language and adding entries in your language's EDN file using the
bb lang:missingworkflow.