<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html>
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<!-- linguist-manual.qdoc -->
<title>Overview of the Translation Process | Qt Linguist Manual</title>
<link rel="stylesheet" type="text/css" href="style/offline-simple.css" />
<script type="text/javascript">
document.getElementsByTagName("link").item(0).setAttribute("href", "style/offline.css");
// loading style sheet breaks anchors that were jumped to before
// so force jumping to anchor again
setTimeout(function() {
var anchor = location.hash;
// need to jump to different anchor first (e.g. none)
location.hash = "#";
setTimeout(function() {
location.hash = anchor;
}, 0);
}, 0);
</script>
</head>
<body>
<div class="header" id="qtdocheader">
<div class="main">
<div class="main-rounded">
<div class="navigationbar">
<table><tr>
<td >Qt 5.9</td><td ><a href="qtlinguist-index.html">Qt Linguist Manual</a></td><td >Overview of the Translation Process</td></tr></table><table class="buildversion"><tr>
<td id="buildversion" width="100%" align="right">Qt 5.9.4 Reference Documentation</td>
</tr></table>
</div>
</div>
<div class="content">
<div class="line">
<div class="content mainContent">
<link rel="prev" href="qtlinguist-index.html" />
<link rel="next" href="linguist-manager.html" />
<p class="naviNextPrevious headerNavi">
<a class="prevPage" href="qtlinguist-index.html">Qt Linguist Manual</a>
<span class="naviSeparator"> ◦ </span>
<a class="nextPage" href="linguist-manager.html">Qt Linguist Manual: Release Manager</a>
</p><p/>
<div class="sidebar"><div class="sidebar-content" id="sidebar-content"></div></div>
<h1 class="title">Overview of the Translation Process</h1>
<span class="subtitle"></span>
<!-- $$$linguist-overview.html-description -->
<div class="descr"> <a name="details"></a>
<p>Most of the text that must be translated in an application consists of either single words or short phrases. These typically appear as window titles, menu items, tooltips, and labels to buttons, check boxes and radio buttons.</p>
<p>The phrases are entered into the source code by the developer in their native language using a simple but special syntax to identify that the phrases require translation. The Qt tools provide context information for each of the phrases to help the translator, and the developer is able to add additional context information to phrases when necessary.</p>
<p>The release manager generates a set of translation files that are produced from the source files and passes these to the translator. The translator opens the translation files using <i>Qt Linguist</i>, enters their translations and saves the results back into the translation files, which they pass back to the release manager. The release manager then generates fast compact versions of these translation files ready for use by the application.</p>
<p>The tools are designed to be used in repeated cycles as applications change and evolve, preserving existing translations and making it easy to identify which new translations are required. <i>Qt Linguist</i> also provides a phrase book facility to help ensure consistent translations across multiple applications and projects.</p>
<p>Translators and developers must address a number of issues because of the subtleties and complexities of human language:</p>
<ul>
<li>A single phrase may need to be translated into several different forms depending on context. For example, <i>open</i> in English might become <i>ö</i><i>ffnen</i>, "open file", or <i>aufbauen</i>, "open internet connection", in German.</li>
<li>Keyboard accelerators may need to be changed but without introducing conflicts. For example, "&Quit" in English becomes "Avslutt" in Norwegian which does not contain a "Q". We cannot use a letter that is already in use - unless we change several accelerators.</li>
<li>Phrases that contain variables, for example, "The 25 files selected will take 63 seconds to process", where the two numbers are inserted programmatically at run-time may need to be reworded because in a different language the word order and therefore the placement of the variables may have to change.</li>
</ul>
<p>The Qt translation tools provide clear and simple solutions to these issues.</p>
<p><i>Qt Linguist</i> and lupdate are able to import and export XML Localization Interchange File Format (XLIFF) files, making it possible to take advantage of tools and translation services that work with this format. For more information on working with these files, see <a href="linguist-translators.html">Translators</a>.</p>
</div>
<!-- @@@linguist-overview.html -->
<p class="naviNextPrevious footerNavi">
<a class="prevPage" href="qtlinguist-index.html">Qt Linguist Manual</a>
<span class="naviSeparator"> ◦ </span>
<a class="nextPage" href="linguist-manager.html">Qt Linguist Manual: Release Manager</a>
</p>
</div>
</div>
</div>
</div>
</div>
<div class="footer">
<p>
<acronym title="Copyright">©</acronym> 2017 The Qt Company Ltd.
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> Qt and respective logos are trademarks of The Qt Company Ltd. in Finland and/or other countries worldwide. All other trademarks are property
of their respective owners. </p>
</div>
</body>
</html>
distrib
>
Mageia
>
6
>
x86_64
>
media
>
core-updates
>
by-pkgid
>
749fcc421771b410525f39bd88a5732d
>
files
>
497
