summaryrefslogtreecommitdiffstats
path: root/doc/trouble.html
diff options
context:
space:
mode:
authorTimothy Pearson <kb9vqf@pearsoncomputing.net>2011-12-03 22:23:44 -0600
committerTimothy Pearson <kb9vqf@pearsoncomputing.net>2011-12-03 22:23:44 -0600
commit203ba231d0276943aae36111f9ec1e949f3c6a4c (patch)
treef039f7a5b5fc2da88a96876971bac580d87f6788 /doc/trouble.html
parentfd35f4a8382b7d223bc0325b9ca3f88515778aa0 (diff)
downloadpytde-203ba231d0276943aae36111f9ec1e949f3c6a4c.tar.gz
pytde-203ba231d0276943aae36111f9ec1e949f3c6a4c.zip
Initial TQt conversion
Diffstat (limited to 'doc/trouble.html')
-rw-r--r--doc/trouble.html18
1 files changed, 9 insertions, 9 deletions
diff --git a/doc/trouble.html b/doc/trouble.html
index 085a204..c3f5576 100644
--- a/doc/trouble.html
+++ b/doc/trouble.html
@@ -23,17 +23,17 @@ CLASS="NAVHEADER"
</p>
<p>
Before each release, PyKDE is test built against SuSE, Red Hat and Mandrake Linux distributions,
-and various versions of Python, Qt and KDE. Even after performing test builds, errors still can
+and various versions of Python, TQt and KDE. Even after performing test builds, errors still can
occur with your installation. The most common sources of errors are (roughly in order of occurance):
</p>
<ul>
<li>Differences in user environments</li>
<li>Differences between distributions (or even between different builds of same version of the same distribution</li>
-<li>Bugs - in PyKDE or any of the software it's based on (KDE, Qt, PyQt, sip, or even Python)</li>
+<li>Bugs - in PyKDE or any of the software it's based on (KDE, TQt, PyTQt, sip, or even Python)</li>
</ul>
<h2>Reporting errors -- PLEASE READ!</h2>
<p>
-The people on the PyKDE mailing list are knowledgeable about Python, PyQt,and PyKDE and are
+The people on the PyKDE mailing list are knowledgeable about Python, PyTQt,and PyKDE and are
genuinely helpful. You shouldn't hesitate to post a question or problem there (you may hear
"RTFM" occasionally, but not often). Chances are that someone using your distribution is already
posting to the list.
@@ -93,7 +93,7 @@ build PyKDE as root.
</dd>
<dt>"Can't remove or create directory"</dt>
<dd>
-This happens rarely, but is a quirk of the PyKDE build process. PyKDE will build and make
+This happens rarely, but is a tquirk of the PyKDE build process. PyKDE will build and make
as an unprivileged user BUT if you did a build of PyKDE previously as root and then attempt
to build PyKDE again as a user, the build will fail. The reason is that configure.py creates a
number of directories and a lot of files. The next time configure.py runs, it will try to delete
@@ -101,13 +101,13 @@ these directories and files before re-creating them. If the original directories
were owned by root, a user will be unable to delete them and configure.py will fail if run as
a user in that case.
</dd>
-<dt>"Can't find PyQt sip files"</dt>
+<dt>"Can't find PyTQt sip files"</dt>
<dd>
-You did install them, right? If you build PyQt from sources, the sip files will be there
-somewhere (by default, PyQt installs the PyQt sip files in /usr/share/PyQt if built from
+You did install them, right? If you build PyTQt from sources, the sip files will be there
+somewhere (by default, PyTQt installs the PyTQt sip files in /usr/share/PyTQt if built from
source). When you find them, you can tell configure.py where they are with a switch (see
-<a href="switches.html">next page</a>). If you installed PyQt from RPMs (either downloaded or
-from your distribution), the sip files are usually in a "devel" RPM for PyQt, which also needs
+<a href="switches.html">next page</a>). If you installed PyTQt from RPMs (either downloaded or
+from your distribution), the sip files are usually in a "devel" RPM for PyTQt, which also needs
to be installed if you want to build PyKDE from sources.
</dd>
<dt>Code generation errors</dt>