Translation | README file | Relevant methodology needed

[Ricky-Tigg]

version: 1.2.1; Tested on: Fedora; Kernel: v.5.14

$ rpm -ql scap-workbench | grep -E '.xml$|translation'
/usr/share/appdata/scap-workbench.appdata.xml
/usr/share/scap-workbench/translations/README
$ cat  /usr/share/scap-workbench/translations/README
Translations created using QtLinguist go into this folder.

Project: creation of translation file

Hello, This appdata.xml file is the unique installed file containing strings covering the texts exhibited in this application's interfaces. Therefore it is most likely to be the file against which a translation file would be created. Though in that README, as you can noticed it by yourself, a complete and up-to-date methodology to achieve a creation of such file is missing. In the meanwhile, is there any relevant information that would be worth a mention here?

[ggbecker]

I guess some additional work to the scap-workbench is needed to kick off the translation support. The program needs to be adapted to load different languages and translation files need to be created. Then an integration with the weblate (as mentioned before) can help with translations itself.

[Ricky-Tigg]

It sounds that adaptation would be a task where solely developers have power over if my interpretation is correct. I had figured out by investigating on Qt's side that it could be so.

[ggbecker]

#294 should get things started

[ggbecker]

Unfortunately there was no interest in the community to make things go forward with that pull request as it is not on the priority list.

I will check if someone can take a look at that to at least have the basis for translation support.