Qt Linguist: Open several ts files from command line
-
Hi,
our projects are divided in many subprojects. That is, we have one parent pro file referring to several child pro files.
When we run lupdate on the parent pro file, we get several ts files.
One of our use cases is to search translations keys or translations in all these ts files when a bad or missing translation is detected in the GUI. The problem is, that we have really many ts files and when I open many ts files with Qt Linguist, I get the warning, that the to be opened ts files are not related and if I really want to open them. I get this warning for every ts file!
My question is, if it is possible to open all ts files by command line with the option to surpress the warning.Thanks in advance!
Stefano
-
Hi and welcome to devnet,
A quick look at linguist's code doesn't show any flag/option to avoid that message. You can try to open a feature request for that.
-
Thanks for your reply. Unfortunately, the developer didn't take us seriously.
And because we assume he would resign patches from us, we are forced to develop a custom tool with our needs. -
If by patches you mean implement multi-document support in Assistant then I don't think it will be blocked.
-
Hi,
our projects are divided in many subprojects. That is, we have one parent pro file referring to several child pro files.
When we run lupdate on the parent pro file, we get several ts files.
One of our use cases is to search translations keys or translations in all these ts files when a bad or missing translation is detected in the GUI. The problem is, that we have really many ts files and when I open many ts files with Qt Linguist, I get the warning, that the to be opened ts files are not related and if I really want to open them. I get this warning for every ts file!
My question is, if it is possible to open all ts files by command line with the option to surpress the warning.Thanks in advance!
Stefano
@StefanoD
Hello,
It's not a good answer, but you could open the *.ts files with any text editor of choice (they're XML) and do the searching/modification by hand. Granted, it's not the most convenient way but should work.Kind regards.
-
@kshegunov : Thx, but this was meant only to be the first step for more features, like batch translations of multiple ts files. We would have implemented them ourselves, if we could really be sure, the patches would be accepted.
@StefanoD
Fair enough. I'd then file a multi-document feature request for Linguist, as this seems to be the main reasoning of the developer for rejecting your suggestion, and if it's "accepted" I'd start implementing the needed changes. -
I'll give it a try.
