Rename KDEHOME and KDEDIR

pull/1/head
Timothy Pearson 13 years ago
parent 11433c5e3b
commit dc6974ef6a

@ -41,11 +41,11 @@
from an open document.</para>
<para>The template folder is part of the &kde; file system, and
consists of at least
KDEDIR/share/applications/kate/plugins/katefiletemplates/templates and
KDEHOME/share/applications/kate/plugins/katefiletemplates/templates. If your
KDEDIRS environment variable contains additional directories, those are
TDEDIR/share/applications/kate/plugins/katefiletemplates/templates and
TDEHOME/share/applications/kate/plugins/katefiletemplates/templates. If your
TDEDIRS environment variable contains additional directories, those are
searched for a similar subdirectory as well. If equally named templates are
found, the one in the local (KDEHOME) folder is chosen.</para>
found, the one in the local (TDEHOME) folder is chosen.</para>
<sect1 id="katefiletemplates-menu">
<title>Menu Structure</title>

@ -39,7 +39,7 @@ open tag on the left.</para>
<para>The <acronym>DTD</acronym> must exist in &XML; format, as produced by the Perl program
<command>dtdparse</command>. We will call a DTD in this format <quote>meta DTD</quote>.
Some meta DTDs are supplied. They are installed in
<filename class="directory">$KDEDIR/share/apps/katexmltools/</filename>,
<filename class="directory">$TDEDIR/share/apps/katexmltools/</filename>,
which is also the default folder when you choose
<guimenuitem>Assign Meta DTD...</guimenuitem>.
To produce your own meta DTDs, get <command>dtdparse</command> from
@ -93,7 +93,7 @@ current element if you are inside a tag.</para>
<title>Features and Limitations</title>
<para>You can test all functions and limitations by loading
<filename>$KDEDIR/share/apps/katexmltools/testcases.xml</filename>
<filename>$TDEDIR/share/apps/katexmltools/testcases.xml</filename>
into &kate; and following the instructions. Note that working with
more than one view per document is not yet correctly supported by
this plugin.</para>

@ -22,7 +22,7 @@
#define __KFILE_CERT_H__
/**
* Note: For further information look into <$KDEDIR/include/kfilemetainfo.h>
* Note: For further information look into <$TDEDIR/include/kfilemetainfo.h>
*/
#include <kfilemetainfo.h>

@ -26,7 +26,7 @@
#define __KFILE_LNK_H__
/**
* Note: For further information look into <$KDEDIR/include/kfilemetainfo.h>
* Note: For further information look into <$TDEDIR/include/kfilemetainfo.h>
*/
#include <kfilemetainfo.h>

@ -23,7 +23,7 @@
#define __KFILE_MHTML_H__
/**
* Note: For further information look into <$KDEDIR/include/kfilemetainfo.h>
* Note: For further information look into <$TDEDIR/include/kfilemetainfo.h>
*/
#include <kfilemetainfo.h>

@ -25,7 +25,7 @@ class TQTimer;
*
* If you want this plugin to be used by a part, you need to
* install the rc file under the directory
* "data" (KDEDIR/share/apps usually)+"/instancename/kpartplugins/"
* "data" (TDEDIR/share/apps usually)+"/instancename/kpartplugins/"
* where instancename is the name of the part's instance.
**/
class AutoRefresh : public KParts::Plugin

@ -107,7 +107,7 @@ public:
TQStringList names() const;
/**
* deletes the file if it is in KDEHOME, or marks it as hidden if it's a
* deletes the file if it is in TDEHOME, or marks it as hidden if it's a
* system file
**/
void remove(const TQString &name);
@ -124,7 +124,7 @@ public:
/**
* @returns the filename for a file you can save into. If @p create is
* false, it'll return an empty string if the file doesn't already exist in
* KDEHOME
* TDEHOME
*
* This function will not create the file, only return what the name is in
* theory.

Loading…
Cancel
Save