Version:           inconnu (using KDE 3.1.2)
Installed from:    compiled sources
Compiler:          gcc version 3.2.2 (Mandrake Linux 9.1 3.2.2-3mdk)
OS:          Linux (i686) release 2.4.21-0.13mdk

In khelpcenter_userguide_history.pot

>At the time of writing, &kde; 3.0 is in preparation for >release, introducing 
>a broad range of improvements over the 2.0 series. 

In khelpcenter_userguide_installation.pot
The Qt libraries, version 3.0.2. You can obtain these at <ulink 
url=\"ftp://ftp.trolltech.com/qt\">Troll Tech's FTP Server</ulink> in tgz 
format.

This will unpack the base distribution and install it by default in 
<filename>/opt/kde</filename>.

The installation for a Debian system is also rather straightforward. You 
will only find KDE 2.0 packages for Debian 2.2 (Potato) and 3.0 (Woody). We 
describe here how to install packages for Debian 2.2, the stable version, 
since Debian 3.0 is still in development. However, the installation for both 
versions, is almost identical. The main difference is that KDE is officially 
included in Debian 3.0 and you do not need to specify any special location 
to find the deb packages for KDE.

The control files for some KDE applications will be placed at <filename 
class=\"directory\">/etc/kde2</filename>, the executables will go in 
<filename class=\"directory\">/usr/bin</fil

http://kde.tdyc.com/ stable 
kde2
=>unknown host

Qt development version 2.2 or higher.

/usr/src/kdesupport
(remove kdesupport whereever it is please)

Make sure you have write permissions to <filename>/opt/kde</filename>.

 By default, configure will look 
in <filename>/opt/kde</filename>
=>no ! /usr/local/kde

ftp://sunsite.unc.edu/pub/GNU
=>does not exist

In khelpcenter_userguide_kdebase.pot (and all other package docs)
ftp.kde.org/pub/kde/stable/latest/distribution/stable
=>does not exist

ftp.kde.org/pub/kde/unstable/CVS/snapshots/current
=>does not exist

In khelpcenter_userguide_first-impressions.po
When you boot a &UNIX; system, one of two things should happen (that is, if 
the system works correctly; everything else is an undocumented third case). 
Either you stay in text mode and get a login prompt or you are presented 
with a graphical login window. In the former case, you must log into your 
system and type:
=>No ! Tree possible events. The third one is autologin.

In kcontrol_kdm
If you do not specify a logo the default 
<filename>$<envar>KDEDIR</envar>/share/apps/kdm/pics/kdelogo.xpm</filename> 
will be displayed.
=>no ! kdelogo.png

In kcontrol_kcmnotify
Currently, you can only play <literal role=\"extension\">.wav</literal> 
files. This will likely change in future releases.

=>No ! Other formats seem working.

Thanks !

Gerard