How to do dynamic translation in QML: Difference between revisions

From Qt Wiki
Jump to navigation Jump to search
No edit summary
 
m (Fixed formatting of the code samples by using <syntaxhighlight> instead of <code>)
 
(9 intermediate revisions by 5 users not shown)
Line 1: Line 1:
=Introduction=
{{LangSwitch}}
[[Category:HowTo]]
== Introduction ==


<span class="caps">QML</span> relies on the core internationalization capabilities provided by Qt. In the sections below we show how you can load and install the translators on the C++ side and set the needed translation on the <span class="caps">QML</span> side.
QML relies on the core internationalization capabilities provided by Qt. In the sections below we show how you can load and install the translators on the C++ side and set the needed translation on the QML side.


==What to do on the C++ side==
== What to do on the C++ side ==


The example below illustrates the necessary steps to get the dynamic translation to work. In the TranslationTest class we create a property:
The example below illustrates the necessary steps to get the dynamic translation to work. In the TranslationTest class we create a property:


that simply sets an empty string. This empty string is appended to the text in the <span class="caps">QML</span> code. This is a trick to get the whole expression to be reevaluated whenever the property emptyString changes. When not using this trick, QDeclarativeEngine will not know that it should reevaluate the text and do the translation. There is a suggestion in [https://bugreports.qt.nokia.com//browse/QTBUG-15602 Jira] ''[bugreports.qt.nokia.com]'' for for adding a more convenient way to know when the strings should be retranslated.
<code>Q_PROPERTY(QString emptyString READ getEmptyString NOTIFY languageChanged)</code>


The selectLanguage() function checks which language is currently being set and loads and installs the corresponding translation file accordingly. It then emits languageChanged(). All <span class="caps">QML</span> Text { } elements that use rootItem.emptyString in their text binding will receive a “NOTIFY” signal causing the qsTr(”….”) to be reevaluated using the new QTranslator. Because rootItem.emptyString is just “” (an empty string), it will alter the text in your <span class="caps">GUI</span>. This trick is based on the one suggested in the Jira report above and in [http://developer.qt.nokia.com/forums/viewthread/3307/P15 this thread] ''[developer.qt.nokia.com]''
that simply sets an empty string. This empty string is appended to the text in the QML code. This is a trick to get the whole expression to be reevaluated whenever the property emptyString changes. When not using this trick, QDeclarativeEngine will not know that it should reevaluate the text and do the translation. There is a suggestion for adding a more convenient way to know when the strings should be retranslated.


TranslationTest::selectLanguage() is callable from <span class="caps">QML</span> as it uses Q_INVOKABLE. To be able to call Qt class methods from <span class="caps">QML</span> code, the methods must be declared as public slots or conventional methods with the Q_INVOKABLE macro. In both cases, Qt methods are available to the Qt Meta-Object system and the methods are callable from <span class="caps">QML</span>.
The <tt>selectLanguage()</tt> function checks which language is currently being set, loads and installs the corresponding translation file accordingly. It then emits <tt>languageChanged()</tt>. All QML <tt>Text { }</tt> elements that use <tt>rootItem.emptyString</tt> in their text binding will receive a <tt>NOTIFY</tt> signal causing the <tt>qsTr("...")</tt> to be reevaluated using the new <tt>QTranslator</tt>. Because <tt>rootItem.emptyString</tt> is just "" (an empty string), it will alter the text in your GUI.


==<span class="caps">QML</span> implementation==
<tt>TranslationTest::selectLanguage()</tt> is callable from QML as it uses <tt>Q_INVOKABLE</tt>. To be able to call Qt class methods from QML code, the methods must be declared as public slots or conventional methods with the <tt>Q_INVOKABLE</tt> macro. In both cases, Qt methods are available to the Qt Meta-Object system and the methods are callable from QML.
 
<syntaxhighlight lang="cpp">
#include <QtGui>
#include <QtDeclarative>
 
class TranslationTest : public QObject
{
Q_OBJECT
Q_PROPERTY(QString emptyString READ getEmptyString NOTIFY languageChanged)
 
public:
  TranslationTest() {
  translator1 = new QTranslator(this);
  translator2 = new QTranslator(this);
  }
 
  QString getEmptyString() {
  return "";
  }
 
Q_INVOKABLE void selectLanguage(QString language) {
  if(language == QString("fr")) {
  translator1->load("t1_fr", ".");
  qApp->installTranslator(translator1);
  }
 
  if(language == QString("sp")) {
  translator2->load("t1_sp", ".");
  qApp->installTranslator(translator2);
  }
 
  if(language == QString("en")) {
  qApp->removeTranslator(translator1);
  qApp->removeTranslator(translator2);
  }
 
  emit languageChanged();
}
 
signals:
  void languageChanged();
 
private:
  QTranslator *translator1;
  QTranslator *translator2;
};
 
int main(int argc, char *argv[]) {
QApplication app(argc, argv);
TranslationTest myObj;
QDeclarativeView view;
view.rootContext()->setContextProperty("rootItem", (QObject*)&myObj);
view.setSource(QUrl::fromLocalFile("main.qml"));
view.show();
return app.exec();
}
 
#include "main.moc"
</syntaxhighlight>
 
== QML implementation ==


A convenient way to switch between languages is by using buttons, so we create a Button.qml component as follows:
A convenient way to switch between languages is by using buttons, so we create a Button.qml component as follows:
<syntaxhighlight language="qml">
import QtQuick 1.0
Rectangle {
id: root;
property string label;
signal clicked()
width: 120
height: 30
color: mouse.pressed ? "lightgray" : "white"
radius: 4
border.width: 1
border.color: "gray"
MouseArea {
  id: mouse
  anchors.fill: parent
  onClicked: root.clicked();
}
Text {
  anchors.centerIn: parent
  text: root.label
}
}
</syntaxhighlight>


Button.qml is then used in the main.qml file below to create 3 buttons that allow us to switch between English, French and Spanish. Each time a button is pressed, it causes the selectLanguage() of the C++ class to be called with the appropriate language string. This will then trigger the text to be reevaluated and hence translated.
Button.qml is then used in the main.qml file below to create 3 buttons that allow us to switch between English, French and Spanish. Each time a button is pressed, it causes the selectLanguage() of the C++ class to be called with the appropriate language string. This will then trigger the text to be reevaluated and hence translated.


==The project file==
<syntaxhighlight language="qml">
import QtQuick 1.0


In the .pro file we need to list the translation files under the [http://doc.qt.nokia.com/latest/qmake-variable-reference.html#translations <span class="caps">TRANSLATIONS</span>] ''[doc.qt.nokia.com]'' variable.
Rectangle {
width: 340; height: 150


==lupdate and lrelease==
Column {
  anchors.fill: parent; spacing: 20


We can now create the translation files by running [http://doc.qt.nokia.com/latest/linguist-manager.html#lupdate lupdate] ''[doc.qt.nokia.com]'' on the .qml file. lupdate will generate the first set of TS translation source files with all the user-visible text but no translations. In our example, we do:
  Text {
  text: qsTr("Hello") + rootItem.emptyString
  font.pointSize: 25; anchors.horizontalCenter: parent.horizontalCenter
  }
}
Row {
  anchors.verticalCenter: parent.verticalCenter
  Button { label: "English"; onClicked: rootItem.selectLanguage("en"); }
  Button { label: "Spanish"; onClicked: rootItem.selectLanguage("sp"); }
  Button { label: "French"; onClicked: rootItem.selectLanguage("fr"); }
}
}
</syntaxhighlight>


to create the translation files. These files can now be opened in [http://doc.qt.nokia.com/latest/linguist-manual.html Linguist] ''[doc.qt.nokia.com]'' and translated there. Finally, when the application is finished, you need to run [http://doc.qt.nokia.com/latest/linguist-manager.html#lrelease lrelease] ''[doc.qt.nokia.com]'' on the .ts files to read the .ts files and produce the .qm files used by the application at runtime. For example:
== The Project File ==


When running the example at this point, it should now switch between English, French and Spanish when clicking the respective buttons.
In the .pro file we need to list the translation files under the <tt>TRANSLATIONS</tt> variable.
 
<syntaxhighlight language="qmake">
TEMPLATE = app
TARGET =
INCLUDEPATH += .
 
# Input
SOURCES += main.cpp
QT+= declarative
TRANSLATIONS = t1_fr.ts t1_sp.ts
 
OTHER_FILES += Button.qml
</syntaxhighlight>
 
== lupdate and lrelease ==
 
We can now create the translation files by running <tt>lupdate</tt> on the <tt>.qml</tt> file. <tt>lupdate</tt> will generate the first set of TS translation source files with all the user-visible text but no translations. In our example, we do:


==Further reading==
# lupdate main.qml -ts t1_fr.ts t1_sp.ts


For further reading, see the [http://doc.qt.nokia.com/latest/qdeclarativei18n.html <span class="caps">QML</span> internationalization] ''[doc.qt.nokia.com]'' documentation, the [http://doc.qt.nokia.com/latest/declarative-i18n.html <span class="caps">QML</span> internationalization example] ''[doc.qt.nokia.com]'', the [http://doc.qt.nokia.com/latest/internationalization.html Qt internationalization documentation] ''[doc.qt.nokia.com]'' and the [http://developer.qt.nokia.com/wiki/QtInternationalization Qt Internationalization wiki] ''[developer.qt.nokia.com]''.
to create the translation files. These files can now be opened in Linguist and translated there. Finally, when the application is finished, you need to run <tt>lrelease</tt> on the <tt>.ts</tt> files to read the <tt>.ts</tt> files and produce the <tt>.qm</tt> files used by the application at runtime. For example:


===Categories:===
# lrelease t1_fr.ts
# lrelease t1_sp.ts


* [[:Category:Developing with Qt|Developing_with_Qt]]
When running the example at this point, it should now switch between English, French and Spanish when clicking the respective buttons.
** [[:Category:Developing with Qt::General|General]]
* [[:Category:HowTo|HowTo]]
* [[:Category:Tutorial|Tutorial]]

Latest revision as of 07:30, 9 May 2022

En Ar Bg De El Es Fa Fi Fr Hi Hu It Ja Kn Ko Ms Nl Pl Pt Ru Sq Th Tr Uk Zh

Introduction

QML relies on the core internationalization capabilities provided by Qt. In the sections below we show how you can load and install the translators on the C++ side and set the needed translation on the QML side.

What to do on the C++ side

The example below illustrates the necessary steps to get the dynamic translation to work. In the TranslationTest class we create a property:

Q_PROPERTY(QString emptyString READ getEmptyString NOTIFY languageChanged)

that simply sets an empty string. This empty string is appended to the text in the QML code. This is a trick to get the whole expression to be reevaluated whenever the property emptyString changes. When not using this trick, QDeclarativeEngine will not know that it should reevaluate the text and do the translation. There is a suggestion for adding a more convenient way to know when the strings should be retranslated.

The selectLanguage() function checks which language is currently being set, loads and installs the corresponding translation file accordingly. It then emits languageChanged(). All QML Text { } elements that use rootItem.emptyString in their text binding will receive a NOTIFY signal causing the qsTr("...") to be reevaluated using the new QTranslator. Because rootItem.emptyString is just "" (an empty string), it will alter the text in your GUI.

TranslationTest::selectLanguage() is callable from QML as it uses Q_INVOKABLE. To be able to call Qt class methods from QML code, the methods must be declared as public slots or conventional methods with the Q_INVOKABLE macro. In both cases, Qt methods are available to the Qt Meta-Object system and the methods are callable from QML.

#include <QtGui>
#include <QtDeclarative>

class TranslationTest : public QObject
{
 Q_OBJECT
 Q_PROPERTY(QString emptyString READ getEmptyString NOTIFY languageChanged)

 public:
  TranslationTest() {
   translator1 = new QTranslator(this);
   translator2 = new QTranslator(this);
  }

  QString getEmptyString() {
   return "";
  }

 Q_INVOKABLE void selectLanguage(QString language) {
  if(language == QString("fr")) {
   translator1->load("t1_fr", ".");
   qApp->installTranslator(translator1);
  }

  if(language == QString("sp")) {
   translator2->load("t1_sp", ".");
   qApp->installTranslator(translator2);
  }

  if(language == QString("en")) {
   qApp->removeTranslator(translator1);
   qApp->removeTranslator(translator2);
  }

  emit languageChanged();
 }

 signals:
  void languageChanged();

 private:
  QTranslator *translator1;
  QTranslator *translator2;
};

int main(int argc, char *argv[]) {
 QApplication app(argc, argv);
 TranslationTest myObj;
 QDeclarativeView view;
 view.rootContext()->setContextProperty("rootItem", (QObject*)&myObj);
 view.setSource(QUrl::fromLocalFile("main.qml"));
 view.show();
 return app.exec();
}

#include "main.moc"

QML implementation

A convenient way to switch between languages is by using buttons, so we create a Button.qml component as follows:

import QtQuick 1.0

Rectangle {
 id: root;
 property string label;

 signal clicked()

 width: 120
 height: 30
 color: mouse.pressed ? "lightgray" : "white"

 radius: 4
 border.width: 1
 border.color: "gray"

 MouseArea {
  id: mouse
  anchors.fill: parent
  onClicked: root.clicked();
 }

 Text {
  anchors.centerIn: parent
  text: root.label
 }
}

Button.qml is then used in the main.qml file below to create 3 buttons that allow us to switch between English, French and Spanish. Each time a button is pressed, it causes the selectLanguage() of the C++ class to be called with the appropriate language string. This will then trigger the text to be reevaluated and hence translated.

import QtQuick 1.0

Rectangle {
 width: 340; height: 150

 Column {
  anchors.fill: parent; spacing: 20

  Text {
   text: qsTr("Hello") + rootItem.emptyString
   font.pointSize: 25; anchors.horizontalCenter: parent.horizontalCenter
  }
 }
 
 Row {
  anchors.verticalCenter: parent.verticalCenter
  Button { label: "English"; onClicked: rootItem.selectLanguage("en"); }
  Button { label: "Spanish"; onClicked: rootItem.selectLanguage("sp"); }
  Button { label: "French"; onClicked: rootItem.selectLanguage("fr"); }
 }
}

The Project File

In the .pro file we need to list the translation files under the TRANSLATIONS variable.

TEMPLATE = app
TARGET =
INCLUDEPATH += .

# Input
SOURCES += main.cpp
QT+= declarative
TRANSLATIONS = t1_fr.ts t1_sp.ts

OTHER_FILES += Button.qml

lupdate and lrelease

We can now create the translation files by running lupdate on the .qml file. lupdate will generate the first set of TS translation source files with all the user-visible text but no translations. In our example, we do:

# lupdate main.qml -ts t1_fr.ts t1_sp.ts

to create the translation files. These files can now be opened in Linguist and translated there. Finally, when the application is finished, you need to run lrelease on the .ts files to read the .ts files and produce the .qm files used by the application at runtime. For example:

# lrelease t1_fr.ts
# lrelease t1_sp.ts

When running the example at this point, it should now switch between English, French and Spanish when clicking the respective buttons.