Ok, there is a concurrent between two things: the automatical way (with static value) and the programatic way.

I propose that you add a function:

Of course to each time you need a contextual handling of the translation reimplement this function:

And of course empty the label to avoid an unnecessary double set of the value.

I forget to bind it …

But how should this change the fact that I don’t get the translation from my .qm file?

I’m confused…

I’m using myself a similar mechanism, the tr() will use the values of your new loaded dictionary.

The values not set in designer will simply not appear in the retranslateUI(), you should simply clear the content of your label in the designer and use alternatively the translationChanged() to handle the non-static cases.

Clearing the content of my label in the designer does not change anything it seems… The label just becomes empty when when trying to change language.

Also, I’m sure what the translationChanged() function does? Doesn’t it just overwrite whatever is in the label with “loaded” or “empty”?

Your code works perfectly, if you put in designer Textlabel as ‘text’ entry, the retranslatedUI() will simply find the equivalent in the string map (of your translator) and replace it and if none found he reset to the original value.

Which means probably: it’s missing the translation of your text?

Oh but the label has dynamic content.

The text is set when I create an instance of my ui. It takes a parameter called “title”. It’s this variable which should be translated and showed in the label.

move this code from the c’tr to the ‘famous’ routine:

void translationChanged() { mylabel->setText(tr(“title”)); }

what you dream is that Qt detects the ‘title’ with something like:

Now remarks:

• how he could find the translation if the text() is chinese?
• how you will untranslate text like: tr(“It will reboot in %1, please save your work!”).arg(time) ?

I want to translate my gui to danish. My default language is english.
I expect that Qt looks up my title (“Main menu”) i my “dan.qm” file, and exchange it with the danish equivalent (“Hovedmenu”).

When creating my screen/ui object, I do this:

The first parameter is the title.

This all should be done in 3 parts:

a) Application

b) make automatical response to LanguageChange message

C) Now the goal is to make all this simplier, because of course it’s not confortable to have to create manually for each widget all the routine. An idea is to inherit your own interface that you construct too in the constructor, this interface could install an event filter, here my quick and dirty and fast solution, not simply copy, check more the ideas:

Thanks a lot for your replies BilbonSacquet.

I’m afraid I’m rather thickheaded…

You make me very confused. In your previous post – the goal for me is to make it like shown in c), right? a) and b) are what? Just to show the difference?

So in c) you tell me that all my screen widgets, should inherit from this MyTranslation interface? And why inherit from Ui::MyWidget? I just don’t get it.

And what about the EventFilter – what is that for?

My brain is soon gonna pop out of my skull.

Can you, or anyone else, explain it to me in other words? Or just spell it out more.

I’m sorry :(

But thank you so much for your time!

ok, I go perhaps too fast, I’m stressed right now with work and I will to help the directest way possible. But that’s my bad.

That’s true a) b) is just to explain the steps … and c) the solution.

Yes, all widget which needs translation should inherits this class, that’s necessary to take the message QEvent::LanguageChange and to make ‘automatically’ callback the translation functions. The event filter is necessary because the template MyTranslation doesn’t inherit of the widget (it’s just an QObject) function like event().

The message LanguageChange cycle is now:
app -> MyWidget::event() -> MyTranslator::eventFilter() -> MyWidget::Ui::MyWidget::retranslateUI() , MyWidget::translationChanged()
(if the function is redefined otherwise MyTranslator::translationChanged())

Now why I inherits from Ui::MyClass, you will get the information from the Qt help. But mainly it makes all simplier in the handle of your widgets: same interface, you have all your children direct, you could use the on_mywidget_signal() slots without to connect/disconnct anything.
What I need is that all the widget has the function retranslateUi() accessible in the interface to be called by the template.

I hope that I have helped you with the explanation and not make all darker like in the Morian mines :D

Okay I’m trying to work my way through it.

I’m writing the MyTranslation class now, but I get some errors:

Do I need to include something in order to do this?

Now I have verified/compiled the prototype given, I had done an error m_t->retranslateUi(his m_t);

Translation template – MyTranslator.h:

The widget – MyWidget.h:

The MyWidget.cpp:

And of course you need a MyWidget.ui with class MyWidget :) use the default widget. To make it faster I integrate on my current project, and redo a adapted copy/paste. It could have typos but should be ok now.