Want to collaborate?

• 1: Translating
• 2: Your help is precious
• 3: Stuck?
• 4: Contribute!

1 - Translating

Thorium Reader user Interface localisation are provided and maintained thanks to volunteers and contributing organisations.

All locales are stored in the sources resources locales folder.

To add a translation, you can start from the English “en.json”, rename it as and change the values after the colon punctuation (:).

If you are comfortable with github you can open a pull request to submit the file.

Otherwise you can just send us the localised file by email and we’ll proceed to the addition. A list of contributors is maintained on the wiki page Localization (l10n) language translation.

Be aware that we are currently reworking the user interface, so important changes may happen by the first quarter of 2024. We usually alert localisation contributors before any release so they can update the translation file. Also, mentioning that the thorium documentation website can be localised thru similar contribution methodology. ](../900_about)

2 - Your help is precious

You too can help Thorium Reader become the best reading application reading application by becoming a member of EDRLab. Or by making a donation to the EDRLab via the Github sponsorship "piggy-bank", which accepts small monthly donations.

Thorium is built by its community. If you want to participate, please contact us !

You can also:

• Report an error or suggest a change by opening an Issue in our [support tracking tool](https://github.com/edrlab/thorium-reader-doc/issues/new).
• Participate in the translation of resources.

3 - Stuck?

If you do not find the answer to your problem on this site, you can tell us your problem via our support tracking tool or contact form.

Here is the information we need:

• Operating system and it version
• Thorium version (it is indicated at the bottom of the library under the title About Thorium)

4 - Contribute!

Thorium and its documentation are developed thanks to the user community. We need help to translate this documentation.

To do so, you can contact us.

If you are comfortable enough with GitHub and the Markdown format you can propose a new translation via a Pull Request.

To do this: clone the repository and create a branch with the name of the language you want to add, make a copy of the content.en folder and rename it with two letters corresponding to the language you want to add (for example content.es will contain the Spanish translation). The names of the files must not be changed as they insure correspondence between languages.

The i18n folder contains the translations for the fixed elements of the header and footer. Several languages are already present, if your language is not present, copy paste the .yaml file and rename it with the first two letters of the letters of the language you want to add.

Finally to activate the menu of the language you add, edit the file config.toml and add the language with the following code:

[languages.en]
  languageName = 'English'
  contentDir = 'content.en'
  weight = 1

You must replace .en' with the first two letters of the language you are adding and fill in the name of the language as the languageNamevalue. Theweight` indicates the order of appearance in the language menu.

Example for Spanish :

[languages.es]
  languageName = 'Español'
  contentDir = 'content.es'
  weight = 3

Localized images such as screenshots should be added to the folder statics/images/local-(two letter language).