[Solved] translation doesn't work when executing application
-
wrote on 4 Dec 2013, 13:19 last edited by
I am using Qt linguist to translate my application (ui file and the rest of the code). Everything goes alright , the problem is all translations (in ui) work fine except an element added not from designer, here is my code to further explain :
@ tableWidget = new MyDropTableWidget(ui->verticalLayoutWidget_2);
if (tableWidget->columnCount() < 1)
tableWidget->setColumnCount(1);
tableWidget->setHorizontalHeaderItem(0, new QTableWidgetItem(tr("My non translated text")));
if (tableWidget->rowCount() < 21)
tableWidget->setRowCount(21);
...
ui->verticalLayout_2->addWidget(tableWidget);
...@in main file:
@QTranslator Translator ;
qDebug()<<"Translator->load( lang)"<< Translator.load(":/"+language);
app.installTranslator( &Translator );@in mainwindow constructor:
@ui->retranslateUi(this);@
all texts in ui are translated fine , only "My non translated text" was not. *.ts file are ok ("My non translated text" was detected and checked) , .qm file are well placed, I rebuild re lupdate re lrelease my application but in vain: when executing my application, all texts are translated expect "My non translated text" still in the source language.
Any help will be appreciated.
-
Hi and welcome to devnet,
Can you try the hello world translation example from the documentation ? Just to ensure that it's indeed the widget translation that is the problem
-
wrote on 10 Dec 2013, 09:13 last edited by
Hi, thanks for your reply , actually I found the issue reason, the translator was installed after MainWindow constructor call, so when the item is initialized the translator is not set yet, so I fixed it by calling the translation before creating tablewidget :)
-
Great !
Indeed, it must be done before anything else when using widgets. IIRC you can also have your own method that sets every text on your widget and that you call on reaction of QEvent::LanguageChanged.
Anyway, since you have it working now, please update the thread title prepending [solved] so other forum users may know a solution has been found :)
3/4