summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLeena Miettinen <riitta-leena.miettinen@digia.com>2013-04-03 17:09:08 +0200
committerThe Qt Project <gerrit-noreply@qt-project.org>2013-04-10 09:30:46 +0200
commit687e709cc0000c99a0ceeb15de831cb54b0e7832 (patch)
treea3d061e34b9e7c9f3ca63997fc86219eda36ce70
parent3455a96c6728873a3ba69585ebb27bf8e733c0f9 (diff)
downloadqttools-687e709cc0000c99a0ceeb15de831cb54b0e7832.tar.gz
Doc: move release management task list in Qt Linguist Manual
Move the description of the release process from the Developer chapter to the Release Manager chapter. Change-Id: Ia119e57b090d10d23b875120b1394be1c89b8405 Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
-rw-r--r--src/linguist/linguist/doc/src/linguist-manual.qdoc53
1 files changed, 27 insertions, 26 deletions
diff --git a/src/linguist/linguist/doc/src/linguist-manual.qdoc b/src/linguist/linguist/doc/src/linguist-manual.qdoc
index 97cd36e4c..fc76ee4fe 100644
--- a/src/linguist/linguist/doc/src/linguist-manual.qdoc
+++ b/src/linguist/linguist/doc/src/linguist-manual.qdoc
@@ -151,6 +151,33 @@
lrelease. These tools can process \l qmake project files, or operate
directly on the file system.
+ \section1 Creating Translation Files
+
+ Translation files consist of all the user-visible text and Ctrl key
+ accelerators in an application and translations of that text.
+
+ To create translation files:
+
+ \list 1
+
+ \li Run lupdate to generate the first set of translation source (TS) files
+ with all the user-visible text but no translations.
+
+ \li Give the TS files to the translator who adds translations using \QL. \QL
+ takes care of any changed or deleted source text.
+
+ \li Run lupdate to incorporate any new text added to the application.
+ lupdate synchronizes the user-visible text from the application with the
+ translations. It does not destroy any data.
+
+ \li To release the application, run lrelease to read the TS files and
+ produce the QM files used by the application at runtime.
+
+ \endlist
+
+ For lupdate to work successfully, it must know which translation files to
+ produce. The files are listed in the application's \c .pro Qt project file.
+
\section1 Qt Project Files
The easiest method to use lupdate and lrelease is by specifying
@@ -1241,32 +1268,6 @@
translatable. For more information about making QML sources translatable, see
\l{Internationalization and Localization with Qt Quick}.
- \section2 Creating Translation Files
-
- Translation files consist of all the user-visible text and Ctrl key
- accelerators in an application and translations of that text.
- Translation files are created as follows:
-
- \list 1
- \li Run lupdate to generate the first set of TS translation source files
- with all the user-visible text but no translations.
- \li Give the TS files to the translator who adds translations using \QL. \QL
- takes care of any changed or deleted source text.
- \li Run lupdate to incorporate any new text added to the application.
- lupdate synchronizes the user-visible text from the application with the
- translations. It does not destroy any data.
- \li To release the application, run lrelease to read the TS files and
- produce the QM files used by the application at runtime.
- \endlist
-
- For lupdate to work successfully, it must know which translation files to
- produce. The files are
- listed in the application's \c .pro Qt project file, for example:
-
- \snippet arrowpad/arrowpad.pro 1
-
- For more information, see \l{Using lupdate} and \l{Using lrelease}.
-
\section2 Loading Translations
\snippet hellotr/main.cpp 1