Localisation update, Thorium 3.1

[gautierchomel]

Dear contributors, Thorium 3.1 will be released around early february 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.

[jonaslil]

Thanks for the update @gautierchomel. I noticed that the original post mentions a release date of January 20th for Thorium 3.1, but since this issue was opened on January 31st, that date doesn’t seem to be correct. Could you clarify?

[gautierchomel]

Thanks for pointing out that error, @jonaslil. I corrected the initial comment.
We don't have a release date, as some consistency checks still have to be done. It should not happen before one week.

[milliet]

Hi Gauthier, I'll be dealing with it tomorrow. Best, Pedro Em seg., 3 de fev. de 2025, 05:42, Gautier Chomel ***@***.***> escreveu:

…

Thanks for pointing out that error, @jonaslil <https://github.com/jonaslil>. I corrected the initial comment. We don't have a release date, as some consistency checks still have to be done. It should not happen before one week. — Reply to this email directly, view it on GitHub <#2759 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AALE6OS3V7MS77DA42ZKTRL2N4TXVAVCNFSM6AAAAABWH6WRVKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMZQGI4TQOBZHA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[milliet]

Hi Gautier, I couldn't login to GitLocalize. When I get the page from the link you've sent, and try to login, it gives me a 500 error message. Any ideas? best Pedro Em seg., 3 de fev. de 2025 às 08:16, Pedro Milliet ***@***.***> escreveu:

…

Hi Gauthier, I'll be dealing with it tomorrow. Best, Pedro Em seg., 3 de fev. de 2025, 05:42, Gautier Chomel < ***@***.***> escreveu: > Thanks for pointing out that error, @jonaslil > <https://github.com/jonaslil>. I corrected the initial comment. > We don't have a release date, as some consistency checks still have to be > done. It should not happen before one week. > > — > Reply to this email directly, view it on GitHub > <#2759 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AALE6OS3V7MS77DA42ZKTRL2N4TXVAVCNFSM6AAAAABWH6WRVKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMZQGI4TQOBZHA> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> >

[gautierchomel]

@milliet it happens often, but in my case, despite the error 500 message, I am logged and I can access the project thru the upper right menu where my profile image appears.

[danielweck]

GitLocalize is going downhill, unfortunately.
Quite unreliable in recent months.
(probably not a high-priority / business-critical operation for the owner company https://alconost.com )

Possible alternatives?

https://weblate.org/en-gb/features/

https://crowdin.com/features

[gautierchomel]

I agree we should reopen #1779 discussion

[danielweck]

I have just used Weblate for the first time:
#2771

See:
https://hosted.weblate.org/projects/thorium-reader-documentation/thorium-reader-translation/

[milliet]

I'll try it Em seg., 3 de fev. de 2025, 14:00, Gautier Chomel ***@***.***> escreveu:

…

@milliet <https://github.com/milliet> it happens often, but in my case, despite the error 500 message, I am logged and I can access the project thru the upper right menu where my profile image appears. — Reply to this email directly, view it on GitHub <#2759 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AALE6OUFQZBXSCCNZMAH6TT2N6OCNAVCNFSM6AAAAABWH6WRVKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMZRGU3DGMZXHE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[danielweck]

Weblate translations are now up to date both ways (no pending changes in Weblate Git fork to be pushed to a Thorium PR, and no recent changes in Thorium's upstream develop branch to be synchronized back into Weblate).

https://hosted.weblate.org/projects/thorium-reader-documentation/thorium-reader-translation/

I updated the JSON format to match the 4-spaces indentation convention of Weblate, which was Thorium's too before Gitlocalize broke this by forcing 2-spaces. Unfortunately this means that we will have to manually edit JSON data coming from Gitlocalize but this is an acceptable tradeoff given that Gitlocalize has been very buggy (we should recommend Weblate from now on).

The Weblate website user and admin interface is not as user-friendly / simple, because the feature-set is more sophisticated (even for developers / project maintainers). However the Git-focussed workflow means that we can fix problems, and the learning curve for basic operations is not too steep (many features can simply be ignored while updating translations).

[tedvandertogt]

Hi Daniel, I did my best to complete the Dutch translation of Thorium. Almost done, but have doubt on some wordings as I do not always have the context in which terms are used. Would love to have these checked by a colleague at KB who is better in translation, but he or she will also need context. Is there already a beta version to look at? Or do you have any other suggestion on how to tackle this? Kind regards, Ted Van: Daniel Weck ***@***.***> Verzonden: donderdag 6 februari 2025 18:18 Aan: edrlab/thorium-reader ***@***.***> CC: Ted van der Togt ***@***.***>; Mention ***@***.***> Onderwerp: Re: [edrlab/thorium-reader] Localisation update, Thorium 3.1 (Issue #2759) Weblate translations are now up to date both ways (no pending changes in Weblate Git fork to be pushed to a Thorium PR, and no recent changes in Thorium's upstream develop branch to be synchronized back into Weblate). https://hosted.weblate.org/projects/thorium-reader-documentation/thorium-reader-translation/ I updated the JSON format to match the 4-spaces indentation convention of Weblate, which was Thorium's too before Gitlocalize broke this by forcing 2-spaces. Unfortunately this means that we will have to manually edit JSON data coming from Gitlocalize but this is an acceptable tradeoff given that Gitlocalize has been very buggy (we should recommend Weblate from now on). The Weblate web user interface is not as user-friendly / simple, because the feature-set is more sophisticated (even for developers / project maintainers). However the Git-focussed workflow means that we can fix problems, and the learning curve for basic operations is not too steep (many features can simply be ignored while updating translations). - Reply to this email directly, view it on GitHub<#2759 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AQHKIDVX2IN6S723KLOKYUT2OOKM3AVCNFSM6AAAAABWH6WRVKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNBQGUYTKNJWGI>. You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>

[danielweck]

Hello Ted,
Thorium is built automatically from this Git repository's develop branch, which is where the latest code and translations are published. Make sure to pick the appropriate operating system / architecture from the "releases" page:
https://github.com/edrlab/thorium-reader/releases

[danielweck]

Or do you have any other suggestion on how to tackle this?

Hi Ted, @gautierchomel started documenting the GUI / translated labels. Also, I think that Weblate (the localization tool we are currently trialing) offers a feature to help translators find their way around the application's user interface.