/usr/share/qt5/doc/qtdoc/qtquick-internationalization.html is in qt5-doc-html 5.2.1-1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 | <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en_US" lang="en_US">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<!-- internationalization.qdoc -->
<title>Internationalization and Localization with Qt Quick | QtDoc 5.2</title>
<link rel="stylesheet" type="text/css" href="style/offline.css" />
</head>
<body>
<div class="header" id="qtdocheader">
<div class="main">
<div class="main-rounded">
<div class="navigationbar">
<ul>
<li><a href="index.html">Qt 5.2</a></li>
<li>Internationalization and Localization with Qt Quick</li>
<li id="buildversion">
Qt 5.2.1 Reference Documentation</li>
</ul>
</div>
</div>
<div class="content">
<div class="line">
<div class="content mainContent">
<div class="toc">
<h3><a name="toc">Contents</a></h3>
<ul>
<li class="level1"><a href="#internationalizing-your-application">Internationalizing your Application</a></li>
<li class="level2"><a href="#1-use-qstr-for-all-literal-user-interface-strings">1. Use qsTr() for all Literal User Interface Strings</a></li>
<li class="level2"><a href="#2-add-context-for-the-translator">2. Add Context for the Translator</a></li>
<li class="level2"><a href="#3-disambiguate-identical-texts">3. Disambiguate Identical Texts</a></li>
<li class="level2"><a href="#4-use-op-op-x-to-insert-parameters-into-a-string">4. Use <tt>%x</tt> to Insert Parameters into a String</a></li>
<li class="level2"><a href="#5-use-lx-so-numbers-are-localized">5. Use %Lx so Numbers are Localized</a></li>
<li class="level2"><a href="#6-internationalize-dates-times-and-currencies">6. Internationalize Dates, Times and Currencies</a></li>
<li class="level2"><a href="#7-use-qt-tr-noop-for-translatable-data-text-strings">7. Use QT_TR_NOOP() for Translatable Data Text Strings</a></li>
<li class="level2"><a href="#8-use-locale-to-extend-localization-features">8. Use Locale to Extend Localization Features</a></li>
<li class="level1"><a href="#localizing-your-application">Localizing your Application</a></li>
<li class="level2"><a href="#use-a-conditional-to-hide-qml-source-from-the-compiler">Use a Conditional to Hide QML Source From the Compiler</a></li>
</ul>
</div>
<h1 class="title">Internationalization and Localization with Qt Quick</h1>
<span class="subtitle"></span>
<!-- $$$qtquick-internationalization.html-description -->
<div class="descr"> <a name="details"></a>
<a name="internationalizing-your-application"></a>
<h2>Internationalizing your Application</h2>
<p>The following sections describe various aspects of internationalizing your QML source code. If you follow these guides for all the user interface components in your application, it becomes possible to localize every aspect of your application for different languages and local cultural conventions such as the way dates and numbers are formatted.</p>
<a name="1-use-qstr-for-all-literal-user-interface-strings"></a>
<h3>1. Use qsTr() for all Literal User Interface Strings</h3>
<p>Strings in QML can be marked for translation using the qsTr(), qsTranslate(), qsTrId(), <a href="../qtcore/qtglobal.html#QT_TR_NOOP">QT_TR_NOOP</a>(), <a href="../qtcore/qtglobal.html#QT_TRANSLATE_NOOP">QT_TRANSLATE_NOOP</a>(), and <a href="../qtcore/qtglobal.html#QT_TRID_NOOP">QT_TRID_NOOP</a>() functions. The most common way of marking strings is with the qsTr() function. For example:</p>
<pre class="cpp">Text {
id: txt1;
text: qsTr(<span class="string">"Back"</span>);
}</pre>
<p>This code makes "Back" a key entry in the translation files. At runtime, the translation system looks up the keyword "Back" and then gets the corresponding translation value for the current system locale. The result is returned to the <tt>text</tt> property and the user interface will show the appropriate translation of "Back" for the current locale.</p>
<a name="2-add-context-for-the-translator"></a>
<h3>2. Add Context for the Translator</h3>
<p>User interface strings are often short so you need to help the person translating the text understand the context of the text. You can add context information in the source code as extra descriptive text before the string to be translated. These extra descriptions are included in the .ts translation files delivered to the translator.</p>
<p><b>Note: </b>The .ts files are XML files with the source texts and a place for the translated text. The updated .ts files are converted into binary translation files and included as part of the final application.</p><p>In the following code snippet, the text on the <tt>//:</tt> line is the main comment for the translator.</p>
<p>The text on the <tt>//~</tt> line is optional extra information. The first word of the text is used as an additional identifier in the XML element in the .ts file so make sure the first word is not part of the sentence. For example, the comment "Context Not related to that" is converted to "<extra-Context>Not related to that" in the .ts file.</p>
<pre class="cpp">Text {
id: txt1;
<span class="comment">// This user interface string is only used here</span>
<span class="comment">//: The back of the object, not the front</span>
<span class="comment">//~ Context Not related to back-stepping</span>
text: qsTr(<span class="string">"Back"</span>);
}</pre>
<a name="3-disambiguate-identical-texts"></a>
<h3>3. Disambiguate Identical Texts</h3>
<p>The translation system consolidates the user interface text strings into unique items. This consolidation saves the person doing the translation work having to translate the same text multiple times. However, in some cases, the text is identical but has a different meaning. For example, in English, "back" means take a step backward and also means the part of an object opposite to the front. You need to tell the translation system about these two separate meanings so the translator can create two separate translations.</p>
<p>Differentiate between identical texts by adding some id text as the second parameter of the qsTr() function.</p>
<p>In the following code snippet, the <tt>not front</tt> text is an id to differentiate this "Back" text from the backstepping "Back" text:</p>
<pre class="cpp">Text {
id: txt1;
<span class="comment">// This user interface string is used only here</span>
<span class="comment">//: The back of the object, not the front</span>
<span class="comment">//~ Context Not related to back-stepping</span>
text: qsTr(<span class="string">"Back"</span><span class="operator">,</span> <span class="string">"not front"</span>);
}</pre>
<a name="4-use-op-op-x-to-insert-parameters-into-a-string"></a>
<h3>4. Use <tt>%x</tt> to Insert Parameters into a String</h3>
<p>Different languages put words together in different orders so it is not a good idea to create sentences by concatenating words and data. Instead, use <tt>%</tt> to insert parameters into strings. For example, the following snippet has a string with two number parameters <tt>%1</tt> and <tt>%2</tt>. These parameters are inserted with the <tt>.arg()</tt> functions.</p>
<pre class="cpp">Text {
text: qsTr(<span class="string">"File %1 of %2"</span>)<span class="operator">.</span>arg(counter)<span class="operator">.</span>arg(total)
}</pre>
<p>%1 refers to the first parameter and <tt>%2</tt> refers to the second parameter so this code produces output like: "File 2 of 3".</p>
<a name="5-use-lx-so-numbers-are-localized"></a>
<h3>5. Use %Lx so Numbers are Localized</h3>
<p>If you include the <tt>%L</tt> modifier when you specify a parameter, the number is localized according to the current regional settings. For example, in the following code snippet, <tt>%L1</tt> means to format the first parameters according to the number formatting conventions of the currently selected locale (geographical region):</p>
<pre class="cpp">Text {
text: qsTr(<span class="string">"%L1"</span>)<span class="operator">.</span>arg(total)
}</pre>
<p>Then, with the above code, if <tt>total</tt> is the number "4321.56" (four thousand three hundred and twenty one point fifty six); with English regional settings, (locale) the output is "4,321.56"; with German regional settings, the output is "4.321,56".</p>
<a name="6-internationalize-dates-times-and-currencies"></a>
<h3>6. Internationalize Dates, Times and Currencies</h3>
<p>There are no special in-string modifiers for formatting dates and times. Instead, you need to query the current locale (geographical region) and use the methods of Date to format the string.</p>
<p><tt>Qt.locale()</tt> returns a Locale object which contains all kinds of information about the locale. In particular, the Locale.name property contains the language and country information for the current locale. You can use the value as is, or you can parse it to determine the appropriate content for the current locale.</p>
<p>The following snippet gets the current date and time with <a href="../qtqml/qml-date.html">Date</a>(), then converts that to a string for the current locale. Then it inserts the date string into the %1 parameter for the appropriate translation.</p>
<pre class="cpp">Text {
text: qsTr(<span class="string">"Date %1"</span>)<span class="operator">.</span>arg(Date()<span class="operator">.</span>toLocaleString(<span class="type"><a href="../qtcore/qt.html">Qt</a></span><span class="operator">.</span>locale()))
}</pre>
<p>To make sure currency numbers are localized, use the Number type. This type has similar functions as the Date type for converting numbers into localized currency strings.</p>
<a name="7-use-qt-tr-noop-for-translatable-data-text-strings"></a>
<h3>7. Use QT_TR_NOOP() for Translatable Data Text Strings</h3>
<p>If the user changes the system language without a reboot, depending on the system, the strings in arrays and list models and other data structures might not be refreshed automatically. To force the texts to be refreshed when they are displayed in the user interface, you need declare the strings with the <a href="../qtcore/qtglobal.html#QT_TR_NOOP">QT_TR_NOOP</a>() macro. Then, when you populate the objects for display, you need to explicitly retrieve the translation for each text. For example:</p>
<pre class="cpp">ListModel {
id: myListModel;
ListElement {
<span class="comment">//: Capital city of Finland</span>
name: QT_TR_NOOP(<span class="string">"Helsinki"</span>);
}
}
<span class="operator">.</span><span class="operator">.</span><span class="operator">.</span>
Text {
text: qsTr(myListModel<span class="operator">.</span>get(<span class="number">0</span>)<span class="operator">.</span>name); <span class="comment">// get the translation of the name property in element 0</span>
}</pre>
<a name="8-use-locale-to-extend-localization-features"></a>
<h3>8. Use Locale to Extend Localization Features</h3>
<p>If you want different graphics or audio for different geographical regions, you can use Qt.<a href="../qtqml/qml-qtqml-locale.html">locale</a>() to get the current locale. Then you choose appropriate graphics or audio for that locale.</p>
<p>The following code snippet shows how you could select an appropriate icon that represents the language of the current locale.</p>
<pre class="cpp">Component<span class="operator">.</span>onCompleted: {
<span class="keyword">switch</span> (<span class="type"><a href="../qtcore/qt.html">Qt</a></span><span class="operator">.</span>locale()<span class="operator">.</span>name<span class="operator">.</span>substring(<span class="number">0</span><span class="operator">,</span><span class="number">2</span>)) {
<span class="keyword">case</span> <span class="string">"en"</span>: <span class="comment">// show the English-language icon</span>
languageIcon <span class="operator">=</span> <span class="string">"../images/language-icon_en.png"</span>;
<span class="keyword">break</span>;
<span class="keyword">case</span> <span class="string">"fi"</span>: <span class="comment">// show the Finnish language icon</span>
languageIcon <span class="operator">=</span> <span class="string">"../images/language-icon_fi.png"</span>;
<span class="keyword">break</span>;
<span class="keyword">default</span>: <span class="comment">// show a default language icon</span>
languageIcon <span class="operator">=</span> <span class="string">"../images/language-icon_default.png"</span>;
}
}</pre>
<a name="localizing-your-application"></a>
<h2>Localizing your Application</h2>
<p>Qt Quick applications use the same underlying localization system as Qt C++ applications (lupdate, lrelease and .ts files). You use the same tools as described in the <a href="../qtlinguist/linguist-manager.html">Qt Linguist Manual</a>. You can even have user interface strings in C++ and QML source in the same application. The system will create a single combined translation file and the strings are accessible from QML and C++.</p>
<a name="use-a-conditional-to-hide-qml-source-from-the-compiler"></a>
<h3>Use a Conditional to Hide QML Source From the Compiler</h3>
<p>The <tt>lupdate</tt> tool extracts user interface strings from your application. lupdate reads your application's .pro file to identify which source files contain texts to be translated. This means your source files must be listed in the <tt>SOURCES</tt> or <tt>HEADERS</tt> entry in the .pro file. If your files are not listed the texts in them will not be found.</p>
<p>However, the SOURCES variable is intended for C++ source files. If you list QML or JavaScript source files there, the compiler tries to build them as though they are C++ files. As a workaround, you can use an <tt>lupdate_only{...}</tt> conditional statement so the <tt>lupdate</tt> tool sees the .qml files but the C++ compiler ignores them.</p>
<p>For example, the following .pro file snippet specifies two .qml files in the application.</p>
<pre class="cpp">lupdate_only{
SOURCES <span class="operator">=</span> main<span class="operator">.</span>qml \
MainPage<span class="operator">.</span>qml
}</pre>
<p>You can also specify the .qml source files with a wildcard match. The search is not recursive so you need to specify each directory where there are user interface strings in the source code:</p>
<pre class="cpp">lupdate_only{
SOURCES <span class="operator">=</span> <span class="operator">*</span><span class="operator">.</span>qml \
<span class="operator">*</span><span class="operator">.</span>js \
content<span class="comment">/*.qml \
content/*.js
}
</span></pre>
<p>See the <a href="../qtlinguist/qtlinguist-index.html">Qt Linguist Manual</a> for more details about Qt localization.</p>
</div>
<!-- @@@qtquick-internationalization.html -->
</div>
</div>
</div>
</div>
</div>
<div class="footer">
<p>
<acronym title="Copyright">©</acronym> 2013 Digia Plc and/or its
subsidiaries. Documentation contributions included herein are the copyrights of
their respective owners.<br> The documentation provided herein is licensed under the terms of the <a href="http://www.gnu.org/licenses/fdl.html">GNU Free Documentation License version 1.3</a> as published by the Free Software Foundation.<br> Digia, Qt and their respective logos are trademarks of Digia Plc in Finland and/or other countries worldwide. All other trademarks are property
of their respective owners. </p>
</div>
</body>
</html>
|