Use tdeApp

Signed-off-by: Michele Calgaro <[email protected]>

1 files changed, 15 insertions, 15 deletions

diff --git a/doc/en/index.docbook b/doc/en/index.docbook
index b8de907..79eb15f 100644
--- a/doc/en/index.docbook
+++ b/doc/en/index.docbook
@@ -1,7 +1,7 @@
 <?xml version="1.0" ?>
 <!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" "dtd/kdex.dtd" [
   <!ENTITY kmyfirewall '<application>KMyFirewall</application>'>
-  <!ENTITY kapp "&kmyfirewall;"><!-- replace kmyfirewall here -->
+  <!ENTITY tdeApp "&kmyfirewall;"><!-- replace kmyfirewall here -->
   <!ENTITY % addindex "IGNORE">
   <!ENTITY % English "INCLUDE"><!-- change language only here -->
   
@@ -473,7 +473,7 @@ The option <quote>-A INPUT</quote> tells the program to add the rule at the end
 options <quote>-I chain [rulenum] </quote> for inserting a rule, <quote>-R chain [rulenum]</quote> for replacing a rule and
 <quote>-D chain rulenum</quote> for deleting a rule from a chain.
 </para>
-<para>&kapp; only uses the -A option in the generated script.</para>
+<para>&tdeApp; only uses the -A option in the generated script.</para>
 </sect1>
 
 <sect1 id="options">
@@ -758,24 +758,24 @@ to see the list of allowed names).
 </chapter>
 
 
-<chapter id="using-kapp">
-<title>Using &kapp;</title>
+<chapter id="using-tdeApp">
+<title>Using &tdeApp;</title>
 
 <!-- This chapter should tell the user how to use your app. You should use as
 many sections (Chapter, Sect1, Sect3, etc...) as is necessary to fully document
 your application. -->
 
-<sect1 id="kapp-overview">
+<sect1 id="tdeApp-overview">
 <title>Overview - GUI Interfaces</title>
-<para>&kapp; ships with two different GUI interfaces.</para>
+<para>&tdeApp; ships with two different GUI interfaces.</para>
 
-<sect2 id="kapp-interfaces-generic">
+<sect2 id="tdeApp-interfaces-generic">
 <title>Generic Interface</title>
 
 <para>The Generic Interface is an abstract view on what kind of netwok traffic may or may not pass yout computer. The rules are generated by a compiler plugin so that it is possible to generate scripts for other plattforms p.e. OpenBSD/pf then GNU/Linux/iptables (well currently just the iptables compiler is implemented. Let me know if you are interrested in implementing that :)).</para>
 </sect2>
 
-<sect2 id="kapp-interfaces-ipt">
+<sect2 id="tdeApp-interfaces-ipt">
 <title>IPTables Interface</title>
 
 <para>The IPTables interfaces tries to represent a 1-1 look at the iptables rule set your configuration will create. Therefore it is ment to be used by experienced system administrators in order to setup very fine graduaded rulesets. Becaus of the tight relation this GUI has to the netfilter/iptables framework it can only be used on GNU/Linux workstations as the document can not be compiled into any other rule description language.</para>
@@ -819,7 +819,7 @@ are no rules defined to filter any kind of packets.
 <chapter id="commands">
 <title>Command Reference</title>
 
-<sect1 id="kapp-mainwindow">
+<sect1 id="tdeApp-mainwindow">
 <title>The main KMyFirewall window</title>
 <para></para>
 
@@ -855,7 +855,7 @@ are no rules defined to filter any kind of packets.
 <guimenu>File</guimenu>
 <guimenuitem>Quit</guimenuitem>
 </menuchoice></term>
-<listitem><para><action>Quits</action> &kapp;</para></listitem>
+<listitem><para><action>Quits</action> &tdeApp;</para></listitem>
 </varlistentry>
 </variablelist>
 </para>
@@ -868,7 +868,7 @@ are no rules defined to filter any kind of packets.
 -->
 
 <chapter id="developers">
-<title>Developer's Guide to &kapp;</title>
+<title>Developer's Guide to &tdeApp;</title>
 
 <para>
 As you can see this thing gets quiet big so every kind of help (coding,docs,translations)
@@ -877,9 +877,9 @@ if you have some ideas, patches, wishes or whatever.
 </para>
 
 <sect1 id="developers-plugins">
-<title>&kapp; Plugin framework</title>
+<title>&tdeApp; Plugin framework</title>
 <para>
-&kapp; extensively uses KDE's KParts/XMLGUI technology to provide an easy to and robust plugin infrastructure. Allmost every function is performed by dynamicaly loaded plugins in order to make it easy manage the code and write extentions. Especially the IPTables interface uses plugins to embeed the different iptables rule options edit dialogs.
+&tdeApp; extensively uses KDE's KParts/XMLGUI technology to provide an easy to and robust plugin infrastructure. Allmost every function is performed by dynamicaly loaded plugins in order to make it easy manage the code and write extentions. Especially the IPTables interface uses plugins to embeed the different iptables rule options edit dialogs.
 </para>
 </sect1>
 
@@ -1417,7 +1417,7 @@ void KMFRuleEditMac::accept() {
 
 void KMFRuleEditMac::slotHelp() {
 	kdDebug() &lt;&lt; "void KMFRuleEditMac::slotHelp()" &lt;&lt; endl;
-	kapp->invokeHelp( "src_mac" );
+	tdeApp->invokeHelp( "src_mac" );
 }
 void KMFRuleEditMac::reject() {
 	kdDebug() &lt;&lt; "void KMFRuleEditMac::reject()" &lt;&lt; endl;
@@ -1454,7 +1454,7 @@ application work. -->
 <qandaset id="faqlist">
 <qandaentry>
 <question>
-<para>My Mouse doesn't work. How do I quit &kapp;?</para>
+<para>My Mouse doesn't work. How do I quit &tdeApp;?</para>
 </question>
 <answer>
 <para>You silly goose! Check out the <link linkend="commands">Commands