You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As we are consistently use tr() in our code (at least I think so) it shouldn't be to hard to do translation.
Actually that was one of my next "feature" ideas
The tool of choice to translate pure Qt applications (like sqlitebrowser) is Qt Linguist. As Rene said, the code is mostly ready for it, as it uses tr() to display strings. If possible I would like to stay away from Launchpad, as it is too specific to Ubuntu/Canonical. We had a lot of problems in the past in KDE, with Launchpad translations taking precedence over upstream ones in some cases.
As Rene and Mauricio already said, the application is basically ready for translations. I just fixed a minor bug in the code that loads the translation files (see commits 51be349 and dac1ed1). It now tries to load a translation according to the current locale settings of the user which I think is enough for now (and what the average user is expecting anyway).
The actual translation work is done by using lupdate to create a ts file which is then opened and edited in Qt Linguist. As a last step it needs to be converted to a qm file using qrelease. If this qm file is called something like 'tr_{locale}.qm' and is placed in the translations directory it'll be used automatically. I just started this process for a German translation but probably won't finish it (soon), this really is a lot of work 😒
Closing this, as translations are up and running (just need more of them).
Btw @VanDerSam is the Russian translation still completely in sync with all of our text strings? The project rename might mean some adjustment is needed. Unsure. 😉
Activity
rp- commentedon May 24, 2014
As we are consistently use tr() in our code (at least I think so) it shouldn't be to hard to do translation.
Actually that was one of my next "feature" ideas
piacentini commentedon May 24, 2014
The tool of choice to translate pure Qt applications (like sqlitebrowser) is Qt Linguist. As Rene said, the code is mostly ready for it, as it uses tr() to display strings. If possible I would like to stay away from Launchpad, as it is too specific to Ubuntu/Canonical. We had a lot of problems in the past in KDE, with Launchpad translations taking precedence over upstream ones in some cases.
MKleusberg commentedon May 24, 2014
As Rene and Mauricio already said, the application is basically ready for translations. I just fixed a minor bug in the code that loads the translation files (see commits 51be349 and dac1ed1). It now tries to load a translation according to the current locale settings of the user which I think is enough for now (and what the average user is expecting anyway).
The actual translation work is done by using lupdate to create a ts file which is then opened and edited in Qt Linguist. As a last step it needs to be converted to a qm file using qrelease. If this qm file is called something like 'tr_{locale}.qm' and is placed in the translations directory it'll be used automatically. I just started this process for a German translation but probably won't finish it (soon), this really is a lot of work 😒
justinclift commentedon May 24, 2014
Cool, not one of my crap ideas then. 😃
VanDerSam commentedon Jul 16, 2014
In issue #57 I made translation to Russian.
justinclift commentedon Jul 16, 2014
Thanks @VanDerSam, that's awesome. 😄
justinclift commentedon Sep 22, 2014
Closing this, as translations are up and running (just need more of them).
Btw @VanDerSam is the Russian translation still completely in sync with all of our text strings? The project rename might mean some adjustment is needed. Unsure. 😉