[Development] Configuring Qt VS Tools to auto generate .qm files from .ts files

[Miguel Costa]

We plan to revise the support for lupdate/lrelease in the Qt VS Tools as part of release 2.6 (end of August 2020). We'll add new property pages with settings for the Qt Linguist tools, including target paths for .ts and .qm files.

You can track progress by watching this issue: https://bugreports.qt.io/browse/QTVSADDINBUG-578
Please feel free to add any comments / suggestions.

Best regards,

--Miguel Costa
Software Engineer

The Qt Company GmbH
Erich-Thilo-Straße 10
D-12489 Berlin
http://qt.io
Geschäftsführer: Mika Pälsi,
Juha Varelius, Mika Harjuaho
Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B


________________________________
From: Development <development-bounces at qt-project.org> on behalf of David C. Partridge <david.partridge at perdrix.co.uk>
Sent: Wednesday, May 13, 2020 12:46 PM
To: development at qt-project.org <development at qt-project.org>
Subject: [Development] Configuring Qt VS Tools to auto generate .qm files from .ts files

I posted a question about this here:
<https://forum.qt.io/topic/114479/another-vs-tools-translation-question> and
was directed here when I didn't get an answer there.

I wanted Qt VS Tools to automatically build .ts files (ideally in a defined
location such as ".\GeneratedFiles\i18n").  What I can up with was much less
sophisticated.  I'd placed my .ts files in an i18n directory under my VS
project, and added a Custom Build step to be run before QTPrepare.

This simply did: cd i18n && for %%f in (*.ts) do
($(QtInstallDir)\bin\lrelease %%f)

I'm sure there must be a better way to achieve this, so my question is what
is the recommended way to do this,

Many thanks
David

_______________________________________________
Development mailing list
Development at qt-project.org
https://lists.qt-project.org/listinfo/development
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20200513/3b279e15/attachment-0001.html>