Line 52:
Line 52:
It provides what I presume is the usual opportunities for manual and automatic language translation, and has a project / component structure.
It provides what I presume is the usual opportunities for manual and automatic language translation, and has a project / component structure.
−
It provides a number of different formats for input of the text to be translated, but not ".lex" files. I have written a python program to convert them to .po files which are well supported.
+
It provides a number of different formats for input of the text to be translated, but not ".lex" files.
+
+
I have written a python program to convert them to .po files which are well supported. The program is here: https://src.koozali.org/brianr/Lex2Po
Weblate can interact directly with the Gitea/git VCS and uses its own git VCS to hold the local files. It can write any changes back to the remote VCS and/or (for Gitea) write it as a pull reqauest. allowing some oversight before changes are applied. I've not got this to work yet, due almost certainly to my own lack of real understanding of certificates and public/private keys and tokens. It can read the data from Gitea with no problem, and can create the translation components needed semi-automatically.
Weblate can interact directly with the Gitea/git VCS and uses its own git VCS to hold the local files. It can write any changes back to the remote VCS and/or (for Gitea) write it as a pull reqauest. allowing some oversight before changes are applied. I've not got this to work yet, due almost certainly to my own lack of real understanding of certificates and public/private keys and tokens. It can read the data from Gitea with no problem, and can create the translation components needed semi-automatically.