Second part of prior commit

4 files changed, 2197 insertions, 0 deletions

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:
+-->
+