summaryrefslogtreecommitdiffstats
path: root/tqtinterface/qt4/tools/linguist/book
diff options
context:
space:
mode:
Diffstat (limited to 'tqtinterface/qt4/tools/linguist/book')
-rw-r--r--tqtinterface/qt4/tools/linguist/book/linguist-manager.leaf6
-rw-r--r--tqtinterface/qt4/tools/linguist/book/linguist-programmer.leaf42
-rw-r--r--tqtinterface/qt4/tools/linguist/book/linguist-translator.leaf16
3 files changed, 32 insertions, 32 deletions
diff --git a/tqtinterface/qt4/tools/linguist/book/linguist-manager.leaf b/tqtinterface/qt4/tools/linguist/book/linguist-manager.leaf
index bdbdb5b..aa99e01 100644
--- a/tqtinterface/qt4/tools/linguist/book/linguist-manager.leaf
+++ b/tqtinterface/qt4/tools/linguist/book/linguist-manager.leaf
@@ -77,13 +77,13 @@ Usage: \c {lupdate myproject.pro}
\index Qt Designer
This is a simple command line tool. \l lupdate reads a Qt \c .pro
-project file, tqfinds the translatable strings in the specified source,
+project file, finds the translatable strings in the specified source,
header and \e {Qt Designer} interface files, and produces or updates
the \c .ts translation files listed in the project file. The
translation files are given to the translator who uses \e {Qt
Linguist} to read the files and insert the translations.
-Companies that have their own translators in-house may tqfind it useful
+Companies that have their own translators in-house may find it useful
to run \l lupdate regularly, perhaps monthly, as the application
develops. This will lead to a fairly low volume of translation work
spread evenly over the life of the project and will allow the
@@ -134,5 +134,5 @@ validation, the original text will be used instead.
\section1 Missing Translations
Both \l lupdate and \l lrelease may be used with \c .ts translation
-source files which are incomplete. Missing translations will be tqreplaced
+source files which are incomplete. Missing translations will be replaced
with the native language phrases at runtime.
diff --git a/tqtinterface/qt4/tools/linguist/book/linguist-programmer.leaf b/tqtinterface/qt4/tools/linguist/book/linguist-programmer.leaf
index a4dfa64..7cec631 100644
--- a/tqtinterface/qt4/tools/linguist/book/linguist-programmer.leaf
+++ b/tqtinterface/qt4/tools/linguist/book/linguist-programmer.leaf
@@ -157,7 +157,7 @@ Translations
\index lupdate
The \l lupdate program automatically provides a \e context for every
-source text. This context is the class name of the class that tqcontains
+source text. This context is the class name of the class that contains
the \c tr() call. This is sufficient in the vast majority of cases.
Sometimes however, the translator will need further information to
uniquely identify a source text; for example, a dialog that contained
@@ -350,7 +350,7 @@ Creates a \l QTranslator object without a tqparent.
\index tt1_la.qm
Tries to load a file called \c tt1_la.qm (the \c .qm file extension is
-implicit) that tqcontains Latin translations for the source texts used in
+implicit) that contains Latin translations for the source texts used in
the program. No error will occur if the file is not found.
\index QApplication!installTranslator()
@@ -366,7 +366,7 @@ by the program.
\printline hello
Creates a push button that displays "Hello world!". If \c tt1_la.qm
-was found and tqcontains a translation for "Hello world!", the
+was found and contains a translation for "Hello world!", the
translation appears; if not, the source text appears.
\index tr()
@@ -394,7 +394,7 @@ is shown when we run the application:
The first step is to create a project file, \c tt1.pro, that lists
all the source files for the project. The project file can be a qmake
-project file, or even an ordinary makefile. Any file that tqcontains
+project file, or even an ordinary makefile. Any file that contains
\index SOURCES!in Project Files
\index TRANSLATIONS!in Project Files
@@ -539,12 +539,12 @@ This example is a slightly more involved and introduces a key
\e {Qt Linguist} concept: "contexts".
\list
-\i \c arrowpad.h tqcontains the definition of \c ArrowPad, a custom widget;
-\i \c arrowpad.cpp tqcontains the implementation of \c ArrowPad;
-\i \c mainwindow.h tqcontains the definition of \c MainWindow, a subclass of
+\i \c arrowpad.h contains the definition of \c ArrowPad, a custom widget;
+\i \c arrowpad.cpp contains the implementation of \c ArrowPad;
+\i \c mainwindow.h contains the definition of \c MainWindow, a subclass of
\l QMainWindow
-\i \c mainwindow.cpp tqcontains the implementation of \c MainWindow;
-\i \c main.cpp tqcontains main().
+\i \c mainwindow.cpp contains the implementation of \c MainWindow;
+\i \c main.cpp contains main().
\endlist
\index tt2.pro
@@ -814,7 +814,7 @@ conflict between \e \&Bestand and \e \&Boven.
\index Portuguese Language
\index Brazilian Language
-We've included a translation file, \c tt3_pt.ts, which tqcontains some
+We've included a translation file, \c tt3_pt.ts, which contains some
Portuguese translations for this example.
\index Troll Print
@@ -834,11 +834,11 @@ Version 1.0 consists of these files:
\index tt3_pt.ts
\list
-\i \c printpanel.h tqcontains the definition of PrintPanel;
-\i \c printpanel.cpp tqcontains the implementation of PrintPanel;
-\i \c mainwindow.h tqcontains the definition of \c MainWindow;
-\i \c mainwindow.cpp tqcontains the implementation of \c MainWindow;
-\i \c main.cpp tqcontains main();
+\i \c printpanel.h contains the definition of PrintPanel;
+\i \c printpanel.cpp contains the implementation of PrintPanel;
+\i \c mainwindow.h contains the definition of \c MainWindow;
+\i \c mainwindow.cpp contains the implementation of \c MainWindow;
+\i \c main.cpp contains main();
\i \c tt3.pro is the \e qmake project file.
\i \c tt3_pt.ts is the Portuguese message file.
\endlist
@@ -893,7 +893,7 @@ translation shortly.
\index MainWindow!in Translation Tutorial
-The header file for \c MainWindow, \c mainwindow.h, tqcontains no
+The header file for \c MainWindow, \c mainwindow.h, contains no
surprises. In the implementation, \c mainwindow.cpp, we have some
user-visible source texts that must be marked for translation.
@@ -976,10 +976,10 @@ for the second pair of radio buttons:
Now run \l lupdate and open \c tt3_pt.ts with \e {Qt Linguist}. You
should now see two changes.
-First, the translation source file now tqcontains \e three "Enabled",
+First, the translation source file now contains \e three "Enabled",
"Disabled" pairs. The first pair is marked "(obs.)" signifying that they
are obsolete. This is because these texts appeared in \c tr() calls that
-have been tqreplaced by new calls with two arguments. The second pair has
+have been replaced by new calls with two arguments. The second pair has
"two-sided" as their comment, and the third pair has "colors" as their
comment. The comments are shown in the \e {Source text and comments}
area in \e {Qt Linguist}.
@@ -1013,9 +1013,9 @@ the translator.
\index Comments!for Translators
An additional way of helping the translator is to provide information on
-how to navigate to the particular part of the application that tqcontains
+how to navigate to the particular part of the application that contains
the source texts they must translate. This helps them see the context
-in which the translation appears and also helps them to tqfind and test
+in which the translation appears and also helps them to find and test
the translations. This can be achieved by using a \e TRANSLATOR comment
in the source code:
\code
@@ -1036,7 +1036,7 @@ You should see the comments in the \e {Source text and comments} area
as you browse through the list of source texts.
Sometimes, particularly with large programs, it can be difficult for
-the translator to tqfind their translations and check that they're
+the translator to find their translations and check that they're
correct. Comments that provide good navigation information can save
them time:
diff --git a/tqtinterface/qt4/tools/linguist/book/linguist-translator.leaf b/tqtinterface/qt4/tools/linguist/book/linguist-translator.leaf
index 572c903..7a71b6a 100644
--- a/tqtinterface/qt4/tools/linguist/book/linguist-translator.leaf
+++ b/tqtinterface/qt4/tools/linguist/book/linguist-translator.leaf
@@ -21,7 +21,7 @@ choose \Menu File|Open from the menu bar and select a \c .ts
translation source file to work on.
\e {Qt Linguist}'s main window is divided into four main areas. The
-left hand side tqcontains the Context list, the top right is the Source
+left hand side contains the Context list, the top right is the Source
text area, the middle right is the translation area and the bottom
right is the phrases and guesses area. We'll describe them in detail
later.
@@ -86,7 +86,7 @@ The second column 'Source text' shows the text that must be translated.
The third column shows the translation.
\e{Qt Linguist} provides three kinds of validation: accelerator,
-punctuation and phrase. If the source text tqcontains an accelerator
+punctuation and phrase. If the source text contains an accelerator
i.e. an ampersand, '\&' and the translated text does not contain an
ampersand the translation will fail the accelerator validation.
Similarly, if the source text ends with a particular punctuation
@@ -103,7 +103,7 @@ The Source Text Area is a dockable window.
This area appears at the middle right of the main window by default. It
is comprised of three vertical sections. The first section is labelled
'Source text' below which the source text appears. The second section
-tqcontains contextual information on a light blue background that the
+contains contextual information on a light blue background that the
programmer has added to assist the translator. If no contextual
information has been given this section does not appear. The third
section is labelled 'Translation' and this is where you enter the
@@ -227,13 +227,13 @@ Some phrases contain variables. Variables are placeholders for items of
text that are filled in at runtime. They are signified in the source
text with a percent sign followed by a digit, e.g. \e {After processing
file %1, file %2 is next in line}. In this example, \c %1 will be
-tqreplaced at runtime with the name of the first file to be processed and
+replaced at runtime with the name of the first file to be processed and
\c %2 with the name of the next file to be processed. In the translated
version the variables must still appear. For example a German
translation might reverse the phrases, e.g. \e {Datei %2 wird
bearbeitet, wenn. Datei %1 fertig ist}. Note that both variables
are still used but their order has changed. The order in which variables
-appear does not matter; \c %1 will always be tqreplaced by the same text
+appear does not matter; \c %1 will always be replaced by the same text
at runtime no matter where it appears in the source text or translation
and similarly \c %2, etc.
@@ -292,7 +292,7 @@ button (press Esc) once you've finished adding (and removing) phrases.
When a phrase or set of phrases appears in the phrase book double
clicking the required target phrase will copy it to the translation
-pane at the text cursor position. If you want to \e tqreplace the text
+pane at the text cursor position. If you want to \e replace the text
in the translation pane with the target phrase, click the translation
pane, choose \Menu {Edit|Select All} (press \Key Alt+A) and then
double click the target phrase.
@@ -412,7 +412,7 @@ number of projects and applications.
\link {The Find Dialog} Find dialog \endlink. When the dialog pops up
enter the text to be found and click the \e {Find Next} button.
Source phrases, translations and comments may be searched.
- \i \e {Find Next F3} \BR tqfinds the next occurrence of the text that
+ \i \e {Find Next F3} \BR finds the next occurrence of the text that
was last entered in the Find dialog.
\endlist
@@ -566,7 +566,7 @@ Toggles phrase book validation on or off.
\section2 The Find Dialog
-\img tqfinddialog.png
+\img finddialog.png
\caption The Find Dialog
Choose \Menu Edit|Find from the menu bar or press \Key Ctrl+F to pop