<!DOCTYPE book PUBLIC "-//KDE//DTD DocBook V3.1-Based Variant V1.0//EN">
<book lang="de">
<bookinfo>
<title>KDE Oft gestellte Fragen (FAQ)</title>
<authorgroup>
<author>
<surname>Erstellt von Matthias H&ouml;lzer-Kl&uuml;pfel und Lee Wee Tiong</surname>
</author>
</authorgroup>
<date>12. August 1999</date>
<releaseinfo><!-- information about this particular version --></releaseinfo>
<revhistory>
<revision>
<revnumber></revnumber>
<date></date>
</revision>
</revhistory>
<abstract>
<para>Dies ist eine Zusammenstellung der zum K-Desktop-Environment am häufigsten gestellten Fragen (FAQ, Frequently
Ask Questions)</para>
<para>Oft gestellte Fragen (Frequently Asked Questions) zum K Desktop Environment (KDE)</para><!-- Merge this with the previous paragraph; it comes from <META NAME="description" CONTENT="..."> --></abstract>
<keywordset>
<keyword>KDE</keyword>
<keyword>FAQ</keyword>
<keyword>question</keyword>
<keyword>answer</keyword>
<keyword>Frage</keyword>
<keyword>Antwort</keyword>
</keywordset>
</bookinfo>

<chapter id="berdieseFAQ">
<title>Über diese FAQ</title>

<note>
<para>Übersetzt von Daniel Bolege (in der Fassung vom 26. Oktober 1998) und Tobias Burnus (SGML-Konversion und
Aktualisierung).</para>

<para>Berichten Sie mögliche Fehler oder Unvollständigkeiten in dieses Dokumentes bitte an <ulink url="mailto:kde-faq@kde.org">kde-faq@kde.org</ulink>. Bitte senden Sie uns jedoch keine Fragen, sondern
benutzen Sie die KDE-E-Maillisten und -Nachrichtengruppen statt dessen.</para>
</note>

<para>Viele der Anworten in dies Dokumentes wurden den zahlreichen KDE-E-Maillisten und -Nachrichtengruppen
entnommen. An alle, die Anworten gegeben haben, welche möglicherweise jetzt in dieser FAQ auftauchen,
nocheinmal ein herzliches Dankeschön. </para>

<sect1 id="wie-kann-ich-zu-dieser-faq-beitragen">
<title>Wie kann ich zu dieser FAQ beitragen?</title>

<para>Als erstes senden Sie uns jeden Fehler, den Sie entdecken. Weiterhin sind auch Ihre Vorschläge willkommen.
Noch besser ist es, wenn Sie etwas entdecken, daß unklar ist und Sie das am besten noch klarstellen können.
Sie erreichen uns unter <ulink url="mailto:kde-faq@kde.org">kde-faq@kde.org</ulink>.</para>

<para>Natürlich freuen wir uns auch über Antworten auf Fragen, die hier noch
nicht abgedeckt worden sind. Wir werden sie baldmöglichst hinzufügen. </para>

<para>Und nicht zu letzt sollten Sie dieses Dokument nutzen; lesen sie es grüdlich durch, bevor Sie Fragen an die
zahlreichen KDE-E-Maillisten und -Neuigkeitenlisten stellen. </para>

<para>P.S.: Erwägen Sie auch, ob Sie nicht die FAQ pflegen möchten; mehr Details finden sich im nächsten Abschnitt.</para>
</sect1>

<sect1 id="wie-bekomme-ich-ein-faq-pfleger">
<title>Wie bekomme ich ein FAQ-Pfleger?</title>

<para>Eigentlich ist es ganz leicht, die Aufgabe der FAQ-Pflege zu übernehmen. Zudem brauchen wir immer junges Blut.
:-) Sie brauchen nur folgendes zu tun: Erstesn benötigen Sie die folgenden Programmpakete auf Ihrem Rechner:</para>

<para><orderedlist><listitem>
<para> <ulink url="http://www.sgmltools.org/download-1.0.html">sgmltools 1.0.9</ulink>: Um die verschieden FAQ-Formate wie HTML und PostScript aus SGML zu erstellen.
Besorgen Sie sich nicht die 2.<emphasis>x</emphasis>-Version, da wir Linuxdoc-Kompatibiliät benötigen. Dies kann sich jedoch
gut ändern, wenn wir komplett zum neuen DocBook-Format wechseln.</para>
</listitem>
<listitem>
<para> ksgml2html: Ein Skript (eines der Hilfsprogramme in sgmltools), daß benutzt wird, um HTML-Dokumente im
KDE-Stil zu erstellen. Es ist im kdesdk-Paket unter <literal remap="tt">unstable/CVS/snapshots/current/</literal> auf dem
KDE-FTP-Server und seinen Spiegelservern enthalten.</para>
</listitem>
<listitem>
<para> cvs: Benötigt um auf das KDE-CVS-System zuzugreifen. Das Programm sollte auf jedem ordentlichen
GNU-FTP-Spiegelserver vorhanden sein. </para>
</listitem>
<listitem>
<para> Qt und KDE: Keine Erklärung nötig, hoffe ich. :-)</para>
</listitem>
</orderedlist>
</para>

<para>Zwar ist es nicht nötig die KDE zu benutzen, aber desto mehr man mit der KDE vertraut ist desto besser kann
man die FAQ pflegen.</para>

<para>Nachdem Sie sichergestellt haben, daß die nötigen Programme auf Ihrem System installiert sind, können Sie
anfangen. Zuerst bitten Sie <ulink url="mailto:coolo@kde.org">Stephan Kulow</ulink> Ihnen CVS-Schreibzugriff zu
geben. Diesen benötigen Sie, um die Veränderungen und Ergänzungen an den FAQ-Dateien wirksam werden zu lassen.
Sie sollten auch <ulink url="mailto:konold@alpha.tat.physik.uni-tuebingen.de">Martin Konold</ulink> bitten, Sie
der <ulink url="mailto:kde-faq@kde.org">KDE-FAQ E-Mailliste</ulink> hinzuzufügen. Während Sie auf den
CVS-Schreibzugriff warten, machen Sie sich mit den verschieden Werkzeugen, die Sie installiert haben,
vertraut.</para>

<para>Sobald Sie auf das KDE-CVS-System zugreiffen können, sollten Sie die FAQ-Dateien herunterladen. Sie sind unter
<literal remap="tt">kdebase/doc/khelpcenter/faq</literal> zu finden. Nur die original SGML-Datei und die erstellten HTML-Dateien
kommen in dies Verzeichnis. Zusätzlich gibt es einen anderen Ort, an den Sie die FAQ-Dateien senden:
<literal remap="tt">www/documentation/faq</literal>.  Die SGML-Version kommt jedoch nicht in dieses Verzeichnis, nur die HTML-, PostScript-,
ASCII-Text- und HTML-TAR-Dateien kommen hierhinein.</para>

<para>Schlußendlich mögen Sie sich fragen, welche Informationen der KDE-FAQ hinzugefügt werden sollten. Antwort: die
oft gestellten Fragen natürlich. Sie sollten die verschieden KDE-E-Maillisten und -Nachrichengruppen
abonnieren und, nachdem Sie Tonnen von E-Mails gelesen haben, in denen immer dasselbe gefragt wird, wissen
Sie, was fehlt. ;-)</para>

<para><emphasis>(Oben gesagtes gilt für das englische (amerikanische) Original. Die deutsche Übersetzung ist unter
<literal remap="tt">kde-i18n/de/docs/kdebase/khelpcenter/faq</literal> im CVS-System zu finden. Bevor man sich an das Korrigieren
und Modifizieren macht, sollte man die <ulink url="http://www.dtp-service.com/kde/de/">deutsche KDE-i18n-Seite</ulink> aufsuchen.)</emphasis></para>
</sect1>
</chapter>

<chapter id="Einleitung">
<title>Einleitung</title>

<sect1 id="was-ist-kde">
<title>Was ist KDE?</title>

<para>KDE ist das K Desktop Environment (&raquo;K-Desktopumgebung&laquo;).</para>

<para>KDE ist ein Projekt, das von <ulink url="mailto:ettrich@kde.org">Matthias Ettrich</ulink> 1996 begründet
wurde. Das Ziel des KDE-Projektes ist es, die Stärke des Unix-Betriebsystems mit dem Komfort einer modernen
Benutzeroberfläche zu verbinden.</para>

<para>Kurz: KDE bringt Unix den Desktop.</para>

<para>Falls Sie weitere Informationen zur KDE benötigen, werfen Sie einen Blick auf <ulink url="http://www.kde.org/whatiskde/index.html">What is KDE?</ulink> (&raquo;Was ist KDE&laquo;).</para>
</sect1>

<sect1 id="wofuer-steht-das-k-in-kde">
<title>Wofür Steht das K in KDE?</title>

<para>Für nichts. Es heißt einfach K Desktop Environment, genau wie das X in X Window System.</para>
</sect1>
<sect1 id="platform">
<title>Auf welchen Systemen kann ich das Laufen der KDE erwarten?</title>

<para>KDE ist eine Desktopumgebung für alle Arten von Unix. Obwohl die meisten KDE-Entwickler Linux verwenden, läuft
KDE problemlost auf einer Vielzahl von Systemen. Es kann sein, daß Sie den Quelltext etwas anpassen müssen, um
KDE auf einem seltenern System oder ohne GNU-Entwicklerwerkzeuge -- insbesondere ohne den gcc-Kompiler --
kompilieren zu können.</para>

<para>Einige der Systeme, auf denen KDE läuft, sind:
<itemizedlist>
<listitem>
<para> Linux</para>
</listitem>
<listitem>
<para> Solaris</para>
</listitem>
<listitem>
<para> FreeBSD</para>
</listitem>
<listitem>
<para> IRIX</para>
</listitem>
<listitem>
<para> HP-UX</para>
</listitem>
</itemizedlist>
</para>
</sect1>

<sect1 id="ist-kde-ein-fenstermanager">
<title>Ist KDE ein Fenstermanager?</title>

<para>Nein, KDE ist kein Fenstermanger. Obwohl KDE einen sehr moderen Fenstermanager, genannt KWM, enthält, ist KDE
mehr als das -- es ist eine vollständige integrierte Desktopumgebung (IDE, <emphasis>Integrated Desktop
Environment</emphasis>).</para>

<para>KDE bietet eine komplette Desktopumgebung, einschließlich eines Datei- und Fenstermanagers, eines Hilfe- und
Konfigurationssystems, einer Vielzahl von Werkzeugen und Hilfsprogrammen und eine stark zunehmende Anzahl von
Anwendungen, wie E-Mail- und Newsprogrammen, Zeichenanwendungen, PostScript- und DVI-Betrachtern.</para>
</sect1>

<sect1 id="ist-kde-ein-kopie">
<title>Ist KDE ein Kopie von CDE-, Windows95 oder MacOS?</title>

<para>Nein, KDE ist eine Kopie. Insbesondere keine CDE- oder Windowskopie. Während die KDE-Entwickler versuchen, die
besten Ideen von allen existierenden Desktopumgebungen zu verwenden, ist KDE eine eigenständige Umgebung, die
einen eigenen Weg zurückgelegt hat und weiter weiter tun wird.</para>
</sect1>

<sect1 id="ist-kde-freie-software">
<title>Ist KDE freie Software?</title>

<para>Ja, KDE ist frei Software gemäß der <ulink url="http://www.gnu.org/copyleft/gpl.html">GNU General Public License</ulink>
(<ulink url="http://www.gnu.de/gpl-ger.html">deutsche Übersetzung</ulink>). Alle KDE-Bibliotheken sind unter
der LGPL verfügbar, die kommerzielle Softwareentwicklung für den KDE-Desktop ermöglicht. Die KDE-Anwendungen
hingegen stehen unter der GPL-Lizenz.</para>

<para>KDE kommt mit dem <link linkend="was-ist-qt-eigentlich">Qt C++ crossplatform toolkit</link>, das eine eigene Lizenz besitzt.</para>

<para>Verkürzt gesagt erlaubt die Qt-Lizenz, Qt kostenlos für die Entwicklung von X-Window-Anwendungen zu verwenden,
solange man den Quelltext der Anwendungen kostenlos verfügbar macht. Falls Sie dies nicht wollen, müssen Sie
eine kommerzielle Lizenz für Qt erwerben. Mehr zu Qt und dessen Lizenz findent sich auf den Internetseiten von
<ulink url="http://www.troll.no">Troll Tech</ulink>.</para>

<para>Falls Sie Zweifel haben, welche Lizenz Sie benötigen, wenden Sie sich bitte direkt an
<ulink url="mailto:license@troll.no">Troll Tech</ulink>.</para>

<para>Es ist vollkommen legal KDE und Qt kostenlos auf CD verfügbar zu machen. Keine Laufzeitkosten jeglicher Form
fallen an.</para>
</sect1>
</chapter>

<chapter id="KDEerhalten">
<title>KDE erhalten</title>

<sect1 id="woher-bekomme-ich-die-kde">
<title>Woher bekomme ich die KDE?</title>

<para>Die Hauptverteilseite der KDE ist
<itemizedlist>
<listitem>
<para><ulink url="ftp://ftp.kde.org">ftp://ftp.kde.org</ulink></para>
</listitem>
</itemizedlist>
</para>

<para>Diese Seite ist jedoch oft stark ausgelastet, so daß Sie einen der folgenden
FTP-Spiegelserver bevorzugen könnten:
<itemizedlist>
<listitem>
<para> <ulink url="ftp://ftp.mouk.s-jaani.ee/pub/kde">ftp://ftp.mouk.s-jaani.ee/pub/kde</ulink></para>
</listitem>
<listitem>
<para> <ulink url="ftp://beer.stampede.org/ftp.kde.org">ftp://beer.stampede.org/ftp.kde.org</ulink></para>
</listitem>
<listitem>
<para> <ulink url="ftp://ftp1.change-espace.fr/pub/Linux/kde">ftp://ftp1.change-espace.fr/pub/Linux/kde</ulink></para>
</listitem>
<listitem>
<para> <ulink url="ftp://ftp.tsc.uvigo.es/pub/linux/kde">ftp://ftp.tsc.uvigo.es/pub/linux/kde</ulink></para>
</listitem>
<listitem>
<para> <ulink url="ftp://bromo.ptf.hro.nl/pub/mirrors/kde">ftp://bromo.ptf.hro.nl/pub/mirrors/kde</ulink></para>
</listitem>
<listitem>
<para> <ulink url="ftp://ftp.cised.unina.it/pub/kde">ftp://ftp.cised.unina.it/pub/kde</ulink></para>
</listitem>
<listitem>
<para> <ulink url="ftp://ftp.sw.com.sg/pub/kde">ftp://ftp.sw.com.sg/pub/kde</ulink></para>
</listitem>
<listitem>
<para> <ulink url="ftp://ftp.netlab.is.tsukuba.ac.jp/pub/X/KDE">ftp://ftp.netlab.is.tsukuba.ac.jp/pub/X/KDE</ulink></para>
</listitem>
<listitem>
<para> <ulink url="ftp://ftp.arpanet.ch/pub/mirrors/kde/">ftp://ftp.arpanet.ch/pub/mirrors/kde/</ulink></para>
</listitem>
<listitem>
<para> <ulink url="ftp://ftp.fu-berlin.de/pub/unix/X11/gui/kde/">ftp://ftp.fu-berlin.de/pub/unix/X11/gui/kde/</ulink></para>
</listitem>
<listitem>
<para> <ulink url="ftp://ftp.funet.fi/mirrors/ftp.kde.org/pub/kde">ftp://ftp.funet.fi/mirrors/ftp.kde.org/pub/kde</ulink></para>
</listitem>
<listitem>
<para> <ulink url="ftp://ftp.net.lut.ac.uk/kde">ftp://ftp.net.lut.ac.uk/kde</ulink></para>
</listitem>
<listitem>
<para> <ulink url="ftp://ftp.nvg.unit.no/pub/linux/kde">ftp://ftp.nvg.unit.no/pub/linux/kde</ulink></para>
</listitem>
<listitem>
<para> <ulink url="ftp://sunsite.unc.edu/pub/Linux/Incoming">ftp://sunsite.unc.edu/pub/Linux/Incoming</ulink></para>
</listitem>
<listitem>
<para> <ulink url="ftp://linux.unipv.it/pub/linux/kde">ftp://linux.unipv.it/pub/linux/kde</ulink></para>
</listitem>
<listitem>
<para> <ulink url="ftp://sunsite.icm.edu.pl/pub/unix/kde">ftp://sunsite.icm.edu.pl/pub/unix/kde</ulink></para>
</listitem>
<listitem>
<para> <ulink url="ftp://ftp.chialpha.org/pub/kde">ftp://ftp.chialpha.org/pub/kde</ulink></para>
</listitem>
<listitem>
<para> <ulink url="ftp://ftp.blaze.net.au/pub/kde">ftp://ftp.blaze.net.au/pub/kde</ulink></para>
</listitem>
<listitem>
<para> <ulink url="ftp://ftp.gwdg.de/pub/x11/kde/">ftp://ftp.gwdg.de/pub/x11/kde/</ulink></para>
</listitem>
<listitem>
<para> <ulink url="ftp://ops.linux.co.za/pub/Linux/kde">ftp://ops.linux.co.za/pub/Linux/kde</ulink></para>
</listitem>
<listitem>
<para> <ulink url="ftp://ftp.uni-erlangen.de/pub/Linux/MIRROR.KDE">ftp://ftp.uni-erlangen.de/pub/Linux/MIRROR.KDE</ulink></para>
</listitem>
<listitem>
<para> <ulink url="ftp://ftp.dataplus.se/pub/linux/kde">ftp://ftp.dataplus.se/pub/linux/kde</ulink></para>
</listitem>
<listitem>
<para> <ulink url="ftp://ftp.tvnet.hu/pub/kde">ftp://ftp.tvnet.hu/pub/kde</ulink></para>
</listitem>
<listitem>
<para> <ulink url="ftp://canine.resnet.gatech.edu/pub/kde">ftp://canine.resnet.gatech.edu/pub/kde</ulink></para>
</listitem>
<listitem>
<para> <ulink url="ftp://ftp.fh-heilbronn.de/pub/mirrors/kde">ftp://ftp.fh-heilbronn.de/pub/mirrors/kde</ulink></para>
</listitem>
<listitem>
<para> <ulink url="ftp://ftp.appl-opt.physik.uni-essen.de/pub/linux/kde">ftp://ftp.appl-opt.physik.uni-essen.de/pub/linux/kde</ulink></para>
</listitem>
<listitem>
<para> <ulink url="ftp://ftp.dsnet.it/pub/internet/unix/Linux/kde">ftp://ftp.dsnet.it/pub/internet/unix/Linux/kde</ulink></para>
</listitem>
<listitem>
<para> <ulink url="ftp://sunsite.mff.cuni.cz/X11/Desktops/KDE">ftp://sunsite.mff.cuni.cz/X11/Desktops/KDE</ulink></para>
</listitem>
<listitem>
<para> <ulink url="ftp://sunsite.icm.edu.pl/pub/unix/kde/">ftp://sunsite.icm.edu.pl/pub/unix/kde/</ulink></para>
</listitem>
<listitem>
<para> <ulink url="ftp://ftp.fh-dortmund.de/pub/unix/kde.mirror">ftp://ftp.fh-dortmund.de/pub/unix/kde.mirror</ulink></para>
</listitem>
<listitem>
<para> <ulink url="ftp://kde.flash.net/pub/unix/kde/">ftp://kde.flash.net/pub/unix/kde/</ulink></para>
</listitem>
<listitem>
<para> <ulink url="ftp://ftp.cs.us.es/pub/Linux/kde/">ftp://ftp.cs.us.es/pub/Linux/kde/</ulink></para>
</listitem>
<listitem>
<para> <ulink url="ftp://ftp.isis.nsu.ru/mirrors/kde/">ftp://ftp.isis.nsu.ru/mirrors/kde/</ulink></para>
</listitem>
<listitem>
<para> <ulink url="ftp://belief.unix.cslab.tuwien.ac.at/pub/kde">ftp://belief.unix.cslab.tuwien.ac.at/pub/kde</ulink></para>
</listitem>
<listitem>
<para> <ulink url="ftp://clio.unice.fr/">ftp://clio.unice.fr/</ulink></para>
</listitem>
<listitem>
<para> <ulink url="ftp://ftp.iinet.net.au/pub/kde/">ftp://ftp.iinet.net.au/pub/kde/</ulink></para>
</listitem>
<listitem>
<para> <ulink url="ftp://ftp.lbi.ro/pub/Linux/KDE">ftp://ftp.lbi.ro/pub/Linux/KDE</ulink></para>
</listitem>
<listitem>
<para> <ulink url="ftp://ftp.linux.org.au/pub/linux/kde/">ftp://ftp.linux.org.au/pub/linux/kde/</ulink></para>
</listitem>
<listitem>
<para> <ulink url="ftp://ftp.kreonet.re.kr/pub/tools/X11/kde/">ftp://ftp.kreonet.re.kr/pub/tools/X11/kde/</ulink></para>
</listitem>
<listitem>
<para> <ulink url="ftp://sundog.v-wave.com/pub/kde/">ftp://sundog.v-wave.com/pub/kde/</ulink></para>
</listitem>
<listitem>
<para> <ulink url="ftp://sunsite.bilkent.edu.tr/pub/linux/kde">ftp://sunsite.bilkent.edu.tr/pub/linux/kde</ulink></para>
</listitem>
<listitem>
<para> <ulink url="ftp://ftp.fisica.ist.utl.pt/pub/mirrors/kde">ftp://ftp.fisica.ist.utl.pt/pub/mirrors/kde</ulink></para>
</listitem>
<listitem>
<para> <ulink url="ftp://ftp.rz.uni-wuerzburg.de/pub/unix/kde">ftp://ftp.rz.uni-wuerzburg.de/pub/unix/kde</ulink></para>
</listitem>
</itemizedlist>
</para>

<para>Eine aktuelle Aufstellung ist in der <ulink url="http://www.kde.org/mirrors.html">KDE-Spiegelserverliste</ulink> zu
finden.</para>
</sect1>

<sect1 id="linuxdistributionen">
<title>Gibt es Linuxdistributionen, die KDE enthalten?</title>

<para>Die großen Linux-Distributionen enthalteb bereits KDE. Da das Erstellen einer Distribution etwas Zeit
benötigt, kann es sein, daß sie nicht immer die neuste Version enthalten, aber für den Anfang oder um das
Laden aus dem Internet zu sparen, bieten sie einen guten Ausganspunkt.</para>

<para>Unten finden Sie einige Distributionen, die KDE enthalten. Sie finden eine aktuelle Aufstellung in der
<ulink url="http://www.kde.org/kdeships.html">KDE Distributionsliste</ulink>.</para>

<para><itemizedlist>
<listitem>
<para> <ulink url="http://www.redhat.de">Red Hat Linux</ulink></para>
</listitem>
<listitem>
<para> <ulink url="http://www.suse.de">S.u.S.E. Linux</ulink></para>
</listitem>
<listitem>
<para> <ulink url="http://www.delix.de">DLD Linux</ulink></para>
</listitem>
<listitem>
<para> <ulink url="http://www.caldera.com/">Caldera OpenLinux</ulink></para>
</listitem>
<listitem>
<para> <ulink url="http://www.mklinux.apple.com/">MkLinux</ulink></para>
</listitem>
<listitem>
<para> <ulink url="http://www.linux-mandrake.com/">Linux-Mandrake</ulink></para>
</listitem>
<listitem>
<para> <ulink url="http://www.stampede.org/">Stampede Linux</ulink></para>
</listitem>
<listitem>
<para> <ulink url="http://www.linuxppc.org/">LinuxPPC</ulink></para>
</listitem>
</itemizedlist>
</para>

<para>Zusätzlich gibt es einige Computerzeitschriften, die eine CD mit KDE enthalten:</para>

<para><itemizedlist>
<listitem>
<para> <ulink url="http://www.chip.de">Chip</ulink> (auf deutsch)</para>
</listitem>
<listitem>
<para> <ulink url="http://www.linux-france.com/dream">Dream</ulink> (auf französisch)</para>
</listitem>
<listitem>
<para> <ulink url="http://www.pcquest.com">PC Quest</ulink> (auf englisch)</para>
</listitem>
</itemizedlist>
</para>
</sect1>

<sect1 id="was-ist-die-aktuelle-version">
<title>Was ist aktuelle Version?</title>

<para>Die aktuelle stabile Version ist 1.1.1.</para>
</sect1>

<sect1 id="schnappshuesse">
<title>Wo finde ich KDE-Schnappschüsse?</title>

<para>Unter <ulink url="ftp://ftp.kde.org/pub/kde/unstable/CVS/snapshots">ftp://ftp.kde.org/pub/kde/unstable/CVS/snapshots</ulink> sind die aktuellen Schnappschüsse zu
finden. Sie können jedoch auch ein CVS-Programm verwenden, um immer den neusten Schnappschuß zu erhalten. Wie
Sie das machen, können Sie der <ulink url="http://www.kde.org/cvsup.html">KDE-cvsup-Seite</ulink> entnehmen.</para>

<para>Übrigens: Falls Sie wissen wollen, was CVS ist, finden Sie unter <link linkend="was-ist-CVS">Was ist CVS</link> eine
Erklärung.</para>
</sect1>

<sect1 id="wo-bekomme-ich-qt">
<title>Wo bekomme ich Qt?</title>

<para>Qt ist ein Produkt der norwegischen Firma Troll Tech. Die aktuelle Qt Version erhält von ihrem FTP-Server:</para>

<para><ulink url="ftp://ftp.troll.no">Troll Tech FTP-Server</ulink></para>

<para>Sie sollten jedoch Qt auch von den oben angegebenen KDE-Spiegelserver erhalten können. Zudem ist Qt auch bei den
meisten neueren Linux-Distributionen enthalten. Unter <link linkend="Systemvoraussetzungen">Systemvoraussetzungen</link>
steht, welche Qt Version Sie benötigen.</para>
</sect1>

<sect1 id="was-ist-qt-eigentlich">
<title>Was ist Qt eigentlich?</title>

<para>Qt ist eine C++ basierte Klassenbibliothek, um Benutzerschnittstellen zu erstellen. Es stellt die meisten
Oberflächenelemente  <emphasis>(widgets)</emphasis> zur Verfügung, die man in KDE-Anwendungen sieht: Menüs, Knöpfe,
Schiebebalken usw. Qt ist eine Systemübergreifende Bibliothek, die es Ihnen erlaubt Programme zu schreiben,
die unter Unix und unter Windows kompilieren. Sie können mehr zu Qt erfahren unter
<ulink url="http://www.troll.no">http://www.troll.no</ulink>.</para>
</sect1>
</chapter>

<chapter id="Installationsanweisungen">
<title>Installationsanweisungen</title>

<para>Die folgende Installationsanweisungen gelten für die KDE-Version 1.0. Bei späteren Versionen sollten Sie die
README- und INSTALL-Dateien konsultieren, die mit dem Paketen mitgeliefert werden. Bitte lesen Sie diese
gründlich durch, und versuchen Sie sich selbst zu helfen, wenn etwas schief geht. Falls Sie weitergehende
Unterstützung benötigen, erwägen Sie eine KDE-E-Mailliste (siehe unter
<ulink url="http://www.kde.org/contact.html">E-Maillisten</ulink> den KDE-Internetseiten) zu abonnieren oder
sich an eine Nachrichtengruppe zu wenden.</para>

<sect1 id="an-die-umsteiger">
<title>An die Umsteiger</title>

<para>So Sie haben die Gerüchte gehört oder die Bildschirmphotos gesehen. Und jetzt können Sie es kaum erwarten KDE
zu erhalten. Aber Sie wissen fast nichts über das ganze &raquo;alternative BS&laquo;-Geschäft. Keine Angst,
Sie müssen nur etwas (vielleicht auch etwas mehr) zu lesen, das ist alles.</para>

<para>KDE läuft (noch?) nicht auf Windows 95/98/NT oder OS/2. Um KDE laufen zu lassen benötigen Sie ein Unixsystem.
Siehe <link linkend="platform">Auf welchen Systemen kann ich das Laufen der KDE erwarten?</link> für Details.</para>

<para>Nehmen wir an, Sie haben sich entschieden Linux zu installieren. Sie können es entweder aus dem Internet laden
oder ein CD-Rom-Paket kaufen, daß die Distribution Ihrer Wahl enthält. Folgende Verweise könnten nützlich
sein:</para>

<para><itemizedlist>
<listitem>
<para> <ulink url="http://www.control-escape.com/">Control-Escape:  Alternative Software, Linux Help</ulink> </para>
</listitem>
<listitem>
<para> <ulink url="http://www.linux.org/index.html">The Linux Home  Page at Linux Online</ulink></para>
</listitem>
<listitem>
<para> <ulink url="http://searchlinux.com/">SearchLinux Home</ulink></para>
</listitem>
<listitem>
<para> <ulink url="http://www.cheek.com/linux/kb/">Linux Knowledge  Base</ulink></para>
</listitem>
<listitem>
<para>Usenet-Nachrichtengruppen wie <literal remap="tt">comp.os.linux.*</literal> oder <literal remap="tt">de.comp.os.unix.linux.*</literal></para>
</listitem>
</itemizedlist>
</para>

<para>Um KDE auf Linux zum Laufen zu bringen, müssen Sie zuerst X einrichten. X ist der <emphasis>de-facto</emphasis>-Standard der
graphischen Oberfläche unter Unixsystemen. Schauen Sie sich dazu auch folgen Seiten an:</para>

<para><itemizedlist>
<listitem>
<para> <ulink url="http://www.x.org/">Das X Window System</ulink></para>
</listitem>
<listitem>
<para> <ulink url="http://www.xfree86.org/">XFree86(TM): Home Page</ulink></para>
</listitem>
<listitem>
<para> Usenet-Nachrichtengruppen wie <literal remap="tt">comp.os.linux.x</literal>, <literal remap="tt">comp.windows.x.*</literal> oder <literal remap="tt">de.comp.os.unix.x11</literal>.</para>
</listitem>
</itemizedlist>
    </para>

<para>Nun sind Sie schlußendlich bereit für die KDE-Installation. Bitte lesen Sie beim nächsten Absatz weiter.
Um KDE zu erhalten, siehe <link linkend="woher-bekomme-ich-die-kde">Woher bekomme ich die KDE?</link>. Zu guter Letzt:
Zögern Sie nicht, die KDE <link linkend="KDEmailinglists">E-Maillisten</link> und <link linkend="KDEnewsgroups">Nachrichtengruppen</link> zu verwenden; bedenken Sie jedoch auch, daß es zwar keine zu dummen Fragen gibt,
daß manche jedoch zu dumm sind, um sie zu beantworten. Dies gilt insbesondere für Fragen, die in dieser FAQ
beantwortet werden.</para>

<para>Viel glück und haben Sie Spaß!</para>
</sect1>

<sect1 id="verfuegbare-paketformate">
<title>Verfügbare Paketformate</title>

<para>Das KDE-Team stellt sechs verschiedene Paketformate zur Verfügung: RPMs, Debian-Pakete und
.tgz-(tar.gz-)Archive, jeweils als Quelltext- und Binärpaket. Als erstes werden in der Regel die Quelltext
.tgz-Dateien veröffentlicht, die anderen Formate folgen jedoch wenig später. Siehe auch <link linkend="bzip2">Wie entpacke ich tar-Archive mit der &raquo;bz2&laquo;-Erweiterung?</link>.
Zusätzlich werden auch pkg-Pakete für Solaris 2.6 and 7 erstellt.</para>

<para>Der Installationsvorgang hängt vom Paketformat ab, das Sie gewählt haben.
Das Vorgehen nach der Installation ist wieder paketunabhängig. Falls Sie ein
unerfahrener Unix-Benutzer sind und ein RPM-basiertes System haben, ist es wohl
am besten, die RPM-Pakete des Distributionserstellers zu verwenden. Zu mindest
Caldera, Delix und SuSE bieten Binärpakete auf ihren FTP-Servern an.</para>

<para>Falls Sie besondere Konfigurationsoptionen benötigen (beispielsweise benutzen
Sie Shadow-Passworte und möchten Bildschirmschoner verwenden), ist es meist am
besten die Quelltextpakete zu nehmen und das K Desktop Environment selbst zu
kompilieren. Binäre RPM-Pakete für Distributionen, die offiziell keine
KDE-Pakete anbieten, finden sich in der  <ulink url="ftp://ftp.kde.org/pub/kde/stable/1.0/contrib/distribution">contrib</ulink>-Sektion von ftp.kde.org sobald sie verfügbar sind.</para>

<para><ulink url="mailto:bill.mote@bigfoot.com">Bill Mote</ulink> hat eine Internetseite
erstellt, mit dem Titel &raquo;KDE 1.1 Installation via RPM&laquo;.  
Sie ist unter <ulink url="http://home.fuse.net/bmote/kde.htm">http://home.fuse.net/bmote/kde.htm</ulink> zu finden.</para>
</sect1>

<sect1 id="Systemvoraussetzungen">
<title>Systemvoraussetzungen</title>

<para>Für KDE 1.0 benötigen Sie Qt Bibliotheksversion 1.33 oder höher, während Sie Qt 1.42 oder höher für KDE 1.1
benötigen. Verwenden Sie jedoch nicht Qt Version 2.0 oder höher. Sie benötigen auch die Header-Dateien, wenn
Sie KDE selbst kompilieren wollen. Diese erhalten Sie kostenlost unter
<ulink url="http://www.troll.no/dl">http://www.troll.no/dl</ulink>.
Sie benötigen zusätzlich libgr, welches in den meisten Distributionen enthalten sein sollte. Stellen Sie
weiterhin sicher, daß Ihr lokales loopback-Gerät richtig eingestellt ist.</para>
</sect1>

<sect1 id="beschreibung-der-basispakete">
<title>Beschreibung der Basispakete</title>

<para>Die Basisdistribution besteht gegenwärtig aus elf Paketen. Einige sind obligatorisch und andere optional.
Jedes Paket ist in den vorher beschrieben Paketformaten verfügbar.</para>

<para><variablelist>
<varlistentry>
<term>kdesupport</term>
<listitem>
<para><emphasis remap="it">(EMPFOHLEN)</emphasis></para>
<para>Dieses Paket besteht aus Zusatzbibliotheken, die nicht im Rahmen des KDE-Projektes geschrieben wurden, aber
trotzdem benötigt werden. Falls Sie bereits die Bibliotheken (libgif, libjpeg, libmime, libuu, libgdbm) dieses
Paketes in der benötigten Version besitzen, benötigen Sie dieses Paket nicht. Wenn Sie Zweifel haben,
installieren Sie es. Für die Debianpakete würd dieses Paket benötigt.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>kdelibs</term>
<listitem>
<para><emphasis remap="it">(OBLIGATORISCH)</emphasis></para>
<para>Dieses Paket enthält die gemeinsambenutzen Bibliotheken, die vonn allen KDE-Anwendungen benötigt werden.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>kdebase</term>
<listitem>
<para><emphasis remap="it">(OBLIGATORISCH)</emphasis></para>
<para>Dieses Paket enthält die Basisanwendungen, die das Herz des K Desktop Environment formen, wie beispielsweise
der Fenstermanager, der Terminalemulator, das Kontrollzentrum, den Dateimanager und das Panel.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>kdegames</term>
<listitem>
<para><emphasis remap="it">(OPTIONAL)</emphasis></para>
<para>Verschiedene Spiele, wie Mahjoon, Schlangenrennen, Asteroiden und Tetris.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>kdegraphics</term>
<listitem>
<para><emphasis remap="it">(OPTIONAL)</emphasis></para>
<para>Verschiedene graphikbezogene Programme, wie PostScript&lsqb;TM]- und DVI-Betrachter und ein
Zeichenprogramm.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>kdeutils</term>
<listitem>
<para><emphasis remap="it">(OPTIONAL)</emphasis></para>
<para>Verschiedene Desktopwerkzeuge, wie ein Taschenrechner, Editor oder andere kleine und nützliche Programme.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>kdemultimedia</term>
<listitem>
<para><emphasis remap="it">(OPTIONAL)</emphasis></para>
<para>Multimediaanwendungen wie ein CD-Spieler und ein Mischregler.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>kdenetwork</term>
<listitem>
<para><emphasis remap="it">(OPTIONAL)</emphasis></para>
<para>Internetanwendungen. Zur Zeit bestehend aus dem E-Mailprogramm, dem Newsleser und verschiedenen anderen
netzwerkbezogenen Anwendungen.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>kdeadmin</term>
<listitem>
<para><emphasis remap="it">(OPTIONAL)</emphasis></para>
<para>Programme für die Systemadministration. Enthält gegenwärtig z.B. den Benutzermanager und der
System-V-Runleveleditor.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>kdetoys</term>
<listitem>
<para><emphasis remap="it">(OPTIONAL)</emphasis></para>
<para>Spielzeug!</para>
</listitem>
</varlistentry>
<varlistentry>
<term>korganizer</term>
<listitem>
<para><emphasis remap="it">(OPTIONAL)</emphasis></para>
<para>Ein Schreibtisch ohne Terminkalender ist kein Schreibtisch, stimmt's?</para>
</listitem>
</varlistentry>
</variablelist>
</para>

<para>kdesupport (falls benötigt) sollte als erstes installiert werden. Das nächste (oder erste) Paket sollte
kdelibs sein. Die Reihenfolge der anderen Pakete ist egal.</para>
</sect1>

<sect1 id="installationsbeschreibungen">
<title>Installationsbeschreibungen für die verschiedenen Paketformat</title>

<para>Bitte lesen Sie auch die README- und INSTALL-Dateien, falls sie verfügbar sind.</para>

<sect2 id="debian">
<title>Installation der Debian-Pakete</title>

<para>Die Debian-Pakete werden gemäß des kommenden FHS <emphasis>(file hierarchy
standard)</emphasis> installiert.</para>

<para><emphasis remap="it">Um die Debian-Pakete zu installieren:</emphasis></para>

<para><itemizedlist>
<listitem>
<para>Werden Sie Superuser (root)</para>
</listitem>
<listitem>
<para>Führen Sie aus: dpkg -i &lt;Paketname&gt;.deb</para>
</listitem>
</itemizedlist>
</para>

<para>für alle Pakete, die Sie installieren wollen.</para>
</sect2>

<sect2>
<title>Installation der RPM-Pakete</title>

<para>Die RPM-Pakete werden in /opt/kde installiert.</para>

<para><emphasis remap="it">Um binäre RPM-Pakete zu installieren:</emphasis>
<itemizedlist>
<listitem>
<para>Werden Sie Superuser (root)</para>
</listitem>
<listitem>
<para>Starten Sie: rpm -ivh &lt;Paketname&gt;.rpm</para>
</listitem>
</itemizedlist>
</para>

<para><emphasis remap="it">Um ein binär RPM aus einem Quelltext RPM zuerstellen und es zu installieren,
tun Sie das folgende:</emphasis>
<itemizedlist>
<listitem>
<para> Werden Sie Superuser (root)</para>
</listitem>
<listitem>
<para> Führen Sie aus: rpm -ivh &lt;Paketname&gt;.src.rpm</para>
</listitem>
<listitem>
<para> cd /usr/src/redhat/SPECS</para>
</listitem>
<listitem>
<para> rpm -bb &lt;Paketname&gt;.spec</para>
</listitem>
<listitem>
<para> cd ../RPMS/i386 (oder welche andere Achitektur Sie verwenden)</para>
</listitem>
<listitem>
<para> rpm -ivh &lt;Paketname&gt;.i386.rpm</para>
</listitem>
</itemizedlist>
</para>
</sect2>

<sect2>
<title>Installation der Quelltext .tar.gz-Dateien</title>

<para>Die Quelltext .tgz-Pakete werden standardgemäß in /usr/local/kde installiert.
Sie können dies überschreiben, indem Sie die &raquo;--prefix&laquo;-Option des
Konfigurationsskriptes verwenden.</para>

<para><itemizedlist>
<listitem>
<para>Entpacken Sie das Paket mit: tar xvzf &lt;Paketname&gt;.tar.gz</para>
</listitem>
<listitem>
<para>Wechseln Sie in das Paketverzeichnis: cd &lt;Paketname&gt;</para>
</listitem>
<listitem>
<para>Konfigurieren Sie das Paket: ./configure
<note>
<para>Einige Pakete (insbesonde kdebase) besitzten spezielle Konfigurationsoptionen
die für Ihre Installation anwendbar sein können. Geben Sie
&raquo;./configure --help&laquo; ein, um die verfügbaren Option angezeigt
zu bekommen.</para>
</note>
</para>
</listitem>
<listitem>
<para>Erstellen des Paketes: make
</para>
</listitem>
<listitem>
<para>Installieren des Paketes: su -c "make install" (falls Sie noch nicht root
sind; ansonsten: &raquo;make install&laquo;).
</para>
</listitem>
</itemizedlist>
</para>
</sect2>

<sect2>
<title>Installation binärer .tar.gz-Dateien</title>

<para>Die binären .tar.gz-Pakete werden in /opt/kde installiert.</para>

<para><itemizedlist>
<listitem>
<para>Werden Sie Superuser (root)</para>
</listitem>
<listitem>
<para>cd /</para>
</listitem>
<listitem>
<para>tar xvzf &lt;Paketname&gt;.tar.gz</para>
</listitem>
</itemizedlist>
</para>
</sect2>
</sect1>

<sect1 id="vorgehensweise-nach-der-installation">
<title>Vorgehensweise nach der Installation</title>

<para>First of all, please make sure that you have added KDE's binary
installation directory (e.g. /opt/kde/bin) to your PATH and KDE's
library installation directory to your LD&lowbar;LIBRARY&lowbar;PATH (only necessary
on systems that do not support rpath; on Linux ELF, it should work
without).  This environment variable may be called differently on some
systems, e.g. it is called SHLIB&lowbar;PATH on IRIX.  Then set the
environment variable KDEDIR to the base of your KDE tree,
e.g. /opt/kde. </para>

<para>Please bear in mind that it is unwise to set LD&lowbar;LIBRARY&lowbar;PATH blindly.
In the vast majority of cases it's unnecessary and can do more harm
than good.  There's a web page written by <ulink url="mailto:barr@cis.ohio-state.edu">Dave Barr</ulink> explaining the
evils of LD&lowbar;LIBRARY&lowbar;PATH and it can be found at <ulink url="http://www.cis.ohio-state.edu/~barr/ldpath.html">http://www.cis.ohio-state.edu/~barr/ldpath.html</ulink>.</para>

<para>Even though you can use most of the KDE applications simply by calling
them, you can only benefit fully from KDE's advanced features if you use
the KDE window manager KWM and its helper programs.</para>

<para>In order to make it easy for you, we have provided a simple script called
startkde which gets installed in $KDEDIR/bin and is therefore in your path.</para>

<para>Edit the file .xinitrc in your home directory (make a backup copy first!),
remove everything that looks like calling a window manager, and insert
startkde instead.  Restart X.  If you use kdm/xdm, you will have to edit
the file .xsession instead of .xinitrc.  And if there is no
.xinitrc or .xsession in your home directory, simply create a new one
with just one line containing "startkde" (without the quotes!).  Note: 
some systems (notably Redhat Linux) uses .Xclients instead.  </para>

<para>This should present you with a new shining KDE desktop. You can now
start to explore the wonderful world of KDE.  In case you want to read
some documentation first, there is a highly recommended 
<ulink url="http://www.kde.org/documentation/en/general/quickstart/index.html">quickstart guide</ulink> available. Furthermore, every application has
an online help that is available via the help menu.</para>
</sect1>

<sect1 id="sgi-irix">
<title>Micro-WieGeht's: Kompilieren von KDE 1.1.1 auf SGI Irix 6.x</title>

<para><ulink url="mailto:berry@ieeecs.concordia.ca">Chris Sterritt</ulink> hat folgende aktualisierte Fassung der
micro-WieGeht's (verändertes Layout) an comp.windows.x.kde gesendet:</para>

<para>This is a (blatant) modification of the original Micro-HOWTO posted by
<ulink url="mailto:sterritt@mrj.com">Chris Sterritt</ulink>.  This is
valid for KDE-1.1.1 running on Irix 6.5.  I haven't attempted it on
other platforms.  There are some items of contention:  I get many,
many warnings about Qt definitions being preempted, about libkdecore
definitions being preempted, etc.  (So many definitions have been
preempted I could have written a dictionary), the i18n stuff doesn't
work (while it did in v1.0) and kikbd chokes in konsole (it works fine
otherwise).  Any comments or questions can be directed to
<ulink url="mailto:berry@ieeecs.concordia.ca">berry@ieeecs.concordia.ca</ulink>.  I will also keep a copy of this
HOWTO on my personal web-page: <ulink url="http://alcor.concordia.ca/~c_berry/">http://alcor.concordia.ca/~c_berry/</ulink>.</para>

<para>Also, if this isn't your cup of tea, I have uploaded binaries of
kde-1.1.1 and egcs-1.1.2 to <ulink url="ftp://ftp.cmc.ec.gc.ca/pub/hbc/sgi/">ftp://ftp.cmc.ec.gc.ca/pub/hbc/sgi/</ulink>.  KDE has been compiled
with shared libraries, so if you don't have libstdc++.so.2.9.0 I would
suggest downloading the egcs binary as well. Please also download and
&lowbar;read&lowbar; the README in the directory, as it contains important
installion information. </para>

<para>Finally, neither I nor Environment Canada accept any responsibility vis
a vis the worthiness of these instructions.  They have worked for me. 
If they work for you, that's good, if they don't work, I can't help you,
neither can anybody at EC.  Note that several things don't work the way
they are supposed to work.  If you find a way around these problems, let
someone else know.  I personally won't be able to test any fixs after
August 20, 1999 as I will be returning to school (and using SunOS).  </para>

<para>Viel Spaß!</para>

<para><orderedlist><listitem>
<para>Installieren Sie Qt 1.42 oder höher.</para>
</listitem>
<listitem>
<para>Ich installiere KDE als Benutzer (nicht als root), so habe ich eine
KDEDIR-Variablel, die nicht auf /usr/local/ (oder was auch immer der Standard
ist) verweist. Somit werde ich es unten erwähnen, aber es kann sein, daß Sie es
nicht benötigen. Auch besitzt SGI eine jpeg- und eine png-Bibliothek, aber sie
sind veraltet oder sonstwie falsch. Somit müssen Sie den libpng- und
libgz-Quelltext suchen (jpeg kommit mit kdesupport); ich habe es
als Quelltext-RPM auf einem der RedHat-FTP-Spiegelserver gefunden.</para>
</listitem>
<listitem>
<para> Get egcs 1.1.1 or later and compile it with '-fsquangle' support
on.  This is because SGI's assembler can't handle the huge object names
produced by normal g++, and gas doesn't evidently work yet for SGIs. 
You'll have to build gcc's libraries using this binary as well.  Make
sure your PATH gets this compiler only (if you have another gcc
installed somewhere).  When I do a 'g++ -v' I get:
<screen>gcc version egcs-2.91.60 19981201 (egcs-1.1.1 release)
</screen>
</para>
</listitem>
<listitem>
<para> Do a 
<screen>setenv LDFLAGS " "
</screen>

because the 'configure' scripts insist on trying 'g++ -s' when compiling
a test program, which always fails on the SGIs.</para>
</listitem>
<listitem>
<para> Unpack 'kdesupport' and enter its directory.  Run its configure
with "--prefix" if you need to:
<screen>./configure --prefix=$KDEDIR --x-includes=/usr/include/X11 \
--x-libraries=/usr/lib32 --with-qt-includes=/opt/kde-1.1.1 \
--with-qt-libs=/opt/kde-1.1.1 --enable-shared
</screen>

Modify this to reflect your reality.  In my case, I have Qt stuck in
the same dir as KDE, so I had to explicitly name the includes and libs
dir.  Sometimes the configure will still not see the Qt includes dir. 
Source your .login file to correct this (You did set up your .login file
as the instructions in the Qt installation asked?).
</para>
</listitem>
<listitem>
<para> Run the script (which I'll include below) as follows:
<screen>find . -name Makefile -exec ../FixMakesSq {} \;
</screen>

This fixes all the compile lines so that all the 'replicated'
libraries (jpeg and png) are replaced with full paths so they won't be
linked with the SGI ones. Note: In the original HOWTO, -fsquangle was
added to each makefile.  This caused compilation errors.  I found that
it was really only needed in one makefile.  It will be noted below.</para>

<para>Here's the FixMakesSq script:
<screen>#!/bin/perl -ni.bak
 
if ((/-lpng/) || (/-ljpeg/))
{
    if (/^(.*)-lpng(.*)$/)
    {
        $b4 = $1;
        $af = $2;
        print "$b4 /path/to/KDE/libs/libpng.a $af\n";
    }
    if (/^(.*)-ljpeg(.*)$/)
    {
        $b4 = $1;
        $af = $2;
        print "$b4 /path/to/KDE/libs/libjpeg.a $af\n";
    }
}
        
#NOTE!! Uncomment this section if you want to add
#-D_LANGUAGE_C_PLUS_PLUS to all 
#makefiles.  I personally have not tried this, but it should not break 
#anything.
# Alternately, add the flag in the places noted below.

#elsif (/cxxflags\s*=(.*)$/i)
#{
#    print "CXXFLAGS =  -D_LANGUAGE_C_PLUS_PLUS $1\n";
#}
else
{
    print;
}
</screen>
</para>
</listitem>
<listitem>
<para> Do:
<screen>gmake
gmake install
</screen>
</para>
</listitem>
<listitem>
<para> Go to the 'libz' source directory, do:
<screen>./configure --prefix=$KDEDIR
gmake
gmake install
</screen>
</para>
</listitem>
<listitem>
<para> Go to the 'libpng' source directory, do:
<screen>./configure --prefix=$KDEDIR
gmake
gmake install
</screen>
</para>
</listitem>
<listitem>
<para> Unpack 'kdelibs' and enter its directory.  Note the
'--enable-new-stuff' argument to ./configure (this might not be needed,
but nothing complains if you use it): 
<screen>./configure --prefix=$KDEDIR --x-includes=/usr/include/X11 \
--x-libraries=/usr/lib32 --with-qt-includes=/opt/kde-1.1.1 \
--with-qt-libs=/opt/kde-1.1.1 --enable-shared --enable-new-stuff
find . -name Makefile -exec ../FixMakesSq {} \;
</screen>
</para>
</listitem>
<listitem>
<para> Find 'kprocctrl.cpp', and fix the Makefile in that directory. Only
if you did not uncomment the section that accomplishes this in the
FixMakesSq script, add '-D&lowbar;LANGUAGE&lowbar;C&lowbar;PLUS&lowbar;PLUS' to the CXXFLAGS line.
This makes it get the right definition for signal functions (has an
'int' arg).</para>
</listitem>
<listitem>
<para> Find 'addressbook.cc', and fix the Makefile in that directory. Add
'-fsquangle'  to the CXXFLAGS line. This makes it able to handle the
huge name that's going to pop out.
<screen>gmake
gmake install
</screen>
</para>
</listitem>
<listitem>
<para> Unpack 'kdebase' and enter its directory.  Do:
<screen>./configure --prefix=$KDEDIR  --x-includes=/usr/include/X11 \
--x-libraries=/usr/lib32 --with-qt-includes=/opt/kde-1.1.1 \
--with-qt-libs=/opt/kde-1.1.1 --enable-shared 
find . -name Makefile -exec ../FixMakesSq {} \;
</screen>
</para>
</listitem>
<listitem>
<para> Fix 'memory&lowbar;sgi.cpp' (do a find from 'kdebase' directory).  I just
&num;ifdef'd out the contents of the whole function... it doesn't compile on
my machine, and I never open that part of KPanel anyway :-).</para>
</listitem>
<listitem>
<para> Fix 'TEShell.C' (in kdebase-1.1.1/konsole/src/ directory).  It is
the operation for getting a pty for the new Konsole. Alas, it was not
written with Irix in mind, and needs to be patched with the diff
included below:
<screen>*** TEShell.C   Mon Apr 12 00:12:37 1999
--- /users/dor/aspg/ber/data/kdedown/kdebase-1.1.1/konsole/src/TEShell.C
Wed Jul 14 15:15:35 1999
***************
*** 169,174 ****
--- 169,177 ----
    pid_t pid = waitpid(-1,&amp;status,WNOHANG);
    Shell* sh = shells.find(pid);
    if (sh) { shells.remove(pid); sh-&gt;doneShell(status); }
+ #if defined(sgi)
+   signal(SIGCHLD,catchChild);
+ #endif
  }
  
  void Shell::doneShell(int status)
***************
*** 234,239 ****
--- 237,252 ----
        }
      }
    }
+ #endif
+ 
+ #if defined(sgi) /* Irix */
+  
+   needGrantPty = FALSE;
+   char* line;
+   line = _getpty(&amp;ptyfd, O_RDWR|O_NDELAY, 0600, 0);
+   strcpy(ptynam,"/dev/ptc");
+   strcpy(ttynam,line);
+  
  #endif
  
    if (ptyfd &lt; 0) // Linux, FIXME: Trouble on other systems?

gmake
gmake install
</screen>
</para>
</listitem>
<listitem>
<para> Unpack 'kdeutils'. 
<screen>./configure --prefix=$KDEDIR  --x-includes=/usr/include/X11 \
--x-libraries=/usr/lib32 --with-qt-includes=/opt/kde-1.1.1 \
--with-qt-libs=/opt/kde-1.1.1 --enable-shared 
find . -name Makefile -exec ../FixMakesSq {} \;
</screen>
</para>
</listitem>
<listitem>
<para> Find 'kcalc&lowbar;core.cpp' and fix its Makefile like you did for
'kprocctrl.cpp' above. 
<screen>gmake
gmake install
</screen>
</para>
</listitem>
<listitem>
<para> Unpack 'kdegames', 'kdegraphics', and 'kdetoys' and for each one,
enter its directory and do: 
<screen>./configure --prefix=$KDEDIR  --x-includes=/usr/include/X11 \
--x-libraries=/usr/lib32 --with-qt-includes=/opt/kde-1.1.1 \
--with-qt-libs=/opt/kde-1.1.1 --enable-shared \
find . -name Makefile -exec ../FixMakesSq {} \;
gmake
gmake install
</screen>
</para>
</listitem>
<listitem>
<para> This step is optional for KDE-1.1.  I don't think it is necessary
for KDE-1.1.1.  Knotes has never crashed on me.  I have left it here for
completeness . Find where the knotes directory is. Go there, do a 'make
clean', then change the CXXFLAGS in its Makefile. The CXXFLAGS line has
'-O2', change that to '-g'. Then do a 'make' and 'make install'. The
reason for this is that I found knotes crashed within a few minutes of
it starting up; however, when I recompiled it with '-g' (i.e., debugging
support) instead of '-O2' (optimization) it ran fine. Go figure :-). </para>
</listitem>
</orderedlist>
</para>

<para>And that's it.  You should now be able to run KDE.</para>
</sect1>

<sect1 id="suse-yast">
<title>Installing the RPMs with SuSe's YaST makes the rpm database unusable. What can I do?</title>

<para>If you do get</para>

<para><screen>   error -2 reading header: Unknown error
</screen>
</para>

<para>you have to update rpm:</para>

<para><screen>rpm -U ftp://ftp.suse.com/pub/suse_update/suse51/rpm/rpm.rpm
</screen>
</para>

<para>and you should also update YaST</para>

<para><screen>rpm -U ftp://ftp.suse.com/pub/suse_update/suse51/a1/yast.rpm
</screen>
</para>

<para> 
The packages were built using
rpm-2.4.12 and cannot be installed by some old versions of rpm.
this mostly happens to SuSe Linux users. Version 5.0 of their
distribution ships with rpm-2.4.1   </para>

<para>You can find out which version your rpm is with:</para>

<para><screen>rpm -qi rpm
</screen>
</para>
</sect1>

<sect1 id="versions">
<title>Should I remove old version xyz before installing a new one?</title>

<para>In principle, this is not necessary. RPM and DEP packages should take care
of all dependencies. </para>

<para>If you compile the source code yourself, you might take care not to compile
different versions of the KDE packages. So if you install a new version,
please first make and install kdesupport, then kdelibs, then kdebase.  </para>

<para>One thing you should avoid: Installing two (or more, of course) versions of
KDE in parallel. This might happen if you specify a different target
directory for one version than for the other. The result may be
unpredictable. The same is true if you have different versions of Qt
installed at the same time. This happens easily if you already have an old
Qt version installed with a Linux distribution.</para>
</sect1>
<sect1 id="howtostartkde">
<title>How do I start KDE? </title>

<para>The most comfortable method to start KDE is to use the <literal remap="tt">startkde</literal> script.
Simply put the line
<screen>startkde
</screen>

at the end of your <literal remap="tt">.xsession</literal> file (or into your <literal remap="tt">.xinitrc</literal>
file, if you are not using kdm or xdm). Please also remove the lines that
started your previous window manager.  If there is no .xsession or
.xinitrc in your home directory, simply create a new one that just
contain one line saying "startkde" (without the quotes!).</para>
</sect1>

<sect1 id="shadow-passwords">
<title>Whenever I start KDE, it complains about "shadow passwords". Why?</title>

<para>When your system uses shadow passwords, the screensaver can only run
properly if the suid bit is set.  This bit gives the screensavers root
privileges, which are needed to access the shadow passwords.  (Remember: the
screensavers might be configured to secure the machine until the password is
entered.)</para>

<para>To set the suid bit on the screensavers, you (or the systems administrator)
must issue the following commands as root:</para>

<para><screen>chown root $KDEDIR/bin/*.kss
chmod u+s $KDEDIR/bin/*.kss
</screen>
</para>

<para>Alternatively, if you compile KDE from source, you can use</para>

<para><screen>./configure --with-shadow
</screen>
</para>

<para>to configure kdebase.  Then the suid bit is set automatically during <literal remap="tt">make
install</literal>.</para>
</sect1>

<sect1 id="user-directory">
<title>Is it possible to install KDE in a user directory?</title>

<para>You can install KDE in every directory you want. What you have to do depends
on the kind of packages you want to install:</para>

<para><emphasis remap="bf">Source packages</emphasis></para>

<para>To configure, use a command like:</para>

<para><screen>configure --prefix=/users/myhome/kde; make; make install
</screen>
</para>

<para>to install into <literal remap="tt">/users/myhome/kde</literal>. </para>

<para>After you have installed the packages in the user directory, you should add
the following to your init files.  Please note that if it isn't
necessary for you to set LD&lowbar;LIBRARY&lowbar;PATH, it's better to leave it
out.</para>

<para>For csh or tcsh:
<screen>setenv KDEDIR /users/myhome/kde

if ( $?LD_LIBRARY_PATH ) then
   setenv LD_LIBRARY_PATH $KDEDIR/lib:$LD_LIBRARY_PATH
else
   setenv LD_LIBRARY_PATH $KDEDIR/lib
endif

if ( ! $?LIBRARY_PATH ) then
   setenv LIBRARY_PATH $LD_LIBRARY_PATH
endif  
</screen>
</para>

<para>For bash, please use:
<screen>KDEDIR=/users/myhome/kde
PATH=$KDEDIR/bin:$PATH
LD_LIBRARY_PATH=$KDEDIR/lib:$LD_LIBRARY_PATH
LIBRARY_PATH=$LD_LIBRARY_PATH
</screen>
</para>

<para>export KDEDIR PATH LD&lowbar;LIBRARY&lowbar;PATH LIBRARY&lowbar;PATH</para>

<para><emphasis remap="bf">RPM packages</emphasis></para>

<para><literal remap="tt">rpm</literal> allows you to use the <literal remap="tt">-prefix</literal> option to select the directory
to for installtion, e.g.</para>

<para><screen>rpm -i -prefix=/users/myhome/kde package.rpm
</screen>
</para>

<para><emphasis remap="bf">Problems to expect</emphasis></para>

<para>KDE will run from the users directory. There are some problems with programs
that require SUID root, e.g. the programs in the kdeadmin package, but they
are not meant to be run by users, so this is nothing to worry about.</para>

<para>However, on systems using shadow passwords, the screensavers have to be run
SUID root to enable password access for unlocking the screen, so this option
will not work. </para>
</sect1>

<sect1 id="cannot-connect">
<title>startkde fails with "can not connect to X server". What is wrong?</title>

<para>You probably tried to start the X-Server with <literal remap="tt">startkde</literal>. The X-Server is
started with <literal remap="tt">startx</literal>. startkde is the script that should be run in your
<literal remap="tt">.xinitrc</literal> or <literal remap="tt">.xsession</literal> to activate the window manager and the
necessary server daemons for KDE. See also: <link linkend="howtostartkde">How do I start KDE?</link>.</para>
</sect1>

<sect1 id="giflib2">
<title>Installing Debian packages with dpkg says "giflib2 is missing"</title>

<para>Sometimes, when installing KDE Debian packages, dpkg complains about
"dependency problems: giflib2 is missing". As the giflib2 is not needed, the
solution is simple:</para>

<para><screen>dpkg -i --ignore-depends=giflib2 package.deb
</screen>
</para>
</sect1>

<sect1 id="aix">
<title>KDE on AIX?</title>

<para>If you have trouble building KDE on AIX check out  Stefan Westerfeld's 
<ulink url="http://space.twc.de/~stefan/kde/">KDE on AIX</ulink>
page for lots of help on building KDE on this 'exceptional' Unix variant.</para>
</sect1>

<sect1 id="libncurses">
<title>Installing Redhat packages says "libncurses.so.3.0 is needed"</title>

<para>If there isn't a rpm for it on your Redhat CD, poke around the
Redhat FTP site and its mirrors to get it.  Do 
bear in mind that libncurses-3 and -4 coexist so there is no need to 
replace one with the other, i.e. a plain rpm -i will do. </para>

<para>Or you might try the following:
<screen>cd /usr/lib
ln -s libncurses.so.4 libncurses.so.3
ldconfig
rpm -i --nodeps kdebase...
</screen>
</para>

<para>Since libncurses-3 and -4 are 100&percnt; compatible both at binary and at
source level, installing two versions is just a waste of space.</para>
</sect1>

<sect1 id="laptop">
<title>KDE on a laptop?</title>

<para>If you can get X to run, you shouldn't have a problem getting KDE to
run on it.  In addition, you might find the following links helpful:</para>

<para><itemizedlist>
<listitem>
<para><ulink url="http://www.cs.utexas.edu/users/kharker/linux-laptop/">http://www.cs.utexas.edu/users/kharker/linux-laptop/</ulink></para>
</listitem>
<listitem>
<para><ulink url="http://www.yy.cs.keio.ac.jp/~sanpei/how2800x600.html">http://www.yy.cs.keio.ac.jp/~sanpei/how2800x600.html</ulink></para>
</listitem>
</itemizedlist>
</para>

<para>For laptops with exotic resolution like 1024x600, You can try editing
the XF86Config file (in /etc/X11 if you use RedHat).  If you have
some experience with this file, you will know that there are
several different "Modeline" lines in it. You only have to add a
Modeline for your resolution.  Unfortunately, the format of the
Modeline lines is pretty esoteric; i.e., you'd have to read up a
lot.  One source of information could be the <ulink url="http://sunsite.unc.edu/LDP/HOWTO/XFree86-Video-Timings-HOWTO.html">XFree86 Video Timings HOWTO</ulink>.</para>
</sect1>

<sect1 id="default-directory">
<title>I don't like the default KDE directory after installation.  How do I move it without breaking anything?</title>

<para>Assuming the default is /opt/kde and you want to move it to
/usr/local/kde.  Here's what you've to do:
<orderedlist><listitem>
<para> change to superuser if you aren't already</para>
</listitem>
<listitem>
<para> mv /opt/kde /usr/local/kde</para>
</listitem>
<listitem>
<para> ln -s /usr/local/kde /opt/kde</para>
</listitem>
</orderedlist>
</para>

<para>This will put all your KDE files in /usr/local/kde but everything is
still accessible with /opt/kde.</para>
</sect1>

<sect1 id="snapshot-configuer-script">
<title>Where has the snapshot configure script gone?</title>

<para>Maybe this has already been rectified, but just in case it isn't,
here's the solution:
<screen>make -f admin/Makefile.common cvs
</screen>
 </para>
</sect1>

<sect1 id="bzip2">
<title>How do I unzip tarballs with the 'bz2' extension? </title>

<para>First, you need the bzip2 package.  Get it from your favourite FTP
site if you haven't already got one.  Next, to view the contents,
simply do this:
<screen>$ bzip2 -cd files.tar.bz2 | tar tvf -
</screen>
 </para>

<para>To extract, do this instead:
<screen>$ bzip2 -cd files.tar.bz2 | tar xvf -
</screen>
</para>

<para>Of course, you can also use something like: 
<screen>"tar --use-compress-program bzip2 -xvf files.tar.bz2"
</screen>

.  Please "man tar" and "man bzip2" for further information, and you
might also want to read up the Bzip2 mini-HOWTO.  By the way, the
Bzip2 home page is at <ulink url="http://www.muraroa.demon.co.uk/">http://www.muraroa.demon.co.uk/</ulink>.</para>
</sect1>

<sect1 id="extensions">
<title>What files can I delete from my KDE install directory?  Can all the *.h, *.c and *.o files be safely removed?</title>

<para>There shouldn't be any need to keep the .c and .o files, but you might
want to keep the .h files, as they are used by includes if you ever want to
compile your own KDE programs.  Or if you wish to add patches to the
source programs as they become available (rather than downloading 
everything again), then they should stay.</para>
</sect1>

<sect1 id="settings-when-upgrade">
<title>Will I lose my current settings when I upgrade KDE?</title>

<para>No, your settings will be fine even if you let's say remove your old
RPM packages first (rpm -e &lt;Packagename&gt;.i386.rpm).  This is because
your KDE settings are kept in a folder in your home directory called
'Desktop' (as well as in some .files) while KDE itself is normally
installed into a directory available system wide like /opt/kde.</para>

<para>But of course, it is always advisable to backup.  Other than your
personal config files, backing up $KDEDIR/share/config seems to be a
good idea, too.</para>

<para>If you have enough space, move /opt/kde to /opt/ke10, say,
and install onto /opt/kde11.  Do the same with $HOME/.kde and also back up
$HOME/Desktop.  Use symbolic links /opt/kde and $HOME/.kde to
get the installation prefix right without changing the environment
variables, and also to switch between KDE 1.0 and 1.1.  Do the same
with Qt.  </para>
</sect1>

<sect1 id="msgfmt">
<title>Compiling kdebase gives me a "bin/sh: msgfmt: command not found" error!</title>

<para>You need the GNU msgfmt which is part of the GNU i18n package
'gettext'.  You should be able to download it from any decent GNU
mirrors.  </para>
</sect1>

<sect1 id="solaris">
<title>Compiling KDE using gcc in Solaris 2.6 but keep on getting errors.</title>

<para>The main problem seems to be the Solaris assembler.  Switching to
egcs-1.1.1 fixes the compiler crashes and gnu assembler (in
"binutils-2.9.1") fixes the assembler problems.</para>
</sect1>

<sect1 id="uninstall-compiled">
<title>How do I uninstall KDE apps compiled from scratch?</title>

<para>You can uninstall your programs by typing 'make uninstall' in the
directory where you did 'make install'.  If you have already nuked
away that directory, then there's only one way, and it isn't good: go
to $KDEDIR/bin and start deleting files one by one.</para>
</sect1>

<sect1 id="gif-support">
<title>What's up with GIF support?</title>

<para>This has something to do with Unisys' LZW patent.  GIF support is turned
off in Qt 1.44 by default.  Either use an older Qt, or recompile it
with GIF support turned on.  However, I don't know whether it's legal
to do so.  Please search the kde-devel mailing list archive for details.</para>
</sect1>
</chapter>

<chapter id="Thepanel">
<title>The panel</title>

<sect1 id="add-applications-to-the-panel">
<title>How do I add applications to the panel?</title>

<para>There are several ways to add an application to the panel:</para>

<para><emphasis remap="bf">Using the panel menu</emphasis></para>

<para>Perhaps the easiest method is to use the entry "Panel &verbar; Add application" in
the panel menu. (This is the menu that appears when pressing the K button on
the panel). The menu shows all installed KDE applications. To add a button
to the menu, simply click on the application.</para>

<para><emphasis remap="bf">Using the filemanager</emphasis></para>

<para>You can also simply drag a kdelnk file from a window of the filemanager to
the panel.</para>
</sect1>

<sect1 id="panel-complains">
<title>If I try to add an application, the panel complains! Why?</title>

<para>If you try to drag an application to the panel, and it complains: "Cannot
put this as button onto the panel", you have not dragged a kdelnk file, but
an executable. To get this executable to the panel, you must first create a
kdelnk file with "New &verbar; Program" from the File menu of the
filemanager.  Newer kpanel (comes with KDE 1.1 alpha) creates its own
kdelnk file if you drop an executable on the panel, however. </para>
</sect1>

<sect1 id="embed-in-the-panel">
<title>How do I embed an application in the panel?</title>

<para>It is possible to swallow small applications like xload or xbiff in the panel.
To do this, you will have to add the lines:</para>

<para><screen>SwallowExec=...
SwallowTitle=...
</screen>
</para>

<para>in the kdelnk file. The entry <literal remap="tt">SwallowExec</literal> is the command that is executed
to start the swallowed application. <literal remap="tt">SwallowTitle</literal> is the title of the 
applications windows. This entry must <emphasis>exactly</emphasis> match the window title, as
is is used to idenitify the window to show in the panel.</para>

<para>For example, a kdelnk file to swallow xload would read:</para>

<para><screen># KDE Config File
[KDE Desktop Entry]
SwallowExec=xload -nolabel -geometry 50x50+10000+10000
SwallowTitle=xload 
Comment=System load
Type=Application
</screen>
</para>

<para>You can still use the <literal remap="tt">Exec</literal> entry to specifiy an application that is
launched when you click at the panel button. You could e.g. start top.</para>
</sect1>

<sect1 id="wrong-time">
<title>Why is the panel clock showing the wrong time?</title>

<para>On some RedHat systems, the clock in the panel always shows the
time in GMT. This is a bug in the RedHat setup.</para>

<para>The solution is described in <ulink url="http://www.redhat.com/support/docs/rhl/intel/rh50-errata-intel.html">the RedHat errata</ulink>.</para>

<para>It just says to create this symbolic link:</para>

<para><screen>ln -s /usr/share/zoneinfo /usr/lib/zoneinfo
</screen>
</para>
</sect1>

<sect1 id="non-kde-compliant">
<title>Is it possible to run kpanel in a non-KDE-compliant window manager?</title>

<para>Yes.  Try starting it with something like this:</para>

<para><screen>kpanel -no-KDE-compliant-window-manager
</screen>
</para>
</sect1>

<sect1 id="k-button">
<title>It is possible to change the K button of the panel to another picture?</title>

<para>Look for $HOME/.kde/share/apps/kpanel/pics/go.xpm and
$HOME/.kde/share/apps/kpanel/pics/mini/go.xpm and replace them.  Don't 
forget to flatten the replacements to one layer, or else you won't
see anything.  Create the directories if they do not already exist.
Then restart kpanel.</para>
</sect1>
</chapter>

<chapter id="Thedesktop">
<title>The desktop</title>

<sect1 id="add-application">
<title>How do I add an application to the desktop?</title>

<para>This is a simple exercise: click on the desktop with the right mouse button.
In the appearing menu, select New &verbar; Program.  Enter the title of the
program, and soon it appears on the desktop.</para>

<para>You might want to change the new icon's properties, so click on the program
name with the right mouse button, and select Properties. In the dialog, you
should at least change the program to execute, and the icon. That's it.</para>
</sect1>

<sect1 id="mount-unmount">
<title>How do I mount/unmount a device from the desktop?</title>

<para>There are two steps involved:</para>

<para><emphasis remap="bf">Make sure you are allowed to mount/unmount the device</emphasis></para>

<para>Normally, only root is allowed to mount/unmount devices. If you are not
running KDE as root (and this is generally considered a bad idea :), you
must set the right for users to mount a device in <literal remap="tt">/etc/fstab</literal>. This means to
add the option <literal remap="tt">user</literal> to the options of the file system you want to
mount.</para>

<para>For example, to mount the floppy, your <literal remap="tt">/etc/fstab</literal> should include</para>

<para><screen>/dev/fd0   /floppy   msdos   noauto,user,sync 0 0
</screen>
</para>

<para><emphasis remap="bf">Create a kdelnk file for the filesystem</emphasis></para>

<para>An example for a device kdelnk file is:</para>

<para><screen># KDE Config File
[KDE Desktop Entry]
UnmountIcon=3floppy_unmount.xpm
MountPoint=/floppy
Icon=3floppy_mount.xpm
Dev=/dev/fd0
ReadOnly=0
FSType=default
Type=FSDevice
Comment=Floppy Disc
</screen>
</para>
</sect1>

<sect1 id="screensaver-as-background">
<title>How do I use a screensaver as background?</title>

<para>It is possible to use a screensaver instead of a background image. To do
this, call any screensaver with the <literal remap="tt">-inroot</literal> parameter, e.g.:</para>

<para><screen>kswarm.kss -inroot &
</screen>
</para>

<para>Most screensavers will look best of you set the background color to black.</para>

<para>However, using a screensaver as background might eat some CPU and X time ...</para>
</sect1>

<sect1 id="win95">
<title>How do I highlight my menus even when I don't hold down the mouse button (similar to Win95)?</title>

<para>Go to the control center "Desktop/Fonts etc." and click on "Draw
widgets in the style of Windows 95".</para>
</sect1>

<sect1 id="icons">
<title>Where are the icons kept?</title>

<para>The icons can be found only in $KDEDIR/share/icons or
$HOME/.kde/share/icons.  To use icons stored in other locations, you
must either copy them into one of the above-mentioned fixed KDE
locations or make symlinks.</para>
</sect1>

<sect1 id="non-root">
<title>How do I change the standard menu items as non-root?</title>

<para>Try changing the permissions and/or ownership of the directories and
files in $KDEDIR/share/applnk.  Alternatively, you can create a
trusted group--let's say friends--and try 'chgrp -R friends 
$KDEDIR/share/applnk ; chmod -R g+w $KDEDIR/share/applnk' and make all
your trusted users members of friends.  Note that you'd still need
superuser privileges to do the above, however.  If it's impossible
for you to obtain root privileges, then you'd have to settle for
editing your personal menu.</para>
</sect1>

<sect1 id="mouse-wheel">
<title>How do I use the mouse scroll wheel in KDE?</title>

<para>Mouse wheel support will come with Qt 2.0.  Meanwhile, to use the
scroll wheel with KFM, KEdit, and non-KDE applications like Emacs, try
getting IMWheel at <ulink url="http://solaris1.mysolution.com/~jcatki/imwheel/">http://solaris1.mysolution.com/~jcatki/imwheel/</ulink>.  You might
also find the information in <ulink url="http://www.inria.fr/koala/colas/mouse-wheel-scroll/">http://www.inria.fr/koala/colas/mouse-wheel-scroll/</ulink> useful.</para>
</sect1>

<sect1 id="templates">
<title>What exactly is the Templates folder? </title>

<para>The Templates folder holds items that you can create easily anywhere
(on the Desktop, or in a file manager window), by selecting the New
menu item, on the context menu (right-click menu) of the place you 
want the item to be.</para>

<para>You can put both files and directories in the Templates folder, and
they will auto-magically appear in the New submenu.   When you select
them from the submenu, they are copied to the current location.</para>

<para>This is exactly like opening the Templates directory and copying the items
from there directly, only it's slightly easier.  By default, the Templates
directory is populated with only kdelnk files.  These files are here to
allow you to immediately begin creating devices, programs, URL links and
new mime types, but you can put anything you want here.</para>
</sect1>

<sect1 id="system-sounds">
<title>Why can't I get system sounds to work, like for opening windows?</title>

<para>Make sure "kwmsound" is in your start-up script, e.g. $KDEDIR/bin/startkde.</para>
</sect1>

<sect1 id="launch-in-a-desktop">
<title>How do I launch applications in a particular desktop?</title>

<para>KDE pre-1.1 comes with a program called kstart.  You can use it in a .kdelnk
file like this:
<screen>Name=Netscape
Exec=kstart "netscape" -window ".*Netscape.*" -desktop 2 -maximize
BinaryPattern=netscape;
Icon=netscape.xpm
Path=
Type=Application
Terminal=0
</screen>
</para>

<para>Use a shell script to do it.  If you have KDE 1.0, the script should
look something like this:
<screen>kwmcom desktop2 (or desktop3, desktop4, whatever)
netscape
</screen>

Please note that this has the (undesirable) effect of leaving you in
desktop2 while it's executing and also once it's done executing.  </para>

<para>(On the off chance you haven't used shell scripts, they're basically just a
text file you've run "chmod +x &lt;filename&gt;" on.  They're a Linux
version of a DOS batch file, but, of course, better.)</para>

<para>If you use KDE 1.1 then you don't necessarily even need a shell
script.  You just need to run the following:
<screen>kstart "netscape" -desktop 1 -activate
</screen>
</para>
</sect1>

<sect1 id="macos-theme">
<title>What should I do to get the Mac-like window decorations shown in the screenshot on the KDE page?</title>

<para>Get the MacOS and other themes at <ulink url="http://kde.themes.org">http://kde.themes.org</ulink>.
You can find other icons at <ulink url="http://icons.themes.org/">http://icons.themes.org/</ulink>. </para>
</sect1>

<sect1 id="fonts-too-small">
<title>I played with the fonts section in the KDE Control Center but the fonts are still way too small.  What can I do?</title>

<para>Many users use the 75 dpi fonts as the default.   If you've installed
the 100 dpi font, make sure your XF86Config file has those fonts in the
path before the 75 dpi fonts.  Here's a step-by-step procedure on
how to do it: 
<screen>Edit /etc/Xll/XF86Config.  Near the top of the file is a listing
of fonts --- several rows: type1, speedo, etc., and at the bottom there
are two entries, 75dpi and 100dpi. simply reverse their order.  And while
you're at it, move the Type 1 fonts to the bottom of the list (or 
somewhere below the 75 and 100 dpi fonts).  That makes an improvement
too! </screen>
</para>
</sect1>

<sect1 id="icon-menus">
<title>Is it possible to extend the Desktop Icon Menus?</title>

<para>Yes.  Just add the applnk for the required command to
$KDEDIR/share/applnk/, or use kmenuedit. </para>
</sect1>

<sect1 id="remove-trash-template-autostart">
<title>Can I get rid of the Trash/Templates/Autostart icons?</title>

<para>Yes.  Simply edit $KDEDIR/bin/startkde and replace 'kfm' with 'kfm -w'.  If
this doesn't work, here's another way.  Add the following lines to
$HOME/.kde/share/config/kfmrc:</para>

<para><screen>[Paths]
Trash=/home/me/Trash/
Desktop=/home/me/Desktop
Templates=/home/me/Templates/
Autostart=/home/me/Autostart/
</screen>
</para>

<para>The effect is to take trash, templates, and autostart and put them into
your home directory instead of your $HOME/Desktop directory.  You will
have to restart KDE, and you may have to delete the icons from the
desktop the first time--be sure to move anything you have in
autostart into $HOME/Autostart before deleting it from the desktop.  And
then you have a nice, clean desktop with no "My Computer" sort of look.</para>
</sect1>

<sect1 id="files-on-desktop">
<title>Where do I save my files if I want them to appear directly on the desktop?</title>

<para>$HOME/Desktop.  You might need to refresh your desktop after you save
your files.  </para>
</sect1>
</chapter>

<chapter id="Thewindowmanager">
<title>The window manager</title>

<para>The default window manager provided by KDE is the K Window Manager
(KWM).  Please read "The K Window Manager Handbook" (should be
accessible from KDE Help) for usage information.</para>

<sect1 id="kwm-shortcuts">
<title>Are there keyboard shortcuts for KWM operations?</title>

<para>Yes, there are some shortcuts for the most common operations.
<variablelist>
<varlistentry>
<term>Alt-Esc, Ctrl-Esc</term>
<listitem>
<para>Invoke the "Current Session" manager.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Alt-Tab, Alt-Shift-Tab</term>
<listitem>
<para>Traverse the windows on the current desktop.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Ctrl-Tab, Ctrl-Shift-Tab</term>
<listitem>
<para>Traverse the virtual desktops.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Alt-F2</term>
<listitem>
<para>Execute command.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Alt-F3</term>
<listitem>
<para>Popup the window operation menu.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Alt-F4</term>
<listitem>
<para>Close active window.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Ctrl-F&lsqb;1..8&rsqb;</term>
<listitem>
<para>Switch to virtual desktop.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Ctrl-Alt-Esc</term>
<listitem>
<para>Destroy window mode.</para>
</listitem>
</varlistentry>
</variablelist>
</para>
</sect1>

<sect1 id="keyboard-shortcuts">
<title>Can I define my own set of keyboard shortcuts?</title>

<para>Yes, if you are using KDE 1.1 and above.  Go to
Settings-&gt;Keys-&gt;GlobalKeys to configure window manager bindings like
maximising of windows, etc.  For starting apps, you'd need to install
KHotKeys, though.  </para>
</sect1>

<sect1 id="iconified-window-disappears">
<title>When I "iconify" a window, it disappears. Where does it go?</title>

<para>With many X GUI's, the minimize button (a little dot) will erase the
window that the program is running in and create, instead, an icon on the
desktop. KDE does not do this. Instead, when a window is iconified it is
simply hidden (but the program is still running). </para>

<para>There are two ways to get the window back: </para>

<para><itemizedlist>
<listitem>
<para> If you're running the taskbar part of kpanel (see the
Panel --&gt; Configure menu entry), you can choose to have a list of tasks
displayed on you desktop. Iconified tasks have their names surrounded by
parenthesis. 
</para>
</listitem>
<listitem>
<para> If you click the middle mouse button on the root window,
kwm will give you a list of all available tasks (and again, the names of
iconified tasks are bracketed).</para>
</listitem>
</itemizedlist>
</para>
</sect1>

<sect1 id="sticky-no-border">
<title>How do I get a sticky window with no border and focus?</title>

<para>In the current KDE you can use kstart for this (assuming the
application you want to start is xosview):
<screen>kstart xosview -window xosview -sticky -decoration none
</screen>

Try <literal remap="tt">kstart -help</literal> for additional help.</para>

<para>In KDE-1.0 you'd need to write something like this in kwmrc:
<screen>[Sticky]
stickyClasses=xosview,
[Focus]
noFocusClasses=xosview,
[Decoration]
noDecorationClasses=xosview,
</screen>
</para>

<para>In the current KDE you can set these settings in the control center under
Windows/Advanced.</para>
</sect1>

<sect1 id="kill-kwmpager">
<title>How do I kill kwmpager?</title>

<para>Click on the border frame with the right mouse button to bring up a
menu which will let you close the pager.  By the way, kwmpager is
obsolete and will be replaced by kpager.</para>

<para>In addition, if you prefer working through a terminal, type </para>

<para><screen>ps ax | grep kwmpager 
</screen>
</para>

<para>to find it and then kill it using 
<screen>kill pid
</screen>

(please replace "pid" with the relevant pid!).  Or if you dread the
idea of using CLI, just press Ctrl-Alt-Esc, and then move the
pirate-skull mouse pointer over kwmpager and click to kill it.  To
abort (not undo!) the kill, just press Ctrl-Alt-Esc again. </para>
</sect1>

<sect1 id="maximize-vertically-or-horizontally">
<title>How do I maximize windows only vertically or horizontally?</title>

<para>Provided your window isn't already maximized, clicking on the maximize
button with left/middle/right mouse button will maximize
fully/vertically/horizontally respectively.  </para>
</sect1>

<sect1 id="shading">
<title>What is "shading a window"? </title>

<para>By "shading a window" we mean "rolling up" a window leaving just the
titlebar visible.  To enable it with a double click on the titlebar,
simply go to the KDE Control Center and look under Windows/Titlebar
and set the option "LeftMouseButton double click on titlebar does:" to
"(Un)Shade".</para>
</sect1>

<sect1 id="fwm2-shadow-frameworks">
<title>Is it possible to have FVWM2-like shadow frameworks for the placement of windows?</title>

<para>Yes.  Run KDE Control Center and select Windows -&gt; Properties.  There
is a dialog option that allows you to set the placement policy you want.</para>
</sect1>

<sect1 id="disable-session-management">
<title>How do I disable session management?</title>

<para>Open up your startkde script with your favourite editor and find the
line launching kwm (usually the last line).  Change it to "kwm
-nosession".</para>
</sect1>
</chapter>

<chapter id="Thefilemanager">
<title>The filemanager</title>

<sect1 id="kfm-with-proxy">
<title>How do I use KFM as web browser with a proxy?</title>

<para>KFM can be used via HTTP and FTP proxies. You can set the proxy server with
KFM's menu entry <literal remap="tt">Options&verbar;Configure Browser&verbar;Proxy</literal>.</para>

<para>Please make sure to save the changed settings with <literal remap="tt">Options&verbar;Save settings</literal>
to make the proxy setting persistent.</para>
</sect1>

<sect1 id="directory-appearance">
<title>How can I change the appearance of a directory in KFM?</title>

<para>When displaying a directory, KFM looks for a hidden file</para>

<para><screen>.directory
</screen>
</para>

<para>inside the directory. You can create such a file to modify the way in which
the directory is displayed. The file is simply a kdelnk file. For example:</para>

<para><screen># KDE Config File
[KDE Desktop Entry]
Name=Settings
Name[de]=Einstellungen
Name[pl]=Ustawienia
MiniIcon=kcontrol.xpm
SortOrder=Desktop,Input_Devices,KWM,Network,Information,Sound
Icon=kcontrol.xpm
</screen>
</para>

<para>is the file used to describe the Settings directory. It changes the icon
used to display the directory, it sets the (displayed) name of the directory
according to the national language and fixes the order in which the
subdirectories are displayed.</para>

<para>For the directories that build up the K&circ; menu, you can also use kmenuedit to
change the appearance.</para>
</sect1>

<sect1 id="non-anonymous-ftp">
<title>How can I do non-anonymous FTP transfers with KFM?</title>

<para>Normally, if you enter an URL like:</para>

<para><screen>ftp://ftp.somehost.com
</screen>
</para>

<para>KFM attempts an anonymous login to the FTP server. If you want to login as a
certain user, enter an URL like:</para>

<para><screen>ftp://username@ftp.somehost.com
</screen>
</para>

<para>KFM will then ask for your password and connect to the server.</para>
</sect1>
<sect1 id="loopbackdevice">
<title>"KFM cannot connect to 'localhost'", what is going wrong? </title>

<para>In most cases, this is because of an incorrectly configured loopback route
on your system.</para>

<para><emphasis remap="bf">How to check for problems</emphasis></para>

<para>Check if this command returns similar output:</para>

<para><screen># ping localhost

PING localhost (127.0.0.1): 56 data bytes
64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=0.3 ms
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.2 ms
64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.2 ms 
...
</screen>
</para>

<para>If it doesn't, your loopback interface or route is not properly
configured.</para>

<para>The output of the</para>

<para><screen>/sbin/route 
</screen>
</para>

<para>command should contain lines like the following:</para>

<para><screen>Destination     Gateway         Genmask         Flags MSS    Window Use Ifac
loopback        *               255.0.0.0       U     3584   0       13 lo
</screen>
</para>

<para>The important fields are the Destination, Gateway, Genmask and Iface. This
means that the system is properly configured to route all loopback traffic
through the loopback interface (lo).</para>

<para>The output of the</para>

<para><screen>/sbin/ifconfig
</screen>
</para>

<para>command should contain the following lines:</para>

<para><screen>lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Bcast:127.255.255.255  Mask:255.0.0.0
          UP BROADCAST LOOPBACK RUNNING  MTU:3584  Metric:1
</screen>
</para>

<para>This means that the loopback interface is up and running.</para>

<para>Your <literal remap="tt">/etc/hosts</literal> file should contain the following line:</para>

<para><screen>127.0.0.1       localhost
</screen>
</para>

<para>This ensures that the "localhost" hostname is associated with your
system's loopback address (127.0.0.1).</para>

<para><emphasis remap="bf">Fixing these problems</emphasis></para>

<para><screen>/sbin/ifconfig lo 127.0.0.1
/sbin/route add -net 127.0.0.0
</screen>
</para>

<para>Both these commands should, on a healthy system, be executed for you at
the bootup of your computer. If this isn't happening, check your network
startup files in <literal remap="tt">/etc/rc.d</literal>. </para>

<para><emphasis remap="bf">If it STILL doesn't work</emphasis></para>

<para>If none of these work, please send a full report to 
<ulink url="http://buglist.kde.org">the KDE buglist</ulink>
Don't forget to mention that you have checked all these things.</para>
</sect1>

<sect1 id="percent">
<title>What are &percnt;i and &percnt;m in the Execute line?</title>

<para>They are used by all kde-applications (since they are implemented in
KApplication and all good kde-programs create a KApplication object before they
even look at the command line arguments).</para>

<para>A standard line for a KDE application looks like this:</para>

<para><screen>foo .....    %i %m -caption \"%c\"
</screen>
</para>

<para>Pretty confusing, but it has been designed in that way to be able to integrate
legacy, non-KDE applications as smoothly as possible.</para>

<para>KFM when executing the line from above will extend the command to</para>

<para><screen>foo -icon something.xpm -miniicon something_mini.xpm -caption \"The Foo\"
</screen>
</para>

<para>Both the icon and the mini-icon as well as "The Foo" are properties defined
in the kdelnk file. If the icons are not defined, they simply default to
the executable name "foo".</para>

<para>This way a user can change these things in the menu-editor for his or
her applications.  "-caption" is important, because no user will
accept that the menu item "Editor" starts something called
"kedit-0.9pl4-build47". Instead, he expects a window 
called "Editor".  Furthermore these names are localized, i.e. an American
launches "CD-Player" and gets a window called "CD-Player" while a German
launches "CD Spieler" and gets a window called "CD-Spieler".</para>
</sect1>

<sect1 id="kfm-startup-directory">
<title>How do I specify KFM's startup directory?</title>

<para>Right-click on the KFM icon and choose Properties.  Under the 
Execute tab you'd probably find something like 'kfmclient folder &percnt;u
file:/root'; just change 'root' to wherever you'd like KFM to start.</para>
</sect1>

<sect1 id="nsbookmark">
<title>How do I import Netscape bookmarks?</title>

<para>Take a look at the "full" list of KDE apps (not just those in the
distribution) at <ulink url="http://www.kde.org/applications.html">http://www.kde.org/applications.html</ulink>.
Under "network", you will find knsbookmark, the tool you need.</para>
</sect1>

<sect1 id="save-as-in-kfm">
<title>Is there a "Save As..." function in KFM?</title>

<para>There's something close --- "View--&gt;View Document Source" opens KEdit with the
source code, which you can then save.  This works well for text/html
files, but not for graphics. </para>
</sect1>
</chapter>

<chapter id="ConfiguringKDE">
<title>Configuring KDE</title>

<sect1 id="language">
<title>How do I set the language to be used by KDE?</title>

<para>There are two ways to set the language KDE uses in the messages it will
display: </para>

<para><emphasis remap="bf">Using the KDE Control Center</emphasis></para>

<para>In the KDE Control Center (<literal remap="tt">kcontrol</literal>), there is the entry
<literal remap="tt">Desktop&verbar;language</literal>.  You can select three languages, according to your
preferences.  If KDE can't find a translation in to first language, it will
fall back on the second or third.  If there is no appropriate translation at
all, the default language will be used.  This will usually be English.</para>

<para>Using kcontrol is the preferred way of choosing the language.</para>

<para><emphasis remap="bf">Using the LANG environment variable</emphasis></para>

<para>The second method uses the standard locale setting on your system. To change the
language, simply set the environment variable <literal remap="tt">LANG</literal> accordingly.</para>

<para>For example if your shell is bash, execute the following:</para>

<para><screen>export LANG=de
</screen>
</para>
</sect1>

<sect1 id="kikbd">
<title>Is there any keyboard switcher for international keyboards for KDE?</title>

<para>KDE 1.1 (and above) comes with kiKbd (for International KeyBoarD),
which has a cool interface and permits you to create new national
keyboards.</para>
</sect1>

<sect1 id="kde-login-screen">
<title>How do I replace the standard Linux text login screen with the KDE login screen? </title>

<para>First, you need to change to the "xdm runlevel" (runlevel 5 on
RedHat systems) by editing your /etc/inittab file.  In the file, you
should have a line saying:
<screen>id:3:initdefault:
</screen>
</para>

<para>Change it to:
<screen>id:5:initdefault:
</screen>
</para>

<para>Now at the end of the file, comment out the following line:
<screen>x:5:respawn:/usr/bin/X11/xdm -nodaemon
</screen>

and replace it with:
<screen>x:5:respawn:/opt/kde/bin/kdm -nodaemon
</screen>

(the location of kdm may differ on your systems, though)</para>

<para>For changes to take effect immediately, type "init 5" at the shell
prompt.  Please note that it is risky to initiate a graphical login
without checking beforehand whether it works.  If it fails to work,
you'd be in for a hard time getting back....</para>
</sect1>

<sect1 id="replace-kwm">
<title>How do I replace KWM with another KDE-compliant window manager like Blackbox and Window Maker? </title>

<para>First, download the source code and compile them.  You would probably
need to specify some option when you execute the configure script in order 
to produce KDE-compliant binaries.  Read the README and INSTALL files
for instructions.  Then simply replace the 'kwm' command in the startkde
script with the command that runs the new window manager and you're done.   </para>

<sect2>
<title>Blackbox</title>

<para>Blackbox is yet another addition to the list of window managers for
X.  It is built with C++, sharing no common code with any
other window manager (even though the graphics implementation is
similar to that of Window Maker).  Blackbox became KDE compliant at
its 0.50.2 release.  Please visit <ulink url="http://blackbox.wiw.org/">Blackbox's Website</ulink> for further information.  You might also
find this website <ulink url="http://www.netwave.net/members/z934133/kbb/">KDE + Blackbox = KBB!</ulink> useful.</para>

<para>To use Blackbox with KDE, first download the source code and run:
<screen>$ ./configure --with-kde
$ make
# make install
</screen>

(the "with-kde" flag enables KDE support)</para>

<para>Next, replace the 'kwm' command in the startkde script with 'blackbox'.
Save the new script as, for example, '/usr/local/kde/bin/startbb' and
change the bottom line of your $HOME/.xinitrc file so that it runs the new
script instead of the old one.  Fire up X and you're away.  (KDM and
XDM users would probably need to edit $HOME/.xsession instead.)</para>
</sect2>

<sect2>
<title>Window Maker</title>

<para>Window Maker is an X11 window manager designed to give additional
integration support for GNUstep applications.  It tries to emulate the
elegant look and feel of the NeXTSTEP(tm) GUI.  It is relatively fast,
rich in features, and easy to configure and use.  Window Maker becomes
KDE compliant at its 0.50.0 release.  Please visit <ulink url="http://www.windowmaker.org/">the Official Window Maker Website</ulink> for further information.</para>
</sect2>
</sect1>

<sect1 id="red-hat-logo">
<title>How do I change the Red Hat Linux logo bootup screen image?</title>

<para>Redhat uses xbanner to display its logo, so to disable it, just
comment out the line calling xbanner from the configuration file xdm
reads, which is /etc/X11/xdm/Xsetup&lowbar;0 (may vary).  If you want
something else to run there, put it in instead, for example:  </para>

<para><screen>/opt/kde/bin/kdmdesktop
</screen>
</para>
</sect1>

<sect1 id="k-anywhere">
<title>I'd like to click the left mouse button anywhere on the desktop and have the 'K' menu displayed. </title>

<para>First, edit $HOME/.kde/share/config/krootwmrc and add the following
two lines:
<screen>[MouseButtons]
Left=Menu
</screen>

Then restart KDE.</para>
</sect1>

<sect1 id="idiotic-keys">
<title>How do I use the three extra keys on my Windows keyboard in KDE?</title>

<para>You may have to configure your X server via xmodmap to bind the keycodes
of the Windows keys to useful X key symbols (xev is your friend!).</para>

<para>First, create a file $HOME/.Xmodmap containing the entries:</para>

<para><screen>keycode 115=F13
keycode 117=F15
</screen>
</para>

<para>Then run 
<screen>xmodmap ~/.Xmodmap
</screen>
</para>

<para>This sets the 'Start' key to emit F13 and the 'Windows' key to emit
F15.  Next, fire up the KDE Control Center and go to Keys-&gt;Global
Keys.  Set 'Pop-up system menu' to F13 and 'Window operations menu' to
F15.  That's it.</para>

<para>Please note that the numbers 115 and 117 may depend on the keyboard.  If
you aren't sure, please check using xev.  In addition, the above
procedure requires KDE 1.1 and above.</para>

<para>As a side note, kikbd is able to do this too, but keymaps have to be
edited.  The advantage of kikbd is that one can choose whether to use
these mappings on several custom keymaps and have them hotswappable.</para>

<para>It would be interesting to make a little script which will automatically do
the keymaps modifications on demand.  Kikbd should be able to
read/understand user-side keymap files.</para>
</sect1>

<sect1 id="red-hat-menu-disappears">
<title>After installing KDE, the Red Hat start menu disappears!</title>

<para>Just run the command: </para>

<para><screen>wmconfig --output kde
</screen>
</para>

<para>This will put the Redhat-specific icons into your KDE menu. If you run
this from within KDE, you will need to restart your panel. They are
installed by default into the "applnk" folder after you run that
command, but then you can copy and paste them wherever you like with
the KDE Menu Editor.  </para>
</sect1>

<sect1 id="kde-themes">
<title>Where do I find information regarding KDE themes?</title>

<para>Go see <ulink url="http://kde.themes.org/">http://kde.themes.org/</ulink>. </para>
</sect1>

<sect1 id="mime-types">
<title>How do I change Mime Types?</title>

<para>First, open a KFM window and choose Edit-&gt;Mime Types.  In mime type
tree find the type you want to change (e.g. text/english or
image/gif), click the right mouse button, select Properties, choose
the Binding tab and set Default Application to whatever you 
want. </para>
</sect1>

<sect1 id="bash-profile">
<title>KDE (kdm) doesn't read my .bash&lowbar;profile!</title>

<para>Well, xdm (and kdm) doesn't run a login shell, so .profile,
.bash&lowbar;profile, etc. are not sourced.  When the user logs in, xdm runs
Xstartup as root and then Xsession as user.  So the normal practice is
to add statements in Xsession to source the user profile.  Please
edit your Xsession and .xsession files.</para>
</sect1>

<sect1 id="truetype-fonts">
<title>How do I use TrueType Fonts under KDE?</title>

<para>You need to install TrueType Font support to your X Window System.
Please take a look at <ulink url="http://fonts.themes.org/install.shtml">fonts.themes.org</ulink> for the fonts, and <ulink url="http://www.dcs.ed.ac.uk/home/jec/programs/xfsft/">xfstt</ulink> or
<ulink url="http://hawk.ise.chuo-u.ac.jp/student/person/tshiozak/x-tt/index-eng.html">X-TT</ulink> for the font servers.</para>

<para>If you've a bunch of TrueType fonts from MS Windows, edit the
XF86Config file to get the fonts from the font folder.  Then just tell
KDE to use these new fonts with the font administrator utility.</para>

<para>However, many KDE 1.0 applications use a font dialog that does
not use the font list of KDE.  But there is a workaround: edit the rc
files of the rebellious applications directly. </para>
</sect1>

<sect1 id="euro-symbol">
<title>Is it possible to enter, show and work with the Euro Symbol in KDE?</title>

<para>Yes and no.  For details, look here: <ulink url="http://monitor.blvk.ch/euro/">http://monitor.blvk.ch/euro/</ulink>.</para>
</sect1>
</chapter>

<chapter id="KDEapplications">
<title>KDE applications</title>

<sect1 id="kppp">
<title>Kppp</title>

<para>Many KDE users report problems using Kppp. But before you complain
about Kppp, make sure you have already checked the following:</para>

<para><itemizedlist>
<listitem>
<para> can you dial-up to your ISP without using Kppp?</para>
</listitem>
<listitem>
<para> have you gone through the Kppp documentation at least three
times and follow its instructions and trouble-shooting suggestions?</para>
</listitem>
</itemizedlist>
</para>

<para>The Kppp documentation can be accessed either by browsing KDE Help or
going directly to the documentation directory, usually
$KDEDIR/share/doc/HTML/default/kppp.  In addition, there's a web page
on "How to set up kppp with ISPs in the UK" at <ulink url="http://www.kppp-archive.freeserve.co.uk/">http://www.kppp-archive.freeserve.co.uk/</ulink>.</para>

<para>Now, if you still encounter problems, here's what might help you solve
them:</para>

<para><itemizedlist>
<listitem>
<para> make sure pppd has the SETUID bit on, i.e. do a chmod +s pppd,
and make sure it is world-executable (chmod a+x pppd).</para>
</listitem>
<listitem>
<para> examine the "options" file of pppd.  You might want to just
replace it with an empty one.  </para>
</listitem>
<listitem>
<para> are there any other programs currently running which may use
the modem, for example mgetty?  Check the permission of /dev/modem,
and make it world-readable. </para>
</listitem>
<listitem>
<para> if you are connected, take a look at the connection
speed.  Maybe you have chosen 115000 but your system is too slow.</para>
</listitem>
</itemizedlist>
</para>

<sect2>
<title>I don't have a valid DNS!  What can I do?</title>

<para>Well, guess what?  Linux, KDE, kppp, etc. have nothing to do with
providing you with a valid DNS.  That is the responsibility of your
ISP.  So write them a nice friendly letter asking them to provide
you with the necessary information to set it up.</para>
</sect2>

<sect2>
<title>How do I change the mtu setting in kppp?</title>

<para>Open up the kppp dialog box and select "Setup".  Choose an existing
account and click "Edit...", or "New..." to create a new dial-up
account.  Select the "Dial" tab and click on the button that says
"Arguments".  Type what you want to change in the Argument textbox
e.g. mtu 296 and click "Add".  When you're satisfied, click "Close".</para>

<para>To make sure the options "took", do one of the followings:
<itemizedlist>
<listitem>
<para> in a terminal window, run /sbin/ifconfig ppp0 and look at the
reported mtu in the output --- it should match your request. </para>
</listitem>
<listitem>
<para> add "debug" and "kdebug" (each on separate lines, no quotes) to your
/etc/ppp/options file and restart your ppp session.  You'll find
debugging messages in /var/log/messages, including mru and mtu
settings. </para>
</listitem>
</itemizedlist>
</para>

<para>If you want, the mru and mtu settings can be added to the options file,
one complete setting per line, no quotes or dashes.</para>
</sect2>

<sect2>
<title>Where are the kppp settings stored?</title>

<para>It is stored in $HOME/.kde/share/config/kppprc.</para>
</sect2>

<sect2>
<title>Kppp connects at a slower speed than normal.</title>

<para>The following might do the trick:
<itemizedlist>
<listitem>
<para> try executing "setserial spd&lowbar;hi"</para>
</listitem>
<listitem>
<para> The default mtu value is 1500, which is too large for a dial-up 
connection.  Try changing it to a smaller value like 296 or 576.
<orderedlist><listitem>
<para> Make sure you are off-line and click on the kppp "setup" button.
Choose your dialup account from the list, and click the "edit" button.</para>
</listitem>
<listitem>
<para> Under the "Dial" tab, at the bottom of the dialog, find a button
labelled "Arguments" and click it.</para>
</listitem>
<listitem>
<para> You should be in a "Customize" window, where you can add line-item
configuration parameters (those are documented in the pppd man page).</para>
</listitem>
</orderedlist>

In this fashion, I added the following entries to the list:
<screen>mru 296
mtu 296
</screen>
</para>
</listitem>
<listitem>
<para> check in your $HOME/.kde/share/config for the kppprc.  Ensure
the correct modem speed is actually defined there.</para>
</listitem>
</itemizedlist>
</para>
</sect2>
</sect1>

<sect1 id="kscd">
<title>Kscd</title>

<para>This application comes with a fine documentation called "The Kscd Handbook"
which can be accessed through KDE Help.  Make sure you have gone
through it thoroughly before you ask anything.</para>

<sect2>
<title>How do I close it?</title>

<para>If you've read up, you wouldn't have to ask....  There is a little button
on the interface that has a 1 and 0 that is supposed to look like an
on/off switch.  Clicking on it will exit the CD player.  (It is located in the
lower left hand side of the CD player.)</para>

<para>Current snapshot of Kscd has solved this confusing behaviour by 
making the X close the window and where the 1 0 was is now the "DOCK" 
button. </para>
</sect2>

<sect2>
<title>How do I get Kscd to work with CDDB?</title>

<para>If you are using version 1.2.0, try upgrading.</para>
</sect2>

<sect2>
<title>Kscd claims that there is no /dev/cdrom in my system when I try to listen to a music CD.  What should I do?</title>

<para>Create a symlink from the actual cdrom device to /dev/cdrom.  For
example: ln -s /dev/hdc /dev/cdrom.</para>

<para>An easy way to find out your actual cdrom device is to look in
the file /var/log/dmesg for a line similar to:
<screen>hdc: CD-ROM 48X/AKU, ATAPI CDROM drive
</screen>
</para>
</sect2>
</sect1>

<sect1 id="kvt">
<title>Kvt</title>

<sect2>
<title>How do I page-up or page-down in kvt? </title>

<para>Use Shift+Page-up and Shift+Page-down.</para>
</sect2>

<sect2>
<title>How do I toggle the behaviour of backspace and delete?</title>

<para>Look under Options-&gt;Terminal of your kvt window.</para>
</sect2>

<sect2>
<title>How do I perform a simple 'cut' from kvt to anything else?</title>

<para>When I do a ls, first I select with the mouse the desired text, press CTRL+C,
then I make the other app active, point the mouse to the relevant part
and press CTRL+V.  Alternatively, highlight the text by dragging with
the left mouse button down and paste by clicking with the middle
button (or both buttons if you have 3 button emulation set and you
are using a two button mouse). </para>
</sect2>

<sect2>
<title>How do I set the size of the scroll-back buffer?</title>

<para>Try:  kvt -sl &lt;number&gt;</para>

<para>By the way, if you execute kvt with some unknown option eg. kvt -x,
kvt will print out a list of valid options.</para>
</sect2>
</sect1>

<sect1 id="koffice">
<title>KOffice</title>

<para>KOffice's home page is at <ulink url="http://koffice.kde.org/">http://koffice.kde.org/</ulink>, and
the answers to some FAQs concerning KOffice can be found there.
Therefore, I will not repeat those answers here.</para>

<sect2>
<title>Where can I find k2url.h?</title>

<para>It's in the kdelibs/kdeutils subdirectory but you would probably
need libkdeutil as well.  To get this as well as the header
file, unless things have changed since a few days ago, pass
'EXTRA&lowbar;SUBDIRS="kdeutils kio"' to make -f Makefile.cvs, make and make
install when you build kdelibs.</para>
</sect2>

<sect2>
<title>Where can I find StatusBarManager.h?</title>

<para>Please look in the corba package for this header file. It should be in
corba's include directory.</para>
</sect2>
</sect1>

<sect1 id="kmail">
<title>KMail</title>

<para>The one which comes with KDE 1.0 is unfortunately quite buggy.
Upgrade, and your problems would (probably) disappear.</para>

<sect2>
<title>How do I leave mail on the server?</title>

<para>Open up the Settings window from the file menu.  Click on the Network tab.
Select your account from the account list and click the Modify button.  This
dialog contains the "Delete mail from server" setting which you must
not select. </para>
</sect2>

<sect2>
<title>How do I automatically insert a text footer within the mail? </title>

<para>The text footer is called a signature file.  What you need to do is
open up a text editor (like kedit) and type in what you want to appear
in the footer.  Save the file under a name like  
signature or footer.  Go into KMail and select File &verbar; Settings...
Look in the "Identity" tab for the "signature file" field.  Click on
the ellipses button and select the file you just created.  Now KMail
will automatically insert that file in any message you write.</para>
</sect2>

<sect2>
<title>How do I export KMail messages to Netscape Mail?</title>

<para>Try (you might need to be root) </para>

<para><screen>cat /home/me/Mail/inbox &gt;&gt; /var/spool/mail/me
</screen>
</para>

<para>and then start Netscape Mail asking it to check for local mail. </para>
</sect2>
</sect1>

<sect1 id="kbiff">
<title>KBiff</title>

<para>KBiff is a mail notification utility and its home page is at <ulink url="http://home.sprintmail.com/~granroth/kbiff/index.html">http://home.sprintmail.com/~granroth/kbiff/index.html</ulink>.</para>

<sect2>
<title>How can one instance of KBiff monitor two mailboxes and take the appropriate action when mails arrive?</title>

<para>Are you getting many mails in both mailboxes?  If so, it would be
better to use two instances to monitor them.  If not, then go to the
'Mailbox' tab and click on the little mailbox icon.  This will create
another mailbox in that instance.  Now, whenever either 
of them gets new mail, KBiff will do all of its new mail stuff....</para>
</sect2>
</sect1>

<sect1 id="ktop">
<title>KTop</title>

<sect2>
<title>Why can't I see anything on it?</title>

<para>It's a bug, albeit easily fixed.  Just resize it by a few pixels and
everything should be all right.</para>
</sect2>
</sect1>
</chapter>

<chapter id="KDEwithnonKDEapplications">
<title>KDE with non-KDE applications</title>

<sect1 id="strange-fonts">
<title>My non-KDE apps like emacs and kterm are running amok with large windows and strange fonts!</title>

<para>It probably has to do with KDE trying to "apply KDE defaults to non-KDE apps", 
which means it uses xrdb to apply X defaults that are supposed to mimic the 
color, font and other settings that you have set for KDE.  However,
experience tells us that this usually breaks things, particularly if
you have carefully tuned the X resources of your non-KDE apps.</para>

<para>The official solution is to bring up the Settings-&gt;Desktop-&gt;Style config panel 
and disable the "apply KDE settings to non-KDE apps" checkbox.  If the 
new setting does not seem to stick, make sure you have clicked 'ok'
directly without clicking 'apply' after making the change.  If it
still refuses to work, there's a brute-force solution: rename or delete the
$KDEDIR/share/apps/kdisplay/app-defaults directory.  This will prevent KDE from
finding the X resource files it applies, and solve the problem.  You
have to exit your session and log back in for everything to return to
normal. </para>

<para>If you don't want to, or can't rename or delete the system-wide
app-defaults directory, you can always copy it to your personal kde
directory (eg. $HOME/.kde/share/apps/kdisplay/app-defaults) and then
edit/add/remove files to taste. </para>

<para>The Settings-&gt;Desktop-&gt;Style panel exists in 1.1pre2, I am not sure of its 
location in previous versions (it exists since around 1.0).  </para>
</sect1>

<sect1 id="star-office">
<title>StarOffice 5.0 Personal Edition for Linux</title>

<para>If you haven't download this monster (70 MB), get it from <ulink url="http://www.stardivision.com/office/so5linux_body.html">http://www.stardivision.com/office/so5linux_body.html</ulink>. </para>

<para>Please remember that the best place to find answers to
StarOffice-related questions isn't here.  Go to <ulink url="http://www.stardivision.com/">StarOffice's website</ulink>
instead.  When you get there, click on "Support" and then "Personal"
and make use of the resources available there.</para>

<sect2>
<title>StarOffice freezes up!</title>

<para>This is no fault of KDE.  Are you perchance using a S3 Virge
card?  If so, the problem lies with the S3 server.  There are   
three ways to it.  The RedHat Xconfigurator will sense that you have a
S3 card and set you up that way, so you may need to use the old xf86config
program to setup X. There is support in the SVGA server for the S3 card
so you will have to use that, but the one from RedHat still gives you
the freeze-up.</para>
<sect3>
<title>Solution &num;1</title>

<para>Go to <ulink url="http://www.xfree86.org/">http://www.xfree86.org/</ulink> and then to their FTP site
and download Xbin.tgz, Xlib.tgz, and XSVGA.tgz (please note that the
latest version is 3.3.3).  Unzip and untar them and then copy them to
/usr/X11R6.  Delete the X link in /etc/X11.  Create a symbolic link to
the SVGA server like this:
<screen> 
ln -s /usr/X11R6/bin/XF86_SVGA /usr/X11R6/bin/X
</screen>
</para>

<para>(or using xf86config will link it if you choose it specifically).  You
may need to tweak your XF86Config file further to get the proper
resolutions and color depth.  Note that the above-mentioned
directories may vary according to your system configuration.</para>

</sect3>
<sect3>
<title>Solution &num;2</title>

<para>Get the Xserver (I assume S3) source code.
Modify the file xc/programs/Xserver/hx/xfree86/accel/s3&lowbar;virge/s3im.c
around line 823
Substitute
<screen>alu |= MIX_MONO_TRANSP;
</screen>

with
<screen>if (alu != 0x00aa0000) alu |= MIX_MONO_TRANSP;
</screen>

in function s3RealImageStipple.  Compile and install the new Xserver.</para>

</sect3>
<sect3>
<title>Solution  &num;3</title>

<para>There is a patch available from StarOffice at <ulink url="http://www.stardivision.com/download/support/patch1_01.tar.gz">http://www.stardivision.com/download/support/patch1_01.tar.gz</ulink>. 
But there's a catch!  You have to install it to StarOffice after you
install StarOffice, but you can't do so because StarOffice will freeze....
One way around this is to install StarOffice under the X SVGA server,
install the patch and then fire up the X S3V server.</para>

</sect3>
</sect2>
</sect1>

<sect1 id="netscape">
<title>Netscape</title>

<sect2>
<title>Why does Netscape load so slow?</title>

<para>Netscape loads slow because it is statically linked with Motif and has
to load all the widgets, etc. when it loads.</para>
</sect2>

<sect2>
<title>Why does Netscape crash when I visit certain websites?</title>

<para>What websites are you visiting?  Java applets will often cause
Netscape to crash.  Since most people use Java applets for spinning buttons
instead of something useful, just turn Java off in Netscape. </para>
</sect2>

<sect2>
<title>Why does Netscape display images in a pixilated manner?</title>

<para>When you run Netscape, try using the -install switch.  For example,
<screen>netscape -install &
</screen>
</para>

<para>This will force Netscape to allocate its own colormap which would
hopefully solve the problem.</para>
</sect2>

<sect2>
<title>How do I export Netscape bookmarks to KFM?</title>

<para>Look under entry: <link linkend="nsbookmark">How do I import Netscape bookmarks?</link>.  </para>
</sect2>

<sect2>
<title>How do I make KDE use Netscape when I create a WWWUrl kdelnk instead of the builtin browser?</title>

<para>You need to create a .kdelnk for Netscape, then edit it (using kfm,
right click & go to properties) and select the right mime-type for
URLs (in application tab pick text/html, text/sgml).  Then go to "Edit
-&gt; global mime-types", then to ./text and edit the properties for html
and sgml -- in "Binding" tab select the default 
application in the list box (since you added the appropriate mime-type to
Netscape's .kdelnk file, it should appear there).</para>
</sect2>
</sect1>
</chapter>

<chapter id="KnownbugfixesforKDE">
<title>Known bugfixes for KDE</title>

<sect1 id="kzip">
<title>Typo in kzip.kdelnk</title>

<para>In the file kzip.kdelnk (usually located in
$KDEDIR/share/applnk/Utilities/), there is a typo error.  Under the
MimeType entry there is an entry "application/x-tbz" that should
be "application/x-tgz" instead.  If not corrected, may lead to the
following error message during KDE startup:</para>

<para><screen>Error
Could not find mime type
application/x-tbz
in opt/kde/share/applnk/Utilities/kzip.kdelnk
</screen>
 </para>
</sect1>

<sect1 id="wrong-charset">
<title>Wrong Charset!</title>

<para>Actually, there are two types of charset errors, which seem to be
independent from each other at least to a certain extend:</para>

<para><orderedlist><listitem>
<para> error message "Wrong charset (unknown)! Setting to default
(us-ascii)!" when starting X/KDE.</para>
</listitem>
<listitem>
<para> error message "KCharset: Wrong Charset!" while working in X/KDE
and launching/closing apps.</para>
</listitem>
</orderedlist>
</para>

<para>To fix (1), first find the locale directory within the tree you
installed KDE to (usually $KDEDIR/share/locale). Next, put a plain
text file named "charset" in the appropriate directory for your
language, say en, and make it world-readable. The file should consist
of one single line indicating the charset, e.g. us-ascii or iso-8859-1
for most European languages. You might need to restart KDE, too.  </para>

<para>If it still doesn't work--as far as (1) is concerned--put a copy of
the "charset" file into the subdirectory for your country as well,
e.g. not only into en, but into en&lowbar;UK or en&lowbar;US as well. Then set all
of the three languages supported by KDE (in the "locale settings"
dialogue box) to the same language and country.  </para>

<para>As for (2), it is actually just a harmless warning message and it's
safe to ignore it. The way to get around it is to refrain from
starting KDE apps from a window. :-)  </para>

<para>But if you really want to get rid of those messages, you can try
making sure that the language settings in the KDE Control Center under
Desktop-&gt;Language are all the same. In my case, I set them all to be
"Default language (C)" and the problem promptly disappeared.  </para>
</sect1>
</chapter>

<chapter id="Usefultips">
<title>Useful tips</title>

<sect1 id="man-pages">
<title>Reading man pages in KDE</title>

<para>Pop up the minicli window (Alt-F2 by default) and type:
'man:&lt;command&gt;'.  It even unpacks on the fly when gzipped. </para>
</sect1>

<sect1 id="quick-window-manipulation">
<title>Move or resize windows quickly</title>

<para>To move a window, press the Alt key and click the left mouse button
together on the window.  Alt-right mouse button will resize it.  Last
but not least, Alt-middle mouse button raises/lowers the window.</para>

<para>For more information about mouse control, please refer to "The K
Window Manager Handbook".</para>

<para>By the way, KDE 1.1 allows you to change these mouse bindings.</para>
</sect1>

<sect1 id="kill-windows-in-kde">
<title>Killing windows in KDE</title>

<para>There is a standard keybinding (Ctrl-Alt-Esc) that gives you a
skull/crossbones cursor.  Click that cursor on a window to 
kill it.</para>

<para>The keybindings are viewable/changeable from the KDE Control Center
Keys-&gt;Global config.  Not possible in KDE 1.0, though.</para>
</sect1>

<sect1 id="switch-windows-managers-on-the-fly">
<title>Switching window managers on the fly</title>

<para>If you want to switch your window manager on the fly, type the
following into a terminal window:
<screen>kwmcom go:fvwm
</screen>

This switches to FVWM, but you can substitute any window manager you like.</para>
</sect1>
</chapter>

<chapter id="Miscellaneousquestions">
<title>Miscellaneous questions</title>

<sect1 id="why-qt">
<title>Why does KDE use Qt?</title>

<para>Qt is a very sophisticated toolkit that provides everything that is needed
to build a modern user interface. Qt is written in C++, thus allowing object
oriented development affording the necessary efficiency and reuse of code necessary
for a project of the enormous size and scope of KDE. In our opinion there is no 
better toolkit available for Unix and that it would have been a grave mistake to
try to build KDE on anything but the best.</para>

<para>Furthermore, all  KDE developers agree that it would have not been 
possible to build KDE in equally short amount of time without the use of Qt.</para>
</sect1>

<sect1 id="why-not-gtk">
<title>Why does KDE not use gtk, xforms, xlib, whatever?</title>

<para>There are a number of toolkits available. To provide a consistent user
interface and to keep used resources such as memory to a minimum, KDE can 
use only one of them. Qt was selected for the reasons mentioned above.</para>
</sect1>

<sect1 id="qt-free">
<title>But Qt isn't free, is it?</title>

<para>That depends on your definition of free. According to our definition it is free, 
since:</para>

<para><itemizedlist>
<listitem>
<para> The Qt libraries and source code are available for free and are
readily available on many FTP site.</para>
</listitem>
<listitem>
<para> You can run application written using Qt for free. No run time
charges apply.</para>
</listitem>
<listitem>
<para> You can develop application with Qt for free as long as you make  
the source code of your applications written in Qt 
readily available. Note -- you can even sell your application, however
you must make its source code readily available if you wish to avoid buying a
license for Qt. </para>
</listitem>
<listitem>
<para> You can distribute Qt as well as application using Qt in any form --
be it on FTP sites or CDs. In particular all Linux distribution may 
press a copy of Qt and its source on their CD's free of charge.</para>
</listitem>
</itemizedlist>
</para>

<para>As KDE was, and is, intended to be a noncommercial 
desktop environment for the X Window system, Qt fits our purposes.</para>

<para>Qt is constantly developed by Troll Tech's dedicated, professional staff. 
Troll Tech devotes all of its resources to improve Qt on a daily basis.
Due to this fact Qt continues to develop at a rate unmatched by any 
L/GPL'ed toolkit, providing us with the best toolkit available under Unix
and providing possible commercial developers for KDE with the quality
and support they need.</para>

<para>Troll Tech AS has announced that the Free Edition of Qt, its popular
Graphical User Interface toolkit, will be 
released under an Open Source license. With the new license,
programmers will be able to distribute and share any 
modifications they make to the Qt Free Edition. A draft version of the
new license text, dubbed the QPL, is available 
at <ulink url="http://www.troll.no/qpl/">http://www.troll.no/qpl/</ulink>. It will be first applied  
to the next major release of the Qt Free Edition; version 2.0. </para>
</sect1>

<sect1 id="qt-clone">
<title>Why not code a L/GPL'ed Qt clone?</title>

<para>Given the threat that Windows NT poses to Unix we feel a strong sense of urgency 
and  believe it to be important to develop a great desktop for UNIX first, before 
we might even want to think about rebuilding the &lowbar;tools&lowbar; we are using to build
this desktop. Given the fact that our resources are limited 
KDE itself can not engage in a Qt cloning project at this point. However, if anyone 
feels that they would prefer a L/GPL'ed version of Qt we would like to encourage
you to write such a L/GPL'ed clone. Keep in mind that Qt is only about 80.000
lines of code while KDE is already more than 500.000 lines and the number is
rising daily so that a precise count is very difficult. This means writing
a Qt clone is definitely feasible and it is only a matter of people who feel 
strongly enough about a L/GPL'ed version of Qt getting together and starting
such a subproject.</para>

<para>Currently, there is a project called <ulink url="http://harmony.ruhr.de">Harmony</ulink> which started to implement a GPL'ed Qt-clone. If you dislike Qt's
license, please consider joining this project. </para>
</sect1>

<sect1 id="mount-filesystems">
<title>How do I mount filesystems (eg. my CD-ROM drive) in KDE?</title>

<para>To mount your CD-ROM drive, first, you (as root) need to add the
following line to /etc/fstab:
<screen>/dev/cdrom     /cdrom     iso9660  ro,user,noauto,unhide
</screen>
</para>

<para>Please make sure that you have a soft link from /dev/cdrom to whatever
/dev/hd? your cdrom is (assuming you are using an ATAPI cdrom).  You
should see something like this when you "ls -l /dev/cdrom".  
<screen>lrwxrwxrwx   1 root     root            8 Jul 28 22:21 /dev/cdrom -&gt; /dev/hdb
</screen>

The above would be done with "ln -s /dev/hdb /dev/cdrom" (as root).</para>

<para>Last but not least, make sure a valid mount point exists for the cdrom to be
mounted on, for example:
<screen>% ls -la /cdrom
total 2
drwxrwsr-x   2 root     cdrom        1024 Sep 14  1995 ./
drwxr-xr-x  24 root     root         1024 Dec  1 21:00 ../
</screen>
</para>

<para>Now you can mount it from the command prompt by typing:
<screen>% mount /cdrom
</screen>
</para>

<para>Or if you prefer, create a KDE device link to your cdrom and place it
on your desktop.  Clicking on it will automatically mount the drive
for you.  Okay, concerning the question of how to make a KDE device
link to your cdrom, please look to KDE Help for the answers.</para>

<para>More information on mounting filesystems can be found by running <literal remap="tt">man
fstab</literal> and <literal remap="tt">man mount</literal> respectively.  </para>
</sect1>

<sect1 id="transparent-background">
<title>Does KDE have terminal emulators with transparent background?</title>

<para>No, but <ulink url="http://www.eterm.org">Eterm</ulink> should
work fine using KDE with KWM. </para>
</sect1>

<sect1 id="kdiskfree">
<title>Is there a way to get various kinds of information about my drive contents: free space, directory size, etc.?</title>

<para>Use the commands du and df from the command prompt.  Refer to their
man pages for usage details.  Or you might want to try kdf and
kdiskfree from KDE, or other filemanagers like midnight commander.</para>
</sect1>

<sect1 id="backspace">
<title>How can I get backspace to work under KDE?</title>

<para>Try running xmodmap -e 'keycode 22 = BackSpace' and see if that fixes
it (apps will have to be restarted for that to take effect).  You
should be able to just stick that in your X startup files like
$HOME/.xinitrc. </para>

<para>Or simply upgrade to XFree86-3.3.3.1-1 and above.</para>

<para>Also, concerning the "Backspace"-Bug (Bug number: kb704): the bug is
fixed somehow by putting the following line into $HOME/.xinitrc: 
<screen>xmodmap -  "keysym Delete = BackSpace"
</screen>
</para>
</sect1>

<sect1 id="k-menu">
<title>How do I create icons for non-KDE applications that I can put in the 'K' menu?  Where do these icons (or kdelnk) go?</title>

<para>Create using your favorite image manipulator, for example, GIMP, and
put them in $KDEDIR/share/icons(/mini) or
$HOME/.kde/share/icons(/mini).  Furthermore, there is a KDE icon
editor lying somewhere....</para>
</sect1>

<sect1 id="programs-without-icons">
<title>What about KDE programs that don't have icons (like KWord)? How do I get them into the menu?</title>

<para>Either use the kmenuedit (K =&gt; Panel =&gt; Edit menus) or right-click on the
kdelnk file and pick Properties =&gt; Execute and pick a nice icon.</para>
</sect1>

<sect1 id="ftp-client">
<title>Does KDE have a graphical FTP client?</title>

<para>Yes, and it's none other than your favourite filemanager, KFM.  You
can drag and drop remote files into local directories.  There's also a
utility called KGet that allows resuming and queueing, but you need to
use it in combination with KFM (you can drag-n-drop into KGet but
cannot use it to browse FTP servers).  </para>

<para>Of course, you aren't required to use FTP clients provided by KDE at
all.  WxFTP seems to be a very popular alternative.</para>
</sect1>

<sect1 id="exit-kde">
<title>How do I exit KDE?</title>

<para>Click on that funny looking X thing above the padlock next
to the desktop buttons on the panel to exit KDE.  CTRL-ALT-BACKSPACE
will also do the trick by killing the X server, but its use prevents
session management.  In addition, there's a logout option from the "K"
button, the "Where do you want to go tomorrow?" one.  Last but not
least, if you right-click on an empty area of the desktop, you will be
presented with a menu containing logout as one of the options.</para>
</sect1>

<sect1 id="check-mail">
<title>Is there a program that checks for new mails at my ISP if and only if I'm online?</title>

<para>KOrn and KBiff will both do the job.  It doesn't matter if you
are connected or not -- if you are not connected, both will just sit
there (idling).</para>
</sect1>

<sect1 id="latest-version">
<title>Is it really necessary to upgrade to the latest version?</title>

<para>Not really.  But if you are interested in installing new KDE programs
and also upgrading existing buggy ones, it would probably be necessary
to upgrade.  KMail, for example, is almost unusable in 1.0 but pretty
decent in version 1.1 and later.  To conclude,  if you want a more
polished environment, an increase in speed and the number of features,
then you should upgrade now! </para>
</sect1>

<sect1 id="copy-and-paste">
<title>How do I copy and paste in KDE?</title>

<para>The simplest method is to use your mouse:
<orderedlist><listitem>
<para> highlight the text you want to copy by holding down the left button.</para>
</listitem>
<listitem>
<para> go to the destination area; depending on your configuration,
you might need to click it using the left button to give it focus.</para>
</listitem>
<listitem>
<para> click the middle mouse button to paste.  If you have a two
button mouse and are emulating a three button mouse, push both buttons
simultaneously. </para>
</listitem>
</orderedlist>
</para>
</sect1>

<sect1 id="covert-red-hat-menus">
<title>How do I convert the default Red Hat menus into a menu on the K-Menu?</title>

<para>Click on that 'K' and run System-&gt;Appfinder.</para>
</sect1>

<sect1 id="kdm-and-klock">
<title>Why isn't kdm or klock working in Redhat?</title>

<para>Please check whether you have the /etc/pam.d/kde file.  If it doesn't
exist, create one by copying (or making a symlink) the xdm file to
kde.</para>

<para>However, kdebase-1.1pre2 is supposed to make a symbolic link from
/etc/pam.d/xdm to /etc/pam.d/kde, if it does not exist.</para>

<para>There are reports that the uninstall scripts for kde-1.1pre1 "rh5x"
RPMs interfere with the post-install scripts of kde-1.1pre2 "rh5x" RPMs.</para>

<para>If you have problems, force a reinstall:
<screen>rpm -Uvh --force kdesupport-1.1pre2-1rh5x.i386.rpm
rpm -Uvh --force kdelibs-1.1pre2-1rh5x.i386.rpm
rpm -Uvh --force kdebase-1.1-pre2-1rh5x.i386.rpm
</screen>
</para>
</sect1>

<sect1 id="was-ist-cvs">
<title>What is CVS?</title>

<para>It is an acronym for Concurrent Versions System.  It is a version 
control system and is based on RCS (Revision Control System), but
offers more functionality.  It is
used to maintain source code under development.  It will
keep multiple versions of things (handy if you broke something and
have to back up and get a clean old version), and allows people remote
access over the Net to pick up the latest source code and even to
check in new stuff if they have permission.  It is also open source
(you pay for support if you want it), and since it is free it is the
system of choice for people writing more free products, such as KDE.</para>
</sect1>

<sect1 id="dual-screen">
<title>Does KDE support dual screen?</title>

<para>You need to have the following:
<orderedlist><listitem>
<para> a multi-headed X server (e.g. MertroX)</para>
</listitem>
<listitem>
<para> a window manager that understands a multi-headed display
(e.g. Window Maker)</para>
</listitem>
</orderedlist>
</para>

<para>AFAIK, KWM can't do what you want (yet).</para>
</sect1>

<sect1 id="kde-version">
<title>How do I check which version of KDE I'm using?</title>

<para>Fire up your KDE Control Center.  If there's no mention of KDE's
version number, then it must be 1.0.</para>

<para>Another clear difference is the 'K' on the panel.  In 1.0 it's a
black-and-white 3D K, while in 1.1 it's a white K on top of a wheel.</para>

<para>Or if you have installed KDE from RPMs try:
<screen>$ rpm -qa  | grep kde
kdesupport-1.1pre2-2rh5x
kdeadmin-1.1pre2-1rh5x
kdelibs-1.1pre2-1rh5x
kdegraphics-1.1pre2-1rh5x
kdemultimedia-1.1pre2-1rh5x
kdetoys-1.1pre2-1rh5x
kdegames-1.1pre2-1rh5x
kdeutils-1.1pre2-1rh5x
kdebase-1.1pre2-1rh5x
</screen>

so my current version is 1.1pre2.</para>
</sect1>

<sect1 id="commercial-software">
<title>Can I write commerical software for KDE?</title>

<para>You can use the KDE libs to write "commercial and closed source" as
well as "commercial and open source" software.  If you write open source
software you can use the Qt free edition.  But if you write closed source
software you may not use the Qt free edition; you'd have to obtain the Qt
professional edition from Troll Tech. </para>

<para>If you want more information, please contact Troll Tech directly.</para>
</sect1>
</chapter>

<chapter id="NotreallyKDErelated">
<title>Not really KDE-related, but frequently asked nevertheless :-)</title>

<sect1 id="screen-resolution">
<title>How do I change the screen resolution?</title>

<para>Use Ctrl-Alt-'+' and Ctrl-Alt-'-' to cycle among the resolutions you
have defined in /etc/XF86Config (maybe under /etc/X11/ instead--poke
around first).  If you prefer to get your hands 
dirty, you can always edit the file directly.  By placing your
favourite resolution at the beginning (or making it the only one
listed), X will always start up with that resolution.</para>
</sect1>

<sect1 id="color-depth">
<title>How do I change the color depth?</title>

<para>AFAIK, there's no way you can do it on the fly.  You can either start
X using:
<screen>startx -- -bpp ??
</screen>

where ?? can be 8, 16, 24 or 32 depending on the depth you want, or
if you're using xdm/kdm, you'd have to edit /etc/X11/xdm/Xservers (may
vary) by putting:
<screen>:0 local /usr/X11R6/bin/X -bpp 16
</screen>

for color depth 16.</para>

<para>Alternatively, you can edit the XF86Config file and add a line like
<screen>DefaultColorDepth     ??
</screen>

to Section "Screen".  The next time you start X, it will run with the
newly-configured color depth.</para>
</sect1>

<sect1 id="two-button-mouse">
<title>What can I do if I'm using a 2-button mouse?</title>

<para>Go buy a 3-button one, or use 3rd button emulation.  The 3rd button is
emulated by pressing both left and right buttons together.  You might
need to enable "Emulate3Buttons" in your XF86Config file. </para>
</sect1>

<sect1 id="sticky-window">
<title>What is a "sticky" window?</title>

<para>In a virtual desktop environment with multiple virtual desktops, a
"sticky" window will stay put on the screen when you switch between
desktops, as if sticking to the glass of the screen.  xclock is a typical
candidate for sticking, as you need to run only one instance of it,
and it always stays with you. </para>
</sect1>

<sect1 id="x-pointer">
<title>How do I replace the "X" mouse pointer with an arrow?</title>

<para>The various types of cursor available in X are defined in
X11/cursorfont.h.  You can change it using 'xsetroot -cursor&lowbar;name
NAME&lowbar;OF&lowbar;CURSOR'.  For example, I have the following in my
$HOME/.Xclients: </para>

<para><screen>xsetroot -cursor_name left_ptr
</screen>
</para>

<para>This will create the common left-angled pointer.  To see other
alternatives, type 'xfd -fn cursor'.  And of course, don't forget that 
'man xsetroot' is your friend.</para>
</sect1>

<sect1 id="diff-files">
<title>How do I extract/install diff files?</title>

<para>To generate a context-diff suitable for patching, use:
<screen>diff old-file new-file &gt; patchfile
</screen>
</para>

<para>To apply the diff to a file ("patch the file"), execute:
<screen>patch &lt; patchfile
</screen>
</para>
</sect1>

<sect1 id="recent-kernel">
<title>Should I upgrade to 2.2 kernel?</title>

<para>It depends.  If the 2.2.x kernel provides something you really want or
need that your current kernel does not, then you should upgrade.</para>
</sect1>

<sect1 id="floppy-filesystems-type">
<title>How do I mount the floppy device both in dos and ext2?</title>

<para>Just specify the filesystem type as auto in /etc/fstab. Auto detection
works fine for dos and ext2.</para>
</sect1>

<sect1 id="num-lock">
<title>How do I start KDE with the Num-Lock on?</title>

<para>Have you tried 'man setleds'? </para>

<para>In addition, you might want to edit your $HOME/.Xmodmap and put the
following lines in:</para>

<para><screen>! redefines numeric keypad to be used without NumLock
keycode 79 = 7
keycode 80 = 8
keycode 81 = 9

keycode 83 = 4
keycode 84 = 5
keycode 85 = 6

keycode 87 = 1
keycode 88 = 2
keycode 89 = 3

keycode 90 = 0
keycode 91 = comma
keycode 86 = plus

! deactivates NumLock key
keycode 77 =            
</screen>
</para>

<para>Other possible alternatives: 
<orderedlist><listitem>
<para> xkeycaps: right clicking should allow edits. May have to do
this as root.</para>
</listitem>
<listitem>
<para> "man XF86Config" and look under section Keyboard.</para>
</listitem>
</orderedlist>
</para>
</sect1>

<sect1 id="screenshots">
<title>How do I take window or desktop screenshots?</title>

<para>Use xv, gimp, ksnapshot, whatever.</para>
</sect1>

<sect1 id="html-editor">
<title>Is there somewhere a tool to make webpages? </title>

<para>Yes, and there are a lot of them out there, including StarOffice, Netscape
Composer, XEmacs and last but not least, WebMaker, our very own KDE
web publishing tool!  And by using WINE, it might be possible to run your 
Windows-based tool on PC Unices as well.  Try as many as possible and
choose the one most suitable to your needs.  </para>
</sect1>

<sect1 id="x-server-for-windows">
<title>Where can I find a free X server for Windows 95/98/NT?</title>

<para>You can try downloading MI/X from <ulink url="http://www.microimages.com/">http://www.microimages.com/</ulink>. </para>
</sect1>

<sect1 id="acronyms">
<title>What do all those acronyms like AFAIK mean?</title>

<para><programlisting>AFAIK: as far as I know
BTW: by the way
FWIW: for what it's worth
CMIIW: correct me if I am wrong
IMHO: in my humble opinion
IMAHO: in my always humble opinion
FUD: fear, uncertainty and doubt
BFN: bye for now
AISE: as I see it
AAMOF: as a matter of fact
BION: believe it or not
FYI: for your information
MYOB: mind your own business
SOP: standard operating procedure
RTFM: read the fine manual
YMMV: your mileage may vary
TIA: thanks in advance
HTH: hope this helps
IIRC: if I recall correctly</programlisting>
</para>
</sect1>
</chapter>

<chapter id="Gettingmoreinformation">
<title>Getting more information</title>

<sect1 id="kde-homepage">
<title>Where is the KDE homepage?</title>

<para>The KDE homepage is located at:
<itemizedlist>
<listitem>
<para> <ulink url="http://www.kde.org">http://www.kde.org</ulink></para>
</listitem>
</itemizedlist>
</para>

<para>If you prefer a local mirror, there are several to choose:
<itemizedlist>
<listitem>
<para> <ulink url="http://www.swappy.osc.de/kde/www">http://www.swappy.osc.de/kde/www</ulink></para>
</listitem>
<listitem>
<para> <ulink url="http://ftp.unina.it:21000">http://ftp.unina.it:21000</ulink></para>
</listitem>
<listitem>
<para> <ulink url="http://linux.kreonet.re.kr/kde">http://linux.kreonet.re.kr/kde</ulink></para>
</listitem>
<listitem>
<para> <ulink url="http://kde.a1.nl">http://kde.a1.nl</ulink></para>
</listitem>
<listitem>
<para> <ulink url="http://www.ptf.hro.nl/kde">http://www.ptf.hro.nl/kde</ulink></para>
</listitem>
<listitem>
<para> <ulink url="http://www.tuniv.szczecin.pl/kde">http://www.tuniv.szczecin.pl/kde</ulink></para>
</listitem>
<listitem>
<para> <ulink url="http://kde.fnet.com.pl">http://kde.fnet.com.pl</ulink></para>
</listitem>
<listitem>
<para> <ulink url="http://kde.sw.com.sg">http://kde.sw.com.sg</ulink></para>
</listitem>
<listitem>
<para> <ulink url="http://www.leg.uct.ac.za/mirrors/kde">http://www.leg.uct.ac.za/mirrors/kde</ulink></para>
</listitem>
<listitem>
<para> <ulink url="http://www.kde.ch">http://www.kde.ch</ulink></para>
</listitem>
<listitem>
<para> <ulink url="http://kde.flash.net">http://kde.flash.net</ulink></para>
</listitem>
<listitem>
<para> <ulink url="http://kde.stealth.com.au">http://kde.stealth.com.au</ulink></para>
</listitem>
</itemizedlist>
</para>

<para>For the latest list of WWW mirrors, please refer to <ulink url="http://www.kde.org/webmirrors.html">http://www.kde.org/webmirrors.html</ulink>.</para>
</sect1>

<sect1 id="KDEmailinglists">
<title>Is there a KDE mailing list?  </title>

<para>Well, there is more than one.  Each focuses on a different aspect of KDE.
Some of them are for the developers, so they are not discussed in detail.
The important lists are:
<variablelist>
<varlistentry>
<term>kde</term>
<listitem>
<para>This is the main KDE mailing list for general discussions.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>kde-announce</term>
<listitem>
<para>This list is used to announce new versions of KDE as
well as new tools and applications. </para>
</listitem>
</varlistentry>
<varlistentry>
<term>kde-user</term>
<listitem>
<para>This list is intented for users helping other users.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>kde-look</term>
<listitem>
<para>This is the list that deals with questions of look & feel and
general user interface considerations.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>kde-licensing</term>
<listitem>
<para>This list is devoted to discussions about the KDE and Qt
license issues.</para>
</listitem>
</varlistentry>
</variablelist>
</para>

<para>For the complete list of mailing lists available, please refer to <ulink url="http://www.kde.org/contact.html">http://www.kde.org/contact.html</ulink>.</para>

<para>Please note that it is not a good idea to ask questions which are
already answered in this FAQ.</para>
</sect1>

<sect1 id="howtosubscribe">
<title>How do I subscribe/unsubscribe to these lists? </title>

<para>All lists are available via the university of T&uuml;bingen.</para>

<sect2>
<title>To subscribe</title>

<para>Send an email to list-request, that is:
<itemizedlist>
<listitem>
<para> <ulink url="mailto:kde-request@kde.org">kde-request@kde.org</ulink></para>
</listitem>
<listitem>
<para> <ulink url="mailto:kde-announce-request@kde.org">kde-announce-request@kde.org</ulink></para>
</listitem>
<listitem>
<para> <ulink url="mailto:kde-user-request@kde.org">kde-user-request@kde.org</ulink></para>
</listitem>
<listitem>
<para> <ulink url="mailto:kde-look-request@kde.org">kde-look-request@kde.org</ulink></para>
</listitem>
<listitem>
<para> <ulink url="mailto:kde-licensing-request@kde.org">kde-licensing-request@kde.org</ulink></para>
</listitem>
</itemizedlist>
</para>

<para>The email must contain</para>

<para><literal remap="tt">subscribe</literal> <emphasis remap="it">your email address</emphasis></para>

<para>in the subject of the message.</para>
</sect2>

<sect2>
<title>To unsubscribe</title>

<para>Send an email to list-request, that is:
<itemizedlist>
<listitem>
<para> <ulink url="mailto:kde-request@kde.org">kde-request@kde.org</ulink></para>
</listitem>
<listitem>
<para> <ulink url="mailto:kde-announce-request@kde.org">kde-announce-request@kde.org</ulink></para>
</listitem>
<listitem>
<para> <ulink url="mailto:kde-user-request@kde.org">kde-user-request@kde.org</ulink></para>
</listitem>
<listitem>
<para> <ulink url="mailto:kde-look-request@kde.org">kde-look-request@kde.org</ulink></para>
</listitem>
<listitem>
<para> <ulink url="mailto:kde-licensing-request@kde.org">kde-licensing-request@kde.org</ulink></para>
</listitem>
</itemizedlist>
</para>

<para>The email must contain</para>

<para><literal remap="tt">unsubscribe</literal> <emphasis remap="it">your email address</emphasis></para>

<para>in the subject of the message.</para>

<para><emphasis remap="bf"> PLEASE: Never send subscribe/unsubscribe request to the mailing list
directly! </emphasis> Use the list-request instead.</para>
</sect2>
</sect1>

<sect1 id="mailing-list-archive">
<title>Is there a mailing list archive?</title>

<para>Yes, there is a searchable mailing list archive hosted by <ulink url="http://www.progressive-comp.com">Progressive Computer Concepts</ulink>.  The URL is: <ulink url="http://lists.kde.org">http://lists.kde.org</ulink>.  </para>

<sect2>
<title>How do I search it?</title>

<para>Point your browser at <ulink url="http://lists.kde.org/">http://lists.kde.org/</ulink>.  There you
will see a directory listing of the mailing lists.  Note that you can
only do a subject/author search at this level.  You probably will not
find what you want doing this kind of search.</para>

<para>To do a body search, you have to enter one of the mailing lists.  Just
click on the folder you want to search (e.g. "kde" or "kde-user") and
then the pull-down menu by the search box will default to "Body"
searches.  To be thorough you should probably search the "kde",
"kde-user" and "kde-devel" folders. </para>
</sect2>
</sect1>

<sect1 id="KDEnewsgroups">
<title>Is there a newsgroup about KDE? </title>

<para>Yes, there is!  It's at: <literal remap="tt">comp.windows.x.kde</literal>.  In addition,
there is also a German newsgroup at: <literal remap="tt">de.alt.comp.kde</literal>.  Please
note that it is not a good idea to ask questions which are already
answered in this FAQ.  </para>
</sect1>
</chapter>

<chapter id="Contributing">
<title>Contributing</title>

<sect1 id="how-to-contribute">
<title>How can I contribute to KDE?</title>

<para>KDE is a free software project that lives from voluntary contributions.
Everybody is encouraged to contribute to KDE. Not only programmers are
welcome. There are lots of ways in which you can help to continue KDE:</para>

<para><itemizedlist>
<listitem>
<para> Testing the software</para>
</listitem>
<listitem>
<para> Sending in bug reports</para>
</listitem>
<listitem>
<para> Writing documentation or help files</para>
</listitem>
<listitem>
<para> Translating programs, docu and help files</para>
</listitem>
<listitem>
<para> Drawing nice icons, composing sounds</para>
</listitem>
<listitem>
<para> Writing articles and books about KDE</para>
</listitem>
<listitem>
<para> Programming new KDE applications</para>
</listitem>
<listitem>
<para> Of course, sponsors are also welcome :-)</para>
</listitem>
</itemizedlist>
</para>

<para>There are several places to look for more information if you want to get
involved in the development. The first step is to subscribe to some of the
mailing lists. You will soon see something that can be improved or added.</para>
</sect1>

<sect1 id="bug-report">
<title>How do I commit a bug report? </title>

<para> 
There is an automatic bug tracking
system available at: </para>

<para> <ulink url="http://buglist.kde.org">http://buglist.kde.org</ulink> </para>

<para> 
The system features an entry form to
commit new bug descriptions and a list of all known bugs. Please make sure to
look through the buglist before committing a new bug.</para>
</sect1>

<sect1 id="want-to-program">
<title>I want to program for KDE.  What should I do first?</title>

<para>Everybody is encouraged to develop software for KDE.  What you should do
first depends strongly on your experience, e.g. whether you have
already learned C++ or have experience with the Qt toolkit and so on.</para>

<para>To get into KDE programming, you will need some basic tools: automake,
autoconf and egcs.  You should look at <ulink url="http://developer.kde.org/">http://developer.kde.org/</ulink> and <ulink url="http://www.ph.unimelb.edu.au/~ssk/kde/devel/">http://www.ph.unimelb.edu.au/~ssk/kde/devel/</ulink> for more tips.</para>

<para>Another excellent resource for learning KDE programming is the QT
online tutorials.  These are installed along with QT. Open up in
KDE Help or KFM: $QTDIR/html/index.html and bookmark it.  The
tutorial is under "Using QT".  The source code for each lesson 
can be found in the $QTDIR/tutorial directory.</para>

<para>There is, however, one thing that everybody interested in programming for
KDE should do: subscribe to the developers mailing list. To subscribe, you
have to send a mail with your email address in the subject to:</para>

<para><ulink url="mailto:kde-devel-request@kde.org">kde-devel-request@kde.org</ulink></para>

<para>Please read <link linkend="howtosubscribe">How to subscribe to these lists</link>
carefully. Everything said there applies to the development list as well.</para>
</sect1>

<sect1 id="kde-core-devel">
<title>How do I get write access to the kde-core-devel list? </title>

<para> 
By default, when you have subscribed to the kde-core-devel list, you
will not be able to post on this list; you can just receive the
messages. If you want to post on this list, you have to contact
<ulink url="mailto:konold@kde.org">Martin Konold</ulink> first. He
will add you to the list of people allowed to write on kde-core-devel.  </para>

<para> 
This is not a kind of censorship: Everybody interested in developing will
get write access to the list. We think that this procedure is a good way to
keep the signal to noise ratio high on this list.</para>

<para>By the way, kde-devel has been opened up--anyone can post to it
now.  </para>
</sect1>

<sect1 id="access-to-cvs">
<title>How do I get access to the CVS? </title>

<para> 
The KDE project uses the CVS system to develop the core parts of the
software. Usually, if you have changed one of this parts, perhaps fixed a
bug, and you want to commit this change, the best way is to create a patch
against a current snapshot and send this patch to the developer/maintainer
of the respective program. </para>

<para> 
If you are doing this more or less regularly, you can ask <ulink url="mailto:coolo@kde.org">Stephan Kulow</ulink> for direct access to the
CVS. But be aware that more and more users will slow down the CVS access for
all developers, so we want to keep the number of people with direct CVS
access reasonably small. But feel free to ask!</para>
</sect1>

<sect1 id="read-only-cvs">
<title>I am just curious. Can I have read-only access to the CVS? </title>

<para> 
Yes.  It is possible to get read-only access to the CVS repository with the
<literal remap="tt">cvsup</literal> utility. </para>

<para>You can find more information about how to set up cvsup for the KDE
repository at the <ulink url="http://www.kde.org/cvsup.html">KDE cvsup page</ulink>.</para>
</sect1>

<sect1 id="cvs-mirrors">
<title>Are there any CVS mirror sites for KDE?</title>

<para>Yes.  The main KDE server is normally very busy and unresponsive.
Please take a look at <ulink url="http://www.kde.org/cvsupmirrors.html">http://www.kde.org/cvsupmirrors.html</ulink>
for the list of available mirrors.  For example, to use the mirror
cvsup.nl.freebsd.org, simply replace 
<screen> 
*default host=cvs.kde.org
</screen>

with
<screen> 
*default host=cvsup.nl.freebsd.org
</screen>

in your cvsup script.</para>
</sect1>

<sect1 id="translating">
<title>How do I go about translating KDE programs into my native language?</title>

<para>Take a look at <ulink url="http://www.kde.org/i18n.html">http://www.kde.org/i18n.html</ulink> to see whether
your program is already translated (most are).  Otherwise you'll find
information there on how to do it yourself. </para>
</sect1>
</chapter>
</book>
<!--
Local Variables:
mode: sgml
sgml-omittag: nil
sgml-shorttag: t
End:
-->
