Second part of prior commit

69 files changed, 17849 insertions, 0 deletions

diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/Makefile.am b/tde-i18n-en_GB/docs/tdebase/khelpcenter/Makefile.am
new file mode 100644
index 00000000000..6276b21da92
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/Makefile.am
@@ -0,0 +1,4 @@
+KDE_LANG = en_GB
+SUBDIRS = $(AUTODIRS)
+KDE_DOCS = khelpcenter
+KDE_MANS = AUTO
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/Makefile.in b/tde-i18n-en_GB/docs/tdebase/khelpcenter/Makefile.in
new file mode 100644
index 00000000000..426812b2ffa
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/Makefile.in
@@ -0,0 +1,635 @@
+# Makefile.in generated by automake 1.10.1 from Makefile.am.
+# KDE tags expanded automatically by am_edit - $Revision: 483858 $ 
+# @configure_input@
+
+# Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002,
+# 2003, 2004, 2005, 2006, 2007, 2008  Free Software Foundation, Inc.
+# This Makefile.in is free software; the Free Software Foundation
+# gives unlimited permission to copy and/or distribute it,
+# with or without modifications, as long as this notice is preserved.
+
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY, to the extent permitted by law; without
+# even the implied warranty of MERCHANTABILITY or FITNESS FOR A
+# PARTICULAR PURPOSE.
+
+@SET_MAKE@
+VPATH = @srcdir@
+pkgdatadir = $(datadir)/@PACKAGE@
+pkglibdir = $(libdir)/@PACKAGE@
+pkgincludedir = $(includedir)/@PACKAGE@
+am__cd = CDPATH="$${ZSH_VERSION+.}$(PATH_SEPARATOR)" && cd
+install_sh_DATA = $(install_sh) -c -m 644
+install_sh_PROGRAM = $(install_sh) -c
+install_sh_SCRIPT = $(install_sh) -c
+INSTALL_HEADER = $(INSTALL_DATA)
+transform = $(program_transform_name)
+NORMAL_INSTALL = :
+PRE_INSTALL = :
+POST_INSTALL = :
+NORMAL_UNINSTALL = :
+PRE_UNINSTALL = :
+POST_UNINSTALL = :
+subdir = docs/tdebase/khelpcenter
+DIST_COMMON = $(srcdir)/Makefile.am $(srcdir)/Makefile.in
+ACLOCAL_M4 = $(top_srcdir)/aclocal.m4
+am__aclocal_m4_deps = $(top_srcdir)/acinclude.m4 \
+	$(top_srcdir)/configure.in
+am__configure_deps = $(am__aclocal_m4_deps) $(CONFIGURE_DEPENDENCIES) \
+	$(ACLOCAL_M4)
+mkinstalldirs = $(SHELL) $(top_srcdir)/mkinstalldirs
+CONFIG_HEADER = $(top_builddir)/config.h
+CONFIG_CLEAN_FILES =
+SOURCES =
+DIST_SOURCES =
+#>- RECURSIVE_TARGETS = all-recursive check-recursive dvi-recursive \
+#>- 	html-recursive info-recursive install-data-recursive \
+#>- 	install-dvi-recursive install-exec-recursive \
+#>- 	install-html-recursive install-info-recursive \
+#>- 	install-pdf-recursive install-ps-recursive install-recursive \
+#>- 	installcheck-recursive installdirs-recursive pdf-recursive \
+#>- 	ps-recursive uninstall-recursive
+#>+ 7
+RECURSIVE_TARGETS = all-recursive check-recursive dvi-recursive \
+	html-recursive info-recursive install-data-recursive \
+	install-dvi-recursive install-exec-recursive \
+	install-html-recursive install-info-recursive \
+	install-pdf-recursive install-ps-recursive install-recursive \
+	installcheck-recursive installdirs-recursive pdf-recursive \
+	ps-recursive uninstall-recursive nmcheck-recursive bcheck-recursive
+RECURSIVE_CLEAN_TARGETS = mostlyclean-recursive clean-recursive	\
+  distclean-recursive maintainer-clean-recursive
+ETAGS = etags
+CTAGS = ctags
+DIST_SUBDIRS = $(SUBDIRS)
+#>- DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST)
+#>+ 1
+DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST) $(KDE_DIST)
+ACLOCAL = @ACLOCAL@
+AMTAR = @AMTAR@
+ARTSCCONFIG = @ARTSCCONFIG@
+AUTOCONF = @AUTOCONF@
+AUTODIRS = @AUTODIRS@
+AUTOHEADER = @AUTOHEADER@
+AUTOMAKE = @AUTOMAKE@
+AWK = @AWK@
+CONF_FILES = @CONF_FILES@
+CYGPATH_W = @CYGPATH_W@
+DCOPIDL = @DCOPIDL@
+DCOPIDL2CPP = @DCOPIDL2CPP@
+DCOPIDLNG = @DCOPIDLNG@
+DCOP_DEPENDENCIES = @DCOP_DEPENDENCIES@
+DEFS = @DEFS@
+ECHO_C = @ECHO_C@
+ECHO_N = @ECHO_N@
+ECHO_T = @ECHO_T@
+GMSGFMT = @GMSGFMT@
+INSTALL = @INSTALL@
+INSTALL_DATA = @INSTALL_DATA@
+INSTALL_PROGRAM = @INSTALL_PROGRAM@
+INSTALL_SCRIPT = @INSTALL_SCRIPT@
+INSTALL_STRIP_PROGRAM = @INSTALL_STRIP_PROGRAM@
+KCFG_DEPENDENCIES = @KCFG_DEPENDENCIES@
+KCONFIG_COMPILER = @KCONFIG_COMPILER@
+KDECONFIG = @KDECONFIG@
+KDE_EXTRA_RPATH = @KDE_EXTRA_RPATH@
+KDE_RPATH = @KDE_RPATH@
+KDE_XSL_STYLESHEET = @KDE_XSL_STYLESHEET@
+LIBOBJS = @LIBOBJS@
+LIBS = @LIBS@
+LN_S = @LN_S@
+LTLIBOBJS = @LTLIBOBJS@
+MAKEINFO = @MAKEINFO@
+MAKEKDEWIDGETS = @MAKEKDEWIDGETS@
+MCOPIDL = @MCOPIDL@
+MEINPROC = @MEINPROC@
+MKDIR_P = @MKDIR_P@
+MSGFMT = @MSGFMT@
+PACKAGE = @PACKAGE@
+PACKAGE_BUGREPORT = @PACKAGE_BUGREPORT@
+PACKAGE_NAME = @PACKAGE_NAME@
+PACKAGE_STRING = @PACKAGE_STRING@
+PACKAGE_TARNAME = @PACKAGE_TARNAME@
+PACKAGE_VERSION = @PACKAGE_VERSION@
+PATH_SEPARATOR = @PATH_SEPARATOR@
+SET_MAKE = @SET_MAKE@
+SHELL = @SHELL@
+STRIP = @STRIP@
+TOPSUBDIRS = @TOPSUBDIRS@
+VERSION = @VERSION@
+XGETTEXT = @XGETTEXT@
+XMLLINT = @XMLLINT@
+X_RPATH = @X_RPATH@
+abs_builddir = @abs_builddir@
+abs_srcdir = @abs_srcdir@
+abs_top_builddir = @abs_top_builddir@
+abs_top_srcdir = @abs_top_srcdir@
+am__leading_dot = @am__leading_dot@
+am__tar = @am__tar@
+am__untar = @am__untar@
+#>- bindir = @bindir@
+#>+ 2
+DEPDIR = .deps
+bindir = @bindir@
+build_alias = @build_alias@
+builddir = @builddir@
+datadir = @datadir@
+datarootdir = @datarootdir@
+docdir = @docdir@
+dvidir = @dvidir@
+exec_prefix = @exec_prefix@
+host_alias = @host_alias@
+htmldir = @htmldir@
+includedir = @includedir@
+infodir = @infodir@
+install_sh = @install_sh@
+kde_appsdir = @kde_appsdir@
+kde_bindir = @kde_bindir@
+kde_confdir = @kde_confdir@
+kde_datadir = @kde_datadir@
+kde_htmldir = @kde_htmldir@
+kde_icondir = @kde_icondir@
+kde_kcfgdir = @kde_kcfgdir@
+kde_libs_htmldir = @kde_libs_htmldir@
+kde_libs_prefix = @kde_libs_prefix@
+kde_locale = @kde_locale@
+kde_mimedir = @kde_mimedir@
+kde_moduledir = @kde_moduledir@
+kde_servicesdir = @kde_servicesdir@
+kde_servicetypesdir = @kde_servicetypesdir@
+kde_sounddir = @kde_sounddir@
+kde_styledir = @kde_styledir@
+kde_templatesdir = @kde_templatesdir@
+kde_wallpaperdir = @kde_wallpaperdir@
+kde_widgetdir = @kde_widgetdir@
+tdeinitdir = @tdeinitdir@
+libdir = @libdir@
+libexecdir = @libexecdir@
+localedir = @localedir@
+localstatedir = @localstatedir@
+mandir = @mandir@
+mkdir_p = @mkdir_p@
+oldincludedir = @oldincludedir@
+pdfdir = @pdfdir@
+prefix = @prefix@
+program_transform_name = @program_transform_name@
+psdir = @psdir@
+sbindir = @sbindir@
+sharedstatedir = @sharedstatedir@
+srcdir = @srcdir@
+sysconfdir = @sysconfdir@
+target_alias = @target_alias@
+top_builddir = @top_builddir@
+top_srcdir = @top_srcdir@
+xdg_appsdir = @xdg_appsdir@
+xdg_directorydir = @xdg_directorydir@
+xdg_menudir = @xdg_menudir@
+KDE_LANG = en_GB
+#>- SUBDIRS = $(AUTODIRS)
+#>+ 1
+SUBDIRS =. glossary quickstart userguide faq visualdict
+KDE_DOCS = khelpcenter
+KDE_MANS = AUTO
+#>- all: all-recursive
+#>+ 1
+all: docs-am  all-recursive
+
+.SUFFIXES:
+$(srcdir)/Makefile.in:  $(srcdir)/Makefile.am  $(am__configure_deps)
+#>- 	@for dep in $?; do \
+#>- 	  case '$(am__configure_deps)' in \
+#>- 	    *$$dep*) \
+#>- 	      cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh \
+#>- 		&& exit 0; \
+#>- 	      exit 1;; \
+#>- 	  esac; \
+#>- 	done; \
+#>- 	echo ' cd $(top_srcdir) && $(AUTOMAKE) --gnu  docs/tdebase/khelpcenter/Makefile'; \
+#>- 	cd $(top_srcdir) && \
+#>- 	  $(AUTOMAKE) --gnu  docs/tdebase/khelpcenter/Makefile
+#>+ 12
+	@for dep in $?; do \
+	  case '$(am__configure_deps)' in \
+	    *$$dep*) \
+	      cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh \
+		&& exit 0; \
+	      exit 1;; \
+	  esac; \
+	done; \
+	echo ' cd $(top_srcdir) && $(AUTOMAKE) --gnu  docs/tdebase/khelpcenter/Makefile'; \
+	cd $(top_srcdir) && \
+	  $(AUTOMAKE) --gnu  docs/tdebase/khelpcenter/Makefile
+	cd $(top_srcdir) && perl ../scripts/admin/am_edit -p../scripts/admin docs/tdebase/khelpcenter/Makefile.in
+.PRECIOUS: Makefile
+Makefile: $(srcdir)/Makefile.in $(top_builddir)/config.status
+	@case '$?' in \
+	  *config.status*) \
+	    cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh;; \
+	  *) \
+	    echo ' cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__depfiles_maybe)'; \
+	    cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__depfiles_maybe);; \
+	esac;
+
+$(top_builddir)/config.status: $(top_srcdir)/configure $(CONFIG_STATUS_DEPENDENCIES)
+	cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
+
+$(top_srcdir)/configure:  $(am__configure_deps)
+	cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
+$(ACLOCAL_M4):  $(am__aclocal_m4_deps)
+	cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
+
+# This directory's subdirectories are mostly independent; you can cd
+# into them and run `make' without going through this Makefile.
+# To change the values of `make' variables: instead of editing Makefiles,
+# (1) if the variable is set in `config.status', edit `config.status'
+#     (which will cause the Makefiles to be regenerated when you run `make');
+# (2) otherwise, pass the desired values on the `make' command line.
+$(RECURSIVE_TARGETS):
+	@failcom='exit 1'; \
+	for f in x $$MAKEFLAGS; do \
+	  case $$f in \
+	    *=* | --[!k]*);; \
+	    *k*) failcom='fail=yes';; \
+	  esac; \
+	done; \
+	dot_seen=no; \
+	target=`echo $@ | sed s/-recursive//`; \
+	list='$(SUBDIRS)'; for subdir in $$list; do \
+	  echo "Making $$target in $$subdir"; \
+	  if test "$$subdir" = "."; then \
+	    dot_seen=yes; \
+	    local_target="$$target-am"; \
+	  else \
+	    local_target="$$target"; \
+	  fi; \
+	  (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS) $$local_target) \
+	  || eval $$failcom; \
+	done; \
+	if test "$$dot_seen" = "no"; then \
+	  $(MAKE) $(AM_MAKEFLAGS) "$$target-am" || exit 1; \
+	fi; test -z "$$fail"
+
+$(RECURSIVE_CLEAN_TARGETS):
+	@failcom='exit 1'; \
+	for f in x $$MAKEFLAGS; do \
+	  case $$f in \
+	    *=* | --[!k]*);; \
+	    *k*) failcom='fail=yes';; \
+	  esac; \
+	done; \
+	dot_seen=no; \
+	case "$@" in \
+	  distclean-* | maintainer-clean-*) list='$(DIST_SUBDIRS)' ;; \
+	  *) list='$(SUBDIRS)' ;; \
+	esac; \
+	rev=''; for subdir in $$list; do \
+	  if test "$$subdir" = "."; then :; else \
+	    rev="$$subdir $$rev"; \
+	  fi; \
+	done; \
+	rev="$$rev ."; \
+	target=`echo $@ | sed s/-recursive//`; \
+	for subdir in $$rev; do \
+	  echo "Making $$target in $$subdir"; \
+	  if test "$$subdir" = "."; then \
+	    local_target="$$target-am"; \
+	  else \
+	    local_target="$$target"; \
+	  fi; \
+	  (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS) $$local_target) \
+	  || eval $$failcom; \
+	done && test -z "$$fail"
+tags-recursive:
+	list='$(SUBDIRS)'; for subdir in $$list; do \
+	  test "$$subdir" = . || (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS) tags); \
+	done
+ctags-recursive:
+	list='$(SUBDIRS)'; for subdir in $$list; do \
+	  test "$$subdir" = . || (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS) ctags); \
+	done
+
+ID: $(HEADERS) $(SOURCES) $(LISP) $(TAGS_FILES)
+	list='$(SOURCES) $(HEADERS) $(LISP) $(TAGS_FILES)'; \
+	unique=`for i in $$list; do \
+	    if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
+	  done | \
+	  $(AWK) '{ files[$$0] = 1; nonemtpy = 1; } \
+	      END { if (nonempty) { for (i in files) print i; }; }'`; \
+	mkid -fID $$unique
+tags: TAGS
+
+TAGS: tags-recursive $(HEADERS) $(SOURCES)  $(TAGS_DEPENDENCIES) \
+		$(TAGS_FILES) $(LISP)
+	tags=; \
+	here=`pwd`; \
+	if ($(ETAGS) --etags-include --version) >/dev/null 2>&1; then \
+	  include_option=--etags-include; \
+	  empty_fix=.; \
+	else \
+	  include_option=--include; \
+	  empty_fix=; \
+	fi; \
+	list='$(SUBDIRS)'; for subdir in $$list; do \
+	  if test "$$subdir" = .; then :; else \
+	    test ! -f $$subdir/TAGS || \
+	      tags="$$tags $$include_option=$$here/$$subdir/TAGS"; \
+	  fi; \
+	done; \
+	list='$(SOURCES) $(HEADERS)  $(LISP) $(TAGS_FILES)'; \
+	unique=`for i in $$list; do \
+	    if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
+	  done | \
+	  $(AWK) '{ files[$$0] = 1; nonempty = 1; } \
+	      END { if (nonempty) { for (i in files) print i; }; }'`; \
+	if test -z "$(ETAGS_ARGS)$$tags$$unique"; then :; else \
+	  test -n "$$unique" || unique=$$empty_fix; \
+	  $(ETAGS) $(ETAGSFLAGS) $(AM_ETAGSFLAGS) $(ETAGS_ARGS) \
+	    $$tags $$unique; \
+	fi
+ctags: CTAGS
+CTAGS: ctags-recursive $(HEADERS) $(SOURCES)  $(TAGS_DEPENDENCIES) \
+		$(TAGS_FILES) $(LISP)
+	tags=; \
+	list='$(SOURCES) $(HEADERS)  $(LISP) $(TAGS_FILES)'; \
+	unique=`for i in $$list; do \
+	    if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
+	  done | \
+	  $(AWK) '{ files[$$0] = 1; nonempty = 1; } \
+	      END { if (nonempty) { for (i in files) print i; }; }'`; \
+	test -z "$(CTAGS_ARGS)$$tags$$unique" \
+	  || $(CTAGS) $(CTAGSFLAGS) $(AM_CTAGSFLAGS) $(CTAGS_ARGS) \
+	     $$tags $$unique
+
+GTAGS:
+	here=`$(am__cd) $(top_builddir) && pwd` \
+	  && cd $(top_srcdir) \
+	  && gtags -i $(GTAGS_ARGS) $$here
+
+distclean-tags:
+	-rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
+
+#>- distdir: $(DISTFILES)
+#>+ 1
+distdir: distdir-nls  $(DISTFILES)
+	@srcdirstrip=`echo "$(srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \
+	topsrcdirstrip=`echo "$(top_srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \
+	list='$(DISTFILES)'; \
+	  dist_files=`for file in $$list; do echo $$file; done | \
+	  sed -e "s|^$$srcdirstrip/||;t" \
+	      -e "s|^$$topsrcdirstrip/|$(top_builddir)/|;t"`; \
+	case $$dist_files in \
+	  */*) $(MKDIR_P) `echo "$$dist_files" | \
+			   sed '/\//!d;s|^|$(distdir)/|;s,/[^/]*$$,,' | \
+			   sort -u` ;; \
+	esac; \
+	for file in $$dist_files; do \
+	  if test -f $$file || test -d $$file; then d=.; else d=$(srcdir); fi; \
+	  if test -d $$d/$$file; then \
+	    dir=`echo "/$$file" | sed -e 's,/[^/]*$$,,'`; \
+	    if test -d $(srcdir)/$$file && test $$d != $(srcdir); then \
+	      cp -pR $(srcdir)/$$file $(distdir)$$dir || exit 1; \
+	    fi; \
+	    cp -pR $$d/$$file $(distdir)$$dir || exit 1; \
+	  else \
+	    test -f $(distdir)/$$file \
+	    || cp -p $$d/$$file $(distdir)/$$file \
+	    || exit 1; \
+	  fi; \
+	done
+	list='$(DIST_SUBDIRS)'; for subdir in $$list; do \
+	  if test "$$subdir" = .; then :; else \
+	    test -d "$(distdir)/$$subdir" \
+	    || $(MKDIR_P) "$(distdir)/$$subdir" \
+	    || exit 1; \
+	    distdir=`$(am__cd) $(distdir) && pwd`; \
+	    top_distdir=`$(am__cd) $(top_distdir) && pwd`; \
+	    (cd $$subdir && \
+	      $(MAKE) $(AM_MAKEFLAGS) \
+	        top_distdir="$$top_distdir" \
+	        distdir="$$distdir/$$subdir" \
+		am__remove_distdir=: \
+		am__skip_length_check=: \
+	        distdir) \
+	      || exit 1; \
+	  fi; \
+	done
+check-am: all-am
+check: check-recursive
+all-am: Makefile
+installdirs: installdirs-recursive
+installdirs-am:
+install: install-recursive
+install-exec: install-exec-recursive
+install-data: install-data-recursive
+#>- uninstall: uninstall-recursive
+#>+ 1
+uninstall: uninstall-docs uninstall-nls  uninstall-recursive
+
+install-am: all-am
+	@$(MAKE) $(AM_MAKEFLAGS) install-exec-am install-data-am
+
+installcheck: installcheck-recursive
+install-strip:
+	$(MAKE) $(AM_MAKEFLAGS) INSTALL_PROGRAM="$(INSTALL_STRIP_PROGRAM)" \
+	  install_sh_PROGRAM="$(INSTALL_STRIP_PROGRAM)" INSTALL_STRIP_FLAG=-s \
+	  `test -z '$(STRIP)' || \
+	    echo "INSTALL_PROGRAM_ENV=STRIPPROG='$(STRIP)'"` install
+mostlyclean-generic:
+
+clean-generic:
+
+distclean-generic:
+	-test -z "$(CONFIG_CLEAN_FILES)" || rm -f $(CONFIG_CLEAN_FILES)
+
+maintainer-clean-generic:
+	@echo "This command is intended for maintainers to use"
+	@echo "it deletes files that may require special tools to rebuild."
+#>- clean: clean-recursive
+#>+ 1
+clean: kde-rpo-clean  clean-recursive
+
+#>- clean-am: clean-generic mostlyclean-am
+#>+ 1
+clean-am: clean-docs clean-bcheck  clean-generic mostlyclean-am
+
+distclean: distclean-recursive
+	-rm -f Makefile
+distclean-am: clean-am distclean-generic distclean-tags
+
+dvi: dvi-recursive
+
+dvi-am:
+
+html: html-recursive
+
+info: info-recursive
+
+info-am:
+
+#>- install-data-am:
+#>+ 1
+install-data-am: install-docs install-nls 
+
+install-dvi: install-dvi-recursive
+
+install-exec-am:
+
+install-html: install-html-recursive
+
+install-info: install-info-recursive
+
+install-man:
+
+install-pdf: install-pdf-recursive
+
+install-ps: install-ps-recursive
+
+installcheck-am:
+
+maintainer-clean: maintainer-clean-recursive
+	-rm -f Makefile
+maintainer-clean-am: distclean-am maintainer-clean-generic
+
+mostlyclean: mostlyclean-recursive
+
+mostlyclean-am: mostlyclean-generic
+
+pdf: pdf-recursive
+
+pdf-am:
+
+ps: ps-recursive
+
+ps-am:
+
+uninstall-am:
+
+.MAKE: $(RECURSIVE_CLEAN_TARGETS) $(RECURSIVE_TARGETS) install-am \
+	install-strip
+
+.PHONY: $(RECURSIVE_CLEAN_TARGETS) $(RECURSIVE_TARGETS) CTAGS GTAGS \
+	all all-am check check-am clean clean-generic ctags \
+	ctags-recursive distclean distclean-generic distclean-tags \
+	distdir dvi dvi-am html html-am info info-am install \
+	install-am install-data install-data-am install-dvi \
+	install-dvi-am install-exec install-exec-am install-html \
+	install-html-am install-info install-info-am install-man \
+	install-pdf install-pdf-am install-ps install-ps-am \
+	install-strip installcheck installcheck-am installdirs \
+	installdirs-am maintainer-clean maintainer-clean-generic \
+	mostlyclean mostlyclean-generic pdf pdf-am ps ps-am tags \
+	tags-recursive uninstall uninstall-am
+
+# Tell versions [3.59,3.63) of GNU make to not export all variables.
+# Otherwise a system limit (for SysV at least) may be exceeded.
+.NOEXPORT:
+
+#>+ 2
+KDE_DIST=Makefile.in whatiskde.docbook help.docbook support.docbook welcome.docbook index.docbook links.docbook contact.docbook Makefile.am index.cache.bz2 
+
+#>+ 24
+index.cache.bz2: $(srcdir)/index.docbook $(KDE_XSL_STYLESHEET) links.docbook help.docbook whatiskde.docbook support.docbook index.docbook welcome.docbook contact.docbook 
+	@if test -n "$(MEINPROC)"; then echo $(MEINPROC) --check --cache index.cache.bz2 $(srcdir)/index.docbook; $(MEINPROC) --check --cache index.cache.bz2 $(srcdir)/index.docbook; fi
+
+docs-am: index.cache.bz2
+
+install-docs: docs-am install-nls
+	$(mkinstalldirs) $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter
+	@if test -f index.cache.bz2; then \
+	echo $(INSTALL_DATA) index.cache.bz2 $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/; \
+	$(INSTALL_DATA) index.cache.bz2 $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/; \
+	elif test -f  $(srcdir)/index.cache.bz2; then \
+	echo $(INSTALL_DATA) $(srcdir)/index.cache.bz2 $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/; \
+	$(INSTALL_DATA) $(srcdir)/index.cache.bz2 $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/; \
+	fi
+	-rm -f $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/common
+	$(LN_S) $(kde_libs_htmldir)/$(KDE_LANG)/common $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/common
+
+uninstall-docs:
+	-rm -rf $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter
+
+clean-docs:
+	-rm -f index.cache.bz2
+
+
+#>+ 13
+install-nls:
+	$(mkinstalldirs) $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter
+	@for base in links.docbook help.docbook whatiskde.docbook support.docbook index.docbook welcome.docbook contact.docbook ; do \
+	  echo $(INSTALL_DATA) $$base $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/$$base ;\
+	  $(INSTALL_DATA) $(srcdir)/$$base $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/$$base ;\
+	done
+
+uninstall-nls:
+	for base in links.docbook help.docbook whatiskde.docbook support.docbook index.docbook welcome.docbook contact.docbook ; do \
+	  rm -f $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/$$base ;\
+	done
+
+
+#>+ 5
+distdir-nls:
+	for file in links.docbook help.docbook whatiskde.docbook support.docbook index.docbook welcome.docbook contact.docbook ; do \
+	  cp $(srcdir)/$$file $(distdir); \
+	done
+
+#>+ 15
+force-reedit:
+		@for dep in $?; do \
+	  case '$(am__configure_deps)' in \
+	    *$$dep*) \
+	      cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh \
+		&& exit 0; \
+	      exit 1;; \
+	  esac; \
+	done; \
+	echo ' cd $(top_srcdir) && $(AUTOMAKE) --gnu  docs/tdebase/khelpcenter/Makefile'; \
+	cd $(top_srcdir) && \
+	  $(AUTOMAKE) --gnu  docs/tdebase/khelpcenter/Makefile
+	cd $(top_srcdir) && perl ../scripts/admin/am_edit -p../scripts/admin docs/tdebase/khelpcenter/Makefile.in
+
+
+#>+ 21
+clean-bcheck: 
+	rm -f *.bchecktest.cc *.bchecktest.cc.class a.out
+
+bcheck: bcheck-recursive
+
+bcheck-am:
+	@for i in ; do \
+	    if test $(srcdir)/$$i -nt $$i.bchecktest.cc; then \
+	        echo "int main() {return 0;}" > $$i.bchecktest.cc ; \
+	        echo "#include \"$$i\"" >> $$i.bchecktest.cc ; \
+	        echo "$$i"; \
+	        if ! $(CXX) $(DEFS) -I. -I$(srcdir) -I$(top_builddir) $(INCLUDES) $(AM_CPPFLAGS) $(CPPFLAGS) $(CXXFLAGS) $(KDE_CXXFLAGS)  --dump-class-hierarchy -c $$i.bchecktest.cc; then \
+	            rm -f $$i.bchecktest.cc; exit 1; \
+	        fi ; \
+	        echo "" >> $$i.bchecktest.cc.class; \
+	        perl $(top_srcdir)/admin/bcheck.pl $$i.bchecktest.cc.class || { rm -f $$i.bchecktest.cc; exit 1; }; \
+	        rm -f a.out; \
+	    fi ; \
+	done
+
+
+#>+ 3
+final:
+	$(MAKE) all-am
+
+#>+ 3
+final-install:
+	$(MAKE) install-am
+
+#>+ 3
+no-final:
+	$(MAKE) all-am
+
+#>+ 3
+no-final-install:
+	$(MAKE) install-am
+
+#>+ 3
+kde-rpo-clean:
+	-rm -f *.rpo
+
+#>+ 3
+nmcheck: 
+nmcheck-am: nmcheck
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/contact.docbook b/tde-i18n-en_GB/docs/tdebase/khelpcenter/contact.docbook
new file mode 100644
index 00000000000..c164370fb32
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/contact.docbook
@@ -0,0 +1,232 @@
+<chapter id="contact-the-kde-team">
+<chapterinfo
+><date
+>2002-01-18</date
+> <releaseinfo
+>3.00.00</releaseinfo
+> </chapterinfo>
+<title
+>Contact the &kde; team</title>
+<anchor id="contact"/>
+
+<sect1 id="contact-mailinglists">
+<title
+>Mailing lists</title>
+
+<para
+>&kde; has several mailing lists up. See below for some of the most useful. Older articles can be found in the <ulink url="http://lists.kde.org"
+>mailing list archive</ulink
+>.</para>
+
+<variablelist>
+
+<varlistentry>
+<term
+><ulink url="http://mail.kde.org/mailman/listinfo/kde"
+>kde</ulink
+></term>
+<listitem
+><para
+>For general discussion, users helping each other.</para
+></listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+><ulink url="http://mail.kde.org/mailman/listinfo/kde-announce"
+>kde-announce</ulink
+></term>
+<listitem
+><para
+>Announcements of new &kde; applications</para
+></listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+><ulink url="http://mail.kde.org/mailman/listinfo/kde-devel"
+>kde-devel</ulink
+></term>
+<listitem
+><para
+>For developers.</para
+></listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+><ulink url="http://mail.kde.org/mailman/listinfo/kde-artists"
+>kde-artists</ulink
+></term>
+<listitem
+><para
+>Creating icons and other artwork</para
+></listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+><ulink url="http://mail.kde.org/mailman/listinfo/kde-doc-english"
+>kde-doc-english</ulink
+></term>
+<listitem
+><para
+>For people interested in writing documentation for &kde;.</para
+></listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+><ulink url="http://mail.kde.org/mailman/listinfo/tde-i18n-doc"
+>tde-i18n-doc</ulink
+></term>
+<listitem
+><para
+>Internationalisation and documentation issues</para
+></listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+><ulink url="http://i18n.kde.org/teams/"
+>http://i18n.kde.org/teams/</ulink
+></term>
+<listitem
+><para
+>For localised information, which may include user email lists and websites, check the translation teams page at the above &URL;.</para
+></listitem>
+</varlistentry>
+
+</variablelist>
+
+</sect1>
+
+<sect1 id="contact-developers">
+<title
+>Contacting the &kde; developers</title>
+
+<para
+>On this page, you can find links to &kde; related web sites.</para>
+
+<para
+>The K Desktop Environment is developed by a large group of people around the world. Our main communication channel is the Internet. For general questions, you will be best served by asking on the mailing lists mentioned in the <link linkend="contact-mailinglists"
+>previous section</link
+>, and contact addresses for individual developers can be found in the documentation of their individual application.</para>
+
+<para
+>Please visit our <ulink url="http://www.kde.org/contact/representatives.php"
+>Official Representatives</ulink
+> page for official enquiries regarding &kde; (&eg; interviews).</para>
+
+<para
+>More information about &kde; is available at &kde-http;.</para>
+
+<para
+><anchor id="links"/>Other &kde; websites include:</para>
+
+<variablelist>
+<varlistentry>
+<term
+><ulink url="http://www.kde.org"
+>www.kde.org</ulink
+></term>
+<listitem
+><para
+>&kde;'s official website</para
+></listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+><ulink url="http://developer.kde.org"
+>developer.kde.org</ulink
+></term>
+<listitem
+><para
+>The &kde; developers centre</para
+></listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+><ulink url="http://webcvs.kde.org"
+>webcvs.kde.org</ulink
+></term>
+<listitem
+><para
+>A web interface to the &kde; CVS repository</para
+></listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+><ulink url="http://i18n.kde.org"
+>i18n.kde.org</ulink
+></term>
+<listitem
+><para
+>&kde;'s internationalisation and documentation server</para
+></listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+><ulink url="ftp://ftp.kde.org"
+>ftp.kde.org</ulink
+></term>
+<listitem
+><para
+>The main &kde; &FTP; server. Please have a look at the link below to find a mirror site in your geographic region.</para
+></listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+><ulink
+url="http://www.kde.org/mirrors"
+>www.kde.org/mirrors</ulink
+></term
+> 
+<listitem
+><para
+>&kde; web and &FTP; mirror sites</para
+></listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+><ulink url="http://www.kde-apps.org"
+>www.kde-apps.org</ulink
+></term>
+<listitem
+><para
+>A directory of &kde; applications.</para
+></listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+><ulink url="http://www.kde-look.org"
+>www.kde-look.org</ulink
+></term>
+<listitem
+><para
+>&kde; themes, icons, and other items to change the look of your desktop.</para
+></listitem>
+</varlistentry>
+</variablelist>
+
+</sect1>
+</chapter>
+<!-- Keep this comment at the end of the file
+Local variables:
+mode: sgml
+sgml-omittag:t
+sgml-shorttag:nil
+sgml-namecase-general:t
+sgml-general-insert-case:lower
+sgml-always-quote-attributes:t
+sgml-parent-document:index.docbook
+End:
+-->
+
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/faq/Makefile.am b/tde-i18n-en_GB/docs/tdebase/khelpcenter/faq/Makefile.am
new file mode 100644
index 00000000000..15208dfc8a8
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/faq/Makefile.am
@@ -0,0 +1,4 @@
+KDE_LANG = en_GB
+SUBDIRS = $(AUTODIRS)
+KDE_DOCS = khelpcenter/faq
+KDE_MANS = AUTO
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/faq/Makefile.in b/tde-i18n-en_GB/docs/tdebase/khelpcenter/faq/Makefile.in
new file mode 100644
index 00000000000..4b4129be98a
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/faq/Makefile.in
@@ -0,0 +1,635 @@
+# Makefile.in generated by automake 1.10.1 from Makefile.am.
+# KDE tags expanded automatically by am_edit - $Revision: 483858 $ 
+# @configure_input@
+
+# Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002,
+# 2003, 2004, 2005, 2006, 2007, 2008  Free Software Foundation, Inc.
+# This Makefile.in is free software; the Free Software Foundation
+# gives unlimited permission to copy and/or distribute it,
+# with or without modifications, as long as this notice is preserved.
+
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY, to the extent permitted by law; without
+# even the implied warranty of MERCHANTABILITY or FITNESS FOR A
+# PARTICULAR PURPOSE.
+
+@SET_MAKE@
+VPATH = @srcdir@
+pkgdatadir = $(datadir)/@PACKAGE@
+pkglibdir = $(libdir)/@PACKAGE@
+pkgincludedir = $(includedir)/@PACKAGE@
+am__cd = CDPATH="$${ZSH_VERSION+.}$(PATH_SEPARATOR)" && cd
+install_sh_DATA = $(install_sh) -c -m 644
+install_sh_PROGRAM = $(install_sh) -c
+install_sh_SCRIPT = $(install_sh) -c
+INSTALL_HEADER = $(INSTALL_DATA)
+transform = $(program_transform_name)
+NORMAL_INSTALL = :
+PRE_INSTALL = :
+POST_INSTALL = :
+NORMAL_UNINSTALL = :
+PRE_UNINSTALL = :
+POST_UNINSTALL = :
+subdir = docs/tdebase/khelpcenter/faq
+DIST_COMMON = $(srcdir)/Makefile.am $(srcdir)/Makefile.in
+ACLOCAL_M4 = $(top_srcdir)/aclocal.m4
+am__aclocal_m4_deps = $(top_srcdir)/acinclude.m4 \
+	$(top_srcdir)/configure.in
+am__configure_deps = $(am__aclocal_m4_deps) $(CONFIGURE_DEPENDENCIES) \
+	$(ACLOCAL_M4)
+mkinstalldirs = $(SHELL) $(top_srcdir)/mkinstalldirs
+CONFIG_HEADER = $(top_builddir)/config.h
+CONFIG_CLEAN_FILES =
+SOURCES =
+DIST_SOURCES =
+#>- RECURSIVE_TARGETS = all-recursive check-recursive dvi-recursive \
+#>- 	html-recursive info-recursive install-data-recursive \
+#>- 	install-dvi-recursive install-exec-recursive \
+#>- 	install-html-recursive install-info-recursive \
+#>- 	install-pdf-recursive install-ps-recursive install-recursive \
+#>- 	installcheck-recursive installdirs-recursive pdf-recursive \
+#>- 	ps-recursive uninstall-recursive
+#>+ 7
+RECURSIVE_TARGETS = all-recursive check-recursive dvi-recursive \
+	html-recursive info-recursive install-data-recursive \
+	install-dvi-recursive install-exec-recursive \
+	install-html-recursive install-info-recursive \
+	install-pdf-recursive install-ps-recursive install-recursive \
+	installcheck-recursive installdirs-recursive pdf-recursive \
+	ps-recursive uninstall-recursive nmcheck-recursive bcheck-recursive
+RECURSIVE_CLEAN_TARGETS = mostlyclean-recursive clean-recursive	\
+  distclean-recursive maintainer-clean-recursive
+ETAGS = etags
+CTAGS = ctags
+DIST_SUBDIRS = $(SUBDIRS)
+#>- DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST)
+#>+ 1
+DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST) $(KDE_DIST)
+ACLOCAL = @ACLOCAL@
+AMTAR = @AMTAR@
+ARTSCCONFIG = @ARTSCCONFIG@
+AUTOCONF = @AUTOCONF@
+AUTODIRS = @AUTODIRS@
+AUTOHEADER = @AUTOHEADER@
+AUTOMAKE = @AUTOMAKE@
+AWK = @AWK@
+CONF_FILES = @CONF_FILES@
+CYGPATH_W = @CYGPATH_W@
+DCOPIDL = @DCOPIDL@
+DCOPIDL2CPP = @DCOPIDL2CPP@
+DCOPIDLNG = @DCOPIDLNG@
+DCOP_DEPENDENCIES = @DCOP_DEPENDENCIES@
+DEFS = @DEFS@
+ECHO_C = @ECHO_C@
+ECHO_N = @ECHO_N@
+ECHO_T = @ECHO_T@
+GMSGFMT = @GMSGFMT@
+INSTALL = @INSTALL@
+INSTALL_DATA = @INSTALL_DATA@
+INSTALL_PROGRAM = @INSTALL_PROGRAM@
+INSTALL_SCRIPT = @INSTALL_SCRIPT@
+INSTALL_STRIP_PROGRAM = @INSTALL_STRIP_PROGRAM@
+KCFG_DEPENDENCIES = @KCFG_DEPENDENCIES@
+KCONFIG_COMPILER = @KCONFIG_COMPILER@
+KDECONFIG = @KDECONFIG@
+KDE_EXTRA_RPATH = @KDE_EXTRA_RPATH@
+KDE_RPATH = @KDE_RPATH@
+KDE_XSL_STYLESHEET = @KDE_XSL_STYLESHEET@
+LIBOBJS = @LIBOBJS@
+LIBS = @LIBS@
+LN_S = @LN_S@
+LTLIBOBJS = @LTLIBOBJS@
+MAKEINFO = @MAKEINFO@
+MAKEKDEWIDGETS = @MAKEKDEWIDGETS@
+MCOPIDL = @MCOPIDL@
+MEINPROC = @MEINPROC@
+MKDIR_P = @MKDIR_P@
+MSGFMT = @MSGFMT@
+PACKAGE = @PACKAGE@
+PACKAGE_BUGREPORT = @PACKAGE_BUGREPORT@
+PACKAGE_NAME = @PACKAGE_NAME@
+PACKAGE_STRING = @PACKAGE_STRING@
+PACKAGE_TARNAME = @PACKAGE_TARNAME@
+PACKAGE_VERSION = @PACKAGE_VERSION@
+PATH_SEPARATOR = @PATH_SEPARATOR@
+SET_MAKE = @SET_MAKE@
+SHELL = @SHELL@
+STRIP = @STRIP@
+TOPSUBDIRS = @TOPSUBDIRS@
+VERSION = @VERSION@
+XGETTEXT = @XGETTEXT@
+XMLLINT = @XMLLINT@
+X_RPATH = @X_RPATH@
+abs_builddir = @abs_builddir@
+abs_srcdir = @abs_srcdir@
+abs_top_builddir = @abs_top_builddir@
+abs_top_srcdir = @abs_top_srcdir@
+am__leading_dot = @am__leading_dot@
+am__tar = @am__tar@
+am__untar = @am__untar@
+#>- bindir = @bindir@
+#>+ 2
+DEPDIR = .deps
+bindir = @bindir@
+build_alias = @build_alias@
+builddir = @builddir@
+datadir = @datadir@
+datarootdir = @datarootdir@
+docdir = @docdir@
+dvidir = @dvidir@
+exec_prefix = @exec_prefix@
+host_alias = @host_alias@
+htmldir = @htmldir@
+includedir = @includedir@
+infodir = @infodir@
+install_sh = @install_sh@
+kde_appsdir = @kde_appsdir@
+kde_bindir = @kde_bindir@
+kde_confdir = @kde_confdir@
+kde_datadir = @kde_datadir@
+kde_htmldir = @kde_htmldir@
+kde_icondir = @kde_icondir@
+kde_kcfgdir = @kde_kcfgdir@
+kde_libs_htmldir = @kde_libs_htmldir@
+kde_libs_prefix = @kde_libs_prefix@
+kde_locale = @kde_locale@
+kde_mimedir = @kde_mimedir@
+kde_moduledir = @kde_moduledir@
+kde_servicesdir = @kde_servicesdir@
+kde_servicetypesdir = @kde_servicetypesdir@
+kde_sounddir = @kde_sounddir@
+kde_styledir = @kde_styledir@
+kde_templatesdir = @kde_templatesdir@
+kde_wallpaperdir = @kde_wallpaperdir@
+kde_widgetdir = @kde_widgetdir@
+tdeinitdir = @tdeinitdir@
+libdir = @libdir@
+libexecdir = @libexecdir@
+localedir = @localedir@
+localstatedir = @localstatedir@
+mandir = @mandir@
+mkdir_p = @mkdir_p@
+oldincludedir = @oldincludedir@
+pdfdir = @pdfdir@
+prefix = @prefix@
+program_transform_name = @program_transform_name@
+psdir = @psdir@
+sbindir = @sbindir@
+sharedstatedir = @sharedstatedir@
+srcdir = @srcdir@
+sysconfdir = @sysconfdir@
+target_alias = @target_alias@
+top_builddir = @top_builddir@
+top_srcdir = @top_srcdir@
+xdg_appsdir = @xdg_appsdir@
+xdg_directorydir = @xdg_directorydir@
+xdg_menudir = @xdg_menudir@
+KDE_LANG = en_GB
+#>- SUBDIRS = $(AUTODIRS)
+#>+ 1
+SUBDIRS =.
+KDE_DOCS = khelpcenter/faq
+KDE_MANS = AUTO
+#>- all: all-recursive
+#>+ 1
+all: docs-am  all-recursive
+
+.SUFFIXES:
+$(srcdir)/Makefile.in:  $(srcdir)/Makefile.am  $(am__configure_deps)
+#>- 	@for dep in $?; do \
+#>- 	  case '$(am__configure_deps)' in \
+#>- 	    *$$dep*) \
+#>- 	      cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh \
+#>- 		&& exit 0; \
+#>- 	      exit 1;; \
+#>- 	  esac; \
+#>- 	done; \
+#>- 	echo ' cd $(top_srcdir) && $(AUTOMAKE) --gnu  docs/tdebase/khelpcenter/faq/Makefile'; \
+#>- 	cd $(top_srcdir) && \
+#>- 	  $(AUTOMAKE) --gnu  docs/tdebase/khelpcenter/faq/Makefile
+#>+ 12
+	@for dep in $?; do \
+	  case '$(am__configure_deps)' in \
+	    *$$dep*) \
+	      cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh \
+		&& exit 0; \
+	      exit 1;; \
+	  esac; \
+	done; \
+	echo ' cd $(top_srcdir) && $(AUTOMAKE) --gnu  docs/tdebase/khelpcenter/faq/Makefile'; \
+	cd $(top_srcdir) && \
+	  $(AUTOMAKE) --gnu  docs/tdebase/khelpcenter/faq/Makefile
+	cd $(top_srcdir) && perl ../scripts/admin/am_edit -p../scripts/admin docs/tdebase/khelpcenter/faq/Makefile.in
+.PRECIOUS: Makefile
+Makefile: $(srcdir)/Makefile.in $(top_builddir)/config.status
+	@case '$?' in \
+	  *config.status*) \
+	    cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh;; \
+	  *) \
+	    echo ' cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__depfiles_maybe)'; \
+	    cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__depfiles_maybe);; \
+	esac;
+
+$(top_builddir)/config.status: $(top_srcdir)/configure $(CONFIG_STATUS_DEPENDENCIES)
+	cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
+
+$(top_srcdir)/configure:  $(am__configure_deps)
+	cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
+$(ACLOCAL_M4):  $(am__aclocal_m4_deps)
+	cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
+
+# This directory's subdirectories are mostly independent; you can cd
+# into them and run `make' without going through this Makefile.
+# To change the values of `make' variables: instead of editing Makefiles,
+# (1) if the variable is set in `config.status', edit `config.status'
+#     (which will cause the Makefiles to be regenerated when you run `make');
+# (2) otherwise, pass the desired values on the `make' command line.
+$(RECURSIVE_TARGETS):
+	@failcom='exit 1'; \
+	for f in x $$MAKEFLAGS; do \
+	  case $$f in \
+	    *=* | --[!k]*);; \
+	    *k*) failcom='fail=yes';; \
+	  esac; \
+	done; \
+	dot_seen=no; \
+	target=`echo $@ | sed s/-recursive//`; \
+	list='$(SUBDIRS)'; for subdir in $$list; do \
+	  echo "Making $$target in $$subdir"; \
+	  if test "$$subdir" = "."; then \
+	    dot_seen=yes; \
+	    local_target="$$target-am"; \
+	  else \
+	    local_target="$$target"; \
+	  fi; \
+	  (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS) $$local_target) \
+	  || eval $$failcom; \
+	done; \
+	if test "$$dot_seen" = "no"; then \
+	  $(MAKE) $(AM_MAKEFLAGS) "$$target-am" || exit 1; \
+	fi; test -z "$$fail"
+
+$(RECURSIVE_CLEAN_TARGETS):
+	@failcom='exit 1'; \
+	for f in x $$MAKEFLAGS; do \
+	  case $$f in \
+	    *=* | --[!k]*);; \
+	    *k*) failcom='fail=yes';; \
+	  esac; \
+	done; \
+	dot_seen=no; \
+	case "$@" in \
+	  distclean-* | maintainer-clean-*) list='$(DIST_SUBDIRS)' ;; \
+	  *) list='$(SUBDIRS)' ;; \
+	esac; \
+	rev=''; for subdir in $$list; do \
+	  if test "$$subdir" = "."; then :; else \
+	    rev="$$subdir $$rev"; \
+	  fi; \
+	done; \
+	rev="$$rev ."; \
+	target=`echo $@ | sed s/-recursive//`; \
+	for subdir in $$rev; do \
+	  echo "Making $$target in $$subdir"; \
+	  if test "$$subdir" = "."; then \
+	    local_target="$$target-am"; \
+	  else \
+	    local_target="$$target"; \
+	  fi; \
+	  (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS) $$local_target) \
+	  || eval $$failcom; \
+	done && test -z "$$fail"
+tags-recursive:
+	list='$(SUBDIRS)'; for subdir in $$list; do \
+	  test "$$subdir" = . || (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS) tags); \
+	done
+ctags-recursive:
+	list='$(SUBDIRS)'; for subdir in $$list; do \
+	  test "$$subdir" = . || (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS) ctags); \
+	done
+
+ID: $(HEADERS) $(SOURCES) $(LISP) $(TAGS_FILES)
+	list='$(SOURCES) $(HEADERS) $(LISP) $(TAGS_FILES)'; \
+	unique=`for i in $$list; do \
+	    if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
+	  done | \
+	  $(AWK) '{ files[$$0] = 1; nonemtpy = 1; } \
+	      END { if (nonempty) { for (i in files) print i; }; }'`; \
+	mkid -fID $$unique
+tags: TAGS
+
+TAGS: tags-recursive $(HEADERS) $(SOURCES)  $(TAGS_DEPENDENCIES) \
+		$(TAGS_FILES) $(LISP)
+	tags=; \
+	here=`pwd`; \
+	if ($(ETAGS) --etags-include --version) >/dev/null 2>&1; then \
+	  include_option=--etags-include; \
+	  empty_fix=.; \
+	else \
+	  include_option=--include; \
+	  empty_fix=; \
+	fi; \
+	list='$(SUBDIRS)'; for subdir in $$list; do \
+	  if test "$$subdir" = .; then :; else \
+	    test ! -f $$subdir/TAGS || \
+	      tags="$$tags $$include_option=$$here/$$subdir/TAGS"; \
+	  fi; \
+	done; \
+	list='$(SOURCES) $(HEADERS)  $(LISP) $(TAGS_FILES)'; \
+	unique=`for i in $$list; do \
+	    if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
+	  done | \
+	  $(AWK) '{ files[$$0] = 1; nonempty = 1; } \
+	      END { if (nonempty) { for (i in files) print i; }; }'`; \
+	if test -z "$(ETAGS_ARGS)$$tags$$unique"; then :; else \
+	  test -n "$$unique" || unique=$$empty_fix; \
+	  $(ETAGS) $(ETAGSFLAGS) $(AM_ETAGSFLAGS) $(ETAGS_ARGS) \
+	    $$tags $$unique; \
+	fi
+ctags: CTAGS
+CTAGS: ctags-recursive $(HEADERS) $(SOURCES)  $(TAGS_DEPENDENCIES) \
+		$(TAGS_FILES) $(LISP)
+	tags=; \
+	list='$(SOURCES) $(HEADERS)  $(LISP) $(TAGS_FILES)'; \
+	unique=`for i in $$list; do \
+	    if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
+	  done | \
+	  $(AWK) '{ files[$$0] = 1; nonempty = 1; } \
+	      END { if (nonempty) { for (i in files) print i; }; }'`; \
+	test -z "$(CTAGS_ARGS)$$tags$$unique" \
+	  || $(CTAGS) $(CTAGSFLAGS) $(AM_CTAGSFLAGS) $(CTAGS_ARGS) \
+	     $$tags $$unique
+
+GTAGS:
+	here=`$(am__cd) $(top_builddir) && pwd` \
+	  && cd $(top_srcdir) \
+	  && gtags -i $(GTAGS_ARGS) $$here
+
+distclean-tags:
+	-rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
+
+#>- distdir: $(DISTFILES)
+#>+ 1
+distdir: distdir-nls  $(DISTFILES)
+	@srcdirstrip=`echo "$(srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \
+	topsrcdirstrip=`echo "$(top_srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \
+	list='$(DISTFILES)'; \
+	  dist_files=`for file in $$list; do echo $$file; done | \
+	  sed -e "s|^$$srcdirstrip/||;t" \
+	      -e "s|^$$topsrcdirstrip/|$(top_builddir)/|;t"`; \
+	case $$dist_files in \
+	  */*) $(MKDIR_P) `echo "$$dist_files" | \
+			   sed '/\//!d;s|^|$(distdir)/|;s,/[^/]*$$,,' | \
+			   sort -u` ;; \
+	esac; \
+	for file in $$dist_files; do \
+	  if test -f $$file || test -d $$file; then d=.; else d=$(srcdir); fi; \
+	  if test -d $$d/$$file; then \
+	    dir=`echo "/$$file" | sed -e 's,/[^/]*$$,,'`; \
+	    if test -d $(srcdir)/$$file && test $$d != $(srcdir); then \
+	      cp -pR $(srcdir)/$$file $(distdir)$$dir || exit 1; \
+	    fi; \
+	    cp -pR $$d/$$file $(distdir)$$dir || exit 1; \
+	  else \
+	    test -f $(distdir)/$$file \
+	    || cp -p $$d/$$file $(distdir)/$$file \
+	    || exit 1; \
+	  fi; \
+	done
+	list='$(DIST_SUBDIRS)'; for subdir in $$list; do \
+	  if test "$$subdir" = .; then :; else \
+	    test -d "$(distdir)/$$subdir" \
+	    || $(MKDIR_P) "$(distdir)/$$subdir" \
+	    || exit 1; \
+	    distdir=`$(am__cd) $(distdir) && pwd`; \
+	    top_distdir=`$(am__cd) $(top_distdir) && pwd`; \
+	    (cd $$subdir && \
+	      $(MAKE) $(AM_MAKEFLAGS) \
+	        top_distdir="$$top_distdir" \
+	        distdir="$$distdir/$$subdir" \
+		am__remove_distdir=: \
+		am__skip_length_check=: \
+	        distdir) \
+	      || exit 1; \
+	  fi; \
+	done
+check-am: all-am
+check: check-recursive
+all-am: Makefile
+installdirs: installdirs-recursive
+installdirs-am:
+install: install-recursive
+install-exec: install-exec-recursive
+install-data: install-data-recursive
+#>- uninstall: uninstall-recursive
+#>+ 1
+uninstall: uninstall-docs uninstall-nls  uninstall-recursive
+
+install-am: all-am
+	@$(MAKE) $(AM_MAKEFLAGS) install-exec-am install-data-am
+
+installcheck: installcheck-recursive
+install-strip:
+	$(MAKE) $(AM_MAKEFLAGS) INSTALL_PROGRAM="$(INSTALL_STRIP_PROGRAM)" \
+	  install_sh_PROGRAM="$(INSTALL_STRIP_PROGRAM)" INSTALL_STRIP_FLAG=-s \
+	  `test -z '$(STRIP)' || \
+	    echo "INSTALL_PROGRAM_ENV=STRIPPROG='$(STRIP)'"` install
+mostlyclean-generic:
+
+clean-generic:
+
+distclean-generic:
+	-test -z "$(CONFIG_CLEAN_FILES)" || rm -f $(CONFIG_CLEAN_FILES)
+
+maintainer-clean-generic:
+	@echo "This command is intended for maintainers to use"
+	@echo "it deletes files that may require special tools to rebuild."
+#>- clean: clean-recursive
+#>+ 1
+clean: kde-rpo-clean  clean-recursive
+
+#>- clean-am: clean-generic mostlyclean-am
+#>+ 1
+clean-am: clean-docs clean-bcheck  clean-generic mostlyclean-am
+
+distclean: distclean-recursive
+	-rm -f Makefile
+distclean-am: clean-am distclean-generic distclean-tags
+
+dvi: dvi-recursive
+
+dvi-am:
+
+html: html-recursive
+
+info: info-recursive
+
+info-am:
+
+#>- install-data-am:
+#>+ 1
+install-data-am: install-docs install-nls 
+
+install-dvi: install-dvi-recursive
+
+install-exec-am:
+
+install-html: install-html-recursive
+
+install-info: install-info-recursive
+
+install-man:
+
+install-pdf: install-pdf-recursive
+
+install-ps: install-ps-recursive
+
+installcheck-am:
+
+maintainer-clean: maintainer-clean-recursive
+	-rm -f Makefile
+maintainer-clean-am: distclean-am maintainer-clean-generic
+
+mostlyclean: mostlyclean-recursive
+
+mostlyclean-am: mostlyclean-generic
+
+pdf: pdf-recursive
+
+pdf-am:
+
+ps: ps-recursive
+
+ps-am:
+
+uninstall-am:
+
+.MAKE: $(RECURSIVE_CLEAN_TARGETS) $(RECURSIVE_TARGETS) install-am \
+	install-strip
+
+.PHONY: $(RECURSIVE_CLEAN_TARGETS) $(RECURSIVE_TARGETS) CTAGS GTAGS \
+	all all-am check check-am clean clean-generic ctags \
+	ctags-recursive distclean distclean-generic distclean-tags \
+	distdir dvi dvi-am html html-am info info-am install \
+	install-am install-data install-data-am install-dvi \
+	install-dvi-am install-exec install-exec-am install-html \
+	install-html-am install-info install-info-am install-man \
+	install-pdf install-pdf-am install-ps install-ps-am \
+	install-strip installcheck installcheck-am installdirs \
+	installdirs-am maintainer-clean maintainer-clean-generic \
+	mostlyclean mostlyclean-generic pdf pdf-am ps ps-am tags \
+	tags-recursive uninstall uninstall-am
+
+# Tell versions [3.59,3.63) of GNU make to not export all variables.
+# Otherwise a system limit (for SysV at least) may be exceeded.
+.NOEXPORT:
+
+#>+ 2
+KDE_DIST=desktop.docbook moreinfo.docbook about.docbook configkde.docbook install.docbook winmng.docbook Makefile.in contrib.docbook tips.docbook nonkdeapps.docbook getkde.docbook intro.docbook index.docbook notrelated.docbook panel.docbook filemng.docbook kdeapps.docbook Makefile.am misc.docbook index.cache.bz2 
+
+#>+ 24
+index.cache.bz2: $(srcdir)/index.docbook $(KDE_XSL_STYLESHEET) misc.docbook tips.docbook panel.docbook contrib.docbook intro.docbook kdeapps.docbook nonkdeapps.docbook winmng.docbook notrelated.docbook index.docbook about.docbook desktop.docbook install.docbook configkde.docbook getkde.docbook filemng.docbook moreinfo.docbook 
+	@if test -n "$(MEINPROC)"; then echo $(MEINPROC) --check --cache index.cache.bz2 $(srcdir)/index.docbook; $(MEINPROC) --check --cache index.cache.bz2 $(srcdir)/index.docbook; fi
+
+docs-am: index.cache.bz2
+
+install-docs: docs-am install-nls
+	$(mkinstalldirs) $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/faq
+	@if test -f index.cache.bz2; then \
+	echo $(INSTALL_DATA) index.cache.bz2 $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/faq/; \
+	$(INSTALL_DATA) index.cache.bz2 $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/faq/; \
+	elif test -f  $(srcdir)/index.cache.bz2; then \
+	echo $(INSTALL_DATA) $(srcdir)/index.cache.bz2 $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/faq/; \
+	$(INSTALL_DATA) $(srcdir)/index.cache.bz2 $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/faq/; \
+	fi
+	-rm -f $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/faq/common
+	$(LN_S) $(kde_libs_htmldir)/$(KDE_LANG)/common $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/faq/common
+
+uninstall-docs:
+	-rm -rf $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/faq
+
+clean-docs:
+	-rm -f index.cache.bz2
+
+
+#>+ 13
+install-nls:
+	$(mkinstalldirs) $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/faq
+	@for base in misc.docbook tips.docbook panel.docbook contrib.docbook intro.docbook kdeapps.docbook nonkdeapps.docbook winmng.docbook notrelated.docbook index.docbook about.docbook desktop.docbook install.docbook configkde.docbook getkde.docbook filemng.docbook moreinfo.docbook ; do \
+	  echo $(INSTALL_DATA) $$base $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/faq/$$base ;\
+	  $(INSTALL_DATA) $(srcdir)/$$base $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/faq/$$base ;\
+	done
+
+uninstall-nls:
+	for base in misc.docbook tips.docbook panel.docbook contrib.docbook intro.docbook kdeapps.docbook nonkdeapps.docbook winmng.docbook notrelated.docbook index.docbook about.docbook desktop.docbook install.docbook configkde.docbook getkde.docbook filemng.docbook moreinfo.docbook ; do \
+	  rm -f $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/faq/$$base ;\
+	done
+
+
+#>+ 5
+distdir-nls:
+	for file in misc.docbook tips.docbook panel.docbook contrib.docbook intro.docbook kdeapps.docbook nonkdeapps.docbook winmng.docbook notrelated.docbook index.docbook about.docbook desktop.docbook install.docbook configkde.docbook getkde.docbook filemng.docbook moreinfo.docbook ; do \
+	  cp $(srcdir)/$$file $(distdir); \
+	done
+
+#>+ 15
+force-reedit:
+		@for dep in $?; do \
+	  case '$(am__configure_deps)' in \
+	    *$$dep*) \
+	      cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh \
+		&& exit 0; \
+	      exit 1;; \
+	  esac; \
+	done; \
+	echo ' cd $(top_srcdir) && $(AUTOMAKE) --gnu  docs/tdebase/khelpcenter/faq/Makefile'; \
+	cd $(top_srcdir) && \
+	  $(AUTOMAKE) --gnu  docs/tdebase/khelpcenter/faq/Makefile
+	cd $(top_srcdir) && perl ../scripts/admin/am_edit -p../scripts/admin docs/tdebase/khelpcenter/faq/Makefile.in
+
+
+#>+ 21
+clean-bcheck: 
+	rm -f *.bchecktest.cc *.bchecktest.cc.class a.out
+
+bcheck: bcheck-recursive
+
+bcheck-am:
+	@for i in ; do \
+	    if test $(srcdir)/$$i -nt $$i.bchecktest.cc; then \
+	        echo "int main() {return 0;}" > $$i.bchecktest.cc ; \
+	        echo "#include \"$$i\"" >> $$i.bchecktest.cc ; \
+	        echo "$$i"; \
+	        if ! $(CXX) $(DEFS) -I. -I$(srcdir) -I$(top_builddir) $(INCLUDES) $(AM_CPPFLAGS) $(CPPFLAGS) $(CXXFLAGS) $(KDE_CXXFLAGS)  --dump-class-hierarchy -c $$i.bchecktest.cc; then \
+	            rm -f $$i.bchecktest.cc; exit 1; \
+	        fi ; \
+	        echo "" >> $$i.bchecktest.cc.class; \
+	        perl $(top_srcdir)/admin/bcheck.pl $$i.bchecktest.cc.class || { rm -f $$i.bchecktest.cc; exit 1; }; \
+	        rm -f a.out; \
+	    fi ; \
+	done
+
+
+#>+ 3
+final:
+	$(MAKE) all-am
+
+#>+ 3
+final-install:
+	$(MAKE) install-am
+
+#>+ 3
+no-final:
+	$(MAKE) all-am
+
+#>+ 3
+no-final-install:
+	$(MAKE) install-am
+
+#>+ 3
+kde-rpo-clean:
+	-rm -f *.rpo
+
+#>+ 3
+nmcheck: 
+nmcheck-am: nmcheck
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/faq/about.docbook b/tde-i18n-en_GB/docs/tdebase/khelpcenter/faq/about.docbook
new file mode 100644
index 00000000000..02fc73b3111
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/faq/about.docbook
@@ -0,0 +1,69 @@
+<!--
+<?xml version="1.0" ?>
+<!DOCTYPE chapter PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN"
+ "dtd/kdex.dtd">
+-->
+ 
+<chapter id="about">
+<title
+>About this <acronym
+>FAQ</acronym
+></title>
+
+<qandaset>
+<qandaentry>
+<question>
+<para
+>What can I do to help out with this <acronym
+>FAQ</acronym
+>?</para>
+</question>
+
+<answer>
+
+<para
+>First, send us any errors that you may find. Also, any suggestions that you might have, are appreciated. Better yet, send us everything that you think is unclear, and if possible, send us what you think would be a clearer solution. Our email address is <email
+>kde-doc-english@kde.org</email
+>. </para>
+
+<para
+>Second, send us your solutions of those frequently-asked questions which are still not in this <acronym
+>FAQ</acronym
+>. We will put them in as soon as possible.</para>
+
+<para
+>Last but not least, please make full use of this <acronym
+>FAQ</acronym
+>. Read this <acronym
+>FAQ</acronym
+> (and other relevant documentation) well before asking questions on the various &kde; mailing lists or newsgroups.</para>
+
+<note
+><para
+>You might also want to consider becoming a <acronym
+>FAQ</acronym
+> maintainer. Please refer to <xref linkend="FAQ-maintainer-HOWTO"/> for more details. </para
+></note>
+
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question id="FAQ-maintainer-HOWTO">
+<para
+>How do I become a <acronym
+>FAQ</acronym
+> maintainer?</para>
+</question>
+
+<answer>
+<para
+>Actually, it is very easy to become an <acronym
+>FAQ</acronym
+> maintainer, and we are always in need of fresh blood. :-) Just send us an email at <email
+>kde-doc-english@kde.org</email
+>. </para>
+</answer>
+</qandaentry>
+</qandaset>
+</chapter>
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/faq/configkde.docbook b/tde-i18n-en_GB/docs/tdebase/khelpcenter/faq/configkde.docbook
new file mode 100644
index 00000000000..7402dbde6d5
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/faq/configkde.docbook
@@ -0,0 +1,271 @@
+<!-- 
+<?xml version="1.0" ?>
+<!DOCTYPE chapter PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" "dtd/kdex.dtd">
+	--> 
+<chapter id="configure">
+<title
+>Configuring &kde;</title>
+
+<qandaset>
+<qandaentry>
+<question>
+<para
+>How do I set the language used by &kde;?</para>
+</question>
+
+<answer>
+<para
+>There are two ways to set the language &kde; uses in the messages it will display:</para>
+
+<variablelist>
+<varlistentry
+><term
+>Using the <application
+>&kde; Control Centre</application
+></term>
+<listitem
+><para
+>Fire up the <application
+>&kde; Control Centre</application
+> and select <guimenu
+>Regional &amp; Accessibility</guimenu
+> followed by <guimenuitem
+>Country/Region &amp; Language</guimenuitem
+>. You can select your language and location here. If &kde; cannot find a translation in the first language chosen, it will fall back on the default language. This is usually (American) English by default.</para>
+<note
+><para
+>Using the <application
+>&kde; Control Centre</application
+> is the preferred way of choosing languages in &kde;.</para
+></note
+></listitem>
+</varlistentry>
+<varlistentry
+><term
+>Using the <envar
+>LANG</envar
+> environment variable</term>
+<listitem
+><para
+>The second method uses the standard locale setting on your system. To change the language, simply set the environment variable <envar
+>LANG</envar
+> accordingly. For example, if your shell is <application
+>bash</application
+>, execute <userinput
+><command
+>export</command
+> <envar
+>LANG</envar
+>=de</userinput
+> to set German as the language used.</para
+></listitem>
+</varlistentry>
+</variablelist>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>Is there any keyboard switcher for international keyboards for &kde;?</para>
+</question>
+<answer>
+<para
+>Yes, you can configure it using the <application
+>&kde; Control Centre</application
+> <guimenu
+>Regional &amp; Accessibility</guimenu
+> <guimenuitem
+>Keyboard Layout</guimenuitem
+> configuration page. </para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>How do I replace the standard text login screen with the &kde; login screen?</para>
+</question>
+<answer>
+<note
+><para
+>Your distribution/&UNIX; flavour may have its own setup tools to change this (&eg; <application
+>YaST</application
+> on &SuSE; &Linux;). This will be the safest way to enable the &kde; login screen. However, if for some reason you do not wish to use these tools, the following instructions may be useful.</para
+></note>
+<para
+>First, you need to change to the <quote
+>xdm runlevel</quote
+> (runlevel 5 on &RedHat; and &SuSE; systems) by editing your <filename
+>/etc/inittab</filename
+> file. In the file, you should have a line saying <userinput
+>id:3:initdefault:</userinput
+>. Change it to <userinput
+>id:5:initdefault:</userinput
+>. Now, at the end of the file, comment out the following line: <literal
+>x:5:respawn:/usr/bin/X11/xdm -nodaemon</literal
+> and replace it with <userinput
+>x:5:respawn:<replaceable
+>/opt/kde/</replaceable
+>bin/kdm -nodaemon</userinput
+>. <note
+><para
+>The location of &kdm; may differ on your system.</para
+></note
+></para>
+<para
+>For changes to take effect immediately, type <command
+>init 5</command
+> (for &RedHat; systems) at the shell prompt. <caution
+><para
+>It is risky to initiate a graphical login without checking beforehand whether it works. If it fails to work, you would be in for a hard time getting back....</para
+></caution
+></para>
+</answer>
+<answer>
+<para
+>For FreeBSD, you should edit the file <filename
+>/etc/ttys</filename
+> and change one of the lines that look like <programlisting
+>ttyv8   "/usr/X11R6/bin/xdm -nodaemon"  xterm   off secure</programlisting
+> to instead say <userinput
+>ttyv8 "/usr/local/bin/kdm -nodaemon" xterm off secure</userinput
+>.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+
+<para
+>I would like to click the &LMB; anywhere on the desktop and have the <guimenu
+>K</guimenu
+> menu displayed.</para>
+</question>
+<answer>
+<para
+>Open the <application
+>&kde; Control Centre</application
+> and choose <menuchoice
+><guisubmenu
+>Desktop</guisubmenu
+> <guisubmenu
+>Behaviour</guisubmenu
+></menuchoice
+>. You can now choose the behaviour of mouse clicks on the desktop. To have the <guimenu
+>K</guimenu
+> menu open from a single &LMB; click, change the entry labelled <guilabel
+>Left button</guilabel
+> to say <guilabel
+>Application Menu</guilabel
+>.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>Where do I find information regarding &kde; themes?</para>
+</question>
+<answer>
+<para
+>Go to <ulink url="http://kde.themes.org/"
+>http://kde.themes.org/</ulink
+> or <ulink url="http://www.kde-look.org"
+>http://www.kde-look.org</ulink
+>.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>How do I change &MIME; Types?</para>
+</question>
+<answer>
+<para
+>If you are using &konqueror;, do this instead: first, open a &konqueror; window and choose <menuchoice
+><guimenu
+>Settings</guimenu
+><guimenuitem
+>Configure Konqueror</guimenuitem
+></menuchoice
+>, then <guilabel
+>File Associations</guilabel
+>. Find the type you want to change (&eg; <literal
+>text/english</literal
+> or <literal
+>image/gif</literal
+>), and set the application preference order to whatever you want.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>&kde; (&kdm;) does not read my <filename
+>.bash_profile</filename
+>!</para>
+</question>
+<answer>
+<para
+>The login managers<application
+>xdm</application
+> and &kdm; do not run a login shell, so <filename
+>.profile</filename
+>, <filename
+>.bash_profile</filename
+>, &etc; are not sourced. When the user logs in, <application
+>xdm</application
+> runs <command
+>Xstartup</command
+> as root and then <command
+>Xsession</command
+> as user. So the normal practice is to add statements in <filename
+>Xsession</filename
+> to source the user profile. Please edit your <filename
+>Xsession</filename
+> and <filename
+>.xsession</filename
+> files.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>How do I use &TrueType; fonts in &kde;?</para>
+</question>
+<answer>
+
+<para
+>You need to install &TrueType; font support into your &X-Window; configuration. Please take a look at <ulink url="http://x.themes.org/"
+>x.themes.org</ulink
+> for the fonts, and <ulink url="http://www.dcs.ed.ac.uk/home/jec/programs/xfsft/"
+>xfsft: &TrueType; Font Support For X11</ulink
+> or <ulink url="http://X-TT.dsl.gr.jp/"
+>X-&TrueType; Server Project Home Page</ulink
+> for the font servers.</para>
+
+<para
+>If you have a bunch of &TrueType; fonts from &Microsoft; &Windows;, edit the <filename
+>XF86Config</filename
+> file to get the fonts from the font folder. Then just tell &kde; to use these new fonts with the font administrator utility.</para>
+
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>Is it possible to enter, show and work with the Euro Symbol in &kde;?</para>
+</question>
+<answer>
+<para
+>Yes and no. For details, look here: <ulink url="http://www.koffice.org/kword/euro.php"
+>http://www.koffice.org/kword/euro.php</ulink
+>.</para>
+</answer>
+</qandaentry>
+</qandaset>
+</chapter>
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/faq/contrib.docbook b/tde-i18n-en_GB/docs/tdebase/khelpcenter/faq/contrib.docbook
new file mode 100644
index 00000000000..8bff6911cd5
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/faq/contrib.docbook
@@ -0,0 +1,249 @@
+<!--
+<?xml version="1.0" ?>
+<!DOCTYPE chapter PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN"
+ "dtd/kdex.dtd">
+-->
+
+
+<chapter id="contribute">
+<title
+>Contributing</title>
+
+<qandaset>
+<qandaentry>
+<question>
+<para
+>How can I contribute to &kde;?</para>
+</question>
+<answer>
+<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 many ways in which you can help to improve &kde;:</para>
+<itemizedlist>
+<listitem
+><para
+>Test the software.</para
+></listitem>
+<listitem
+><para
+>Send in bug reports. For more information on this, see <link linkend="bug-report"
+>How do I submit a bug report?</link
+>.</para
+></listitem>
+<listitem
+><para
+>Write documentation or help files. You can get some information by visiting the <ulink url="http://i18n.kde.org/doc/"
+>&kde; Editorial Team Home Page</ulink
+>.</para
+></listitem>
+<listitem
+><para
+>Translate programs, documentation, and help files. For more information on this, you should visit <ulink url="http://i18n.kde.org"
+>The &kde; Translators' and Documenters' Web Site</ulink
+>.</para
+></listitem>
+<listitem
+><para
+>Draw nice icons or compose sound effects. You can visit the <ulink url="http://artist.kde.org/"
+>&kde; artists page</ulink
+> to find out more.</para
+></listitem>
+<listitem
+><para
+>Write articles and books about &kde;. If you want to help spread the word about &kde;, simply send an email to <email
+>kde-pr@kde.org</email
+>. This will get you in touch with the &kde; public relations volunteers.</para
+></listitem>
+<listitem
+><para
+>Program new &kde; applications. Please refer to <xref linkend="programming"/> for more information.</para
+></listitem>
+<listitem
+><para
+>Of course, sponsors are also welcome. :-)</para
+></listitem>
+</itemizedlist>
+<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 <ulink url="http://www.kde.org/mailinglists/"
+>mailing lists</ulink
+>. You will soon see something that can be improved or added.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question id="bug-report">
+<para
+>How do I submit a bug report?</para>
+</question>
+<answer>
+<para
+>There is a bug tracking system available at <ulink url="http://bugs.kde.org"
+>http://bugs.kde.org</ulink
+>. The system features a wizard to submit new bug reports and a list of all known bugs.</para>
+<para
+>The easiest way to submit a bug is to select <menuchoice
+><guimenu
+>Help</guimenu
+><guimenuitem
+>Report Bug...</guimenuitem
+></menuchoice
+> from the menu bar of the application with the bug. This will open a small dialogue box with a link to the bug tracking system. Please make sure to follow the instructions of the bug reporting wizard.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question id="programming">
+<para
+>I want to program for &kde;. What should I do first?</para>
+</question>
+<answer>
+<para
+>Everybody is encouraged to develop software for &kde;. What you should do first depends strongly on your experience, &eg; 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: <application
+>automake</application
+>, <application
+>autoconf</application
+>, and <application
+>egcs</application
+>. You should look to <ulink url="http://developer.kde.org/"
+>http://developer.kde.org/</ulink
+> for more tips.</para>
+<para
+>Another excellent resource for learning &kde; programming is the &Qt; online tutorials. These are installed along with &Qt;. To view them, open <filename
+>$<envar
+>QTDIR</envar
+>/doc/html/index.html</filename
+> in &konqueror; and bookmark it. The tutorials can be found under "Using Qt". The source code for each lesson can be found in the <filename class="directory"
+>$<envar
+>QTDIR</envar
+>/tutorial</filename
+> directory.</para>
+<para
+>There is, however, one thing that everybody interested in programming for &kde; should do: <emphasis
+>subscribe to the developers mailing list</emphasis
+>. To subscribe, you have to send an email to <ulink url="mailto:kde-devel-request@kde.org"
+>kde-devel-request@kde.org</ulink
+> with the subject <userinput
+>subscribe <replaceable
+>your_email_address</replaceable
+></userinput
+>. <important
+><para
+>Please read <link linkend="subscribe"
+>How to subscribe/unsubscribe to these lists</link
+> carefully. Everything said there applies to the development list as well.</para
+></important
+></para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>How do I get access to the <acronym
+>CVS</acronym
+>?</para>
+</question>
+<answer>
+<para
+>The &kde; project uses <acronym
+>CVS</acronym
+> to develop the core parts of the software. Usually, when you have changed one of the parts (&eg; 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 Stephan Kulow, <email
+>coolo@kde.org</email
+> for direct access to the <acronym
+>CVS</acronym
+> server. But be aware that more users will slow down <acronym
+>CVS</acronym
+> access for all developers, so we want to keep the number of people with direct <acronym
+>CVS</acronym
+> access reasonably small. But feel free to ask!</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>I am just curious. Can I have read-only access to the <acronym
+>CVS</acronym
+>?</para>
+</question>
+<answer>
+<para
+>Yes. It is possible to get read-only access to the <acronym
+>CVS</acronym
+> repository with <application
+>cvsup</application
+> or <application
+>cvs</application
+> utility. You can find more information about how to set up <application
+>cvsup</application
+> for the &kde; repository from <ulink url="http://developer.kde.org/source/cvsup.html"
+>How to use <application
+>cvsup</application
+> to get &kde;</ulink
+>.</para>
+<para
+>In addition, anonymous <acronym
+>CVS</acronym
+> service is also available. To find out more about how to set up and use anonymous <acronym
+>CVS</acronym
+>, please see <ulink url="http://developer.kde.org/source/anoncvs.html"
+>here</ulink
+>.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>Are there any <application
+>cvs</application
+> mirror sites for &kde;?</para>
+</question>
+<answer>
+<para
+>Yes. The main &kde; server is normally very busy. Please take a look at <ulink url="http://developer.kde.org/source/cvsupmirrors.html"
+>http://developer.kde.org/source/cvsupmirrors.html</ulink
+> and <ulink url="http://developer.kde.org/source/anoncvs.html"
+>http://developer.kde.org/source/anoncvs.html</ulink
+> for the list of available mirrors.</para
+>  
+<para
+>Once you have selected a new <application
+>cvsup</application
+> server, simply replace <screen
+> 
+*default host=cvs.kde.org
+</screen
+> with <screen
+> 
+*default host=cvsup.your.new.host
+</screen
+> in your <application
+>cvsup</application
+> script.</para>
+<para
+>The instructions to change the anoncvs server can be found on <ulink url="http://developer.kde.org/source/anoncvs.html"
+>http://developer.kde.org/source/anoncvs.html</ulink
+>, too. </para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>How do I go about translating &kde; programs into my native language?</para>
+</question>
+<answer>
+<para
+>Look at the <ulink url="http://i18n.kde.org"
+>The &kde; Translators' and Documenters' Web Site</ulink
+> to see whether your program is already translated (most are). Otherwise you will find information there on how to do it yourself.</para>
+</answer>
+</qandaentry>
+</qandaset>
+</chapter>
+
+
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/faq/desktop.docbook b/tde-i18n-en_GB/docs/tdebase/khelpcenter/faq/desktop.docbook
new file mode 100644
index 00000000000..b95a8a96dbc
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/faq/desktop.docbook
@@ -0,0 +1,151 @@
+<!--
+<?xml version="1.0" ?>
+<!DOCTYPE chapter PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN"
+ "dtd/kdex.dtd">
+-->
+
+<chapter id="desktop">
+<title
+>The desktop</title>
+
+<qandaset>
+<qandaentry>
+<question>
+<para
+>How do I add an application to the desktop?</para>
+</question>
+<answer>
+
+<para
+>Just choose the desired application from the <guimenu
+>K</guimenu
+> menu and drag and drop it to the Desktop. </para
+> 
+<para
+>For applications not listed in the <guimenu
+>K</guimenu
+> menu, use the &RMB; on the desktop and choose <menuchoice
+><guimenuitem
+>Create New</guimenuitem
+><guisubmenu
+>File</guisubmenu
+> <guimenuitem
+>Link to Application...</guimenuitem
+></menuchoice
+> and fill in the configuration for the application you want to link to. </para>
+
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>How do I mount/unmount a device from the desktop?</para>
+</question>
+<answer>
+
+<para
+>First, make sure you are allowed to <command
+>mount</command
+>/<command
+>umount</command
+> the relevant device as a user. </para>
+<para
+>Then you can add any device via &RMB; on the desktop and then choosing <guimenuitem
+>Create New</guimenuitem
+>. </para>
+
+</answer>
+</qandaentry>
+
+
+<qandaentry>
+<question>
+<para
+>Where are the icons kept?</para>
+</question>
+<answer>
+<para
+>The icons can be found only in <filename class="directory"
+>$<envar
+>KDEDIRS</envar
+>/share/icons</filename
+> or <filename class="directory"
+>$<envar
+>HOME</envar
+>/.kde/share/icons</filename
+> or <filename class="directory"
+>$<envar
+>HOME</envar
+>/.kde2/share/icons</filename
+>. 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>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>How do I use the mouse scroll wheel in &kde;?</para>
+</question>
+<answer>
+<para
+>Mouse wheel support comes with &Qt; 2.0 and above, so &kde; based on that will automatically support the use of the mouse scroll wheel.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>Why can't I get system sound to work, like for opening windows?</para>
+</question>
+<answer>
+<para
+>System sound currently does not work on non-FreeBSD and non-&Linux; systems. This is being worked on. If you use FreeBSD or &Linux;, you have found a bug, so please report it.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>How do I launch applications in a particular desktop?</para>
+</question>
+<answer>
+<para
+>&kde; comes with a program called &kstart;. To start an <application
+>xterm</application
+> on the second desktop and then activate it use: <userinput
+><command
+>kstart</command
+> <option
+>--desktop 2 --activate --window "xterm" </option
+>xterm</userinput
+>.</para>
+<para
+>Note that the <option
+>--window</option
+> option is important. It takes an argument which is a regular expression matching the title of the window to apply the settings to.</para>
+<para
+>Please read <command
+>kstart</command
+> <option
+>--help-all</option
+> for more magic available with &kstart; (and there is an abundance). </para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>Where do I save my files if I want them to appear directly on the desktop?</para>
+</question>
+<answer>
+<para
+><filename class="directory"
+>$<envar
+>HOME</envar
+>/Desktop</filename
+>. You might need to refresh your desktop after you have saved your files.</para>
+</answer>
+</qandaentry>
+</qandaset>
+</chapter>
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/faq/filemng.docbook b/tde-i18n-en_GB/docs/tdebase/khelpcenter/faq/filemng.docbook
new file mode 100644
index 00000000000..3a8af4c727b
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/faq/filemng.docbook
@@ -0,0 +1,280 @@
+<!-- <?xml version="1.0" ?>
+<!DOCTYPE chapter PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN"
+ "dtd/kdex.dtd"
+> -->
+	
+<chapter id="filemanager">
+<title
+>The File Manager and Web Browser</title>
+
+<para
+>The file manager and web browser of &kde; is &konqueror;. The &konqueror; home page is located at <ulink url="http://www.konqueror.org"
+>http://www.konqueror.org</ulink
+> where a &konqueror; specific <acronym
+>FAQ</acronym
+> can be found.</para>
+
+<qandaset>
+<qandaentry>
+<question>
+<para
+>How do I use &konqueror; as a web browser with a proxy?</para>
+</question>
+<answer>
+<para
+>&konqueror; can be used with &HTTP; and &FTP; proxies. To set up the proxy server in &konqueror;, just select <menuchoice
+><guimenu
+>Settings</guimenu
+><guisubmenu
+>Configure &konqueror;...</guisubmenu
+></menuchoice
+> from the &konqueror; menu and go to the <guilabel
+>Proxy</guilabel
+> tab.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>How can I change the appearance of a folder in &konqueror;?</para>
+</question>
+<answer>
+<para
+>Right-click the folder, select <guimenuitem
+>Properties</guimenuitem
+>, click on the large icon in the dialogue which appears and choose another icon.</para>
+<para
+>To change the icon displayed for entries in the <guimenu
+>K Menu</guimenu
+>, use the <application
+>Menu Editor</application
+>, located at <menuchoice
+><guisubmenu
+>Settings</guisubmenu
+><guimenuitem
+>Menu Editor</guimenuitem
+></menuchoice
+>. </para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>How can I do non-anonymous &FTP; transfers with &konqueror;?</para>
+</question>
+<answer>
+<para
+>Normally, if you enter a &URL; like <userinput
+>ftp://<replaceable
+>ftp.somehost.com</replaceable
+></userinput
+>, &konqueror; will attempt an anonymous login to the &FTP; server. If you want to login as a particular user, enter a &URL; like <userinput
+>ftp://<replaceable
+>username@ftp.somehost.com</replaceable
+></userinput
+> instead. &konqueror; will ask for your password and connect to the server.</para>
+</answer>
+</qandaentry>
+
+<qandaentry
+> <question
+> <para
+>What are <option
+>%i</option
+> and <option
+>%m</option
+> in the Execute line?</para
+> </question
+> <answer>
+<para
+>They are used by all &kde; applications (since they are implemented in <classname
+>KApplication</classname
+> and all good &kde; programs create a <classname
+>KApplication</classname
+> object before they even look at the command line arguments).</para
+> <para
+>A standard line for a &kde; application looks like this: <userinput
+><command
+>foo</command
+> <option
+>... %i %m -caption \"%c\"</option
+></userinput
+>. Pretty confusing, but it has been designed in that way so that it can integrate legacy, non-&kde; applications as smoothly as possible. &konqueror;, when executing the line above, will extend the command to <userinput
+><command
+><replaceable
+>foo</replaceable
+></command
+> <option
+>-icon something.png -miniicon something_mini.png -caption \"The Foo\"</option
+></userinput
+>. Both the icon and the mini-icon as well as "The Foo" are properties defined in the <filename
+>.desktop</filename
+> file. If the icons are not defined, they simply default to the executable name <replaceable
+>foo</replaceable
+>.</para>
+
+<para
+>This way a user can change these things in &kmenuedit; for his or her applications. The <option
+>-caption</option
+> option is important, because no user will accept that the menu item <guimenuitem
+>Editor</guimenuitem
+> starts something called <guilabel
+>kedit-0.9pl4-build47</guilabel
+>. Instead, he expects a window called <guilabel
+>Editor</guilabel
+>. Furthermore these names are localised, <abbrev
+>i.e.</abbrev
+> an American user launches <guimenuitem
+>CD-Player</guimenuitem
+> and gets a window called <guilabel
+>CD-Player</guilabel
+> while a German user launches <guimenuitem
+>CD-Spieler</guimenuitem
+> and gets a window called <guilabel
+>CD-Spieler</guilabel
+>.</para>
+
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>How do I specify the startup folder for &konqueror;?</para>
+</question>
+<answer>
+
+<para
+>Using the &RMB;, click on the Home icon and choose <guimenuitem
+>Properties</guimenuitem
+>. Under the <guilabel
+>Application</guilabel
+> tab you will probably find something like <command
+>kfmclient openProfile filemanagement</command
+>; just append <filename class="directory"
+>file:/whereever/you/want</filename
+> with the folder you would like &konqueror; to start in.</para>
+
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question id="nsbookmark">
+<para
+>How do I import &Netscape; bookmarks?</para>
+</question>
+<answer>
+<para
+>There is no need to import anything at all. &Netscape; bookmarks are automatically available under the <guimenu
+>Bookmarks</guimenu
+> menu in &konqueror; with no configuration on your part necessary. The <application
+>Bookmark Editor</application
+> is able to convert &Netscape; bookmarks to the format used by &konqueror;, if you want this.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>How do I fool a site into believing &konqueror; is &Netscape; or some other browser?</para>
+</question>
+<answer>
+<para
+>In &konqueror;, select <menuchoice
+><guimenu
+>Settings</guimenu
+><guimenuitem
+>Configure Konqueror...</guimenuitem
+></menuchoice
+> and in the configuration dialogue, select <guilabel
+>Browser Identification</guilabel
+>. Default and site-specific browser identifications can be set from here.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>How do I configure &konqueror; to run &Java; applets?</para>
+</question>
+<answer>
+<para
+>Choose <menuchoice
+><guimenu
+>Settings</guimenu
+><guimenuitem
+>Configure &konqueror;...</guimenuitem
+></menuchoice
+> from &konqueror;'s menubar and then select <guilabel
+>Java &amp; Javascript</guilabel
+>. Set the <guilabel
+>Path to Java executable</guilabel
+> correctly. If it doesn't work, please check the <ulink url="http://www.konqueror.org/javahowto/"
+>Konqueror + Java HOWTO</ulink
+>.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>What is this new <guilabel
+>Smart</guilabel
+> policy for JavaScript web popups?</para>
+</question>
+<answer>
+<para
+>This new policy attempts to block intrusive JavaScript popup windows. If the user does not click on a button or submit a form to trigger the popup, then the popup is not permitted. Some sites will open a second new window from within the first and in that case, the second window will not show. </para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>Why doesn't my banking site work with &konqueror;? It pops up a new window with the login screen in other browsers, but not in &konqueror;.</para>
+</question>
+<answer>
+<para
+>Make sure you have Javascript enabled, and the default JavaScript web popups policy set to <guilabel
+>Ask</guilabel
+> or <guilabel
+>Allow</guilabel
+>. The <guilabel
+>Smart</guilabel
+> policy is not always sufficient for some banks. Many banks also require &Java; support. You can find more help on enabling this at <ulink url="http://www.konqueror.org/"
+>http://www.konqueror.org/</ulink
+>. </para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>Why can't &konqueror; render &GIF; images?</para>
+</question>
+<answer>
+<para
+>It is because you did not enable &GIF; support in &Qt;. Please see <xref linkend="gif"/> for more details.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>How do I rename files?</para>
+</question>
+<answer>
+<para
+>Simply <mousebutton
+>right</mousebutton
+> click on the file and select <guimenuitem
+>Rename</guimenuitem
+> or click once on an already selected file. The default keyboard shortcut to rename a file is <keycap
+>F2</keycap
+>.</para>
+</answer>
+</qandaentry>
+</qandaset>
+</chapter>
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/faq/getkde.docbook b/tde-i18n-en_GB/docs/tdebase/khelpcenter/faq/getkde.docbook
new file mode 100644
index 00000000000..a059b9b7204
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/faq/getkde.docbook
@@ -0,0 +1,111 @@
+<!--
+<?xml version="1.0" ?>
+<!DOCTYPE chapter PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN"
+ "dtd/kdex.dtd">
+-->
+
+<chapter id="getting-kde">
+<title
+>Getting &kde;</title>
+
+<qandaset>
+<qandaentry>
+<question id="where-to-get-kde">
+<para
+>Where do I get &kde;?</para>
+</question>
+<answer>
+<!-- This needs a rewrite including informations about the latest version (link to the info page?)-->
+<para
+>The main distribution site for &kde; is <ulink url="ftp://ftp.kde.org/"
+>ftp.kde.org</ulink
+>. However, this site is often under heavy load, so you might prefer to use <ulink url="http://download.kde.org/"
+>download.kde.org</ulink
+> which automatically redirects you to the mirror nearest to you. You can also have a look at the list of <ulink url="http://www.kde.org/ftpmirrors.html"
+> &kde; mirror sites</ulink
+>.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>Are there &Linux; distributions that include &kde;?</para>
+</question>
+<answer>
+<para
+>Yes, major &Linux; distributions already ship &kde;. As building a distribution takes some time, they might not always contain the latest version, but for a start or to avoid downloading from the Internet, they do provide a good starting point. </para>
+<para
+>You can find an up-to-date list of distributions that ship with &kde; <ulink url="http://www.kde.org/download/distributions.php"
+>here</ulink
+>. </para>
+
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>What is the current version?</para>
+</question>
+<answer>
+
+<para
+>Currently, the latest stable version is 3.2</para>
+
+<para
+>The <ulink url="http://www.kde.org/info/3.2.php"
+>&kde; 3.2 Info Page</ulink
+> contains a lot of information specific to this release.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>Where do I find &kde; snapshots?</para>
+</question>
+<answer>
+<para
+>You can get the latest snapshots from <ulink url="ftp://ftp.kde.org/pub/kde/unstable/snapshots"
+>ftp://ftp.kde.org/pub/kde/unstable/snapshots</ulink
+>. You might also want to consider setting up your own <acronym
+>CVS</acronym
+> client in order to maintain the latest snapshot at all times. Please refer to <ulink url="http://developer.kde.org/source/anoncvs.html"
+>Anonymous <acronym
+>CVS</acronym
+> and &kde;</ulink
+> for further information. </para>
+
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question id="where-to-get-qt">
+<para
+>Where do I get &Qt;?</para>
+</question>
+<answer>
+<para
+>&Qt; is a product of the Norwegian company Trolltech. You can always get the latest &Qt; version from their <ulink url="ftp://ftp.trolltech.com"
+>&FTP; server</ulink
+>.</para>
+<para
+>And with most up-to-date &Linux; distributions, &Qt; is already included. Please see <xref linkend="prerequisites"/> for the version of &Qt; you need.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question id="qt">
+<para
+>What is &Qt;, by the way?</para>
+</question>
+<answer>
+<para
+>&Qt; is a C++-based class library to build user interfaces. It also includes many utility classes like string classes and classes to handle input and output. It provides most of the widgets you will see in a &kde; application: menus, buttons, sliders, &etc;. &Qt; is a cross-platform library that allows you to write code that will compile on &UNIX; systems as well as &Windows; and embedded devices. You can learn more about &Qt; at <ulink url="http://www.trolltech.com"
+>http://www.trolltech.com</ulink
+>.</para>
+</answer>
+</qandaentry>
+</qandaset>
+</chapter>
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/faq/index.cache.bz2 b/tde-i18n-en_GB/docs/tdebase/khelpcenter/faq/index.cache.bz2
new file mode 100644
index 00000000000..f47541c06de
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/faq/index.cache.bz2
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/faq/index.docbook b/tde-i18n-en_GB/docs/tdebase/khelpcenter/faq/index.docbook
new file mode 100644
index 00000000000..e833f6b663c
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/faq/index.docbook
@@ -0,0 +1,165 @@
+<?xml version="1.0" ?>
+<!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN"
+ "dtd/kdex.dtd" [
+  <!ENTITY kappname "&kde; Frequently Asked Questions">
+  <!ENTITY % addindex "IGNORE">
+  <!ENTITY % British-English "INCLUDE"
+> <!-- change language only here -->
+  <!ENTITY faq-about SYSTEM "about.docbook">
+  <!ENTITY faq-intro SYSTEM "intro.docbook">
+  <!ENTITY faq-getkde SYSTEM "getkde.docbook">
+  <!ENTITY faq-install SYSTEM "install.docbook">
+  <!ENTITY faq-panel SYSTEM "panel.docbook">
+  <!ENTITY faq-desktop SYSTEM "desktop.docbook">
+  <!ENTITY faq-winmng SYSTEM "winmng.docbook">
+  <!ENTITY faq-filemng SYSTEM "filemng.docbook">
+  <!ENTITY faq-configkde SYSTEM "configkde.docbook">
+  <!ENTITY faq-kdeapps SYSTEM "kdeapps.docbook">
+  <!ENTITY faq-nonkdeapps SYSTEM "nonkdeapps.docbook">
+  <!ENTITY faq-tips SYSTEM "tips.docbook">
+  <!ENTITY faq-misc SYSTEM "misc.docbook">
+  <!ENTITY faq-notrelated SYSTEM "notrelated.docbook">
+  <!ENTITY faq-moreinfo SYSTEM "moreinfo.docbook">
+  <!ENTITY faq-contrib SYSTEM "contrib.docbook">
+  <!ENTITY faq-credits SYSTEM "credits.docbook">
+
+
+]>
+<!--Time-stamp: "2001-09-03 00:10:00 endres"-->
+<book lang="&language;">
+
+<bookinfo>
+<title
+>&kde; Frequently Asked Questions</title>
+
+<authorgroup>
+<author>
+<surname
+>The &kde; Team</surname>
+</author>
+<othercredit role="translator"
+><firstname
+>Malcolm</firstname
+><surname
+>Hunter</surname
+><affiliation
+><address
+><email
+>malcolm.hunter@gmx.co.uk</email
+></address
+></affiliation
+><contrib
+>Conversion to British English</contrib
+></othercredit
+> 
+
+</authorgroup>
+
+<copyright>
+<year
+>1997</year>
+<year
+>1998</year>
+<year
+>1999</year>
+<year
+>2000</year>
+<year
+>2001</year>
+<year
+>2003</year>
+<holder
+>The &kde; Team</holder>
+</copyright>
+
+<legalnotice
+>&FDLNotice;</legalnotice>
+
+<date
+>2003-09-16</date>
+<releaseinfo
+>3.2</releaseinfo>
+
+<abstract>
+<para
+>This is a compilation of the most frequently asked questions about the K Desktop Environment. Please report any bugs, inconsistencies or omissions you find in this &FAQ; to <email
+>kde-doc-english@kde.org</email
+>. Please do not mail your questions to this list. Post them to the &kde; mailing lists and newsgroups instead. They are monitored for this FAQ.</para
+> </abstract>
+
+<keywordset>
+<keyword
+>KDE</keyword>
+<keyword
+>FAQ</keyword>
+<keyword
+>question</keyword>
+<keyword
+>answer</keyword>
+</keywordset>
+</bookinfo>
+
+&faq-about;
+&faq-intro;
+&faq-getkde;
+&faq-install;
+&faq-panel;
+&faq-desktop;
+&faq-winmng;
+&faq-filemng;
+&faq-configkde;
+&faq-kdeapps;
+&faq-nonkdeapps;
+&faq-tips;
+&faq-misc;
+&faq-moreinfo;
+&faq-contrib;
+
+<chapter id="credits">
+<title
+>Credits and Licence</title>
+
+<para
+>The current &FAQ; maintainers are:</para>
+
+<itemizedlist>
+<listitem
+><para
+>Rainer Endres <email
+>endres@kde.org</email
+></para
+></listitem>
+</itemizedlist>
+
+<para
+>Many of the answers in this &FAQ; are taken from the various &kde; mailing lists and newsgroups. Here is a <emphasis
+>big</emphasis
+> thank you to all of you who have contributed answers that eventually appear in this &FAQ;.</para>
+
+<para
+>Special thanks go to the former &FAQ; maintainer, who has written most of the stuff in here, and did a tremendous job: Mr. Lee Wee Tiong </para>
+
+
+<para
+>Conversion to British English: Malcolm Hunter <email
+>malcolm.hunter@gmx.co.uk</email
+></para
+> 
+&underFDL; </chapter>
+
+&documentation.index;
+</book>
+<!--
+Local Variables:
+sgml-minimize-attributes:nil
+sgml-general-insert-case:lower
+sgml-omittag:t
+sgml-shorttag:t
+sgml-namecase-general:t
+sgml-always-quote-attributes:t
+sgml-indent-step:2
+sgml-indent-data:nil
+sgml-parent-document:nil
+sgml-exposed-tags:nil
+End:
+-->
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/faq/install.docbook b/tde-i18n-en_GB/docs/tdebase/khelpcenter/faq/install.docbook
new file mode 100644
index 00000000000..7b184f261b1
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/faq/install.docbook
@@ -0,0 +1,1035 @@
+<!-- <?xml version="1.0" ?>
+<!DOCTYPE chapter PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN"
+ "dtd/kdex.dtd"
+> -->
+
+
+<chapter id="install">
+<title
+>Installation instructions</title>
+
+<para
+>These are the generic installation instructions for the K Desktop Environment. Please complement your reading with the <filename
+>README</filename
+>s and <filename
+>INSTALL</filename
+>s that come along with the package. Please read them carefully and try to help yourself out if anything goes wrong. If you need further assistance, consider joining the &kde; mailing lists (see our web site instructions for joining the &kde; <ulink url="http://www.kde.org/mailinglists/"
+>mailing lists</ulink
+>) or newsgroups.</para>
+
+
+<qandaset>
+
+
+<qandaentry>
+<question>
+<para
+>To the would-be converts</para>
+</question>
+<answer>
+
+<para
+>So you have heard the rumours. Or you have seen the screenshots. And you are dying to get hold of &kde;. But you know next to nothing about this whole <quote
+>alternative OS</quote
+> business. Don't worry! You only need to do some (well, maybe not some) reading, that's all!</para>
+
+<para
+>&kde; does not run on any version of &Microsoft; &Windows; or OS/2 (yet). To run &kde;, you need to have a &UNIX; system. Please refer to <xref linkend="platform"/> for more details.</para>
+
+<para
+>Decide on a platform and set it up for your system. This <acronym
+>FAQ</acronym
+> can not help you with this, since &kde;<ulink url="http://www.kde.org"
+> runs on many &UNIX;</ulink
+> platforms. </para>
+
+<!-- Taken out because we can not help with all platforms and KDEisnotLINUX -->
+
+<para
+>Finally, you are ready to commence the &kde; installation. Please start reading from the next section. To get &kde;, please refer to <xref linkend="where-to-get-kde"/>. Last but not least, if you encounter any problems while installing &kde;, please do not hesitate to make use of the &kde; <link linkend="mailing-lists"
+>mailing lists</link
+> and <link linkend="newsgroups"
+>newsgroups</link
+>. But do bear this in mind: no question is too silly to ask, but some are too silly to answer, especially when they are already answered in this <acronym
+>FAQ</acronym
+>.</para>
+<para
+>Good luck and have fun!</para>
+
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>Available package formats</para>
+</question>
+<answer>
+
+
+<para
+>You can find several kinds of binary and source packages for different distributions and operating systems on the &kde-ftp;. The binary packages are not made by the &kde; Team, but by the distributors themselves, or some dedicated individuals. Please refer to <ulink url="http://dot.kde.org/986933826/"
+>&kde; Package Policy Explained</ulink
+> for information about the &kde; Package Policy. The only <quote
+>official</quote
+> release is the source tar.bz2 packages. Please refer to the <filename
+>README</filename
+>s and <filename
+>INSTALL</filename
+>s in the several binaries folders. For a list of the available packages for a release, refer to the relevant info page. For the latest release this is the <ulink url="http://www.kde.org/info/3.2.php"
+>&kde; 3.2 Info Page</ulink
+>.</para>
+
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question id="prerequisites">
+<para
+>Prerequisites</para>
+</question>
+<answer>
+
+<!-- rewrite to make it more general, pointing to the according webpages? -->
+
+<para
+>For &kde; 3.2, you need the &Qt; library version 3.2 or greater. Please make sure you download the correct &Qt;. You will also need the header files, if you want to compile &kde; yourself. They are all available, at no cost, from <ulink url="http://www.trolltech.com/products/download"
+>http://www.trolltech.com/download</ulink
+>. In addition, there are optional libraries that might improve &kde; if installed on your system. An example is OpenSSL which will enable &konqueror; to browse web pages securely and is needed in a version 
+>=0.9.6. These should be provided by your distributor; if not, ask for an update.</para>
+
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>Description of the base packages</para>
+</question>
+<answer>
+<para
+>The base distribution currently consists of eleven packages. Some are required, while others are optional. Each package is available in each of the aforementioned package formats.</para>
+<variablelist>
+<varlistentry>
+<term
+>tdelibs</term>
+<listitem>
+<para
+>Required</para>
+<para
+>This package contains shared libraries that are needed by all &kde; applications.</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term
+>tdebase</term>
+<listitem>
+<para
+>Required</para>
+<para
+>This package contains the base applications that form the core of the K Desktop Environment like the window manager, the terminal emulator, the control centre, the file manager, and the panel.</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term
+>&arts;</term>
+<listitem>
+<para
+>Required</para>
+<para
+>The &arts; sound server. A powerful, network transparent sound server.</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term
+>tdeaddons</term>
+<listitem>
+<para
+>Optional</para>
+<para
+>Various plugins for &kate;, &kicker;, &knewsticker;, &konqueror; and &noatun; </para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term
+>tdeartwork</term>
+<listitem>
+<para
+>Optional</para>
+<para
+>Additional wallpapers, themes, styles, sounds ...</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term
+>tdebindings</term>
+<listitem>
+<para
+>Optional</para>
+<para
+>Various bindings for other languages, including &Java;, Perl, Python, ...</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term
+>tdegames</term>
+<listitem>
+<para
+>Optional</para>
+<para
+>Various games like &kmahjongg;, &ksnake;, &kasteroids;, and &kpatience;.</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term
+>tdegraphics</term>
+<listitem>
+<para
+>Optional</para>
+<para
+>Various graphics-related programs like &PostScript; previewer, &DVI; previewer, and a drawing program.</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term
+>tdeutils</term>
+<listitem>
+<para
+>Optional</para>
+<para
+>Various desktop tools like a calculator, an editor and other nifty stuff.</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term
+>tdemultimedia</term>
+<listitem>
+<para
+>Optional</para>
+<para
+>Multimedia applications like a &CD; player and a mixer.</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term
+>tdenetwork</term>
+<listitem>
+<para
+>Optional</para>
+<para
+>Network applications. Currently contains the mail program &kmail;, the news reader &knode;, and several other network-related programs.</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term
+>tdeadmin</term>
+<listitem>
+<para
+>Optional</para>
+<para
+>System administration programs.</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term
+>tdeedu</term>
+<listitem>
+<para
+>Educational and entertaining applications for &kde;'s younger users. </para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term
+>tdetoys</term>
+<listitem>
+<para
+>Optional</para>
+<para
+>Toys!</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term
+>tdevelop</term>
+<listitem>
+<para
+>Optional</para>
+<para
+>A complete Integrated Development Environment for &kde; and Qt</para>
+</listitem>
+</varlistentry>
+</variablelist>
+	
+<para
+>&arts; and then tdelibs should be installed before everything else, and tdeaddons last. The other packages can be installed in any arbitrary order.</para>
+
+<para
+>Most package management tools will let you put all these packages in one folder and install them all at once, figuring out the dependencies as they go.</para>
+
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>Installation instructions for the different package formats</para>
+</question>
+<answer>
+<para
+><important>
+<para
+>Please do not forget to read the <filename
+>README</filename
+> and <filename
+>INSTALL</filename
+> files if they are available.</para>
+</important
+></para>
+<variablelist>
+<varlistentry>
+<term
+>Installation of the Debian packages</term>
+<listitem>
+<para
+>The Debian packages install in accordance with the upcoming <acronym
+>FHS</acronym
+> (File Hierarchy Standard).</para>
+<procedure>
+<step performance="required"
+><para
+>become superuser</para
+></step>
+<step performance="required"
+><para
+>run <command
+>dpkg <option
+>-i <replaceable
+>packagename.deb</replaceable
+></option
+></command
+> for every package you want to install.</para
+></step>
+</procedure>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term
+>Installation of the <acronym
+>RPM</acronym
+> packages</term>
+<listitem>
+<procedure>
+<title
+>To install binary <acronym
+>RPM</acronym
+>s</title>
+<step performance="required"
+><para
+>become superuser</para
+></step>
+<step performance="required"
+><para
+>execute <command
+>rpm <option
+>-ivh <replaceable
+>packagename.rpm</replaceable
+></option
+></command
+></para
+></step>
+</procedure>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term
+>Installation of the source <filename
+>.tar.bz2</filename
+> files</term>
+<listitem>
+<para
+>Since there are always changes and updates to the way &kde; is compiled, please refer to <ulink url="http://developer.kde.org/build/index.html"
+>Download and Install from Source</ulink
+> for the most up to date installation instructions for the source packages. </para>
+<para
+>The general approach should work in most cases though. </para>
+<para
+>The source <filename
+>.tar.bz2</filename
+> package installs into <filename class="directory"
+>/usr/local/kde</filename
+> by default. You can override this setting by using the <option
+>--prefix</option
+> option of the <filename
+>configure</filename
+> script.</para>
+<procedure>
+<step performance="required"
+><para
+>unpack the packages with <command
+>tar <option
+>jxvf <replaceable
+>packagename.tar.bz2</replaceable
+></option
+></command
+></para
+></step>
+<step performance="required"
+><para
+>change folder to the package folder: <command
+>cd <replaceable
+>packagename</replaceable
+></command
+></para
+></step>
+<step performance="required"
+><para
+>configure the package: <command
+>./configure</command
+> <note
+><para
+>Some packages (notably tdebase) have special configuration options that might be applicable to your installation. Type <command
+>./configure <option
+>--help</option
+></command
+> to see the available options.</para
+></note
+></para
+></step>
+<step performance="required"
+><para
+>build the package: <command
+>make</command
+></para
+></step>
+<step performance="required"
+><para
+>install the package: <command
+>su <option
+>-c "make install"</option
+></command
+> (if you aren't already root). If you already are, just type <command
+>make <option
+>install</option
+></command
+>.</para
+></step>
+</procedure>
+</listitem>
+</varlistentry>
+</variablelist>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>Post-installation procedures</para>
+</question>
+<answer>
+<para
+>First of all, please make sure that you have added &kde;'s binary installation folder (&eg; <filename class="directory"
+>/usr/local/kde/bin</filename
+>) to your <envar
+>PATH</envar
+> and &kde;'s library installation folder to your <envar
+>LD_LIBRARY_PATH</envar
+> (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, &eg; it is called <envar
+>SHLIB_PATH</envar
+> on &IRIX;. Then set the environment variable <envar
+>KDEDIR</envar
+> to the base of your &kde; tree, &eg; <filename class="directory"
+>/usr/local/kde</filename
+>. <caution
+> <para
+>Please bear in mind that it is unwise to set <envar
+>LD_LIBRARY_PATH</envar
+> blindly. In the vast majority of cases it is unnecessary and can do more harm than good. There is a web page written by <ulink url="mailto:barr@cis.ohio-state.edu"
+>Dave Barr</ulink
+> explaining the evils of <envar
+>LD_LIBRARY_PATH</envar
+> 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>
+</caution>
+</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 and its helper programs.</para>
+<para
+>In order to make it easy for you, we have provided a simple script called <filename
+>starttde</filename
+> which gets installed in <filename class="directory"
+>$<envar
+>KDEDIR</envar
+>/bin</filename
+> and is therefore in your path.</para>
+<para
+>Edit the file <filename
+>.xinitrc</filename
+> in your home folder (make a backup copy first!), remove everything that looks like calling a window manager, and insert <command
+>starttde</command
+> instead. Restart the &X-Server;. If you use &kdm;/<application
+>xdm</application
+>, you will have to edit the file <filename
+>.xsession</filename
+> instead of <filename
+>.xinitrc</filename
+>. And if there is no <filename
+>.xinitrc</filename
+> or <filename
+>.xsession</filename
+> in your home folder, simply create a new one with just one line containing <command
+>starttde</command
+>. <note
+> <para
+>Some systems (notably &RedHat; &Linux;) use <filename
+>.Xclients</filename
+> instead.</para>
+</note
+></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/quickstart/index.html"
+>Quick Start guide</ulink
+> available. Furthermore, every application has an online help that is available via the <guimenu
+>help</guimenu
+> menu.</para>
+</answer>
+</qandaentry>
+
+
+<qandaentry>
+<question>
+<para
+>Should I remove old version xyz before installing a new one?</para>
+</question>
+<answer>
+<para
+>In principle, this is not necessary. <acronym
+>RPM</acronym
+> and Debian packages should take care of all dependencies.</para>
+<para
+>If you compile the source code yourself, you should take more care. Instructions for running two different versions of &kde; on the same system are given at <ulink url="http://developer.kde.org/build/kde2-and-kde3.html"
+>http://developer.kde.org/build/kde2-and-kde3.html</ulink
+>. However, please note that running two different versions of &kde; from source can lead to problems if you are not careful. </para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question id="starttde">
+<para
+>How do I start &kde;?</para>
+</question>
+<answer>
+<para
+>The most comfortable method to start &kde; is to use the <filename
+>starttde</filename
+> script. Simply put the line <command
+>starttde</command
+> at the end of your <filename
+>.xsession</filename
+> file (or your <filename
+>.xinitrc</filename
+> or <filename
+>.Xclients</filename
+> file if you are not using &kdm; or <application
+>xdm</application
+>). Please also remove the lines that start your previous window manager. If there is no <filename
+>.xsession</filename
+>, <filename
+>.xinitrc</filename
+>, or <filename
+>.Xclients</filename
+> in your home folder, simply create a new one that contains just one line: <command
+>starttde</command
+>.</para>
+</answer>
+</qandaentry>
+<!-- Still needed?
+<qandaentry>
+<question>
+<para
+>Whenever I start &kde;, it complains about "shadow passwords".
+Why?</para>
+</question>
+<answer>
+<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.
+<caution
+><para
+>The screensavers might be configured to secure the
+machine until the password is entered.</para
+></caution
+></para>
+<procedure>
+<title
+>Setting the suid bit on the screensavers</title>
+<step performance="required"
+><para
+>become root</para
+></step>
+<step performance="required"
+><para
+><command
+>chown root
+$<envar
+>KDEDIR</envar
+>/bin/*.kss</command
+></para
+></step>
+<step performance="required"
+><para
+><command
+>chmod u+s
+$<envar
+>KDEDIR</envar
+>/bin/*.kss</command
+></para
+></step>
+</procedure>
+<para
+>Alternatively, if you compile &kde; from source, you can use
+<command
+>./configure <option
+>with-shadow</option
+></command
+> to
+configure tdebase.  Then the suid bit is set automatically during
+<command
+>make install</command
+>.</para>
+</answer>
+</qandaentry>
+-->
+<qandaentry>
+<question>
+<para
+>Is it possible to install &kde; in a user folder?</para>
+</question>
+<answer>
+<para
+>Yes, you can install &kde; in any folder you want. What you have to do depends on the kind of packages you want to install:</para>
+<procedure
+><title
+>Source packages</title>
+<step performance="required"
+><para
+>Configure and install the package using <command
+>configure <option
+>--prefix=<replaceable
+>/users/myhome/kde</replaceable
+></option
+>; make; make install</command
+> to install into <filename class="directory"
+>/users/myhome/kde</filename
+>.</para
+></step>
+<step performance="required"
+><para
+>Add the following to your init files. Please note that if it is not necessary for you to set <envar
+>LD_LIBRARY_PATH</envar
+>, it is better to leave it out.</para>
+
+<para
+>For csh or tcsh:</para>
+<programlisting
+>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  
+</programlisting>
+<para
+>For <application
+>bash</application
+>:</para>
+<programlisting
+>KDEDIR=/users/myhome/kde
+PATH=$KDEDIR/bin:$PATH
+LD_LIBRARY_PATH=$KDEDIR/lib:$LD_LIBRARY_PATH
+LIBRARY_PATH=$LD_LIBRARY_PATH
+export KDEDIR PATH LD_LIBRARY_PATH LIBRARY_PATH
+</programlisting
+></step>
+</procedure>
+<procedure
+><title
+><acronym
+>RPM</acronym
+> packages</title>
+<step performance="required"
+><para
+><command
+>rpm</command
+> allows you to use the <option
+>--prefix</option
+> option to select the folder you want to install to. For example, executing <command
+>rpm <option
+>-i --prefix=<replaceable
+>/users/myhome/kde package.rpm</replaceable
+></option
+></command
+> will install the package to <filename class="directory"
+>/users/myhome/kde</filename
+>.</para
+></step>
+</procedure>
+<para
+><note>
+<para
+>Although &kde; will run from a user folder, there are some problems with programs that require suid root, &eg; the programs in the tdeadmin package. But since they are not meant to be run by users in the first place, this is nothing to worry about.</para>
+<para
+>However, on systems using shadow passwords, the screensavers have to be suid root to enable password access for unlocking the screen, so this option will not work.</para>
+</note
+></para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+><command
+>starttde</command
+> fails with <errorname
+>can not connect to X server</errorname
+>. What is wrong?</para>
+</question>
+<answer>
+<para
+>You probably tried to start the X server with <command
+>starttde</command
+>. The X server is started with <command
+>startx</command
+>. <command
+>starttde</command
+> is the script that should be run from your <filename
+>.xinitrc</filename
+>, <filename
+>.xsession</filename
+>, or <filename
+>.Xclients</filename
+> to activate the window manager and the necessary server daemons for &kde;. See also <xref linkend="starttde"/>.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>&kde; on &AIX;?</para>
+</question>
+<answer>
+<para
+><acronym
+>IBM</acronym
+> now officially support &kde; on &AIX;. You can find details at <ulink url="http://www.ibm.com/servers/aix/products/aixos/linux/index.html"
+>http://www.ibm.com/servers/aix/products/aixos/linux/index.html</ulink
+>. There is also some older information at <ulink url="http://space.twc.de/~stefan/kde/aix.html"
+>http://space.twc.de/~stefan/kde/aix.html</ulink
+>.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>&kde; on a laptop?</para>
+</question>
+<answer>
+<para
+>If you can get &X-Window; to run on your laptop, you should not have any problem getting &kde; to run on it. In addition, you might find the following links helpful:</para>
+<itemizedlist>
+<listitem>
+<para
+><ulink url="http://www.linux-laptop.net/"
+>http://www.linux-laptop.net/</ulink
+></para>
+</listitem>
+<listitem>
+<para
+><ulink url="http://www.sanpei.org/Laptop-X/note-list.html"
+>http://www.sanpei.org/Laptop-X/note-list.html</ulink
+></para>
+</listitem>
+</itemizedlist>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>I have a neomagic chipset in my laptop. Is there anything special I should do to run &kde;?</para>
+</question>
+<answer>
+<para
+>On some laptops using the 2160 chipset (MagicGraph 128XD) the following options in <filename
+>XF86Config</filename
+> are needed to avoid a lock-up of the graphic engine:</para>
+<screen
+>Option "XaaNoScanlineImageWriteRect"
+           Option "XaaNoScanlineCPUToScreenColorExpandFill"</screen>
+
+<para
+>If you have experienced desktop hangs while using &kde; please try this option.</para
+> 
+</answer
+> 
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>I do not like the default &kde; folder after installation. How do I move it without breaking anything?</para>
+</question>
+<answer>
+<para
+>Assuming the default is <filename class="directory"
+>/opt/kde</filename
+> and you want to move it to <filename class="directory"
+>/usr/local/kde</filename
+>, here's what you have to do:</para>
+<procedure>
+<step performance="required"
+><para
+>change to superuser if you aren't already</para
+></step>
+<step performance="required"
+><para
+><command
+>mv /opt/kde /usr/local/kde</command
+></para
+></step>
+<step performance="required"
+><para
+><command
+>ln -s /usr/local/kde /opt/kde</command
+></para
+></step>
+</procedure>
+<para
+>This will put all your &kde; files in <filename class="directory"
+>/usr/local/kde</filename
+> but everything is still accessible from <filename class="directory"
+>/opt/kde</filename
+>.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>What files can I delete from my &kde; install folder? Can all the <filename
+>*.h</filename
+>, <filename
+>*.c</filename
+> and <filename
+>*.o</filename
+> files be safely removed?</para>
+</question>
+<answer>
+<para
+>There should not be any need to keep the <filename
+>.c</filename
+> and <filename
+>.o</filename
+> files, but you might want to keep the <filename
+>.h</filename
+> files, as they are used by includes if you ever want to compile your own &kde; programs. But if you wish to add patches to the source programs as they become available (rather than downloading everything again), then they should stay.</para
+> 
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>Will I lose my current settings when I upgrade &kde;?</para>
+</question>
+<answer>
+
+<para
+>No. In most cases &kde; will be able to transport your settings intact. You may need to reenter passwords in some applications (such as &kmail; or &knode;) but most other settings will be safe.</para>
+
+<para
+>There were mixed reports of results between some previous versions of &kde;. To be safe, you may like to back up your entire &kde; configuration. </para>
+
+<para
+>Settings are kept in the <filename class="directory"
+>$<envar
+>HOME</envar
+>/.kde</filename
+> or <filename class="directory"
+>$<envar
+>HOME</envar
+>/.kde2</filename
+> subfolder in your home folder. Copy your old <filename class="directory"
+>.kde</filename
+>/<filename class="directory"
+>.kde2</filename
+> folder to a backup location, install &kde; 3.2, and then copy back any necessary mail and news settings. That said, most people can make a direct upgrade, without removing the old <filename class="directory"
+>.kde</filename
+> folder, without a hitch.</para>
+<para
+>You can override the use of <filename class="directory"
+>$<envar
+>HOME</envar
+>/.kde</filename
+> by setting the $<envar
+>KDEHOME</envar
+> variable.</para
+> 
+</answer>
+</qandaentry>
+
+<qandaentry id="greyscreen">
+<question>
+<para
+>I upgraded &kde; and it seemed to go fine, but when I start it, I get a blank grey screen, and nothing happens. There are errors in the console about DCOPserver. What's going on?</para>
+</question>
+
+<answer>
+<para
+>&kde; uses several temporary files during its operation. These are usually to be found in the following locations:</para>
+<itemizedlist>
+<listitem
+><para
+><filename
+>~/.DCOPserver-*</filename
+> (there are usually two of these; one is a symlink to the other)</para
+></listitem>
+<listitem
+><para
+><filename
+>~/.kde/socket-<replaceable
+>hostname</replaceable
+></filename
+></para
+></listitem>
+<listitem
+><para
+><filename
+>~/.kde/tmp-<replaceable
+>hostname</replaceable
+></filename
+> which is normally a symlink to the next file:</para
+></listitem>
+<listitem
+><para
+><filename
+>/tmp/tmp-kde-<replaceable
+>USER</replaceable
+></filename
+></para
+></listitem>
+<listitem
+><para
+><filename
+>~/.kde/socket-<replaceable
+>hostname</replaceable
+></filename
+> which is also normally a symlink to:</para
+></listitem>
+<listitem
+><para
+><filename
+>/tmp/ksocket-<replaceable
+>USER</replaceable
+></filename
+></para
+></listitem>
+</itemizedlist>
+
+<para
+>If the symlinks get broken, usually because a <command
+>cron</command
+> or shutdown script is emptying out the <filename class="directory"
+>/tmp</filename
+> folder, then strange things will happen. These files, and the symlinks, will all be created automatically at the start of &kde; so you can safely remove them <emphasis
+>while &kde; is not running</emphasis
+>.</para>
+
+<para
+>If you are only getting a grey screen when you start &kde;, or if you get an error message telling you to <errorname
+>Check your installation</errorname
+>, then shut down X and delete all the files listed above, then try to restart X.</para>
+
+<para
+>Normally (&ie; when not upgrading between &kde; versions) it's quite safe to leave these files intact, and you may shave a few seconds off your &kde; startup time by doing so.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>Compiling tdebase gives me a <errorname
+>bin/sh: msgfmt: command not found</errorname
+> error!</para>
+</question>
+<answer>
+<para
+>You need the &GNU; <application
+>msgfmt</application
+> which is part of the &GNU; i18n package <application
+>gettext</application
+>. You should be able to download it from any &GNU; mirror.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>How do I uninstall &kde; applications compiled from source?</para>
+</question>
+<answer>
+<para
+>You can uninstall your programs by typing <command
+>make uninstall</command
+> in the folder where you did <command
+>make install</command
+>. If you have already deleted that folder, then there is only one way, and it is not good: go to <filename class="directory"
+>$<envar
+>KDEDIR</envar
+>/bin</filename
+> and start deleting files one by one.</para>
+<para
+>If you expect to find yourself in this situation, you might want to consider a program such as &GNU; <application
+>stow</application
+>, found at <ulink url="http://www.gnu.org/software/stow/stow.html"
+>http://www.gnu.org/software/stow/stow.html</ulink
+>.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question id="gif">
+<para
+>What is up with &GIF; support?</para>
+</question>
+<answer>
+<para
+>This has to do with issues with Unisys' &LZW; patent. &GIF; support is turned off from &Qt; 1.44 onwards by default. When you want to use &GIF;s and have the relevant license, recompile &Qt; with &GIF; support. <command
+>./configure <option
+>-gif</option
+></command
+>.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>How do I install &kde; themes?</para>
+</question>
+<answer>
+<para
+>Theme support in &kde; has been discontinued with this version. However, there are many opportunities to personalise and add eye candy to &kde; Look at, for example, <guilabel
+>Appearance &amp; Themes</guilabel
+> in &kcontrol;. </para>
+</answer>
+</qandaentry>
+</qandaset>
+</chapter>
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/faq/intro.docbook b/tde-i18n-en_GB/docs/tdebase/khelpcenter/faq/intro.docbook
new file mode 100644
index 00000000000..525629c101d
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/faq/intro.docbook
@@ -0,0 +1,100 @@
+<!--
+<?xml version="1.0" ?>
+<!DOCTYPE chapter PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN"
+ "dtd/kdex.dtd">
+-->
+
+<chapter id="introduction">
+<title
+>Introduction</title>
+
+<qandaset>
+<qandaentry>
+<question>
+<para
+>What is &kde;?</para>
+</question>
+<answer>
+<para
+>&kde; is the K Desktop Environment. It is a project initiated by <ulink url="mailto:ettrich@kde.org"
+>Matthias Ettrich</ulink
+> in 1996. The aim of the &kde; project is to connect the power of the &UNIX; operating systems with the comfort of a modern user interface.</para>
+<para
+>In short, &kde; will bring &UNIX; to the desktop!</para>
+<para
+>If you want further information about &kde;, have a look at <ulink url="http://www.kde.org/whatiskde/index.html"
+>What is &kde;?</ulink
+></para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question id="platform">
+<para
+>On which platforms can I expect &kde; to work?</para>
+</question>
+<answer>
+<para
+>&kde; is a Desktop Environment for all flavours of &UNIX;. While it is true that most &kde; developers use &Linux;, &kde; runs smoothly on a wide range of systems. You may, however, need to tweak the source code a bit to get &kde; to compile on a not-so-popular variant of &UNIX;, or if you are not using the &GNU; development tools, in particular the &gcc; compiler.</para>
+<para
+>For an almost complete list of systems &kde; is running on, please refer to <ulink url="http://promo.kde.org/kde_systems.php"
+>this list of systems for KDE</ulink
+> </para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>Is &kde; a window manager?</para>
+</question>
+<answer>
+<para
+>No, &kde; is not a window manager. While &kde; includes a very sophisticated window manager (&twin;), &kde; is much more than that. It is a full-blown Integrated Desktop Environment.</para>
+<para
+>&kde; provides a complete desktop environment, including a web browser, a file manager, a window manager, a help system, a configuration system, uncountable tools and utilities, and an ever increasing number of applications, including but not limited to mail and news clients, drawing programs, a &PostScript; and a &DVI; viewer and so forth.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>Is &kde; a <acronym
+>CDE</acronym
+>, &Windows; 95 or &Mac; <acronym
+>OS</acronym
+> clone?</para>
+</question>
+<answer>
+<para
+>No, &kde; is not a clone. Specifically &kde; is not a <acronym
+>CDE</acronym
+> or &Windows; clone. While the &kde; developers have and will continue to glean the best features from all existing desktop environments, &kde; is a truly unique environment that has and will continue to go its own way.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>Is &kde; free software?</para>
+</question>
+<answer>
+<para
+>Yes, &kde; is free software according to the &GNU; General Public Licence. All &kde; libraries are available under the <acronym
+>LGPL</acronym
+> making commercial software development for the &kde; desktop possible, but all &kde; applications are licensed under the <acronym
+>GPL</acronym
+>.</para>
+<para
+>&kde; uses the <link linkend="qt"
+>&Qt; C++ crossplatform toolkit</link
+>, which is also released (since version 2.2) under the <acronym
+>GPL</acronym
+>.</para>
+<para
+>It is absolutely legal to make &kde; and &Qt; available on &CD-ROM; free of charge. No runtime fees of any kind are incurred.</para>
+</answer>
+</qandaentry>
+</qandaset>
+</chapter>
+
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/faq/kdeapps.docbook b/tde-i18n-en_GB/docs/tdebase/khelpcenter/faq/kdeapps.docbook
new file mode 100644
index 00000000000..efca528158a
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/faq/kdeapps.docbook
@@ -0,0 +1,202 @@
+<!--
+<?xml version="1.0" ?>
+<!DOCTYPE chapter PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN"
+ "dtd/kdex.dtd">
+-->
+
+<chapter id="applications">
+<title
+>&kde; applications</title>
+
+<qandaset>
+<qandaentry>
+<question>
+<para
+>&kppp;</para>
+</question>
+<answer>
+
+<para
+>Many &kde; users report problems using &kppp;. But before you complain about &kppp;, make sure you have already checked the following:</para>
+
+<itemizedlist>
+<listitem
+><para
+>Can you dialup to your <acronym
+>ISP</acronym
+> without using &kppp;? If you cannot, then perhaps &kppp; is not the culprit after all.</para
+></listitem>
+<listitem
+><para
+>Have you gone through the &kppp; documentation at least three times and followed its instructions and trouble-shooting suggestions?</para
+></listitem>
+</itemizedlist>
+<para
+>The &kppp; documentation can be accessed through the <application
+>&kde; Help Centre</application
+>. Last, but not least, the &kppp; homepage is at <ulink url="http://ktown.kde.org/~kppp/"
+>http://ktown.kde.org/~kppp/</ulink
+>.</para>
+<para
+>Now, if you still encounter problems, here's what might help you solve them:</para>
+<variablelist>
+<varlistentry
+><term
+>How do I change the &MTU; setting in &kppp;?</term>
+<listitem
+><para
+>Open up the &kppp; dialogue box and select <guibutton
+>Setup</guibutton
+>. Choose an existing account and click <guibutton
+>Edit</guibutton
+>, or <guibutton
+>New</guibutton
+> to create a new dialup account. Select the <guilabel
+>Dial</guilabel
+> tab and click <guibutton
+>Arguments</guibutton
+>. Type what you want to change in the Argument textbox (&eg; <userinput
+>mtu 296</userinput
+>) and click <guibutton
+>Add</guibutton
+>. When you are satisfied, click <guibutton
+>Close</guibutton
+>.</para>
+<para
+>To check whether the options <quote
+>took</quote
+>, do one of the following:</para>
+<itemizedlist>
+<listitem>
+<para
+>In a terminal window, run <userinput
+><command
+>/sbin/ifconfig</command
+> ppp0</userinput
+> and look at the reported &MTU; in the output. It should match your request.</para>
+</listitem>
+<listitem
+><para
+>Add <option
+>debug</option
+> and <option
+>kdebug</option
+> (each on a separate line) to your <filename
+>/etc/ppp/options</filename
+> file and restart your &PPP; session. You will find debugging messages in <filename
+>/var/log/messages</filename
+>, including &MRU; and &MTU; settings.</para
+></listitem>
+</itemizedlist>
+<para
+>If you want, the &MRU; and &MTU; settings can be added to the <filename
+>options</filename
+> file, one complete setting per line, no quotes or dashes.</para
+></listitem>
+</varlistentry>
+<varlistentry>
+<term
+>&kppp; connects at a slower speed than normal.</term>
+<listitem
+><para
+>The following might do the trick:</para>
+<itemizedlist>
+<listitem
+><para
+>Try executing <command
+>setserial spd_hi</command
+>.</para
+></listitem>
+<listitem
+><para
+>The default &MTU; value is 1500, which maybe too large for a dialup connection. Try changing it to a smaller value like <userinput
+>296</userinput
+> or <userinput
+>576</userinput
+>.</para
+></listitem>
+<listitem
+><para
+>Check in your <filename class="directory"
+>$<envar
+>HOME</envar
+>/.kde/share/config</filename
+> for the <filename
+>kppprc</filename
+>. Ensure the correct modem speed is actually defined there.</para
+></listitem>
+</itemizedlist
+></listitem>
+</varlistentry>
+</variablelist>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>&konsole;</para>
+</question>
+<answer>
+<variablelist>
+<varlistentry>
+<term
+>How do I page-up or page-down?</term>
+<listitem
+><para
+>Use <keycombo action="simul"
+> <keycap
+>Shift</keycap
+><keycap
+>Page Up</keycap
+></keycombo
+> and <keycombo action="simul"
+><keycap
+>Shift</keycap
+><keycap
+>Pg Dn</keycap
+></keycombo
+>. </para
+></listitem>
+</varlistentry>
+<varlistentry>
+<term
+>How do I perform a simple <quote
+>copy</quote
+> from &konsole; to anything else?</term>
+<listitem
+><para
+>When I do a <command
+>ls</command
+>, first I select with the mouse the desired text, press <keycombo action="simul"
+>&Ctrl;<keycap
+>C</keycap
+></keycombo
+>, then I make the target application active, point the mouse to the relevant part and press <keycombo action="simul"
+>&Ctrl;<keycap
+>V</keycap
+></keycombo
+>. Alternatively, highlight the text by dragging with the &LMB; down and paste by clicking with the &MMB; (or both buttons if you are using a 2 button mouse with 3 button emulation). </para
+></listitem>
+</varlistentry>
+</variablelist>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>&kmail;</para>
+</question>
+<answer>
+<para
+>&kmail; has its own home page at <ulink url="http://kmail.kde.org"
+>http://kmail.kde.org</ulink
+> where an <acronym
+>FAQ</acronym
+> is available.</para>
+</answer>
+</qandaentry>
+
+</qandaset>
+</chapter>
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/faq/misc.docbook b/tde-i18n-en_GB/docs/tdebase/khelpcenter/faq/misc.docbook
new file mode 100644
index 00000000000..a2ae1725981
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/faq/misc.docbook
@@ -0,0 +1,327 @@
+<!--
+<?xml version="1.0" ?>
+<!DOCTYPE chapter PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN"
+ "dtd/kdex.dtd">
+-->
+
+<chapter id="misc">
+<title
+>Miscellaneous questions</title>
+
+<qandaset>
+<qandaentry>
+<question>
+<para
+>Why does &kde; use &Qt;?</para>
+</question>
+<answer>
+<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 which ensures efficiency and code reuse in a project the size and scope of &kde;. In our opinion there is no better toolkit available for &UNIX; systems and that it would have been a grave mistake to try to build &kde; on anything but the best.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>Why does &kde; not use gtk, xforms, xlib, whatever?</para>
+</question>
+<answer>
+<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>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>But &Qt; isn't free, is it?</para>
+</question>
+<answer>
+<para
+>It is! As of September 4, 2000, version 2.2 of the &Qt; libraries were licensed under the <acronym
+>GPL</acronym
+>, thereby fulfiling all aspects of <quote
+>free software</quote
+>.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>Does &kde; have terminal emulators with transparent background?</para>
+</question>
+<answer>
+<para
+>Yes and no. &konsole; has the ability to simulate transparency by redrawing the background of the window inside the &konsole; window. This gives the illusion of transparency, but if you place &konsole; on top of another window, the transparency is lost. <ulink url="http://www.eterm.org"
+>Eterm</ulink
+> should work fine under &kde; if you desire more complete transparency.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>How do I create icons for non-&kde; applications that I can put in the <guimenu
+>K</guimenu
+> menu? Where do these icons go?</para>
+</question>
+<answer>
+<para
+>Create them using your favourite image manipulator, for example, <application
+>GIMP</application
+>, or the <application
+>&kde; Icon Editor</application
+> and put them in <filename class="directory"
+>$<envar
+>KDEDIR</envar
+>/share/icons(/mini)</filename
+> or <filename class="directory"
+>$<envar
+>HOME</envar
+>/.kde/share/icons(/mini)</filename
+>. </para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>What about &kde; programs that do not have icons? How do I get them into the menu?</para>
+</question>
+<answer>
+<para
+>Use &kmenuedit;. To access it use the &RMB; on the <guibutton
+>K</guibutton
+> button and select <guimenu
+>Menu Editor</guimenu
+>.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>Does &kde; have a graphical &FTP; client?</para>
+</question>
+<answer>
+<para
+>Yes, and it is none other than your favourite file manager, &konqueror;. You can drag and drop remote files into local folders.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>How do I exit &kde;?</para>
+</question>
+<answer>
+<para
+>Simply click on the <guibutton
+>K</guibutton
+> button and select <guimenu
+>Logout</guimenu
+>. In addition, if you <mousebutton
+>right</mousebutton
+> click on an empty area of the desktop, you will be presented with a menu containing logout as one of the options. <note
+><para
+>Depending on your configuration of the &X-Window;, <keycombo action="simul"
+>&Ctrl;&Alt;&Backspace;</keycombo
+> might also do the trick by killing the X server, but its use prevents session management and cannot be recommended.</para
+></note
+></para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>Is there a program that checks for new mails at my <acronym
+>ISP</acronym
+> if and only if I am online?</para>
+</question>
+<answer>
+<para
+>&korn; will do the job. If you are not connected, it will just sit there (idling).</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>Is it really necessary to upgrade to the latest version?</para>
+</question>
+<answer>
+<para
+>We recommend to always use the latest stable release. If you don't, it will probably be difficult to get answers to your questions. If you have a problem with an old version, the answer will probably be <quote
+>Please upgrade and try again</quote
+>. Note that new versions also sometimes fix security problems.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>How do I copy and paste in &kde;?</para>
+</question>
+<answer>
+<para
+>The simplest method is to use your mouse:</para>
+<procedure>
+<step performance="required"
+><para
+>Highlight the text you want to copy by holding down the &LMB; and dragging across the text.</para
+></step>
+<step performance="required"
+><para
+>Go to the destination area; depending on your configuration, you might need to click it using the &LMB; to give it focus.</para
+></step>
+<step performance="required"
+><para
+>Click the &MMB; to paste. If you have a two button mouse and are emulating a three button mouse, push both buttons simultaneously.</para
+></step>
+</procedure>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>How do I convert the default &RedHat; menus into a menu in the <guimenu
+>K</guimenu
+> menu?</para>
+</question>
+<answer>
+<para
+>Click on the <guibutton
+>K</guibutton
+> button and select <menuchoice
+><guimenu
+>System</guimenu
+><guimenuitem
+>Appfinder</guimenuitem
+></menuchoice
+>.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question id="CVS">
+<para
+>What is <acronym
+>CVS</acronym
+>?</para>
+</question>
+<answer>
+<para
+>It stands for Concurrent Versions System. It is a version control system and is based on <acronym
+>RCS</acronym
+> (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 files 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>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>Does &kde; support dual screen (Xinerama)?</para>
+</question>
+<answer>
+<para
+>Yes, you need to have a multi-headed X server (&eg; MetroX or XFree86 4.0 and above) and a &kde; 
+>= 2.2.1 </para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>Why does Drag and Drop not work with Xinerama?</para>
+</question>
+<answer>
+<para
+>You should upgrade to XFree86 4.2.0 for this to work properly.</para>
+</answer>
+</qandaentry>
+
+
+<qandaentry>
+<question>
+<para
+>How do I check which version of &kde; I am using?</para>
+</question>
+<answer>
+<para
+>Fire up your <application
+>&kde; Control Centre</application
+>. It comes up with an Info Screen including the version of &kde; The &kde; version is also included in the application's <guimenuitem
+>About</guimenuitem
+> dialogue. </para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>Can I write commercial software for &kde;?</para>
+</question>
+<answer>
+<para
+>You can use the &kde; libraries to write <quote
+>commercial and closed source</quote
+> as well as <quote
+>commercial and open source</quote
+> 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 need to obtain the &Qt; professional edition from Troll Tech. </para
+> <para
+>If you want more information, please contact <ulink url="http://www.trolltech.com"
+>Troll Tech</ulink
+> directly.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>How do I go about creating themes and icons?</para>
+</question>
+<answer>
+<para
+>Go see <ulink url="http://artist.kde.org"
+>http://artist.kde.org</ulink
+>.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>Is <application
+>KLyX</application
+> dead?</para>
+</question>
+<answer>
+<para
+>Yes. But future versions of <application
+>LyX</application
+> will be &GUI; independent. Check the progress of the various &GUI; frontends <ulink url="http://devel.lyx.org/guii.php3"
+>here</ulink
+>.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>How can I get to know about development updates?</para>
+</question>
+<answer>
+<para
+>You might want to subscribe to the various &kde; mailing lists available, especially kde-cvs, which lists all commits done to the &kde; <acronym
+>CVS</acronym
+> repository. Check <ulink url="http://lists.kde.org"
+>http://lists.kde.org</ulink
+> if you want to read without subscribing.</para>
+</answer>
+</qandaentry>
+</qandaset>
+</chapter>
+
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/faq/moreinfo.docbook b/tde-i18n-en_GB/docs/tdebase/khelpcenter/faq/moreinfo.docbook
new file mode 100644
index 00000000000..ee77ff73614
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/faq/moreinfo.docbook
@@ -0,0 +1,253 @@
+<!--
+<?xml version="1.0" ?>
+<!DOCTYPE chapter PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN"
+ "dtd/kdex.dtd">
+-->
+
+<chapter id="more-info">
+<title
+>Getting more information</title>
+
+<qandaset>
+<qandaentry>
+<question>
+<para
+>Where is the &kde; homepage?</para>
+</question>
+<answer>
+<para
+>The &kde; homepage is located at <ulink url="http://www.kde.org"
+>http://www.kde.org</ulink
+>. If you prefer a local mirror, there are several to choose from. For a current list of web site mirrors sorted by location, please visit <ulink url="http://www.kde.org/mirrors/web.php"
+>http://www.kde.org/mirrors/web.php</ulink
+>.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question id="mailing-lists">
+<para
+>Is there a &kde; mailing list?</para>
+</question>
+<answer>
+<para
+>There are several &kde; mailing lists. Each focuses on a different aspect of &kde;. Some are for developers, so they are not discussed in detail. Some of the more important lists that users might be interested in are:</para>
+<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-look</term>
+<listitem
+><para
+>This is the list that deals with questions about look and feel, and general user interface considerations.</para
+></listitem>
+</varlistentry>
+</variablelist>
+<para
+>For the complete list of mailing lists available, please refer to <ulink url="http://www.kde.org/mailinglists/"
+>http://www.kde.org/mailinglists/</ulink
+>.</para>
+<para
+>Please note that it is not a good idea to ask questions which are already answered in this &FAQ;.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question id="subscribe">
+<para
+>How do I subscribe/unsubscribe to these lists?</para>
+</question>
+<answer>
+<para
+>To subscribe, send an email to list-request, that is:</para>
+<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>
+</itemizedlist>
+<para
+>The email must contain <userinput
+>subscribe <replaceable
+>your_email_address</replaceable
+></userinput
+> in the subject.</para>
+<para
+>To unsubscribe, send an email to list-request, that is:</para>
+<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>
+</itemizedlist>
+<para
+>The email must contain <userinput
+>unsubscribe <replaceable
+>your_email_address</replaceable
+></userinput
+> in the subject. <important
+><para
+>Never send subscribe/unsubscribe request to the mailing lists directly! Use the list-request instead.</para
+></important
+></para>
+<para
+>There is also a complete list of all &kde;-related mailing lists, and a web interface for subscribing and unsubscribing located at <ulink url="http://master.kde.org/mailman/listinfo"
+>http://master.kde.org/mailman/listinfo</ulink
+>.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>Is there a mailing list archive?</para>
+</question>
+<answer>
+
+<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
+>. There you will see a folder 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 (&eg; <quote
+>kde</quote
+> or <quote
+>kde-user</quote
+>) and then the pull-down menu by the search box will default to <quote
+>Body</quote
+> searches. To be thorough, you should probably search the <quote
+>kde</quote
+>, <quote
+>kde-user</quote
+>, and <quote
+>kde-devel</quote
+> folders. </para>
+
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question id="newsgroups">
+<para
+>Is there a newsgroup about &kde;?</para>
+</question>
+<answer>
+<para
+>Yes, there is! It is at <literal
+>comp.windows.x.kde</literal
+>. In addition, there is also a German newsgroup at <literal
+>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>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>Are there any other &kde;-related &FAQ;s?</para>
+</question>
+<answer>
+<para
+>Yes. Here is a list of them:</para>
+<itemizedlist>
+<listitem
+><para
+><ulink
+url="http://www.kde.org/info/faq.php"
+>&kde; &FAQ;</ulink
+></para
+></listitem>
+<listitem
+><para
+><ulink
+url="http://konqueror.org/faq/"
+>&konqueror; &FAQ;</ulink
+></para
+></listitem>
+<listitem
+><para
+><ulink
+url="http://www.arts-project.org/doc/manual/index.html"
+>aRts sound server documentation</ulink
+></para
+></listitem>
+
+<!-- Removed because the kmail FAQ is part of the KMail manual and not a -->
+<!-- separate document 
+<listitem
+><para
+><ulink
+url="http://kmail.kde.org/manual/faq.html"
+>&kmail;
+&FAQ;</ulink
+></para
+></listitem>
+-->
+
+</itemizedlist>
+</answer>
+</qandaentry>
+
+</qandaset>
+</chapter>
+
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/faq/nonkdeapps.docbook b/tde-i18n-en_GB/docs/tdebase/khelpcenter/faq/nonkdeapps.docbook
new file mode 100644
index 00000000000..c6f90e3ae54
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/faq/nonkdeapps.docbook
@@ -0,0 +1,38 @@
+<!--
+<?xml version="1.0" ?>
+<!DOCTYPE chapter PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN"
+ "dtd/kdex.dtd">
+-->
+
+<chapter id="non-kde-apps">
+<title
+>&kde; with non-&kde; applications</title>
+
+<!-- FIXME: This seems to be obsolete. The only similar option is "Apply *colors* to -->
+<!-- non-kde apps" -->
+<qandaset>
+<qandaentry>
+<question>
+<para
+>My non-&kde; applications like &Emacs; and <application
+>kterm</application
+> are running amok with strange colours!</para>
+</question>
+<answer>
+<para
+>Start the <application
+>&kde; Control Centre</application
+> and in <guimenu
+>Appearance &amp; Themes</guimenu
+><guisubmenu
+>Colours</guisubmenu
+> uncheck the <guilabel
+>Apply colours to non-KDE applications</guilabel
+> checkbox and click <guibutton
+>Apply</guibutton
+>.</para>
+</answer>
+</qandaentry>
+
+</qandaset>
+</chapter>
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/faq/notrelated.docbook b/tde-i18n-en_GB/docs/tdebase/khelpcenter/faq/notrelated.docbook
new file mode 100644
index 00000000000..3439bc16594
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/faq/notrelated.docbook
@@ -0,0 +1,309 @@
+<!-- if you want to validate this file separately, uncomment this prolog:
+
+<?xml version="1.0" ?>
+<!DOCTYPE chapter PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN"
+ "dtd/kdex.dtd">
+
+-->
+
+<chapter id="not-kde">
+<title
+>Not really &kde;-related, but frequently asked nevertheless.</title>
+
+<qandaset>
+<qandaentry>
+<question>
+<para
+>How do I change the screen resolution?</para>
+</question>
+<answer>
+<para
+>Use <keycombo action="simul"
+>&Ctrl;&Alt;<keycap
+>+</keycap
+></keycombo
+> and <keycombo action="simul"
+>&Ctrl;&Alt;<keycap
+>-</keycap
+></keycombo
+> to cycle through the resolutions you have defined in <filename
+>XF86Config</filename
+> (maybe under <filename class="directory"
+>/etc/X11</filename
+>; 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-Window; will always start up with that resolution. <caution
+><para
+>Always make a backup copy of your <filename
+>XF86Config</filename
+> file <emphasis
+>before</emphasis
+> you start editing it. Errors in this file can render &X-Window; unusable.</para
+></caution>
+<note
+><para
+>These instructions are only valid if you are running version 3.3.x of the XFree86 server. If you are running XFree86 4.x, you must consult with the <ulink url="http://xfree.org"
+>XFree86(TM): Home Page</ulink
+>.</para
+></note
+></para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>How do I change the colour depth?</para>
+</question>
+<answer>
+<para
+>There is no way you can do this on the fly. You can either start &X-Window; using <command
+>startx <option
+> -bpp <replaceable
+>number</replaceable
+></option
+></command
+> where <replaceable
+>number</replaceable
+> can be 8, 16, 24 or 32, depending on the depth you want. Alternatively, if you are using <application
+>xdm</application
+>/&kdm;, you need to edit <filename
+>/etc/X11/xdm/Xservers</filename
+> (may vary) and enter <userinput
+>:0 local /usr/X11R6/bin/X -bpp 16</userinput
+> for 16 bit colour depth.</para>
+<para
+>You can also edit the <filename
+>XF86Config</filename
+> file and add a line like <userinput
+>DefaultColorDepth <replaceable
+>number</replaceable
+></userinput
+> to Section "Screen". The next time you start X, it will run with the newly-configured colour depth.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>What can I do if I am using a 2-button mouse?</para>
+</question>
+<answer>
+<para
+>Go buy a 3-button one, or use third button emulation. The third button is emulated by pressing both the &LMB; and the &RMB; together. You would need to enable <option
+>Emulate3Buttons</option
+> in your <filename
+>XF86Config</filename
+> file. </para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>What is a "sticky" window?</para>
+</question>
+<answer>
+<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. <application
+>Xclock</application
+> is a typical candidate for sticking, as you need to run only one instance of it, and it always stays with you. </para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>How do I replace the "X" mouse pointer with an arrow?</para>
+</question>
+<answer>
+<para
+>The various types of cursor available in X are defined in <filename class="headerfile"
+>X11/cursorfont.h</filename
+>. You can change it using <command
+>xsetroot -cursor_name <replaceable
+>name_of_cursor</replaceable
+></command
+>. For example, I have the following in my <filename
+>.Xclients</filename
+>:</para>
+<screen
+>xsetroot -cursor_name left_ptr
+</screen>
+<para
+>This will create the common left-angled pointer. To see other alternatives, type <command
+>xfd -fn cursor</command
+>. And of course, do not forget that <command
+>man xsetroot</command
+> is your friend.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>How do I extract/install diff files?</para>
+</question>
+<answer>
+<para
+>To generate a context-diff suitable for patching, use <command
+>diff -u <replaceable
+>old-file new-file</replaceable
+> &gt; <replaceable
+>patchfile</replaceable
+></command
+>. To apply the diff to a file (<abbrev
+>i.e.</abbrev
+> "patch the file"), execute <command
+>patch &lt; <replaceable
+>patchfile</replaceable
+></command
+>.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>How do I get &Linux; to mount the floppy device for use with both DOS and ext2 formatted floppies?</para>
+</question>
+<answer>
+<para
+>Just specify the filesystem type as auto in <filename
+>/etc/fstab</filename
+>. Auto detection works fine for DOS and ext2.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>How do I start &kde; with the <keycap
+>Num Lock</keycap
+> on?</para>
+</question>
+<answer>
+<para
+>Have you tried <command
+>man setleds</command
+>? In addition, you might want to edit your <filename
+>$<envar
+>HOME</envar
+>/.Xmodmap</filename
+> and put the following lines in:</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
+>Other possible alternatives:</para>
+<itemizedlist>
+<listitem
+><para
+><application
+>xkeycaps</application
+>: <mousebutton
+>right</mousebutton
+> clicking should allow edits. You may have to do this as root.</para
+></listitem>
+<listitem
+><para
+><command
+>man XF86Config</command
+> and look under section Keyboard.</para
+></listitem>
+<listitem
+><para
+>Install <application
+>NumLockX</application
+>, which is available from <ulink url="http://dforce.sh.cvut.cz/~seli/en/numlockx"
+>http://dforce.sh.cvut.cz/~seli/en/numlockx</ulink
+>.</para
+></listitem>
+</itemizedlist>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>How do I take window or desktop screenshots?</para>
+</question>
+<answer>
+<para
+>Use &ksnapshot;.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>Is there a tool to make webpages?</para>
+</question>
+<answer>
+<para
+>Yes, and there are a lot of them out there, including <application
+>StarOffice</application
+>, <application
+>&Netscape; Composer</application
+>, and <application
+>XEmacs</application
+>. There are also many &kde; applications. To find the most current list, go to <ulink url="http://kde-apps.org"
+>kde-apps.org: The Latest in &kde; Applications</ulink
+> and search for <emphasis
+>web development</emphasis
+>. Try as many as possible and choose the one most suitable to your needs.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>What do all those acronyms like AFAIK mean?</para>
+</question>
+<answer>
+<para
+><screen
+>AAMOF: as a matter of fact
+AFAIK: as far as I know
+AISE: as I see it
+BFN: bye for now
+BION: believe it or not
+BRB: be right back
+BTW: by the way
+CMIIW: correct me if I am wrong
+FUD: fear, uncertainty, and doubt
+FWIW: for what it's worth
+FYI: for your information
+HTH: hope this helps
+IIRC: if I recall correctly
+IMHO: in my humble opinion
+LOL: laughing out loud
+MYOB: mind your own business
+PITA: pain in the ass
+ROTFL: rolling on the floor laughing
+RTFM: read the fine manual
+SOP: standard operating procedure
+TIA: thanks in advance
+YMMV: your mileage may vary
+</screen
+></para>
+</answer>
+</qandaentry>
+</qandaset>
+</chapter>
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/faq/panel.docbook b/tde-i18n-en_GB/docs/tdebase/khelpcenter/faq/panel.docbook
new file mode 100644
index 00000000000..ad731a7a8ee
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/faq/panel.docbook
@@ -0,0 +1,64 @@
+<!--
+<?xml version="1.0" ?>
+<!DOCTYPE chapter PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN"
+ "dtd/kdex.dtd">
+-->
+
+<chapter id="panel">
+<title
+>The panel</title>
+
+<qandaset>
+<qandaentry>
+<question>
+<para
+>How do I add applications to the &kde; panel (&kicker;)?</para>
+</question>
+<answer>
+<para
+>There are several ways to add an application to the panel, of which the easiest is to right-click on the panel, and from the context menu which appears, select <menuchoice
+><guimenu
+>Panel Menu</guimenu
+><guisubmenu
+>Add</guisubmenu
+><guisubmenu
+>Application Button</guisubmenu
+></menuchoice
+> and then the application for which you want to add a link.</para>
+<para
+>For more ways of adding buttons to the panel, refer to the &kicker; Handbook.</para>
+
+</answer>
+</qandaentry>
+
+<!-- Since I don't know the answer for this in KDE 2.2.1 I have to comment it out -->
+<!--
+<qandaentry>
+<question>
+<para
+>Is it possible to change the <guibutton
+>K</guibutton
+> button of
+the panel to another picture?</para>
+</question
+>/
+<answer>
+<para
+>Look for
+<filename
+>$<envar
+>HOME</envar
+>/.kde/share/apps/kicker/pics/go.png</filename
+> and
+<filename
+>$<envar
+>HOME</envar
+>/.kde/share/apps/kicker/pics/mini/go.png</filename>
+and replace them.  Do not forget to flatten the replacements to one
+layer, or else you will not see anything.  Create the folders if
+they do not already exist.  Then restart &kicker;.</para>
+</answer>
+</qandaentry>
+-->
+</qandaset>
+</chapter>
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/faq/tips.docbook b/tde-i18n-en_GB/docs/tdebase/khelpcenter/faq/tips.docbook
new file mode 100644
index 00000000000..9f7b4e80e26
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/faq/tips.docbook
@@ -0,0 +1,207 @@
+<!--
+<?xml version="1.0" ?>
+<!DOCTYPE chapter PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN"
+ "dtd/kdex.dtd">
+-->
+
+<chapter id="tips">
+<title
+>Useful tips</title>
+
+<qandaset>
+<qandaentry>
+<question>
+<para
+>Reading documentation in &kde;</para>
+</question>
+<answer>
+<para
+>Pop up the <guilabel
+>Run Command</guilabel
+> window (<keycombo action="simul"
+>&Alt;<keycap
+>F2</keycap
+></keycombo
+> by default) and type: <itemizedlist>
+<listitem>
+<para
+><command
+>man:<replaceable
+>command</replaceable
+></command
+> for man pages. It even unpacks on the fly if the man pages are gzipped.</para>
+</listitem>
+
+<listitem>
+<para
+><command
+>info:<replaceable
+>command</replaceable
+></command
+> for info pages.</para>
+</listitem>
+
+<listitem>
+<para
+><command
+>help:<replaceable
+>kdeappname</replaceable
+></command
+> for &kde; application help pages.</para>
+</listitem>
+
+</itemizedlist>
+</para>
+
+<para
+>You can also enter any of these in the <guilabel
+>Location</guilabel
+> text box in &konqueror;.</para>
+<para
+>Or you can use the <application
+>&kde; Help Centre</application
+> if you are using &kde; 2. Simply start the <application
+>&kde; Help Centre</application
+> by clicking on the icon (the blue book with the yellow key) on the toolbar. Once the <application
+>&kde; Help Centre</application
+> has loaded, the window on the left will contain an entry called <guilabel
+>Unix manual pages</guilabel
+>. Click once on this entry, and you can browse through all the installed manual pages on your system.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>Move or resize windows quickly</para>
+</question>
+<answer>
+<para
+>To move a window, use <keycombo action="simul"
+>&Alt;<mousebutton
+>left</mousebutton
+></keycombo
+> mouse button. <keycombo action="simul"
+>&Alt;<mousebutton
+>right</mousebutton
+></keycombo
+> mouse button will resize the window. Last but not least, <keycombo action="simul"
+>&Alt;<mousebutton
+>middle</mousebutton
+></keycombo
+> mouse button raises/lowers the window. The <application
+>&kde; Control Centre</application
+> allows you to change these mouse bindings.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>Killing windows in &kde;</para>
+</question>
+<answer>
+<para
+>There is a standard keybinding (<keycombo action="simul"
+>&Ctrl;&Alt;&Esc;</keycombo
+>) that gives you a skull &amp; crossbones cursor. Click that cursor on a window to kill it. The keybindings are viewable/changeable from the <application
+>&kde; Control Centre</application
+>. <caution
+><para
+>Using this option kills the program forcibly. Data may be lost, and some processes related to the program may remain active. Use only as a last resort.</para
+></caution>
+<!-- fixme: use only if necessary; processes might remain --></para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>What if something is so wrong that I ca not even get the skull &amp; crossbones cursor? How do I get out of a total lockup?</para>
+</question>
+<answer>
+<para
+>These kind of locks tend to occur when an application locks up while it has a so called <quote
+>mouse/keyboard grab</quote
+>. When that happens you can try to select a virtual text console with <keycombo action="simul"
+>&Ctrl;&Alt;<keycap
+>F1</keycap
+></keycombo
+> and login. With the following command you will get a list of all running processes:</para>
+
+<screen
+><userinput
+>        <command
+>ps</command
+> <option
+>-aux</option
+> | <command
+>more</command
+></userinput
+></screen>
+
+<para
+>By killing the process that has the mousegrab, your desktop will come to life again. Unfortunately you ca not see which process that is, so you will have to find out through trial and error. To kill a process use:</para>
+
+<screen
+><userinput
+>        <command
+>kill</command
+> <option
+>-9</option
+> <replaceable
+>pid</replaceable
+></userinput
+></screen>
+
+<para
+>Here <replaceable
+>pid</replaceable
+> is the process id of the process, which is the first number on each line reported by <command
+>ps</command
+> <option
+>-aux</option
+>.</para>
+
+<para
+>You can switch back to the desktop with <keycombo action="simul"
+>&Ctrl;&Alt;<keycap
+>F7</keycap
+></keycombo
+> (or <keycap
+>F8</keycap
+> through <keycap
+>F9</keycap
+> depending on your operating system) to see if things work again. When you press <keycombo action="simul"
+>&Alt;<keycap
+>Tab</keycap
+></keycombo
+> you should get a response from the window manager. If not, you need to get back to the text console and try to kill another process.</para>
+
+<para
+>Good candidates to kill are: the application you were working with, &kicker;, &klipper; and &kdesktop;.</para>
+</answer>
+</qandaentry>
+
+<!-- fixme: how to do in KDE2.x
+<qandaentry>
+<question>
+<para
+>Switching window managers on the fly in &kde; 1.x</para>
+</question>
+<answer>
+<para
+>If you want to switch your window manager on the fly, type the
+following into a terminal window: <command
+>kwmcom
+go:<replaceable
+>blackbox</replaceable
+></command
+>.  This switches to
+Blackbox, but you can substitute any window manager you like.</para>
+</answer>
+</qandaentry>
+-->
+
+</qandaset>
+</chapter>
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/faq/winmng.docbook b/tde-i18n-en_GB/docs/tdebase/khelpcenter/faq/winmng.docbook
new file mode 100644
index 00000000000..4c1fd830618
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/faq/winmng.docbook
@@ -0,0 +1,129 @@
+<!--
+<?xml version="1.0" ?>
+<!DOCTYPE chapter PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN"
+ "dtd/kdex.dtd">
+-->
+
+
+
+<chapter id="windowmanager">
+<title
+>The window manager</title>
+
+<para
+>The default window manager provided by &kde; is the K Window Manager (&twin;). Please read <quote
+>The K Window Manager Handbook</quote
+> (which should be accessible from the <application
+>&kde; Help Centre</application
+>) for usage information.</para>
+
+<qandaset>
+<qandaentry>
+<question>
+<para
+>Are there keyboard shortcuts for &twin; operations?</para>
+</question>
+<answer>
+<para
+>Yes. Please refer to "The K Window Manager Handbook" for the list of shortcuts available.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>Can I define my own set of keyboard shortcuts?</para>
+</question>
+<answer>
+<para
+>Yes. Launch the <application
+>&kde; Control Centre</application
+> and select <menuchoice
+><guimenu
+>Regional &amp; Accessibility</guimenu
+><guimenuitem
+>Keyboard Shortcuts</guimenuitem
+></menuchoice
+> to configure window manager bindings like maximising windows, &etc;. </para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>When I "iconify" a window, it disappears. Where does it go?</para>
+</question>
+<answer>
+<para
+>With many &X-Window; &GUI;s, the minimise 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 a few ways to access <quote
+>disappeared</quote
+> windows:</para>
+<itemizedlist>
+<listitem>
+<para
+>If you are running the taskbar part of &kicker;, you can choose to have a list of tasks displayed on your desktop. Iconified tasks will have their names displayed in grey.</para>
+</listitem>
+<listitem>
+<para
+>If you click the &MMB; on the root window (&ie;, the background of the desktop), &twin; will give you a list of all available tasks.</para>
+</listitem>
+</itemizedlist>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>How do I maximise windows only vertically or horizontally?</para>
+</question>
+<answer>
+<para
+>Provided your window is not already maximised, clicking on the maximise button with the &LMB;/&MMB;/&RMB; will maximise fully/vertically/horizontally respectively.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para
+>What is <quote
+>shading</quote
+> a window?</para>
+</question>
+<answer>
+<para
+>By <quote
+>shading</quote
+> a window we mean <quote
+>rolling up</quote
+> the window leaving just the title bar visible. You can do this by double clicking on the window title bar.</para>
+</answer>
+</qandaentry>
+
+<!-- Not sure this is still applicable
+<qandaentry>
+<question>
+<para
+>Is it possible to have FVWM2-like shadow frameworks for the
+placement of windows?</para>
+</question>
+<answer>
+<para
+>Yes.  Run <application
+>&kde; Control Center</application
+> and select <guimenu
+>Look and Feel</guimenu>
+followed by <guisubmenu
+>Window Behavior</guisubmenu
+> and finally
+<guimenuitem
+>Advanced</guimenuitem
+>.  There is a dialog option that
+allows you to set the placement policy you want.</para>
+</answer>
+</qandaentry>
+-->
+</qandaset>
+</chapter>
+
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/glossary/Makefile.am b/tde-i18n-en_GB/docs/tdebase/khelpcenter/glossary/Makefile.am
new file mode 100644
index 00000000000..ff629e8b913
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/glossary/Makefile.am
@@ -0,0 +1,4 @@
+KDE_LANG = en_GB
+SUBDIRS = $(AUTODIRS)
+KDE_DOCS = khelpcenter/glossary
+KDE_MANS = AUTO
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/glossary/Makefile.in b/tde-i18n-en_GB/docs/tdebase/khelpcenter/glossary/Makefile.in
new file mode 100644
index 00000000000..606f0fbf678
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/glossary/Makefile.in
@@ -0,0 +1,635 @@
+# Makefile.in generated by automake 1.10.1 from Makefile.am.
+# KDE tags expanded automatically by am_edit - $Revision: 483858 $ 
+# @configure_input@
+
+# Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002,
+# 2003, 2004, 2005, 2006, 2007, 2008  Free Software Foundation, Inc.
+# This Makefile.in is free software; the Free Software Foundation
+# gives unlimited permission to copy and/or distribute it,
+# with or without modifications, as long as this notice is preserved.
+
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY, to the extent permitted by law; without
+# even the implied warranty of MERCHANTABILITY or FITNESS FOR A
+# PARTICULAR PURPOSE.
+
+@SET_MAKE@
+VPATH = @srcdir@
+pkgdatadir = $(datadir)/@PACKAGE@
+pkglibdir = $(libdir)/@PACKAGE@
+pkgincludedir = $(includedir)/@PACKAGE@
+am__cd = CDPATH="$${ZSH_VERSION+.}$(PATH_SEPARATOR)" && cd
+install_sh_DATA = $(install_sh) -c -m 644
+install_sh_PROGRAM = $(install_sh) -c
+install_sh_SCRIPT = $(install_sh) -c
+INSTALL_HEADER = $(INSTALL_DATA)
+transform = $(program_transform_name)
+NORMAL_INSTALL = :
+PRE_INSTALL = :
+POST_INSTALL = :
+NORMAL_UNINSTALL = :
+PRE_UNINSTALL = :
+POST_UNINSTALL = :
+subdir = docs/tdebase/khelpcenter/glossary
+DIST_COMMON = $(srcdir)/Makefile.am $(srcdir)/Makefile.in
+ACLOCAL_M4 = $(top_srcdir)/aclocal.m4
+am__aclocal_m4_deps = $(top_srcdir)/acinclude.m4 \
+	$(top_srcdir)/configure.in
+am__configure_deps = $(am__aclocal_m4_deps) $(CONFIGURE_DEPENDENCIES) \
+	$(ACLOCAL_M4)
+mkinstalldirs = $(SHELL) $(top_srcdir)/mkinstalldirs
+CONFIG_HEADER = $(top_builddir)/config.h
+CONFIG_CLEAN_FILES =
+SOURCES =
+DIST_SOURCES =
+#>- RECURSIVE_TARGETS = all-recursive check-recursive dvi-recursive \
+#>- 	html-recursive info-recursive install-data-recursive \
+#>- 	install-dvi-recursive install-exec-recursive \
+#>- 	install-html-recursive install-info-recursive \
+#>- 	install-pdf-recursive install-ps-recursive install-recursive \
+#>- 	installcheck-recursive installdirs-recursive pdf-recursive \
+#>- 	ps-recursive uninstall-recursive
+#>+ 7
+RECURSIVE_TARGETS = all-recursive check-recursive dvi-recursive \
+	html-recursive info-recursive install-data-recursive \
+	install-dvi-recursive install-exec-recursive \
+	install-html-recursive install-info-recursive \
+	install-pdf-recursive install-ps-recursive install-recursive \
+	installcheck-recursive installdirs-recursive pdf-recursive \
+	ps-recursive uninstall-recursive nmcheck-recursive bcheck-recursive
+RECURSIVE_CLEAN_TARGETS = mostlyclean-recursive clean-recursive	\
+  distclean-recursive maintainer-clean-recursive
+ETAGS = etags
+CTAGS = ctags
+DIST_SUBDIRS = $(SUBDIRS)
+#>- DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST)
+#>+ 1
+DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST) $(KDE_DIST)
+ACLOCAL = @ACLOCAL@
+AMTAR = @AMTAR@
+ARTSCCONFIG = @ARTSCCONFIG@
+AUTOCONF = @AUTOCONF@
+AUTODIRS = @AUTODIRS@
+AUTOHEADER = @AUTOHEADER@
+AUTOMAKE = @AUTOMAKE@
+AWK = @AWK@
+CONF_FILES = @CONF_FILES@
+CYGPATH_W = @CYGPATH_W@
+DCOPIDL = @DCOPIDL@
+DCOPIDL2CPP = @DCOPIDL2CPP@
+DCOPIDLNG = @DCOPIDLNG@
+DCOP_DEPENDENCIES = @DCOP_DEPENDENCIES@
+DEFS = @DEFS@
+ECHO_C = @ECHO_C@
+ECHO_N = @ECHO_N@
+ECHO_T = @ECHO_T@
+GMSGFMT = @GMSGFMT@
+INSTALL = @INSTALL@
+INSTALL_DATA = @INSTALL_DATA@
+INSTALL_PROGRAM = @INSTALL_PROGRAM@
+INSTALL_SCRIPT = @INSTALL_SCRIPT@
+INSTALL_STRIP_PROGRAM = @INSTALL_STRIP_PROGRAM@
+KCFG_DEPENDENCIES = @KCFG_DEPENDENCIES@
+KCONFIG_COMPILER = @KCONFIG_COMPILER@
+KDECONFIG = @KDECONFIG@
+KDE_EXTRA_RPATH = @KDE_EXTRA_RPATH@
+KDE_RPATH = @KDE_RPATH@
+KDE_XSL_STYLESHEET = @KDE_XSL_STYLESHEET@
+LIBOBJS = @LIBOBJS@
+LIBS = @LIBS@
+LN_S = @LN_S@
+LTLIBOBJS = @LTLIBOBJS@
+MAKEINFO = @MAKEINFO@
+MAKEKDEWIDGETS = @MAKEKDEWIDGETS@
+MCOPIDL = @MCOPIDL@
+MEINPROC = @MEINPROC@
+MKDIR_P = @MKDIR_P@
+MSGFMT = @MSGFMT@
+PACKAGE = @PACKAGE@
+PACKAGE_BUGREPORT = @PACKAGE_BUGREPORT@
+PACKAGE_NAME = @PACKAGE_NAME@
+PACKAGE_STRING = @PACKAGE_STRING@
+PACKAGE_TARNAME = @PACKAGE_TARNAME@
+PACKAGE_VERSION = @PACKAGE_VERSION@
+PATH_SEPARATOR = @PATH_SEPARATOR@
+SET_MAKE = @SET_MAKE@
+SHELL = @SHELL@
+STRIP = @STRIP@
+TOPSUBDIRS = @TOPSUBDIRS@
+VERSION = @VERSION@
+XGETTEXT = @XGETTEXT@
+XMLLINT = @XMLLINT@
+X_RPATH = @X_RPATH@
+abs_builddir = @abs_builddir@
+abs_srcdir = @abs_srcdir@
+abs_top_builddir = @abs_top_builddir@
+abs_top_srcdir = @abs_top_srcdir@
+am__leading_dot = @am__leading_dot@
+am__tar = @am__tar@
+am__untar = @am__untar@
+#>- bindir = @bindir@
+#>+ 2
+DEPDIR = .deps
+bindir = @bindir@
+build_alias = @build_alias@
+builddir = @builddir@
+datadir = @datadir@
+datarootdir = @datarootdir@
+docdir = @docdir@
+dvidir = @dvidir@
+exec_prefix = @exec_prefix@
+host_alias = @host_alias@
+htmldir = @htmldir@
+includedir = @includedir@
+infodir = @infodir@
+install_sh = @install_sh@
+kde_appsdir = @kde_appsdir@
+kde_bindir = @kde_bindir@
+kde_confdir = @kde_confdir@
+kde_datadir = @kde_datadir@
+kde_htmldir = @kde_htmldir@
+kde_icondir = @kde_icondir@
+kde_kcfgdir = @kde_kcfgdir@
+kde_libs_htmldir = @kde_libs_htmldir@
+kde_libs_prefix = @kde_libs_prefix@
+kde_locale = @kde_locale@
+kde_mimedir = @kde_mimedir@
+kde_moduledir = @kde_moduledir@
+kde_servicesdir = @kde_servicesdir@
+kde_servicetypesdir = @kde_servicetypesdir@
+kde_sounddir = @kde_sounddir@
+kde_styledir = @kde_styledir@
+kde_templatesdir = @kde_templatesdir@
+kde_wallpaperdir = @kde_wallpaperdir@
+kde_widgetdir = @kde_widgetdir@
+tdeinitdir = @tdeinitdir@
+libdir = @libdir@
+libexecdir = @libexecdir@
+localedir = @localedir@
+localstatedir = @localstatedir@
+mandir = @mandir@
+mkdir_p = @mkdir_p@
+oldincludedir = @oldincludedir@
+pdfdir = @pdfdir@
+prefix = @prefix@
+program_transform_name = @program_transform_name@
+psdir = @psdir@
+sbindir = @sbindir@
+sharedstatedir = @sharedstatedir@
+srcdir = @srcdir@
+sysconfdir = @sysconfdir@
+target_alias = @target_alias@
+top_builddir = @top_builddir@
+top_srcdir = @top_srcdir@
+xdg_appsdir = @xdg_appsdir@
+xdg_directorydir = @xdg_directorydir@
+xdg_menudir = @xdg_menudir@
+KDE_LANG = en_GB
+#>- SUBDIRS = $(AUTODIRS)
+#>+ 1
+SUBDIRS =.
+KDE_DOCS = khelpcenter/glossary
+KDE_MANS = AUTO
+#>- all: all-recursive
+#>+ 1
+all: docs-am  all-recursive
+
+.SUFFIXES:
+$(srcdir)/Makefile.in:  $(srcdir)/Makefile.am  $(am__configure_deps)
+#>- 	@for dep in $?; do \
+#>- 	  case '$(am__configure_deps)' in \
+#>- 	    *$$dep*) \
+#>- 	      cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh \
+#>- 		&& exit 0; \
+#>- 	      exit 1;; \
+#>- 	  esac; \
+#>- 	done; \
+#>- 	echo ' cd $(top_srcdir) && $(AUTOMAKE) --gnu  docs/tdebase/khelpcenter/glossary/Makefile'; \
+#>- 	cd $(top_srcdir) && \
+#>- 	  $(AUTOMAKE) --gnu  docs/tdebase/khelpcenter/glossary/Makefile
+#>+ 12
+	@for dep in $?; do \
+	  case '$(am__configure_deps)' in \
+	    *$$dep*) \
+	      cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh \
+		&& exit 0; \
+	      exit 1;; \
+	  esac; \
+	done; \
+	echo ' cd $(top_srcdir) && $(AUTOMAKE) --gnu  docs/tdebase/khelpcenter/glossary/Makefile'; \
+	cd $(top_srcdir) && \
+	  $(AUTOMAKE) --gnu  docs/tdebase/khelpcenter/glossary/Makefile
+	cd $(top_srcdir) && perl ../scripts/admin/am_edit -p../scripts/admin docs/tdebase/khelpcenter/glossary/Makefile.in
+.PRECIOUS: Makefile
+Makefile: $(srcdir)/Makefile.in $(top_builddir)/config.status
+	@case '$?' in \
+	  *config.status*) \
+	    cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh;; \
+	  *) \
+	    echo ' cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__depfiles_maybe)'; \
+	    cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__depfiles_maybe);; \
+	esac;
+
+$(top_builddir)/config.status: $(top_srcdir)/configure $(CONFIG_STATUS_DEPENDENCIES)
+	cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
+
+$(top_srcdir)/configure:  $(am__configure_deps)
+	cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
+$(ACLOCAL_M4):  $(am__aclocal_m4_deps)
+	cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
+
+# This directory's subdirectories are mostly independent; you can cd
+# into them and run `make' without going through this Makefile.
+# To change the values of `make' variables: instead of editing Makefiles,
+# (1) if the variable is set in `config.status', edit `config.status'
+#     (which will cause the Makefiles to be regenerated when you run `make');
+# (2) otherwise, pass the desired values on the `make' command line.
+$(RECURSIVE_TARGETS):
+	@failcom='exit 1'; \
+	for f in x $$MAKEFLAGS; do \
+	  case $$f in \
+	    *=* | --[!k]*);; \
+	    *k*) failcom='fail=yes';; \
+	  esac; \
+	done; \
+	dot_seen=no; \
+	target=`echo $@ | sed s/-recursive//`; \
+	list='$(SUBDIRS)'; for subdir in $$list; do \
+	  echo "Making $$target in $$subdir"; \
+	  if test "$$subdir" = "."; then \
+	    dot_seen=yes; \
+	    local_target="$$target-am"; \
+	  else \
+	    local_target="$$target"; \
+	  fi; \
+	  (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS) $$local_target) \
+	  || eval $$failcom; \
+	done; \
+	if test "$$dot_seen" = "no"; then \
+	  $(MAKE) $(AM_MAKEFLAGS) "$$target-am" || exit 1; \
+	fi; test -z "$$fail"
+
+$(RECURSIVE_CLEAN_TARGETS):
+	@failcom='exit 1'; \
+	for f in x $$MAKEFLAGS; do \
+	  case $$f in \
+	    *=* | --[!k]*);; \
+	    *k*) failcom='fail=yes';; \
+	  esac; \
+	done; \
+	dot_seen=no; \
+	case "$@" in \
+	  distclean-* | maintainer-clean-*) list='$(DIST_SUBDIRS)' ;; \
+	  *) list='$(SUBDIRS)' ;; \
+	esac; \
+	rev=''; for subdir in $$list; do \
+	  if test "$$subdir" = "."; then :; else \
+	    rev="$$subdir $$rev"; \
+	  fi; \
+	done; \
+	rev="$$rev ."; \
+	target=`echo $@ | sed s/-recursive//`; \
+	for subdir in $$rev; do \
+	  echo "Making $$target in $$subdir"; \
+	  if test "$$subdir" = "."; then \
+	    local_target="$$target-am"; \
+	  else \
+	    local_target="$$target"; \
+	  fi; \
+	  (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS) $$local_target) \
+	  || eval $$failcom; \
+	done && test -z "$$fail"
+tags-recursive:
+	list='$(SUBDIRS)'; for subdir in $$list; do \
+	  test "$$subdir" = . || (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS) tags); \
+	done
+ctags-recursive:
+	list='$(SUBDIRS)'; for subdir in $$list; do \
+	  test "$$subdir" = . || (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS) ctags); \
+	done
+
+ID: $(HEADERS) $(SOURCES) $(LISP) $(TAGS_FILES)
+	list='$(SOURCES) $(HEADERS) $(LISP) $(TAGS_FILES)'; \
+	unique=`for i in $$list; do \
+	    if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
+	  done | \
+	  $(AWK) '{ files[$$0] = 1; nonemtpy = 1; } \
+	      END { if (nonempty) { for (i in files) print i; }; }'`; \
+	mkid -fID $$unique
+tags: TAGS
+
+TAGS: tags-recursive $(HEADERS) $(SOURCES)  $(TAGS_DEPENDENCIES) \
+		$(TAGS_FILES) $(LISP)
+	tags=; \
+	here=`pwd`; \
+	if ($(ETAGS) --etags-include --version) >/dev/null 2>&1; then \
+	  include_option=--etags-include; \
+	  empty_fix=.; \
+	else \
+	  include_option=--include; \
+	  empty_fix=; \
+	fi; \
+	list='$(SUBDIRS)'; for subdir in $$list; do \
+	  if test "$$subdir" = .; then :; else \
+	    test ! -f $$subdir/TAGS || \
+	      tags="$$tags $$include_option=$$here/$$subdir/TAGS"; \
+	  fi; \
+	done; \
+	list='$(SOURCES) $(HEADERS)  $(LISP) $(TAGS_FILES)'; \
+	unique=`for i in $$list; do \
+	    if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
+	  done | \
+	  $(AWK) '{ files[$$0] = 1; nonempty = 1; } \
+	      END { if (nonempty) { for (i in files) print i; }; }'`; \
+	if test -z "$(ETAGS_ARGS)$$tags$$unique"; then :; else \
+	  test -n "$$unique" || unique=$$empty_fix; \
+	  $(ETAGS) $(ETAGSFLAGS) $(AM_ETAGSFLAGS) $(ETAGS_ARGS) \
+	    $$tags $$unique; \
+	fi
+ctags: CTAGS
+CTAGS: ctags-recursive $(HEADERS) $(SOURCES)  $(TAGS_DEPENDENCIES) \
+		$(TAGS_FILES) $(LISP)
+	tags=; \
+	list='$(SOURCES) $(HEADERS)  $(LISP) $(TAGS_FILES)'; \
+	unique=`for i in $$list; do \
+	    if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
+	  done | \
+	  $(AWK) '{ files[$$0] = 1; nonempty = 1; } \
+	      END { if (nonempty) { for (i in files) print i; }; }'`; \
+	test -z "$(CTAGS_ARGS)$$tags$$unique" \
+	  || $(CTAGS) $(CTAGSFLAGS) $(AM_CTAGSFLAGS) $(CTAGS_ARGS) \
+	     $$tags $$unique
+
+GTAGS:
+	here=`$(am__cd) $(top_builddir) && pwd` \
+	  && cd $(top_srcdir) \
+	  && gtags -i $(GTAGS_ARGS) $$here
+
+distclean-tags:
+	-rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
+
+#>- distdir: $(DISTFILES)
+#>+ 1
+distdir: distdir-nls  $(DISTFILES)
+	@srcdirstrip=`echo "$(srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \
+	topsrcdirstrip=`echo "$(top_srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \
+	list='$(DISTFILES)'; \
+	  dist_files=`for file in $$list; do echo $$file; done | \
+	  sed -e "s|^$$srcdirstrip/||;t" \
+	      -e "s|^$$topsrcdirstrip/|$(top_builddir)/|;t"`; \
+	case $$dist_files in \
+	  */*) $(MKDIR_P) `echo "$$dist_files" | \
+			   sed '/\//!d;s|^|$(distdir)/|;s,/[^/]*$$,,' | \
+			   sort -u` ;; \
+	esac; \
+	for file in $$dist_files; do \
+	  if test -f $$file || test -d $$file; then d=.; else d=$(srcdir); fi; \
+	  if test -d $$d/$$file; then \
+	    dir=`echo "/$$file" | sed -e 's,/[^/]*$$,,'`; \
+	    if test -d $(srcdir)/$$file && test $$d != $(srcdir); then \
+	      cp -pR $(srcdir)/$$file $(distdir)$$dir || exit 1; \
+	    fi; \
+	    cp -pR $$d/$$file $(distdir)$$dir || exit 1; \
+	  else \
+	    test -f $(distdir)/$$file \
+	    || cp -p $$d/$$file $(distdir)/$$file \
+	    || exit 1; \
+	  fi; \
+	done
+	list='$(DIST_SUBDIRS)'; for subdir in $$list; do \
+	  if test "$$subdir" = .; then :; else \
+	    test -d "$(distdir)/$$subdir" \
+	    || $(MKDIR_P) "$(distdir)/$$subdir" \
+	    || exit 1; \
+	    distdir=`$(am__cd) $(distdir) && pwd`; \
+	    top_distdir=`$(am__cd) $(top_distdir) && pwd`; \
+	    (cd $$subdir && \
+	      $(MAKE) $(AM_MAKEFLAGS) \
+	        top_distdir="$$top_distdir" \
+	        distdir="$$distdir/$$subdir" \
+		am__remove_distdir=: \
+		am__skip_length_check=: \
+	        distdir) \
+	      || exit 1; \
+	  fi; \
+	done
+check-am: all-am
+check: check-recursive
+all-am: Makefile
+installdirs: installdirs-recursive
+installdirs-am:
+install: install-recursive
+install-exec: install-exec-recursive
+install-data: install-data-recursive
+#>- uninstall: uninstall-recursive
+#>+ 1
+uninstall: uninstall-docs uninstall-nls  uninstall-recursive
+
+install-am: all-am
+	@$(MAKE) $(AM_MAKEFLAGS) install-exec-am install-data-am
+
+installcheck: installcheck-recursive
+install-strip:
+	$(MAKE) $(AM_MAKEFLAGS) INSTALL_PROGRAM="$(INSTALL_STRIP_PROGRAM)" \
+	  install_sh_PROGRAM="$(INSTALL_STRIP_PROGRAM)" INSTALL_STRIP_FLAG=-s \
+	  `test -z '$(STRIP)' || \
+	    echo "INSTALL_PROGRAM_ENV=STRIPPROG='$(STRIP)'"` install
+mostlyclean-generic:
+
+clean-generic:
+
+distclean-generic:
+	-test -z "$(CONFIG_CLEAN_FILES)" || rm -f $(CONFIG_CLEAN_FILES)
+
+maintainer-clean-generic:
+	@echo "This command is intended for maintainers to use"
+	@echo "it deletes files that may require special tools to rebuild."
+#>- clean: clean-recursive
+#>+ 1
+clean: kde-rpo-clean  clean-recursive
+
+#>- clean-am: clean-generic mostlyclean-am
+#>+ 1
+clean-am: clean-docs clean-bcheck  clean-generic mostlyclean-am
+
+distclean: distclean-recursive
+	-rm -f Makefile
+distclean-am: clean-am distclean-generic distclean-tags
+
+dvi: dvi-recursive
+
+dvi-am:
+
+html: html-recursive
+
+info: info-recursive
+
+info-am:
+
+#>- install-data-am:
+#>+ 1
+install-data-am: install-docs install-nls 
+
+install-dvi: install-dvi-recursive
+
+install-exec-am:
+
+install-html: install-html-recursive
+
+install-info: install-info-recursive
+
+install-man:
+
+install-pdf: install-pdf-recursive
+
+install-ps: install-ps-recursive
+
+installcheck-am:
+
+maintainer-clean: maintainer-clean-recursive
+	-rm -f Makefile
+maintainer-clean-am: distclean-am maintainer-clean-generic
+
+mostlyclean: mostlyclean-recursive
+
+mostlyclean-am: mostlyclean-generic
+
+pdf: pdf-recursive
+
+pdf-am:
+
+ps: ps-recursive
+
+ps-am:
+
+uninstall-am:
+
+.MAKE: $(RECURSIVE_CLEAN_TARGETS) $(RECURSIVE_TARGETS) install-am \
+	install-strip
+
+.PHONY: $(RECURSIVE_CLEAN_TARGETS) $(RECURSIVE_TARGETS) CTAGS GTAGS \
+	all all-am check check-am clean clean-generic ctags \
+	ctags-recursive distclean distclean-generic distclean-tags \
+	distdir dvi dvi-am html html-am info info-am install \
+	install-am install-data install-data-am install-dvi \
+	install-dvi-am install-exec install-exec-am install-html \
+	install-html-am install-info install-info-am install-man \
+	install-pdf install-pdf-am install-ps install-ps-am \
+	install-strip installcheck installcheck-am installdirs \
+	installdirs-am maintainer-clean maintainer-clean-generic \
+	mostlyclean mostlyclean-generic pdf pdf-am ps ps-am tags \
+	tags-recursive uninstall uninstall-am
+
+# Tell versions [3.59,3.63) of GNU make to not export all variables.
+# Otherwise a system limit (for SysV at least) may be exceeded.
+.NOEXPORT:
+
+#>+ 2
+KDE_DIST=tdeprintingglossary.docbook Makefile.in index.docbook Makefile.am index.cache.bz2 
+
+#>+ 24
+index.cache.bz2: $(srcdir)/index.docbook $(KDE_XSL_STYLESHEET) index.docbook tdeprintingglossary.docbook 
+	@if test -n "$(MEINPROC)"; then echo $(MEINPROC) --check --cache index.cache.bz2 $(srcdir)/index.docbook; $(MEINPROC) --check --cache index.cache.bz2 $(srcdir)/index.docbook; fi
+
+docs-am: index.cache.bz2
+
+install-docs: docs-am install-nls
+	$(mkinstalldirs) $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/glossary
+	@if test -f index.cache.bz2; then \
+	echo $(INSTALL_DATA) index.cache.bz2 $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/glossary/; \
+	$(INSTALL_DATA) index.cache.bz2 $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/glossary/; \
+	elif test -f  $(srcdir)/index.cache.bz2; then \
+	echo $(INSTALL_DATA) $(srcdir)/index.cache.bz2 $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/glossary/; \
+	$(INSTALL_DATA) $(srcdir)/index.cache.bz2 $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/glossary/; \
+	fi
+	-rm -f $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/glossary/common
+	$(LN_S) $(kde_libs_htmldir)/$(KDE_LANG)/common $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/glossary/common
+
+uninstall-docs:
+	-rm -rf $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/glossary
+
+clean-docs:
+	-rm -f index.cache.bz2
+
+
+#>+ 13
+install-nls:
+	$(mkinstalldirs) $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/glossary
+	@for base in index.docbook tdeprintingglossary.docbook ; do \
+	  echo $(INSTALL_DATA) $$base $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/glossary/$$base ;\
+	  $(INSTALL_DATA) $(srcdir)/$$base $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/glossary/$$base ;\
+	done
+
+uninstall-nls:
+	for base in index.docbook tdeprintingglossary.docbook ; do \
+	  rm -f $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/glossary/$$base ;\
+	done
+
+
+#>+ 5
+distdir-nls:
+	for file in index.docbook tdeprintingglossary.docbook ; do \
+	  cp $(srcdir)/$$file $(distdir); \
+	done
+
+#>+ 15
+force-reedit:
+		@for dep in $?; do \
+	  case '$(am__configure_deps)' in \
+	    *$$dep*) \
+	      cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh \
+		&& exit 0; \
+	      exit 1;; \
+	  esac; \
+	done; \
+	echo ' cd $(top_srcdir) && $(AUTOMAKE) --gnu  docs/tdebase/khelpcenter/glossary/Makefile'; \
+	cd $(top_srcdir) && \
+	  $(AUTOMAKE) --gnu  docs/tdebase/khelpcenter/glossary/Makefile
+	cd $(top_srcdir) && perl ../scripts/admin/am_edit -p../scripts/admin docs/tdebase/khelpcenter/glossary/Makefile.in
+
+
+#>+ 21
+clean-bcheck: 
+	rm -f *.bchecktest.cc *.bchecktest.cc.class a.out
+
+bcheck: bcheck-recursive
+
+bcheck-am:
+	@for i in ; do \
+	    if test $(srcdir)/$$i -nt $$i.bchecktest.cc; then \
+	        echo "int main() {return 0;}" > $$i.bchecktest.cc ; \
+	        echo "#include \"$$i\"" >> $$i.bchecktest.cc ; \
+	        echo "$$i"; \
+	        if ! $(CXX) $(DEFS) -I. -I$(srcdir) -I$(top_builddir) $(INCLUDES) $(AM_CPPFLAGS) $(CPPFLAGS) $(CXXFLAGS) $(KDE_CXXFLAGS)  --dump-class-hierarchy -c $$i.bchecktest.cc; then \
+	            rm -f $$i.bchecktest.cc; exit 1; \
+	        fi ; \
+	        echo "" >> $$i.bchecktest.cc.class; \
+	        perl $(top_srcdir)/admin/bcheck.pl $$i.bchecktest.cc.class || { rm -f $$i.bchecktest.cc; exit 1; }; \
+	        rm -f a.out; \
+	    fi ; \
+	done
+
+
+#>+ 3
+final:
+	$(MAKE) all-am
+
+#>+ 3
+final-install:
+	$(MAKE) install-am
+
+#>+ 3
+no-final:
+	$(MAKE) all-am
+
+#>+ 3
+no-final-install:
+	$(MAKE) install-am
+
+#>+ 3
+kde-rpo-clean:
+	-rm -f *.rpo
+
+#>+ 3
+nmcheck: 
+nmcheck-am: nmcheck
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/glossary/index.cache.bz2 b/tde-i18n-en_GB/docs/tdebase/khelpcenter/glossary/index.cache.bz2
new file mode 100644
index 00000000000..49b5b277981
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/glossary/index.cache.bz2
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/glossary/index.docbook b/tde-i18n-en_GB/docs/tdebase/khelpcenter/glossary/index.docbook
new file mode 100644
index 00000000000..719ae126ef3
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/glossary/index.docbook
@@ -0,0 +1,467 @@
+<?xml version="1.0" ?>
+<!DOCTYPE glossary PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" "dtd/kdex.dtd" [
+<!ENTITY % addindex "IGNORE">
+<!ENTITY % British-English "INCLUDE">
+<!ENTITY glossary-tdeprinting SYSTEM "tdeprintingglossary.docbook">
+
+
+]>
+
+
+<glossary id="glossary"
+>&glossary-tdeprinting; <glossdiv id="glossdiv-technologies">
+		<title
+>Technologies</title>
+		<glossentry id="gloss-ioslave">
+			<glossterm
+><acronym
+>IO</acronym
+> Slave</glossterm>
+			<glossdef
+><para
+><acronym
+>IO</acronym
+> Slaves enable &kde; applications to access remote resources as easily as local resources (making them <quote
+>network transparent</quote
+>). Remote resources (&eg; files) might be stored on <acronym
+>SMB</acronym
+> shares or similar.</para>
+<glossseealso otherterm="gloss-smb"
+><acronym
+>SMB</acronym
+></glossseealso
+> <glossseealso otherterm="gloss-kde"
+>&kde;</glossseealso
+> </glossdef>
+		</glossentry>
+		<glossentry id="gloss-kio">
+			<glossterm
+><acronym
+>KIO</acronym
+></glossterm>
+			<glossdef
+><para
+>The &kde; Input/Output system which makes use of so-called <quote
+><acronym
+>IO</acronym
+> Slaves</quote
+>.</para>
+<glossseealso otherterm="gloss-ioslave"
+><acronym
+>IO</acronym
+> Slave</glossseealso
+> <glossseealso otherterm="gloss-kde"
+>&kde;</glossseealso
+> </glossdef>
+		</glossentry>
+		<glossentry id="gloss-kparts">
+			<glossterm
+>KParts</glossterm>
+			<glossdef
+><para
+>KParts is an embedding technology which allows &kde; applications to embed other &kde; applications. For example, the text view used by &konqueror; is a KPart.</para>
+				<glossseealso otherterm="gloss-konqueror"
+>&konqueror;</glossseealso>
+			</glossdef>
+		</glossentry>
+		<glossentry id="gloss-ksycoca">
+			<glossterm
+><acronym
+>KSycoca</acronym
+></glossterm>
+			<glossdef
+><para
+><acronym
+>KSycoca</acronym
+> (&kde; <emphasis
+>Sy</emphasis
+>stem <emphasis
+>Co</emphasis
+>nfiguration <emphasis
+>Ca</emphasis
+>che) is a configuration cache which, for example, guarantees fast access to the menu entries.</para>
+				<glossseealso 
+otherterm="gloss-kbuildsycoca"
+><application
+>KBuildSycoca</application
+></glossseealso>
+			</glossdef>
+		</glossentry>
+	</glossdiv>
+	
+	<glossdiv id="glossdiv-xfree86">
+		<title
+>XFree86</title>
+		<glossentry id="gloss-antialiasing">
+			<glossterm
+>Antialiasing</glossterm>
+			<glossdef
+><para
+>If mentioned in context with &kde;, antialiasing often means the smoothing of the fonts visible on the screen. &Qt; version 2.3.0 or higher used together with XFree86 4.x makes this possible under &kde; as well.</para>
+<glossseealso otherterm="gloss-kde"
+>&kde;</glossseealso
+> <glossseealso otherterm="gloss-qt"
+>&Qt;</glossseealso
+> </glossdef>
+		</glossentry>
+		<glossentry id="gloss-xserver">
+			<glossterm
+>&X-Server;</glossterm>
+			<glossdef
+><para
+>The &X-Server; represents a basic layer upon which the various &GUI;s like &kde; are built. It manages the basic mouse and keyboard input (from the local host as well as from remote hosts) and provides elementary graphic routines to draw rectangles and other primitives.</para>
+<glossseealso otherterm="gloss-kde"
+>&kde;</glossseealso
+> <glossseealso otherterm="gloss-gui"
+>&GUI;</glossseealso
+> </glossdef>
+		</glossentry>
+	</glossdiv>
+
+	<glossdiv id="glossdiv-applications">
+		<title
+>Applications</title>
+		<glossentry id="gloss-kbuildsycoca">
+			<glossterm
+><application
+>KBuildSycoca</application
+></glossterm>
+			<glossdef
+><para
+><application
+>KBuildSycoca</application
+> is a command line program and regenerates the so-called <acronym
+>KSycoca</acronym
+>. This is useful, for example, if some or all modules in &kcontrol; are missing.</para>
+<glossseealso otherterm="gloss-ksycoca"
+><acronym
+>KSycoca</acronym
+></glossseealso
+> <glossseealso otherterm="gloss-kcontrol"
+>&kcontrol;</glossseealso
+> </glossdef>
+		</glossentry>
+		<glossentry id="gloss-kcontrol">
+			<glossterm
+>&kcontrol;</glossterm>
+			<glossdef
+><para
+>This is the project and filename of the &kde; control centre. &kcontrol; allows you to customise virtually every configuration option of &kde;.</para>
+				<glossseealso otherterm="gloss-kde"
+>&kde;</glossseealso>
+			</glossdef>
+		</glossentry>
+		<glossentry id="gloss-kicker">
+			<glossterm
+>&kicker;</glossterm>
+			<glossdef
+><para
+>&kicker; is the nickname as well as project name of the &kde; panel.</para>
+<glossseealso otherterm="gloss-kde"
+>&kde;</glossseealso
+> <glossseealso otherterm="gloss-panel"
+>Panel</glossseealso
+> </glossdef>
+		</glossentry>
+		<glossentry id="gloss-konqueror">
+			<glossterm
+>&konqueror;</glossterm>
+			<glossdef
+><para
+>&konqueror; is a filemanager, web browser, picture viewer and more, and a core part of the &kde; project. You can find more information about &konqueror; at <ulink url="http://www.konqueror.org"
+>www.konqueror.org</ulink
+>.</para>
+				<glossseealso otherterm="gloss-kde"
+>&kde;</glossseealso>
+			</glossdef>
+		</glossentry>
+		<glossentry id="gloss-ksirc">
+			<glossterm
+>&ksirc;</glossterm>
+			<glossdef
+><para
+>&ksirc; is the default <acronym
+>IRC</acronym
+> client, which is shipped with &kde;. You can use &ksirc; to chat with anyone on an <acronym
+>IRC</acronym
+> network.</para>
+				<glossseealso otherterm="gloss-irc"
+><acronym
+>IRC</acronym
+></glossseealso>
+			</glossdef>
+		</glossentry
+>			 	
+	</glossdiv>
+	
+	<glossdiv id="glossdiv-desktop-terminology">
+		<title
+>Desktop Terminology</title>
+		<glossentry id="gloss-draganddrop">
+			<glossterm
+>Drag and Drop</glossterm>
+			<glossdef
+><para
+>This concept tries to replace many actions like copying files from one place to another by a certain mouse movement, &eg; clicking on an icon in a &konqueror; window, moving the mouse to another window while keeping the mouse button pressed, and releasing the mouse button (<quote
+>dropping</quote
+> the object) copies files.</para>
+				<glossseealso otherterm="gloss-konqueror"
+>&konqueror;</glossseealso>
+			</glossdef>
+		</glossentry>
+		<glossentry id="gloss-gui">
+			<glossterm
+>&GUI;</glossterm>
+			<glossdef
+><para
+>Abbreviation for <emphasis
+>G</emphasis
+>raphical <emphasis
+>U</emphasis
+>ser <emphasis
+>I</emphasis
+>nterface. Every desktop environment (like &kde;) is a &GUI;. Most &GUI;s feature mouse support and/or windows to manage the programs.</para>
+				<glossseealso otherterm="gloss-kde"
+>&kde;</glossseealso>
+			</glossdef>
+		</glossentry>
+		<glossentry id="gloss-kde">
+			<glossterm
+>&kde;</glossterm>
+			<glossdef
+><para
+>Abbreviation for <quote
+>K Desktop Environment</quote
+>, a leading &GUI; for &UNIX;-based systems. You can find more detailled information at <ulink url="http://www.kde.org"
+>www.kde.org</ulink
+>.</para>
+				<glossseealso otherterm="gloss-gui"
+>&GUI;</glossseealso>
+			</glossdef>
+		</glossentry>
+		<glossentry id="gloss-gnome">
+			<glossterm
+><acronym
+>GNOME</acronym
+></glossterm>
+			<glossdef>
+				<para
+><emphasis
+>G</emphasis
+>NU <emphasis
+>N</emphasis
+>etwork <emphasis
+>O</emphasis
+>bject <emphasis
+>M</emphasis
+>odel <emphasis
+>E</emphasis
+>nvironment, one of the leading &UNIX; &GUI;s.</para>
+				<glossseealso otherterm="gloss-gui"
+>&GUI;</glossseealso>
+			</glossdef>
+		</glossentry>
+		<glossentry id="gloss-panel">
+			<glossterm
+>Panel</glossterm>
+			<glossdef
+><para
+>Refers to the panel (also known as <quote
+>&kicker;</quote
+>) which often resides at the bottom of the screen.</para>
+<glossseealso otherterm="gloss-kde"
+>&kde;</glossseealso
+> <glossseealso otherterm="gloss-kicker"
+>&kicker;</glossseealso
+> </glossdef>
+		</glossentry>
+		<glossentry id="gloss-ripping">
+			<glossterm
+>ripping</glossterm>
+			<glossdef
+><para
+>The process of reading audio data from a &cdrom; and storing it on the hard disk.</para>
+			</glossdef>
+		</glossentry>
+	</glossdiv>
+	
+	<glossdiv id="kde-development">
+		<title
+>&kde; Development</title>
+		<glossentry id="gloss-qt">
+			<glossterm
+>&Qt;</glossterm>
+			<glossdef
+><para
+>The &GUI; of &kde; is built on top of the &Qt; toolkit, which provides many graphical elements (so-called <quote
+>Widgets</quote
+>) which are used to construct the desktop. You can find more information about &Qt; at <ulink url="http://www.trolltech.com"
+>www.trolltech.com</ulink
+>.</para>
+<glossseealso otherterm="gloss-kde"
+>&kde;</glossseealso
+> <glossseealso otherterm="gloss-gui"
+>&GUI;</glossseealso
+> <glossseealso otherterm="gloss-widget"
+>Widget</glossseealso
+> </glossdef>
+		</glossentry>
+		<glossentry id="gloss-i18n">
+			<glossterm
+>i18n</glossterm>
+			<glossdef
+><para
+>Abbreviation for <quote
+>internationalisation</quote
+>. &kde; supports many different languages, and several i18n techniques make it easy to translate the &GUI; as well as the accompanying documents of &kde; into all these languages. More information about the i18n process is available at <ulink url="http://i18n.kde.org"
+>i18n.kde.org</ulink
+>.</para>
+<glossseealso otherterm="gloss-kde"
+>&kde;</glossseealso
+> <glossseealso otherterm="gloss-gui"
+>&GUI;</glossseealso
+> </glossdef>
+		</glossentry>
+		<glossentry id="gloss-l10n">
+			<glossterm
+>l10n</glossterm>
+			<glossdef
+><para
+>Abbreviation for <quote
+>localisation</quote
+>, the process of adapting a program to the local environment. This includes &eg; the currency used for monetary values or the time format.</para>
+				<glossseealso otherterm="gloss-i18n"
+>i18n</glossseealso>
+                        </glossdef>
+		</glossentry>
+		<glossentry id="gloss-widget">
+			<glossterm
+>Widget</glossterm>
+			<glossdef
+><para
+>Graphical elements like scrollbars, buttons or input fields which are used by &kde; to construct the &GUI;. </para>
+<glossseealso otherterm="gloss-kde"
+>&kde;</glossseealso
+> <glossseealso otherterm="gloss-gui"
+>&GUI;</glossseealso
+> </glossdef>
+		</glossentry>
+      <glossentry id="gloss-cvs">
+         <glossterm
+><acronym
+>CVS</acronym
+></glossterm>
+         <glossdef>
+            <para
+><emphasis
+>C</emphasis
+>oncurrent <emphasis
+>V</emphasis
+>ersion <emphasis
+>S</emphasis
+>ystem. The <acronym
+>CVS</acronym
+> is a very elegant way of managing file versions that allow more than one developer to easily work on the same project. You can find a description of how to get the latest (developer) version of the &kde; sources via anonymous <acronym
+>CVS</acronym
+> on <ulink url="http://www.kde.org/anoncvs.html"
+>http://www.kde.org/anoncvs.html</ulink
+>. More about <acronym
+>CVS</acronym
+> is available at <ulink url="http://www.cvshome.org"
+>www.cvshome.org</ulink
+>. </para>
+         </glossdef>
+      </glossentry>
+	</glossdiv>
+	
+	<glossdiv id="glossdiv-misc">
+		<title
+>Miscellaneous</title>
+		<glossentry id="gloss-rfc">
+			<glossterm
+><acronym
+>RFC</acronym
+></glossterm>
+			<glossdef
+><para
+><emphasis
+>R</emphasis
+>equest <emphasis
+>F</emphasis
+>or <emphasis
+>C</emphasis
+>omment. A common way to publish new protocol ideas or procedures for evaluation of the Internet community. Though <acronym
+>RFC</acronym
+>s are not mandatory, many applications try to adhere to them, once they have been approved by the community. More information about <acronym
+>RFC</acronym
+>s can be found at the <ulink url="http://www.rfc-editor.org"
+>RFC Homepage</ulink
+>.</para>
+			</glossdef>
+		</glossentry
+>	
+	</glossdiv>
+	
+	<glossdiv id="glossdiv-protocols">
+		<title
+>Various protocols</title>
+		<glossentry id="gloss-smb">
+			<glossterm
+><acronym
+>SMB</acronym
+></glossterm>
+			<glossdef
+><para
+><emphasis
+>S</emphasis
+>erver <emphasis
+>M</emphasis
+>essage <emphasis
+>B</emphasis
+>lock. A network protocol used in &Microsoft; &Windows; networks to access the filesystems of other computers.</para>
+				<glossseealso otherterm="gloss-ioslave"
+><acronym
+>IO</acronym
+> Slave</glossseealso>
+			</glossdef>
+		</glossentry>
+		<glossentry id="gloss-irc">
+			<glossterm
+><acronym
+>IRC</acronym
+></glossterm>
+			<glossdef
+><para
+><emphasis
+>I</emphasis
+>nternet <emphasis
+>R</emphasis
+>elay <emphasis
+>C</emphasis
+>hat. A protocol defined in <acronym
+>RFC</acronym
+> 1459, which handles the specification to enable real time text chat.</para>
+				<glossseealso otherterm="gloss-rfc"
+><acronym
+>RFC</acronym
+></glossseealso>
+			</glossdef>
+		</glossentry>
+                <glossentry id="gloss-host">
+		        <glossterm
+>host</glossterm>
+			<glossdef
+><para
+>This can either be a name from your <filename
+>/etc/hosts</filename
+> file (<systemitem class="systemname"
+>mycomputer</systemitem
+>), an Internet name (<systemitem class="systemname"
+>www.kde.org</systemitem
+>) or an IP-Address (<systemitem
+>192.168.0.10</systemitem
+>). </para>
+	                </glossdef>
+	        </glossentry>
+	</glossdiv>
+</glossary>
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/glossary/tdeprintingglossary.docbook b/tde-i18n-en_GB/docs/tdebase/khelpcenter/glossary/tdeprintingglossary.docbook
new file mode 100644
index 00000000000..2f7229ec727
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/glossary/tdeprintingglossary.docbook
@@ -0,0 +1,1264 @@
+
+<!--
+<?xml version="1.0" ?>
+<!DOCTYPE glossary PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN"
+"customization/dtd/kdex.dtd" [
+<!ENTITY % addindex "IGNORE">
+<!ENTITY % British-English "INCLUDE">
+<!ENTITY glossary-tdeprinting SYSTEM "tdeprintingglossary.docbook">
+
+]>
+<glossary id="glossary">
+-->
+        <glossdiv id="glossdiv-printing">
+                <title
+>Printing</title>
+ 
+
+                <glossentry id="gloss-acl">
+                        <glossterm
+><acronym
+>ACLs</acronym
+></glossterm>
+                        <glossdef
+><para
+>Abbreviation for <emphasis
+>A</emphasis
+>ccess <emphasis
+>C</emphasis
+>ontrol <emphasis
+>L</emphasis
+>ists; ACLs are used to check for the access by a given (authenticated) user. A first rough support for ACLs for printing is available from &CUPS;; this will be refined in future versions. </para>
+                                <glossseealso otherterm="gloss-authentication"
+>Authentication</glossseealso>
+                        </glossdef>
+                </glossentry>
+
+                <glossentry id="gloss-appsocketprotocol">
+                        <glossterm
+>AppSocket Protocol</glossterm>
+                        <glossdef
+><para
+>AppSocket is a protocol for the transfer of print data, also frequently called "Direct TCP/IP Printing". &Hewlett-Packard; have taken AppSocket, added a few minor extensions around it and been very successful in renaming and marketing it under the brand "&HP; JetDirect"...</para>
+<glossseealso otherterm="gloss-hpjetdirectprotocol"
+>&HP; JetDirect Protocol</glossseealso
+> <glossseealso otherterm="gloss-directtcpipprinting"
+>Direct TCP/IP Printing</glossseealso
+> </glossdef>
+                </glossentry>
+ 
+                <glossentry id="gloss-apsfilter">
+                        <glossterm
+>APSfilter</glossterm>
+                        <glossdef
+><para
+>APSfilter is used mainly in the context of "classical" &UNIX; printing (BSD-style LPD). It is a sophisticated shell script, disguised as an "all-in-one" filtering program. In reality, APSfilter calls "real filters" to do the jobs needed. It sends printjobs automatically through these other filters, based on an initial file-type analysis of the printfile. It is written and maintained by Andreas Klemm. It is similar to Magicfilter and mostly uses Ghostscript for file conversions. Some Linux Distributions (like &SuSE;) use APSfilter, others Magicfilter (like &RedHat;), some have both for preference selection (like *BSD). &CUPS; has <emphasis
+>no</emphasis
+> need for APSfilter, as it runs its own file type recognition (based on &MIME; types) and applies its own filtering logic.</para>
+<glossseealso otherterm="gloss-ghostscript"
+>Ghostscript</glossseealso
+> <glossseealso otherterm="gloss-magicfilter"
+>Magicfilter</glossseealso
+> <glossseealso otherterm="gloss-mimetypes"
+>&MIME;-Types</glossseealso
+> <glossseealso otherterm="gloss-printcap"
+>printcap</glossseealso
+> </glossdef>
+                </glossentry>
+
+                <glossentry id="gloss-authentication">
+                        <glossterm
+>Authentication</glossterm>
+                        <glossdef
+><para
+>Proving the identity of a certain person (maybe via username/password or by means of a certificate) is often called authentication. Once you are authenticated, you may or may not get access to a requested ressource, possibly based on ACLs.</para>
+                                <glossseealso otherterm="gloss-acl"
+>ACLs</glossseealso>
+                        </glossdef>
+                </glossentry>
+ 
+                <glossentry id="gloss-bidirectionalcommunication">
+                        <glossterm
+>Bi-directional communication</glossterm>
+                        <glossdef
+><para
+>In the context of printing, a server or a host may receive additional information sent back from the printer (status messages &etc;), either upon a query or unrequested. AppSocket ( = &HP; JetDirect), &CUPS; and IPP support bi-directional communication, LPR/LPD and BSD-style printing do not...</para>
+<glossseealso otherterm="gloss-appsocketprotocol"
+>AppSocket Protocol</glossseealso
+> <glossseealso otherterm="gloss-cups"
+>&CUPS;</glossseealso
+> <glossseealso otherterm="gloss-directtcpipprinting"
+>Direct TCP/IP Printing</glossseealso
+> <glossseealso otherterm="gloss-hpjetdirectprotocol"
+>&HP; JetDirect</glossseealso
+> <glossseealso otherterm="gloss-ipp"
+>IPP</glossseealso
+> <glossseealso otherterm="gloss-lprlpd"
+>LPR/LPD</glossseealso
+> </glossdef>
+                </glossentry>
+
+                <glossentry id="gloss-bsdstyleprinting">
+                        <glossterm
+>BSD-style Printing</glossterm>
+                        <glossdef
+><para
+>Generic term for different variants of the traditional &UNIX; printing method. Its first version appeared in the early 70s on BSD &UNIX; and was formally described in <ulink url="http://www.rfc.net/rfc1179.html"
+>RFC 1179</ulink
+> only as late as 1990. At the time when BSD "remote" printing was first designed, printers were serially or otherwise directly connected devices to a host (with the Internet hardly consisting of more than 100 nodes!); printers used hole-punched, continuous paper, fed through by a tractor mechanism, with simple rows of ASCII text mechanically hammered on to the medium, drawn from a cardboard box beneath the table. It came out like a zig-zag folded paper "snake". Remote printing consisted of a neighbouring host in the next room sending a file asking for printout. How technology has changed! Printers generally use cut-sheet media, they have built-in intelligence to compute the raster images of pages after pages that are sent to them using one of the powerful page description languages (PDL). Many are network nodes in their own right, with CPU, RAM, a hard disk and their own Operation System, and are hooked to a net with potentially millions of users... It is a vast proof of the flexible &UNIX; concept for doing things, that it made "Line Printing" reliably work even under these modern conditions. But time has finally come now to go for something new -- the IPP. It is strong proof of the flexibility of &UNIX;; that "Line Printing" works reliably, even under these modern conditions. But time has finally come now to go for something new -- the IPP. </para>
+<glossseealso otherterm="gloss-ipp"
+>IPP</glossseealso
+> <glossseealso otherterm="gloss-cups"
+>&CUPS;</glossseealso
+> <glossseealso otherterm="gloss-lprlpd"
+>LPR/LPD printing</glossseealso
+> </glossdef>
+                </glossentry>
+ 
+                <glossentry id="gloss-cups">
+                        <glossterm
+>&CUPS;</glossterm>
+                        <glossdef
+><para
+>Abbreviation for <emphasis
+>C</emphasis
+>ommon <emphasis
+>U</emphasis
+>NIX <emphasis
+>P</emphasis
+>rinting <emphasis
+>S</emphasis
+>ystem; &CUPS; is the most modern &UNIX; and Linux printing system, also providing cross-platform print services to &Microsoft; &Windows; and Apple &MacOS; clients. Based on IPP, it does away with all the pitfalls of old-style BSD printing, providing authentication, encryption and ACLs, plus many more features. At the same time it is backward-compatible enough to serve all legacy clients that are not yet up to IPP, via LPR/LPD (BSD-style). &CUPS; is able to control any &PostScript; printer by utilizing the vendor-supplied PPD (PostScript Printer Description file), targeted originally for &Microsoft; Windows NT printing only. &kde; Printing is most powerful if based on &CUPS;.</para>
+<glossseealso otherterm="gloss-acl"
+>ACLs</glossseealso
+> <glossseealso otherterm="gloss-authentication"
+>Authentication</glossseealso
+> <glossseealso otherterm="gloss-bsdstyleprinting"
+>BSD-style printing</glossseealso
+> <glossseealso otherterm="gloss-ipp"
+>IPP</glossseealso
+> <glossseealso otherterm="gloss-tdeprint"
+>KDEPrint</glossseealso
+> <glossseealso otherterm="gloss-lprlpd"
+>LPR/LPD</glossseealso
+> <glossseealso otherterm="gloss-ppd"
+>PPD</glossseealso
+> </glossdef>
+                </glossentry>
+
+ 
+                <glossentry id="gloss-cupsfaq">
+                        <glossterm
+><acronym
+>&CUPS;-FAQ</acronym
+></glossterm>
+                        <glossdef
+><para
+>Currently only available in German (translation is on the way), the <ulink url="http://www.danka.de/printpro/faq.html"
+>&CUPS;-FAQ</ulink
+> is a valuable resource to answer many questions that anyone new to &CUPS; printing might have at first. </para>
+                                <glossseealso otherterm="gloss-tdeprinthandbook"
+>KDEPrint Handbook</glossseealso>
+                        </glossdef>
+                </glossentry>
+
+
+                <glossentry id="gloss-cups-o-matic">
+                        <glossterm
+>&CUPS;-O-Matic</glossterm>
+                        <glossdef
+><para
+>&CUPS;-O-Matic was the first "Third Party" plugin for the &CUPS; printing software. It is available on the <ulink url="http://www.linuxprinting.org/cups-doc.html"
+>Linuxprinting.org website</ulink
+> to provide an online PPD-generating service. Together with the companion <application
+>cupsomatic</application
+> Perl-Script, that needs to be installed as an additional &CUPS; backend, it redirects output from the native <application
+>pstops</application
+> filter into a chain of suitable Ghostscript filters. Upon completion, it passes the resulting data back to a &CUPS; "backend" for sending to the printer. In this way, &CUPS;-O-Matic enables support for any printer known to have worked previously in a "classical" Ghostscript environment. If no native &CUPS; support for that printer is in sight... &CUPS;-O-Matic is now replaced by the more capable PPD-O-Matic.</para>
+<glossseealso otherterm="gloss-cupsomatic"
+>cupsomatic</glossseealso
+> <glossseealso otherterm="gloss-PPD-O-Matic"
+>PPD-O-Matic</glossseealso
+> <glossseealso otherterm="gloss-foomatic"
+>Foomatic</glossseealso
+> </glossdef>
+                </glossentry>
+
+
+                <glossentry id="gloss-cupsomatic">
+                        <glossterm
+>cupsomatic</glossterm>
+                        <glossdef
+><para
+>The Perl script <application
+>cupsomatic</application
+> (plus a working Perl installation on your system) is needed to make any &CUPS;-O-Matic (or PPD-O-Matic) generated PPD work with &CUPS;. It was written by Grant Taylor, author of the Linux Printing HOWTO and Maintainer of the <ulink url="http://www.linuxprinting.org/printer_list.cgi"
+>printer database</ulink
+> at the Linuxprinting.org website.</para>
+<glossseealso otherterm="gloss-cups-o-matic"
+>&CUPS;-O-Matic</glossseealso
+> <glossseealso otherterm="gloss-foomatic"
+>Foomatic</glossseealso
+> <glossseealso otherterm="gloss-cupsomatic"
+>cupsomatic</glossseealso
+> </glossdef>
+                </glossentry>
+
+                <glossentry id="gloss-daemon">
+                        <glossterm
+><acronym
+>Daemon</acronym
+></glossterm>
+                        <glossdef
+><para
+>Abbreviation for <emphasis
+>D</emphasis
+>isk <emphasis
+>a</emphasis
+>nd <emphasis
+>e</emphasis
+>xecution <emphasis
+>mon</emphasis
+>itor; <acronym
+>Daemons</acronym
+> are present on all &UNIX; systems to perform tasks independent of user intervention. Readers more familiar with &Microsoft; &Windows; might want to compare daemons and the tasks they are responsible with "services". One example of a daemon present on most legacy &UNIX; systems is the LPD (Line Printer Daemon); &CUPS; is widely seen as the successor to LPD in the &UNIX; world and it also operates through a daemon. </para>
+                                <glossseealso otherterm="gloss-spooling"
+>SPOOLing</glossseealso>
+                        </glossdef>
+                </glossentry>
+ 
+                <glossentry id="gloss-databaselinuxprinting">
+                        <glossterm
+>Database, Linuxprinting.org</glossterm>
+                        <glossdef
+><para
+>Already years ago, when Linux printing was still really difficult (only command line printing was known to most Linux users, no device specific print options were available for doing the jobs), Grant Taylor, author of the "Linux Printing HOWTO", collected most of the available information about printers, drivers and filters in his database. With the emerging &CUPS; concept, extending the use of PPDs even to non-PostScript printers, he realised the potential of this database: if one puts the different datablobs (with content that could be described along the lines "Which device prints with which Ghostscript or other filter?", "How well?", and "What command line switches are available?") into PPD-compatible files, he could have all the power of &CUPS; on top of the traditional printer "drivers". This has now developed into a broader concept, known as "Foomatic". Foomatic extends the capabilities of spoolers other than &CUPS; (LPR/LPD, LPRng, PDQ, PPR) to a certain degree ("stealing" some concepts from &CUPS;). The Linuxprinting Database is not a Linux-only stop -- people running other &UNIX; based OSes (like *BSD or &MacOS; X) will also find valuable information and software there. </para>
+<glossseealso otherterm="gloss-foomatic"
+>Foomatic</glossseealso
+> <glossseealso otherterm="gloss-linuxprintingdatabase"
+>Linuxprinting database</glossseealso
+> </glossdef>
+                </glossentry>
+
+                <glossentry id="gloss-directtcpipprinting">
+                        <glossterm
+>Direct TCP/IP Printing</glossterm>
+                        <glossdef
+><para
+>This is a method that often uses TCP/IP port 9100 to connect to the printer. It works with many modern network printers and has a few advantages over LPR/LPD, as it is faster and provides some "backchannel feedback data" from the printer to the host sending the job.</para>
+<glossseealso otherterm="gloss-appsocketprotocol"
+>AppSocket Protocol</glossseealso
+> <glossseealso otherterm="gloss-hpjetdirectprotocol"
+>&HP; JetDirect Protocol</glossseealso
+> </glossdef>
+                </glossentry>
+
+
+                <glossentry id="gloss-drivers">
+                        <glossterm
+>Drivers, Printer Drivers</glossterm>
+                        <glossdef
+><para
+>The term "printer drivers", used in the same sense as on the &Microsoft; &Windows; platform, is not entirely applicable to a Linux or &UNIX; platform. A "driver" functionality is supplied on &UNIX; by different modular components working together. At the core of the printer drivers are "filters". Filters convert print files from a given input format to another format that is acceptable to the target printer. In many cases filters may be connected to a whole filter "chain", where only the result of the last conversion is sent to the printer. The actual transfer of the print data to the device is performed by a "backend". </para>
+<glossseealso otherterm="gloss-filter"
+>Filter</glossseealso
+> <glossseealso otherterm="gloss-ppd"
+>PPDs</glossseealso
+> </glossdef>
+                </glossentry>
+
+                <glossentry id="gloss-easysoftwareproducts">
+                        <glossterm
+>Easy Software Products</glossterm>
+                        <glossdef
+><para
+>Mike Sweet's company, which has contributed a few substantial software products towards the Free Software community; amongst them the initial version of <ulink url="http://gimp-print.sf.net/"
+>Gimp-Print,</ulink
+> the <ulink url="http://www.easysw.com/epm/"
+>EPM software packaging</ulink
+> tool and <ulink url="http://www.easysw.com/htmldoc/"
+>HTMLDOC</ulink
+> (used by the "Linux Documentation Project" to build the PDF versions of the HOWTOs) -- but most importantly: <ulink url="http://www.cups.org/"
+>&CUPS;</ulink
+> (the 'Common &UNIX; Printing System'). ESP finance themselves by selling a commercial version of &CUPS;, called <ulink url="http://www.easysw.com/"
+>ESP PrintPro,</ulink
+> that includes some professional enhancements. </para>
+<glossseealso otherterm="gloss-cups"
+>&CUPS;</glossseealso
+> <glossseealso otherterm="gloss-espprintpro"
+>ESP PrintPro</glossseealso
+> <glossseealso otherterm="gloss-esp"
+>ESP</glossseealso
+> <glossseealso otherterm="gloss-gimpprint"
+>Gimp-Print</glossseealso
+> </glossdef>
+                </glossentry>
+ 
+                <glossentry id="gloss-encryption">
+                        <glossterm
+>Encryption</glossterm>
+                        <glossdef
+><para
+>Encryption of confidential data is an all-important issue if you transfer it over the Internet or even within intranets. Printing via traditional protocols is not encrypted at all -- it is very easy to tap and eavesdrop &eg; into &PostScript; or PCL data transfered over the wire. Therefore, in the design of IPP, provision was made for the easy plugin of encryption mechanisms (which can be provided by the same means as the encryption standards for HTTP traffic: SSL and TLS).</para>
+<glossseealso otherterm="gloss-authentication"
+>Authentication</glossseealso
+> <glossseealso otherterm="gloss-cups"
+>&CUPS;</glossseealso
+> <glossseealso otherterm="gloss-ipp"
+>IPP</glossseealso
+> <glossseealso otherterm="gloss-ssl"
+>SSL</glossseealso
+> <glossseealso otherterm="gloss-tls"
+>TLS</glossseealso
+> </glossdef>
+                </glossentry>
+
+
+                <glossentry id="gloss-epson">
+                        <glossterm
+><acronym
+>Epson</acronym
+></glossterm>
+                        <glossdef
+><para
+>Epson inkjets are among the best supported models by Free software drivers, as the company was not necessarily as secretive about their devices and handed technical specification documents to developers. The excellent print quality achieved by Gimp-Print on the Stylus series of printers can be attributed to this openness. They have also contracted Easy Software Products to maintain an enhanced version of Ghostscript ("ESP GhostScript") for improved support of their printer portfolio. </para>
+                                <glossseealso otherterm="gloss-ghostscript"
+>ESP Ghostscript</glossseealso>
+                        </glossdef>
+                </glossentry>
+
+
+                <glossentry id="gloss-escapesequence">
+                        <glossterm
+>Escape Sequences</glossterm>
+                        <glossdef
+><para
+>The first ever printers printed ASCII data only. To initiate a new line, or eject a page, they included special command sequences, often carrying a leading [ESC]-character. &HP; evolved this concept through its series of PCL language editions until today, having now developed a full-blown Page Description Language (PDL) from these humble beginnings. </para>
+<glossseealso otherterm="gloss-pcl"
+>PCL</glossseealso
+> <glossseealso otherterm="gloss-pdl"
+>PDL</glossseealso
+> </glossdef>
+                </glossentry>
+
+                <glossentry id="gloss-escp">
+                        <glossterm
+><acronym
+>ESC/P</acronym
+></glossterm>
+                        <glossdef
+><para
+>Abbreviation for <emphasis
+>E</emphasis
+>pson <emphasis
+>S</emphasis
+>tandard <emphasis
+>C</emphasis
+>odes for <emphasis
+>P</emphasis
+>rinters. Besides &PostScript; and PCL, Epson's ESC/P printer language is one of the best known.</para>
+<glossseealso otherterm="gloss-pcl"
+>PCL</glossseealso
+> <glossseealso otherterm="gloss-postscript"
+>&PostScript;</glossseealso
+> <glossseealso otherterm="gloss-hpgl"
+>hpgl</glossseealso
+> </glossdef>
+                </glossentry>
+
+                <glossentry id="gloss-esp">
+                        <glossterm
+><acronym
+>ESP</acronym
+></glossterm>
+                        <glossdef
+><para
+>Abbreviation for <emphasis
+>E</emphasis
+>asy <emphasis
+>S</emphasis
+>oftware <emphasis
+>P</emphasis
+>roducts; the company that developed &CUPS; (the "Common &UNIX; Printing System"). </para>
+<glossseealso otherterm="gloss-easysoftwareproducts"
+>Easy Software Products</glossseealso
+> <glossseealso otherterm="gloss-cups"
+>&CUPS;</glossseealso
+> <glossseealso otherterm="gloss-espprintpro"
+>ESP PrintPro</glossseealso
+> </glossdef>
+                </glossentry>
+
+
+                <glossentry id="gloss-espghostscript">
+                        <glossterm
+><acronym
+>ESP</acronym
+> Ghostscript</glossterm>
+                        <glossdef
+><para
+>A Ghostscript version that is maintained by Easy Software Products. It includes pre-compiled Gimp-Print drivers for many inkjets (plus some other goodies). ESP Ghostscript will produce photographic quality prints in many cases, especially with the Epson Stylus model series. ESP Ghostscript is GPL-software. </para>
+<glossseealso otherterm="gloss-easysoftwareproducts"
+>Easy Software Products</glossseealso
+> <glossseealso otherterm="gloss-cups"
+>&CUPS;</glossseealso
+> <glossseealso otherterm="gloss-espprintpro"
+>ESP PrintPro</glossseealso
+> </glossdef>
+                </glossentry>
+
+                <glossentry id="gloss-espprintpro">
+                        <glossterm
+><acronym
+>ESP</acronym
+> PrintPro</glossterm>
+                        <glossdef
+><para
+>This professional enhancement to &CUPS; (the "Common &UNIX; Printing System") is sold by the developers of &CUPS; complete with more than 2,300 printer drivers for several commercial &UNIX; platforms. <ulink url="http://www.easysw.com/printpro/"
+>ESP PrintPro</ulink
+> is supposed to work "out of the box" with little or no configuration for users or admins. ESP also sell support contracts for &CUPS; and PrintPro. These sales help to feed the programmers who develop the Free version of &CUPS;. </para>
+                                <glossseealso otherterm="gloss-cups"
+>&CUPS;</glossseealso>
+                        </glossdef>
+                </glossentry>
+
+               <glossentry id="gloss-filter">
+                        <glossterm
+>Filter</glossterm>
+                        <glossdef
+><para
+>Filters, in general, are programs that take some input data, work on it and pass it on as their output data. Filters may or may not change the data. Filters in the context of printing, are programs that convert a given file (destined for printing, but not suitable in the format it is presently) into a printable format. Sometimes whole "filter chains" have to be constructed to achieve the goal, piping the output of one filter as the input to the next. </para>
+<glossseealso otherterm="gloss-ghostscript"
+>Ghostscript</glossseealso
+> <glossseealso otherterm="gloss-rip"
+>RIP</glossseealso
+> </glossdef>
+                </glossentry>
+
+                <glossentry id="gloss-foomatic">
+                        <glossterm
+>Foomatic</glossterm>
+                        <glossdef
+><para
+>Foomatic started out as the wrapper name for a set of different tools available from <ulink url="http://www.linuxprinting.org/"
+>Linuxprinting.org</ulink
+> These tools aimed to make the usage of traditional Ghostscript and other print filters easier for users and extend the filters' capabilities by adding more command line switches or explain the driver's execution data. Foomatic's different incarnations are &CUPS;-O-Matic, PPD-O-Matic, PDQ-O-Matic, LPD-O-Matic, PPR-O-Matic, MF-O-Matic and Direct-O-Matic. All of these allow the generation of appropriate printer configuration files online, by simply selection the suitable model and suggested (or alternate) driver for that machine. More recently, Foomatic gravitated towards becoming a "meta-spooling" system, that allows configuration of the underlying print subsystem through a unified set of commands (however, this is much more complicated than KDEPrint's &GUI; interface, which performs a similar task with regards to different print subsystems). </para>
+<glossseealso otherterm="gloss-cups-o-matic"
+>&CUPS;-O-Matic</glossseealso
+> <glossseealso otherterm="gloss-PPD-O-Matic"
+>PPD-O-Matic</glossseealso
+> <glossseealso otherterm="gloss-cupsomatic"
+>cupsomatic</glossseealso
+> </glossdef>
+                </glossentry>
+
+               <glossentry id="gloss-ghostscript">
+                        <glossterm
+>Ghostscript</glossterm>
+                        <glossdef
+><para
+>Ghostscript is a &PostScript; Raster Image Processor (RIP) in software, originally developed by L. Peter Deutsch. There is always a <acronym
+>GPL</acronym
+> version of Ghostscript available for free usage and distribution (mostly 1 year old) while the current version is commercially sold under another licence. Ghostscript is widely used inside the Linux and &UNIX; world for transforming &PostScript; into raster data suitable for sending to non-&PostScript; devices.</para>
+<glossseealso otherterm="gloss-postscript"
+>&PostScript;</glossseealso
+> <glossseealso otherterm="gloss-rip"
+>RIP</glossseealso
+> </glossdef>
+                </glossentry>
+
+                <glossentry id="gloss-gimpprint">
+                        <glossterm
+>Gimp-Print</glossterm>
+                        <glossdef
+><para
+>Contrary to its name, Gimp-Print is no longer just the plugin to be used for printing from the popular Gimp program -- its codebase can also serve to be compiled into... *...a set of PPDs and associated filters that integrate seamlessly into &CUPS;, supporting around 130 different printer models, providing photographic output quality in many cases; *...a Ghostscript filter that can be used with any other program that needs a software-RIP; *...a library that can be used by other software applications in need of rasterising functions. </para>
+<glossseealso otherterm="gloss-lexmark"
+>Lexmark Drivers</glossseealso
+> <glossseealso otherterm="gloss-rip"
+>RIP</glossseealso
+> <glossseealso otherterm="gloss-ghostscript"
+>Ghostscript</glossseealso
+> </glossdef>
+                </glossentry>
+
+                <glossentry id="gloss-hp">
+                        <glossterm
+><acronym
+>&HP;</acronym
+></glossterm>
+                        <glossdef
+><para
+>Abbreviation for <emphasis
+>H</emphasis
+>ewlett-<emphasis
+>Packard</emphasis
+>; one of the first companies to distribute their own Linux printer drivers. -- More recently, the Company has released their "HPIJS" package of drivers, including source code and a Free licence. This is the first printer manufacturer to do so. HPIJS supports most current models of HP Ink- and DeskJets. </para>
+                        </glossdef>
+                </glossentry>
+
+
+                <glossentry id="gloss-hpgl">
+                        <glossterm
+><acronym
+>&HP;/GL</acronym
+></glossterm>
+                        <glossdef
+><para
+>Abbreviation for <emphasis
+>&HP;</emphasis
+> <emphasis
+>G</emphasis
+>raphical <emphasis
+>L</emphasis
+>anguage; a &HP; printer language mainly used for plotters; many CAD (Computer Aided Design) software programs output &HP;/GL files for printing.</para>
+<glossseealso otherterm="gloss-escp"
+>ESC/P</glossseealso
+> <glossseealso otherterm="gloss-pcl"
+>PCL</glossseealso
+> <glossseealso otherterm="gloss-postscript"
+>&PostScript;</glossseealso
+> </glossdef>
+                </glossentry>
+
+                <glossentry id="gloss-hpjetdirectprotocol">
+                        <glossterm
+>&HP; JetDirect Protocol</glossterm>
+                        <glossdef
+><para
+>A term branded by &HP; to describe their implementation of print data transfer to the printer via an otherwise "AppSocket" or "Direct TCP/IP Printing" named protocol.</para>
+<glossseealso otherterm="gloss-appsocketprotocol"
+>AppSocket Protocol</glossseealso
+> <glossseealso otherterm="gloss-directtcpipprinting"
+>Direct TCP/IP Printing</glossseealso
+> </glossdef>
+                </glossentry>
+
+		<glossentry id="gloss-ietf">
+                        <glossterm
+><acronym
+>IETF</acronym
+></glossterm>
+                        <glossdef
+><para
+>Abbreviation for <emphasis
+>I</emphasis
+>nternet <emphasis
+>E</emphasis
+>ngineering <emphasis
+>T</emphasis
+>ask <emphasis
+>F</emphasis
+>orce; an assembly of Internet, software and hardware experts that discuss new networking technologies and very often arrive at conclusions that are regarded by many as standards. "TCP/IP" is the most famous example. IETF standards, as well as drafts, discussions, ideas and useful tutorials, are put in writing in the famous series of "RFCs", which are available to the public and included in most Linux and BSD distributions.</para>
+<glossseealso otherterm="gloss-ipp"
+>IPP</glossseealso
+> <glossseealso otherterm="gloss-pwg"
+>PWG</glossseealso
+> <glossseealso otherterm="gloss-rfc"
+>RFC</glossseealso
+> </glossdef>
+                </glossentry>
+
+                <glossentry id="gloss-ipp">
+                        <glossterm
+><acronym
+>IPP</acronym
+></glossterm>
+                        <glossdef
+><para
+>Abbreviation for <emphasis
+>I</emphasis
+>nternet <emphasis
+>P</emphasis
+>rinting <emphasis
+>P</emphasis
+>rotocol; defined in a series of RFCs accepted by the IETF with status "proposed standard"; was designed by the PWG. -- IPP is a completely new design for network printing, but it utilises a very well-known and proven method for the actual data transfer: HTTP 1.1! By not "re-inventing the wheel", and basing itself on an existing and robust Internet standard, IPP is able to relatively easily bolt other HTTP-compatible standard mechanisms into its framework: * Basic, Digest or Certificate authentication mechanisms; * SSL or TLS for encryption of transferred data; * LDAP for directory services (to publish data on printers, device-options, drivers, costs or also to the network; or to check for passwords while performing authentication). </para>
+<glossseealso otherterm="gloss-cups"
+>&CUPS;</glossseealso
+> <glossseealso otherterm="gloss-pwg"
+>PWG</glossseealso
+> <glossseealso otherterm="gloss-ietf"
+>IETF</glossseealso
+> <glossseealso otherterm="gloss-rfc"
+>RFC</glossseealso
+> <glossseealso otherterm="gloss-tls"
+>TLS</glossseealso
+> </glossdef>
+                </glossentry>
+
+                <glossentry id="gloss-tdeprint">
+                        <glossterm
+><acronym
+>KDEPrint</acronym
+></glossterm>
+                        <glossdef
+><para
+>The new printing functionality of &kde; since version 2.2 consists of several modules that translate the features and settings of different available print subsystems (&CUPS;, BSD-style LPR/LPD, RLPR...) into nice &kde; desktop &GUI; windows and dialogues to ease their usage. Most important for day-to-day usage is "kprinter", the new &GUI; print command. -- Note: KDEPrint does <emphasis
+>not</emphasis
+> implement its own spooling mechanism or its own &PostScript; processing; for this it relies on the selected <emphasis
+>print subsystem</emphasis
+> -- however it does add some functionality of its own on top of this foundation... </para>
+<glossseealso otherterm="gloss-bsdstyleprinting"
+>BSD-style printing</glossseealso
+> <glossseealso otherterm="gloss-cups"
+>&CUPS;</glossseealso
+> <glossseealso otherterm="gloss-kprinter"
+>kprinter</glossseealso
+> <glossseealso otherterm="gloss-tdeprinthandbook"
+>KDEPrint Handbook</glossseealso
+> </glossdef>
+                </glossentry>
+
+
+                <glossentry id="gloss-tdeprinthandbook">
+                        <glossterm
+><acronym
+>KDEPrint Handbook...</acronym
+></glossterm>
+                        <glossdef
+><para
+>...is the name of the reference document that describes KDEPrint functions to users and administrators. You can load it into Konqueror by typing "help:/tdeprint" into the address field. The <ulink url="http://printing.kde.org/"
+>KDEPrint website</ulink
+> is the resource for updates to this documentation, as well as PDF versions suitable for printing it. It is authored and maintained by Kurt Pfeifle. </para>
+                                <glossseealso otherterm="gloss-cupsfaq"
+>&CUPS;-FAQ</glossseealso>
+                        </glossdef>
+                </glossentry>
+
+                <glossentry id="gloss-kprinter">
+                        <glossterm
+>kprinter</glossterm>
+                        <glossdef
+><para
+><emphasis
+>kprinter</emphasis
+> is the new powerful print utility that is natively used by all &kde; applications. Contrary to some common misconceptions, <emphasis
+>kprinter</emphasis
+> is <emphasis
+>not</emphasis
+> a &CUPS;-only tool, but supports different print subsystems. You can even switch to a different print subsystem "on the fly", in between two jobs, without re-configuration. Of course, due to the powerful features of &CUPS;, <emphasis
+>kprinter</emphasis
+> is best suited for use with a &CUPS; frontend. <emphasis
+>kprinter</emphasis
+> is the successor to "qtcups", which is no longer being actively maintained. It has inherited all the best features of qtcups and added several new ones. MOST IMPORTANT: you can use <emphasis
+>kprinter</emphasis
+> with all its features in all non-&kde; applications that allow a customized print command, like gv, Acrobat Reader, Netscape, Mozilla, Galeon, StarOffice, OpenOffice and all GNOME programs. <emphasis
+>kprinter</emphasis
+> can act as a "standalone" utility, started from an X-Terminal or a "Mini-CLI" to print many different files, from different folders, with different formats, in one job and simultaneously, without the need to first open the files in the applications! (File formats supported this way are &PostScript;, PDF, International and ASCII Text, as well as many different popular graphic formats, such as PNG, TIFF, JPEG, PNM, Sun RASTER, &etc;) </para>
+                                <glossseealso otherterm="gloss-qtcups"
+>QtCUPS</glossseealso>
+                        </glossdef>
+                </glossentry>
+
+                <glossentry id="gloss-lexmark">
+                        <glossterm
+><acronym
+>Lexmark</acronym
+></glossterm>
+                        <glossdef
+><para
+>was one of the first companies to distribute their own Linux printer drivers for some of their models. However, those drivers are binary only (no source code available), and therefore cannot be used to integrate into other Free printing software projects. </para>
+                        </glossdef>
+                </glossentry>
+
+                <glossentry id="gloss-linuxprintingorg">
+                        <glossterm
+>Linuxprinting.org</glossterm>
+                        <glossdef
+><para
+>Linuxprinting.org = not just for Linux; all &UNIX;-like OS-es, like *BSD and commercial Unices may find useful printing information on this site. This web site is the home for the interesting Foomatic project, that strives to develop the "Meta Print Spool and Driver Configuration Toolset" (being able to configure, through one common interface, different print subsystems and their required drivers) with the ability to transfer all queues, printers and configuration files seamlessly to another spooler without new configuration effort. -- Also, they maintain the Printing Database; a collection of driver and device information that enables everybody to find the most current information about printer models, and also generate online the configuration files for any spooler/driver/device combo known to work with one of the common Linux or &UNIX; print subsystems. </para>
+                                <glossseealso otherterm="gloss-linuxprintingdatabase"
+>Linuxprinting database</glossseealso>
+                        </glossdef>
+                </glossentry>
+
+
+                <glossentry id="gloss-linuxprintingdatabase">
+                        <glossterm
+><acronym
+>Linuxprinting.org Database</acronym
+></glossterm>
+                        <glossdef
+><para
+>....Database containing printers and drivers that are suitable for them... ...a lot of information and documentation to be found... ...it is now also providing some tools and utilities for easing the integration of those drivers into a given system... ...the "Foomatic" family of utilities; being the toolset to make use of the database for most of the commonly used print subsystems, for generating "on the fly" working configurations for your printer model. </para>
+                                <glossseealso otherterm="gloss-foomatic"
+>Foomatic</glossseealso>
+                        </glossdef>
+                </glossentry>
+
+                <glossentry id="gloss-lprlpd">
+                        <glossterm
+><acronym
+>LPR/LPD</acronym
+> printing</glossterm>
+                        <glossdef
+><para
+>LPR == some people translate <emphasis
+>L</emphasis
+>ine <emphasis
+>P</emphasis
+>rinting <emphasis
+>R</emphasis
+>equest, others: <emphasis
+>L</emphasis
+>ine <emphasis
+>P</emphasis
+>rinter <emphasis
+>R</emphasis
+>emote.</para>
+                                <glossseealso otherterm="gloss-bsdstyleprinting"
+>BSD-style printing</glossseealso>
+                        </glossdef>
+                </glossentry>
+
+                <glossentry id="gloss-magicfilter">
+                        <glossterm
+>Magicfilter</glossterm>
+                        <glossdef
+><para
+>Similarly to the APSfilter program, Magicfilter provides automatic file type recognition functions and, base on that, automatic file conversion to a printable format, depending on the target printer.</para>
+                                <glossseealso otherterm="gloss-apsfilter"
+>APSfilter</glossseealso>
+                        </glossdef>
+                </glossentry>
+
+                <glossentry id="gloss-mimetypes">
+                        <glossterm
+>&MIME;-Types</glossterm>
+                        <glossdef
+><para
+>Abbreviation for <emphasis
+>M</emphasis
+>ultipurpose (or Multimedia) <emphasis
+>I</emphasis
+>nternet <emphasis
+>M</emphasis
+>ail <emphasis
+>E</emphasis
+>xtensions; &MIME;-Types were first used to allow the transport of binary data (like mail attachments containing graphics) over mail connections that were normally only transmitting ASCII characters: the data had to be encoded into an ASCII representation. Later this concept was extended to describe a data format in a platform independent, but at the same time non-ambiguous, way. From &Windows; everybody knows the .doc extensions for &Microsoft; Word files. This is handled ambiguously on the &Windows; platform: .doc extensions are also used for simple text files or for Adobe Framemaker files. And if a real Word file is renamed with a different extension, it can no longer be opened by the program. &MIME; typed files carry a recognition string with them, describing their file format based on <emphasis
+>main_category/sub_category</emphasis
+>. Inside IPP, print files are also described using the &MIME; type scheme. &MIME; types are registered with the IANA (Internet Assigning Numbers <emphasis
+>Association</emphasis
+>) to keep them unambiguous. &CUPS; has some &MIME; types of its own registered, like <emphasis
+>application/vnd.cups-raster</emphasis
+> (for the &CUPS;-internal raster image format). </para>
+<glossseealso otherterm="gloss-cups"
+>&CUPS;</glossseealso
+> <glossseealso otherterm="gloss-easysoftwareproducts"
+>Easy Software Products</glossseealso
+> <glossseealso otherterm="gloss-espprintpro"
+>ESP PrintPro</glossseealso
+> <glossseealso otherterm="gloss-gimpprint"
+>Gimp-Print</glossseealso
+> </glossdef>
+                </glossentry>
+
+                <glossentry id="gloss-pcl">
+                        <glossterm
+><acronym
+>PCL</acronym
+></glossterm>
+                        <glossdef
+><para
+>Abbreviation for <emphasis
+>P</emphasis
+>rinter <emphasis
+>C</emphasis
+>ontrol <emphasis
+>L</emphasis
+>anguage; developed by &HP;. PCL started off in version 1 as a simple command set for ASCII printing; now, in its versions PCL6 and PCL-X, it is capable of printing graphics and colour -- but outside the &Microsoft; &Windows; realm and &HP-UX; (&HP;'s own brand of &UNIX;), it is not commonly used...</para>
+<glossseealso otherterm="gloss-escp"
+>ESC/P</glossseealso
+> <glossseealso otherterm="gloss-hpgl"
+>&HP;/GL</glossseealso
+> <glossseealso otherterm="gloss-pdl"
+>PDL</glossseealso
+> <glossseealso otherterm="gloss-postscript"
+>&PostScript;</glossseealso
+> </glossdef>
+                </glossentry>
+
+                <glossentry id="gloss-pdl">
+                        <glossterm
+><acronym
+>PDL</acronym
+></glossterm>
+                        <glossdef
+><para
+>Abbreviation for <emphasis
+>P</emphasis
+>age <emphasis
+>D</emphasis
+>escription <emphasis
+>L</emphasis
+>anguage; PDLs describe, in an abstract way, the graphical representation of a page. - Before it is actually transferred into toner or ink laid down on to paper, a PDL needs to be "interpreted" first. In &UNIX;, the most important PDL is &PostScript;. </para>
+<glossseealso otherterm="gloss-escp"
+>ESC/P</glossseealso
+> <glossseealso otherterm="gloss-hpgl"
+>&HP;/GL</glossseealso
+> <glossseealso otherterm="gloss-pcl"
+>PCL</glossseealso
+> <glossseealso otherterm="gloss-postscript"
+>&PostScript;</glossseealso
+> </glossdef>
+                </glossentry>
+
+                <glossentry id="gloss-pixel">
+                        <glossterm
+>Pixel</glossterm>
+                        <glossdef
+><para
+>Abbreviation for <emphasis
+>Pic</emphasis
+>ture <emphasis
+>El</emphasis
+>ement; this term describes the smallest part of a raster picture (either as printed on paper or as displayed on a monitor by cathode rays or LCD elements). As any graphical or image representation on those types of output devices is composed of pixels, the values of "ppi" (pixel per inch) and &dpi; (dots per inch) are one important parameter for the overall quality and resolution of an image.</para>
+<glossseealso otherterm="gloss-filter"
+>Filter</glossseealso
+> <glossseealso otherterm="gloss-ghostscript"
+>Ghostscript</glossseealso
+> <glossseealso otherterm="gloss-postscript"
+>&PostScript;</glossseealso
+> <glossseealso otherterm="gloss-raster"
+>Raster</glossseealso
+> </glossdef>
+                </glossentry>
+
+                <glossentry id="gloss-pjl">
+                        <glossterm
+><acronym
+>PJL</acronym
+></glossterm>
+                        <glossdef
+><para
+>Abbreviation for <emphasis
+>P</emphasis
+>rint <emphasis
+>J</emphasis
+>ob <emphasis
+>L</emphasis
+>anguage; developed by &HP; to control and influence default and per-job settings of a printer. It may not only be used for &HP;'s own (PCL-)printers; also many &PostScript; and other printers understand PJL commands sent to them inside a print job, or in a separate signal.</para>
+                                <glossseealso otherterm="gloss-pcl"
+>PCL</glossseealso>
+                        </glossdef>
+                </glossentry>
+
+                <glossentry id="gloss-postscript">
+                        <glossterm
+>&PostScript;</glossterm>
+                        <glossdef
+><para
+>&PostScript; (often shortened to "PS") is the de-facto standard in the &UNIX; world for printing files. It was developed by Adobe and licensed to printer manufacturers and software companies. As the &PostScript; specifications were published by Adobe, there are also "Third Party" implementations of &PostScript; generating and &PostScript; interpreting software available (one of the best-known in the Free software world being Ghostscript, a powerful PS-interpreter). </para>
+<glossseealso otherterm="gloss-escp"
+>ESC/P</glossseealso
+> <glossseealso otherterm="gloss-hpgl"
+>&HP;/GL</glossseealso
+> <glossseealso otherterm="gloss-pcl"
+>PCL</glossseealso
+> <glossseealso otherterm="gloss-ppd"
+>PPD</glossseealso
+> </glossdef>
+                </glossentry>
+
+                <glossentry id="gloss-ppd">
+                        <glossterm
+><acronym
+>PPD</acronym
+></glossterm>
+                        <glossdef
+><para
+>Abbreviation for <emphasis
+>P</emphasis
+>ostScript <emphasis
+>P</emphasis
+>rinter <emphasis
+>D</emphasis
+>escription; PPDs are ASCII files storing all information about the special capabilities of a printer, plus definitions of the (PostScript- or PJL-) commands to call on a certain capability (like print duplexing). As the explanation of the acronym reveals, PPDs were originally only used for &PostScript; printers. &CUPS; has extended the PPD concept to all types of printers. PPDs for &PostScript; printers are provided by the printer vendors. They can be used with &CUPS; and KDEPrint to have access to the full features of any &PostScript; printer. The KDEPrint Team recommends using a PPD originally intended for use with &Microsoft; Windows NT. PPDs for non-PostScript printers <emphasis
+>need</emphasis
+> a companion "filter" to process the &PostScript; print files into a format digestible for the non-PostScript target device. Those PPD/filter combos are not (yet) available from the vendors. After the initiative by the &CUPS; developers to utilise PPDs, the Free Software community was creative enough to quickly come up with support for most of the currently used printer models, through PPDs and classical Ghostscript filters. But note: the printout quality varies from "hi-quality photographic output" (using Gimp-Print with most Epson inkjets) to "hardly readable" (using Foomatic-enabled Ghostscript filters for models rated as "paperweight" in the Linuxprinting.org database). </para>
+<glossseealso otherterm="gloss-cups"
+>&CUPS;</glossseealso
+> <glossseealso otherterm="gloss-linuxprintingorg"
+>Linuxprinting.org</glossseealso
+> <glossseealso otherterm="gloss-postscript"
+>&PostScript;</glossseealso
+> </glossdef>
+                </glossentry>
+
+                <glossentry id="gloss-PPD-O-Matic">
+                        <glossterm
+>PPD-O-Matic</glossterm>
+                        <glossdef
+><para
+>PPD-O-Matic is a set of Perl scripts that run on the Linuxprinting.org web server and can be used online to generate PPDs for any printer that is known to print with Ghostscript. These PPDs can be hooked up to &CUPS;/KDEPrint, as well as used inside PPD-aware applications like StarOffice to determine all different parameters of your printjobs. It is now recommended, in most cases, to use "PPD-O-Matic" instead of the older &CUPS;-O-Matic. To generate a PPD, go to the <ulink url="http://www.linuxprinting.org/printer_list.cgi"
+>printer database</ulink
+>, select your printer model, follow the link to show the available Ghostscript filters for that printer, select one, click "generate" and finally save the file to your local system. Be sure to read the instructions. Make sure that your local system does indeed have Ghostscript and the filter, which you chose before generating the PPD, installed. </para>
+<glossseealso otherterm="gloss-postscript"
+>&PostScript;</glossseealso
+> <glossseealso otherterm="gloss-cups-o-matic"
+>&CUPS;-O-Matic</glossseealso
+> <glossseealso otherterm="gloss-linuxprintingorg"
+>Linuxprinting.org</glossseealso
+> <glossseealso otherterm="gloss-foomatic"
+>Foomatic</glossseealso
+> </glossdef>
+                </glossentry>
+
+                <glossentry id="gloss-printcap">
+                        <glossterm
+>printcap</glossterm>
+                        <glossdef
+><para
+>In BSD-style print systems, the "printcap" file holds the configuration information; the printing daemon reads this file to determine which printers are available, what filters are to be user for each, where the spooling folder is located, if there are banner pages to be used, and so on... Some applications also depend on read access to the printcap file, to obtain the names of available printers. </para>
+                                <glossseealso otherterm="gloss-bsdstyleprinting"
+>BSD-style printing</glossseealso>
+                        </glossdef>
+                </glossentry>
+  
+
+                <glossentry id="gloss-printermib">
+                        <glossterm
+>Printer-<acronym
+>MIB</acronym
+></glossterm>
+                        <glossdef
+><para
+>Abbreviation for <emphasis
+>Printer</emphasis
+>-<emphasis
+>M</emphasis
+>anagement <emphasis
+>I</emphasis
+>nformation <emphasis
+>B</emphasis
+>ase; the Printer-MIB defines a set of parameters that are to be stored inside the printer for access through the network. This is useful if many (in some cases, literally thousands) network printers are managed centrally with the help of SNMP (Simple Network Management Protocol).</para>
+<glossseealso otherterm="gloss-pwg"
+>PWG</glossseealso
+> <glossseealso otherterm="gloss-snmp"
+>SNMP</glossseealso
+> </glossdef>
+                </glossentry>
+  
+                <glossentry id="gloss-pwg">
+                        <glossterm
+><acronym
+>PWG</acronym
+></glossterm>
+                        <glossdef
+><para
+>Abbreviation for <emphasis
+>P</emphasis
+>rinter <emphasis
+>W</emphasis
+>orking <emphasis
+>G</emphasis
+>roup; the PWG is a loose grouping of representatives of the printer industry that has, in the past years, developed different standards in relation to network printing. These were later accepted by the IETF as RFC standards, like the "Printer-MIB" and the IPP.</para>
+<glossseealso otherterm="gloss-postscript"
+>&PostScript;</glossseealso
+> <glossseealso otherterm="gloss-ipp"
+>IPP</glossseealso
+> <glossseealso otherterm="gloss-printermib"
+>Printer-MIB</glossseealso
+> <glossseealso otherterm="gloss-snmp"
+>SNMP</glossseealso
+> </glossdef>
+                </glossentry>
+
+                <glossentry id="gloss-printkioslave">
+                        <glossterm
+>print:/ KIO Slave</glossterm>
+                        <glossdef
+><para
+>You can use a syntax of "print:/..." to get quick access to KDEPrint resources. Typing "print:/manager" as a Konqueror URL address gives administrative access to KDEPrint. Konqueror uses &kde;'s famous "KParts" technology to achieve that. </para>
+<glossseealso otherterm="gloss-ioslave"
+>IO Slave</glossseealso
+> <glossseealso otherterm="gloss-kparts"
+>KParts</glossseealso
+> </glossdef>
+                </glossentry>
+
+
+                <glossentry id="gloss-printerdatabase">
+                        <glossterm
+>Printer Database</glossterm>
+                        <glossdef
+><para
+>.</para>
+                                <glossseealso otherterm="gloss-linuxprintingdatabase"
+>Linuxprinting Database</glossseealso>
+                        </glossdef>
+                </glossentry>
+
+                <glossentry id="gloss-qtcups">
+                        <glossterm
+><acronym
+>Qt&CUPS;</acronym
+></glossterm>
+                        <glossdef
+><para
+>Qt&CUPS; and KUPS were the predecessors of KDEPrint; they are now deprecated and no longer maintained. What was good in qtcups is all inherited by "kprinter", the new KDE print dialogue (which is much improved over qtcups); what you liked about kups is now all in the KDEPrint Manager (accessible via the KDE Control Centre or via the URL "print:/manager" from Konqueror) -- with more functionality and less bugs... Its former developer, Michael Goffioul, is now the developer of KDEPrint -- a very nice and productive guy and quick bug fixer... </para>
+                                <glossseealso otherterm="gloss-kprinter"
+>kprinter</glossseealso>
+                        </glossdef>
+                </glossentry>
+
+                <glossentry id="gloss-raster">
+                        <glossterm
+>Raster Image</glossterm>
+                        <glossdef
+><para
+>Every picture on a physical medium is composed of a pattern of discrete dots in different colours and (maybe) sizes. This is called a "raster image". This is as opposed to a "vector image" where the graphic is described in terms of continuous curves, shades, forms and filled areas, represented by mathematical formula. Vector images normally have a smaller file size and may be scaled in size without any loss of information and quality --- but they cannot be output directly, but always have to be "rendered" or "rasterised" first to the given resolution that the output device is capable of... The rasterisation is done by a Raster Image Processor (RIP, often the Ghostscript software) or some other filtering instance.</para>
+<glossseealso otherterm="gloss-pixel"
+>Pixel</glossseealso
+> <glossseealso otherterm="gloss-ghostscript"
+>Ghostscript</glossseealso
+> <glossseealso otherterm="gloss-postscript"
+>&PostScript;</glossseealso
+> <glossseealso otherterm="gloss-filter"
+>Filter</glossseealso
+> <glossseealso otherterm="gloss-rip"
+>RIP</glossseealso
+> </glossdef>
+                </glossentry>
+
+                <glossentry id="gloss-rip">
+                        <glossterm
+><acronym
+>RIP</acronym
+></glossterm>
+                        <glossdef
+><para
+>Abbreviation for <emphasis
+>R</emphasis
+>aster <emphasis
+>I</emphasis
+>mage <emphasis
+>P</emphasis
+>rocess(or); if used in the context of printing, "RIP" means a hardware or software instance that converts &PostScript; (or other print formats that are represented in one of the non-Raster PDLs) into a raster image format in such a way that it is acceptable for the "marking engine" of the printer. &PostScript; printers contain their own PostScript-RIPs. A RIP may or may not be located inside a printer. For many &UNIX; systems, Ghostscript is the package that provides a "RIP in software", running on the host computer, and pre-digesting the &PostScript; or other data to become ready to be sent to the printing device (hence you may perceive a "grain of truth" in the slogan "Ghostscript turns your printer into a &PostScript; machine", which of course is not correct in the true sense of the meaning).</para>
+<glossseealso otherterm="gloss-filter"
+>Filter</glossseealso
+> <glossseealso otherterm="gloss-ghostscript"
+>Ghostscript</glossseealso
+> <glossseealso otherterm="gloss-postscript"
+>&PostScript;</glossseealso
+> <glossseealso otherterm="gloss-pdl"
+>PDL</glossseealso
+> <glossseealso otherterm="gloss-raster"
+>Raster</glossseealso
+> </glossdef>
+                </glossentry>
+
+
+                <glossentry id="gloss-rlpr">
+                        <glossterm
+><acronym
+>RLPR</acronym
+> (Remote LPR)</glossterm>
+                        <glossdef
+><para
+>Abbreviation for <emphasis
+>R</emphasis
+>emote <emphasis
+>L</emphasis
+>ine <emphasis
+>P</emphasis
+>rinting <emphasis
+>R</emphasis
+>equest; this is a BSD-style printing system, that needs no root privileges to be installed, and no "printcap" to work: all parameters may be specified on the command line. RLPR comes in handy for many laptop users who are working in frequently changing environments. This is because it may be installed concurrently with every other printing sub system, and allows a very flexible and quick way to install a printer for direct access via LPR/LPD. KDEPrint has an "Add Printer Wizard" to make RLPR usage even easier. The kprinter command allows switching to RLPR "on the fly" at any time.</para>
+<glossseealso otherterm="gloss-tdeprint"
+>KDEPrint</glossseealso
+> <glossseealso otherterm="gloss-kprinter"
+>kprinter</glossseealso
+> <glossseealso otherterm="gloss-printcap"
+>printcap</glossseealso
+> </glossdef>
+                </glossentry>
+
+ 
+                <glossentry id="gloss-snmp">
+                        <glossterm
+><acronym
+>SNMP</acronym
+></glossterm>
+                        <glossdef
+><para
+>Abbreviation for <emphasis
+>S</emphasis
+>imple <emphasis
+>N</emphasis
+>etwork <emphasis
+>M</emphasis
+>anagement <emphasis
+>P</emphasis
+>rotocol; SNMP is widely used to control all types of network node (Hosts, Routers, Switches, Gateways, Printers...) remotely.</para>
+<glossseealso otherterm="gloss-pwg"
+>PWG</glossseealso
+> <glossseealso otherterm="gloss-printermib"
+>Printer-MIB</glossseealso
+> </glossdef>
+                </glossentry>
+
+	        <glossentry id="gloss-ssl">
+                        <glossterm
+><acronym
+>SSL(3)</acronym
+> encryption</glossterm>
+                        <glossdef
+><para
+>Abbreviation for <emphasis
+>S</emphasis
+>ecure <emphasis
+>S</emphasis
+>ocket <emphasis
+>L</emphasis
+>ayer; <acronym
+>SSL</acronym
+> is a proprietary encryption method for data transfer over HTTP that was developed by Netscape. It is now being replaced by an IETF standard named TLS. </para>
+                                <glossseealso otherterm="gloss-tls"
+><acronym
+>TLS</acronym
+></glossseealso>
+                        </glossdef>
+                </glossentry>
+
+
+	        <glossentry id="gloss-spooling">
+                        <glossterm
+><acronym
+>SPOOL</acronym
+>ing</glossterm>
+                        <glossdef
+><para
+>Abbreviation for <emphasis
+>S</emphasis
+>ynchronous <emphasis
+>P</emphasis
+>eripheral <emphasis
+>O</emphasis
+>perations <emphasis
+>O</emphasis
+>n<emphasis
+>L</emphasis
+>ine; <acronym
+>SPOOL</acronym
+>ing enables printing applications (and users) to continue their work as the job is being taken care of by a system <acronym
+>daemon</acronym
+>, which stores the file at a temporary location until the printer is ready to print. </para>
+                                <glossseealso otherterm="gloss-daemon"
+><acronym
+>Daemon</acronym
+></glossseealso>
+                        </glossdef>
+                </glossentry>
+
+
+	        <glossentry id="gloss-tls">
+                        <glossterm
+><acronym
+>TLS</acronym
+> encryption</glossterm>
+                        <glossdef
+><para
+>Abbreviation for <emphasis
+>T</emphasis
+>ransport <emphasis
+>L</emphasis
+>ayer <emphasis
+>S</emphasis
+>ecurity; <acronym
+>TLS</acronym
+> is an encryption standard for data transfered over HTTP 1.1; it is defined in RFC 2246; although based on the former SSL development (from Netscape) it is not fully compatible with it. </para>
+                                <glossseealso otherterm="gloss-ssl"
+><acronym
+>SSL(3)</acronym
+></glossseealso>
+                        </glossdef>
+                </glossentry>
+
+
+	        <glossentry id="gloss-systemVstyleprinting">
+                        <glossterm
+>System V-style printing</glossterm>
+                        <glossdef
+><para
+>This is the second flavour of traditional &UNIX; printing (as opposed to BSD-style printing). It uses a different command set (lp, lpadmin,...) to BSD, but is not fundamentally different from it. However, the gap between the two is big enough to make the two incompatible, so that a BSD-client cannot simply print to a System V style print server without additional tweaking... IPP is supposed to resolve this weakness and more. </para>
+<glossseealso otherterm="gloss-bsdstyleprinting"
+><acronym
+>BSD-style printing</acronym
+></glossseealso
+> <glossseealso otherterm="gloss-ipp"
+><acronym
+>IPP</acronym
+></glossseealso
+> </glossdef>
+                </glossentry>
+
+                <glossentry id="gloss-turboprint">
+                        <glossterm
+>TurboPrint</glossterm>
+                        <glossdef
+><para
+>Shareware software providing photo quality printing for many inkjet printers. It is useful if you are unable to find a driver for your printer and may be hooked into either a traditional Ghostscript system or a modern &CUPS; system.</para>
+                                <glossseealso otherterm="gloss-gimpprint"
+>Gimp-Print</glossseealso>
+                        </glossdef>
+                </glossentry>
+
+                <glossentry id="gloss-xpp">
+                        <glossterm
+><acronym
+>XPP</acronym
+></glossterm>
+                        <glossdef
+><para
+>Abbreviation for <emphasis
+>X</emphasis
+> <emphasis
+>P</emphasis
+>rinting <emphasis
+>P</emphasis
+>anel; <acronym
+>XPP</acronym
+> was the first Free graphical print command for &CUPS;, written by Till Kamppeter, and in some ways a model for the "kprinter" utility in &kde;.</para>
+                        </glossdef>
+                </glossentry>
+<!--
+                <glossentry id="gloss-1">
+                        <glossterm
+>xxxx</glossterm>
+                        <glossdef
+><para
+>.</para>
+                                <glossseealso otherterm="gloss-1"
+>xyz</glossseealso>
+                        </glossdef>
+                </glossentry>
+
+                <glossentry id="gloss-3">
+                        <glossterm
+>xxxx</glossterm>
+                        <glossdef
+><para
+>.</para>
+                                <glossseealso otherterm="gloss-1"
+>xyz</glossseealso>
+                        </glossdef>
+                </glossentry>
+
+                <glossentry id="gloss-4">
+                        <glossterm
+>xxxx</glossterm>
+                        <glossdef
+><para
+>.</para>
+                                <glossseealso otherterm="gloss-1"
+>xyz</glossseealso>
+                        </glossdef>
+                </glossentry>
+-->
+	</glossdiv>
+
+
+<!--
+</glossary>
+-->
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/help.docbook b/tde-i18n-en_GB/docs/tdebase/khelpcenter/help.docbook
new file mode 100644
index 00000000000..372573d1e1b
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/help.docbook
@@ -0,0 +1,963 @@
+<chapter id="help-system-user-manual">
+<chapterinfo
+><date
+>2002-02-03</date
+> <releaseinfo
+>0.08.00</releaseinfo
+> </chapterinfo>
+<title
+>&kde; Help System User Manual</title>
+<anchor id="help"/>
+
+<sect1 id="help-introduction">
+<title
+>&kde; Help System</title>
+	
+<para
+>The &kde; help system is designed to make accessing the common &UNIX; help systems (<application
+>man</application
+> and <application
+>info</application
+>) simple, as well as the native &kde; documentation (&XML;). </para>
+	
+<para
+>All base &kde; applications come fully documented, thanks to the efforts of the Documentation team. If you would like to help, please write to the Documentation coordinator, Lauri Watts, at <email
+>lauri@kde.org</email
+> for information. No experience is required, just enthusiasm and patience. </para>
+
+<para
+>If you would like to help translating &kde; documentation to your native language, the Translation coordinator is Thomas Diehl, <email
+>thd@kde.org</email
+>, and he would also welcome the help. More information, including the coordinators for each language team, can be found on the <ulink url="http://i18n.kde.org"
+>Internationalisation web site</ulink
+>, and in the <link linkend="contact"
+>Contact</link
+> section of this document. </para>
+
+<sect2 id="installation">
+<title
+>Installation</title>
+
+<para
+>&khelpcenter; is an integral part of the &kde; Base installation, and is installed with every copy of &kde;. It can be found in the tdebase package, and is available from the &kde-ftp;, or will be found in your operating system tdebase package. </para>
+
+</sect2>
+</sect1>
+
+<sect1 id="invoking-help">
+<title
+>Invoking Help</title>
+
+<para
+>&khelpcenter; can be called in several ways: </para>
+
+<variablelist
+> 
+<varlistentry
+> 
+<term
+>From the <guimenu
+>Help</guimenu
+> menu</term
+> 
+<listitem>
+<para
+>The most common will probably be from within an application. Choose <menuchoice
+><guimenu
+>Help</guimenu
+> <guimenuitem
+>Contents</guimenuitem
+></menuchoice
+> to open that application's help file, at the contents page. </para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+>From the <guimenu
+>K</guimenu
+> menu</term>
+<listitem>
+<para
+>Choose the big <guiicon
+>K</guiicon
+> in your panel, and select <guimenuitem
+>Help</guimenuitem
+> to open &khelpcenter;, starting at the default welcome page. </para>
+</listitem
+> 
+</varlistentry>
+
+<varlistentry>
+<term
+>From the panel</term>
+<listitem>
+<para
+>By default, the &kicker; panel contains an icon to call &khelpcenter;. Again, the default welcome page is displayed. </para>
+</listitem
+> 
+</varlistentry>
+
+<varlistentry>
+<term
+>From the command line</term>
+<listitem>
+<para
+>&khelpcenter; may be started using a &URL; to display a file. &URL;s have been added for <command
+>info</command
+> and <command
+>man</command
+> pages also. You can use them as follows: </para
+> 
+
+<variablelist>
+<varlistentry>
+<term
+>An application help file</term>
+<listitem>
+<para
+><command
+>khelpcenter</command
+> <option
+>help:/<replaceable
+>kedit</replaceable
+></option
+> </para>
+<para
+>Opens the &kedit; help file, at the contents page. </para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+>A local &URL;</term>
+<listitem
+><para
+><command
+>khelpcenter</command
+> <option
+>file:/ <replaceable
+>usr/local/src/qt/html/index.html</replaceable
+></option
+> </para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+>A Man page</term>
+<listitem>
+<para
+><command
+>khelpcenter</command
+> <option
+>man:/<replaceable
+>strcpy</replaceable
+></option
+> </para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+>An Info page</term>
+<listitem>
+<para
+><command
+>khelpcenter</command
+> <option
+>info:/<replaceable
+>gcc</replaceable
+></option
+> </para>
+</listitem>
+</varlistentry>
+</variablelist>
+
+<para
+>Invoking <command
+>khelpcenter</command
+> with no parameters opens the default welcome page. </para>
+</listitem>
+</varlistentry>
+
+</variablelist>
+</sect1>
+
+<sect1 id="interface-basics">
+<title
+>The &khelpcenter; interface</title>
+
+<para
+>The &khelpcenter; interface consists of two panes of information. </para>
+
+<para
+>The toolbar and menus are explained further in <xref linkend="menu-and-toolbar-ref"/>. </para>
+
+<para
+>Documents contain their own navigation tools, enabling you to move either sequentially through a document, using <guilabel
+>Next</guilabel
+>, <guilabel
+>Previous</guilabel
+>, and <guilabel
+>Home</guilabel
+> links, or to move around in a less structured manner, using hyperlinks. </para>
+
+<para
+>Links can take you to other parts of the same document, or to a different document, and you can use the <guiicon
+>Back</guiicon
+> (Left pointing arrow) or <guiicon
+>Forward</guiicon
+> (Right pointing arrow) icons on the toolbar to move through the documents you have viewed in this session. </para
+> 
+
+<para
+>The two panes display the contents of the help system, and the help files themselves, on the left and right respectively. </para>
+
+<sect2 id="contents-pane">
+<title
+>The <guilabel
+>Contents</guilabel
+> pane</title>
+
+<para
+>The <guilabel
+>Contents</guilabel
+> pane in &khelpcenter; is displayed on the left hand side of the window. As you might expect, you can move the splitter bar, to make sure you can comfortably read the contents of either pane. </para
+> 
+
+<para
+>The <guilabel
+>Contents</guilabel
+> pane is further divided into two tabs, one containing a <link linkend="contents-menu"
+>menu</link
+> showing all the help information &khelpcenter; is aware of, and the other contains the &kde; <link linkend="kde-glossary"
+>glossary</link
+> of terms. </para>
+
+<sect3 id="contents-menu">
+<title
+>The <guilabel
+>Contents</guilabel
+> Menu</title>
+
+<para
+>The <guilabel
+>Contents</guilabel
+> contains the following default entries: </para
+> 
+
+<variablelist>
+<varlistentry>
+<term
+><guilabel
+>Introduction</guilabel
+></term>
+<listitem
+><para
+>Welcome to &kde; - an introduction to the K Desktop Environment.</para
+></listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+><guilabel
+>Introduction to &kde;</guilabel
+></term>
+<listitem>
+<para
+>The &kde; Quickstart guide. Contains a tour of the &kde; Interface and specific help and tips on how to work smarter with &kde;. </para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+><guilabel
+>&kde; User's manual</guilabel
+></term>
+<listitem>
+<para
+>The &kde; User's manual is an in-depth exploration of &kde;, including installation, configuration and customisation, and use. </para>
+</listitem
+> 
+</varlistentry>
+
+<varlistentry>
+<term
+><guilabel
+>Application manuals</guilabel
+></term>
+<listitem>
+<para
+>Native &kde; application documentation. All &kde; applications have documentation in &XML; format, which are converted to <acronym
+>HTML</acronym
+> when you view them. This section lists all the &kde; applications with a brief description and a link to the full application documentation. </para>
+<para
+>The applications are displayed in a tree structure that echoes the default structure of the <guimenu
+>K</guimenu
+> menu, making it easy to find the application you are looking for. </para>
+</listitem
+> 
+</varlistentry>
+
+<varlistentry>
+<term
+><guilabel
+>&UNIX; manual pages</guilabel
+></term>
+<listitem>
+<para
+>&UNIX; man pages are the traditional on-line documentation format for &UNIX; systems. Most programs on your system will have a man page. In addition, man pages exist for programming functions and file formats. </para>
+</listitem
+> 
+</varlistentry>
+
+<varlistentry>
+<term
+><guilabel
+>Browse info pages</guilabel
+></term>
+<listitem>
+<para
+>TeXinfo documentation is used by many &GNU; applications, including <command
+>gcc</command
+> (the C/C++ compiler), <command
+>emacs</command
+>, and many others. </para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+><guilabel
+>Tutorials</guilabel
+></term>
+<listitem>
+<para
+>Short, task based or informational tutorials. </para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+><guilabel
+>The &kde; FAQ</guilabel
+></term>
+<listitem>
+<para
+>Frequently asked questions about &kde;, and their answers. </para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+><guilabel
+>&kde; on the web</guilabel
+></term>
+<listitem>
+<para
+>Links to &kde; on the web, both the official &kde; website, and other useful sites. </para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+><guilabel
+>Contact Information</guilabel
+></term>
+<listitem>
+<para
+>Information on how to contact &kde; developers, and how to join the &kde; mailing lists. </para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+><guilabel
+>Supporting &kde;</guilabel
+></term>
+<listitem>
+<para
+>How to help, and how to get involved. </para>
+</listitem>
+</varlistentry>
+</variablelist>
+
+</sect3>
+<!-- 
+<sect3 id="search">
+<title
+>The <guilabel
+>Search</guilabel
+> tab</title>
+
+<para>
+Searching requires you have the <application
+>ht://Dig</application>
+application installed.  Information on installing and configuring the
+search index is available in the document.  Configuration of the search
+index is performed in the &kcontrol;, by choosing
+<menuchoice
+><guisubmenu
+>Help</guisubmenu
+><guimenuitem
+>Index</guimenuitem
+></menuchoice
+>,
+and detailed help is available from this module.
+</para>
+
+<para>
+For the purposes of this document, we'll assume you already have this set
+up and configured.
+</para>
+
+<para>
+Searching the help files is fairly intuitive, enter the word(s) you wish
+to search for in the text box, choose your options (if any), and press
+<guibutton
+>Search</guibutton
+>.  The results display in the viewer pane
+to the right.
+</para>
+
+<para
+>The options available are:</para>
+
+<variablelist>
+<varlistentry>
+<term
+><guilabel
+>Method</guilabel
+></term>
+<listitem>
+<para>
+Choose how to search for multiple words.  If you choose
+<guilabel
+>and</guilabel
+>, results are returned only if all your search
+terms are included in the page. <guilabel
+>or</guilabel
+> returns results
+if <emphasis
+>any</emphasis
+> of the search terms are found, and
+<guilabel
+>boolean</guilabel
+> lets you search using a combination.
+</para
+> 
+<para>
+Boolean syntax lets you use the operators <literal
+>AND</literal
+>,
+<literal
+>OR</literal
+> and <literal
+>NOT</literal
+> to create complex
+searches. Some examples:</para>
+<variablelist>
+<varlistentry>
+<term
+><userinput
+>cat and dog</userinput
+></term>
+<listitem
+><para
+>Searches for pages which have both the words
+<userinput
+>cat</userinput
+> and <userinput
+>dog</userinput
+> in them.  Pages with
+only one or the other will not be returned.</para
+></listitem>
+</varlistentry>
+<varlistentry>
+<term
+><userinput
+>cat not dog</userinput
+></term>
+<listitem
+><para
+>Searches for pages with <userinput
+>cat</userinput
+> in them, but
+only returns the ones that don't have the word <userinput
+>dog</userinput
+> in
+them.</para
+></listitem>
+</varlistentry>
+<varlistentry>
+<term
+><userinput
+>cat or (dog not nose)</userinput
+></term>
+<listitem
+><para
+>Searches for pages which contain <userinput
+>cat</userinput
+>, and
+for pages which contain <userinput
+>dog</userinput
+> but don't contain
+<userinput
+>nose</userinput
+>.  Pages which contain both
+<userinput
+>cat</userinput
+> and <userinput
+>nose</userinput
+> would be returned,
+pages containing all three words would not.</para
+></listitem
+> 
+</varlistentry>
+</variablelist>
+<para
+>If your searches are not returning the results you expect, check
+carefully you haven't excluded the wrong search term with an errand
+<literal
+>NOT</literal
+> or a stray brace.</para
+></listitem>
+</varlistentry>
+<varlistentry>
+<term
+><guilabel
+>Max. results</guilabel
+></term>
+<listitem
+><para
+>Determines the maximum number of results returned from your
+search.</para
+></listitem>
+</varlistentry>
+<varlistentry>
+<term
+><guilabel
+>Format</guilabel
+></term>
+<listitem
+><para
+>Decide if you want just a short link to the page
+containing your search terms, or do you want a longer
+summary.</para
+></listitem
+> 
+</varlistentry>
+<varlistentry>
+<term
+><guilabel
+>Sort</guilabel
+></term>
+<listitem
+><para
+>Sort the results in order of <guilabel
+>Score</guilabel
+> (how
+closely your search terms were matched,) alphabetically by
+<guilabel
+>Title</guilabel
+> or by <guilabel
+>Date</guilabel
+>.  Selecting the
+<guilabel
+>Reverse order</guilabel
+> check box, naturally enough, reverses the
+sort order of the results.</para
+></listitem>
+</varlistentry>
+<varlistentry>
+<term
+><guilabel
+>Update index</guilabel
+></term>
+<listitem
+><para
+>Update the search index, to incorporate new documents,
+or if you think your database is incomplete or damaged.  This may take
+some time.</para
+></listitem>
+</varlistentry>
+</variablelist>
+</sect3>
+-->
+
+</sect2>
+
+<sect2 id="man-and-info">
+<title
+>The <application
+>Man</application
+> and <application
+>Info</application
+> sections</title>
+
+<para
+>Man pages are the standard &UNIX; manual pages, and have been in use for many years on many operating systems. They are extremely thorough, and are the very best place to get information about most &UNIX; commands and applications. When people say <quote
+>RTFM</quote
+>, the Manual they are referring to is very often the man page.</para>
+
+<para
+>The man pages are not perfect. They tend to be in depth, but also extremely technical, often written by developers, and for developers. In some cases this makes them somewhat unfriendly, if not downright impossible for many users to understand. They are, however, the best source of solid information on most command line applications, and very often the only source.</para>
+
+<para
+>If you've ever wondered what the number is when people write things like man(1) it means which section of the manual the item is in. You will see &khelpcenter; uses the numbers to divide the very many man pages into their own sections, making it easier for you to find the information you're looking for, if you're just browsing.</para>
+
+<para
+>Also available are the Info pages, intended to be a replacement for the man pages. The maintainer of some applications no longer update the man pages, so if there is both a man page and an info page available, the info page is probably the most recent. Most applications have one or the other though. If the application you are looking for help on is a &GNU; utility, you will most likely find it has an info page, not a man page.</para>
+
+<sect3 id="navigation">
+<title
+>Navigating inside the <application
+>Info</application
+> pages</title>
+
+<para
+>Info documents are arranged hierarchically with each page called a node. All info documents have a <guilabel
+>Top</guilabel
+> node, &ie; the opening page. You can return to the <guilabel
+>Top</guilabel
+> of an info document by pressing <guilabel
+>Top</guilabel
+>.</para>
+
+<para
+><guibutton
+>Prev</guibutton
+> &amp; <guibutton
+>Next</guibutton
+> are used to move to the previous/next page at the current level of the hierarchy.</para>
+
+<para
+>Clicking on a menu item within a document moves you to a lower level in the hierarchy. You may move up the hierarchy by pressing <guibutton
+>Up</guibutton
+>.</para>
+
+<para
+>Man is treated similarly to info, with the section index being the Top node and each man page on the level below. Man entries are one page long.</para>
+
+</sect3>
+</sect2>
+
+<sect2 id="kde-glossary">
+<title
+>The &kde; glossary</title>
+
+<para
+>The glossary provides a quick reference point, where you can look up the definitions of words that may be unfamiliar to you. These range from &kde; specific applications and technologies, through to general &UNIX; computing terms. </para>
+
+<para
+>In the left hand pane you will see a tree view, with two choices: <guilabel
+>Alphabetically</guilabel
+> or <guilabel
+>By topic</guilabel
+>. Both contain the same entries, sorted differently, to allow you to quickly find the item of interest. </para>
+
+<para
+>Navigate down the tree views to the left, and items you select will be displayed on the right. </para>
+
+</sect2>
+
+<sect2 id="menu-and-toolbar-ref">
+<title
+>The menus and toolbar</title>
+
+<para
+>&khelpcenter; has a very minimal interface, allowing you to concentrate on getting help rather than learning how to use the help browser. </para>
+
+<para
+>The icons available to you in the toolbar are as follows: </para>
+
+<variablelist>
+<title
+>Toolbar Icons</title>
+
+<varlistentry>
+
+<term
+><guiicon
+>Back</guiicon
+></term>
+<listitem>
+<para
+>Go to the previous page you viewed.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+><guiicon
+>Forward</guiicon
+></term>
+<listitem>
+<para
+>Go forward one page. This icon is only active if you have already used the <guiicon
+>Back</guiicon
+> icon.</para
+></listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+><guiicon
+>Print</guiicon
+></term>
+<listitem>
+<para
+>Print the contents of the currently visible page. </para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+><guiicon
+>Find</guiicon
+></term>
+<listitem>
+<para
+>Find a word or words within the currently visible page. </para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+><guiicon
+>Increase Font</guiicon
+></term>
+<listitem>
+<para
+>Increase the size of the text in the viewer pane. </para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+><guiicon
+>Decrease Font</guiicon
+></term>
+<listitem>
+<para
+>Decrease the size of the text in the viewer pane. This icon is only enabled if you have previously enlarged the text. </para>
+</listitem>
+</varlistentry>
+
+</variablelist>
+
+<para
+>The menus contain the following entries: </para>
+
+<variablelist>
+<varlistentry>
+<term
+><guimenu
+>File</guimenu
+></term>
+<listitem>
+
+<variablelist>
+<varlistentry>
+<term>
+<menuchoice
+><guimenu
+>File</guimenu
+> <guimenuitem
+>Print...</guimenuitem
+> </menuchoice>
+</term>
+<listitem>
+<para
+>Print the contents of the currently visible page. </para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term>
+<menuchoice
+><shortcut
+> <keycombo action="simul"
+>&Ctrl;<keycap
+>Q</keycap
+></keycombo
+> </shortcut
+> <guimenu
+>File</guimenu
+> <guimenuitem
+>Quit</guimenuitem
+> </menuchoice>
+</term>
+<listitem>
+<para
+>Close and exit &khelpcenter; </para>
+</listitem>
+</varlistentry>
+</variablelist>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+><guimenu
+>Edit</guimenu
+></term>
+<listitem>
+
+<variablelist>
+<varlistentry>
+<term
+><menuchoice
+><shortcut
+> <keycombo action="simul"
+>&Ctrl;<keycap
+>A</keycap
+></keycombo
+></shortcut
+> <guimenu
+>Edit</guimenu
+> <guimenuitem
+>Select All</guimenuitem
+> </menuchoice>
+</term>
+<listitem>
+<para
+>Select all the text in the current page. </para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+><menuchoice
+><shortcut
+> <keycombo action="simul"
+>&Ctrl;<keycap
+>F</keycap
+></keycombo
+></shortcut
+> <guimenu
+>Edit</guimenu
+> <guimenuitem
+>Find...</guimenuitem
+> </menuchoice>
+</term>
+<listitem>
+<para
+>Find a word or words in the currently visible page. </para>
+</listitem>
+</varlistentry>
+</variablelist>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+><guimenu
+>View</guimenu
+></term>
+<listitem>
+<variablelist>
+<varlistentry>
+<term
+><menuchoice
+><guimenu
+>View</guimenu
+> <guimenuitem
+>View Document Source</guimenuitem
+> </menuchoice>
+</term>
+<listitem>
+<para
+>View the <acronym
+>HTML</acronym
+> source of the page you are currently viewing. </para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+><menuchoice
+><guimenu
+>View</guimenu
+> <guisubmenu
+>Set Encoding</guisubmenu
+> </menuchoice>
+</term>
+<listitem>
+<para
+>Change the encoding of the current page. Normally, the default setting of <guimenuitem
+>Auto</guimenuitem
+> should be sufficient, but if you are having problems viewing pages written in languages other than English, you may need to choose a specific encoding in this menu. </para>
+</listitem>
+</varlistentry>
+</variablelist>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+><menuchoice
+><guimenu
+>Go</guimenu
+> <guimenuitem
+>Back</guimenuitem
+></menuchoice
+></term>
+<listitem>
+<para
+>Go back to the previous page you were viewing.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+><menuchoice
+><guimenu
+>Go</guimenu
+> <guimenuitem
+>Forward</guimenuitem
+> </menuchoice
+></term>
+<listitem>
+<para
+>If you have previously moved back with the back icon or menu entry, you can work your way forward again with this menu entry.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+><menuchoice
+><guimenu
+>Go</guimenu
+> <guimenuitem
+>...</guimenuitem
+> </menuchoice
+></term>
+<listitem>
+<para
+>At the bottom of the <guimenu
+>Go</guimenu
+> menu, you will find a history list, of the last few pages you have looked at. Selecting one will take you directly back to that page.</para>
+</listitem
+></varlistentry
+></variablelist>
+
+</sect2>
+
+</sect1>
+
+<sect1 id="credits">
+<title
+>Credits and Licences</title>
+
+<para
+>&khelpcenter;</para>
+
+<para
+>Originally developed by &Matthias.Elter; &Matthias.Elter.mail;</para>
+<para
+>The current maintainer is &Cornelius.Schumacher; &Cornelius.Schumacher.mail;</para>
+&underFDL; &underGPL; </sect1>
+</chapter>
+
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/index.cache.bz2 b/tde-i18n-en_GB/docs/tdebase/khelpcenter/index.cache.bz2
new file mode 100644
index 00000000000..b150b6b4347
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/index.cache.bz2
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/index.docbook b/tde-i18n-en_GB/docs/tdebase/khelpcenter/index.docbook
new file mode 100644
index 00000000000..96af9959d1b
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/index.docbook
@@ -0,0 +1,107 @@
+<?xml version="1.0" ?>
+<!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" 
+"customization/dtd/kdex.dtd" [
+  <!ENTITY contact SYSTEM "contact.docbook">
+  <!ENTITY help SYSTEM "help.docbook">
+  <!ENTITY support SYSTEM "support.docbook">
+  <!ENTITY whatiskde SYSTEM "whatiskde.docbook">
+  <!ENTITY welcome SYSTEM "welcome.docbook">
+  <!ENTITY quickstart SYSTEM "quickstart/index.docbook" NDATA SGML>
+  <!ENTITY userguide SYSTEM "userguide/index.docbook" NDATA SGML>
+  <!ENTITY faq SYSTEM "faq/index.docbook" NDATA SGML>
+  <!ENTITY kpanel SYSTEM "../kpanel/index.html" NDATA SGML>
+  <!ENTITY kcontrolcenter SYSTEM "../kcontrol/index.html" NDATA SGML>
+  <!ENTITY kfm SYSTEM "../konqueror/index.html" NDATA SGML>
+  <!ENTITY kwm SYSTEM "../kwm/index.html" NDATA SGML>
+  <!ENTITY kde-quickstart-doc SYSTEM "quickstart/index.docbook" NDATA SGML>
+  <!ENTITY kde-userguide-doc SYSTEM "userguide/index.docbook" NDATA SGML>
+  <!ENTITY kde-faq-doc SYSTEM "faq/index.docbook" NDATA SGML>
+  <!-- HTML files will probably only work when they have an olink equivalent 
+available, unless only references to the top page are needed, which is doubtful. 
+
+ To be continued.  (FF) -->
+  <!ENTITY kde-kpanel-doc SYSTEM "../kpanel/index.html" NDATA SGML>
+  <!ENTITY kde-kcontrol-doc SYSTEM "../kcontrol/index.html" NDATA SGML>
+  <!ENTITY kde-kfm-doc SYSTEM "../konqueror/index.html" NDATA SGML>
+  <!ENTITY kde-kwm-doc SYSTEM "../kwm/index.html" NDATA SGML>
+  <!-- ENTITY man SYSTEM "." NDATA LINESPECIFIC
+> - to be changed ; should be 
+the reference to the apropos file in this case, but I cannot really imagine 
+putting all manual pages into FPIs or system identifiers, so we'll have to find 
+a way round it. (FF) -->
+  <!ENTITY kappname "&khelpcenter;">
+  <!ENTITY % British-English "INCLUDE"
+> <!-- change language only here -->
+  <!ENTITY % addindex "IGNORE">
+]>
+
+<book lang="&language;">
+<bookinfo>
+<title
+>The &khelpcenter;</title>
+<authorgroup>
+<corpauthor
+>The &kde; Team</corpauthor>
+<othercredit role="translator"
+><firstname
+>Malcolm</firstname
+><surname
+>Hunter</surname
+><affiliation
+><address
+><email
+>malcolm.hunter@gmx.co.uk</email
+></address
+></affiliation
+><contrib
+>Conversion to British English</contrib
+></othercredit
+> 
+</authorgroup>
+<date
+>2002-01-18</date>
+<releaseinfo
+>3.00.00</releaseinfo>
+
+<abstract>
+<para
+>&kde; is a powerful graphical desktop environment for &UNIX; workstations. A &kde; desktop combines ease of use, contemporary functionality and outstanding graphical design with the technological superiority of the &UNIX; operating system.</para>
+</abstract>
+
+<keywordset>
+<keyword
+>KDE</keyword>
+<keyword
+>tdebase</keyword>
+<keyword
+>khelpcenter</keyword>
+<keyword
+>kdehelp</keyword>
+<keyword
+>help</keyword>
+<keyword
+>help centre</keyword>
+<keyword
+>KDE help centre</keyword>
+</keywordset>
+</bookinfo>
+
+&welcome;
+&help;
+&whatiskde;
+&contact;
+&support;
+
+</book>
+
+<!-- Keep this comment at the end of the file
+Local variables:
+mode: sgml
+sgml-omittag:t
+sgml-shorttag:nil
+sgml-namecase-general:t
+sgml-general-insert-case:lower
+sgml-always-quote-attributes:t
+End:
+-->
+
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/links.docbook b/tde-i18n-en_GB/docs/tdebase/khelpcenter/links.docbook
new file mode 100644
index 00000000000..51e671a605c
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/links.docbook
@@ -0,0 +1,91 @@
+<chapter id="web">
+<chapterinfo>
+<date
+>2000-10-02</date>
+<releaseinfo
+>1.94.00</releaseinfo>
+</chapterinfo>
+<title
+>&kde; on the web</title>
+<anchor id="links"/>
+ 
+<para
+>The K Desktop Environment is developed by a large group of developers around the world. Our main communication channel is the Internet. Please find links to &kde; related web sites on this page.</para>
+
+
+<variablelist
+> <varlistentry
+> <term
+><ulink url="http://www.kde.org"
+>www.kde.org</ulink
+></term
+> <listitem
+><para
+>&kde;'s official website</para
+></listitem
+> </varlistentry
+> <varlistentry
+> <term
+><ulink url="http://kde.themes.org"
+>kde.themes.org</ulink
+></term
+> <listitem
+><para
+>&kde; themes</para
+></listitem
+> </varlistentry
+> <varlistentry
+> <term
+><ulink url="http://developer.kde.org"
+>developer.kde.org</ulink
+></term
+> <listitem
+><para
+>The &kde; developers centre</para
+></listitem
+> </varlistentry
+> <varlistentry
+> <term
+><ulink url="http://webcvs.kde.org"
+>webcvs.kde.org</ulink
+></term
+> <listitem
+><para
+>A web interface to the &kde; CVS repository</para
+></listitem
+> </varlistentry
+> <varlistentry
+> <term
+><ulink url="http://i18n.kde.org"
+>i18n.kde.org</ulink
+></term
+> <listitem
+><para
+>&kde;'s internationalisation and documentation server</para
+></listitem
+> </varlistentry
+> <varlistentry
+> <term
+><ulink url="ftp://ftp.kde.org"
+>ftp.kde.org</ulink
+></term
+> <listitem
+><para
+>The main &kde; &FTP; server. Please have a look at the link below to find a mirror site in your geographic region.</para
+></listitem
+> </varlistentry
+> <varlistentry
+> <term
+><ulink url="http://www.kde.org/mirrors.html"
+>www.kde.org/mirrors.html</ulink
+></term
+> <listitem
+><para
+>&kde; &FTP; mirror sites</para
+></listitem
+> </varlistentry
+> </variablelist>
+
+</chapter>
+
+
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/quickstart/Makefile.am b/tde-i18n-en_GB/docs/tdebase/khelpcenter/quickstart/Makefile.am
new file mode 100644
index 00000000000..2102aa47e4f
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/quickstart/Makefile.am
@@ -0,0 +1,4 @@
+KDE_LANG = en_GB
+SUBDIRS = $(AUTODIRS)
+KDE_DOCS = khelpcenter/quickstart
+KDE_MANS = AUTO
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/quickstart/Makefile.in b/tde-i18n-en_GB/docs/tdebase/khelpcenter/quickstart/Makefile.in
new file mode 100644
index 00000000000..5a5ca57fa6e
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/quickstart/Makefile.in
@@ -0,0 +1,635 @@
+# Makefile.in generated by automake 1.10.1 from Makefile.am.
+# KDE tags expanded automatically by am_edit - $Revision: 483858 $ 
+# @configure_input@
+
+# Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002,
+# 2003, 2004, 2005, 2006, 2007, 2008  Free Software Foundation, Inc.
+# This Makefile.in is free software; the Free Software Foundation
+# gives unlimited permission to copy and/or distribute it,
+# with or without modifications, as long as this notice is preserved.
+
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY, to the extent permitted by law; without
+# even the implied warranty of MERCHANTABILITY or FITNESS FOR A
+# PARTICULAR PURPOSE.
+
+@SET_MAKE@
+VPATH = @srcdir@
+pkgdatadir = $(datadir)/@PACKAGE@
+pkglibdir = $(libdir)/@PACKAGE@
+pkgincludedir = $(includedir)/@PACKAGE@
+am__cd = CDPATH="$${ZSH_VERSION+.}$(PATH_SEPARATOR)" && cd
+install_sh_DATA = $(install_sh) -c -m 644
+install_sh_PROGRAM = $(install_sh) -c
+install_sh_SCRIPT = $(install_sh) -c
+INSTALL_HEADER = $(INSTALL_DATA)
+transform = $(program_transform_name)
+NORMAL_INSTALL = :
+PRE_INSTALL = :
+POST_INSTALL = :
+NORMAL_UNINSTALL = :
+PRE_UNINSTALL = :
+POST_UNINSTALL = :
+subdir = docs/tdebase/khelpcenter/quickstart
+DIST_COMMON = $(srcdir)/Makefile.am $(srcdir)/Makefile.in
+ACLOCAL_M4 = $(top_srcdir)/aclocal.m4
+am__aclocal_m4_deps = $(top_srcdir)/acinclude.m4 \
+	$(top_srcdir)/configure.in
+am__configure_deps = $(am__aclocal_m4_deps) $(CONFIGURE_DEPENDENCIES) \
+	$(ACLOCAL_M4)
+mkinstalldirs = $(SHELL) $(top_srcdir)/mkinstalldirs
+CONFIG_HEADER = $(top_builddir)/config.h
+CONFIG_CLEAN_FILES =
+SOURCES =
+DIST_SOURCES =
+#>- RECURSIVE_TARGETS = all-recursive check-recursive dvi-recursive \
+#>- 	html-recursive info-recursive install-data-recursive \
+#>- 	install-dvi-recursive install-exec-recursive \
+#>- 	install-html-recursive install-info-recursive \
+#>- 	install-pdf-recursive install-ps-recursive install-recursive \
+#>- 	installcheck-recursive installdirs-recursive pdf-recursive \
+#>- 	ps-recursive uninstall-recursive
+#>+ 7
+RECURSIVE_TARGETS = all-recursive check-recursive dvi-recursive \
+	html-recursive info-recursive install-data-recursive \
+	install-dvi-recursive install-exec-recursive \
+	install-html-recursive install-info-recursive \
+	install-pdf-recursive install-ps-recursive install-recursive \
+	installcheck-recursive installdirs-recursive pdf-recursive \
+	ps-recursive uninstall-recursive nmcheck-recursive bcheck-recursive
+RECURSIVE_CLEAN_TARGETS = mostlyclean-recursive clean-recursive	\
+  distclean-recursive maintainer-clean-recursive
+ETAGS = etags
+CTAGS = ctags
+DIST_SUBDIRS = $(SUBDIRS)
+#>- DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST)
+#>+ 1
+DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST) $(KDE_DIST)
+ACLOCAL = @ACLOCAL@
+AMTAR = @AMTAR@
+ARTSCCONFIG = @ARTSCCONFIG@
+AUTOCONF = @AUTOCONF@
+AUTODIRS = @AUTODIRS@
+AUTOHEADER = @AUTOHEADER@
+AUTOMAKE = @AUTOMAKE@
+AWK = @AWK@
+CONF_FILES = @CONF_FILES@
+CYGPATH_W = @CYGPATH_W@
+DCOPIDL = @DCOPIDL@
+DCOPIDL2CPP = @DCOPIDL2CPP@
+DCOPIDLNG = @DCOPIDLNG@
+DCOP_DEPENDENCIES = @DCOP_DEPENDENCIES@
+DEFS = @DEFS@
+ECHO_C = @ECHO_C@
+ECHO_N = @ECHO_N@
+ECHO_T = @ECHO_T@
+GMSGFMT = @GMSGFMT@
+INSTALL = @INSTALL@
+INSTALL_DATA = @INSTALL_DATA@
+INSTALL_PROGRAM = @INSTALL_PROGRAM@
+INSTALL_SCRIPT = @INSTALL_SCRIPT@
+INSTALL_STRIP_PROGRAM = @INSTALL_STRIP_PROGRAM@
+KCFG_DEPENDENCIES = @KCFG_DEPENDENCIES@
+KCONFIG_COMPILER = @KCONFIG_COMPILER@
+KDECONFIG = @KDECONFIG@
+KDE_EXTRA_RPATH = @KDE_EXTRA_RPATH@
+KDE_RPATH = @KDE_RPATH@
+KDE_XSL_STYLESHEET = @KDE_XSL_STYLESHEET@
+LIBOBJS = @LIBOBJS@
+LIBS = @LIBS@
+LN_S = @LN_S@
+LTLIBOBJS = @LTLIBOBJS@
+MAKEINFO = @MAKEINFO@
+MAKEKDEWIDGETS = @MAKEKDEWIDGETS@
+MCOPIDL = @MCOPIDL@
+MEINPROC = @MEINPROC@
+MKDIR_P = @MKDIR_P@
+MSGFMT = @MSGFMT@
+PACKAGE = @PACKAGE@
+PACKAGE_BUGREPORT = @PACKAGE_BUGREPORT@
+PACKAGE_NAME = @PACKAGE_NAME@
+PACKAGE_STRING = @PACKAGE_STRING@
+PACKAGE_TARNAME = @PACKAGE_TARNAME@
+PACKAGE_VERSION = @PACKAGE_VERSION@
+PATH_SEPARATOR = @PATH_SEPARATOR@
+SET_MAKE = @SET_MAKE@
+SHELL = @SHELL@
+STRIP = @STRIP@
+TOPSUBDIRS = @TOPSUBDIRS@
+VERSION = @VERSION@
+XGETTEXT = @XGETTEXT@
+XMLLINT = @XMLLINT@
+X_RPATH = @X_RPATH@
+abs_builddir = @abs_builddir@
+abs_srcdir = @abs_srcdir@
+abs_top_builddir = @abs_top_builddir@
+abs_top_srcdir = @abs_top_srcdir@
+am__leading_dot = @am__leading_dot@
+am__tar = @am__tar@
+am__untar = @am__untar@
+#>- bindir = @bindir@
+#>+ 2
+DEPDIR = .deps
+bindir = @bindir@
+build_alias = @build_alias@
+builddir = @builddir@
+datadir = @datadir@
+datarootdir = @datarootdir@
+docdir = @docdir@
+dvidir = @dvidir@
+exec_prefix = @exec_prefix@
+host_alias = @host_alias@
+htmldir = @htmldir@
+includedir = @includedir@
+infodir = @infodir@
+install_sh = @install_sh@
+kde_appsdir = @kde_appsdir@
+kde_bindir = @kde_bindir@
+kde_confdir = @kde_confdir@
+kde_datadir = @kde_datadir@
+kde_htmldir = @kde_htmldir@
+kde_icondir = @kde_icondir@
+kde_kcfgdir = @kde_kcfgdir@
+kde_libs_htmldir = @kde_libs_htmldir@
+kde_libs_prefix = @kde_libs_prefix@
+kde_locale = @kde_locale@
+kde_mimedir = @kde_mimedir@
+kde_moduledir = @kde_moduledir@
+kde_servicesdir = @kde_servicesdir@
+kde_servicetypesdir = @kde_servicetypesdir@
+kde_sounddir = @kde_sounddir@
+kde_styledir = @kde_styledir@
+kde_templatesdir = @kde_templatesdir@
+kde_wallpaperdir = @kde_wallpaperdir@
+kde_widgetdir = @kde_widgetdir@
+tdeinitdir = @tdeinitdir@
+libdir = @libdir@
+libexecdir = @libexecdir@
+localedir = @localedir@
+localstatedir = @localstatedir@
+mandir = @mandir@
+mkdir_p = @mkdir_p@
+oldincludedir = @oldincludedir@
+pdfdir = @pdfdir@
+prefix = @prefix@
+program_transform_name = @program_transform_name@
+psdir = @psdir@
+sbindir = @sbindir@
+sharedstatedir = @sharedstatedir@
+srcdir = @srcdir@
+sysconfdir = @sysconfdir@
+target_alias = @target_alias@
+top_builddir = @top_builddir@
+top_srcdir = @top_srcdir@
+xdg_appsdir = @xdg_appsdir@
+xdg_directorydir = @xdg_directorydir@
+xdg_menudir = @xdg_menudir@
+KDE_LANG = en_GB
+#>- SUBDIRS = $(AUTODIRS)
+#>+ 1
+SUBDIRS =.
+KDE_DOCS = khelpcenter/quickstart
+KDE_MANS = AUTO
+#>- all: all-recursive
+#>+ 1
+all: docs-am  all-recursive
+
+.SUFFIXES:
+$(srcdir)/Makefile.in:  $(srcdir)/Makefile.am  $(am__configure_deps)
+#>- 	@for dep in $?; do \
+#>- 	  case '$(am__configure_deps)' in \
+#>- 	    *$$dep*) \
+#>- 	      cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh \
+#>- 		&& exit 0; \
+#>- 	      exit 1;; \
+#>- 	  esac; \
+#>- 	done; \
+#>- 	echo ' cd $(top_srcdir) && $(AUTOMAKE) --gnu  docs/tdebase/khelpcenter/quickstart/Makefile'; \
+#>- 	cd $(top_srcdir) && \
+#>- 	  $(AUTOMAKE) --gnu  docs/tdebase/khelpcenter/quickstart/Makefile
+#>+ 12
+	@for dep in $?; do \
+	  case '$(am__configure_deps)' in \
+	    *$$dep*) \
+	      cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh \
+		&& exit 0; \
+	      exit 1;; \
+	  esac; \
+	done; \
+	echo ' cd $(top_srcdir) && $(AUTOMAKE) --gnu  docs/tdebase/khelpcenter/quickstart/Makefile'; \
+	cd $(top_srcdir) && \
+	  $(AUTOMAKE) --gnu  docs/tdebase/khelpcenter/quickstart/Makefile
+	cd $(top_srcdir) && perl ../scripts/admin/am_edit -p../scripts/admin docs/tdebase/khelpcenter/quickstart/Makefile.in
+.PRECIOUS: Makefile
+Makefile: $(srcdir)/Makefile.in $(top_builddir)/config.status
+	@case '$?' in \
+	  *config.status*) \
+	    cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh;; \
+	  *) \
+	    echo ' cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__depfiles_maybe)'; \
+	    cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__depfiles_maybe);; \
+	esac;
+
+$(top_builddir)/config.status: $(top_srcdir)/configure $(CONFIG_STATUS_DEPENDENCIES)
+	cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
+
+$(top_srcdir)/configure:  $(am__configure_deps)
+	cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
+$(ACLOCAL_M4):  $(am__aclocal_m4_deps)
+	cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
+
+# This directory's subdirectories are mostly independent; you can cd
+# into them and run `make' without going through this Makefile.
+# To change the values of `make' variables: instead of editing Makefiles,
+# (1) if the variable is set in `config.status', edit `config.status'
+#     (which will cause the Makefiles to be regenerated when you run `make');
+# (2) otherwise, pass the desired values on the `make' command line.
+$(RECURSIVE_TARGETS):
+	@failcom='exit 1'; \
+	for f in x $$MAKEFLAGS; do \
+	  case $$f in \
+	    *=* | --[!k]*);; \
+	    *k*) failcom='fail=yes';; \
+	  esac; \
+	done; \
+	dot_seen=no; \
+	target=`echo $@ | sed s/-recursive//`; \
+	list='$(SUBDIRS)'; for subdir in $$list; do \
+	  echo "Making $$target in $$subdir"; \
+	  if test "$$subdir" = "."; then \
+	    dot_seen=yes; \
+	    local_target="$$target-am"; \
+	  else \
+	    local_target="$$target"; \
+	  fi; \
+	  (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS) $$local_target) \
+	  || eval $$failcom; \
+	done; \
+	if test "$$dot_seen" = "no"; then \
+	  $(MAKE) $(AM_MAKEFLAGS) "$$target-am" || exit 1; \
+	fi; test -z "$$fail"
+
+$(RECURSIVE_CLEAN_TARGETS):
+	@failcom='exit 1'; \
+	for f in x $$MAKEFLAGS; do \
+	  case $$f in \
+	    *=* | --[!k]*);; \
+	    *k*) failcom='fail=yes';; \
+	  esac; \
+	done; \
+	dot_seen=no; \
+	case "$@" in \
+	  distclean-* | maintainer-clean-*) list='$(DIST_SUBDIRS)' ;; \
+	  *) list='$(SUBDIRS)' ;; \
+	esac; \
+	rev=''; for subdir in $$list; do \
+	  if test "$$subdir" = "."; then :; else \
+	    rev="$$subdir $$rev"; \
+	  fi; \
+	done; \
+	rev="$$rev ."; \
+	target=`echo $@ | sed s/-recursive//`; \
+	for subdir in $$rev; do \
+	  echo "Making $$target in $$subdir"; \
+	  if test "$$subdir" = "."; then \
+	    local_target="$$target-am"; \
+	  else \
+	    local_target="$$target"; \
+	  fi; \
+	  (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS) $$local_target) \
+	  || eval $$failcom; \
+	done && test -z "$$fail"
+tags-recursive:
+	list='$(SUBDIRS)'; for subdir in $$list; do \
+	  test "$$subdir" = . || (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS) tags); \
+	done
+ctags-recursive:
+	list='$(SUBDIRS)'; for subdir in $$list; do \
+	  test "$$subdir" = . || (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS) ctags); \
+	done
+
+ID: $(HEADERS) $(SOURCES) $(LISP) $(TAGS_FILES)
+	list='$(SOURCES) $(HEADERS) $(LISP) $(TAGS_FILES)'; \
+	unique=`for i in $$list; do \
+	    if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
+	  done | \
+	  $(AWK) '{ files[$$0] = 1; nonemtpy = 1; } \
+	      END { if (nonempty) { for (i in files) print i; }; }'`; \
+	mkid -fID $$unique
+tags: TAGS
+
+TAGS: tags-recursive $(HEADERS) $(SOURCES)  $(TAGS_DEPENDENCIES) \
+		$(TAGS_FILES) $(LISP)
+	tags=; \
+	here=`pwd`; \
+	if ($(ETAGS) --etags-include --version) >/dev/null 2>&1; then \
+	  include_option=--etags-include; \
+	  empty_fix=.; \
+	else \
+	  include_option=--include; \
+	  empty_fix=; \
+	fi; \
+	list='$(SUBDIRS)'; for subdir in $$list; do \
+	  if test "$$subdir" = .; then :; else \
+	    test ! -f $$subdir/TAGS || \
+	      tags="$$tags $$include_option=$$here/$$subdir/TAGS"; \
+	  fi; \
+	done; \
+	list='$(SOURCES) $(HEADERS)  $(LISP) $(TAGS_FILES)'; \
+	unique=`for i in $$list; do \
+	    if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
+	  done | \
+	  $(AWK) '{ files[$$0] = 1; nonempty = 1; } \
+	      END { if (nonempty) { for (i in files) print i; }; }'`; \
+	if test -z "$(ETAGS_ARGS)$$tags$$unique"; then :; else \
+	  test -n "$$unique" || unique=$$empty_fix; \
+	  $(ETAGS) $(ETAGSFLAGS) $(AM_ETAGSFLAGS) $(ETAGS_ARGS) \
+	    $$tags $$unique; \
+	fi
+ctags: CTAGS
+CTAGS: ctags-recursive $(HEADERS) $(SOURCES)  $(TAGS_DEPENDENCIES) \
+		$(TAGS_FILES) $(LISP)
+	tags=; \
+	list='$(SOURCES) $(HEADERS)  $(LISP) $(TAGS_FILES)'; \
+	unique=`for i in $$list; do \
+	    if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
+	  done | \
+	  $(AWK) '{ files[$$0] = 1; nonempty = 1; } \
+	      END { if (nonempty) { for (i in files) print i; }; }'`; \
+	test -z "$(CTAGS_ARGS)$$tags$$unique" \
+	  || $(CTAGS) $(CTAGSFLAGS) $(AM_CTAGSFLAGS) $(CTAGS_ARGS) \
+	     $$tags $$unique
+
+GTAGS:
+	here=`$(am__cd) $(top_builddir) && pwd` \
+	  && cd $(top_srcdir) \
+	  && gtags -i $(GTAGS_ARGS) $$here
+
+distclean-tags:
+	-rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
+
+#>- distdir: $(DISTFILES)
+#>+ 1
+distdir: distdir-nls  $(DISTFILES)
+	@srcdirstrip=`echo "$(srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \
+	topsrcdirstrip=`echo "$(top_srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \
+	list='$(DISTFILES)'; \
+	  dist_files=`for file in $$list; do echo $$file; done | \
+	  sed -e "s|^$$srcdirstrip/||;t" \
+	      -e "s|^$$topsrcdirstrip/|$(top_builddir)/|;t"`; \
+	case $$dist_files in \
+	  */*) $(MKDIR_P) `echo "$$dist_files" | \
+			   sed '/\//!d;s|^|$(distdir)/|;s,/[^/]*$$,,' | \
+			   sort -u` ;; \
+	esac; \
+	for file in $$dist_files; do \
+	  if test -f $$file || test -d $$file; then d=.; else d=$(srcdir); fi; \
+	  if test -d $$d/$$file; then \
+	    dir=`echo "/$$file" | sed -e 's,/[^/]*$$,,'`; \
+	    if test -d $(srcdir)/$$file && test $$d != $(srcdir); then \
+	      cp -pR $(srcdir)/$$file $(distdir)$$dir || exit 1; \
+	    fi; \
+	    cp -pR $$d/$$file $(distdir)$$dir || exit 1; \
+	  else \
+	    test -f $(distdir)/$$file \
+	    || cp -p $$d/$$file $(distdir)/$$file \
+	    || exit 1; \
+	  fi; \
+	done
+	list='$(DIST_SUBDIRS)'; for subdir in $$list; do \
+	  if test "$$subdir" = .; then :; else \
+	    test -d "$(distdir)/$$subdir" \
+	    || $(MKDIR_P) "$(distdir)/$$subdir" \
+	    || exit 1; \
+	    distdir=`$(am__cd) $(distdir) && pwd`; \
+	    top_distdir=`$(am__cd) $(top_distdir) && pwd`; \
+	    (cd $$subdir && \
+	      $(MAKE) $(AM_MAKEFLAGS) \
+	        top_distdir="$$top_distdir" \
+	        distdir="$$distdir/$$subdir" \
+		am__remove_distdir=: \
+		am__skip_length_check=: \
+	        distdir) \
+	      || exit 1; \
+	  fi; \
+	done
+check-am: all-am
+check: check-recursive
+all-am: Makefile
+installdirs: installdirs-recursive
+installdirs-am:
+install: install-recursive
+install-exec: install-exec-recursive
+install-data: install-data-recursive
+#>- uninstall: uninstall-recursive
+#>+ 1
+uninstall: uninstall-docs uninstall-nls  uninstall-recursive
+
+install-am: all-am
+	@$(MAKE) $(AM_MAKEFLAGS) install-exec-am install-data-am
+
+installcheck: installcheck-recursive
+install-strip:
+	$(MAKE) $(AM_MAKEFLAGS) INSTALL_PROGRAM="$(INSTALL_STRIP_PROGRAM)" \
+	  install_sh_PROGRAM="$(INSTALL_STRIP_PROGRAM)" INSTALL_STRIP_FLAG=-s \
+	  `test -z '$(STRIP)' || \
+	    echo "INSTALL_PROGRAM_ENV=STRIPPROG='$(STRIP)'"` install
+mostlyclean-generic:
+
+clean-generic:
+
+distclean-generic:
+	-test -z "$(CONFIG_CLEAN_FILES)" || rm -f $(CONFIG_CLEAN_FILES)
+
+maintainer-clean-generic:
+	@echo "This command is intended for maintainers to use"
+	@echo "it deletes files that may require special tools to rebuild."
+#>- clean: clean-recursive
+#>+ 1
+clean: kde-rpo-clean  clean-recursive
+
+#>- clean-am: clean-generic mostlyclean-am
+#>+ 1
+clean-am: clean-docs clean-bcheck  clean-generic mostlyclean-am
+
+distclean: distclean-recursive
+	-rm -f Makefile
+distclean-am: clean-am distclean-generic distclean-tags
+
+dvi: dvi-recursive
+
+dvi-am:
+
+html: html-recursive
+
+info: info-recursive
+
+info-am:
+
+#>- install-data-am:
+#>+ 1
+install-data-am: install-docs install-nls 
+
+install-dvi: install-dvi-recursive
+
+install-exec-am:
+
+install-html: install-html-recursive
+
+install-info: install-info-recursive
+
+install-man:
+
+install-pdf: install-pdf-recursive
+
+install-ps: install-ps-recursive
+
+installcheck-am:
+
+maintainer-clean: maintainer-clean-recursive
+	-rm -f Makefile
+maintainer-clean-am: distclean-am maintainer-clean-generic
+
+mostlyclean: mostlyclean-recursive
+
+mostlyclean-am: mostlyclean-generic
+
+pdf: pdf-recursive
+
+pdf-am:
+
+ps: ps-recursive
+
+ps-am:
+
+uninstall-am:
+
+.MAKE: $(RECURSIVE_CLEAN_TARGETS) $(RECURSIVE_TARGETS) install-am \
+	install-strip
+
+.PHONY: $(RECURSIVE_CLEAN_TARGETS) $(RECURSIVE_TARGETS) CTAGS GTAGS \
+	all all-am check check-am clean clean-generic ctags \
+	ctags-recursive distclean distclean-generic distclean-tags \
+	distdir dvi dvi-am html html-am info info-am install \
+	install-am install-data install-data-am install-dvi \
+	install-dvi-am install-exec install-exec-am install-html \
+	install-html-am install-info install-info-am install-man \
+	install-pdf install-pdf-am install-ps install-ps-am \
+	install-strip installcheck installcheck-am installdirs \
+	installdirs-am maintainer-clean maintainer-clean-generic \
+	mostlyclean mostlyclean-generic pdf pdf-am ps ps-am tags \
+	tags-recursive uninstall uninstall-am
+
+# Tell versions [3.59,3.63) of GNU make to not export all variables.
+# Otherwise a system limit (for SysV at least) may be exceeded.
+.NOEXPORT:
+
+#>+ 2
+KDE_DIST=Makefile.in index.docbook Makefile.am index.cache.bz2 
+
+#>+ 24
+index.cache.bz2: $(srcdir)/index.docbook $(KDE_XSL_STYLESHEET) index.docbook 
+	@if test -n "$(MEINPROC)"; then echo $(MEINPROC) --check --cache index.cache.bz2 $(srcdir)/index.docbook; $(MEINPROC) --check --cache index.cache.bz2 $(srcdir)/index.docbook; fi
+
+docs-am: index.cache.bz2
+
+install-docs: docs-am install-nls
+	$(mkinstalldirs) $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/quickstart
+	@if test -f index.cache.bz2; then \
+	echo $(INSTALL_DATA) index.cache.bz2 $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/quickstart/; \
+	$(INSTALL_DATA) index.cache.bz2 $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/quickstart/; \
+	elif test -f  $(srcdir)/index.cache.bz2; then \
+	echo $(INSTALL_DATA) $(srcdir)/index.cache.bz2 $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/quickstart/; \
+	$(INSTALL_DATA) $(srcdir)/index.cache.bz2 $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/quickstart/; \
+	fi
+	-rm -f $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/quickstart/common
+	$(LN_S) $(kde_libs_htmldir)/$(KDE_LANG)/common $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/quickstart/common
+
+uninstall-docs:
+	-rm -rf $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/quickstart
+
+clean-docs:
+	-rm -f index.cache.bz2
+
+
+#>+ 13
+install-nls:
+	$(mkinstalldirs) $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/quickstart
+	@for base in index.docbook ; do \
+	  echo $(INSTALL_DATA) $$base $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/quickstart/$$base ;\
+	  $(INSTALL_DATA) $(srcdir)/$$base $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/quickstart/$$base ;\
+	done
+
+uninstall-nls:
+	for base in index.docbook ; do \
+	  rm -f $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/quickstart/$$base ;\
+	done
+
+
+#>+ 5
+distdir-nls:
+	for file in index.docbook ; do \
+	  cp $(srcdir)/$$file $(distdir); \
+	done
+
+#>+ 15
+force-reedit:
+		@for dep in $?; do \
+	  case '$(am__configure_deps)' in \
+	    *$$dep*) \
+	      cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh \
+		&& exit 0; \
+	      exit 1;; \
+	  esac; \
+	done; \
+	echo ' cd $(top_srcdir) && $(AUTOMAKE) --gnu  docs/tdebase/khelpcenter/quickstart/Makefile'; \
+	cd $(top_srcdir) && \
+	  $(AUTOMAKE) --gnu  docs/tdebase/khelpcenter/quickstart/Makefile
+	cd $(top_srcdir) && perl ../scripts/admin/am_edit -p../scripts/admin docs/tdebase/khelpcenter/quickstart/Makefile.in
+
+
+#>+ 21
+clean-bcheck: 
+	rm -f *.bchecktest.cc *.bchecktest.cc.class a.out
+
+bcheck: bcheck-recursive
+
+bcheck-am:
+	@for i in ; do \
+	    if test $(srcdir)/$$i -nt $$i.bchecktest.cc; then \
+	        echo "int main() {return 0;}" > $$i.bchecktest.cc ; \
+	        echo "#include \"$$i\"" >> $$i.bchecktest.cc ; \
+	        echo "$$i"; \
+	        if ! $(CXX) $(DEFS) -I. -I$(srcdir) -I$(top_builddir) $(INCLUDES) $(AM_CPPFLAGS) $(CPPFLAGS) $(CXXFLAGS) $(KDE_CXXFLAGS)  --dump-class-hierarchy -c $$i.bchecktest.cc; then \
+	            rm -f $$i.bchecktest.cc; exit 1; \
+	        fi ; \
+	        echo "" >> $$i.bchecktest.cc.class; \
+	        perl $(top_srcdir)/admin/bcheck.pl $$i.bchecktest.cc.class || { rm -f $$i.bchecktest.cc; exit 1; }; \
+	        rm -f a.out; \
+	    fi ; \
+	done
+
+
+#>+ 3
+final:
+	$(MAKE) all-am
+
+#>+ 3
+final-install:
+	$(MAKE) install-am
+
+#>+ 3
+no-final:
+	$(MAKE) all-am
+
+#>+ 3
+no-final-install:
+	$(MAKE) install-am
+
+#>+ 3
+kde-rpo-clean:
+	-rm -f *.rpo
+
+#>+ 3
+nmcheck: 
+nmcheck-am: nmcheck
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/quickstart/index.cache.bz2 b/tde-i18n-en_GB/docs/tdebase/khelpcenter/quickstart/index.cache.bz2
new file mode 100644
index 00000000000..bf07cb8f10e
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/quickstart/index.cache.bz2
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/quickstart/index.docbook b/tde-i18n-en_GB/docs/tdebase/khelpcenter/quickstart/index.docbook
new file mode 100644
index 00000000000..6ae9e9adacd
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/quickstart/index.docbook
@@ -0,0 +1,1558 @@
+<?xml version="1.0" ?>
+<!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" 
+"dtd/kdex.dtd" [
+  <!ENTITY kappname "&kde; Quick Start Guide">
+  <!ENTITY package "tdebase">
+  <!ENTITY % addindex "IGNORE">
+  <!ENTITY % British-English "INCLUDE"
+> <!-- change language only here -->
+]>
+
+<book lang="&language;">
+<bookinfo>
+	
+<title
+>An Introduction to &kde;</title>
+
+<authorgroup>
+
+<author>
+<surname
+>The KDE Team</surname>
+</author>
+<othercredit role="translator"
+><firstname
+>Malcolm</firstname
+><surname
+>Hunter</surname
+><affiliation
+><address
+><email
+>malcolm.hunter@gmx.co.uk</email
+></address
+></affiliation
+><contrib
+>Conversion to British English</contrib
+></othercredit
+> 
+</authorgroup>
+
+<date
+>2002-01-18</date>
+<releaseinfo
+>3.00.00</releaseinfo>
+
+<copyright>
+<year
+>1999</year
+><year
+>2000</year
+><year
+>2001</year
+><year
+>2002</year>
+<holder
+>The KDE Team</holder>
+</copyright>
+
+<legalnotice
+>&FDLNotice;</legalnotice>
+
+<abstract>
+<para
+>An introduction to the K Desktop Environment</para>
+<para
+>Quick Start Guide to &kde;</para
+></abstract>
+
+<keywordset>
+<keyword
+>KDE</keyword>
+<keyword
+>quick start</keyword>
+<keyword
+>introduction</keyword>
+</keywordset>
+</bookinfo>
+
+<chapter id="introduction">
+<title
+>Introduction</title>
+
+<para
+>This document is a brief introduction to the K Desktop Environment. It will familiarise you with some of the basic features of &kde;. </para>
+
+<para
+>This guide is far from covering all aspects of the K Desktop or even most of them. It will only describe some of the most basic ways to accomplish a few of the most common tasks. </para>
+
+<para
+>We assume that you are already familiar with at least one graphical user interface, for example <trademark
+>CDE</trademark
+>, <trademark
+>Geos</trademark
+>, <trademark
+>GEM</trademark
+>, &NeXTSTEP;, &Mac;, <trademark
+>OS/2</trademark
+> or &Microsoft; &Windows;. So we will not explain the usage of the mouse or the keyboard but concentrate on hopefully more interesting things. </para>
+
+</chapter>
+
+<chapter id="an-overview-of-kde">
+<title
+>An Overview of &kde;</title>
+
+<para
+>This section is for users who prefer to learn by exploring and want only a brief orientation to get started. Later sections provide a more thorough introduction to the environment, with helpful hints and shortcuts. If you are impatient to get started, skim this section, go play for a bit, then come back and peruse the other sections of this guide as needed. </para>
+
+<note>
+<para
+>&kde; provides a highly configurable desktop environment. This overview assumes that you are using the default environment. </para>
+</note>
+
+<sect1 id="the-kde-desktop">
+<title
+>The &kde; Desktop</title>
+
+<para
+>A typical &kde; desktop consists of several parts:</para>
+
+<itemizedlist>
+<listitem>
+<para
+>A <interface
+>panel</interface
+> at the bottom of the screen, used to start applications and switch between desktops. Among other things, it contains the &kmenu;, a large &kicon; which displays a menu of applications to start when clicked. </para>
+</listitem>
+
+<listitem>
+<para
+>A <interface
+>taskbar</interface
+>, by default embedded in the panel, used to switch between and manage currently running applications. Click on an application on the taskbar to switch to the application. </para>
+</listitem
+> 
+
+<listitem>
+<para
+>The <interface
+>desktop</interface
+> itself, on which frequently used files and folders may be placed. &kde; provides multiple desktops, each of which has its own windows. Click on the numbered buttons on the panel to switch between desktops. </para>
+</listitem>
+</itemizedlist>
+
+</sect1>
+
+<sect1 id="ready-set-go">
+<title
+>Ready, Set, Go!</title>
+
+<para
+>Here are a few quick tips to get you up and running.</para>
+
+<itemizedlist>
+<listitem>
+<para
+>To start an application, click on the &kicon; button on the panel (called the <link linkend="starter"
+>&kmenu;</link
+>) and choose an item from the menu. </para>
+</listitem>
+<listitem>
+<para
+>Click the icon that looks like a folder with a picture of a house on the panel to access the files in your home folder using &konqueror;, &kde;'s File Manager utility. </para>
+</listitem>
+<listitem>
+<para
+>Choose <menuchoice
+><guimenu
+>K menu</guimenu
+> <guisubmenu
+>System</guisubmenu
+> <guimenuitem
+>Konsole</guimenuitem
+></menuchoice
+> to get a &UNIX; command prompt, or press <keycombo action="simul"
+>&Alt; <keycap
+>F2</keycap
+></keycombo
+> to get a mini command prompt window to execute a single command. </para>
+</listitem>
+
+<listitem>
+<para
+>Choose the <menuchoice
+><guisubmenu
+>Settings</guisubmenu
+><guimenuitem
+>Control Centre</guimenuitem
+> </menuchoice
+>item on the &kmenu; to configure &kde;. </para>
+</listitem
+> 
+
+<listitem>
+<para
+>Press <keycombo action="simul"
+>&Alt;<keycap
+>Tab</keycap
+></keycombo
+> to switch between applications and <keycombo action="simul"
+>&Ctrl;<keycap
+>Tab</keycap
+></keycombo
+> to switch between desktops using the keyboard. </para>
+</listitem
+> 
+
+<listitem>
+<para
+>Use the &RMB; mouse button to access context menus for the panel, desktop, and most &kde; applications. </para>
+</listitem
+> 
+</itemizedlist>
+
+</sect1>
+</chapter>
+
+<chapter id="launching-applications">
+<title
+>Launching Applications</title>
+
+<sect1 id="starter">
+<title
+>Using the &kmenu; and the Panel</title>
+
+<para
+>At the bottom of the screen you will find the desktop panel, which is called &kicker;. You use the panel to launch applications. Have a look at the button on the left with a large &kicon;. </para>
+
+<para
+>This button is called the &kmenu;. It has a small arrow on the top to indicate that it will pop up a menu if you click on it. Just do it! The pop-up offers you easy access to all &kde; applications installed on your computer system. </para>
+
+<sect2>
+<title
+>Customising &kicker;</title>
+
+<!-- FIXME: To add a button, use the little arrows on kicker, not the K menu -->
+<para
+>If you use one application or tool very often, then you may want to have even faster access to it, of course. In this case, you can add a single application, or an entire sub-menu of the &kmenu;, as a special quick-launch button, on to the panel. If you want to reach the &kfind; application directly via a launch button, simply choose <menuchoice
+><guimenu
+>K menu</guimenu
+> <guisubmenu
+>Panel Menu</guisubmenu
+> <guisubmenu
+>Add</guisubmenu
+> <guisubmenu
+>Button</guisubmenu
+> <guimenuitem
+>Find Files</guimenuitem
+></menuchoice
+> (By this we mean that you should first click the &kmenu;, then select <guisubmenu
+>Panel Menu</guisubmenu
+>, where the small arrow to the right indicates that another menu will pop up. In this menu, choose <guisubmenu
+>Add</guisubmenu
+>, then <guisubmenu
+>Button</guisubmenu
+>, and in the next sub-menu, <guimenuitem
+>Find Files</guimenuitem
+>). </para>
+	
+<para
+>You can add an entire menu this way, or one of the &kicon; button sub-menus. For example, if you have &koffice; installed and want quick access to all the &koffice; applications, without having to navigate through the &kmenu;, then instead of choosing an application, click on the <guimenuitem
+>Add this menu</guimenuitem
+> menu entry. Now you will have instant access to all the &koffice; applications, without having to put an icon for each on the panel. </para>
+
+<note>
+<para
+>You can move all items of the panel around with the <guimenuitem
+>Move</guimenuitem
+> command of the context menu. Just click with the <mousebutton
+>third</mousebutton
+> mouse button (the <mousebutton
+>third</mousebutton
+> mouse button is normally the <mousebutton
+>right</mousebutton
+> button, but if you have configured your mouse differently, for example for left-handers, it might also be the <mousebutton
+>left</mousebutton
+> one). A menu will pop up where you can choose <guimenuitem
+>Move</guimenuitem
+>. Now move the mouse and see how the icon follows while still staying on the panel. When you are done, simply hit the <mousebutton
+>first</mousebutton
+> mouse button (by default the <mousebutton
+>left</mousebutton
+> one). As you may have noticed, there is also a menu entry <guimenuitem
+>Remove</guimenuitem
+> in case you are tired of a certain launch button on your desktop. </para
+> 
+</note>
+
+</sect2>
+
+<sect2>
+<title
+>Using Context menus</title>
+
+<para
+>This leads us to another interesting topic: in many places, you can click the <mousebutton
+>right</mousebutton
+> mouse button to display a <interface
+>context menu</interface
+> with choices that are applicable to the item you clicked. It is therefore always a good idea to try out the <mousebutton
+>third</mousebutton
+> mouse button on something, if you do not know what to do with it. Even the background of the desktops has such a menu! </para>
+
+</sect2>
+
+<sect2>
+<title
+>Other Panel features</title>
+
+<para
+>There are other interesting things possible with the panel. One may be important if you have a low resolution on your monitor: it is the <quote
+>hide-and-show</quote
+> function, activated by clicking on the small arrowed button, which is at one or both ends of the panel. </para>
+
+<para
+>Perhaps you just don't like the panel extending the full width of the screen. That's easily changed! &RMB; on an empty space in the panel, and choose <menuchoice
+><guimenu
+>Panel</guimenu
+> <guisubmenu
+>Preferences</guisubmenu
+></menuchoice
+>. In the &kcontrol; dialogue that pops up, you can choose <guilabel
+>Panel Size</guilabel
+> on the <guilabel
+>General</guilabel
+> tab, and use the slider there to set the panel to less than 100% width. </para>
+
+<para
+>If you're following along, and have that dialogue open anyway, then feel free to play with all the options, and use the <guibutton
+>Apply</guibutton
+> to see the effect they have. You can easily reset everything to the default configuration, by simply pressing the <guibutton
+>Use Defaults</guibutton
+> button. </para>
+
+<para
+>By the way, if you are not sure what a certain button does in &kde;, just move the mouse pointer over it and wait for a short while: &kde; has a built-in mini context help, called <quote
+>tool tips</quote
+>, which explains the functionality of such controls in a few words. </para>
+
+
+</sect2>
+</sect1>
+
+<sect1 id="want-command-line-back">
+<title
+>But I want my command line back!</title>
+
+<para
+>Just calm down, there is nothing to fear. &kde; does not want to take your beloved (and sometimes very effective) command line away from you. You can move your files with the desktop, but you can also use the &UNIX; commands you are accustomed to. In fact,&kde; puts command line power at your fingertips, in perhaps some surprising places. </para>
+
+<para
+>&kde; provides a very sophisticated command line window called &konsole;. Choose <menuchoice
+><guimenu
+>K menu</guimenu
+> <guisubmenu
+>System</guisubmenu
+> <guimenuitem
+>Konsole</guimenuitem
+></menuchoice
+> to start it. This may be something you want on your panel: luckily it is already there in the default configuration! </para>
+  
+<para
+>Sometimes, you only want to enter one command on the command line. In these cases, you do not need a full-blown terminal. Just hit <keycombo
+>&Alt;<keycap
+>F2</keycap
+></keycombo
+> and you get a small command line where you can enter one command. The command line window will disappear afterwards, but it remembers your command. </para>
+
+<para
+>When you pop up this window (which we call <application
+>minicli</application
+> by the way) and hit the <keycap
+>Up arrow</keycap
+>, you can browse through all the commands you have previously entered. Also, you can enter &URL;s in <application
+>minicli</application
+> to open a &konqueror; window with the specified &URL;. </para>
+
+<para
+>&konqueror; and the editor &kate; can both display terminal windows, which behave just like &konsole;. In &konqueror;, you can turn this on with the menu choice <menuchoice
+><guimenu
+>Window</guimenu
+><guimenuitem
+>Show Terminal Emulator</guimenuitem
+></menuchoice
+>. The embedded terminal will display at the bottom of your &konqueror; window, and the really clever thing is that it will follow your clicks in the file manager view, changing folder as you do. In &kate; you can display a terminal with the menu choice <menuchoice
+><guimenu
+>Settings</guimenu
+><guimenuitem
+>Show Console</guimenuitem
+></menuchoice
+>. </para>
+
+<tip>
+<para
+>To display a &UNIX; man page, enter <userinput
+><command
+>man:</command
+><replaceable
+>command</replaceable
+></userinput
+> in <application
+>minicli</application
+>, where <replaceable
+>command</replaceable
+> is the name of a &UNIX; command. </para>
+</tip>
+
+<tip>
+<para
+>To search for a word or words on the Google search engine, you can try entering <userinput
+><command
+>gg:</command
+><replaceable
+>word or words</replaceable
+></userinput
+>. There are a whole lot more of these shortcut commands, and you can even add your own! Take a look in &kcontrol;, in the tab <menuchoice
+><guilabel
+>Web Browsing</guilabel
+> <guilabel
+>Enhanced Browsing</guilabel
+></menuchoice
+>. </para>
+</tip>
+
+<para
+>Finally, there's a way to have your command line always available, no matter what you're doing - add one to your &kicker; panel! </para>
+
+<para
+>Simply &RMB; click on an empty space in the panel, and choose <menuchoice
+><guimenu
+>Panel</guimenu
+> <guisubmenu
+>Add</guisubmenu
+> <guisubmenu
+>Applet</guisubmenu
+> <guimenuitem
+>Application Launcher</guimenuitem
+></menuchoice
+>. This will embed a mini-cli directly into your panel, complete with command history. </para>
+
+<para
+>So, in conclusion, the command line is never far from view when you're using &kde;. </para>
+
+</sect1>
+</chapter>
+
+<chapter id="working-with-windows">
+<title
+>Working with Windows</title>
+
+<para
+>If you have not already done so, start an application using the <link linkend="starter"
+>&kmenu;</link
+>; say, <guimenuitem
+>Find Files</guimenuitem
+>. </para>
+
+<sect1 id="window-what-now">
+<title
+>A window! What now?</title>
+
+<para
+>Well, usually people work <emphasis
+>inside</emphasis
+> windows, but sometimes you may want to manipulate windows. Here's a quick overview of some of the most common window related functions: </para>
+
+<variablelist>
+<varlistentry>
+<term
+>Move a window</term>
+<listitem>
+<para
+>Drag the window's title bar, or hold the &Alt; key down and drag anywhere in the window. </para>
+</listitem
+> 
+</varlistentry>
+
+<varlistentry>
+<term
+>Resize a window:</term>
+<listitem>
+<para
+>Drag the window's border, or hold the &Alt; key down and drag with the &RMB; anywhere in the window. </para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+>Maximise a window</term>
+<listitem>
+<para
+>Click the maximise button in the title bar (in the default decoration it is the square, next to the X) to make the window fill the screen, or if the window is already maximised, to shrink it back to its original size. Clicking with the &MMB; maximises the window vertically, and with the &RMB;, horizontally. </para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+>Iconify a window</term>
+<listitem>
+<para
+>Click the iconify button in the title bar (next to Maximise) to hide the window. Restore it by clicking on the window's icon in the taskbar. </para>
+</listitem
+> 
+</varlistentry>
+
+<varlistentry>
+<term
+>Switch between windows</term>
+<listitem>
+<para
+>Aside from the usual mouse click to switch to another window, you can use <keycombo action="simul"
+>&Alt; <keycap
+>Tab</keycap
+></keycombo
+> to switch windows. See below for more techniques. </para>
+</listitem>
+</varlistentry>
+</variablelist>
+
+<sect2>
+<title
+>Title bar buttons</title>
+
+<para
+>&kde; windows have some pretty standard buttons on their title bars which give you fast access to some common operations. The default button layout looks like this: </para>
+
+<itemizedlist>
+<title
+>On the left side:</title>
+<listitem>
+<para
+>A menu button. This usually shows a mini icon for the application. Click on it to get a window operations menu. Shortcut: <keycombo action="simul"
+>&Alt;<keycap
+>F3</keycap
+></keycombo
+> opens the window menu. </para>
+</listitem>
+ 
+<listitem>
+<para
+>A sticky button, with a picture of a tack. What the heck is this? Stay tuned! </para>
+</listitem
+> 
+</itemizedlist>
+
+<itemizedlist>
+<title
+>On the right side:</title>
+<listitem>
+<para
+>An iconify button. </para>
+</listitem>
+
+<listitem>
+<para
+>A maximise button. </para>
+</listitem>
+
+<listitem>
+<para
+>A close button. This closes the window. Shortcut: <keycombo action="simul"
+>&Alt;<keycap
+>F4</keycap
+></keycombo
+>. </para>
+</listitem>
+</itemizedlist>
+
+</sect2>
+
+<sect2>
+<title
+>Switching between windows</title>
+
+<para
+>Now that we know how to deal with windows, we encourage you to open some other windows using the panel, since we will now discuss how to switch between different windows. Since this is such a common activity, &kde; offers several ways to do it; pick your favourite! </para>
+
+<para
+>Many window systems require you to click the mouse in another window to begin using it. This is &kde;'s default behaviour, termed <quote
+>Click To Focus</quote
+> focus policy. But you can also configure your desktop in a way that moving the mouse pointer on to a window will activate it. This is called <quote
+>Focus Follows Mouse</quote
+>. If you select this policy using the <link linkend="configure"
+>&kde; Control Centre</link
+>, the window under the mouse pointer is always the active one. It doesn't necessarily come to the front automatically, but you can still click on to the title bar or the border of a window or, a &kde; special, you can use the &Alt; key and click the &MMB; anywhere on the window to raise it. </para>
+
+<para
+>Here are some other methods to switch windows: </para>
+
+<itemizedlist>
+<listitem>
+<para
+>Pick a window from the <emphasis
+>window list</emphasis
+> menu. To open the menu, click the &MMB; on an empty area of the desktop, or click the icon with several windows on the panel, or finally click the up arrow at the left hand end of the taskbar in the panel. </para>
+</listitem
+> 
+
+<listitem>
+<para
+>Hold down the &Alt; key and press <keycap
+>Tab</keycap
+> to cycle through the windows. </para>
+</listitem
+> 
+
+<listitem>
+<para
+>Use the taskbar (see below). </para>
+</listitem>
+</itemizedlist>
+
+</sect2>
+</sect1>
+
+<sect1 id="using-taskbar">
+<title
+>Using the Taskbar</title>
+
+<para
+>The <interface
+>taskbar</interface
+> displays a list of small icons, one for each window on the desktop. In the default &kde; setup the taskbar is located inside the panel, but it can also be located at the top or the bottom of the screen. </para>
+
+<para
+>The taskbar is very powerful. In the default configuration, if you have more than one window from the same application open, they will be <quote
+>grouped</quote
+>, so that you see one icon per application in the taskbar.</para>
+
+<para
+>A simple &LMB; click on the taskbar button will pop up a list of the open windows for that application and you can choose the window you want to use. Choosing one of these entries with the <mousebutton
+>left</mousebutton
+> will bring you to the selected window immediately. Click on a taskbar entry with the <mousebutton
+>right</mousebutton
+> and you will see a menu allowing you to operate on all the windows grouped under that icon, or each window individually.</para>
+
+<para
+>You can choose to see all the windows on all the desktops in your taskbar, no matter which desktop you are currently viewing, or to only see the icons for the desktop you are looking at. You can also choose to ungroup the icons, so that each open window will have its own icon in the taskbar. These and many more options are available simply by right clicking on the taskbar handle (the small textured bar at the left hand side) and choosing <guimenuitem
+>Preferences</guimenuitem
+>. </para>
+
+<para
+>The icons on the taskbar resize themselves to make room for applications, so you can fit many more applications than you might think. Making the panel wider will let the taskbar icons take on a row and column layout, but they will still resize to fit more icons. </para>
+
+</sect1>
+
+<sect1 id="using-v-desktops">
+<title
+>Using Virtual Desktops</title>
+
+<para
+>Now, what was that <quote
+>sticky</quote
+> thing? </para>
+
+<para
+>It may happen that you have more windows open than space on your desktop. In this case you have three possibilities: </para>
+
+<orderedlist>
+<listitem>
+<para
+>Leave all windows open (cluttered desktop) </para>
+</listitem>
+
+<listitem>
+<para
+>Iconify those windows which you do not need at present and use the taskbar or <keycombo action="simul"
+>&Alt; <keycap
+>Tab</keycap
+></keycombo
+> to switch between them (still a bit confusing and much work!) </para>
+</listitem
+> 
+
+<listitem>
+<para
+>Recommended: Do what a real operating system does if there is not enough physical memory: Use virtual memory, in this case virtual desktops. </para>
+</listitem>
+</orderedlist>
+
+<para
+>The third option is the way to go! &kde; can handle several different desktops, each with its own windows. The default configuration provides four desktops. You can switch between the virtual desktops easily with a click on one of the desktop buttons on the panel. Also <keycombo action="simul"
+>&Ctrl;<keycap
+>F1...F4</keycap
+></keycombo
+> will send you to the corresponding desktop immediately, or <keycombo action="simul"
+>&Ctrl; <keycap
+>Tab</keycap
+></keycombo
+> will cycle through the desktops. </para>
+
+<para
+>Virtual desktops are very nice. But sometimes you want a window to be present on <emphasis
+>every</emphasis
+> desktop. This could be, for example, a small chat window, an alarm clock or whatever. In this case you can use the above mentioned <quote
+>sticky</quote
+> button which will pin the window on the background so that it will appear on every virtual desktop. </para
+> 
+
+<para
+>The sticky button can also be used to move a window from one virtual desktop to another one: push the sticky pin on the window, switch to a different desktop, and release the pin by pushing it again. You can achieve the same result by using the context pop-up menu of the window's entry in the taskbar (menu item <guimenuitem
+>To Current Desktop</guimenuitem
+>) or the <guimenuitem
+>To Desktop</guimenuitem
+> option on the window operations menu. </para>
+
+</sect1>
+</chapter>
+
+<chapter id="managing-your-files">
+<title
+>Managing your files</title>
+
+<!-- NB Deliberate use of 'directory' rather than 'folder', since we're talking -->
+<!-- about directories on disk -->
+<para
+>A common metaphor of graphical desktops is the use of folders to represent directories on your hard disk. Folders contain files and other folders. A &kde; application called &konqueror;, the K File Manager, uses this metaphor to help you manage your files. </para>
+
+<sect1 id="using-konqueror">
+<title
+>Using &konqueror;</title>
+
+<para
+>The first time you start &kde;, a window with lots of icons in it appears. This is a &konqueror; window displaying the files in your home folder (the area where your personal files are stored). The pathname of the folder is displayed under the window's tool bar. If you do not see such a window now, click the icon on the panel that looks like a folder with a picture of a house. </para>
+
+<para
+>To open a file or folder, simply click it once with the &LMB;. You can also choose <menuchoice
+><guimenu
+>Window</guimenu
+><guimenuitem
+>Show Navigation Panel</guimenuitem
+></menuchoice
+> from the menu to display the folder hierarchy for more direct navigation. Or you can edit the path displayed under the toolbar to get to a specific folder quickly. </para>
+
+<sect2>
+<title
+>Opening Files</title>
+
+<para
+>&kde; comes with a set of applications to view and edit files of many common types, and when you click a file containing, say, a document or image, &konqueror; will start the appropriate application to display the file. If it doesn't know what application to start to open a file you clicked, &konqueror; will prompt you for the name of the application to run, and when you have chosen, &konqueror; will offer to remember your choice for the next time you open a file of that type. </para>
+
+<note>
+<para
+>&konqueror; uses <link linkend="mime"
+>MIME types</link
+> to associate files with applications. </para>
+</note
+> 
+
+</sect2>
+
+<sect2>
+<title
+>Dragging and Dropping Icons</title>
+
+<para
+>To copy or move a file, simply drag its icon to the desktop, to another &konqueror; window, or to a folder icon. When you release the button, &konqueror; displays a menu to allow you to choose to copy, move, or create a link to the file. </para>
+
+<note>
+<para
+>Note that if you choose to create a link, &kde; creates a &UNIX; symbolic link (not a hard link), so if you move or delete the original file, the link will be broken. </para>
+</note>
+
+<para
+>Most &kde; applications also support drag and drop operations: you can drag an icon on to a window of a running application, or on to an icon of an application that is not started, to have the application open the file. Try it! </para>
+
+</sect2>
+
+<sect2>
+<title
+>Setting File Properties</title>
+ 
+<para
+>To change file properties, such as its name and permissions, &RMB; click the icon and choose <guimenuitem
+>Properties</guimenuitem
+> from the menu. </para>
+
+</sect2>
+</sect1>
+
+<sect1 id="archives-and-networks">
+<title
+>Working with Archives and Networks</title>
+
+<para
+>In the recent past, you needed special software to access files on the Internet. Not any more! </para>
+
+<para
+>&kde; supports a technology called <quote
+>Network Transparent Access</quote
+> (<acronym
+>NTA</acronym
+>) which allows you to work with files on the other side of the world as easily as those on your local hard disk.</para>
+
+<para
+>For example, to access files on an &FTP; server, just choose <menuchoice
+><guimenu
+>Location</guimenu
+><guimenuitem
+>Open Location</guimenuitem
+></menuchoice
+> from a &konqueror; menu, and enter the <acronym
+>URL</acronym
+> of an &FTP; server. You can drag and drop files to and from the folders on the server just as if they were on your local disk. You'll even be able to open files on the &FTP; server without having to manually copy them to your local disk (&kde; does it for you when necessary). </para>
+
+<note>
+<para
+>Note that &konqueror; uses anonymous &FTP; access, which may restrict your access to files on the &FTP; server. If you have an account on the server, you can supply your user <abbrev
+>ID</abbrev
+> as part of the <acronym
+>URL</acronym
+>, like this: <userinput
+><command
+>ftp://</command
+><parameter
+>userid</parameter
+>@<parameter
+>server</parameter
+>/<parameter
+>folder</parameter
+></userinput
+> </para>
+
+<para
+>&konqueror; will prompt you for your password, and if the login succeeds, you will have full access to your files on the server. </para>
+</note>
+
+<para
+>If you are used to the <trademark
+><application
+>WinZip</application
+></trademark
+> utility on &Microsoft; &Windows;, then you will be happy to hear that &kde; can look into tar archives, too. It treats such archives just like a normal folder, and you can browse into the archive, open files, &etc; In general, accessing files on the Internet and in archives should look and feel just like accessing files on your local disk, except for delays imposed by the network and extracting the archive. </para>
+</sect1>
+
+<sect1 id="using-templates">
+<title
+>Using Templates to access Applications and Devices</title>
+
+<para
+>In &kde; it's easy to put icons on the panel or the desktop to access your applications. It's just as easy to add icons to access other items of interest. &kde; has templates for shortcuts to: </para>
+
+<itemizedlist>
+<listitem>
+<para
+>Applications </para>
+</listitem>
+<listitem>
+<para
+>Printers </para>
+</listitem>
+<listitem>
+<para
+>Mountable Devices (&eg; floppy drives) </para>
+</listitem
+> 
+<listitem>
+<para
+>Internet resources (&eg; <acronym
+>WWW</acronym
+> documents, &FTP; folders) </para>
+</listitem>
+<listitem>
+<para
+>Documents for some of &kde;'s &koffice; applications. </para>
+</listitem>
+</itemizedlist>
+
+<para
+>You can add any of these items to the desktop by &RMB; clicking where you want the icon, and choosing <guisubmenu
+>Create New</guisubmenu
+> and selecting the item you want to link to. </para>
+
+<para
+>Nearly every item in the &kmenu;, on the desktop, and on the panel refers to a <literal role="extension"
+>.desktop</literal
+> file on disk. The <literal role="extension"
+>.desktop</literal
+> file specifies what icon to display, as well as specific information about what the icon represents (an application, device, or <acronym
+>URL</acronym
+>). You can drag any <literal role="extension"
+>.desktop</literal
+> file to the panel to create a quick-launch button. </para>
+
+<!-- 
+<sect2>
+<title
+>Setting up printers</title>
+
+<para>
+You can create icons for your printers so that you can print a file by
+dragging it to a printer icon. Here's how:
+</para>
+
+<procedure>
+<step
+><para
+>Open the Templates folder located on the desktop. </para
+></step>
+<step
+><para
+>Drag the Program icon in the folder to the desktop. Choose
+<guimenuitem
+>Copy</guimenuitem
+> from the menu that appears when you drop the
+icon.</para
+></step>
+<step
+><para
+><mousebutton
+>Right</mousebutton
+> click the new icon, and choose
+<guimenuitem
+>Properties</guimenuitem
+> from the context menu.</para
+></step>
+<step
+><para
+>On the <guilabel
+>General</guilabel
+> tab, change the name to
+<filename
+>Printer.kdelnk</filename
+>.</para
+></step>
+<step
+><para
+>On the <guilabel
+>Execute</guilabel
+> tab, enter the following in the
+first <guilabel
+>Execute</guilabel
+> field:</para>
+<screen
+><command>lpr <option>%f</option></command></screen>
+<note
+><para
+>This example assumes that you print using the <command
+>lpr</command>
+command. If you use a different command, enter the one you
+use.</para
+></note
+></step>
+<step
+><para
+>Still in the <guilabel
+>Execute</guilabel
+> tab, click the icon that
+looks like a <guiicon
+>cog</guiicon
+>, and select the <guiicon
+>Printer</guiicon
+> icon from the list that appears.</para
+></step>
+</procedure>
+
+<para
+>Now you should be able to drag a file to the Printer icon and have it
+printed on your default printer.</para
+> 
+</sect2>
+
+--> 
+
+<sect2>
+<title
+>Mounting devices</title>
+
+<para
+>&UNIX; provides access to storage devices other than the primary <hardware
+>hard disk</hardware
+> through a process called <emphasis
+>mounting</emphasis
+>. &kde; uses <literal role="extension"
+>.desktop</literal
+> files to allow you to easily mount, unmount, and access files on secondary storage devices such as <hardware
+>floppy</hardware
+> drives and &cdrom; drives. </para>
+
+<para
+>As an example, here are the steps needed to create an icon to access files on a floppy disk: </para>
+
+<note>
+<para
+>Many systems require you to be logged in as <systemitem class="username"
+>root</systemitem
+> to mount and unmount devices. </para>
+</note>
+
+<procedure>
+<step>
+<para
+><mousebutton
+>Right</mousebutton
+> click on the desktop and choose <menuchoice
+><guisubmenu
+>Create New</guisubmenu
+> <guimenuitem
+>Floppy Device...</guimenuitem
+></menuchoice
+>. </para>
+</step>
+<step>
+<para
+>On the <guilabel
+>General</guilabel
+> tab of the resulting dialogue, change the name to whatever you like, in the text box at the top. </para>
+</step>
+
+<step>
+<para
+>On the <guilabel
+>Device</guilabel
+> tab, enter <filename class="devicefile"
+>/dev/fd0</filename
+> (or the path to the floppy device as it is named on your system) as the <guilabel
+>Device</guilabel
+>. </para>
+</step>
+<step>
+<para
+>You can add a <guilabel
+>Mount Point</guilabel
+> here too. This should be an existing folder, but empty. Common mount points are <filename class="directory"
+>/mnt/floppy</filename
+> or <filename class="directory"
+>/floppy</filename
+>, but you can just as easily have floppy disks mounted on <filename class="directory"
+>~/mydisk</filename
+> if you want. </para>
+</step
+> 
+<step>
+<para
+>Click the <guilabel
+>Unmounted Icon</guilabel
+> and select the picture of a floppy disk without the green light. </para>
+</step>
+<step>
+<para
+>Once you're happy with your choices, choose <guibutton
+>OK</guibutton
+> and you are finished! </para>
+</step>
+</procedure>
+
+<para
+>Now, place a properly formatted floppy in the drive and click the <guiicon
+>Floppy</guiicon
+> icon to have &kde; mount the floppy drive and display the files on the disk. Before removing the disk from the drive, &RMB; click the <guiicon
+>Floppy</guiicon
+> icon and choose <guimenuitem
+>Unmount</guimenuitem
+> from the menu. </para>
+
+</sect2>
+</sect1>
+</chapter>
+
+<chapter id="configure">
+<title
+>Configuring your desktop</title>
+
+<para
+>If you do not like something about the way the desktop looks or operates, you can probably change it. &kde; is very configurable and you can change almost every aspect of the appearance and the behaviour of your desktop. Unlike many other &UNIX; desktop environments, you do not have to edit cryptic configuration files either (but you can if you really want to!) You use the &kcontrol;, a special program for configuring your desktop. </para>
+
+<sect1 id="using-kde-control">
+<title
+>Using the <application
+>&kde; Control Centre</application
+></title>
+
+<para
+>Launch the &kcontrol; from the <link linkend="starter"
+>&kmenu;</link
+>. A window with two panes appears, displaying a list of modules in the left pane. </para
+>  
+
+<para
+>Open a module by clicking its name; a list of submodules will appear. Then, click one of the submodule category names to edit its configuration in the right pane. </para>
+
+<para
+>Changing the configuration is fairly straightforward. A help button is available on each configuration panel to explain settings that are not obvious. Each panel has buttons labelled <guibutton
+>Help</guibutton
+>, <guibutton
+>Use Defaults</guibutton
+>, <guibutton
+>Apply</guibutton
+>, and <guibutton
+>Reset</guibutton
+>, which work as follows: </para>
+
+<variablelist>
+<varlistentry>
+<term
+><guibutton
+>Help</guibutton
+></term>
+<listitem>
+<para
+>Displays a short help text in the left hand pane, including a link to a longer manual for the module in question. </para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+><guibutton
+>Use Defaults</guibutton
+></term>
+<listitem>
+<para
+>Sets all the options in the current module back to the default at the time &kde; was installed. </para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+><guibutton
+>Apply</guibutton
+></term>
+<listitem>
+<para
+>Applies the current settings in the currently open module. </para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+><guibutton
+>Reset</guibutton
+></term>
+<listitem>
+<para
+>Resets the options to the state they were in when you opened the module. If you have already used the <guibutton
+>Apply</guibutton
+> button, then this button will reset the options to the state they were in when you pressed <guibutton
+>Apply</guibutton
+>. </para>
+</listitem>
+</varlistentry>
+</variablelist>
+
+<note>
+<para
+>If you make changes on one configuration panel and move to a different module without clicking <guibutton
+>OK</guibutton
+> or <guibutton
+>Apply</guibutton
+> first, &kcontrol; will prompt you to ask whether your changes should be applied first. </para>
+</note>
+
+</sect1>
+
+<sect1 id="configuration-modules">
+<title
+>Configuration Modules</title>
+
+<para
+>Here is a brief overview of the major configuration modules categories: </para>
+
+<variablelist>
+<varlistentry>
+<term
+><guilabel
+>File Browsing</guilabel
+></term>
+<listitem>
+<para
+>Contains options that relate to how you view the contents of your local system. </para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+><guilabel
+>Information</guilabel
+></term>
+<listitem>
+<para
+>Contains modules that you normally can't use to change anything. They display useful information about your computer instead. </para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+><guilabel
+>Appearance &amp; Themes</guilabel
+></term>
+<listitem>
+<para
+>Here you find the modules that have the most visible effect on your environment: Colours, styles, window decorations. Nearly everything you see can be customised to suit your tastes, and the few things that can't be, soon will. </para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+><guilabel
+>Network</guilabel
+></term>
+<listitem>
+<para
+>The place to configure how your computer sees the world outside, as well as how the world sees you. Among other things, you can set up central email identities that many &kde; applications can use, to save you having to enter the same information over and over, you can set up SOCKS firewall support, and you can configure &Windows; (<acronym
+>SMB</acronym
+>) shares... and much more. </para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+><guilabel
+>Peripherals</guilabel
+></term>
+<listitem>
+<para
+>Contains settings for your keyboard and mouse, and for printers. </para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+><guilabel
+>Personalisation</guilabel
+></term>
+<listitem>
+<para
+>Here you can set up things that make your life easier, from accessibility features to localisation, so that &kde; applications know how you like to see numbers and dates formatted, for example. </para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+><guilabel
+>Power Control</guilabel
+></term>
+<listitem>
+<para
+>If your computer supports <acronym
+>APM</acronym
+> power saving features, or you are using a laptop, this is the place to configure them. </para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+><guilabel
+>Sound</guilabel
+></term>
+<listitem>
+<para
+>Configure the sound daemon (&artsd;) and other audio behaviour. </para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+><guilabel
+>System</guilabel
+></term>
+<listitem>
+<para
+>Here you can set the remaining system features - how the &konsole; and &kdm; applications behave, set up printing, and set your system date. You might not be able to set some of these options unless you are logged in as <systemitem class="username"
+>root</systemitem
+>, but &kcontrol; will let you know if this is the case. </para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+><guilabel
+>Web Browsing</guilabel
+></term>
+<listitem>
+<para
+>With the Internet, and especially the web, being such an integral part of today's computer world, there are many options to be set to enhance your experience. You'll find them all here, from setting up custom style sheets, to proxies and caching. </para>
+</listitem>
+</varlistentry>
+</variablelist>
+
+<para
+>Go ahead! Explore the configuration possibilities and discover the flexibility of &kde;. </para>
+
+</sect1>
+</chapter>
+
+<chapter id="logging-out">
+<title
+>Logging out</title>
+
+<para
+>We sincerely hope that using &kde; gives you so much fun and pleasure that you never want to log out. But if you do, simply choose <menuchoice
+><guimenu
+>K menu</guimenu
+> <guimenuitem
+>Logout</guimenuitem
+></menuchoice
+>. </para>
+
+<para
+>There is also a logout button directly on the panel, which looks like a small power button. Or you can press <keycombo action="simul"
+>&Ctrl; &Alt; <keycap
+>Delete</keycap
+></keycombo
+> to log out. </para>
+
+<sect1 id="session-management">
+<title
+>Session Management</title>
+
+<para
+>When you log out, &kde; can remember which applications you had open, as well as where all the windows were located, so that it can open them for you the next time you log in. This feature is termed <emphasis
+>Session Management</emphasis
+>. &kde;-aware applications will restore themselves to the state they were in when you logged out. For example, &kate; remembers which files you were editing. </para>
+
+<para
+>Non-&kde; applications do not memorise their state on logout, and &kde; will warn you to make sure that you have saved any important data in them when you start to log out. </para>
+
+<para
+>To illustrate session management, choose <menuchoice
+> <guimenu
+>K menu</guimenu
+><guisubmenu
+>Applications</guisubmenu
+> <guimenuitem
+>Editor</guimenuitem
+> </menuchoice
+> to start &kedit;. Open a text document to edit. Now log out and back in. You will observe that &kate; will be restored to the exact same position on the screen, including the right virtual desktop, and the document we left open in &kate; before we logged out is opened again automatically. &kate; will even remember whether you had unsaved changes to your document before you logged out and will save them to the file you were working on if you choose <guimenuitem
+>Save</guimenuitem
+> from the <guimenu
+>File</guimenu
+> menu. </para>
+
+</sect1>
+</chapter>
+
+<chapter id="kde-an-exciting-journey">
+<title
+>&kde;, an exciting Journey</title>
+
+<para
+>We hope you enjoyed this brief tour of the K Desktop environment and that this unique desktop environment will help you get your work done faster and more comfortably than ever. </para>
+
+<para
+>Please remember that the &kde; project is not a commercial venture, but rather a project run by volunteers from all over the world. We would like to invite you to join the &kde; project and become part of this unique network of people. If you are a programmer you might consider helping us write &kde; applications. If you are an artist or have experience with graphic design, consider creating icons sets, colour schemes, sound schemes and logos for &kde;. If you enjoy writing we would love for you to join our documentation project. </para>
+
+<para
+>As you can see there are many ways in which you can help. You are cordially invited to join this world-wide network of people dedicated to making &kde; the best desktop environment for any computer. Please visit <ulink url="http://www.kde.org"
+>www.kde.org</ulink
+> for more information. </para>
+
+<para>
+<emphasis
+>Welcome aboard on this exciting journey, </emphasis>
+</para>
+<para>
+<literal
+>Your &kde; Team</literal>
+</para>
+</chapter>
+
+<chapter id="advanced-topics">
+<title
+>Advanced Topics</title>
+
+<sect1 id="mime">
+<title
+>&MIME; Types</title>
+
+<para
+>&kde; comes with a number of &MIME; types predefined, but you can add your own &MIME; types by choosing <menuchoice
+><guimenu
+>Settings</guimenu
+> <guisubmenu
+>Configure Konqueror...</guisubmenu
+> </menuchoice
+> and then <guilabel
+>File Associations</guilabel
+> in a &konqueror; window. </para>
+
+<para
+>&kde;'s handling of &MIME; types is very powerful, and very configurable. On the one hand, you can set a default action to be performed when you click on a file in &konqueror;. Just as usefully, you can add many more actions, which are then available with a &RMB; click menu on the file in question. </para>
+
+<!-- Note: this is copied from the user-guide - eventually these two -->
+<!-- docs will merge, so there's no point adding new text in both, but -->
+<!-- for the moment they have a slightly different audience -->
+<procedure>
+<title
+>To link a certain file type with a particular application:</title>
+<step>
+<para
+>Make sure the application you want to start this file type has an entry in the &kmenu;. </para>
+</step>
+
+<step>
+<para
+>In &konqueror; find or make a file with the extension you wish to link. </para>
+</step
+> 
+
+<step>
+<para
+><mousebutton
+>Right</mousebutton
+> click on the file, and choose <guimenuitem
+>Edit File Type</guimenuitem
+> from the context menu, or choose <menuchoice
+><guimenu
+>Edit</guimenu
+><guimenuitem
+>Edit File Type</guimenuitem
+></menuchoice
+> in &konqueror;'s menu bar. </para>
+</step>
+
+<step
+> <para
+>Add file masks for the application by clicking the <guibutton
+>Add</guibutton
+> button, and entering the file pattern you want. Remember that &UNIX; is case sensitive, so you may need to add variations - <userinput
+>*.mp3</userinput
+> may need <userinput
+>*.MP3</userinput
+> added as well, for example. Add as many extensions as you like in this way. </para
+> </step>
+
+<step>
+<para
+>Add a description if you like. This is optional. </para>
+</step>
+
+<step>
+<para
+>In the section labeled <guilabel
+>Application Preference Order</guilabel
+>, press the <guibutton
+>Add</guibutton
+> button. A miniature copy of the &kmenu; will open, where you can choose the application you want files of this type to be opened with. </para>
+</step>
+
+<step>
+<para
+>Sometimes, you may want to use a different application to open this file type. For example, you might like to use &kate; to open text files you wish to edit, and &kedit; for text files that you just want to take a quick peek into. You can add more applications in the same way as you did in the last step, and you can change the preferred order using the <guibutton
+>Move Up</guibutton
+> and <guibutton
+>Move Down</guibutton
+> buttons. </para>
+</step
+> 
+
+<step>
+<para
+>If you're satisfied with your choices, you can click the <guibutton
+>Apply</guibutton
+> button to save your changes without closing the dialogue box. This gives you the opportunity to test in the <application
+>Konqueror</application
+> window that your file association is correct. You can choose <guibutton
+>OK</guibutton
+> to save your changes and close the dialogue box, or <guibutton
+>Cancel</guibutton
+> if you have changed your mind and just want to close the dialogue box. </para>
+</step>
+</procedure>
+  
+<para
+>Be sure to try your new association by opening a folder containing a file of the type you just selected. Click on the file, and the program needed to edit it should start. </para>
+
+<note>
+<para
+>&MIME; types are a way of describing the contents of files. You may be used to using file extensions for that purpose, and you may know that on &UNIX; systems the file extension often bears little or no relation to the contents of the file. On the other hand, it may be vital - for example, some implementations of <command
+>gunzip</command
+> will not operate on files that are not named <literal role="extension"
+>.gz</literal
+>. </para>
+
+<para
+>&MIME; types naturally make use of filename patterns, but not necessarily the extensions - you can set up any filename pattern you like. For example, if you always want to open any files relating to a particular client with &kate;, and you make a habit of naming the files with the client's name at the beginning so that they naturally group in the &konqueror; window, then you can set up a filename pattern that matches <literal
+>^<replaceable
+>clientname</replaceable
+>*</literal
+>. Then any files that have <replaceable
+>clientname</replaceable
+> at the beginning (the <token
+>^</token
+> character means <quote
+>starts with...</quote
+>) and without any regard to the rest of the filename. </para>
+</note>
+
+</sect1>
+
+</chapter>
+<chapter id="credits">
+<title
+>Credits</title>
+<sect1 id="authors">
+<title
+>Authors</title>
+
+<itemizedlist>
+<listitem
+><para
+>Matthias Ettrich <email
+>ettrich@kde.org</email
+></para
+></listitem>
+<listitem
+><para
+>Kalle Dahlheimer <email
+>kalle@kde.org</email
+></para
+></listitem>
+<listitem
+><para
+>Torben Weiss <email
+>weis@kde.org</email
+></para
+></listitem>
+<listitem
+><para
+>Bernd Wuebben <email
+>wuebben@kde.org</email
+></para
+></listitem>
+<listitem
+><para
+>Stephen Schaub <email
+>sschaub@bju.edu</email
+> - Editor</para
+></listitem>
+<listitem
+><para
+>Robert Williams <email
+>rwilliams@kde.org</email
+> - Editor</para
+></listitem>
+<listitem
+><para
+>Lauri Watts <email
+>lauri@kde.org</email
+></para
+></listitem>
+</itemizedlist>
+
+<para
+>Conversion to British English: Malcolm Hunter <email
+>malcolm.hunter@gmx.co.uk</email
+></para
+> 
+&underFDL; </sect1>
+</chapter>
+</book>
+
+<!--
+Local Variables:
+mode: sgml
+sgml-omittag: nil
+sgml-shorttag: t
+End:
+-->
+
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/support.docbook b/tde-i18n-en_GB/docs/tdebase/khelpcenter/support.docbook
new file mode 100644
index 00000000000..c15b43176d2
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/support.docbook
@@ -0,0 +1,102 @@
+<chapter id="supporting-kde">
+<chapterinfo
+><date
+>2002-03-04</date
+> <releaseinfo
+>2.02.00</releaseinfo
+> </chapterinfo>
+<title
+>Supporting &kde;</title>
+<anchor id="support"/>
+
+<sect1 id="supporting-kde-introduction">
+<title
+>Supporting &kde;</title>
+
+<para
+>If you are new to &kde;, the &kde; project might look like big machinery to you. Undoubtedly, &kde; is no longer a small project, nevertheless it is very important to realise that it is easy to <quote
+>make a difference</quote
+> in the &kde; world. </para>
+
+<para
+>There is always a need for dedicated developers, graphic artists, sound engineers, translators and documentation writers. Consider jumping aboard this exciting international project and make yourself a name in the software world.</para>
+
+<para
+>Along the way you will make countless friends and acquaintances all over the world. Also, the satisfaction that stems from doing actual hands-on work, that will benefit an uncountable number of users world-wide, and from seeing an unparalleled project grow, is hard to beat. Please consider joining and supporting &kde; and hop aboard this exciting journey towards a free and open alternative computing platform. </para>
+
+</sect1>
+
+<sect1 id="supporting-kde-get-started">
+<title
+>How to get started</title>
+
+<itemizedlist>
+
+<listitem
+><para
+>Subscribe to the <link linkend="contact"
+>&kde; mailing lists</link
+> that interest you. </para
+></listitem>
+
+<listitem
+><para
+>Read the <ulink url="http://lists.kde.org"
+>mailing list</ulink
+> archives in order to get a feel for &kde; development. </para
+></listitem>
+
+<listitem
+><para
+>Learn how to program using the &kde; application framework and join the friendly &kde; developers' community. </para
+></listitem>
+
+</itemizedlist>
+
+</sect1>
+
+<sect1 id="supporting-kde-financial-support">
+<title
+>Supporting financially</title>
+
+<para
+>The &kde; team is working very hard on providing you with the best desktop available for the &UNIX; operating system. &kde; is available for free and will always be available for free, including each and every line of its source code, for everyone to modify and distribute. If you enjoy and use &kde; please consider supporting the &kde; Project financially. &kde; is in constant need of funds in order to finance its operations. </para>
+
+<para
+>If your busy schedule or skills do not permit you to be actively involved in &kde; development, please consider supporting &kde; financially by sending a donation to: </para>
+
+<para
+>You can send standard US cheques to the following address: </para>
+
+<literallayout
+>K Desktop Environment e.V.
+Mirko Boehm
+2029 Chadds Ford Drive
+Reston, VA 20191
+USA
+</literallayout>
+
+<para
+>Use "KDE e.V. - Mirko Boehm" in the "Pay to the order of..." line. </para>
+
+<para
+>From Europe, you may remit your donation to (be aware of a fee if wiring from outside of Germany): </para>
+
+<literallayout
+>K Desktop Environment e.V.
+Account-Nr. 0 66 64 46
+BLZ 200 700 24
+Deutsche Bank 24
+</literallayout>
+
+<para
+>Please contact Mirko Boehm <email
+>kde-ev-treasurer@kde.org</email
+> if you have any questions. </para>
+
+<para
+>Your contribution is very much appreciated. Thank you! </para>
+
+</sect1>
+</chapter>
+
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/Makefile.am b/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/Makefile.am
new file mode 100644
index 00000000000..8161986a832
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/Makefile.am
@@ -0,0 +1,4 @@
+KDE_LANG = en_GB
+SUBDIRS = $(AUTODIRS)
+KDE_DOCS = khelpcenter/userguide
+KDE_MANS = AUTO
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/Makefile.in b/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/Makefile.in
new file mode 100644
index 00000000000..5f33e6883c6
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/Makefile.in
@@ -0,0 +1,635 @@
+# Makefile.in generated by automake 1.10.1 from Makefile.am.
+# KDE tags expanded automatically by am_edit - $Revision: 483858 $ 
+# @configure_input@
+
+# Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002,
+# 2003, 2004, 2005, 2006, 2007, 2008  Free Software Foundation, Inc.
+# This Makefile.in is free software; the Free Software Foundation
+# gives unlimited permission to copy and/or distribute it,
+# with or without modifications, as long as this notice is preserved.
+
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY, to the extent permitted by law; without
+# even the implied warranty of MERCHANTABILITY or FITNESS FOR A
+# PARTICULAR PURPOSE.
+
+@SET_MAKE@
+VPATH = @srcdir@
+pkgdatadir = $(datadir)/@PACKAGE@
+pkglibdir = $(libdir)/@PACKAGE@
+pkgincludedir = $(includedir)/@PACKAGE@
+am__cd = CDPATH="$${ZSH_VERSION+.}$(PATH_SEPARATOR)" && cd
+install_sh_DATA = $(install_sh) -c -m 644
+install_sh_PROGRAM = $(install_sh) -c
+install_sh_SCRIPT = $(install_sh) -c
+INSTALL_HEADER = $(INSTALL_DATA)
+transform = $(program_transform_name)
+NORMAL_INSTALL = :
+PRE_INSTALL = :
+POST_INSTALL = :
+NORMAL_UNINSTALL = :
+PRE_UNINSTALL = :
+POST_UNINSTALL = :
+subdir = docs/tdebase/khelpcenter/userguide
+DIST_COMMON = $(srcdir)/Makefile.am $(srcdir)/Makefile.in
+ACLOCAL_M4 = $(top_srcdir)/aclocal.m4
+am__aclocal_m4_deps = $(top_srcdir)/acinclude.m4 \
+	$(top_srcdir)/configure.in
+am__configure_deps = $(am__aclocal_m4_deps) $(CONFIGURE_DEPENDENCIES) \
+	$(ACLOCAL_M4)
+mkinstalldirs = $(SHELL) $(top_srcdir)/mkinstalldirs
+CONFIG_HEADER = $(top_builddir)/config.h
+CONFIG_CLEAN_FILES =
+SOURCES =
+DIST_SOURCES =
+#>- RECURSIVE_TARGETS = all-recursive check-recursive dvi-recursive \
+#>- 	html-recursive info-recursive install-data-recursive \
+#>- 	install-dvi-recursive install-exec-recursive \
+#>- 	install-html-recursive install-info-recursive \
+#>- 	install-pdf-recursive install-ps-recursive install-recursive \
+#>- 	installcheck-recursive installdirs-recursive pdf-recursive \
+#>- 	ps-recursive uninstall-recursive
+#>+ 7
+RECURSIVE_TARGETS = all-recursive check-recursive dvi-recursive \
+	html-recursive info-recursive install-data-recursive \
+	install-dvi-recursive install-exec-recursive \
+	install-html-recursive install-info-recursive \
+	install-pdf-recursive install-ps-recursive install-recursive \
+	installcheck-recursive installdirs-recursive pdf-recursive \
+	ps-recursive uninstall-recursive nmcheck-recursive bcheck-recursive
+RECURSIVE_CLEAN_TARGETS = mostlyclean-recursive clean-recursive	\
+  distclean-recursive maintainer-clean-recursive
+ETAGS = etags
+CTAGS = ctags
+DIST_SUBDIRS = $(SUBDIRS)
+#>- DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST)
+#>+ 1
+DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST) $(KDE_DIST)
+ACLOCAL = @ACLOCAL@
+AMTAR = @AMTAR@
+ARTSCCONFIG = @ARTSCCONFIG@
+AUTOCONF = @AUTOCONF@
+AUTODIRS = @AUTODIRS@
+AUTOHEADER = @AUTOHEADER@
+AUTOMAKE = @AUTOMAKE@
+AWK = @AWK@
+CONF_FILES = @CONF_FILES@
+CYGPATH_W = @CYGPATH_W@
+DCOPIDL = @DCOPIDL@
+DCOPIDL2CPP = @DCOPIDL2CPP@
+DCOPIDLNG = @DCOPIDLNG@
+DCOP_DEPENDENCIES = @DCOP_DEPENDENCIES@
+DEFS = @DEFS@
+ECHO_C = @ECHO_C@
+ECHO_N = @ECHO_N@
+ECHO_T = @ECHO_T@
+GMSGFMT = @GMSGFMT@
+INSTALL = @INSTALL@
+INSTALL_DATA = @INSTALL_DATA@
+INSTALL_PROGRAM = @INSTALL_PROGRAM@
+INSTALL_SCRIPT = @INSTALL_SCRIPT@
+INSTALL_STRIP_PROGRAM = @INSTALL_STRIP_PROGRAM@
+KCFG_DEPENDENCIES = @KCFG_DEPENDENCIES@
+KCONFIG_COMPILER = @KCONFIG_COMPILER@
+KDECONFIG = @KDECONFIG@
+KDE_EXTRA_RPATH = @KDE_EXTRA_RPATH@
+KDE_RPATH = @KDE_RPATH@
+KDE_XSL_STYLESHEET = @KDE_XSL_STYLESHEET@
+LIBOBJS = @LIBOBJS@
+LIBS = @LIBS@
+LN_S = @LN_S@
+LTLIBOBJS = @LTLIBOBJS@
+MAKEINFO = @MAKEINFO@
+MAKEKDEWIDGETS = @MAKEKDEWIDGETS@
+MCOPIDL = @MCOPIDL@
+MEINPROC = @MEINPROC@
+MKDIR_P = @MKDIR_P@
+MSGFMT = @MSGFMT@
+PACKAGE = @PACKAGE@
+PACKAGE_BUGREPORT = @PACKAGE_BUGREPORT@
+PACKAGE_NAME = @PACKAGE_NAME@
+PACKAGE_STRING = @PACKAGE_STRING@
+PACKAGE_TARNAME = @PACKAGE_TARNAME@
+PACKAGE_VERSION = @PACKAGE_VERSION@
+PATH_SEPARATOR = @PATH_SEPARATOR@
+SET_MAKE = @SET_MAKE@
+SHELL = @SHELL@
+STRIP = @STRIP@
+TOPSUBDIRS = @TOPSUBDIRS@
+VERSION = @VERSION@
+XGETTEXT = @XGETTEXT@
+XMLLINT = @XMLLINT@
+X_RPATH = @X_RPATH@
+abs_builddir = @abs_builddir@
+abs_srcdir = @abs_srcdir@
+abs_top_builddir = @abs_top_builddir@
+abs_top_srcdir = @abs_top_srcdir@
+am__leading_dot = @am__leading_dot@
+am__tar = @am__tar@
+am__untar = @am__untar@
+#>- bindir = @bindir@
+#>+ 2
+DEPDIR = .deps
+bindir = @bindir@
+build_alias = @build_alias@
+builddir = @builddir@
+datadir = @datadir@
+datarootdir = @datarootdir@
+docdir = @docdir@
+dvidir = @dvidir@
+exec_prefix = @exec_prefix@
+host_alias = @host_alias@
+htmldir = @htmldir@
+includedir = @includedir@
+infodir = @infodir@
+install_sh = @install_sh@
+kde_appsdir = @kde_appsdir@
+kde_bindir = @kde_bindir@
+kde_confdir = @kde_confdir@
+kde_datadir = @kde_datadir@
+kde_htmldir = @kde_htmldir@
+kde_icondir = @kde_icondir@
+kde_kcfgdir = @kde_kcfgdir@
+kde_libs_htmldir = @kde_libs_htmldir@
+kde_libs_prefix = @kde_libs_prefix@
+kde_locale = @kde_locale@
+kde_mimedir = @kde_mimedir@
+kde_moduledir = @kde_moduledir@
+kde_servicesdir = @kde_servicesdir@
+kde_servicetypesdir = @kde_servicetypesdir@
+kde_sounddir = @kde_sounddir@
+kde_styledir = @kde_styledir@
+kde_templatesdir = @kde_templatesdir@
+kde_wallpaperdir = @kde_wallpaperdir@
+kde_widgetdir = @kde_widgetdir@
+tdeinitdir = @tdeinitdir@
+libdir = @libdir@
+libexecdir = @libexecdir@
+localedir = @localedir@
+localstatedir = @localstatedir@
+mandir = @mandir@
+mkdir_p = @mkdir_p@
+oldincludedir = @oldincludedir@
+pdfdir = @pdfdir@
+prefix = @prefix@
+program_transform_name = @program_transform_name@
+psdir = @psdir@
+sbindir = @sbindir@
+sharedstatedir = @sharedstatedir@
+srcdir = @srcdir@
+sysconfdir = @sysconfdir@
+target_alias = @target_alias@
+top_builddir = @top_builddir@
+top_srcdir = @top_srcdir@
+xdg_appsdir = @xdg_appsdir@
+xdg_directorydir = @xdg_directorydir@
+xdg_menudir = @xdg_menudir@
+KDE_LANG = en_GB
+#>- SUBDIRS = $(AUTODIRS)
+#>+ 1
+SUBDIRS =.
+KDE_DOCS = khelpcenter/userguide
+KDE_MANS = AUTO
+#>- all: all-recursive
+#>+ 1
+all: docs-am  all-recursive
+
+.SUFFIXES:
+$(srcdir)/Makefile.in:  $(srcdir)/Makefile.am  $(am__configure_deps)
+#>- 	@for dep in $?; do \
+#>- 	  case '$(am__configure_deps)' in \
+#>- 	    *$$dep*) \
+#>- 	      cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh \
+#>- 		&& exit 0; \
+#>- 	      exit 1;; \
+#>- 	  esac; \
+#>- 	done; \
+#>- 	echo ' cd $(top_srcdir) && $(AUTOMAKE) --gnu  docs/tdebase/khelpcenter/userguide/Makefile'; \
+#>- 	cd $(top_srcdir) && \
+#>- 	  $(AUTOMAKE) --gnu  docs/tdebase/khelpcenter/userguide/Makefile
+#>+ 12
+	@for dep in $?; do \
+	  case '$(am__configure_deps)' in \
+	    *$$dep*) \
+	      cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh \
+		&& exit 0; \
+	      exit 1;; \
+	  esac; \
+	done; \
+	echo ' cd $(top_srcdir) && $(AUTOMAKE) --gnu  docs/tdebase/khelpcenter/userguide/Makefile'; \
+	cd $(top_srcdir) && \
+	  $(AUTOMAKE) --gnu  docs/tdebase/khelpcenter/userguide/Makefile
+	cd $(top_srcdir) && perl ../scripts/admin/am_edit -p../scripts/admin docs/tdebase/khelpcenter/userguide/Makefile.in
+.PRECIOUS: Makefile
+Makefile: $(srcdir)/Makefile.in $(top_builddir)/config.status
+	@case '$?' in \
+	  *config.status*) \
+	    cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh;; \
+	  *) \
+	    echo ' cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__depfiles_maybe)'; \
+	    cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__depfiles_maybe);; \
+	esac;
+
+$(top_builddir)/config.status: $(top_srcdir)/configure $(CONFIG_STATUS_DEPENDENCIES)
+	cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
+
+$(top_srcdir)/configure:  $(am__configure_deps)
+	cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
+$(ACLOCAL_M4):  $(am__aclocal_m4_deps)
+	cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
+
+# This directory's subdirectories are mostly independent; you can cd
+# into them and run `make' without going through this Makefile.
+# To change the values of `make' variables: instead of editing Makefiles,
+# (1) if the variable is set in `config.status', edit `config.status'
+#     (which will cause the Makefiles to be regenerated when you run `make');
+# (2) otherwise, pass the desired values on the `make' command line.
+$(RECURSIVE_TARGETS):
+	@failcom='exit 1'; \
+	for f in x $$MAKEFLAGS; do \
+	  case $$f in \
+	    *=* | --[!k]*);; \
+	    *k*) failcom='fail=yes';; \
+	  esac; \
+	done; \
+	dot_seen=no; \
+	target=`echo $@ | sed s/-recursive//`; \
+	list='$(SUBDIRS)'; for subdir in $$list; do \
+	  echo "Making $$target in $$subdir"; \
+	  if test "$$subdir" = "."; then \
+	    dot_seen=yes; \
+	    local_target="$$target-am"; \
+	  else \
+	    local_target="$$target"; \
+	  fi; \
+	  (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS) $$local_target) \
+	  || eval $$failcom; \
+	done; \
+	if test "$$dot_seen" = "no"; then \
+	  $(MAKE) $(AM_MAKEFLAGS) "$$target-am" || exit 1; \
+	fi; test -z "$$fail"
+
+$(RECURSIVE_CLEAN_TARGETS):
+	@failcom='exit 1'; \
+	for f in x $$MAKEFLAGS; do \
+	  case $$f in \
+	    *=* | --[!k]*);; \
+	    *k*) failcom='fail=yes';; \
+	  esac; \
+	done; \
+	dot_seen=no; \
+	case "$@" in \
+	  distclean-* | maintainer-clean-*) list='$(DIST_SUBDIRS)' ;; \
+	  *) list='$(SUBDIRS)' ;; \
+	esac; \
+	rev=''; for subdir in $$list; do \
+	  if test "$$subdir" = "."; then :; else \
+	    rev="$$subdir $$rev"; \
+	  fi; \
+	done; \
+	rev="$$rev ."; \
+	target=`echo $@ | sed s/-recursive//`; \
+	for subdir in $$rev; do \
+	  echo "Making $$target in $$subdir"; \
+	  if test "$$subdir" = "."; then \
+	    local_target="$$target-am"; \
+	  else \
+	    local_target="$$target"; \
+	  fi; \
+	  (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS) $$local_target) \
+	  || eval $$failcom; \
+	done && test -z "$$fail"
+tags-recursive:
+	list='$(SUBDIRS)'; for subdir in $$list; do \
+	  test "$$subdir" = . || (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS) tags); \
+	done
+ctags-recursive:
+	list='$(SUBDIRS)'; for subdir in $$list; do \
+	  test "$$subdir" = . || (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS) ctags); \
+	done
+
+ID: $(HEADERS) $(SOURCES) $(LISP) $(TAGS_FILES)
+	list='$(SOURCES) $(HEADERS) $(LISP) $(TAGS_FILES)'; \
+	unique=`for i in $$list; do \
+	    if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
+	  done | \
+	  $(AWK) '{ files[$$0] = 1; nonemtpy = 1; } \
+	      END { if (nonempty) { for (i in files) print i; }; }'`; \
+	mkid -fID $$unique
+tags: TAGS
+
+TAGS: tags-recursive $(HEADERS) $(SOURCES)  $(TAGS_DEPENDENCIES) \
+		$(TAGS_FILES) $(LISP)
+	tags=; \
+	here=`pwd`; \
+	if ($(ETAGS) --etags-include --version) >/dev/null 2>&1; then \
+	  include_option=--etags-include; \
+	  empty_fix=.; \
+	else \
+	  include_option=--include; \
+	  empty_fix=; \
+	fi; \
+	list='$(SUBDIRS)'; for subdir in $$list; do \
+	  if test "$$subdir" = .; then :; else \
+	    test ! -f $$subdir/TAGS || \
+	      tags="$$tags $$include_option=$$here/$$subdir/TAGS"; \
+	  fi; \
+	done; \
+	list='$(SOURCES) $(HEADERS)  $(LISP) $(TAGS_FILES)'; \
+	unique=`for i in $$list; do \
+	    if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
+	  done | \
+	  $(AWK) '{ files[$$0] = 1; nonempty = 1; } \
+	      END { if (nonempty) { for (i in files) print i; }; }'`; \
+	if test -z "$(ETAGS_ARGS)$$tags$$unique"; then :; else \
+	  test -n "$$unique" || unique=$$empty_fix; \
+	  $(ETAGS) $(ETAGSFLAGS) $(AM_ETAGSFLAGS) $(ETAGS_ARGS) \
+	    $$tags $$unique; \
+	fi
+ctags: CTAGS
+CTAGS: ctags-recursive $(HEADERS) $(SOURCES)  $(TAGS_DEPENDENCIES) \
+		$(TAGS_FILES) $(LISP)
+	tags=; \
+	list='$(SOURCES) $(HEADERS)  $(LISP) $(TAGS_FILES)'; \
+	unique=`for i in $$list; do \
+	    if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
+	  done | \
+	  $(AWK) '{ files[$$0] = 1; nonempty = 1; } \
+	      END { if (nonempty) { for (i in files) print i; }; }'`; \
+	test -z "$(CTAGS_ARGS)$$tags$$unique" \
+	  || $(CTAGS) $(CTAGSFLAGS) $(AM_CTAGSFLAGS) $(CTAGS_ARGS) \
+	     $$tags $$unique
+
+GTAGS:
+	here=`$(am__cd) $(top_builddir) && pwd` \
+	  && cd $(top_srcdir) \
+	  && gtags -i $(GTAGS_ARGS) $$here
+
+distclean-tags:
+	-rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
+
+#>- distdir: $(DISTFILES)
+#>+ 1
+distdir: distdir-nls  $(DISTFILES)
+	@srcdirstrip=`echo "$(srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \
+	topsrcdirstrip=`echo "$(top_srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \
+	list='$(DISTFILES)'; \
+	  dist_files=`for file in $$list; do echo $$file; done | \
+	  sed -e "s|^$$srcdirstrip/||;t" \
+	      -e "s|^$$topsrcdirstrip/|$(top_builddir)/|;t"`; \
+	case $$dist_files in \
+	  */*) $(MKDIR_P) `echo "$$dist_files" | \
+			   sed '/\//!d;s|^|$(distdir)/|;s,/[^/]*$$,,' | \
+			   sort -u` ;; \
+	esac; \
+	for file in $$dist_files; do \
+	  if test -f $$file || test -d $$file; then d=.; else d=$(srcdir); fi; \
+	  if test -d $$d/$$file; then \
+	    dir=`echo "/$$file" | sed -e 's,/[^/]*$$,,'`; \
+	    if test -d $(srcdir)/$$file && test $$d != $(srcdir); then \
+	      cp -pR $(srcdir)/$$file $(distdir)$$dir || exit 1; \
+	    fi; \
+	    cp -pR $$d/$$file $(distdir)$$dir || exit 1; \
+	  else \
+	    test -f $(distdir)/$$file \
+	    || cp -p $$d/$$file $(distdir)/$$file \
+	    || exit 1; \
+	  fi; \
+	done
+	list='$(DIST_SUBDIRS)'; for subdir in $$list; do \
+	  if test "$$subdir" = .; then :; else \
+	    test -d "$(distdir)/$$subdir" \
+	    || $(MKDIR_P) "$(distdir)/$$subdir" \
+	    || exit 1; \
+	    distdir=`$(am__cd) $(distdir) && pwd`; \
+	    top_distdir=`$(am__cd) $(top_distdir) && pwd`; \
+	    (cd $$subdir && \
+	      $(MAKE) $(AM_MAKEFLAGS) \
+	        top_distdir="$$top_distdir" \
+	        distdir="$$distdir/$$subdir" \
+		am__remove_distdir=: \
+		am__skip_length_check=: \
+	        distdir) \
+	      || exit 1; \
+	  fi; \
+	done
+check-am: all-am
+check: check-recursive
+all-am: Makefile
+installdirs: installdirs-recursive
+installdirs-am:
+install: install-recursive
+install-exec: install-exec-recursive
+install-data: install-data-recursive
+#>- uninstall: uninstall-recursive
+#>+ 1
+uninstall: uninstall-docs uninstall-nls  uninstall-recursive
+
+install-am: all-am
+	@$(MAKE) $(AM_MAKEFLAGS) install-exec-am install-data-am
+
+installcheck: installcheck-recursive
+install-strip:
+	$(MAKE) $(AM_MAKEFLAGS) INSTALL_PROGRAM="$(INSTALL_STRIP_PROGRAM)" \
+	  install_sh_PROGRAM="$(INSTALL_STRIP_PROGRAM)" INSTALL_STRIP_FLAG=-s \
+	  `test -z '$(STRIP)' || \
+	    echo "INSTALL_PROGRAM_ENV=STRIPPROG='$(STRIP)'"` install
+mostlyclean-generic:
+
+clean-generic:
+
+distclean-generic:
+	-test -z "$(CONFIG_CLEAN_FILES)" || rm -f $(CONFIG_CLEAN_FILES)
+
+maintainer-clean-generic:
+	@echo "This command is intended for maintainers to use"
+	@echo "it deletes files that may require special tools to rebuild."
+#>- clean: clean-recursive
+#>+ 1
+clean: kde-rpo-clean  clean-recursive
+
+#>- clean-am: clean-generic mostlyclean-am
+#>+ 1
+clean-am: clean-docs clean-bcheck  clean-generic mostlyclean-am
+
+distclean: distclean-recursive
+	-rm -f Makefile
+distclean-am: clean-am distclean-generic distclean-tags
+
+dvi: dvi-recursive
+
+dvi-am:
+
+html: html-recursive
+
+info: info-recursive
+
+info-am:
+
+#>- install-data-am:
+#>+ 1
+install-data-am: install-docs install-nls 
+
+install-dvi: install-dvi-recursive
+
+install-exec-am:
+
+install-html: install-html-recursive
+
+install-info: install-info-recursive
+
+install-man:
+
+install-pdf: install-pdf-recursive
+
+install-ps: install-ps-recursive
+
+installcheck-am:
+
+maintainer-clean: maintainer-clean-recursive
+	-rm -f Makefile
+maintainer-clean-am: distclean-am maintainer-clean-generic
+
+mostlyclean: mostlyclean-recursive
+
+mostlyclean-am: mostlyclean-generic
+
+pdf: pdf-recursive
+
+pdf-am:
+
+ps: ps-recursive
+
+ps-am:
+
+uninstall-am:
+
+.MAKE: $(RECURSIVE_CLEAN_TARGETS) $(RECURSIVE_TARGETS) install-am \
+	install-strip
+
+.PHONY: $(RECURSIVE_CLEAN_TARGETS) $(RECURSIVE_TARGETS) CTAGS GTAGS \
+	all all-am check check-am clean clean-generic ctags \
+	ctags-recursive distclean distclean-generic distclean-tags \
+	distdir dvi dvi-am html html-am info info-am install \
+	install-am install-data install-data-am install-dvi \
+	install-dvi-am install-exec install-exec-am install-html \
+	install-html-am install-info install-info-am install-man \
+	install-pdf install-pdf-am install-ps install-ps-am \
+	install-strip installcheck installcheck-am installdirs \
+	installdirs-am maintainer-clean maintainer-clean-generic \
+	mostlyclean mostlyclean-generic pdf pdf-am ps ps-am tags \
+	tags-recursive uninstall uninstall-am
+
+# Tell versions [3.59,3.63) of GNU make to not export all variables.
+# Otherwise a system limit (for SysV at least) may be exceeded.
+.NOEXPORT:
+
+#>+ 2
+KDE_DIST=installation.docbook history.docbook tdeedu-apps.docbook tdepim-apps.docbook tdegraphics-apps.docbook koffice-apps.docbook Makefile.in tdeutils-apps.docbook tdenetwork-apps.docbook about-desktop.docbook first-impressions.docbook ug-faq.docbook intro.docbook shortcuts.docbook more-help.docbook index.docbook staff.docbook tdegames-apps.docbook tdetoys-apps.docbook tdebase-apps.docbook tdemultimedia-apps.docbook tdeadmin-apps.docbook Makefile.am getting-started.docbook notices-trademarks.docbook index.cache.bz2 
+
+#>+ 24
+index.cache.bz2: $(srcdir)/index.docbook $(KDE_XSL_STYLESHEET) first-impressions.docbook tdeedu-apps.docbook tdenetwork-apps.docbook intro.docbook tdegraphics-apps.docbook tdetoys-apps.docbook tdeadmin-apps.docbook about-desktop.docbook index.docbook more-help.docbook history.docbook tdemultimedia-apps.docbook tdepim-apps.docbook tdeutils-apps.docbook shortcuts.docbook installation.docbook tdegames-apps.docbook ug-faq.docbook getting-started.docbook koffice-apps.docbook notices-trademarks.docbook tdebase-apps.docbook staff.docbook 
+	@if test -n "$(MEINPROC)"; then echo $(MEINPROC) --check --cache index.cache.bz2 $(srcdir)/index.docbook; $(MEINPROC) --check --cache index.cache.bz2 $(srcdir)/index.docbook; fi
+
+docs-am: index.cache.bz2
+
+install-docs: docs-am install-nls
+	$(mkinstalldirs) $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/userguide
+	@if test -f index.cache.bz2; then \
+	echo $(INSTALL_DATA) index.cache.bz2 $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/userguide/; \
+	$(INSTALL_DATA) index.cache.bz2 $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/userguide/; \
+	elif test -f  $(srcdir)/index.cache.bz2; then \
+	echo $(INSTALL_DATA) $(srcdir)/index.cache.bz2 $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/userguide/; \
+	$(INSTALL_DATA) $(srcdir)/index.cache.bz2 $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/userguide/; \
+	fi
+	-rm -f $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/userguide/common
+	$(LN_S) $(kde_libs_htmldir)/$(KDE_LANG)/common $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/userguide/common
+
+uninstall-docs:
+	-rm -rf $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/userguide
+
+clean-docs:
+	-rm -f index.cache.bz2
+
+
+#>+ 13
+install-nls:
+	$(mkinstalldirs) $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/userguide
+	@for base in first-impressions.docbook tdeedu-apps.docbook tdenetwork-apps.docbook intro.docbook tdegraphics-apps.docbook tdetoys-apps.docbook tdeadmin-apps.docbook about-desktop.docbook index.docbook more-help.docbook history.docbook tdemultimedia-apps.docbook tdepim-apps.docbook tdeutils-apps.docbook shortcuts.docbook installation.docbook tdegames-apps.docbook ug-faq.docbook getting-started.docbook koffice-apps.docbook notices-trademarks.docbook tdebase-apps.docbook staff.docbook ; do \
+	  echo $(INSTALL_DATA) $$base $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/userguide/$$base ;\
+	  $(INSTALL_DATA) $(srcdir)/$$base $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/userguide/$$base ;\
+	done
+
+uninstall-nls:
+	for base in first-impressions.docbook tdeedu-apps.docbook tdenetwork-apps.docbook intro.docbook tdegraphics-apps.docbook tdetoys-apps.docbook tdeadmin-apps.docbook about-desktop.docbook index.docbook more-help.docbook history.docbook tdemultimedia-apps.docbook tdepim-apps.docbook tdeutils-apps.docbook shortcuts.docbook installation.docbook tdegames-apps.docbook ug-faq.docbook getting-started.docbook koffice-apps.docbook notices-trademarks.docbook tdebase-apps.docbook staff.docbook ; do \
+	  rm -f $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/userguide/$$base ;\
+	done
+
+
+#>+ 5
+distdir-nls:
+	for file in first-impressions.docbook tdeedu-apps.docbook tdenetwork-apps.docbook intro.docbook tdegraphics-apps.docbook tdetoys-apps.docbook tdeadmin-apps.docbook about-desktop.docbook index.docbook more-help.docbook history.docbook tdemultimedia-apps.docbook tdepim-apps.docbook tdeutils-apps.docbook shortcuts.docbook installation.docbook tdegames-apps.docbook ug-faq.docbook getting-started.docbook koffice-apps.docbook notices-trademarks.docbook tdebase-apps.docbook staff.docbook ; do \
+	  cp $(srcdir)/$$file $(distdir); \
+	done
+
+#>+ 15
+force-reedit:
+		@for dep in $?; do \
+	  case '$(am__configure_deps)' in \
+	    *$$dep*) \
+	      cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh \
+		&& exit 0; \
+	      exit 1;; \
+	  esac; \
+	done; \
+	echo ' cd $(top_srcdir) && $(AUTOMAKE) --gnu  docs/tdebase/khelpcenter/userguide/Makefile'; \
+	cd $(top_srcdir) && \
+	  $(AUTOMAKE) --gnu  docs/tdebase/khelpcenter/userguide/Makefile
+	cd $(top_srcdir) && perl ../scripts/admin/am_edit -p../scripts/admin docs/tdebase/khelpcenter/userguide/Makefile.in
+
+
+#>+ 21
+clean-bcheck: 
+	rm -f *.bchecktest.cc *.bchecktest.cc.class a.out
+
+bcheck: bcheck-recursive
+
+bcheck-am:
+	@for i in ; do \
+	    if test $(srcdir)/$$i -nt $$i.bchecktest.cc; then \
+	        echo "int main() {return 0;}" > $$i.bchecktest.cc ; \
+	        echo "#include \"$$i\"" >> $$i.bchecktest.cc ; \
+	        echo "$$i"; \
+	        if ! $(CXX) $(DEFS) -I. -I$(srcdir) -I$(top_builddir) $(INCLUDES) $(AM_CPPFLAGS) $(CPPFLAGS) $(CXXFLAGS) $(KDE_CXXFLAGS)  --dump-class-hierarchy -c $$i.bchecktest.cc; then \
+	            rm -f $$i.bchecktest.cc; exit 1; \
+	        fi ; \
+	        echo "" >> $$i.bchecktest.cc.class; \
+	        perl $(top_srcdir)/admin/bcheck.pl $$i.bchecktest.cc.class || { rm -f $$i.bchecktest.cc; exit 1; }; \
+	        rm -f a.out; \
+	    fi ; \
+	done
+
+
+#>+ 3
+final:
+	$(MAKE) all-am
+
+#>+ 3
+final-install:
+	$(MAKE) install-am
+
+#>+ 3
+no-final:
+	$(MAKE) all-am
+
+#>+ 3
+no-final-install:
+	$(MAKE) install-am
+
+#>+ 3
+kde-rpo-clean:
+	-rm -f *.rpo
+
+#>+ 3
+nmcheck: 
+nmcheck-am: nmcheck
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/about-desktop.docbook b/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/about-desktop.docbook
new file mode 100644
index 00000000000..013f11d8926
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/about-desktop.docbook
@@ -0,0 +1,581 @@
+<chapter id="all-about-your-desktop">
+<title
+>All About Your Desktop</title>
+
+<epigraph>
+<attribution
+>Little Red Riding Hood</attribution>
+<para
+>Grandma, what big eyes you have!</para>
+</epigraph>
+
+<epigraph>
+<attribution
+>The Wolf</attribution>
+<para
+>The better to see you!</para>
+</epigraph>
+
+<para
+>The more you see, the more efficiently you can use your desktop. &kde; gives you the opportunity to make the desktop look and work the way you prefer, enabling you to work faster and more productively. It even gives you the opportunity to be warned if a wolf is trying to eat you, or (if you happen to be a granny) alert you when Little Red Riding Hood is on her way to bring you the goodies. Now that's service. </para>
+
+<sect1 id="the-autostart-folder">
+<title
+>Autostarting Applications</title>
+
+<para
+>Native &kde; programs and many third party applications left open at the end of a session will save their state and reappear when you login again, but there are some programs (like some versions of &Netscape;) that will not. You can use the <filename
+>Autostart</filename
+> folder for these programs.</para>
+
+<para
+>To launch programs when &kde; is started, do the following:</para>
+
+<procedure>
+<step>
+<para
+>Open the <filename
+>Autostart</filename
+> folder. By default this folder is at <filename class="directory"
+>$<envar
+>HOME</envar
+>/.kde/Autostart</filename
+></para>
+</step>
+<step>
+<para
+>Open a &konqueror; window and browse to the program you want to add. If you do not know how to do this, it was covered in <xref linkend="the-filemanager-screen"/>.</para>
+</step>
+<step>
+<para
+>Drag and drop the desired program from the &konqueror; window on to the <filename class="directory"
+>Autostart</filename
+> folder. When asked, choose <guimenuitem
+>Link</guimenuitem
+> to create a symbolic link rather than a full copy, as this saves a great deal of disk space.</para>
+</step>
+<step>
+<para
+>Repeat the above steps for every program you want started when &kde; is launched. Remember, you do not need to add native &kde; applications, just leave them open when you log out, and they will open up again as if nothing had happened the next time you log in to &kde;.</para>
+</step>
+<step>
+<para
+>Restart &kde; if you want to see the autostart function in action.</para>
+</step>
+</procedure>
+
+<para
+>Your programs should have launched automatically when &kde; restarted.</para>
+
+<para
+>Do not forget though that you will only need the Autostart folder for a few applications. Many applications, including almost all native &kde; applications, now understand session management, and you can simply leave them open when you log out in order for them to be restarted exactly as you left them. You can leave a &konqueror; window open with your favourite website, &kmail; looking at your inbox, and &kate; with a half dozen files open, log out, log back in, and find your desktop exactly as you left it.</para>
+
+</sect1>
+
+<sect1 id="adding-programs">
+<title
+>Adding Programs and Shortcut Icons to Your &kmenu; and Panel</title>
+
+<para
+>The &kde; &kmenu; and &kicker; are not limited to the setup you find right after installing &kde;. The &kde; panel is designed to be extended, and there are two main ways of doing that: Adding new programs, and adding shortcut icons.</para>
+
+<sect2 id="menu-items-add">
+<title
+>Adding menu entries</title>
+
+<para
+>&kde; comes with a great many applications already in the menu. Depending on your operating system and distribution, this could include many non-&kde; applications. &kde; also includes an application that will search your hard drive for more applications, and add them to the menu for you. Try pressing <keycombo action="simul"
+>&Alt;<keycap
+>F2</keycap
+></keycombo
+> and entering <userinput
+>kappfinder</userinput
+> to see it in action &mdash; operation is very straightforward.</para>
+
+<para
+>&kappfinder; is clever enough, but it doesn't know about every application there is. Or perhaps you simply don't want to have all those applications in the menu, and just want to add a single extra program.</para>
+
+<para
+>To add your favourite programs to the &kde; menu, you can use the <application
+>KDE Menu Editor</application
+>. To start it, use the &kmenu; and choose <menuchoice
+><guimenuitem
+>Settings</guimenuitem
+><guimenuitem
+>Menu Editor</guimenuitem
+></menuchoice
+>.</para>
+
+<para
+>A window will open showing the existing &kmenu; on the left, and an empty menu entry dialogue on the right</para>
+
+<para
+>For this example, we will be adding an entry for the <application
+>Gimp</application
+> under the <guisubmenu
+>Graphics</guisubmenu
+> submenu. If you already have a <guimenuitem
+>Gimp</guimenuitem
+> entry there and don't want a new one, you can still follow through this example, but just don't click the <guibutton
+>Apply</guibutton
+> when you are done.</para>
+
+<procedure>
+<step
+><para
+>Navigate down the left hand tree to the <guisubmenu
+>Graphics</guisubmenu
+> entry.</para
+></step>
+<step>
+<para
+>Click on it once with the <mousebutton
+>left</mousebutton
+> mouse button to expand the entry.</para>
+</step>
+<step>
+<para
+>Click the icon labelled <guiicon
+>New Item</guiicon
+> in the toolbar, or choose <menuchoice
+><guimenu
+>File</guimenu
+><guimenuitem
+>New Item</guimenuitem
+></menuchoice
+> in the menu bar.</para>
+</step>
+<step>
+<para
+>In the dialogue box that pops up, enter the name you want your new menu entry to have. For this example, enter <userinput
+>Gimp</userinput
+>.</para
+><para
+>Then press <guibutton
+>OK</guibutton
+> in the dialogue.</para>
+</step>
+<step>
+<para
+>Click on the new <guimenuitem
+>Gimp</guimenuitem
+> menu entry that was created for you under the <guisubmenu
+>Graphics</guisubmenu
+> submenu. The menu entry dialogue to the right will now change to be mostly empty, except for the name you already gave.</para>
+</step>
+<step>
+<para
+>Fill in an optional <guilabel
+>Comment</guilabel
+>. You might like to put <userinput
+>An image editor</userinput
+> for the example. Text entered here will be shown as a tool-tip in the &kmenu;.</para>
+</step>
+<step>
+<para
+>Enter in the box labelled <guilabel
+>Command</guilabel
+>, the command you would type on the command line to open your application. For this example, this is <command
+>gimp</command
+>. You may also enter any optional command line parameters if you wish. You can use this to make a menu entry that always opens a particular document or image, for example. Check the application's documentation to find out more about command line parameters.</para>
+</step>
+<step>
+<para
+>If you want the application to operate from a particular folder (for example, for <application
+>Gimp</application
+> to begin its <guilabel
+>Load Image</guilabel
+> dialogue in a particular place) enter this path in the box labelled <guilabel
+>Work Path</guilabel
+>. This is optional.</para>
+</step>
+<step>
+<para
+>If you wish to change the icon from the default <quote
+>unknown</quote
+>, click on the <guiicon
+>icon</guiicon
+> to the right of the dialogue, to open a standard &kde; icon chooser.</para>
+</step>
+<step>
+<para
+>Some applications must be <guilabel
+>run in a terminal</guilabel
+> window (for example <application
+>Pine</application
+>). If this is the case, check the appropriate check box.</para>
+</step>
+<step>
+<para
+>If you want to run your application as a different user, check the box labelled <guilabel
+>Run as a different user</guilabel
+> and enter the appropriate user name in the text box.</para>
+</step>
+<step>
+<para
+>If you're happy with your menu entry, press <guibutton
+>Apply</guibutton
+>. If you would like to start over, press <guibutton
+>Reset</guibutton
+>.</para>
+</step>
+</procedure>
+
+<para
+>And that's all. You now have a new menu entry.</para>
+
+</sect2>
+
+<sect2 id="icons-add">
+<title
+>Shortcut Icons</title>
+
+<para
+>Although &kde; is much more comfortable than the average &UNIX; window manager, everyone wants a solution for a one-click way to start a program. Later, you will learn how to create links and files on your desktop, but this also has some disadvantages: sometimes all your desktops are filled up with windows, and you cannot reach your icons without minimising all the windows that cover them. For commonly used programs, you can minimise this problem and speed access by creating shortcut icons on the &kde; panel.</para>
+
+<para
+>To create a shortcut on the &kicker; panel, you have some choices: Drag-and-drop, or via a menu. </para>
+
+<procedure>
+<title
+>Adding a shortcut icon with the menu</title>
+<step
+><para
+>Click on the &kicon; and choose <menuchoice
+><guisubmenu
+>Panel Menu</guisubmenu
+><guisubmenu
+>Add</guisubmenu
+><guimenuitem
+>Application</guimenuitem
+> </menuchoice
+>.</para
+></step>
+<step
+><para
+>You will see the top level of the &kmenu; again. Go through the menus to find the entry for which you want to create the shortcut, such as <guimenuitem
+>Home folder</guimenuitem
+> or &konqueror;. Click on the program you want.</para>
+</step>
+</procedure>
+
+<para
+>A new icon will appear on the panel. Click on it, and the program will start.</para>
+
+<para
+>Adding a shortcut icon with drag-and-drop is even simpler - just drag any icon from your desktop, or a &konqueror; window, to an empty space on the panel.</para>
+
+<para
+>What happens when you drag an item to your panel depends on what kind of item it is:</para>
+
+<variablelist>
+<varlistentry>
+<term
+>If you drag a folder...</term
+> <listitem
+><para
+>A menu will pop up giving you a choice of <guimenuitem
+>Add as a File Manager URL</guimenuitem
+> or <guimenuitem
+>Add as a QuickBrowser</guimenuitem
+>. Choosing the first will create an icon that opens a &konqueror; window, starting at this folder, while choosing the latter will open that folder as a menu from the Panel.</para
+></listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+>If you drag a shortcut from your desktop...</term>
+<listitem
+><para
+>It will be copied to the panel.</para
+></listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+>If you drag a document...</term>
+<listitem
+><para
+>A link will be made on the panel, leaving the original in place. Clicking on the resulting icon will open that document in the default application.</para
+></listitem>
+</varlistentry>
+</variablelist>
+
+<para
+>In any case, if you want to move the icon, click on it using the &RMB; and choose <guimenuitem
+>Move <replaceable
+>Name of Button</replaceable
+></guimenuitem
+> Move the icon to the position you want and press the &LMB;. If you wish to remove the icon, click on it using the &RMB; and choose <guimenuitem
+>Remove <replaceable
+>Name of Button</replaceable
+></guimenuitem
+>.</para>
+
+</sect2>
+</sect1>
+
+<sect1 id="creating-new-files-on-your-desktop">
+<title
+>Creating New Files On Your Desktop</title>
+
+<para
+>Your desktop can be an efficient place to work. Every time you start &kde;, you can see the complete files, folders and &URL;s which you often use.</para>
+
+<para
+>There are two ways to create and edit files on your desktop. In any application, you can say that you want to save your work in the Desktop subfolder of your home folder. For example, my home folder is <filename class="directory"
+>/home/stupiddog</filename
+>, so my Desktop folder is <filename class="directory"
+>/home/stupiddog/Desktop</filename
+>. Everything you save there will be put on your desktop.</para>
+
+<para
+>If you want to move existing files to your Desktop, the best way to achieve this is to use &konqueror;. Open a file manager window and drag the files you need to your desktop. You can choose to copy them if you want to keep all your common stuff on the desktop now, or you can create symbolic links to the real files. Everything you change in the link files will be automatically updated in the originals. For more information on how to use drag &amp; drop and the file manager, see the chapter <link linkend="moving-files-with-drag-and-drop"
+>Moving files with drag &amp; drop.</link
+></para>
+
+</sect1>
+
+<sect1 id="desktop-links">
+<title
+>Placing Links on Your Desktop</title>
+
+<para
+>Placing files on your desktop may shorten the paths you need to enter. However, sometimes it would be nice if you could start &kedit; with a commonly edited file already opened in it. And how often do you find yourself frustrated after browsing through endless lists of bookmarks to find a site you visit often? Wouldn't it be nice if everything necessary to deliver you to that site was done automatically after clicking a single icon?</para>
+<!-- 
+<sect2 id="using-mimetype">
+<title
+>Using Templates</title>
+
+<para
+>Templates provide a convenient mechanism for performing tasks
+such as those outlined above.  Templates can also be used to associate
+particular file extensions with a specific application.  When a file
+ending in a known extension is double-clicked, the application
+associated with that extension is automatically started.  In short,
+<emphasis
+>templates</emphasis
+> help you get the most out of
+&kde;.</para>
+
+<para
+>Example: You want to put an icon for visiting the &kde; web site
+on your desktop.</para>
+
+<procedure>
+<step
+><para
+><mousebutton
+>Right</mousebutton
+> click on an empty space
+in the desktop.</para
+></step
+> <step
+><para
+>Choose
+<menuchoice
+><guisubmenu
+>Create
+New</guisubmenu
+><guisubmenu
+>File</guisubmenu
+><guimenuitem
+>Link to
+Location (URL)</guimenuitem
+></menuchoice
+> from the context
+menu.</para
+></step
+> <step
+><para
+>A dialog box will open where you can
+type in the address you are making a shortcut to.</para
+></step>
+<step
+><para
+>A new icon will be created on your desktop.</para
+></step>
+</procedure>
+
+<para
+>Your new Internet shortcut can be customized like any other
+shortcut icon.  <mousebutton
+>Right</mousebutton
+> click on the icon and
+choose <guimenuitem
+>Properties</guimenuitem
+>, and you can change the
+icon, or the name of the shortcut as you wish.</para>
+
+</sect2>
+-->
+
+<sect2>
+<title
+>Using &MIME; Types and File Associations</title>
+
+<para
+>&MIME; Types are very powerful. Employing them, you can easily customise your system such that clicking on a file of a specific type starts the application with which that file type has been associated. For example, all <literal role="extension"
+>.mod</literal
+> files could be set to start &noatun;, <literal role="extension"
+>.html</literal
+> files could open a &konqueror; window showing the file, and a <filename
+>core</filename
+> file can be viewed with the &khexedit; by simply clicking on the <filename
+>core</filename
+> file.</para>
+
+<warning>
+<para
+>Although &MIME; types are very powerful, they are not without dangers. Playing around with &MIME; types as the system administrator (<systemitem class="username"
+>root</systemitem
+>) can damage a &kde; system so severely that it cannot be restarted! In this example, you will create your <emphasis
+>personal</emphasis
+> &MIME; style, which is only relevant for you. It will only affect other users if you copy or move it to <filename class="directory"
+>$<envar
+>KDEDIR</envar
+>/share/mimelnk</filename
+>.</para>
+</warning>
+
+<para
+>To link a certain file type with a particular application:</para>
+
+<procedure>
+
+<step
+><para
+>Make sure the application you want to start this file type has an entry in the &kmenu;.</para
+></step>
+
+<step
+><para
+>In &konqueror; find or make a file with the extension you wish to link.</para
+></step>
+
+<step
+><para
+><mousebutton
+>Right</mousebutton
+> click on the file, and choose <guimenuitem
+>Properties</guimenuitem
+> from the context menu and then press the tiny button with an icon next to the <guilabel
+>Type</guilabel
+> resulting properties dialogue. Or, choose <menuchoice
+><guimenu
+>Edit</guimenu
+><guimenuitem
+>Edit File Type...</guimenuitem
+></menuchoice
+> in the &konqueror; menu bar.</para
+></step>
+
+<step
+><para
+>Add file masks for the application by clicking the <guibutton
+>Add</guibutton
+> button, and entering the file pattern you want. Remember that &UNIX; is case sensitive, so you may need to add variations - <userinput
+>*.mp3</userinput
+> may need <userinput
+>*.MP3</userinput
+> added as well, for example. Add as many masks as you like in this way.</para
+></step>
+
+<step
+><para
+>Add a description if you like. This is optional.</para
+></step>
+
+<step
+><para
+>In the section labelled <guilabel
+>Application Preference Order</guilabel
+>, press the <guibutton
+>Add</guibutton
+> button. A miniature copy of the &kmenu; will open, where you can choose the application you want files of this type to be opened with.</para
+></step>
+
+<step
+><para
+>Sometimes, you may want to use a different application to open this file type. For example, you might like to use &kate; to open text files you wish to edit, and &kedit; for text files that you just want to take a quick peek into. You can add more applications in the same way as you did in the last step, and you can change the preferred order using the <guibutton
+>Move Up</guibutton
+> and <guibutton
+>Move Down</guibutton
+> buttons.</para
+></step>
+
+<step
+><para
+>If you're satisfied with your choices, you can click the <guibutton
+>Apply</guibutton
+> button to save your changes without closing the dialogue box. This gives you the opportunity to test in the &konqueror; window that your file association is correct. You can choose <guibutton
+>OK</guibutton
+> to save your changes and close the dialogue box, or <guibutton
+>Cancel</guibutton
+> if you have changed your mind and just want to close the dialogue box.</para
+></step>
+</procedure>
+  
+<para
+>Be sure to try your new association by opening a folder containing a file of the type you just selected. Click on the file, and the program needed to edit it should start.</para>
+
+<note>
+<para
+>&MIME; types are a way of describing the contents of files. You may be used to using file extensions for that purpose, and you may know that on &UNIX; systems the file extension often bears little or no relation to the contents of the file. On the other hand, it may be vital - for example, some implementations of <command
+>gunzip</command
+> won't operate on files that aren't named <literal role="extension"
+>.gz</literal
+>. </para>
+
+<para
+>&MIME; types naturally make use of filename patterns, but not necessarily the extensions - you can set up any filename pattern you like. For example, if you always want to open any files relating to a particular client with &kate;, and you make a habit of naming the files with the client's name at the beginning so that they naturally group in the &konqueror; window, then you can set up a filename pattern that matches <literal
+>^<replaceable
+>clientname</replaceable
+>*</literal
+>. Then any files that have <replaceable
+>clientname</replaceable
+> at the beginning (the <literal
+>^</literal
+> character means <quote
+>starts with...</quote
+>) will be opened with the application you choose. </para>
+</note>
+</sect2>
+
+</sect1>
+
+<sect1 id="using-the-trashcan">
+<title
+>Using the Trash Can</title>
+
+<para
+>Under normal circumstances, deleting a file under &UNIX; is something which cannot be undone. However, with &kde;, you can choose <guimenuitem
+>Move to Trash</guimenuitem
+> instead of <guimenuitem
+>Delete</guimenuitem
+>. This will move the file into the <filename class="directory"
+>Trash</filename
+> Folder, which, by default, is accessible as an icon on your desktop. In the <filename class="directory"
+>Trash</filename
+> Folder, you can always recover deleted files. Remember to empty the trashcan now and then by clicking on it using the right mouse button, then choosing <guimenuitem
+>Empty trashcan</guimenuitem
+>, otherwise you might run out of disk space because the files still need space. Note, however, that once you empty the <filename
+>Trash</filename
+> Folder, the files contained therein are lost forever.</para>
+
+</sect1>
+</chapter>
+<!--
+Local Variables:
+mode: sgml
+sgml-omittag:nil
+sgml-shorttag:t
+sgml-namecase-general:t
+sgml-general-insert-case:lower
+sgml-minimize-attributes:nil
+sgml-always-quote-attributes:t
+sgml-indent-step:0
+sgml-indent-data:nil
+sgml-parent-document:("index.docbook" "book" "chapter")
+End:
+-->
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/first-impressions.docbook b/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/first-impressions.docbook
new file mode 100644
index 00000000000..1328a2e0170
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/first-impressions.docbook
@@ -0,0 +1,470 @@
+<chapter id="first-impressions">
+<title
+>First Impressions </title>
+
+<epigraph>
+<attribution
+>Origin unknown</attribution>
+<para
+>You see to sea to see all that you can see is sea</para>
+</epigraph>
+
+<para
+>First impressions are so important -- this is not only true for Agatha Christie's famous thriller <quote
+>The Mousetrap</quote
+> -- but also for &kde;. As we mentioned before, &kde; is supposed to be the most intuitive, easy to learn user interface available. In fact, we will have reached our goal when users no longer need this book in order to work with &kde;, causing the authors to lose their (unpaid and voluntary) jobs as documenters. </para>
+
+<sect1 id="starting-kde">
+<title
+>Starting &kde; </title>
+
+<para
+>When you boot a &UNIX; system, one of three things should happen (that is, if the system works correctly; everything else is an undocumented fourth case). Either you stay in text mode and get a login prompt, you are logged into your &GUI; of choice automatically, or you are presented with a graphical login window. In the first case, you must log into your system and type: </para>
+
+<screen
+><command
+>startx</command
+>  
+</screen>
+
+<para
+>If the installation was successful, the &kde; desktop should appear after a few seconds of initialisation. </para>
+
+<para
+>If a graphical login window is presented, then all that should be required is your login name and password. Assuming the &kde; installation was successful, &kde; should start without further intervention. </para>
+
+<para
+>If you have not done so already, we recommend changing your X display manager from <application
+>xdm</application
+> to &kdm;, which includes the same functionality, but with the advanced features of the K Desktop Environment. </para>
+
+<para
+>If your system is configured to automatically log you into a &GUI; you will need to consult your operating system manuals or support forums for instructions how to have &kde; be that &GUI;.</para>
+
+</sect1>
+
+<sect1 id="desktop-components">
+<title
+>Desktop Components </title>
+
+<para
+>After everything has come up, take some time to explore the new environment. If you have already worked with <emphasis
+>&Windows;</emphasis
+>, <emphasis
+>OS/2</emphasis
+> or <emphasis
+>&MacOS;</emphasis
+>, many things should look familiar to you. The main visible parts of &kde; that you will see are the desktop itself, and the panel.</para>
+
+
+<sect2 id="kde-logout">
+<title
+>Panel </title>
+
+<para
+>When you start &kde; for the first time, the panel is situated at the bottom of the screen. From here, you will start your programs and switch between the virtual screens. </para>
+
+<variablelist>
+<varlistentry>
+<term
+>&kicon; button</term>
+<listitem
+><para
+>The &kicon; button is one of the most important places on your &kde; desktop. From here, you can start all &kde; applications installed. Later, when you learn how to use <link linkend="adding-programs"
+>the K Menu Editor</link
+>, you can also add other programs here as well. To start a program, just click on the button. You will see a list of different categories, plus some special entries. Whenever you move your mouse over an entry that has an arrow to the right, a new menu will appear. When you find the program you want to start, just click on it with the <mousebutton
+>left</mousebutton
+> mouse button.</para
+></listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+>Virtual Desktop buttons</term>
+<listitem
+><para
+>When you start &kde; for the first time, note the four buttons labelled, appropriately enough, <guilabel
+>1</guilabel
+>, <guilabel
+>2</guilabel
+>, <guilabel
+>3</guilabel
+> and <guilabel
+>4</guilabel
+>. These represent your four <emphasis
+>desktops</emphasis
+>. Just click one of them. Don't worry; though they have <quote
+>disappeared</quote
+>, any open windows are still active (just take a look at the task list!). Using multiple desktops is one of the most powerful features of &kde; and the &X-Window;. Instead of placing one window over another, as you would when using &Windows; or OS/2, you can say <quote
+>Well, on the first desktop, I will write the &kde; User Guide. On the second desktop I'll run the <command
+>meinproc</command
+> documentation compiler and see my results while compiling my &Linux; kernel on the third desktop, and reading my email on the fourth.</quote
+> </para
+></listitem>
+</varlistentry>
+<varlistentry>
+<term
+>Icon bar</term>
+<listitem>
+<para
+>Some people are so lazy that they consider even the two or three motions through the application's menu to be too much (me included). For them, additional buttons can be placed next to the desktop buttons; for example, shortcuts to your home folder, to your trashcan, to the <application
+>Konsole</application
+> terminal emulator and to the documents you use often. For information on how to add icons to the taskbar, read <link linkend="icons-add"
+>Adding icons to your taskbar</link
+>. </para>
+<para
+>&kde; by default installs several commonly used buttons, including links to &khelpcenter;, &kwrite; and &kcontrol;.</para
+></listitem>
+</varlistentry>
+<varlistentry>
+<term
+>Time and date</term>
+<listitem
+><para
+>At the far right end of the &kde; panel, you can always see the time and date.</para
+></listitem>
+</varlistentry>
+<varlistentry>
+<term
+>The task list</term>
+<listitem>
+<para
+>In another section of the panel, find a button for each open window. Just click on the button corresponding to the windows you want to open. Another click will minimise the window. A <mousebutton
+>right</mousebutton
+> mouse button click will give you a menu allowing you to move the window to another desktop, manipulate it's size, or close the application.</para
+></listitem>
+</varlistentry>
+</variablelist>
+
+</sect2>
+<sect2>
+<title
+>Using Windows </title>
+
+<variablelist>
+<varlistentry>
+<term
+>Window menu</term>
+<listitem>
+<para
+><mousebutton
+>Right</mousebutton
+> mouse button clicking in the title bar of the window (where you see the application's name), you can see a window manipulation icon. This is the same menu you see if you <mousebutton
+>right</mousebutton
+> click on an application's icon in the panel taskbar. When you click on it, a context menu containing commands to manipulate the window is presented. The available commands are as follows:</para>
+
+<variablelist>
+<varlistentry>
+<term
+><guimenuitem
+>Move</guimenuitem
+></term>
+<listitem
+><para
+>Lets you move the window with your mouse. Click on the <mousebutton
+>left</mousebutton
+> mouse button when you have the window where you want it to be.</para
+></listitem>
+</varlistentry>
+<varlistentry>
+<term
+><guimenuitem
+>Resize</guimenuitem
+></term>
+<listitem
+><para
+>Enables you to make the window smaller or larger. Move your mouse around and click when you are satisfied with the new size.</para
+></listitem>
+</varlistentry>
+<varlistentry>
+<term
+><guimenuitem
+>Minimise</guimenuitem
+></term>
+<listitem
+><para
+>Hides the window, leaving only an icon in the taskbar. Notice that the window title in this icon is now shown in (parentheses). To bring the window to the desktop again, click the icon.</para
+></listitem>
+</varlistentry>
+<varlistentry>
+<term
+><guimenuitem
+>Maximise</guimenuitem
+></term>
+<listitem
+><para
+>This will expand the window to the largest size possible. Note that &kde; will take the size of your <emphasis
+>virtual desktop</emphasis
+>, which means that the window could be bigger than your screen. </para
+></listitem>
+</varlistentry>
+<varlistentry>
+<term
+><guimenuitem
+>Shade</guimenuitem
+></term>
+<listitem
+><para
+><quote
+>Roll</quote
+> up the window, leaving only the titlebar visible. You can achieve the same effect by double clicking in the titlebar. To display the entire window again, select <guimenuitem
+>Shade</guimenuitem
+> again, or double click in the titlebar.</para
+></listitem>
+</varlistentry>
+<varlistentry>
+<term
+><guisubmenu
+>Advanced</guisubmenu
+></term>
+<listitem
+><para
+>Here you can find menu options that allow you to manipulate how windows may cover each other up, and more:</para>
+
+<variablelist>
+<varlistentry>
+<term
+><guimenuitem
+>Keep Above Others</guimenuitem
+></term>
+<listitem
+><para
+>Selecting this will keep this window on top of all other applications, even when it does not have the focus.</para
+></listitem>
+</varlistentry>
+<varlistentry>
+<term
+><guimenuitem
+>Keep Below Others</guimenuitem
+></term>
+<listitem
+><para
+>Selecting this will keep this window below all others, even when it does have the focus.</para
+></listitem>
+</varlistentry>
+<varlistentry>
+<term
+><guimenuitem
+>Fullscreen</guimenuitem
+></term>
+<listitem
+><para
+>Selecting this makes the window take up the entire screen, similar to maximising, however, there are no window decorations showing. To switch to other applications, you may need to use the keybindings. For instance <keycombo action="simul"
+>&Alt;&Tab;</keycombo
+> to switch to another window or <keycombo action="simul"
+>&Ctrl;&Tab;</keycombo
+> to switch to another virtual desktop.</para>
+<para
+>To revert from fullscreen mode, you can use the <keycombo action="simul"
+>&Alt;<keycap
+>F3</keycap
+></keycombo
+> shortcut to show the window operations menu and deselect <menuchoice
+><guisubmenu
+>Advanced</guisubmenu
+><guimenuitem
+>Fullscreen</guimenuitem
+> </menuchoice
+>.</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term
+><guimenuitem
+>No Border</guimenuitem
+></term>
+<listitem>
+<para
+>Remove the window decoration and border from this window. This is useful for <quote
+>monitor</quote
+> type applications, such as &kpager; which you keep on screen all the time and will never need the window decorations for. Many people also like to use this for <application
+>xterm</application
+> and &konsole; windows.</para>
+<para
+>To revert from no border mode, you can use the <keycombo action="simul"
+>&Alt;<keycap
+>F3</keycap
+></keycombo
+> shortcut to show the window operations menu and deselect <menuchoice
+><guisubmenu
+>Advanced</guisubmenu
+><guimenuitem
+>No Border</guimenuitem
+> </menuchoice
+>.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+><guimenuitem
+>Store Window Settings</guimenuitem
+></term>
+<listitem
+><para
+>Stored the current settings for this window (position, size, whether it should always stay on top of all other windows &etc;.). This configuration will then be loaded the next time the window gets opened.</para>
+</listitem>
+</varlistentry>
+</variablelist>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term
+><guimenuitem
+>To Desktop</guimenuitem
+></term>
+<listitem
+><para
+>Enables you to send a window to another desktop. Choose the desktop where you want the window to be. The window will disappear at once. To see your window again, select the appropriate <guiicon
+>Desktop Button</guiicon
+> on the &kde; <application
+>Panel</application
+>. Selecting <guimenuitem
+>All Desktops</guimenuitem
+> will make the window <quote
+>sticky</quote
+> - it will display on all desktops at once, so you can alway see this window.</para
+></listitem>
+</varlistentry>
+<varlistentry>
+<term
+><guimenuitem
+>Configure Window Behaviour...</guimenuitem
+></term>
+<listitem
+><para
+>Allows you to change the look and feel, of all the windows in &kde;. This changes the window decoration widgets, including the titlebar buttons, but also including things such as checkboxes and buttons within dialogues, scrollbars, and the titlebar itself. The default is <guilabel
+>Keramik</guilabel
+>.</para>
+<para
+>You can further customise nearly everything about the window manager itself, including how windows behave when moved, what different mouse button clicks will do in different parts of the window, and how to decide which windows have focus.</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term
+><guimenuitem
+>Close</guimenuitem
+></term>
+<listitem
+><para
+>This will close the window. Sometimes the application will allow you to save your work, but in some cases (&eg;, old X11 applications) this does not work. It is best to close an application with its own commands, using this menu item only as a last resort.</para>
+<para
+>If the application itself is experiencing a problem that doesn't allow you to close it normally, using this menu item, or the window decoration close button will offer you the chance to <quote
+>kill</quote
+> it as gracefully as possible. Note that this may still leave the application open in the background but not showing any windows. Allowing the application to be killed in this manner will most likely allow you back into the desktop however, so you can check in a terminal window and clean up any remaining processes.</para>
+</listitem>
+</varlistentry>
+</variablelist>
+</listitem>
+</varlistentry>
+</variablelist>
+
+<variablelist>
+<title
+>Window Decoration Buttons</title>
+<varlistentry>
+<term
+>Sticky button</term>
+<listitem
+><para
+>This button looks like a plus symbol in the default window decoration (Keramik) and may look like a thumb tack in others. It performs the same operation as selecting <menuchoice
+><guimenu
+>To Desktop</guimenu
+><guimenuitem
+>All Desktops</guimenuitem
+> </menuchoice
+> in the <guimenu
+>Window Menu</guimenu
+>, but requires fewer steps to invoke.</para
+></listitem>
+</varlistentry>
+<varlistentry>
+<term
+>Title bar</term>
+<listitem
+><para
+>The title bar containing the name of the window can be double-clicked in order to shade it. Use the <mousebutton
+>right</mousebutton
+> mouse button: The <guimenu
+>Window menu</guimenu
+> will reappear, allowing you to (un)maximise, iconify, move, resize, (un)sticky the window, to move it to another desktop (this works faster than the method with the sticky button). When a program does not react anymore, you can close (which will sometimes give you the opportunity to save your work) it. </para
+></listitem>
+</varlistentry>
+<varlistentry>
+<term
+><guibutton
+>Minimise</guibutton
+>, <guibutton
+>Maximise</guibutton
+> and <guibutton
+>Close</guibutton
+> Buttons</term>
+<listitem
+><para
+>To the right of the title bar, there are two buttons that can also be used to iconify or maximise the window (this is faster than using the window manipulation menu). Iconified windows can be brought back with a click on the taskbar. </para>
+<para
+>At the far left of the titlebar (with the default window decoration) is a button to close the window.</para
+></listitem>
+</varlistentry>
+</variablelist>
+
+<para
+>To move a window, place the cursor on the title bar and hold down the &LMB;. Without releasing the mouse button, move the window to the location of your choice, then release the mouse button. If you want to resize a window, move the mouse cursor to the window border you wish to change. Once you have reached the correct spot, the cursor will change from an arrow to a bracket and an arrow. Hold down the &LMB; and drag the side in question to the location you wish, then release the button. Note that you may drag sides or corners (which will adjust the size in two dimensions at once.)</para>
+
+<para
+>Using the menu bar of each &kde; window is easy. Just click on what you want to do, and it will be done.</para>
+
+<para
+>Below the menu bar, there is a set of tool symbols you can use to execute commands. Whenever you move over them, an active picture will be marked. But the menu bar can do even more for you. Notice the textured stripe on the left of the menu and icon bars? Depress your <mousebutton
+>right</mousebutton
+> mouse button and a context menu will appear, allowing you to put the menu bar on the <guimenuitem
+>top</guimenuitem
+>, <guimenuitem
+>left</guimenuitem
+>, <guimenuitem
+>right</guimenuitem
+>, or <guimenuitem
+>bottom</guimenuitem
+> of the window. You can also hide the menubar by selecting <guimenuitem
+>Flat</guimenuitem
+></para>
+
+</sect2>
+
+<sect2>
+<title
+>Getting Help </title>
+
+<para
+>Help is available basically everywhere: On the desktop, just use the <mousebutton
+>right</mousebutton
+> mouse button and choose <menuchoice
+><guisubmenu
+>Help</guisubmenu
+><guimenuitem
+>KDesktop Handbook</guimenuitem
+></menuchoice
+>. On the &kde; panel, open the application menu and choose <guimenu
+>Help</guimenu
+>. Every &kde; program has a help menu.</para>
+
+</sect2>
+</sect1>
+</chapter>
+<!--
+Local Variables:
+mode: sgml
+sgml-omittag:nil
+sgml-shorttag:t
+sgml-namecase-general:t
+sgml-general-insert-case:lower
+sgml-minimize-attributes:nil
+sgml-always-quote-attributes:t
+sgml-indent-step:0
+sgml-indent-data:nil
+sgml-parent-document:("index.docbook" "book" "chapter")
+sgml-exposed-tags:nil
+sgml-local-catalogs:nil	
+sgml-local-ecat-files:nil
+End:
+-->
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/getting-started.docbook b/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/getting-started.docbook
new file mode 100644
index 00000000000..65641835014
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/getting-started.docbook
@@ -0,0 +1,581 @@
+<chapter id="getting-started">
+<title
+>Getting Started </title>
+
+<epigraph>
+<attribution
+>Help for one of the toughest riddles in <quote
+>The 7th Guest</quote
+></attribution>
+<para
+>Using only what you see, can you get from A to B?</para>
+</epigraph>
+
+<para
+>So far, you may be thinking that &kde; is little more than another window manager. Relax, and read this chapter, and we'll introduce you to some features that will assure you that &kde; is very much more than a window manager &mdash; it's a full fledged environment.</para>
+
+<sect1 id="editing-files">
+<title
+>Editing Files </title>
+
+<para
+>Since you do not only have &kde; applications installed on your system, you probably know the mess of editing <abbrev
+>ASCII</abbrev
+> style configuration files. But in fact, there are a lot of other file types that need to be edited this way. For example, the raw &XML; source for this guide was written <abbrev
+>ASCII</abbrev
+> style, as was the source code for the &kde; programs themselves. We will now show you how you can use the &kwrite; facility in &kde; to edit <abbrev
+>ASCII</abbrev
+> files of your own. </para>
+
+<sect2 id="the-filemanager-screen">
+<title
+>Opening a Window Containing Your Home Folder </title>
+
+<para
+>Click on the &kicon; button and choose <guimenuitem
+>Home (Personal Files)</guimenuitem
+>. A window showing the contents of your home folder will pop up. To see a more detailed listing of files in your home folder, select <guimenuitem
+>Show Hidden Files</guimenuitem
+> from the <guimenu
+>View</guimenu
+> menu.</para>
+
+<para
+>On the left hand of the window, a tree view of your file system structure should appear, while on the right hand side, you can see icons for each file in your Home folder, including any <quote
+>hidden files</quote
+> &mdash; files or folders beginning with a period. </para>
+
+</sect2>
+
+<sect2>
+<title
+>The File Manager Screen </title>
+
+<para
+>We tried to make the File Manager as easy as possible to use, and if you know other window managers (including those built into other Operating Systems) with integrated file management, many of the following concepts should be familiar to you.</para>
+
+<para
+>On the top, there is a <guimenu
+>Location</guimenu
+> menu which contains functions to open and close file manager windows. You can also print the current contents.</para>
+
+<note
+><para
+>Want to visit the Internet? There are several paths you can take. You could choose <menuchoice
+><guimenu
+>Location</guimenu
+><guimenuitem
+>Open Location</guimenuitem
+></menuchoice
+> (or press <keycombo
+>&Ctrl;<keycap
+>O</keycap
+></keycombo
+>) and enter a &URL;.</para>
+
+<para
+>The simplest way however, is to simply type in the address you want to go to in the location bar itself.</para>
+
+<para
+>For example, if you want to visit the &kde; homepage, enter <userinput
+>http://www.kde.org</userinput
+>. You can also quickly transfer files over &FTP; using this method. &kde; is <quote
+>Internet ready</quote
+>, which means that you can load and save files not only on your local hard disk, but also on remote &FTP; and other remote servers that you have write access to. While other operating systems and desktops make a distinction between local and remote file systems, &kde; does not.</para>
+</note>
+
+<para
+>The <guimenu
+>Edit</guimenu
+> menu offers functions to select, copy and move files. We will use them later. Already having used the <guimenu
+>View</guimenu
+> menu, you have probably seen that you can view the content in many different ways. Just play around a bit and see what happens.</para>
+
+<para
+>You will undoubtedly find the <guimenu
+>Bookmarks</guimenu
+> to be extremely useful: Now you can remember virtually any link, be it on the local machine or somewhere on the Internet. &kde;'s network transparency works both ways, allowing you to treat files and folders on your hard drive as if they were Internet bookmarks.</para>
+
+<para
+>The <guimenu
+>Tools</guimenu
+> menu helps you find the notorious file-that-I-put-somewhere-I-do-not-remember-anymore.</para>
+
+</sect2>
+
+<sect2>
+<title
+>Navigating Through Folders </title>
+
+<para
+>We will now pick one of your configuration files and edit it. First, we must change the folder in the File Manager.</para>
+
+<para
+>&konqueror; started with your home folder as the top of the <quote
+>tree</quote
+>. For most day-to-day purposes, this is where you are likely to be working, so it is a practical default. Sometimes you need to see the broader picture though, so the rest of your file system is not far away.</para>
+
+<para
+>You can quickly display the <filename class="directory"
+>/</filename
+> or <quote
+>root</quote
+> folder several ways: click the small <guiicon
+>folder</guiicon
+> icon beside the navigation pane to switch to a full filesystem tree, use the <guiicon
+>Up</guiicon
+> arrow on the toolbar above to go to the top of your filesystem in the right hand pane, or type in <userinput
+>/</userinput
+> in the location bar.</para>
+
+<para
+>For the purpose of following this guide, press the small blue folder icon beside the navigation pane, so that the navigation pane switches to a full filesystem view. Notice that part of the tree is expanded, and your home folder is still selected. Now you can see how your home folder fits into the whole hierarchy, and your home folder files are still visible in the right hand pane.</para>
+
+<para
+>Scroll down the navigation pane on the left side of the window until you find the folder <filename
+>/etc</filename
+>. Double-click on <filename
+>etc</filename
+>. You will see a long list of files in the right window.</para>
+
+</sect2>
+
+<sect2 id="opening-a-file">
+<title
+>Opening A File </title>
+
+<para
+>Some of the files you see here are at the heart of your operating system, so making permanent changes to them require you to be the <systemitem class="username"
+>root</systemitem
+> or superuser. We are going to practice on a file that will not hurt anything if a mistake is made, called <filename
+>motd</filename
+>.</para>
+
+<para
+>Scroll down until you find the file <filename
+>motd</filename
+> and click on it with the <mousebutton
+>right</mousebutton
+> mouse button. In the <guimenu
+>context menu</guimenu
+>, select <guimenuitem
+>Open With</guimenuitem
+>. A new menu will pop up. Choose <guimenuitem
+>&kwrite;</guimenuitem
+>. Voila!</para>
+
+<para
+>There are many ways to open a file, and this is just one of them. &kwrite; is an editor with a simple and probably familiar interface. You could also have navigated down the small tree in the popup dialogue to the <guilabel
+>Editors</guilabel
+> section, and chosen another editor, or simply double click the file to open it in the default editor.</para>
+
+<para
+>In the meantime, you have the file <filename
+>/etc/motd</filename
+> open in &kwrite; and we're ready to do some editing.</para>
+
+</sect2>
+
+<sect2>
+<title
+>The Editor Screen </title>
+
+<para
+>The more you work with &kde;, the more you will notice that most screens and applications look and feel the same. The &kwrite; <guimenu
+>File</guimenu
+> menu is a great example of this. Almost every other &kde; program has the same menu, allowing you to create new files, open existing files from your local file system or (coming soon) even the web, save them (soon even on the web, too!), print it or mail it to somebody else.</para>
+
+<para
+>The <guimenu
+>Edit</guimenu
+> menu can also be found in most &kde; applications, allowing you to cut and paste information between programs. You can also search and replace text. Using the <guimenu
+>Settings</guimenu
+> Menu, you can customise the editor in many different ways. For example, you can increase the font size to suit your monitor resolution &mdash; and your eyes. Of course, as in any other &kde; application, you find a <guimenu
+>Help</guimenu
+> Menu, offering you on-line help whenever you need it. </para>
+
+</sect2>
+
+<sect2>
+<title
+>Using the Editor </title>
+
+<para
+>Most <filename
+>motd</filename
+> files contain useless stuff like <quote
+>Do not forget to back up your data</quote
+> or <quote
+>Do not annoy the system manager</quote
+>. Boring. Let's change the text so that users logging in get the really important information. You can navigate through the text using the arrow keys, and mark sections of text with <keycombo
+>&Shift;<keycap
+>Arrows</keycap
+> </keycombo
+>or by using the mouse with the <mousebutton
+>left</mousebutton
+> button pressed. Use the <guimenu
+>Edit</guimenu
+> Menu to cut and paste text. Enter whatever you want, or use the following (great) example: </para>
+
+<screen
+><userinput
+>Welcome!
+ 
+This machine now has KDE installed, providing you with a great, 
+easy-to-use interface and a consistent Look-and-Feel for all your 
+applications. For more information on how to get KDE running on your 
+account, please email the administrator. </userinput
+></screen>
+
+</sect2>
+
+<sect2 id="saving-files">
+<title
+>Saving Your Work </title>
+
+<para
+>Now that you have changed the <filename
+>motd</filename
+> file, it is time to save the file, putting the changes into effect. To do this, you can use either the <guimenu
+>File</guimenu
+> Menu, or you can use the <guiicon
+>Save</guiicon
+> Icon on the toolbar.</para>
+
+<para
+>At this point, reality hits us. You need to have <systemitem class="username"
+>root</systemitem
+> permission to save the changes to this file. &kde; handles this by asking you for the <systemitem class="username"
+>root</systemitem
+> password.</para>
+
+<para
+>You probably don't really want to save this file, so you can press <guibutton
+>Cancel</guibutton
+> in the password dialogue and <guibutton
+>Cancel</guibutton
+> again in the save dialogue.</para>
+
+<para
+>Finally, finish your work by closing the editor and file manager window. You can do this by clicking the <guibutton
+>X</guibutton
+> button on the top left of the window, by using the window menu of the title bar, or by choosing <menuchoice
+><guimenu
+>File</guimenu
+> <guimenuitem
+>Quit</guimenuitem
+></menuchoice
+>. Simple and elegant, isn't it? </para>
+
+</sect2>
+
+<sect2 id="creating-new-files">
+<title
+>Creating New Files</title>
+
+<para
+>As with everything in &kde;, there are several ways to create a new file. You could open up the file manager, <mousebutton
+>right</mousebutton
+> click on an empty space in a folder you own, and choose <menuchoice
+><guisubmenu
+>Create New</guisubmenu
+><guisubmenu
+>File</guisubmenu
+><guimenuitem
+>Text File...</guimenuitem
+></menuchoice
+>. A new empty file will appear, which you can open just like any other. You can even do this right on the desktop itself.</para>
+
+<para
+>More often you are already in an application and want to start a new file. Most &kde; applications offer a <menuchoice
+><guimenu
+>File</guimenu
+><guimenuitem
+>New</guimenuitem
+></menuchoice
+> menu item, and an icon on the toolbar to complement it. A new empty document will appear that you can immediately begin working in.</para>
+
+<para
+>Both these approaches have advantages, so use the one that is most practical at the time.</para>
+
+</sect2>
+
+</sect1>
+
+<sect1 id="moving-files-with-drag-and-drop">
+<title
+>Moving Files With Drag and Drop </title>
+
+<para
+>As you have seen in the previous section, working with files is as easy as 1-2-3. However, when you want to copy and move files, the whole copy-and-paste business can get annoying. Don't worry &mdash; a procedure called <quote
+>drag and drop</quote
+> allows you to copy and move files more quickly and easily. </para>
+
+<sect2>
+<title
+>Opening Two File Manager Windows </title>
+
+<para
+>Before you can start, you will need to open two file manager windows. The simplest way to open a new window is to press the gear wheel button on the right of the icon bar. If you do not see the tree view in the new window, activate it (<menuchoice
+><guimenu
+>Window</guimenu
+><guimenuitem
+>Navigation Panel</guimenuitem
+> </menuchoice
+> or press <keycap
+>F9</keycap
+>).</para>
+
+</sect2>
+
+<sect2>
+<title
+>Dragging a File From One Window To Another </title>
+
+<para
+>In the first window, open the <filename
+>/etc</filename
+> folder and scroll until you see the <filename
+>motd</filename
+> file we modified in the previous section.</para>
+
+<para
+>In the second window, open your home folder.</para>
+
+<para
+>Click on the <filename
+>motd</filename
+> file. Hold your <mousebutton
+>left</mousebutton
+> mouse button and drag your file into your home folder. Release the <mousebutton
+>left</mousebutton
+> mouse button (this is called <emphasis
+>dropping</emphasis
+> the file). You will be presented up to four options: <guimenuitem
+>Copy Here</guimenuitem
+>, <guimenuitem
+>Move Here</guimenuitem
+>, <guimenuitem
+>Link Here</guimenuitem
+> and <guimenuitem
+>Cancel</guimenuitem
+>. In this example, since you are not <systemitem class="username"
+>root</systemitem
+>, you cannot move the file, so this option is not presented. <guimenuitem
+>Link Here</guimenuitem
+> will create a symbolic link to the file, while <guimenuitem
+>Copy Here</guimenuitem
+> and <guimenuitem
+>Move Here</guimenuitem
+> do exactly what they say. Select <guimenuitem
+>Copy Here</guimenuitem
+>. You should now have a copy of the <filename
+>motd</filename
+> file in your home folder. </para>
+
+</sect2>
+</sect1>
+
+<sect1 id="using-command-line-and-terminals">
+<title
+>Using Command Line And Terminals </title>
+
+<para
+>So far, you have only worked with the tools and programs &kde; provides. Undoubtedly, you will want to use other &UNIX; programs as well. There are two ways of running them: The quick command line and the terminal.</para>
+
+<sect2>
+<title
+>Quick Command Line </title>
+
+<para
+>Pressing <keycombo action="simul"
+>&Alt; <keycap
+>F2</keycap
+></keycombo
+> pops up a small window where you can enter a command to run. Please note that you will not see any text output generated from a program started in this manner! This method is only recommended for starting &X-Window; based programs or for running tools where you do not need to see or type anything. For other programs, you will still need to use the terminal.</para>
+
+</sect2>
+
+<sect2>
+<title
+>The &UNIX; Terminal Emulator </title>
+
+<para
+>From the application menu, choose <menuchoice
+><guisubmenu
+>System</guisubmenu
+><guimenuitem
+>Terminal</guimenuitem
+> </menuchoice
+>. A terminal window will open. Here you can use regular &UNIX; shell commands: <command
+>ls</command
+>, <command
+>cat</command
+>, <command
+>less</command
+>, and so forth. Using the <guimenu
+>Settings</guimenu
+> menu, you can customise the terminal emulator to suit your needs. </para>
+
+</sect2>
+</sect1>
+
+<sect1 id="finding-your-lost-files">
+<title
+>Finding Your Lost Files </title>
+
+<para
+>Everyone has undoubtedly encountered the following problem: You start <command
+>ftp</command
+>, log into a great site like ftp.kde.org and start downloading files. It is late in the evening and you shut down your machine after completing the transfer. The next morning, you are at the keyboard again, and you start wondering into which folder you placed the recently transferred files. Using &kde;'s &kfind; utility makes finding those lost files a snap.</para>
+
+<sect2>
+<title
+>Starting &kfind;</title>
+
+<para
+>Starting &kfind; is simple: Choose <guimenuitem
+>Find Files</guimenuitem
+> in the &kmenu;. &kfind; uses an interface part you probably have not yet met in &kde;: tabs. When &kfind; starts, you see that <guilabel
+>Name/Location</guilabel
+> is selected. When you click on <guilabel
+>Date Range</guilabel
+>, the tab content changes. Since you have never run a search before, most of the icons on the toolbar and most of the menu entries are disabled. We will change this now.</para>
+
+</sect2>
+
+<sect2>
+<title
+>Finding a File by Knowing Parts of Its Name </title>
+
+<para
+>As long as you know a bit of the file name, searching is easy. Select the <guilabel
+>Name/Location</guilabel
+> tab, and enter the file name in the <guilabel
+>Named</guilabel
+> field. Wildcards may be used as needed. As a test, type <userinput
+>*.tar.gz</userinput
+>. By default, the search begins in your home folder, but you can select any starting folder you wish by clicking on the <guilabel
+>Look in</guilabel
+> or <guibutton
+>Browse...</guibutton
+>. To start searching, press the <guibutton
+>Find</guibutton
+> button. After a moment, a list of files will appear in the search results window. If they do not appear, you started the search in the wrong folder, made a spelling mistake in the <guilabel
+>Named</guilabel
+> field, or no files ending with a <filename
+>.tar.gz</filename
+> extension are located on your machine.</para>
+
+</sect2>
+
+<sect2 id="finding-with-complex-criteria">
+<title
+>Finding a File by More Complex Criteria </title>
+
+<para
+>There are many categories you can use to make your search more precise. <emphasis
+>The more you know about the file, the better are your chances of finding it</emphasis
+>.</para>
+
+<variablelist>
+<varlistentry>
+<term
+><guilabel
+>Date Range</guilabel
+></term>
+<listitem>
+<para
+>Here, you can specify that you only want to see files which were last touched in a given period of time. You can also specify that you only want to see files that were touched since a specified number of months or days ago.</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term
+><guilabel
+>File Type</guilabel
+> in the <guilabel
+>Contents</guilabel
+> tab.</term>
+<listitem
+><para
+>If you know that the file was of a special type (&eg;, a tar/gzip archive or a jpeg picture), you can tell &kfind; to find only this type of file.</para
+></listitem>
+</varlistentry>
+<varlistentry>
+<term
+><guilabel
+>Containing text</guilabel
+> in the <guilabel
+>Advanced</guilabel
+> tab</term>
+<listitem>
+<para
+>You can specify text that the file must contain. </para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term
+><guilabel
+>File size is</guilabel
+>, in the <guilabel
+>Properties</guilabel
+> tab</term>
+<listitem
+><para
+>If you know the file size, you can limit your search in this regard, as well. </para
+></listitem>
+</varlistentry>
+</variablelist>
+
+<para
+>&kfind; has many more options to refine searches, explore them all!</para>
+
+</sect2>
+</sect1>
+
+<sect1 id="using-multiple-desktops">
+<title
+>Using Multiple Desktops </title>
+
+<para
+>Using multiple desktops helps you organise your work. You can place your programs on different desktops, and name the desktops so you know what you do there. This increases and optimises your workspace. It also helps you when you are surfing the net instead of doing your work and your boss comes in. But, of course, this is rare &mdash; at least in the office where I work. </para>
+
+<para
+>You can switch between desktops by clicking the desktop buttons on the &kicker; panel. If you want to rename them, you can do so by double-clicking on them. </para>
+
+<para
+>You can use windows on multiple desktops. If you want to have a window present everywhere, just click the sticky button on the top-left of the window. To send a window to another desktop, click on the title bar with the <mousebutton
+>right</mousebutton
+> mouse button, choose <guimenuitem
+>To Desktop</guimenuitem
+>, and select the desktop where you would like the window moved. </para>
+
+</sect1>
+
+<sect1 id="quitting-kde">
+<title
+>Quitting &kde;</title>
+
+<para
+>To quit working with &kde;, you can use the <guimenuitem
+>Logout</guimenuitem
+> entry in the &kmenu;. You will be asked if you really want to quit &kde;. Quitting will close all windows and return you to your console or display manager. For information on how programs can save your work during logout, please read <link linkend="kde-logout"
+>the notes for logging out.</link
+> </para>
+
+</sect1>
+</chapter>
+<!--
+Local Variables:
+mode: sgml
+sgml-omittag:nil
+sgml-shorttag:t
+sgml-namecase-general:t
+sgml-general-insert-case:lower
+sgml-minimize-attributes:nil
+sgml-always-quote-attributes:t
+sgml-indent-step:0
+sgml-indent-data:nil
+sgml-parent-document:("index.docbook" "book" "chapter")
+End:
+-->
\ No newline at end of file
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/history.docbook b/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/history.docbook
new file mode 100644
index 00000000000..6b5bff13bf4
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/history.docbook
@@ -0,0 +1,186 @@
+<chapter id="history">
+<title
+>A Short Guided Tour of &kde;'s History</title>
+
+<epigraph>
+<attribution
+>The <abbrev
+>CEO</abbrev
+> of a big software company, at the beginning of the 80s...(apocryphal)</attribution
+> 
+<para
+>640KB ought to be enough for everybody </para>
+</epigraph>
+
+<sect1 id="before-kde">
+<title
+>Before &kde;</title>
+
+<para
+>Since the beginning of &UNIX; development, there has been one great problem: There were stable kernels, and good, powerful software. Unfortunately, only a few people could use &UNIX;, because it was written mainly for those students and professionals who had studied the system for a long time. For example, the standard method for reading USENET news was:</para>
+
+<screen
+><userinput
+><command
+>find</command
+> <filename
+>/var/spool/news</filename
+> <parameter
+>-name '[0-9]*' -exec cat {} \;</parameter
+> | <command
+>more</command
+></userinput
+>
+</screen>
+
+<para
+>Although fast and relatively efficient, this couldn't be called user friendly. Today, there are many good front ends available, such as <application
+>tin</application
+> and &knode;, which provide easy-to-use, intuitive graphical user interfaces (&GUI;s). Unfortunately, the &GUI;s lack a common look-and-feel. Commercial libraries for programmers like &Motif; promised a solution to this, but these libraries remained, until recently, far too expensive and far too slow. </para>
+
+<para
+>The configuration of programs is also often difficult. While compiling is usually done with a command line such as <userinput
+><command
+>./configure</command
+> &amp;&amp; <command
+>make</command
+> &amp;&amp; <command
+>make <option
+>install</option
+></command
+></userinput
+> only a very few programs can be configured with menus or scripts. In most cases, you must edit text configuration files yourself. It often happens that a misplaced period ruins the whole file, forcing you to restart the configuration process. Whenever you need to change your settings or reconfigure a program, the whole mess comes up again.</para>
+
+<para
+>All this contributes to the fact that &Linux; and other &UNIX;'s fail to reach a wider audience. At the same time, many people are not satisfied with their current operating system, often because of the lack of stability and performance found in those operating systems. Other people hate to buy a new computer each time a new version of the program they cannot live without comes out, because it needs more <acronym
+>RAM</acronym
+> and more disk space. Often the new version provides functions few people really need. </para>
+
+<para
+><emphasis
+>&kde; is different.</emphasis
+> Although we do not try to replace the standard &UNIX; shell, we are working on a tool that will make using &UNIX; easier. We also want to attract more users to the &UNIX; environment. Simple things will be made easy, yet complex things will still be just as possible. A single interface will be provided, instead of the dozens currently required. </para>
+
+</sect1>
+
+
+<sect1 id="what-kde-can-do-for-you">
+<title
+>What &kde; Can Do For You</title>
+
+<para
+>&kde; is designed for everyone.</para>
+
+<para
+>Those new to &UNIX;, or those who simply have no interest in learning to use new technologies and commands not found in their previous operating systems don't need to face the intricacies of the command line unless they want to. Yet there is much &kde; offers that is of value to experienced &UNIX; users, with &GUI; tools to make simple what were previously complex tasks, and the command line just a mouse click away if you want it.</para>
+
+<para
+>No matter what your level of experience with &UNIX; or any other operating system, &kde; brings you:</para>
+
+<itemizedlist>
+<listitem>
+<para
+>A good looking, easy to use desktop environment.</para>
+</listitem>
+<listitem>
+<para
+>A powerful, easy to use file manager</para>
+</listitem>
+<listitem>
+<para
+>An equally powerful and easy to use web browser</para>
+</listitem>
+<listitem>
+<para
+>A simple, centralised configuration</para>
+</listitem>
+<listitem>
+<para
+>A comprehensive list of applications, so you can be productive within minutes of your first &kde; login.</para>
+</listitem>
+<listitem>
+<para
+>Online help to support you in every situation.</para>
+</listitem>
+<listitem>
+<para
+>Consistency of interface. Menus are in the same place across applications, keybindings behave the same way, toolbar icons, once learned, always work the same.</para>
+</listitem>
+</itemizedlist>
+
+</sect1>
+
+<sect1 id="background-of-kde">
+<title
+>The Background Of &kde;</title>
+
+<para
+>In October 1996, German <application
+>LyX</application
+> developer Matthias Ettrich initiated the development of &kde; with a USENET posting. Soon after, a couple of interested developers began planning and programming parts of the new project. One year later, the window and file managers, the terminal emulator, the help system and the display configuration tool were released for Alpha and Beta testing and proved to be relatively stable. </para>
+
+<para
+>In July 1998, &kde; 1.0 was released. It was the stable version for the next six months, while developers continued work on improving &kde; without stability constraints. In January 1999, their improvements were consolidated and integrated to produce &kde; 1.1, the new standard, stable version. </para>
+
+<para
+>Development continued from there with &kde; 2.0, an almost complete rewrite of the desktop, being released on October 23rd 2000. The &kde; 2.x version evolved through six minor releases over the period of a year, each bringing an already impressive desktop further features and stability.</para>
+
+<para
+>At the time of writing, &kde; 3.2 is in preparation for release, introducing a broad range of improvements over the 2.0 series. Although the &GUI; didn't change as dramatically as it did during the move from &kde; 1 to &kde; 2, many refinements like a completely new printing system, vastly improved <acronym
+>SSL</acronym
+> support (for secure Internet transactions) or full support for languages which are written right-to-left (like Arabic or Hebrew) found their way into the desktop. You can find more information about this exciting development at &kde-http;. </para>
+
+<para
+>The developers and users communicate primarily via several mailing lists, as described in the <link linkend="mailing-lists"
+>Mailing Lists</link
+> section. If you would like to help, please do, &kde; is driven by volunteer contribution, and you are always welcome to take part.</para>
+
+</sect1>
+
+<sect1 id="getting-kde">
+<title
+>How To Get New Components</title>
+
+<para
+>The main web site for &kde; is &kde-http;. Here you can find all important information regarding &kde;, including announcements, bugfixes, developer information and much more.</para>
+
+<para
+>For software upgrades, please visit our &FTP; site, &kde-ftp;, or use a mirror if one exists near you. You can find an up to date list of mirrors at <ulink url="http://www.kde.org/ftpmirrors.html"
+>http://www.kde.org/ftpmirrors.html</ulink
+>.</para>
+
+<para
+>On the &FTP; servers, the folder <filename
+>unstable</filename
+> always contains brand new software, but it is often untested and may not even compile. If you are looking for more reliable components, please take a look in the <filename
+>stable</filename
+> folder, where we put Beta and release versions. </para>
+
+<para
+>If you are interested in developing &kde; applications of your own, you should visit <ulink url="http://developer.kde.org/"
+>http://developer.kde.org/"</ulink
+> where you will find a wealth of information, including tutorials, <acronym
+>API</acronym
+> guides to the &kde; libraries, and much more. You should also visit Troll Tech's server (<ulink url="http://www.trolltech.com/"
+>http://www.trolltech.com</ulink
+>) which features a great deal of information concerning the &Qt; library used by &kde;. You will probably find it valuable to join <link linkend="mailing-lists"
+>the &kde; developer mailing list</link
+>.</para>
+
+</sect1>
+
+</chapter>
+<!--
+Local Variables:
+mode: sgml
+sgml-omittag:nil
+sgml-shorttag:t
+sgml-namecase-general:t
+sgml-general-insert-case:lower
+sgml-minimize-attributes:nil
+sgml-always-quote-attributes:t
+sgml-indent-step:0
+sgml-indent-data:nil
+sgml-parent-document:("index.docbook" "book" "chapter")
+End:
+-->
\ No newline at end of file
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/index.cache.bz2 b/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/index.cache.bz2
new file mode 100644
index 00000000000..12039a7d83f
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/index.cache.bz2
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/index.docbook b/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/index.docbook
new file mode 100644
index 00000000000..d1d8b2db1ee
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/index.docbook
@@ -0,0 +1,116 @@
+<?xml version="1.0" ?>
+<!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" 
+"dtd/kdex.dtd" [
+  <!ENTITY kappname "&kde; User's Guide">
+  <!ENTITY introduction SYSTEM "intro.docbook">
+  <!ENTITY history SYSTEM "history.docbook">
+  <!ENTITY installation SYSTEM "installation.docbook">
+  <!ENTITY first-impressions SYSTEM "first-impressions.docbook">
+  <!ENTITY getstarted SYSTEM "getting-started.docbook">
+  <!ENTITY about-desktop SYSTEM "about-desktop.docbook">
+  <!ENTITY shortcuts SYSTEM "shortcuts.docbook">
+  <!ENTITY ug-faq SYSTEM "ug-faq.docbook">
+  <!ENTITY more-help SYSTEM "more-help.docbook">
+  <!ENTITY staff SYSTEM "staff.docbook">
+  <!ENTITY notices-and-trademarks SYSTEM "notices-trademarks.docbook">
+  <!ENTITY % addindex "IGNORE">
+  <!ENTITY % British-English "INCLUDE"
+> <!-- change language only here -->
+]>
+
+<book lang="&language;">
+<bookinfo>
+<title
+>K Desktop Environment</title>
+<authorgroup>
+<author>
+<surname
+>The KDE Team</surname>
+</author>
+<othercredit role="translator"
+><firstname
+>Malcolm</firstname
+><surname
+>Hunter</surname
+><affiliation
+><address
+><email
+>malcolm.hunter@gmx.co.uk</email
+></address
+></affiliation
+><contrib
+>Conversion to British English</contrib
+></othercredit
+> 
+</authorgroup>
+
+<date
+>2003-10-19</date>
+<releaseinfo
+>3.2</releaseinfo>
+
+<copyright>
+<year
+>2000</year
+><year
+>2001</year
+><year
+>2002</year
+><year
+>2003</year>
+<holder
+>The KDE Team</holder>
+</copyright>
+
+<legalnotice
+>&GPLNotice;</legalnotice>
+
+<!-- Please note: This is NOT the final KDE Users Guide, which is not complete.
+This is a quick rewrite of the KDE 1.1x user guide, because it was badly out of
+date, and so that KDE wasn't released without a users guide entirely.  -->
+
+<abstract
+><para
+>This is the &kde; User's Guide, a complete documentation of the K Desktop Environment from the user perspective. The K Desktop Environment is a collection of tools that will make your &UNIX; life easier and more enjoyable. </para
+></abstract>
+
+<keywordset>
+<keyword
+>KDE</keyword>
+<keyword
+>user</keyword>
+<keyword
+>guide</keyword>
+</keywordset>
+</bookinfo>
+
+&introduction;
+&history;
+<!-- &installation; -->
+&first-impressions;
+&getstarted;
+&about-desktop;
+&shortcuts;
+&ug-faq;
+&more-help;
+&staff;
+&notices-and-trademarks;
+</book>
+<!--
+Local Variables:
+mode: sgml
+sgml-omittag:nil
+sgml-shorttag:t
+sgml-namecase-general:t
+sgml-general-insert-case:lower
+sgml-minimize-attributes:nil
+sgml-always-quote-attributes:t
+sgml-indent-step:0
+sgml-indent-data:nil
+sgml-parent-document:nil
+sgml-exposed-tags:nil
+sgml-local-catalogs:nil
+sgml-local-ecat-files:nil
+End:
+-->
+
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/installation.docbook b/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/installation.docbook
new file mode 100644
index 00000000000..73a92b8eba3
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/installation.docbook
@@ -0,0 +1,729 @@
+<chapter id="installation">
+<title
+>Installation </title>
+
+<epigraph>
+<attribution
+>Linus Torvalds, after finding one of his file systems smashed by a new Beta kernel</attribution>
+<para
+>Core dumping fsck's tend to make me nervous</para>
+</epigraph>
+
+<para
+>Don't worry! Although the use of some Beta software can cause considerable grief, it is unlikely that the installation of KDE will trash your hard disk. In fact, this chapter is designed to guide you through the installation process, so that you can take a look at your new desktop as quickly (and with as little grief) as possible. As with all new Window Manager installs, it is recommended that you back up all your X11-specific configuration files before you begin the install. If you do not know the exact location of them, try all the hidden (<filename
+>.*</filename
+>) files in your home folder and the folder <filename
+>/usr/X11/lib/X11/xdm</filename
+>. </para
+> 
+
+<sect1 id="requirements">
+<title
+>Requirements </title>
+
+<para
+>Before installing KDE, ascertain that your system fulfills the following requirements: </para>
+
+<itemizedlist>
+
+<listitem
+><para
+>A running POSIX compatible UNIX system. UNIX's that are known to work with KDE include: Linux, FreeBSD, Solaris, HP-UX, and MkLinux. We are working to make KDE available for more platforms soon. </para
+></listitem>
+
+<listitem
+><para
+>Some free hard disk space on the partition where <filename
+>/opt/kde</filename
+> will be created. We recommend that you reserve about 50MB if your system supports shared libraries, and considerably more if it does not. If you need or want to build KDE from the source tree, please remember to reserve about 100MB in <filename
+>/usr/src</filename
+>.</para
+></listitem>
+
+<listitem
+><para
+>A running X11 system with or without <application
+>xdm</application
+>. If you have not installed the X Window System yet, first check your UNIX installation media for an installable version. If you cannot find any version working, visit <ulink url="http://www.xfree86.org"
+>the XFree86 web site</ulink
+> for more information on how to get and install the X Window System, or contact your UNIX vendor support. </para
+></listitem>
+
+<listitem
+><para
+>The &Qt; libraries, version 3.2 or higher. You can obtain these at <ulink url="ftp://ftp.trolltech.com/qt"
+>Troll Tech's FTP Server</ulink
+> in tgz format. </para>
+</listitem>
+</itemizedlist>
+
+<warning
+><para
+>A warning before you start: Before upgrading from a previous version of &kde;, we recommend that you do the following:</para>
+
+<screen
+><command
+>cd <filename
+>/opt/kde</filename
+></command
+> 
+<command
+>tar <option
+>cfvz <replaceable
+>~/KDE-old-version-backup.tar.gz</replaceable
+> * </option
+></command
+>
+</screen>
+</warning>
+
+</sect1>
+
+<sect1 id="linux-installing-rpms">
+<title
+>Linux: Installing RPMs for RedHat, Caldera and SuSE.</title>
+
+<para
+>Using RPMs is the easiest method to get KDE up and running. Just visit your favourite KDE mirror and visit the folder <filename
+>/pub/kde/stable/distribution/rpm</filename
+>. There, you can see folders for different operating systems. Currently, the i386, alpha and sparc architectures are supported. The RPM packages can also be found on the Red Hat contrib sites like sunsite.unc.edu or ftp.redhat.com. </para>
+
+<para
+>The basic system consists of the files <filename
+>kde-<replaceable
+>component</replaceable
+>.<replaceable
+>architecture</replaceable
+>.rpm</filename
+> You need at least tdesupport, tdelibs and tdebase. After getting the base distribution, feel free to download any other RPMs that you think may come in handy. </para>
+
+<para
+>Next, start installing with the base package. If you are installing KDE for the first time, use </para>
+
+<screen
+><userinput
+><command
+>rpm</command
+> <option
+>-i</option
+> <filename
+>tdesupport.arch.rpm</filename
+></userinput>
+<userinput
+><command
+>rpm</command
+> <option
+>-i</option
+> <filename
+>tdelibs.arch.rpm</filename
+></userinput>
+<userinput
+><command
+>rpm</command
+> <option
+>-i</option
+> <filename
+>tdebase.arch.rpm</filename
+></userinput
+>
+</screen>
+ 
+<important
+><para
+>It is important that these components are installed in the order listed, and that they are installed before any other KDE component.</para
+></important>
+
+<para
+>If you are upgrading from a previous release, try <screen
+><userinput
+><command
+>rpm</command
+> <option
+>-Uvh</option
+> <filename
+>kde-<replaceable
+>component</replaceable
+>.<replaceable
+>arch</replaceable
+>.rpm</filename
+></userinput
+>
+</screen>
+</para>
+
+<para
+>Once again, the order given above should be preserved, and the given components should be installed before any other KDE components.</para>
+
+<para
+>This will unpack the base distribution and install it by default in <filename
+>/opt/kde</filename
+>.</para>
+
+<para
+>If the installation of the base packages has been successful, you can install the remaining packages (use <option
+>-Uvh</option
+> instead of <option
+>-i</option
+> once again to update an existing version) the same way. </para>
+
+</sect1>
+
+<sect1 id="installing-debian">
+<title
+>Linux: Installing <acronym
+>DEB</acronym
+>s for debian</title>
+
+<para
+>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.</para>
+
+<para
+>The first step is to tell your system where it can find the deb packages for KDE. A list of locations for the Debian packages is kept on your hard disk in <filename
+>/etc/apt/sources.list</filename
+>. You should add to that file the following line: <userinput
+>http://kde.tdyc.com/ stable kde2</userinput
+></para>
+
+ 
+<para
+>Then you have to update your local package database so that your system knows that there are new packages available. Type the following command:</para>
+
+<screen
+><userinput
+><command
+>apt-get</command
+> <option
+>update</option
+></userinput
+>
+</screen>
+ 
+<para
+>Finally you should install the KDE base components. This is accomplished by typing:</para>
+
+<screen
+><userinput
+><command
+>apt-get</command
+> <option
+>install tdebase</option
+></userinput
+>
+</screen>
+ 
+<para
+>If you want to install other components you should try some, or all of these options:</para>
+
+<screen
+><userinput
+><command
+>apt-get</command
+> <option
+>install task-tdenetwork</option
+></userinput>
+<userinput
+><command
+>apt-get</command
+> <option
+>install task-tdeadmin</option
+></userinput>
+<userinput
+><command
+>apt-get</command
+> <option
+>install task-tdetoys</option
+></userinput>
+<userinput
+><command
+>apt-get</command
+> <option
+>install task-tdeutils</option
+></userinput>
+<userinput
+><command
+>apt-get</command
+> <option
+>install task-tdemultimedia</option
+></userinput>
+<userinput
+><command
+>apt-get</command
+> <option
+>install task-tdegraphics</option
+></userinput>
+<userinput
+><command
+>apt-get</command
+> <option
+>install task-tdepim</option
+></userinput>
+<userinput
+><command
+>apt-get</command
+> <option
+>install task-tdegames</option
+></userinput>
+<userinput
+><command
+>apt-get</command
+> <option
+>install task-koffice</option
+></userinput>
+<userinput
+><command
+>apt-get</command
+> <option
+>install tdebase-docs</option
+></userinput>
+<userinput
+><command
+>apt-get</command
+> <option
+>install kdm</option
+></userinput
+>
+</screen>
+
+<para
+>You may also be interested in installing your language.</para>
+
+<screen
+><userinput
+><command
+>apt-get</command
+> <option
+>install
+tde-i18n-<replaceable
+>xx</replaceable
+></option
+></userinput
+>
+ </screen>
+<para
+>where <replaceable
+>xx</replaceable
+> has to be substituted by the country code.</para>
+
+<para
+>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</filename
+> and most of the auxiliary files in <filename class="directory"
+>/usr/share</filename
+> under different folders. </para>
+
+<para
+>If you are upgrading from a previous version of KDE you should perform the following steps. First, update file <filename
+>/etc/apt/sources.list</filename
+> by changing the line with the location of KDE packages with line: <userinput
+>http://kde.tdyc.com/ stable kde2</userinput
+>. Second update your package database:</para>
+
+<screen
+><userinput
+><command
+>apt-get</command
+> <option
+>update</option
+></userinput
+>
+</screen>
+ 
+<para
+>Finally install the KDE base system:</para>
+
+<screen
+><userinput
+><command
+>apt-get</command
+> <option
+>install tdebase</option
+></userinput>
+<userinput
+><command
+>apt-get</command
+> <option
+>dist-upgrade</option
+></userinput
+>
+</screen>
+ 
+<para
+>If you want to install more KDE components try some, or all of these options.</para>
+
+<screen
+><userinput
+><command
+>apt-get</command
+> <option
+>install task-tdenetwork</option
+></userinput>
+<userinput
+><command
+>apt-get</command
+> <option
+>install task-tdeadmin</option
+></userinput>
+<userinput
+><command
+>apt-get</command
+> <option
+>install task-tdetoys</option
+></userinput>
+<userinput
+><command
+>apt-get</command
+> <option
+>install task-tdeutils</option
+></userinput>
+<userinput
+><command
+>apt-get</command
+> <option
+>install task-tdemultimedia</option
+></userinput>
+<userinput
+><command
+>apt-get</command
+> <option
+>install task-tdegraphics</option
+></userinput>
+<userinput
+><command
+>apt-get</command
+> <option
+>install task-tdepim</option
+></userinput>
+<userinput
+><command
+>apt-get</command
+> <option
+>install task-tdegames</option
+></userinput>
+<userinput
+><command
+>apt-get</command
+> <option
+>install task-koffice</option
+></userinput>
+<userinput
+><command
+>apt-get</command
+> <option
+>install tdebase-docs</option
+></userinput>
+<userinput
+><command
+>apt-get</command
+> <option
+>install kdm</option
+></userinput
+>
+</screen>
+
+</sect1>
+
+<sect1 id="source-distribution">
+<title
+>Using Source Compilation to Install on Top of Other Systems </title>
+
+<para
+>If your Linux distribution did not come with an RPM or DEB archive format, or you are not using Linux at all, you must compile KDE on your own. In the future, we are planning to provide a binary distribution which includes its own installation program. </para>
+
+<para
+>In order to compile and install KDE properly, you need to have the following items installed on your hard disk: </para>
+
+<itemizedlist>
+<listitem
+><para
+>An ANSI-C compiler, <abbrev
+>e.g.</abbrev
+> the <abbrev
+>GNU</abbrev
+> C compiler. </para
+></listitem>
+<listitem
+><para
+>An ANSI-C++ compiler, <abbrev
+>e.g.</abbrev
+> <abbrev
+>GNU</abbrev
+> C++. </para
+></listitem>
+<listitem
+><para
+>The <application
+>make</application
+> utility. </para
+></listitem>
+<listitem
+><para
+>Qt development version 2.2 or higher.</para
+></listitem>
+<listitem
+><para
+>X11 development version (include files are often missing) </para
+></listitem>
+</itemizedlist>
+
+<para
+>Once you have all the needed helper applications, go to your favourite KDE mirror and retrieve the following files from the folder <filename
+>/pub/kde/stable/<replaceable
+>newest version</replaceable
+></filename
+>:</para>
+
+<itemizedlist>
+<listitem
+><para
+><filename
+>tdesupport-<replaceable
+>version</replaceable
+>.tar.gz</filename
+></para
+></listitem>
+<listitem
+><para
+><filename
+>tdelibs-<replaceable
+>version</replaceable
+>.tar.gz</filename>
+</para
+></listitem>
+<listitem
+><para
+><filename
+>tdebase-<replaceable
+>version</replaceable
+>.tar.gz</filename
+></para
+></listitem>
+<listitem
+><para
+>any other packages you wish to install. We advise you to get at least tdeutils. </para
+></listitem>
+</itemizedlist>
+
+<para
+>In all cases above, <replaceable
+>version</replaceable
+> stands for the current version number. Once you have downloaded all you need, extract these files to <filename
+>/usr/src</filename
+>. This process should yield the following folder structure:</para>
+
+<itemizedlist>
+<listitem
+><para
+><filename
+>/usr/src/tdesupport</filename
+></para
+></listitem>
+<listitem
+><para
+><filename
+>/usr/src/tdelibs</filename
+></para
+></listitem>
+<listitem
+><para
+><filename
+>/usr/src/tdebase</filename
+></para
+></listitem>
+<listitem
+><para
+><filename
+>/usr/src/...</filename
+> (any other packages)</para
+></listitem>
+</itemizedlist>
+
+<para
+>Make sure you have write permissions to <filename
+>/opt/kde</filename
+>.</para>
+
+<para
+>Next you must compile and install the packages using the following: </para>
+
+<procedure>
+<step
+><para
+><command
+>cd</command
+> into the folder of the package, you want to install (see above)</para
+></step>
+<step
+><para
+><command
+>./configure</command
+> (with the options you want to apply)</para
+></step>
+<step
+><para
+><command
+>make</command
+></para
+></step>
+<step
+><para
+><command
+>make install</command
+></para
+></step>
+</procedure>
+
+<para
+>Apply the above steps to every package you want to install.</para>
+
+<note
+><para
+>These instructions can be used for almost every source package available, not just KDE packages. </para
+></note>
+
+<para
+>Every configure script has several options available. Some are common between the packages while others are specific to an individual package. The following is a small part of the result of <command
+>configure <option
+>--help</option
+></command
+> in tdelibs:</para>
+
+<screen
+><computeroutput>
+ Installation directories:
+  --prefix=PREFIX         install architecture-independent files in PREFIX
+                          [/usr/local/kde-cvs]
+...
+Optional Features:
+  --disable-FEATURE       do not include FEATURE (same as --enable-FEATURE=no)
+  --enable-FEATURE[=ARG]  include FEATURE [ARG=yes]
+  --disable-fast-perl     disable fast Makefile generation (needs perl)
+  --enable-debug=ARG    enables debug symbols (yes|no|full) default=no
+  --disable-debug         disables debug output and debug symbols default=no
+  --enable-strict         compiles with strict compiler options (may not work!)
+  --disable-warnings      disables compilation with -Wall and similar
+... 
+</computeroutput
+>
+</screen>
+
+<para
+>Several options are not required and are only useful as workarounds for known problems (&eg; <option
+>--disable-FEATURE</option
+>). Since some are important options, for instance <emphasis
+>--with-shadow</emphasis
+>, you should always check the available options.</para>
+
+<para
+>An important option is <option
+>--prefix</option
+>. This option specifies the path where configure should install (for tdesupport and tdelibs) or where to look for libraries (for the other packages). By default, configure will look in <filename
+>/usr/local/kde</filename
+> . If you want to install &kde; into <filename
+>/opt/kde</filename
+>, you have to use <command
+>configure <option
+>--prefix /opt/kde</option
+></command
+>.</para>
+
+<para
+>If you have installed the &Qt; libraries in an uncommon place, for instance in <filename
+>$HOME/src/qt</filename
+>, you must use <command
+>configure <option
+>--with-qt-dir=$HOME/src/qt</option
+></command
+>. By default configure looks in the most common places for &Qt; before it gives up.</para>
+
+<para
+>If you have problems that you are not able to solve, send a copy of the <filename
+>config.log</filename
+> file to the address given in the offending package's <filename
+>README</filename
+> file.</para>
+
+<para
+>You must install KDE in the following order: arts, tdelibs, then the application packages (for example tdebase). All the application packages should only depend on tdelibs, so you can compile them at the same time (if you have a powerful machine).</para>
+
+<para
+>If you want to take advantage of multiprocessor systems, try <command
+>make <option
+> -j <replaceable
+>Number of processors</replaceable
+></option
+></command
+> instead of <command
+>make</command
+>. </para>
+
+<sect2>
+<title
+>Platform Specific Building Notes </title>
+
+<sect3>
+<title
+>Linux </title>
+
+<para
+>For &Linux;, most of the utilities needed to build &kde; can be found either at <ulink url="ftp://sunsite.unc.edu/pub/Linux/GCC"
+>ftp://sunsite.unc.edu/pub/Linux/GCC</ulink
+> or <ulink url="ftp://sunsite.unc.edu/pub/GNU"
+>ftp://sunsite.unc.edu/pub/GNU</ulink
+>. The Qt libraries can be found at <ulink url="ftp://ftp.troll.no/pub/qt/source"
+>ftp://ftp.troll.no/pub/qt/source</ulink
+>, available as source code. Detailed instructions on how to install them are provided. Include files for X11 programs should be available at <ulink url="ftp://ftp.xfree86.org"
+>ftp://ftp.xfree86.org</ulink
+> in the xdevel section. </para>
+
+</sect3>
+</sect2>
+</sect1>
+
+<sect1 id="suse-install">
+<title
+>Required Changes To Your Configuration Files </title>
+<para
+>After you have placed the KDE binaries into their destination folder, there are a few adjustments you must make to your startup scripts. </para>
+<para
+>The following procedure was tested on SuSE Linux 5.0, and should be compatible with the other popular UNIX's as well. <emphasis
+>Always make backups of configuration files before changing them!</emphasis
+> Add the following to the end of your /etc/profile: </para>
+<para
+> 
+<screen
+>export PATH=$PATH:/opt/kde/bin 
+export KDEDIR=/opt/kde
+</screen>
+ </para>
+<para
+>Next, edit the .xinitrc file in your home folder. Look for the line that calls your window manager and replace it with <literal
+>starttde</literal
+>.</para>
+<para
+>Now that everything needed to run KDE has been installed, you can go on to chapter 4 where you will start KDE for the first time. If something goes wrong, you may need to compile KDE on your own. Read<emphasis
+> <link linkend="source-distribution"
+>Using Source Compilation to Install on Top of Other Systems</link
+> </emphasis
+>for more information. </para>
+<para
+>We have made the installation as bulletproof as possible, so you should not encounter any serious problems unless your configuration is exotic. If you do experience difficulties feel free to use <link linkend="mailing-lists"
+>the KDE mailing lists</link
+> </para>
+</sect1>
+</chapter>
+<!--
+Local Variables:
+mode: sgml
+sgml-omittag:nil
+sgml-shorttag:t
+sgml-namecase-general:t
+sgml-general-insert-case:lower
+sgml-minimize-attributes:nil
+sgml-always-quote-attributes:t
+sgml-indent-step:0
+sgml-indent-data:nil
+sgml-parent-document:("index.docbook" "book" "chapter")
+End:
+-->
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/intro.docbook b/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/intro.docbook
new file mode 100644
index 00000000000..e1900a1800b
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/intro.docbook
@@ -0,0 +1,34 @@
+<chapter id="introduction">
+<title
+>Introduction</title>
+
+<para
+>Welcome to the K Desktop Environment User Guide.</para>
+
+<para
+>This book is intended to be an introduction to the K Desktop Environment as a whole, with a broad description of the user interface, some practical examples on how to use &kde; for daily work, and some hints on how to customise the &kde; desktop.</para>
+
+<para
+>Included is a table of shortcuts, and some tips and tricks intended to help you find your way around quickly and efficiently.</para>
+
+<para
+>This book is not a guide to the use of the individual applications, as they each have their own User Manual. However, &kde; is an integrated environment &mdash; what you learn in this manual and in your own exploration of &kde;'s interface is consistent and readily transferable between &kde; applications.</para>
+
+<para
+>This book also explores some of the philosophy behind &kde; and some of its history, and rounds out with how to find more information, should you need it.</para>
+
+</chapter>
+<!--
+Local Variables:
+mode: sgml
+sgml-omittag:nil
+sgml-shorttag:t
+sgml-namecase-general:t
+sgml-general-insert-case:lower
+sgml-minimize-attributes:nil
+sgml-always-quote-attributes:t
+sgml-indent-step:0
+sgml-indent-data:nil
+sgml-parent-document:("index.docbook" "book" "chapter")
+End:
+-->
\ No newline at end of file
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/koffice-apps.docbook b/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/koffice-apps.docbook
new file mode 100644
index 00000000000..8b579888517
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/koffice-apps.docbook
@@ -0,0 +1,92 @@
+<chapter id="office-apps">
+<title
+>Office Applications</title>
+
+<para
+>You can get the following applications in the &koffice; distributions.</para>
+
+<para
+>Stable applications are relatively bug free and come in source and binary formats.</para>
+
+<para
+><ulink url="ftp://ftp.kde.org/pub/kde/stable/latest/distribution/"
+>ftp.kde.org/pub/kde/stable/latest/distribution/stable</ulink
+></para>
+
+<para
+>Unstable versions change daily and are only in source form, meaning you must compile them to get a working version. Remember these are unstable and might not even compile. If you have a problem with an unstable application, report the problem and it will most likely be fixed in a future snapshot.</para>
+<para
+><ulink url="ftp://ftp.kde.org/pub/kde/unstable/CVS/snapshots/current/"
+>ftp.kde.org/pub/kde/unstable/CVS/snapshots/current</ulink
+></para>
+
+<variablelist
+> <varlistentry
+> <term
+>&kword;</term
+> <listitem
+> <para
+>A powerful and fully featured frames based word processor capable of professional document layout.</para
+> </listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&kspread;</term
+> <listitem
+> <para
+>A powerful spreadsheet application.</para
+> </listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&kpresenter;</term
+> <listitem
+> <para
+>A presentation program that meets professional presentation requirements.</para
+> </listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&kivio;</term
+> <listitem
+> <para
+>A flowchart and diagramming application.</para
+> </listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&kontour;</term
+> <listitem
+> <para
+>An up and coming vector illustration application.</para
+> </listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&kugar;</term
+> <listitem
+> <para
+>A tool for generating business quality reports.</para
+> </listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&kchart;</term
+> <listitem
+> <para
+>An integrated graph and chart drawing tool.</para
+> </listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&koshell;</term
+> <listitem
+> <para
+>A tool to help you create seamless multi application documents.</para
+> </listitem
+> </varlistentry
+> </variablelist>
+
+</chapter>
+
+
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/more-help.docbook b/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/more-help.docbook
new file mode 100644
index 00000000000..a62047b4dab
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/more-help.docbook
@@ -0,0 +1,68 @@
+<chapter id="more-help">
+<title
+>Further Help</title>
+
+<sect1 id="mailing-lists">
+<title
+>Other Sources for Help </title>
+
+<para
+>Take a look at the &kde-http; for the most up-to-date information available about &kde; on the web. You may also want to subscribe to our mailing lists. </para>
+
+<para
+>You can subscribe at the web pages listed below:</para>
+
+<simplelist>
+
+<member
+>&kde; announcements - <ulink url="http://mail.kde.org/mailman/listinfo/kde-announce"
+> http://mail.kde.org/mailman/listinfo/kde-announce</ulink
+></member>
+
+<member
+>&kde; users' mailing list - <ulink url="http://mail.kde.org/mailman/listinfo/kde"
+> http://mail.kde.org/mailman/listinfo/kde</ulink
+></member>
+
+<member
+>KDE developers' mailing list - <ulink url="http://mail.kde.org/mailman/listinfo/kde-devel"
+> http://mail.kde.org/mailman/listinfo/kde-devel</ulink
+></member>
+
+<member
+>KDE look and feel discussions - <ulink url="http://mail.kde.org/mailman/listinfo/kde-look"
+> http://mail.kde.org/mailman/listinfo/kde-look </ulink
+></member>
+
+<member
+>KDE licensing questions - <ulink url="http://mail.kde.org/mailman/listinfo/kde-licensing"
+> http://mail.kde.org/mailman/listinfo/kde-licensing </ulink
+></member>
+
+<member
+>KDE Documenters' list - <ulink url="http://mail.kde.org/mailman/listinfo/kde-doc-english"
+> http://mail.kde.org/mailman/listinfo/kde-doc-english </ulink
+></member>
+</simplelist>
+
+<para
+>Many &kde; applications and sub-projects maintain more specific lists for themselves. You can find a complete list of archives at <ulink url="http://lists.kde.org/"
+>http://lists.kde.org/</ulink
+>.</para>
+
+</sect1>
+</chapter>
+<!--
+Local Variables:
+mode: sgml
+sgml-omittag:nil
+sgml-shorttag:t
+sgml-namecase-general:t
+sgml-general-insert-case:lower
+sgml-minimize-attributes:nil
+sgml-always-quote-attributes:t
+sgml-indent-step:0
+sgml-indent-data:nil
+sgml-parent-document:("index.docbook" "book" "chapter")
+End:
+-->
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/notices-trademarks.docbook b/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/notices-trademarks.docbook
new file mode 100644
index 00000000000..49fda79a921
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/notices-trademarks.docbook
@@ -0,0 +1,110 @@
+<appendix id="legal-notices-and-trademarks">
+<title
+>Legal Notices</title>
+<sect1 id="legal-status">
+<title
+>Licence</title>
+
+<para
+>&kde; is open source software, and all of &kde; is released under free licenses such as the GPL.</para>
+
+</sect1>
+
+<sect1 id="trademarks-list">
+<title
+>Trademarks</title>
+
+<!-- <para
+>&kde; and <quote
+>K Desktop Environment</quote
+> are registered
+trademarks of KDE e.V.</para
+> -->
+
+<para
+>All trademarks mentioned on this web server or in &kde; documentation are recognised as belonging to their respective owners, including but not limited to:</para>
+
+<simplelist>
+<member
+>&AIX; is a registered trademark of IBM Corporation</member>
+<member
+>&CSS;, &XHTML;, &XSL; and &XML; are common law trademarks of the Massachusetts Institute of Technology, Institut National de Recherche en Informatique et en Automatique, or Keio University on behalf of the World Wide Web Consortium.</member>
+<member
+>&Handspring; and &Visor; are trademarks of Handspring, Inc. and may be registered in certain jurisdictions.</member>
+<member
+>&Hewlett-Packard;, &HP; &LaserJet;,&HP-UX; PCL, PCL 5 and PCL 6 are U.S. registered trademarks of Hewlett Packard Company.</member>
+<member
+>&IRIX; is a registered trademark and &SGI; is a trademark of Silicon Graphics, Inc.</member>
+<member
+>&Java; and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries.</member>
+<member
+>&Jini; and all Jini-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the US and other countries.</member>
+<member
+>&Linux; is a registered trademark of Linus Torvalds</member>
+<member
+>&LinuxPPC; is a trademark of LinuxPPC Inc.</member>
+<member
+>&Mac; is a trademark of Apple Computer Inc., registered in the United States and other countries.</member>
+<member
+>&Mandrake; and &Linux-Mandrake; are trademarks of MandrakeSoft.</member>
+<member
+>&Netscape; is a registered trademark of Netscape Communications Corporation in the United States and other countries.</member>
+<member
+>&NeXTSTEP; is a trademark of NeXT Software, Inc., registered in the U.S. and other countries. </member>
+<member
+>&PalmOS;, &HotSync; and &PalmPilot; are registered trademarks of Palm, Inc.</member>
+<member
+>&PostScript; is a registered trademark of Adobe Systems Incorporated.</member>
+<member
+>&Qt; is a trademark of Trolltech AS</member>
+<member
+>&RedHat; and all Red Hat-based trademarks and logos are trademarks or registered trademarks of Red Hat, Inc. in the United States and other countries. </member>
+<member
+>&Sendmail; is a registered trademark of Sendmail Inc.</member>
+<member
+>&Solaris;, <trademark
+>Sun</trademark
+> and <trademark
+>SunOS</trademark
+> are trademarks of Sun Microsystems Inc.</member>
+<member
+>&SuSE; is a registered trademark of SuSE AG</member>
+<member
+>&ThreeCom; is a registered trademark of 3com corporation in the United States and other countries.</member>
+<member
+>&Motif;, &UNIX; and the <quote
+>X</quote
+> device are registered trademark of The Open Group in the United States and other countries</member>
+<member
+>&Microsoft; and &Windows; are registered trademarks of the Microsoft Corporation</member>
+<member
+>XFree86 is pending trademark registration by The XFree86 Project, Inc.</member>
+</simplelist>
+
+<!-- Others that needs to be covered above:
+
+&MacOS;
+&Netscape;
+&PMX;
+&TrueType;
+&X-Window;
+Xing,
+Yamaha
+-->
+
+</sect1>
+</appendix>
+<!--
+Local Variables:
+mode: sgml
+sgml-omittag:nil
+sgml-shorttag:t
+sgml-namecase-general:t
+sgml-general-insert-case:lower
+sgml-minimize-attributes:nil
+sgml-always-quote-attributes:t
+sgml-indent-step:0
+sgml-indent-data:nil
+sgml-parent-document:("index.docbook" "book" "appendix")
+End:
+-->
\ No newline at end of file
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/shortcuts.docbook b/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/shortcuts.docbook
new file mode 100644
index 00000000000..39b1c62c17f
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/shortcuts.docbook
@@ -0,0 +1,357 @@
+<chapter id="shortcuts">
+<title
+>Tips &amp; Tricks for Your Daily Work </title>
+
+<epigraph>
+<attribution
+>Fortune Cookies</attribution>
+<para
+>Everyone can make an omelette with eggs. The trick is to make one with none.</para>
+</epigraph>
+
+<para
+>Nearly everyone can use &kde;; this is why the developers made it. There are no cryptic switches with which to cope, and few configuration files you need edit in <acronym
+>ASCII</acronym
+> style. However, there are some ways you can do your work more elegantly, saving you time for the truly important things, like &ksirtet;.</para>
+
+<sect1 id="shortcut-table">
+<title
+>Shortcut Table </title>
+
+<variablelist>
+
+<varlistentry>
+<term
+><keycombo
+>&Alt;<keycap
+>Tab</keycap
+> </keycombo
+> or <keycombo
+>&Alt;&Shift;<keycap
+>Tab</keycap
+></keycombo
+></term>
+<listitem
+><para
+>Cycle through the windows </para
+></listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+><keycombo
+>&Ctrl;<keycap
+>Tab</keycap
+></keycombo
+> or <keycombo
+>&Ctrl;&Shift;<keycap
+>Tab</keycap
+> </keycombo
+></term>
+<listitem
+><para
+>Cycle through your desktops </para
+></listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+><keycombo
+>&Alt;<keycap
+>F2</keycap
+> </keycombo
+></term>
+<listitem
+><para
+>Mini Command line</para
+></listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+><keycombo
+>&Alt;<keycap
+>F3</keycap
+></keycombo
+></term>
+<listitem
+><para
+>Window Menu </para
+></listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+><keycombo
+>&Alt;<keycap
+>F4</keycap
+> </keycombo
+></term>
+<listitem
+><para
+>Close the current window </para
+></listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+><keycombo
+>&Ctrl;<keycap
+>F{1..8}</keycap
+></keycombo
+></term>
+<listitem
+><para
+>Switch to a specific desktop </para
+></listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+><keycombo
+>&Ctrl;&Alt;<keycap
+>Esc</keycap
+> </keycombo
+></term>
+<listitem
+><para
+>Window destroyer (every window you click on will be destroyed). Press this key combination again to cancel the killer cursor. </para
+></listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+><keycombo
+>&Ctrl;&Alt;<keycap
+>Backspace</keycap
+> </keycombo
+></term>
+<listitem
+><para
+>This exits &kde; (without saving!) Use this as a last resort </para
+></listitem>
+</varlistentry>
+<varlistentry>
+<term
+><keycombo
+>&Ctrl;&Alt;<keycap
+>Numpad +</keycap
+></keycombo
+></term>
+<listitem
+><para
+>Cycles to the next screen resolution. You need to configure this in your &X-Server; configuration for it to work. </para
+></listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+><keycombo
+>&Ctrl;&Alt;<keycap
+>Numpad -</keycap
+> </keycombo
+></term>
+<listitem
+><para
+>Cycles to the previous screen resolution. You need to configure this in your &X-Server; configuration for it to work.</para
+></listitem>
+</varlistentry>
+</variablelist>
+
+</sect1>
+
+<sect1 id="mouse-techniques">
+<title
+>Mouse Techniques </title>
+
+<para
+>Note these are defaults only, and you can customise them to your liking.</para>
+
+<variablelist>
+
+<varlistentry>
+<term
+>Clicking on the border or the titlebar</term>
+<listitem>
+<variablelist>
+
+<varlistentry>
+<term
+><mousebutton
+>Left</mousebutton
+></term>
+<listitem
+><para
+>Activates and raises the window.</para
+></listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+><mousebutton
+>Middle</mousebutton
+></term>
+<listitem
+><para
+>Lowers the window</para
+></listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+><mousebutton
+>Right</mousebutton
+></term>
+<listitem
+><para
+>Shows the <guimenu
+>Window menu</guimenu
+> if the window is active, otherwise activates the window.</para
+></listitem>
+</varlistentry>
+</variablelist>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+>Doubleclick on the window title</term>
+<listitem
+><para
+>Shades the window (<quote
+>rolls it up</quote
+> so only the titlebar is visible).</para
+></listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+>Drag on the titlebar</term>
+<listitem
+><para
+>Moves the window around.</para
+></listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+>Drag on corners or edges</term>
+<listitem
+><para
+>Resizes the window.</para
+></listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+><keycombo
+>&Alt;<mousebutton
+>Left</mousebutton
+></keycombo
+> Button</term>
+<listitem
+><para
+>Moves the window around.</para
+></listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+><keycombo
+>&Alt;<mousebutton
+>Middle</mousebutton
+> </keycombo
+> Button</term>
+<listitem
+><para
+>Raises the window.</para
+></listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+><keycombo
+>&Alt;<mousebutton
+>Right</mousebutton
+> </keycombo
+> Button</term>
+<listitem
+><para
+>Resizes the window in the direction you drag the mouse.</para
+></listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+>Click on the Icon on the top left</term>
+<listitem
+><para
+>Close the application</para
+></listitem>
+</varlistentry>
+<varlistentry>
+<term
+>Click on the Sticky Button</term>
+<listitem
+><para
+>toggles sticky </para
+></listitem>
+</varlistentry>
+
+<varlistentry>
+<term
+>Clicking on Maximise</term>
+<listitem>
+<variablelist>
+<varlistentry>
+<term
+><mousebutton
+>Left</mousebutton
+></term>
+<listitem
+><para
+>Maximises the window</para
+></listitem>
+</varlistentry>
+<varlistentry>
+<term
+><mousebutton
+>Middle</mousebutton
+></term>
+<listitem
+><para
+>Maximises only vertically</para
+></listitem>
+</varlistentry>
+<varlistentry>
+<term
+><mousebutton
+>Right</mousebutton
+></term>
+<listitem
+><para
+>Maximises horizontally</para
+></listitem>
+</varlistentry>
+</variablelist>
+</listitem>
+</varlistentry>
+</variablelist>
+
+</sect1>
+
+</chapter>
+<!--
+Local Variables:
+mode: sgml
+sgml-omittag:nil
+sgml-shorttag:t
+sgml-namecase-general:t
+sgml-general-insert-case:lower
+sgml-minimize-attributes:nil
+sgml-always-quote-attributes:t
+sgml-indent-step:0
+sgml-indent-data:nil
+sgml-parent-document:("index.docbook" "book" "chapter")
+End:
+-->
\ No newline at end of file
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/staff.docbook b/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/staff.docbook
new file mode 100644
index 00000000000..ae37ce0d813
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/staff.docbook
@@ -0,0 +1,151 @@
+<chapter id="docu-staff">
+<title
+>Epilogue </title>
+
+<epigraph>
+<attribution
+>The end of Evita</attribution>
+<para
+>She had her moments, she had some style, the best show in town was the crowd, outside the Casa Rosada crying 'Eva Peron'; but that's all gone now...</para
+></epigraph>
+
+<para
+>We hope that you found this documentation useful, informative and perhaps even entertaining. The following things are not necessary to understand the KDE Desktop Environment, but you still may want to read it. </para>
+
+<sect1 id="the-k-documentation-staff">
+<title
+>The K Documentation Staff </title>
+
+<para
+>This User Guide has been updated for 3.0, and is currently maintained by Lauri Watts <email
+>lauri@kde.org</email
+></para>
+
+<para
+>Others who have contributed to this guide.</para>
+<itemizedlist>
+<listitem
+><para
+>Pablo de Vicente <email
+>vicente@oan.es</email
+>, who updated the section regarding installing on Debian for KDE 2.0</para
+></listitem>
+<listitem
+><para
+>Andreas Buschka <email
+>andi@circe.tops.net</email
+></para
+></listitem>
+<listitem
+><para
+>Robert D. Williams <email
+>rwilliam@kde.org</email
+></para
+></listitem>
+<listitem
+><para
+>Poul Gerhard</para
+></listitem>
+<listitem
+><para
+>John Waalkes</para
+></listitem>
+<listitem
+><para
+>Vernon Wells</para
+></listitem>
+<listitem
+><para
+>Kay Lutz</para
+></listitem>
+<listitem
+><para
+>Stephan Kulow</para
+></listitem>
+</itemizedlist>
+</sect1>
+
+<sect1 id="we-still-need-people">
+<title
+>We still need people! </title>
+
+<para
+>KDE is a huge project, and every KDE supporter has already realised that. All of us are trying very hard to create a user interface that is easy to use and maybe also has the potential to make UNIX ready for the desktop PC. You have the chance to participate in this project too, and we would be thankful if you did. Developers and interested users communicate via several mailing lists described in <xref linkend="mailing-lists"/>. If you would like to help, please do so! We are still looking for helpers in the following departments: </para>
+
+<itemizedlist>
+<listitem
+><para
+>Development (Libraries and Applications)</para
+></listitem>
+<listitem
+><para
+>Documentation</para
+></listitem>
+<listitem
+><para
+>Graphics</para
+></listitem>
+<listitem
+><para
+>Beta-Testing</para
+></listitem>
+<listitem
+><para
+>and everywhere else, too :-) </para
+></listitem>
+</itemizedlist>
+
+</sect1>
+
+<sect1 id="legal-notices">
+<title
+>Legal notices </title>
+
+<para
+>This document contains copyrighted material from Andreas Buschka, Gerhard Poul and Robert David Williams. All trademarks and branded names mentioned are properties of their legal owners. </para>
+
+</sect1>
+
+<sect1 id="sources-of-information-used-during-the-creat">
+<title
+>Sources of information used during the creation of this book </title>
+
+<para
+>During the creation of this documentation, the authors used the following sources for information: </para>
+
+<itemizedlist>
+<listitem
+><para
+>The KDE Mailing lists </para
+></listitem>
+<listitem
+><para
+>Various <filename
+>README</filename
+> and <abbrev
+>HTML</abbrev
+> help files that came with the KDE components </para
+></listitem>
+</itemizedlist>
+
+</sect1>
+
+<sect1 id="license">
+<title
+>Licence</title>
+&underGPL; </sect1>
+</chapter>
+<!--
+Local Variables:
+mode: sgml
+sgml-omittag:nil
+sgml-shorttag:t
+sgml-namecase-general:t
+sgml-general-insert-case:lower
+sgml-minimize-attributes:nil
+sgml-always-quote-attributes:t
+sgml-indent-step:0
+sgml-indent-data:nil
+sgml-parent-document:("index.docbook" "book" "chapter")
+End:
+-->
\ No newline at end of file
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/tdeadmin-apps.docbook b/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/tdeadmin-apps.docbook
new file mode 100644
index 00000000000..6adceba32b4
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/tdeadmin-apps.docbook
@@ -0,0 +1,81 @@
+<chapter id="tdeadmin-applications">
+<title
+>tdeadmin applications</title>
+
+<para
+>You can get the following applications in the tdeadmin distributions.</para>
+
+<para
+>Stable applications are relatively bug free and come in source and binary formats.</para>
+
+<para
+><ulink url="ftp://ftp.kde.org/pub/kde/stable/latest/distribution/"
+>ftp.kde.org/pub/kde/stable/latest/distribution/stable</ulink
+></para>
+
+<para
+>Unstable versions change daily and are only in source form, meaning you must compile them to get a working version. Remember these are unstable and might not even compile. If you have a problem with an unstable application report the problem and it will most likely be fixed in a future snapshot.</para
+> <para
+><ulink url="ftp://ftp.kde.org/pub/kde/unstable/CVS/snapshots/current/"
+>ftp.kde.org/pub/kde/unstable/CVS/snapshots/current</ulink
+></para>
+
+<variablelist
+> <varlistentry
+> <term
+>&kcron;</term
+> <listitem
+><para
+>&kde; puts a pretty and user friendly face on the task scheduling capabilities of <application
+>Cron</application
+></para
+></listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&kuser;</term
+> <listitem
+><para
+>A graphical user manager (requires <systemitem class="username"
+>root</systemitem
+> privileges to run)</para
+></listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&kpackage;</term
+> <listitem
+><para
+>Keep your system up to date with &kde;'s own package manager.</para
+></listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&kdat;</term
+> <listitem
+><para
+>A backup utility for tape drive owners.</para
+></listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&ksysv;</term
+> <listitem
+><para
+>A SysV-Init editor, to keep your computer's start up organised.</para
+></listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&kwuftpd;</term
+> <listitem
+><para
+>A graphical interface to configure the <application
+>wuftpd</application
+> &FTP; daemon.</para
+></listitem
+> </varlistentry
+> </variablelist>
+
+</chapter>
+
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/tdebase-apps.docbook b/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/tdebase-apps.docbook
new file mode 100644
index 00000000000..c5f181e5b0b
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/tdebase-apps.docbook
@@ -0,0 +1,173 @@
+<chapter id="tdebase-applications">
+<title
+>tdebase applications</title>
+
+<para
+>You can get the following applications in the tdebase distributions.</para>
+
+<para
+>Stable applications are relatively bug free and come in source and binary formats.</para>
+
+<para
+><ulink url="ftp://ftp.kde.org/pub/kde/stable/latest/distribution/"
+>ftp.kde.org/pub/kde/stable/latest/distribution/stable</ulink
+></para>
+
+<para
+>Unstable versions change daily and are only in source form, meaning you must compile them to get a working version. Remember these are unstable and might not even compile. If you have a problem with an unstable application, report the problem and it will most likely be fixed in a future snapshot.</para>
+<para
+><ulink url="ftp://ftp.kde.org/pub/kde/unstable/CVS/snapshots/current/"
+>ftp.kde.org/pub/kde/unstable/CVS/snapshots/current</ulink
+></para>
+
+<variablelist
+> <varlistentry
+> <term
+>&twin;</term
+> <listitem
+><para
+>&kde;'s own window manager</para
+></listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&konqueror;</term
+> <listitem
+><para
+>Browse the web, your hard drive or an &FTP; site with equal ease.</para
+></listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&kicker;</term
+> <listitem
+><para
+>The &kde; panel, incorporating the taskbar, pager, clock and the <guimenu
+>K</guimenu
+> menu.</para
+></listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&konsole;</term
+> <listitem
+><para
+>A highly configurable X terminal emulator.</para
+></listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&kate;</term
+> <listitem
+><para
+>A powerful and fully featured text editor, with syntax highlighting, project management, and much more.</para
+> </listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&kwrite;</term
+> <listitem
+><para
+>A lighterweight text editor, still with full syntax highlighting and many features.</para
+> </listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&klipper;</term
+> <listitem
+><para
+>A clipboard utility with a difference - you can configure different actions based on things you copy.</para
+></listitem
+> </varlistentry
+> <varlistentry
+> <term
+><application
+>KDesktop</application
+></term
+> <listitem
+><para
+>The desktop itself.</para
+></listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&khelpcenter;</term
+> <listitem
+><para
+>&kde;'s own help centre, including the ability to browse man and info pages.</para
+></listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&kdm;</term
+> <listitem
+><para
+>&kde;'s login manager</para
+></listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&kcontrol;</term
+> <listitem
+><para
+>The Control Panel. Almost everything you can configure in &kde; can be configured from here - and almost everything in &kde; can be configured to your taste.</para
+></listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&kwrite;</term
+> <listitem
+><para
+>A highly configurable text editor, with syntax highlighting.</para
+></listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&kappfinder;</term
+> <listitem
+><para
+>A utility to add non-&kde; applications to your <guimenu
+>K</guimenu
+> menu, to avoid having to do it manually.</para
+></listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&kscreensaver;</term
+> <listitem
+><para
+>Everyone loves a screensaver, and &kde; comes with a generous helping.</para
+></listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&ksysguard;</term
+> <listitem
+><para
+>A network enabled system monitor, incorporating the added functionality of <application
+>top</application
+></para
+></listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&ktip;</term
+> <listitem
+><para
+>Kandalf the wizard is on hand with handy hints, and interesting info.</para
+></listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&kmenuedit;</term
+> <listitem
+><para
+>Rearrange or add to your <guimenu
+>K</guimenu
+> menu with this utility.</para
+></listitem
+> </varlistentry
+> </variablelist>
+
+</chapter>
+
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/tdeedu-apps.docbook b/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/tdeedu-apps.docbook
new file mode 100644
index 00000000000..26665c88699
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/tdeedu-apps.docbook
@@ -0,0 +1,86 @@
+<chapter id="edutainment-apps">
+<title
+>tdeedu applications</title>
+
+<para
+>You can get the following applications in the tdeedu distributions.</para>
+
+<para
+>Stable applications are relatively bug free and come in source and binary formats.</para>
+
+<para
+><ulink url="ftp://ftp.kde.org/pub/kde/stable/latest/distribution/"
+>ftp.kde.org/pub/kde/stable/latest/distribution/stable</ulink
+></para>
+
+<para
+>Unstable versions change daily and are only in source form, meaning you must compile them to get a working version. Remember these are unstable and might not even compile. If you have a problem with an unstable application, report the problem and it will most likely be fixed in a future snapshot.</para>
+<para
+><ulink url="ftp://ftp.kde.org/pub/kde/unstable/CVS/snapshots/current/"
+>ftp.kde.org/pub/kde/unstable/CVS/snapshots/current</ulink
+></para>
+
+<variablelist
+> <varlistentry
+> <term
+>&klettres;</term
+> <listitem
+> <para
+> Very small children can learn the alphabet, using audio and/or visual cues. </para
+> </listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&kmessedwords;</term
+> <listitem
+> <para
+> A simple mind-training game, in which you have to <quote
+>figure out</quote
+> the word that has been given in the program. </para
+> </listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&ktouch;</term
+> <listitem
+> <para
+> A program to help you learn to touch type. </para
+> </listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&keduca;</term
+> <listitem
+> <para
+> An educational project to allow the creation and revision of form based tests/exams. </para
+> </listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&kstars;</term
+> <listitem
+> <para
+>Put a planetarium on your desktop. &kstars; contains a huge amount of reference material, and includes the ability to download photographs of items you see in the heavens.</para
+> </listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&kgeo;</term
+> <listitem
+> <para
+>Even geometry is fun with &kgeo;.</para
+> </listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&kvoctrain;</term
+> <listitem
+> <para
+>Learning another language is easier with &kvoctrain; to practise and expand your vocabulary.</para
+> </listitem
+> </varlistentry
+> </variablelist>
+
+</chapter>
+
+
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/tdegames-apps.docbook b/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/tdegames-apps.docbook
new file mode 100644
index 00000000000..2aa66a4cc65
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/tdegames-apps.docbook
@@ -0,0 +1,203 @@
+<chapter id="entertainment-applications">
+<title
+>Entertainment Applications</title>
+
+<para
+>You can get the following applications in the tdegames distributions.</para>
+
+<para
+>Stable applications are relatively bug free and come in source and binary formats.</para>
+
+<para
+><ulink url="ftp://ftp.kde.org/pub/kde/stable/latest/distribution/"
+>ftp.kde.org/pub/kde/stable/latest/distribution/stable</ulink
+></para>
+<para
+>Unstable versions change daily and are only in source form, meaning you must compile them to get a working version. Remember these are unstable and might not even compile. If you have a problem with an unstable application, report the problem and it will most likely be fixed in a future snapshot.</para
+> <para
+><ulink url="ftp://ftp.kde.org/pub/kde/unstable/CVS/snapshots/current/"
+>ftp.kde.org/pub/kde/unstable/CVS/snapshots/current</ulink
+></para>
+
+<variablelist
+> <varlistentry
+> <term
+>&kenolaba;</term
+> <listitem
+><para
+>A Network enabled board game you can play against the computer or against another player on your network.</para
+></listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&kasteroids;</term
+> <listitem
+><para
+> A little space shoot-em-up. </para
+></listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&katomic;</term
+> <listitem
+><para
+> A perplexing little logic puzzle game, where you get to build your own molecules. </para
+></listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&kblackbox;</term
+> <listitem
+><para
+> A &kde; rewrite of the classic <application
+>Emacs</application
+> blackbox game. </para
+></listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&kbackgammon;</term
+> <listitem
+><para
+> Backgammon, the &kde; way. </para
+></listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&kjumpingcube;</term
+> <listitem
+><para
+> A tactical one or two player game that's harder than it looks. </para
+></listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&kmahjongg;</term
+> <listitem
+><para
+> The classic tile matching game. </para
+></listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&kmines;</term
+> <listitem
+><para
+> Find the mines without making them explode. </para
+></listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&konquest;</term
+> <listitem
+><para
+> Expand your interstellar empire across the galaxy and of course, crush your rivals in the process. </para
+></listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&kpat;</term
+> <listitem
+><para
+> No computer is complete without Patience. </para
+></listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&kpoker;</term
+> <listitem
+><para
+> A &kde; version of those addictive one armed bandits. </para
+></listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&kreversi;</term
+> <listitem
+><para
+> A &kde; version of the classic game. </para
+></listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&ksame;</term
+> <listitem
+><para
+> Addictive little logic game. </para
+></listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&kshisen;</term
+> <listitem
+><para
+> Another tile matching game. </para
+></listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&ksirtet;</term
+> <listitem
+><para
+> Play either a version of Tetris, or the well known (in Japan) game Puyo-Puyo. </para
+></listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&ksmiletris;</term
+> <listitem
+><para
+> A slightly different from the norm Tetris clone. </para
+></listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&ksnake;</term
+> <listitem
+><para
+> The classic nibbles game gets an update and a speed boost. </para
+></listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&ksokoban;</term
+> <listitem
+><para
+> Push those crates to get where you need to go. </para
+></listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&kspaceduel;</term
+> <listitem
+><para
+> Shoot your enemy down, in a challenging two player arcade game. </para
+></listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&ktron;</term
+> <listitem
+><para
+> Classic keep-away - keep away from your foe, the walls, and your own tail. </para
+></listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&ktuberling;</term
+> <listitem
+><para
+> One for the little ones, who could resist the potato guy? </para
+></listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&lskat;</term
+> <listitem
+><para
+> A tricky card game </para
+></listitem
+> </varlistentry
+> </variablelist>
+</chapter>
+
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/tdegraphics-apps.docbook b/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/tdegraphics-apps.docbook
new file mode 100644
index 00000000000..859a07b4f28
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/tdegraphics-apps.docbook
@@ -0,0 +1,95 @@
+<chapter id="graphical-applications">
+<title
+>Graphical Applications</title>
+
+<para
+>You can get the following applications in the tdegraphics distributions.</para>
+
+<para
+>Stable applications are relatively bug free and come in source and binary formats.</para>
+
+<para
+><ulink url="ftp://ftp.kde.org/pub/kde/stable/latest/distribution/"
+>ftp.kde.org/pub/kde/stable/latest/distribution/stable</ulink
+></para>
+
+<para
+>Unstable versions change daily and are only in source form, meaning you must compile them to get a working version. Remember these are unstable and might not even compile. If you have a problem with an unstable application, report the problem and it will most likely be fixed in a future snapshot.</para>
+<para
+><ulink url="ftp://ftp.kde.org/pub/kde/unstable/CVS/snapshots/current/"
+>ftp.kde.org/pub/kde/unstable/CVS/snapshots/current</ulink
+></para>
+
+<variablelist
+> <varlistentry
+> <term
+>&kuickshow;</term
+> <listitem
+> <para
+>A fast and powerful image viewer</para
+> </listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&ksnapshot;</term
+> <listitem
+><para
+> A utility to grab screenshots. </para
+></listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&kfract;</term
+> <listitem
+><para
+> A little fractal generator </para
+></listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&kview;</term
+> <listitem
+><para
+> A powerful image viewer, capable of handling a multitude of formats. </para
+></listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&kghostview;</term
+> <listitem
+><para
+> &kde;'s own &PostScript; viewer. </para
+></listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&kfax; and <application
+>KViewFax</application
+></term
+> <listitem
+><para
+> Utilities to view and handle facsimile images. </para
+></listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&kdvi;</term
+> <listitem
+><para
+> A &DVI; viewer. </para
+></listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&kruler;</term
+> <listitem
+> <para
+>A screen ruler, very useful for working with images or <acronym
+>HTML</acronym
+> pages.</para
+> </listitem
+> </varlistentry
+> </variablelist>
+
+</chapter>
+
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/tdemultimedia-apps.docbook b/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/tdemultimedia-apps.docbook
new file mode 100644
index 00000000000..d1fae7f49c5
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/tdemultimedia-apps.docbook
@@ -0,0 +1,88 @@
+<chapter id="multimedia-applications">
+<title
+>Multimedia Applications</title>
+
+<para
+>You can get the following applications in the tdemultimedia distributions.</para>
+
+<para
+>Stable applications are relatively bug free and come in source and binary formats.</para>
+
+<para
+><ulink url="ftp://ftp.kde.org/pub/kde/stable/latest/distribution/"
+>ftp.kde.org/pub/kde/stable/latest/distribution/stable</ulink
+></para>
+
+<para
+>Unstable versions change daily and are only in source form, meaning you must compile them to get a working version. Remember these are unstable and might not even compile. If you have a problem with an unstable application, report the problem and it will most likely be fixed in a future snapshot.</para>
+
+<para
+><ulink url="ftp://ftp.kde.org/pub/kde/unstable/CVS/snapshots/current/"
+>ftp.kde.org/pub/kde/unstable/CVS/snapshots/current</ulink
+></para>
+
+<variablelist
+> <varlistentry
+> <term
+>&kmix;</term
+> <listitem
+><para
+>A sound mixer panel</para
+></listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&aktion;</term
+> <listitem
+><para
+>A player for movies and animations, with support for many formats.</para
+></listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&noatun;</term
+> <listitem
+><para
+>A Media player for multimedia files, with support for many formats, playlists, and even videos.</para
+></listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&kaboodle;</term
+> <listitem
+> <para
+>A light, versatile, one-shot &arts; media player - no playlists, no fancy features to slow it down, just quickly play a single file.</para
+> </listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&kscd;</term
+> <listitem
+><para
+>A &CD; Player for &kde;, with <acronym
+>CDDB</acronym
+> support.</para
+></listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&kmid;</term
+> <listitem
+><para
+> A MIDI player with support for lyrics.. your very own Karaoke machine! </para
+></listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&kmidi;</term
+> <listitem
+><para
+> A nice sounding but somewhat <acronym
+>CPU</acronym
+> intensive MIDI player </para
+></listitem
+> </varlistentry
+> </variablelist>
+
+</chapter>
+
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/tdenetwork-apps.docbook b/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/tdenetwork-apps.docbook
new file mode 100644
index 00000000000..1aa759bdbdd
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/tdenetwork-apps.docbook
@@ -0,0 +1,86 @@
+<chapter id="network-applications">
+<title
+>Network Applications </title>
+
+<para
+>You can get the following applications in the tdenetwork distributions.</para>
+
+<para
+>Stable applications are relatively bug free and come in source and binary formats.</para>
+<para
+><ulink url="ftp://ftp.kde.org/pub/kde/stable/latest/distribution/"
+>ftp.kde.org/pub/kde/stable/latest/distribution/stable</ulink
+> </para>
+<para
+>Unstable versions change daily and are only in source form, meaning you must compile them to get a working version. Remember these are unstable and might not even compile. If you have a problem with an unstable application, report the problem and it will most likely be fixed in a future snapshot.</para>
+<para
+><ulink url="ftp://ftp.kde.org/pub/kde/unstable/CVS/snapshots/current/"
+>ftp.kde.org/pub/kde/unstable/CVS/snapshots/current</ulink
+></para>
+
+<variablelist
+> <varlistentry
+> <term
+>&kmail;</term
+> <listitem
+><para
+>A fully featured email client, allowing multiple servers and multiple identities.</para
+></listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&knode;</term
+> <listitem
+><para
+>A powerful usenet news client, with support for multiple NNTP servers.</para
+></listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&kit;</term
+> <listitem
+><para
+>An AOL Instant Messenger client, using the <abbrev
+>TOC</abbrev
+> protocol.</para
+></listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&ksirc;</term
+> <listitem
+><para
+>An IRC Client</para
+></listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&korn;</term
+> <listitem
+><para
+>A Biff applet. <application
+>Korn</application
+> checks for new mail and tells you when there is mail to download from your server(s).</para
+></listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&kppp;</term
+> <listitem
+><para
+>An Internet dialer.</para
+></listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&ktalkd;</term
+> <listitem
+><para
+> Users on your network using the classic <command
+>talk</command
+> can still get your attention even in &kde; using &ktalkd;. </para
+></listitem
+> </varlistentry
+> </variablelist>
+</chapter>
+
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/tdepim-apps.docbook b/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/tdepim-apps.docbook
new file mode 100644
index 00000000000..367b269d1bd
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/tdepim-apps.docbook
@@ -0,0 +1,50 @@
+<chapter id="tdepim-applications">
+<title
+>tdepim applications</title>
+
+<para
+>You can get the following applications in the tdepim distributions.</para>
+
+<para
+>Stable applications are relatively bug free and come in source and binary formats.</para>
+
+<para
+><ulink url="ftp://ftp.kde.org/pub/kde/stable/latest/distribution/"
+>ftp.kde.org/pub/kde/stable/latest/distribution/stable</ulink
+></para>
+
+<para
+>Unstable versions change daily and are only in source form, meaning you must compile them to get a working version. Remember these are unstable and might not even compile. If you have a problem with an unstable application, report the problem and it will most likely be fixed in a future snapshot.</para>
+<para
+><ulink url="ftp://ftp.kde.org/pub/kde/unstable/CVS/snapshots/current/"
+>ftp.kde.org/pub/kde/unstable/CVS/snapshots/current</ulink
+></para>
+
+<variablelist
+> <varlistentry
+> <term
+>&korganizer;</term
+> <listitem
+><para
+>Organise your time with this handy calendar, diary, and task scheduler.</para
+></listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&kpilot;</term
+> <listitem
+><para
+>A utility to synchronise your &PalmPilot; with your pc.</para
+></listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&kalarm; and &kalarmd;</term
+> <listitem
+> <para
+>A daemon to watch your calendar for appointments, and the client to make sure you don't miss them.</para
+> </listitem
+> </varlistentry
+> </variablelist>
+</chapter>
+
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/tdetoys-apps.docbook b/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/tdetoys-apps.docbook
new file mode 100644
index 00000000000..45546f19c2b
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/tdetoys-apps.docbook
@@ -0,0 +1,110 @@
+<chapter id="toys-apps">
+<title
+>&kde; Toys</title>
+
+<para
+>You can get the following applications in the tdetoys distributions.</para>
+
+<para
+>Stable applications are relatively bug free and come in source and binary formats.</para>
+
+<para
+><ulink url="ftp://ftp.kde.org/pub/kde/stable/latest/distribution/"
+>ftp.kde.org/pub/kde/stable/latest/distribution/stable</ulink
+></para>
+
+<para
+>Unstable versions change daily and are only in source form, meaning you must compile them to get a working version. Remember these are unstable and might not even compile. If you have a problem with an unstable application, report the problem and it will most likely be fixed in a future snapshot.</para>
+<para
+><ulink url="ftp://ftp.kde.org/pub/kde/unstable/CVS/snapshots/current/"
+>ftp.kde.org/pub/kde/unstable/CVS/snapshots/current</ulink
+></para>
+
+<variablelist
+> <varlistentry
+> <term
+><application
+>fifteenapplet</application
+> and <application
+>eyesapplet</application
+></term
+> <listitem
+> <para
+>Some little applets to put the fifteen game and some spooky eyes on your panel.</para
+> </listitem
+> </varlistentry
+> <varlistentry
+> <term
+><application
+>KAphorism</application
+></term
+> <listitem
+> <para
+>Words of wisdom, based on the date.</para
+> </listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&kmoon;</term
+> <listitem
+> <para
+> Put the moon in your panel, and keep up with it's phases. </para
+> </listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&kodo;</term
+> <listitem
+> <para
+>Ever wondered how far your mouse travels in a day? Wonder no more.</para
+> </listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&kscore;</term
+> <listitem
+> <para
+>Sports fans can keep up with the latest scores for their favourite team with &kscore;.</para
+> </listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&kteatime;</term
+> <listitem
+> <para
+>The one application no &kde; developer would be without, it reminds you when the beverage that fuels &kde; is ready to drink.</para
+> </listitem
+> </varlistentry
+> <varlistentry
+> <term
+><application
+>KWeather</application
+></term
+> <listitem
+> <para
+>Get up to date weather forecasts from your nearest weather station, no matter where you are in the world. Or maybe keep an eye on your next holiday destination.</para
+> </listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&kworldclock;</term
+> <listitem
+> <para
+>Watch as time marches across the world with this nifty applet.</para
+> </listitem
+> </varlistentry
+> <varlistentry
+> <term
+><application
+>KTux</application
+></term
+> <listitem
+> <para
+>The &Linux; penguin Tux takes to space in this screensaver.</para
+> </listitem
+> </varlistentry
+> </variablelist>
+
+</chapter>
+
+
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/tdeutils-apps.docbook b/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/tdeutils-apps.docbook
new file mode 100644
index 00000000000..62ccb552417
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/tdeutils-apps.docbook
@@ -0,0 +1,144 @@
+<chapter id="utility-applications">
+<title
+>Utility Applications</title>
+<para
+>You can get the following applications in the tdeutils distributions.</para>
+
+<para
+>Stable applications are relatively bug free and come in source and binary formats.</para>
+
+<para
+><ulink url="ftp://ftp.kde.org/pub/kde/stable/latest/distribution/"
+>ftp.kde.org/pub/kde/stable/latest/distribution/stable</ulink
+></para>
+
+<para
+>Unstable versions change daily and are only in source form, meaning you must compile them to get a working version. Remember these are unstable and might not even compile. If you have a problem with an unstable application, report the problem and it will most likely be fixed in a future snapshot.</para>
+<para
+><ulink url="ftp://ftp.kde.org/pub/kde/unstable/CVS/snapshots/current/"
+>ftp.kde.org/pub/kde/unstable/CVS/snapshots/current</ulink
+></para>
+
+<variablelist
+> <varlistentry
+> <term
+>&kcharselect;</term
+> <listitem
+><para
+>Character selector (shows all characters available in a given font, including those you don't have keys on your keyboard for)</para
+> </listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&kdepasswd;</term
+> <listitem
+><para
+>A &kde; front end to the &UNIX; <command
+>passwd</command
+> command.</para
+> </listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&kdessh;</term
+> <listitem
+><para
+>A &kde; front end to <command
+>ssh</command
+>. </para
+> </listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&kdf;</term
+> <listitem
+><para
+>A &kde; front end to the <command
+>df</command
+> utility, with added functionality</para
+> </listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&kfloppy;</term
+> <listitem
+><para
+>A floppy formatter</para
+> </listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&kedit;</term
+> <listitem
+><para
+>A small, simple editor, just like the well-known Notepad. It is suitable for small editing tasks, or as a simple textfile browser. </para
+> </listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&karm;</term
+> <listitem
+><para
+>A time tracker. You can enter a list of <quote
+>tasks</quote
+>, start &karm;'s clock, and it will count the number of minutes you spend on the highlighted task.</para
+> </listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&khexedit;</term
+> <listitem
+><para
+>A fully featured Hex Editor</para
+> </listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&kjots;</term
+> <listitem
+><para
+>A small note taker program.</para
+> </listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&klaptopdaemon;</term
+> <listitem
+><para
+>Provides battery monitoring and management for laptops</para
+> </listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&kljettool;</term
+> <listitem
+><para
+>An &HP; LaserJet Control Panel</para
+> </listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&klpq;</term
+> <listitem
+><para
+>&klpq; is a frontend to <application
+>lpq</application
+>, <application
+>lprm</application
+> and <application
+>lpc</application
+>. </para
+> </listitem
+> </varlistentry
+> <varlistentry
+> <term
+>&knotes;</term
+> <listitem
+><para
+>A useable and good looking notes utility.</para
+> </listitem
+> </varlistentry
+> </variablelist>
+
+</chapter>
+
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/ug-faq.docbook b/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/ug-faq.docbook
new file mode 100644
index 00000000000..9a94f503c70
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/userguide/ug-faq.docbook
@@ -0,0 +1,129 @@
+<chapter id="frequently-asked-questions">
+<title
+>Frequently Asked Questions About &kde; </title>
+
+<epigraph>
+<attribution
+>Batman Animated Series</attribution>
+<para
+>What are you?</para>
+<para
+>I'm your worst nightmare...</para>
+</epigraph>
+
+<para
+>There are some questions that are always raised on the &kde; mailing lists. To keep the traffic as low as possible (making the lists more readable), we have included them in this section. So please be kind and do not ask them in the mailing lists anymore - think of the quote above! </para>
+
+<!-- pretty short list.. going to watch mailing lists a little, and
+see if there aren't any more questions that ought to be here -->
+
+<qandaset id="faq">
+<qandaentry>
+<question
+><para
+>What does <quote
+>&kde;</quote
+> stand for?</para
+></question>
+<answer
+><para
+>Originally the <emphasis
+>K</emphasis
+> stood for <emphasis
+>Kool</emphasis
+>, nowadays the K has no meaning and &kde; simply stands for the <emphasis
+>K Desktop Environment</emphasis
+>. &kde; is intended to be a collection of small tools, a window manager, a file manager and tools that bring all this together. It is created to make your life with &UNIX; easier. </para
+></answer>
+</qandaentry>
+
+<qandaentry>
+<question
+><para
+>I cannot compile package xxx</para
+></question>
+<answer>
+
+<para
+>Always be sure that you have the newest version of the &kde; libraries installed. The software is in constant development, so the dependencies can change from one day to another if you are using <acronym
+>CVS</acronym
+>. For most users, using a released version is much more practical.</para>
+
+<para
+>Another problem could be that you are using a program written for a very old version of &kde;, which depends on outdated include files. Check in the source archive's <filename
+>README</filename
+> to see if it explains which version of &kde; the application is looking for. If that file doesn't exist, check the file dates. They should be more recent than your current &kde; version.</para>
+</answer>
+</qandaentry>
+
+<qandaentry
+> 
+
+<question
+><para
+>What version of &kde; should I use for a stable desktop?</para
+></question>
+<answer
+><para
+>One can, in general, obtain &kde; in many ways. Obtaining pre-compiled binaries in a package format (rpm,deb,tgz) labeled with a particular version (&eg; 3.2) is the best way to encourage stability on your &kde; desktop.</para>
+
+</answer>
+</qandaentry>
+
+<qandaentry
+> 
+<question
+><para
+>But I heard that my problem/wishlist item is <quote
+>already in <acronym
+>CVS</acronym
+></quote
+>. I want to get my hands on the new features, why shouldn't I try <acronym
+>CVS</acronym
+>?</para
+></question>
+
+<answer>
+<para
+>The price of stability is that one must wait for each release to get new features. Conversely the price of being the first to see new features, is that you risk stability. &kde; has a fairly frequent release schedule, and stability of released versions is a particular focus. For the majority of &kde; users, unless you are planning to help develop &kde;, there is little advantage to running development versions of &kde;.</para>
+
+<para
+>However, there is always a place for experienced users who know what they are letting themselves in for, and are willing to report bugs found. If this is you, then there is no reason not to try the <acronym
+>CVS</acronym
+> versions. Be prepared for things to break occasionally, <acronym
+>CVS</acronym
+> gives you a snapshot of source code that is currently being worked on.</para>
+
+<para
+>These are daily snapshots of whatever the developers are working on, and some things are guaranteed to be broken.</para
+> 
+
+<warning>
+<para
+><emphasis
+>Do not rely on <acronym
+>CVS</acronym
+> snapshots to maintain operational desktops</emphasis
+>. You will get burned eventually!</para>
+</warning>
+
+</answer>
+
+</qandaentry>
+</qandaset>
+
+</chapter>
+<!--
+Local Variables:
+mode: sgml
+sgml-omittag:nil
+sgml-shorttag:t
+sgml-namecase-general:t
+sgml-general-insert-case:lower
+sgml-minimize-attributes:nil
+sgml-always-quote-attributes:t
+sgml-indent-step:0
+sgml-indent-data:nil
+sgml-parent-document:("index.docbook" "book" "chapter")
+End:
+-->
\ No newline at end of file
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/visualdict/Makefile.am b/tde-i18n-en_GB/docs/tdebase/khelpcenter/visualdict/Makefile.am
new file mode 100644
index 00000000000..f2bfec833e0
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/visualdict/Makefile.am
@@ -0,0 +1,4 @@
+KDE_LANG = en_GB
+SUBDIRS = $(AUTODIRS)
+KDE_DOCS = khelpcenter/visualdict
+KDE_MANS = AUTO
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/visualdict/Makefile.in b/tde-i18n-en_GB/docs/tdebase/khelpcenter/visualdict/Makefile.in
new file mode 100644
index 00000000000..e22fc8a567b
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/visualdict/Makefile.in
@@ -0,0 +1,635 @@
+# Makefile.in generated by automake 1.10.1 from Makefile.am.
+# KDE tags expanded automatically by am_edit - $Revision: 483858 $ 
+# @configure_input@
+
+# Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002,
+# 2003, 2004, 2005, 2006, 2007, 2008  Free Software Foundation, Inc.
+# This Makefile.in is free software; the Free Software Foundation
+# gives unlimited permission to copy and/or distribute it,
+# with or without modifications, as long as this notice is preserved.
+
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY, to the extent permitted by law; without
+# even the implied warranty of MERCHANTABILITY or FITNESS FOR A
+# PARTICULAR PURPOSE.
+
+@SET_MAKE@
+VPATH = @srcdir@
+pkgdatadir = $(datadir)/@PACKAGE@
+pkglibdir = $(libdir)/@PACKAGE@
+pkgincludedir = $(includedir)/@PACKAGE@
+am__cd = CDPATH="$${ZSH_VERSION+.}$(PATH_SEPARATOR)" && cd
+install_sh_DATA = $(install_sh) -c -m 644
+install_sh_PROGRAM = $(install_sh) -c
+install_sh_SCRIPT = $(install_sh) -c
+INSTALL_HEADER = $(INSTALL_DATA)
+transform = $(program_transform_name)
+NORMAL_INSTALL = :
+PRE_INSTALL = :
+POST_INSTALL = :
+NORMAL_UNINSTALL = :
+PRE_UNINSTALL = :
+POST_UNINSTALL = :
+subdir = docs/tdebase/khelpcenter/visualdict
+DIST_COMMON = $(srcdir)/Makefile.am $(srcdir)/Makefile.in
+ACLOCAL_M4 = $(top_srcdir)/aclocal.m4
+am__aclocal_m4_deps = $(top_srcdir)/acinclude.m4 \
+	$(top_srcdir)/configure.in
+am__configure_deps = $(am__aclocal_m4_deps) $(CONFIGURE_DEPENDENCIES) \
+	$(ACLOCAL_M4)
+mkinstalldirs = $(SHELL) $(top_srcdir)/mkinstalldirs
+CONFIG_HEADER = $(top_builddir)/config.h
+CONFIG_CLEAN_FILES =
+SOURCES =
+DIST_SOURCES =
+#>- RECURSIVE_TARGETS = all-recursive check-recursive dvi-recursive \
+#>- 	html-recursive info-recursive install-data-recursive \
+#>- 	install-dvi-recursive install-exec-recursive \
+#>- 	install-html-recursive install-info-recursive \
+#>- 	install-pdf-recursive install-ps-recursive install-recursive \
+#>- 	installcheck-recursive installdirs-recursive pdf-recursive \
+#>- 	ps-recursive uninstall-recursive
+#>+ 7
+RECURSIVE_TARGETS = all-recursive check-recursive dvi-recursive \
+	html-recursive info-recursive install-data-recursive \
+	install-dvi-recursive install-exec-recursive \
+	install-html-recursive install-info-recursive \
+	install-pdf-recursive install-ps-recursive install-recursive \
+	installcheck-recursive installdirs-recursive pdf-recursive \
+	ps-recursive uninstall-recursive nmcheck-recursive bcheck-recursive
+RECURSIVE_CLEAN_TARGETS = mostlyclean-recursive clean-recursive	\
+  distclean-recursive maintainer-clean-recursive
+ETAGS = etags
+CTAGS = ctags
+DIST_SUBDIRS = $(SUBDIRS)
+#>- DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST)
+#>+ 1
+DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST) $(KDE_DIST)
+ACLOCAL = @ACLOCAL@
+AMTAR = @AMTAR@
+ARTSCCONFIG = @ARTSCCONFIG@
+AUTOCONF = @AUTOCONF@
+AUTODIRS = @AUTODIRS@
+AUTOHEADER = @AUTOHEADER@
+AUTOMAKE = @AUTOMAKE@
+AWK = @AWK@
+CONF_FILES = @CONF_FILES@
+CYGPATH_W = @CYGPATH_W@
+DCOPIDL = @DCOPIDL@
+DCOPIDL2CPP = @DCOPIDL2CPP@
+DCOPIDLNG = @DCOPIDLNG@
+DCOP_DEPENDENCIES = @DCOP_DEPENDENCIES@
+DEFS = @DEFS@
+ECHO_C = @ECHO_C@
+ECHO_N = @ECHO_N@
+ECHO_T = @ECHO_T@
+GMSGFMT = @GMSGFMT@
+INSTALL = @INSTALL@
+INSTALL_DATA = @INSTALL_DATA@
+INSTALL_PROGRAM = @INSTALL_PROGRAM@
+INSTALL_SCRIPT = @INSTALL_SCRIPT@
+INSTALL_STRIP_PROGRAM = @INSTALL_STRIP_PROGRAM@
+KCFG_DEPENDENCIES = @KCFG_DEPENDENCIES@
+KCONFIG_COMPILER = @KCONFIG_COMPILER@
+KDECONFIG = @KDECONFIG@
+KDE_EXTRA_RPATH = @KDE_EXTRA_RPATH@
+KDE_RPATH = @KDE_RPATH@
+KDE_XSL_STYLESHEET = @KDE_XSL_STYLESHEET@
+LIBOBJS = @LIBOBJS@
+LIBS = @LIBS@
+LN_S = @LN_S@
+LTLIBOBJS = @LTLIBOBJS@
+MAKEINFO = @MAKEINFO@
+MAKEKDEWIDGETS = @MAKEKDEWIDGETS@
+MCOPIDL = @MCOPIDL@
+MEINPROC = @MEINPROC@
+MKDIR_P = @MKDIR_P@
+MSGFMT = @MSGFMT@
+PACKAGE = @PACKAGE@
+PACKAGE_BUGREPORT = @PACKAGE_BUGREPORT@
+PACKAGE_NAME = @PACKAGE_NAME@
+PACKAGE_STRING = @PACKAGE_STRING@
+PACKAGE_TARNAME = @PACKAGE_TARNAME@
+PACKAGE_VERSION = @PACKAGE_VERSION@
+PATH_SEPARATOR = @PATH_SEPARATOR@
+SET_MAKE = @SET_MAKE@
+SHELL = @SHELL@
+STRIP = @STRIP@
+TOPSUBDIRS = @TOPSUBDIRS@
+VERSION = @VERSION@
+XGETTEXT = @XGETTEXT@
+XMLLINT = @XMLLINT@
+X_RPATH = @X_RPATH@
+abs_builddir = @abs_builddir@
+abs_srcdir = @abs_srcdir@
+abs_top_builddir = @abs_top_builddir@
+abs_top_srcdir = @abs_top_srcdir@
+am__leading_dot = @am__leading_dot@
+am__tar = @am__tar@
+am__untar = @am__untar@
+#>- bindir = @bindir@
+#>+ 2
+DEPDIR = .deps
+bindir = @bindir@
+build_alias = @build_alias@
+builddir = @builddir@
+datadir = @datadir@
+datarootdir = @datarootdir@
+docdir = @docdir@
+dvidir = @dvidir@
+exec_prefix = @exec_prefix@
+host_alias = @host_alias@
+htmldir = @htmldir@
+includedir = @includedir@
+infodir = @infodir@
+install_sh = @install_sh@
+kde_appsdir = @kde_appsdir@
+kde_bindir = @kde_bindir@
+kde_confdir = @kde_confdir@
+kde_datadir = @kde_datadir@
+kde_htmldir = @kde_htmldir@
+kde_icondir = @kde_icondir@
+kde_kcfgdir = @kde_kcfgdir@
+kde_libs_htmldir = @kde_libs_htmldir@
+kde_libs_prefix = @kde_libs_prefix@
+kde_locale = @kde_locale@
+kde_mimedir = @kde_mimedir@
+kde_moduledir = @kde_moduledir@
+kde_servicesdir = @kde_servicesdir@
+kde_servicetypesdir = @kde_servicetypesdir@
+kde_sounddir = @kde_sounddir@
+kde_styledir = @kde_styledir@
+kde_templatesdir = @kde_templatesdir@
+kde_wallpaperdir = @kde_wallpaperdir@
+kde_widgetdir = @kde_widgetdir@
+tdeinitdir = @tdeinitdir@
+libdir = @libdir@
+libexecdir = @libexecdir@
+localedir = @localedir@
+localstatedir = @localstatedir@
+mandir = @mandir@
+mkdir_p = @mkdir_p@
+oldincludedir = @oldincludedir@
+pdfdir = @pdfdir@
+prefix = @prefix@
+program_transform_name = @program_transform_name@
+psdir = @psdir@
+sbindir = @sbindir@
+sharedstatedir = @sharedstatedir@
+srcdir = @srcdir@
+sysconfdir = @sysconfdir@
+target_alias = @target_alias@
+top_builddir = @top_builddir@
+top_srcdir = @top_srcdir@
+xdg_appsdir = @xdg_appsdir@
+xdg_directorydir = @xdg_directorydir@
+xdg_menudir = @xdg_menudir@
+KDE_LANG = en_GB
+#>- SUBDIRS = $(AUTODIRS)
+#>+ 1
+SUBDIRS =.
+KDE_DOCS = khelpcenter/visualdict
+KDE_MANS = AUTO
+#>- all: all-recursive
+#>+ 1
+all: docs-am  all-recursive
+
+.SUFFIXES:
+$(srcdir)/Makefile.in:  $(srcdir)/Makefile.am  $(am__configure_deps)
+#>- 	@for dep in $?; do \
+#>- 	  case '$(am__configure_deps)' in \
+#>- 	    *$$dep*) \
+#>- 	      cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh \
+#>- 		&& exit 0; \
+#>- 	      exit 1;; \
+#>- 	  esac; \
+#>- 	done; \
+#>- 	echo ' cd $(top_srcdir) && $(AUTOMAKE) --gnu  docs/tdebase/khelpcenter/visualdict/Makefile'; \
+#>- 	cd $(top_srcdir) && \
+#>- 	  $(AUTOMAKE) --gnu  docs/tdebase/khelpcenter/visualdict/Makefile
+#>+ 12
+	@for dep in $?; do \
+	  case '$(am__configure_deps)' in \
+	    *$$dep*) \
+	      cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh \
+		&& exit 0; \
+	      exit 1;; \
+	  esac; \
+	done; \
+	echo ' cd $(top_srcdir) && $(AUTOMAKE) --gnu  docs/tdebase/khelpcenter/visualdict/Makefile'; \
+	cd $(top_srcdir) && \
+	  $(AUTOMAKE) --gnu  docs/tdebase/khelpcenter/visualdict/Makefile
+	cd $(top_srcdir) && perl ../scripts/admin/am_edit -p../scripts/admin docs/tdebase/khelpcenter/visualdict/Makefile.in
+.PRECIOUS: Makefile
+Makefile: $(srcdir)/Makefile.in $(top_builddir)/config.status
+	@case '$?' in \
+	  *config.status*) \
+	    cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh;; \
+	  *) \
+	    echo ' cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__depfiles_maybe)'; \
+	    cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__depfiles_maybe);; \
+	esac;
+
+$(top_builddir)/config.status: $(top_srcdir)/configure $(CONFIG_STATUS_DEPENDENCIES)
+	cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
+
+$(top_srcdir)/configure:  $(am__configure_deps)
+	cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
+$(ACLOCAL_M4):  $(am__aclocal_m4_deps)
+	cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
+
+# This directory's subdirectories are mostly independent; you can cd
+# into them and run `make' without going through this Makefile.
+# To change the values of `make' variables: instead of editing Makefiles,
+# (1) if the variable is set in `config.status', edit `config.status'
+#     (which will cause the Makefiles to be regenerated when you run `make');
+# (2) otherwise, pass the desired values on the `make' command line.
+$(RECURSIVE_TARGETS):
+	@failcom='exit 1'; \
+	for f in x $$MAKEFLAGS; do \
+	  case $$f in \
+	    *=* | --[!k]*);; \
+	    *k*) failcom='fail=yes';; \
+	  esac; \
+	done; \
+	dot_seen=no; \
+	target=`echo $@ | sed s/-recursive//`; \
+	list='$(SUBDIRS)'; for subdir in $$list; do \
+	  echo "Making $$target in $$subdir"; \
+	  if test "$$subdir" = "."; then \
+	    dot_seen=yes; \
+	    local_target="$$target-am"; \
+	  else \
+	    local_target="$$target"; \
+	  fi; \
+	  (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS) $$local_target) \
+	  || eval $$failcom; \
+	done; \
+	if test "$$dot_seen" = "no"; then \
+	  $(MAKE) $(AM_MAKEFLAGS) "$$target-am" || exit 1; \
+	fi; test -z "$$fail"
+
+$(RECURSIVE_CLEAN_TARGETS):
+	@failcom='exit 1'; \
+	for f in x $$MAKEFLAGS; do \
+	  case $$f in \
+	    *=* | --[!k]*);; \
+	    *k*) failcom='fail=yes';; \
+	  esac; \
+	done; \
+	dot_seen=no; \
+	case "$@" in \
+	  distclean-* | maintainer-clean-*) list='$(DIST_SUBDIRS)' ;; \
+	  *) list='$(SUBDIRS)' ;; \
+	esac; \
+	rev=''; for subdir in $$list; do \
+	  if test "$$subdir" = "."; then :; else \
+	    rev="$$subdir $$rev"; \
+	  fi; \
+	done; \
+	rev="$$rev ."; \
+	target=`echo $@ | sed s/-recursive//`; \
+	for subdir in $$rev; do \
+	  echo "Making $$target in $$subdir"; \
+	  if test "$$subdir" = "."; then \
+	    local_target="$$target-am"; \
+	  else \
+	    local_target="$$target"; \
+	  fi; \
+	  (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS) $$local_target) \
+	  || eval $$failcom; \
+	done && test -z "$$fail"
+tags-recursive:
+	list='$(SUBDIRS)'; for subdir in $$list; do \
+	  test "$$subdir" = . || (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS) tags); \
+	done
+ctags-recursive:
+	list='$(SUBDIRS)'; for subdir in $$list; do \
+	  test "$$subdir" = . || (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS) ctags); \
+	done
+
+ID: $(HEADERS) $(SOURCES) $(LISP) $(TAGS_FILES)
+	list='$(SOURCES) $(HEADERS) $(LISP) $(TAGS_FILES)'; \
+	unique=`for i in $$list; do \
+	    if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
+	  done | \
+	  $(AWK) '{ files[$$0] = 1; nonemtpy = 1; } \
+	      END { if (nonempty) { for (i in files) print i; }; }'`; \
+	mkid -fID $$unique
+tags: TAGS
+
+TAGS: tags-recursive $(HEADERS) $(SOURCES)  $(TAGS_DEPENDENCIES) \
+		$(TAGS_FILES) $(LISP)
+	tags=; \
+	here=`pwd`; \
+	if ($(ETAGS) --etags-include --version) >/dev/null 2>&1; then \
+	  include_option=--etags-include; \
+	  empty_fix=.; \
+	else \
+	  include_option=--include; \
+	  empty_fix=; \
+	fi; \
+	list='$(SUBDIRS)'; for subdir in $$list; do \
+	  if test "$$subdir" = .; then :; else \
+	    test ! -f $$subdir/TAGS || \
+	      tags="$$tags $$include_option=$$here/$$subdir/TAGS"; \
+	  fi; \
+	done; \
+	list='$(SOURCES) $(HEADERS)  $(LISP) $(TAGS_FILES)'; \
+	unique=`for i in $$list; do \
+	    if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
+	  done | \
+	  $(AWK) '{ files[$$0] = 1; nonempty = 1; } \
+	      END { if (nonempty) { for (i in files) print i; }; }'`; \
+	if test -z "$(ETAGS_ARGS)$$tags$$unique"; then :; else \
+	  test -n "$$unique" || unique=$$empty_fix; \
+	  $(ETAGS) $(ETAGSFLAGS) $(AM_ETAGSFLAGS) $(ETAGS_ARGS) \
+	    $$tags $$unique; \
+	fi
+ctags: CTAGS
+CTAGS: ctags-recursive $(HEADERS) $(SOURCES)  $(TAGS_DEPENDENCIES) \
+		$(TAGS_FILES) $(LISP)
+	tags=; \
+	list='$(SOURCES) $(HEADERS)  $(LISP) $(TAGS_FILES)'; \
+	unique=`for i in $$list; do \
+	    if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
+	  done | \
+	  $(AWK) '{ files[$$0] = 1; nonempty = 1; } \
+	      END { if (nonempty) { for (i in files) print i; }; }'`; \
+	test -z "$(CTAGS_ARGS)$$tags$$unique" \
+	  || $(CTAGS) $(CTAGSFLAGS) $(AM_CTAGSFLAGS) $(CTAGS_ARGS) \
+	     $$tags $$unique
+
+GTAGS:
+	here=`$(am__cd) $(top_builddir) && pwd` \
+	  && cd $(top_srcdir) \
+	  && gtags -i $(GTAGS_ARGS) $$here
+
+distclean-tags:
+	-rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
+
+#>- distdir: $(DISTFILES)
+#>+ 1
+distdir: distdir-nls  $(DISTFILES)
+	@srcdirstrip=`echo "$(srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \
+	topsrcdirstrip=`echo "$(top_srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \
+	list='$(DISTFILES)'; \
+	  dist_files=`for file in $$list; do echo $$file; done | \
+	  sed -e "s|^$$srcdirstrip/||;t" \
+	      -e "s|^$$topsrcdirstrip/|$(top_builddir)/|;t"`; \
+	case $$dist_files in \
+	  */*) $(MKDIR_P) `echo "$$dist_files" | \
+			   sed '/\//!d;s|^|$(distdir)/|;s,/[^/]*$$,,' | \
+			   sort -u` ;; \
+	esac; \
+	for file in $$dist_files; do \
+	  if test -f $$file || test -d $$file; then d=.; else d=$(srcdir); fi; \
+	  if test -d $$d/$$file; then \
+	    dir=`echo "/$$file" | sed -e 's,/[^/]*$$,,'`; \
+	    if test -d $(srcdir)/$$file && test $$d != $(srcdir); then \
+	      cp -pR $(srcdir)/$$file $(distdir)$$dir || exit 1; \
+	    fi; \
+	    cp -pR $$d/$$file $(distdir)$$dir || exit 1; \
+	  else \
+	    test -f $(distdir)/$$file \
+	    || cp -p $$d/$$file $(distdir)/$$file \
+	    || exit 1; \
+	  fi; \
+	done
+	list='$(DIST_SUBDIRS)'; for subdir in $$list; do \
+	  if test "$$subdir" = .; then :; else \
+	    test -d "$(distdir)/$$subdir" \
+	    || $(MKDIR_P) "$(distdir)/$$subdir" \
+	    || exit 1; \
+	    distdir=`$(am__cd) $(distdir) && pwd`; \
+	    top_distdir=`$(am__cd) $(top_distdir) && pwd`; \
+	    (cd $$subdir && \
+	      $(MAKE) $(AM_MAKEFLAGS) \
+	        top_distdir="$$top_distdir" \
+	        distdir="$$distdir/$$subdir" \
+		am__remove_distdir=: \
+		am__skip_length_check=: \
+	        distdir) \
+	      || exit 1; \
+	  fi; \
+	done
+check-am: all-am
+check: check-recursive
+all-am: Makefile
+installdirs: installdirs-recursive
+installdirs-am:
+install: install-recursive
+install-exec: install-exec-recursive
+install-data: install-data-recursive
+#>- uninstall: uninstall-recursive
+#>+ 1
+uninstall: uninstall-docs uninstall-nls  uninstall-recursive
+
+install-am: all-am
+	@$(MAKE) $(AM_MAKEFLAGS) install-exec-am install-data-am
+
+installcheck: installcheck-recursive
+install-strip:
+	$(MAKE) $(AM_MAKEFLAGS) INSTALL_PROGRAM="$(INSTALL_STRIP_PROGRAM)" \
+	  install_sh_PROGRAM="$(INSTALL_STRIP_PROGRAM)" INSTALL_STRIP_FLAG=-s \
+	  `test -z '$(STRIP)' || \
+	    echo "INSTALL_PROGRAM_ENV=STRIPPROG='$(STRIP)'"` install
+mostlyclean-generic:
+
+clean-generic:
+
+distclean-generic:
+	-test -z "$(CONFIG_CLEAN_FILES)" || rm -f $(CONFIG_CLEAN_FILES)
+
+maintainer-clean-generic:
+	@echo "This command is intended for maintainers to use"
+	@echo "it deletes files that may require special tools to rebuild."
+#>- clean: clean-recursive
+#>+ 1
+clean: kde-rpo-clean  clean-recursive
+
+#>- clean-am: clean-generic mostlyclean-am
+#>+ 1
+clean-am: clean-docs clean-bcheck  clean-generic mostlyclean-am
+
+distclean: distclean-recursive
+	-rm -f Makefile
+distclean-am: clean-am distclean-generic distclean-tags
+
+dvi: dvi-recursive
+
+dvi-am:
+
+html: html-recursive
+
+info: info-recursive
+
+info-am:
+
+#>- install-data-am:
+#>+ 1
+install-data-am: install-docs install-nls 
+
+install-dvi: install-dvi-recursive
+
+install-exec-am:
+
+install-html: install-html-recursive
+
+install-info: install-info-recursive
+
+install-man:
+
+install-pdf: install-pdf-recursive
+
+install-ps: install-ps-recursive
+
+installcheck-am:
+
+maintainer-clean: maintainer-clean-recursive
+	-rm -f Makefile
+maintainer-clean-am: distclean-am maintainer-clean-generic
+
+mostlyclean: mostlyclean-recursive
+
+mostlyclean-am: mostlyclean-generic
+
+pdf: pdf-recursive
+
+pdf-am:
+
+ps: ps-recursive
+
+ps-am:
+
+uninstall-am:
+
+.MAKE: $(RECURSIVE_CLEAN_TARGETS) $(RECURSIVE_TARGETS) install-am \
+	install-strip
+
+.PHONY: $(RECURSIVE_CLEAN_TARGETS) $(RECURSIVE_TARGETS) CTAGS GTAGS \
+	all all-am check check-am clean clean-generic ctags \
+	ctags-recursive distclean distclean-generic distclean-tags \
+	distdir dvi dvi-am html html-am info info-am install \
+	install-am install-data install-data-am install-dvi \
+	install-dvi-am install-exec install-exec-am install-html \
+	install-html-am install-info install-info-am install-man \
+	install-pdf install-pdf-am install-ps install-ps-am \
+	install-strip installcheck installcheck-am installdirs \
+	installdirs-am maintainer-clean maintainer-clean-generic \
+	mostlyclean mostlyclean-generic pdf pdf-am ps ps-am tags \
+	tags-recursive uninstall uninstall-am
+
+# Tell versions [3.59,3.63) of GNU make to not export all variables.
+# Otherwise a system limit (for SysV at least) may be exceeded.
+.NOEXPORT:
+
+#>+ 2
+KDE_DIST=Makefile.in index.docbook Makefile.am index.cache.bz2 
+
+#>+ 24
+index.cache.bz2: $(srcdir)/index.docbook $(KDE_XSL_STYLESHEET) index.docbook 
+	@if test -n "$(MEINPROC)"; then echo $(MEINPROC) --check --cache index.cache.bz2 $(srcdir)/index.docbook; $(MEINPROC) --check --cache index.cache.bz2 $(srcdir)/index.docbook; fi
+
+docs-am: index.cache.bz2
+
+install-docs: docs-am install-nls
+	$(mkinstalldirs) $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/visualdict
+	@if test -f index.cache.bz2; then \
+	echo $(INSTALL_DATA) index.cache.bz2 $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/visualdict/; \
+	$(INSTALL_DATA) index.cache.bz2 $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/visualdict/; \
+	elif test -f  $(srcdir)/index.cache.bz2; then \
+	echo $(INSTALL_DATA) $(srcdir)/index.cache.bz2 $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/visualdict/; \
+	$(INSTALL_DATA) $(srcdir)/index.cache.bz2 $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/visualdict/; \
+	fi
+	-rm -f $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/visualdict/common
+	$(LN_S) $(kde_libs_htmldir)/$(KDE_LANG)/common $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/visualdict/common
+
+uninstall-docs:
+	-rm -rf $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/visualdict
+
+clean-docs:
+	-rm -f index.cache.bz2
+
+
+#>+ 13
+install-nls:
+	$(mkinstalldirs) $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/visualdict
+	@for base in index.docbook ; do \
+	  echo $(INSTALL_DATA) $$base $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/visualdict/$$base ;\
+	  $(INSTALL_DATA) $(srcdir)/$$base $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/visualdict/$$base ;\
+	done
+
+uninstall-nls:
+	for base in index.docbook ; do \
+	  rm -f $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/visualdict/$$base ;\
+	done
+
+
+#>+ 5
+distdir-nls:
+	for file in index.docbook ; do \
+	  cp $(srcdir)/$$file $(distdir); \
+	done
+
+#>+ 15
+force-reedit:
+		@for dep in $?; do \
+	  case '$(am__configure_deps)' in \
+	    *$$dep*) \
+	      cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh \
+		&& exit 0; \
+	      exit 1;; \
+	  esac; \
+	done; \
+	echo ' cd $(top_srcdir) && $(AUTOMAKE) --gnu  docs/tdebase/khelpcenter/visualdict/Makefile'; \
+	cd $(top_srcdir) && \
+	  $(AUTOMAKE) --gnu  docs/tdebase/khelpcenter/visualdict/Makefile
+	cd $(top_srcdir) && perl ../scripts/admin/am_edit -p../scripts/admin docs/tdebase/khelpcenter/visualdict/Makefile.in
+
+
+#>+ 21
+clean-bcheck: 
+	rm -f *.bchecktest.cc *.bchecktest.cc.class a.out
+
+bcheck: bcheck-recursive
+
+bcheck-am:
+	@for i in ; do \
+	    if test $(srcdir)/$$i -nt $$i.bchecktest.cc; then \
+	        echo "int main() {return 0;}" > $$i.bchecktest.cc ; \
+	        echo "#include \"$$i\"" >> $$i.bchecktest.cc ; \
+	        echo "$$i"; \
+	        if ! $(CXX) $(DEFS) -I. -I$(srcdir) -I$(top_builddir) $(INCLUDES) $(AM_CPPFLAGS) $(CPPFLAGS) $(CXXFLAGS) $(KDE_CXXFLAGS)  --dump-class-hierarchy -c $$i.bchecktest.cc; then \
+	            rm -f $$i.bchecktest.cc; exit 1; \
+	        fi ; \
+	        echo "" >> $$i.bchecktest.cc.class; \
+	        perl $(top_srcdir)/admin/bcheck.pl $$i.bchecktest.cc.class || { rm -f $$i.bchecktest.cc; exit 1; }; \
+	        rm -f a.out; \
+	    fi ; \
+	done
+
+
+#>+ 3
+final:
+	$(MAKE) all-am
+
+#>+ 3
+final-install:
+	$(MAKE) install-am
+
+#>+ 3
+no-final:
+	$(MAKE) all-am
+
+#>+ 3
+no-final-install:
+	$(MAKE) install-am
+
+#>+ 3
+kde-rpo-clean:
+	-rm -f *.rpo
+
+#>+ 3
+nmcheck: 
+nmcheck-am: nmcheck
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/visualdict/index.cache.bz2 b/tde-i18n-en_GB/docs/tdebase/khelpcenter/visualdict/index.cache.bz2
new file mode 100644
index 00000000000..83943b11833
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/visualdict/index.cache.bz2
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/visualdict/index.docbook b/tde-i18n-en_GB/docs/tdebase/khelpcenter/visualdict/index.docbook
new file mode 100644
index 00000000000..5ad5575f4d1
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/visualdict/index.docbook
@@ -0,0 +1,352 @@
+<?xml version="1.0" ?>
+<!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" 
+"dtd/kdex.dtd" [
+  <!ENTITY kappname "Visual Guide to &kde;">
+  <!ENTITY % addindex "IGNORE">
+  <!ENTITY % British-English "INCLUDE"
+> <!-- change language only here -->
+  
+  
+]>
+
+<book lang="&language;">
+  
+<bookinfo>
+<title
+>The &kde; Visual Guide</title>
+<authorgroup>
+<corpauthor
+>The KDE Team </corpauthor>
+<othercredit role="translator"
+><firstname
+>Malcolm</firstname
+><surname
+>Hunter</surname
+><affiliation
+><address
+><email
+>malcolm.hunter@gmx.co.uk</email
+></address
+></affiliation
+><contrib
+>Conversion to British English</contrib
+></othercredit
+> 
+</authorgroup>
+
+<date
+>2000-10-04</date>
+<releaseinfo
+>2.00.00</releaseinfo>
+
+<copyright>
+<year
+>2000</year>
+<holder
+>The KDE Team</holder>
+</copyright>
+
+<legalnotice
+>&FDLNotice;</legalnotice>
+
+<abstract
+><para
+>A visual guide to &kde;'s interface. This is a very early version of the document. Eventually, this will be a graphical tour of &kde;.</para
+></abstract>
+
+<keywordset>
+<keyword
+>KDE</keyword>
+<keyword
+>Visual</keyword>
+<keyword
+>Dictionary</keyword>
+<keyword
+>Guide</keyword>
+</keywordset>
+
+</bookinfo>
+
+<chapter id="visual-dictionary">
+
+<!-- Translators please note:  If you have already translated the visual -->
+<!-- dictionary on the i18n website, please make sure the translations here -->
+<!-- match that file exactly. -->
+
+<title
+>&kde; Visual Dictionary of terms</title>
+
+<para
+>This project was started to help unify the vocabulary used in &kde; documentation.</para>
+
+<para
+>We provide this for you here as an aid to learning your way around the &kde; Graphical User Interface. These names have been standardised within &kde; documentation, so that you will always find interface items referred to in the same way.</para>
+
+<tip
+><para
+>The term <quote
+>Widget</quote
+> refers to the basic building block of a computer program's interface.</para>
+<para
+>Each widget operates in a similar manner each time it is used, but the effect that the widget has depends on its place within the program.</para
+></tip>
+
+<sect1 id="widget-table">
+<title
+>Listing of Common &kde; Widgets</title>
+<para
+>Currently, this guide consists of a table of the names of the graphical elements often found in &kde; documentation, and an example of each one. </para>
+<para
+>Our hope, eventually, is to make this a much more complete document, which will take you on a visual tour of &kde;.</para>
+
+<informaltable>
+<tgroup cols="2">
+<tbody>
+
+<row>
+<entry
+>Button</entry>
+<entry>
+<inlinemediaobject>
+<imageobject>
+<imagedata fileref="pict12.png" format="PNG"/>
+</imageobject>
+</inlinemediaobject>
+</entry>
+</row>
+
+<row>
+<entry
+>Check Boxes</entry>
+<entry>
+<inlinemediaobject>
+<imageobject>
+<imagedata fileref="pict13.png" format="PNG"/>
+</imageobject>
+</inlinemediaobject>
+</entry>
+</row>
+
+<row>
+<entry
+>Colour Selector</entry>
+<entry>
+<inlinemediaobject>
+<imageobject>
+<imagedata fileref="pict9.png" format="PNG"/>
+</imageobject>
+</inlinemediaobject>
+</entry>
+</row>
+
+<row>
+<entry
+>Combo Box</entry>
+<entry>
+<inlinemediaobject>
+<imageobject>
+<imagedata fileref="pict2.png" format="PNG"/>
+</imageobject>
+</inlinemediaobject>
+</entry>
+</row>
+
+<row>
+<entry
+>Dialogue Box</entry>
+<entry>
+<inlinemediaobject>
+<imageobject>
+<imagedata fileref="pict6.png" format="PNG"/>
+</imageobject>
+</inlinemediaobject>
+</entry>
+</row>
+
+<row>
+<entry
+>Drop Down Box</entry>
+<entry>
+<inlinemediaobject>
+<imageobject>
+<imagedata fileref="pict1.png" format="PNG"/>
+</imageobject>
+</inlinemediaobject>
+</entry>
+</row>
+
+<row>
+<entry
+>Icon List</entry>
+<entry>
+<inlinemediaobject>
+<imageobject>
+<imagedata fileref="pict16.png" format="PNG"/>
+</imageobject>
+</inlinemediaobject>
+</entry>
+</row>
+
+<row>
+<entry
+>List Box</entry>
+<entry>
+<inlinemediaobject>
+<imageobject>
+<imagedata fileref="pict7.png" format="PNG"/>
+</imageobject>
+</inlinemediaobject>
+</entry>
+</row>
+
+<row>
+<entry
+>Menubar</entry>
+<entry>
+<inlinemediaobject>
+<imageobject>
+<imagedata fileref="pict4.png" format="PNG"/>
+</imageobject>
+</inlinemediaobject>
+</entry>
+</row>
+
+<row>
+<entry
+>Progress Bar</entry>
+<entry>
+<inlinemediaobject>
+<imageobject>
+<imagedata fileref="pict17.png" format="PNG"/>
+</imageobject>
+</inlinemediaobject>
+</entry>
+</row>
+
+<row>
+<entry
+>Radio Buttons</entry>
+<entry>
+<inlinemediaobject>
+<imageobject>
+<imagedata fileref="pict10.png" format="PNG"/>
+</imageobject>
+</inlinemediaobject>
+</entry>
+</row>
+
+<row>
+<entry
+>Scroll Bar</entry>
+<entry>
+<inlinemediaobject>
+<imageobject>
+<imagedata fileref="pict18.png" format="PNG"/>
+</imageobject>
+</inlinemediaobject>
+</entry>
+</row>
+
+<row>
+<entry
+>Slider</entry>
+<entry>
+<inlinemediaobject>
+<imageobject>
+<imagedata fileref="pict15.png" format="PNG"/>
+</imageobject>
+</inlinemediaobject>
+</entry>
+</row>
+
+<row>
+<entry
+>Spin Box</entry>
+<entry>
+<inlinemediaobject>
+<imageobject>
+<imagedata fileref="pict11.png" format="PNG"/>
+</imageobject>
+</inlinemediaobject>
+</entry>
+</row>
+
+<row>
+<entry
+>Status Bar</entry>
+<entry>
+<inlinemediaobject>
+<imageobject>
+<imagedata fileref="pict20.png" format="PNG"/>
+</imageobject>
+</inlinemediaobject>
+</entry>
+</row>
+
+<row>
+<entry
+>Text Box</entry>
+<entry>
+<inlinemediaobject>
+<imageobject>
+<imagedata fileref="pict14.png" format="PNG"/>
+</imageobject>
+</inlinemediaobject>
+</entry>
+</row>
+
+
+<row>
+<entry
+>Toolbar</entry>
+<entry>
+<inlinemediaobject>
+<imageobject>
+<imagedata fileref="pict3.png" format="PNG"/>
+</imageobject>
+</inlinemediaobject>
+</entry>
+</row>
+
+<row>
+<entry
+>Tree View</entry>
+<entry>
+<inlinemediaobject>
+<imageobject>
+<imagedata fileref="pict19.png" format="PNG"/>
+</imageobject>
+</inlinemediaobject>
+</entry>
+</row>
+
+
+<row>
+<entry
+>Window Titlebar</entry>
+<entry>
+<inlinemediaobject>
+<imageobject>
+<imagedata fileref="pict5.png" format="PNG"/>
+</imageobject>
+</inlinemediaobject>
+</entry>
+</row>
+
+</tbody>
+</tgroup>
+</informaltable>
+</sect1>
+</chapter>
+<chapter id="credits">
+<title
+>Credits and Licences</title>
+<para
+>&kappname;</para>
+
+<para
+>Documentation by the KDE Documentation Team.</para>
+&underFDL; </chapter>
+
+</book>
+
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/welcome.docbook b/tde-i18n-en_GB/docs/tdebase/khelpcenter/welcome.docbook
new file mode 100644
index 00000000000..d4aa9329fb6
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/welcome.docbook
@@ -0,0 +1,98 @@
+<chapter id="welcome-to-kde">
+<chapterinfo
+><date
+>2002-01-18</date
+> <releaseinfo
+>3.00.00</releaseinfo
+> </chapterinfo>
+<title
+>Welcome to &kde;</title>
+<anchor id="welcome"/>
+
+<para
+> <emphasis
+>The &kde; team welcomes you to user-friendly &UNIX; computing.</emphasis
+> </para>
+
+<sect1 id="welcome-page">
+<title
+>Welcome to the K Desktop Environment</title>
+
+<sect2 id="welcome-information-about-kde">
+<title
+>Information about &kde;</title>
+
+<para
+>&kde; is a powerful graphical desktop environment for &UNIX; workstations. A &kde; desktop combines ease of use, contemporary functionality and outstanding graphical design with the technological superiority of the &UNIX; operating system. </para>
+
+<para
+><link linkend="what-is-kde"
+>What is the K Desktop Environment?</link
+></para>
+
+<para
+><link linkend="contact"
+>Contacting the &kde; Project</link
+></para>
+
+<para
+><link linkend="support"
+>Supporting the &kde; Project</link
+></para>
+
+<para
+><link linkend="links"
+>Useful links</link
+></para>
+
+</sect2>
+
+<sect2 id="welcome-getting-the-most-out-of-kde">
+<title
+>Getting the most out of &kde;</title>
+
+<sect3 id="welcome-general-documentation">
+<title
+>General documentation</title>
+
+<para
+><ulink url="help:/khelpcenter/quickstart"
+>A Quick Start Guide to the Desktop</ulink
+></para>
+
+<para
+><ulink url="help:/khelpcenter/userguide"
+>&kde; User's guide</ulink
+></para>
+
+<para
+><ulink url="help:/khelpcenter/faq"
+>Frequently asked questions</ulink
+></para>
+
+</sect3>
+
+<sect3 id="welcome-basic-applications">
+<title
+>Basic applications</title>
+
+<para
+><ulink url="help:/kicker"
+>Desktop Panel</ulink
+></para>
+
+<para
+><ulink url="help:/kcontrol"
+>Control Centre</ulink
+></para>
+
+<para
+><ulink url="help:/konqueror"
+>File Manager</ulink
+></para>
+
+</sect3>
+</sect2>
+</sect1>
+</chapter>
+
diff --git a/tde-i18n-en_GB/docs/tdebase/khelpcenter/whatiskde.docbook b/tde-i18n-en_GB/docs/tdebase/khelpcenter/whatiskde.docbook
new file mode 100644
index 00000000000..dc5535fdb51
--- /dev/null
+++ b/tde-i18n-en_GB/docs/tdebase/khelpcenter/whatiskde.docbook
@@ -0,0 +1,101 @@
+<chapter id="what-is-kde">
+<chapterinfo
+><date
+>2002-01-18</date
+> <releaseinfo
+>3.00.00</releaseinfo
+> </chapterinfo>
+<title
+>What is &kde;?</title>
+<anchor id="whatiskde"/>
+
+<sect1 id="what-is-kde-introduction">
+<title
+>What is &kde;?</title>
+
+<para
+>&kde; is a desktop environment. In other words, &kde; is a collection of programs, technologies and documentation that attempt to make life easier for computer users. &kde; is targeted at &UNIX; workstations. It features network transparency and a contemporary work philosophy. </para>
+
+<para
+>The creators of the K Desktop Environment are a world-wide group of software engineers. This group's major goal in free software development is to provide high quality software that empowers the user with easy control of his computer's resources.</para>
+
+<para
+>&kde; seeks to fill the need for an easy to use desktop for &UNIX; workstations, similar to the desktop environments found under &MacOS; or &Windows; 95/NT. &kde; meets the requirement of users for an easy to use work environment. Tools used to reach this end are: enhanced inter-application communication, component reuse, global drag and drop, uniform look and feel and many more. Thus, &kde; offers much more than the traditional &UNIX; window managers.</para>
+
+<para
+>Stability, scaleability and openness are qualities which have made &UNIX; the undisputed choice for the information technology professional for many years. &kde; builds on top of this excellent base framework and brings new, much needed qualities: usability, user friendliness and beauty! &kde; was the first, and stays the forefront player in bringing these qualities to &UNIX;, which constituted for years, the premier platform for server computers and scientific institutions, but wasn't very attractive for desktop users.</para>
+
+<para
+>Without &UNIX; the Internet would not exist, or at least would have a vastly different form. &UNIX; has not, until now, addressed the needs of the average computer user. This fact is particularly unfortunate, since a number of implementations of &UNIX; (<ulink url="http://www.linux.org"
+>&Linux;</ulink
+>, <ulink url="http://www.freebsd.org"
+>FreeBSD</ulink
+>, <ulink url="http://www.netbsd.org"
+>NetBSD</ulink
+>, &etc;) are freely available on the Internet, all of which are of exceptional quality and stability. </para>
+
+</sect1>
+
+<sect1 id="what-is-kde-the-desktop">
+<title
+>&kde; The Desktop Environment</title>
+
+<para
+>In combination with a free implementation of &UNIX;, &kde; provides to the world an open and completely free desktop computing platform either at home or at work.</para>
+
+<para
+>This platform is available to anyone free of charge including its source code for anyone to modify.</para>
+
+<para
+>While there will always be room for improvement we believe we have now delivered a viable alternative to some of the more commonly found and commercial operating systems/desktops combinations available today. It is our hope that the combination of &UNIX; and &kde; will finally bring the same open, reliable, stable, and monopoly free computing to the average computer user that scientists and computing professionals world-wide have enjoyed for years. </para>
+
+</sect1>
+
+<sect1 id="what-is-kde-the-development-framework">
+<title
+>&kde; The Application Development Framework</title>
+
+<para
+>&kde; focuses on the user's needs, but it's obvious that this focus is more easily achieved by also giving developers the best tools. &kde; code contains, and comes with, some of the best development technologies of the modern computing age.</para>
+
+<para
+>Authoring applications under &UNIX;/X11 used to be an extremely tedious and labour intensive process. &kde; recognises the fact that a computing platform is only as good as the number of first class applications available to the users of that particular platform.</para>
+
+<para
+>&kde; defines new technologies in &DCOP; and KParts, created to offer a component document model and technology. Together with the complete &kde; libraries programming interface, &DCOP;/KParts are set in direct competition with other similar technologies like &Microsoft; <abbrev
+>MFC</abbrev
+>/<abbrev
+>COM</abbrev
+>/ActiveX technologies. The excellent quality and the high level of refinement of &kde;'s application programming interface (<acronym
+>API</acronym
+>) enables developers to focus on original and interesting issues and avoid reinventing the wheel.</para>
+
+</sect1>
+
+<sect1 id="what-is-kde-the-office-suite">
+<title
+>&kde; The Office Application Suite</title>
+
+<para
+>In its current form, &kde; provides, apart from the essential desktop component applications, a suite of powerful office programs known to the world by the name &koffice;.</para>
+
+<para
+>&koffice; is based on the &kde; &DCOP;/KParts technologies. It currently contains: a word processor with desktop publishing capabilities (&kword;), a spreadsheet application (&kspread;) and accompanying charting program (&kchart;), a presentation program (&kpresenter;) and a vector drawing program (&kontour;). Tying things together is the <application
+>KOffice Workspace</application
+>, an integrated shell to ease the use of the &koffice; components in conjunction with each other. Additional components include an email client, a news reader, and a powerful <abbrev
+>PIM</abbrev
+> (Personal Information Manager - an organiser).</para>
+
+<para
+>While some of those components are still in alpha development, others are already extremely powerful. For example, &kpresenter;, &kde;'s presentation application, was successfully used at the 5th International &Linux; Congress in Cologne, Germany to deliver a &kde; presentation. </para>
+
+<para
+>We would like to invite you to <ulink url="http://www.kde.org"
+>learn more about &kde;</ulink
+> and <ulink url="http://koffice.kde.org"
+>&koffice;</ulink
+>.</para>
+
+</sect1>
+</chapter>
+