What kind of text do you have that might be big enough to become a problem for your UI ?

@SGaist generation of qm files works if at first lupdate was run manually.
so the part of creation of ts files from
https://wiki.qt.io/Automating_generation_of_qm_files
doesn't work as expected

Hello,

That not the problem here.
If i understand correctly, the OSX Application Menu is translated by Qt, not my application.
The problem occurs only with QtQuick and on a OSX no-english.

So why i must do give a translated file created by me for QtQuick and not for QtWidgets ? (And not the translated files qt)

Regards,

nelbok

Another solution that not require hacking Qt is to alias QApplication::translate method:

inline QString myTr(const char* context, const char* key, const char* disambiguation = 0, int n = -1) { return QApplication::translate(context, key, disambiguation, n); }

and then get translated text with:

myTr("QShortcut", "Help");

Such texts are invisible for lupdate.

Hi and welcome to devnet,

Do you mean that if you use the qt_fr.qm file everything is going well but if you add your own translation it starts acting up ?ä

i cant share that, why its a private one, i just need to how to change this Qt_tr_noop to tr, and not include inside static i just want to use the tr().