Localisation update, Thorium 3.1

[gautierchomel]

Dear contributors, Thorium 3.1 will be released around January 20th. It comes with some significant localisations news listed here:

• The new version proposes a significant feature addition: the ability to export and import annotation files, including identification for such annotations (title, author, version) and related success, warning and error messages. That represents nearly 20% of new vocabulary to localise. This is the priority work. Check it from GitLocalize.
• We are happy to provide a new helper: the localisation context table to allow you to understand better and visualise the texts to localise. There’s room for improvement; let us know what we can do better through the thorium reader doc issue tracker

Information and discussions about localisation and language translation process can be found in the [Thorium wiki l10n dedicated page](https://github.com/edrlab/thorium-reader/wiki/Localization-(l10n)-language-translations).

Actual known contributors are :

@horus68, @milliet, @martinpub, @Modeo147, @naglis, @jacoporinaldi, @peaceroad, @cary-rowen, @nvdaes, @tofi86, @terhol-celia, @maitreya2019, @ThanatosDi, @georgegach, @sukiletxe, @salah1974, @Adecabo9, @ddfreiling, @izorba, @MiiaKirsi, @KirsiYl, @gregoriopellegrino, @tedvandertogt, @xFizox, @jonaslil, @catdotjs

Post Scriptum:
The Thorium documentation EPUB and the Thorium landing and support page are now available for localisation from its dedicated Gitlocalize address: https://gitlocalize.com/repo/9230. We are still refining the workflow, so please keep in touch with us if you'd like to get involved in that work. The preferred place for discussion is the [thorium reader doc issue tracker](https://github.com/edrlab/thorium-reader-doc/issues).

[nvdaes]

@gautierchomel , when I try to open the webpage for spanish translation, it's not opened and the browser goes to the gitlocalize webpage. I've tried to use the provided link for spanish in the table where translators and languages are reflected, and also pasting this address in the browser:

https://gitlocalize.com/repo/9626/es

Thanks for any help.

[gautierchomel]

@nvdaes, here is a direct link: https://gitlocalize.com/repo/9626/es/src/resources/locales/en.json

[nvdaes]

@gautierchomel , unfortunately Iget the same result: different browsers seem to go to the gitlocalize homepage. I've tested with Firefox, Chrome and Edge.

[gautierchomel]

Ok, i got the same behavior when i am not logged into gitlocalise. Can you try login and then activate the link ?

[nvdaes]

@gautierchomel , for any reason, links labelled as sign with GitHub or Get Start with GitHub don't work at all.

[nvdaes]

Sometimes I'm able to sign in with GitHub authorizing the getLocalize app, but when I try to open links to translate Thorium, the browser goes to the homepage of Gitlocalize.
Hope this can be fixed.

[gautierchomel]

Looks like we really need to find a stronger localisation tool.
For now, the alternative is to directly edit the json at https://github.com/edrlab/thorium-reader/blob/develop/src%2Fresources%2Flocales%2Fes.json

By Monday i can make a list of added or changes values to make it easier.

[nvdaes]

@gautierchomel , I've created PR #2764 .
I've redirected git diff v3.0.0..HEAD source/resources/locales/es.json to a text file to have an idea about changes, and I've searched in the localization context table these changes to make the translation.
There are more strings to translate, but I have translated just those reflected in the context table to avoid mistakes.
Feel free to review my PR, and if I can help translating the documentation let me know, in case there is a good workflow to do it, since translate markdown files is hard.