general wording change for some file type names

- .ts file -> TS file
- .qm file -> QM file
- .ui file -> UI file

+ a handfull of typos I stumbled over

Merge-request: 802
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@nokia.com>

1 files changed, 20 insertions, 20 deletions

diff --git a/doc/src/porting4-designer.qdoc b/doc/src/porting4-designer.qdoc
index 916894b..7de1d43 100644
--- a/doc/src/porting4-designer.qdoc
+++ b/doc/src/porting4-designer.qdoc
@@ -41,12 +41,12 @@
 
 /*!
     \page porting4-designer.html
-    \title Porting .ui Files to Qt 4
+    \title Porting UI Files to Qt 4
     \contentspage {Porting Guides}{Contents}
     \previouspage Porting to Qt 4 - Drag and Drop
     \nextpage Porting to Graphics View
     \ingroup porting
-    \brief Information about changes to the .ui file format in Qt 4.
+    \brief Information about changes to the UI file format in Qt 4.
 
     Qt Designer has changed significantly in the Qt 4 release. We
     have moved away from viewing Qt Designer as an IDE and
@@ -57,20 +57,20 @@
     IDEs.
 
     The most important changes in Qt Designer 4 which affect porting
-    for \c .ui files are summarized below:
+    for UI files are summarized below:
 
     \list
     \o  \bold{Removed project manager.}
-        Qt Designer now only reads and edits \c .ui
-        files. It has no notion of a project (\c .pro file).
+        Qt Designer now only reads and edits UI
+        files. It has no notion of a project file (\c .pro).
 
     \o  \bold{Removed code editor.}
         Qt Designer can no longer be used to edit source files.
 
-    \o  \bold{Changed format of \c .ui files.}
+    \o  \bold{Changed format of UI files.}
         Qt Designer 4 cannot read files created by Qt Designer 3 and
         vice versa. However, we provide the tool \c uic3 to generate Qt
-        4 code out of Qt 3 \c .ui files, and to convert old \c .ui files
+        4 code out of Qt 3 UI files, and to convert old UI files
         into a format readable by Qt Designer 4.
 
     \o  \bold{Changed structure of the code generated by \c uic.}
@@ -80,7 +80,7 @@
         \c Ui::MyForm.
 
     \o  \bold{New resource file system.} Icon data is no longer
-        stored in the \c .ui file. Instead, icons are put into resource
+        stored in the UI file. Instead, icons are put into resource
         files (\c .qrc).
     \endlist
 
@@ -146,9 +146,9 @@
     therefore has an interface identical to that of a class generated
     by \c uic in Qt 3.
 
-    Creating POD classes from \c .ui files is more flexible and
+    Creating POD classes from UI files is more flexible and
     generic than the old approach of creating widgets. Qt Designer
-    doesn't need to know anything about the main container apart from
+    does not need to know anything about the main container apart from
     the base widget class it inherits. Indeed, \c Ui::HelloWorld can
     be used to populate any container that inherits QWidget.
     Conversely, all non-GUI aspects of the main container may be
@@ -163,10 +163,10 @@
     \list 1
     \o To generate headers and source code for a widget to implement any
     custom signals and slots added using Qt Designer 3.
-    \o To generate a new \c .ui file that can be used with Qt Designer 4.
+    \o To generate a new UI file that can be used with Qt Designer 4.
     \endlist
 
-    You can use both these methods in combination to obtain \c{.ui}, header
+    You can use both these methods in combination to obtain UI, header
     and source files that you can use as a starting point when porting
     your user interface to Qt 4.
 
@@ -179,7 +179,7 @@
 
     The resulting files \c myform.h and \c myform.cpp implement the
     form in Qt 4 using a QWidget that will include custom signals,
-    slots and connections specified in the \c .ui file. However,
+    slots and connections specified in the UI file. However,
     see below for the \l{#Limitations of uic3}{limitations} of this
     method.
 
@@ -190,7 +190,7 @@
 
     The resulting file \c myform4.ui can be edited in Qt Designer 4. The
     header file for the form is generated by Qt 4's \c uic. See the
-    \l{Using a Designer .ui File in Your Application} chapter of the
+    \l{Using a Designer UI File in Your Application} chapter of the
     \l{Qt Designer Manual} for information about the preferred ways to
     use forms created with Qt Designer 4.
 
@@ -218,7 +218,7 @@
 
     \section1 Limitations of uic3
 
-    Converting Qt 3 \c .ui files to Qt 4 has some limitations. The
+    Converting Qt 3 UI files to Qt 4 has some limitations. The
     most noticeable limitation is the fact that since \c uic no
     longer generates a QObject, it's not possible to define custom
     signals or slots for the form. Instead, the programmer must
@@ -231,9 +231,9 @@
     A quick and dirty way to port forms containing custom signals and
     slots is to generate the code using \c uic3, rather than \c uic. Since
     \c uic3 does generate a QWidget, it will populate it with custom
-    signals, slots and connections specified in the \c .ui file.
-    However, \c uic3 can only generate code from Qt 3 \c .ui files, which
-    implies that the \c .ui files never get translated and need to be
+    signals, slots and connections specified in the UI file.
+    However, \c uic3 can only generate code from Qt 3 UI files, which
+    implies that the UI files never get translated and need to be
     edited using Qt Designer 3.
 
     Note also that it is possible to create implicit connections
@@ -256,7 +256,7 @@
     \section1 Icons
 
     In Qt 3, the binary data for the icons used by a form was stored
-    in the \c .ui file. In Qt 4 icons and any other external files
+    in the UI file. In Qt 4 icons and any other external files
     can be compiled into the application by listing them in a \l{The
     Qt Resource System}{resource file} (\c .qrc). This file is
     translated into a C++ source file using Qt's resource compiler
@@ -306,7 +306,7 @@
     the following steps:
 
     \list 1
-    \o Use \c{uic3 -convert} to obtain a \c .ui file understood by
+    \o Use \c{uic3 -convert} to obtain a UI file understood by
        Qt Designer 4.
 
     \o Create a \c .qrc file with a list of all the icon files.