Rename KDEHOME and KDEDIR

3 files changed, 7 insertions, 7 deletions

diff --git a/doc/kommander/extending.docbook b/doc/kommander/extending.docbook
index 1adfdc25..473b8ec5 100644
--- a/doc/kommander/extending.docbook
+++ b/doc/kommander/extending.docbook
@@ -346,12 +346,12 @@ mykomplugin.cpp, compiling and installing your plugin would involve
 something similar to the following commands:
 </para>
 <screen>
-libtool --mode=compile g++ -$KDEDIR/include -IQTDIR/include \
+libtool --mode=compile g++ -$TDEDIR/include -IQTDIR/include \
    -I. -fPIC -c komlineedit.cpp
-libtool --mode=compile g++ -$KDEDIR/include -IQTDIR/include \
+libtool --mode=compile g++ -$TDEDIR/include -IQTDIR/include \
    -I. -fPIC -c mykomplugin.cpp
 
-libtool --mode=link g++ -shared -L$KDEDIR/lib -ltdeui -lkommanderwidget \
+libtool --mode=link g++ -shared -L$TDEDIR/lib -ltdeui -lkommanderwidget \
    -lkommanderplugin komlineedit.cppkomlineedit.o mykomplugin.o 
    -o libmykomplugin.so
 </screen>
@@ -359,7 +359,7 @@ libtool --mode=link g++ -shared -L$KDEDIR/lib -ltdeui -lkommanderwidget \
 If you want to install new plugin system-wide, root, use:
 </para>
 <screen>
-su -c "cp libmykomplugin.so $KDEDIR/lib"
+su -c "cp libmykomplugin.so $TDEDIR/lib"
 </screen>
 <note><para>If you use the KDevelop project generator, you will not need to do the above, but instead adapt the Makefile.am to link against extra libraries. By default, it will link to &Qt; and &kde; libraries and generate all the needed object files. Just run <command>make</command> to build, and <command>su -c make install</command> to install.</para></note>
 </sect2>
diff --git a/doc/kommander/translating.docbook b/doc/kommander/translating.docbook
index 15d7def2..629b22ea 100644
--- a/doc/kommander/translating.docbook
+++ b/doc/kommander/translating.docbook
@@ -34,7 +34,7 @@ Here is a short description about the needed steps to make a dialog translatable
 
 <listitem><para>How to extract the messages and create the .po file?</para>
 <para>
-    Use the <command>kmdr2po</command> script to extract the strings. The script is inside the <emphasis>working</emphasis> directory of the source release tarball and should be installed to <command>$KDEDIR/share/apps/kommander/translating</command> as well.
+    Use the <command>kmdr2po</command> script to extract the strings. The script is inside the <emphasis>working</emphasis> directory of the source release tarball and should be installed to <command>$TDEDIR/share/apps/kommander/translating</command> as well.
 </para>
 <para>
 Just run:
@@ -52,7 +52,7 @@ An appropriate &lt;your-kommander-dialog.po> file will be created.
 
 <listitem><para>How to install the translation?</para>
 <para>Put the compiled *.mo file either to</para>
-<para><command>$KDEDIR/share/locale/&lt;your language>/LC_MESSAGES/</command> (will be available globally for all users)</para>
+<para><command>$TDEDIR/share/locale/&lt;your language>/LC_MESSAGES/</command> (will be available globally for all users)</para>
 <para>or to </para>
 <para><command>$HOME/.kde/share/locale/&lt;your language>/LC_MESSAGES/</command> (will be available only for the current user)</para> 
 <para>directory.</para>
diff --git a/doc/kommander/tutorials.docbook b/doc/kommander/tutorials.docbook
index 0f6fd954..00f44d87 100644
--- a/doc/kommander/tutorials.docbook
+++ b/doc/kommander/tutorials.docbook
@@ -316,7 +316,7 @@ Shows how to use Table widget
 These examples reflect the most recent development state of &kommander;. In its current state &kommander; has few limitations for developing small to medium applications. It certainly is not suitable for building a KWord clone, but for a simple editor, database frontend, GUI for commandline programs or any application in the spirit of Unix/Linux small applications it is a good choice. The examples presented here are intended to show the potential as well as how to work around limitations. There are some useful tricks included in these if you want to do a more capable small application with &kommander;. Remember &kommander; is not intended to do everything, but to do most things. For this concession you should be able to build something in &kommander; faster than other alternatives ad add GUI to scripting languages not otherwise supported in KDE.
 </para>
 <note><para>
-The examples are installed to <command>$KDEDIR/share/apps/kmdr-editor/editor</command>. In case you do not have them there, get from <ulink url="http://kommander.tdewebdev.org">our home page</ulink>, by downloading the latest release.
+The examples are installed to <command>$TDEDIR/share/apps/kmdr-editor/editor</command>. In case you do not have them there, get from <ulink url="http://kommander.tdewebdev.org">our home page</ulink>, by downloading the latest release.
 </para>
 </note>