I removed most of the translation stuff from the code years ago.
In Qt translation works basically like this:
a. each text that should be ranslatable needs to be marked as such.
b. then a base translation file is created.
c. using qt linguist one can than translate this file into translation (ts) files for different languages. This also requires the .ui (user interface) design files.
d. the application would let the user select which translation to use.
One could do the translation without qt linguist. by editing the .ts file.
The .ts file is a simple xml file with messtage-elements like this.
a "location": the file where the text is in
a "source": the source text that gets translated
and the "translation", the new translated text.
Main annoyance with this is that the source-text also includes any formating:
so it's a bit of annoying.
For the fun of it I created a translation file for the current source code (which isn't properly prepared for this), so you can see what it looks like.
-> Translation Hybrid probably won't happen any time soon since it would require that I go through the whole code prepare it so at least the translation files get created properly and only strings that should be translated are inside the files.
Cu Selur
Ps.: iirc the old translation thread was in the old forum.selur.de forum years ago.
In Qt translation works basically like this:
a. each text that should be ranslatable needs to be marked as such.
b. then a base translation file is created.
c. using qt linguist one can than translate this file into translation (ts) files for different languages. This also requires the .ui (user interface) design files.
d. the application would let the user select which translation to use.
One could do the translation without qt linguist. by editing the .ts file.
The .ts file is a simple xml file with messtage-elements like this.
<message>
<location filename="Frontend/MainHelper/UI/AVStats.ui"/>
<source>AVStats</source>
<translation>A/V Statistik</translation>
</message>
a "source": the source text that gets translated
and the "translation", the new translated text.
Main annoyance with this is that the source-text also includes any formating:
<message>
<location filename="Frontend/MainHelper/UI/AVStats.ui"/>
<source><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/strict.dtd">
<html><head><meta name="qrichtext" content="1" /><style type="text/css">
p, li { white-space: pre-wrap; }
</style></head><body style=" ; font-weight:400; font-style:normal;">
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;"><span style=" font-weight:600; text-decoration: underline; ">Video:</span></p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;">This shows the video informations detected for the currently selected video stream.</p></body></html></source>
<translation type="unfinished"></translation>
</message>
For the fun of it I created a translation file for the current source code (which isn't properly prepared for this), so you can see what it looks like.
-> Translation Hybrid probably won't happen any time soon since it would require that I go through the whole code prepare it so at least the translation files get created properly and only strings that should be translated are inside the files.
Cu Selur
Ps.: iirc the old translation thread was in the old forum.selur.de forum years ago.
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.