From f7e7a923aca8be643f9ae6f7252f9fb27b3d2c3b Mon Sep 17 00:00:00 2001 From: Timothy Pearson Date: Sat, 3 Dec 2011 11:05:10 -0600 Subject: Second part of prior commit --- tde-i18n-en_GB/docs/tdebase/userguide/Makefile.am | 4 + tde-i18n-en_GB/docs/tdebase/userguide/Makefile.in | 635 ++++++++++++++++++ .../docs/tdebase/userguide/about-desktop.docbook | 581 ++++++++++++++++ .../tdebase/userguide/first-impressions.docbook | 470 +++++++++++++ .../docs/tdebase/userguide/getting-started.docbook | 581 ++++++++++++++++ .../docs/tdebase/userguide/history.docbook | 186 ++++++ .../docs/tdebase/userguide/index.cache.bz2 | Bin 0 -> 25591 bytes .../docs/tdebase/userguide/index.docbook | 116 ++++ .../docs/tdebase/userguide/installation.docbook | 729 +++++++++++++++++++++ .../docs/tdebase/userguide/intro.docbook | 34 + .../docs/tdebase/userguide/more-help.docbook | 68 ++ .../tdebase/userguide/notices-trademarks.docbook | 110 ++++ .../docs/tdebase/userguide/shortcuts.docbook | 357 ++++++++++ .../docs/tdebase/userguide/staff.docbook | 151 +++++ .../docs/tdebase/userguide/ug-faq.docbook | 129 ++++ 15 files changed, 4151 insertions(+) create mode 100644 tde-i18n-en_GB/docs/tdebase/userguide/Makefile.am create mode 100644 tde-i18n-en_GB/docs/tdebase/userguide/Makefile.in create mode 100644 tde-i18n-en_GB/docs/tdebase/userguide/about-desktop.docbook create mode 100644 tde-i18n-en_GB/docs/tdebase/userguide/first-impressions.docbook create mode 100644 tde-i18n-en_GB/docs/tdebase/userguide/getting-started.docbook create mode 100644 tde-i18n-en_GB/docs/tdebase/userguide/history.docbook create mode 100644 tde-i18n-en_GB/docs/tdebase/userguide/index.cache.bz2 create mode 100644 tde-i18n-en_GB/docs/tdebase/userguide/index.docbook create mode 100644 tde-i18n-en_GB/docs/tdebase/userguide/installation.docbook create mode 100644 tde-i18n-en_GB/docs/tdebase/userguide/intro.docbook create mode 100644 tde-i18n-en_GB/docs/tdebase/userguide/more-help.docbook create mode 100644 tde-i18n-en_GB/docs/tdebase/userguide/notices-trademarks.docbook create mode 100644 tde-i18n-en_GB/docs/tdebase/userguide/shortcuts.docbook create mode 100644 tde-i18n-en_GB/docs/tdebase/userguide/staff.docbook create mode 100644 tde-i18n-en_GB/docs/tdebase/userguide/ug-faq.docbook (limited to 'tde-i18n-en_GB/docs/tdebase/userguide') diff --git a/tde-i18n-en_GB/docs/tdebase/userguide/Makefile.am b/tde-i18n-en_GB/docs/tdebase/userguide/Makefile.am new file mode 100644 index 00000000000..8161986a832 --- /dev/null +++ b/tde-i18n-en_GB/docs/tdebase/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/userguide/Makefile.in b/tde-i18n-en_GB/docs/tdebase/userguide/Makefile.in new file mode 100644 index 00000000000..5994afeb027 --- /dev/null +++ b/tde-i18n-en_GB/docs/tdebase/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/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/userguide/Makefile'; \ +#>- cd $(top_srcdir) && \ +#>- $(AUTOMAKE) --gnu docs/tdebase/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/userguide/Makefile'; \ + cd $(top_srcdir) && \ + $(AUTOMAKE) --gnu docs/tdebase/userguide/Makefile + cd $(top_srcdir) && perl ../scripts/admin/am_edit -p../scripts/admin docs/tdebase/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 about-desktop.docbook intro.docbook index.docbook getting-started.docbook notices-trademarks.docbook Makefile.in first-impressions.docbook ug-faq.docbook shortcuts.docbook more-help.docbook staff.docbook Makefile.am index.cache.bz2 + +#>+ 24 +index.cache.bz2: $(srcdir)/index.docbook $(KDE_XSL_STYLESHEET) first-impressions.docbook intro.docbook about-desktop.docbook index.docbook more-help.docbook history.docbook shortcuts.docbook installation.docbook ug-faq.docbook getting-started.docbook notices-trademarks.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 intro.docbook about-desktop.docbook index.docbook more-help.docbook history.docbook shortcuts.docbook installation.docbook ug-faq.docbook getting-started.docbook notices-trademarks.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 intro.docbook about-desktop.docbook index.docbook more-help.docbook history.docbook shortcuts.docbook installation.docbook ug-faq.docbook getting-started.docbook notices-trademarks.docbook staff.docbook ; do \ + rm -f $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/userguide/$$base ;\ + done + + +#>+ 5 +distdir-nls: + for file in first-impressions.docbook intro.docbook about-desktop.docbook index.docbook more-help.docbook history.docbook shortcuts.docbook installation.docbook ug-faq.docbook getting-started.docbook notices-trademarks.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/userguide/Makefile'; \ + cd $(top_srcdir) && \ + $(AUTOMAKE) --gnu docs/tdebase/userguide/Makefile + cd $(top_srcdir) && perl ../scripts/admin/am_edit -p../scripts/admin docs/tdebase/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/userguide/about-desktop.docbook b/tde-i18n-en_GB/docs/tdebase/userguide/about-desktop.docbook new file mode 100644 index 00000000000..013f11d8926 --- /dev/null +++ b/tde-i18n-en_GB/docs/tdebase/userguide/about-desktop.docbook @@ -0,0 +1,581 @@ + +All About Your Desktop + + +Little Red Riding Hood +Grandma, what big eyes you have! + + + +The Wolf +The better to see you! + + +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. + + +Autostarting Applications + +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 Autostart folder for these programs. + +To launch programs when &kde; is started, do the following: + + + +Open the Autostart folder. By default this folder is at $HOME/.kde/Autostart + + +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 . + + +Drag and drop the desired program from the &konqueror; window on to the Autostart folder. When asked, choose Link to create a symbolic link rather than a full copy, as this saves a great deal of disk space. + + +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;. + + +Restart &kde; if you want to see the autostart function in action. + + + +Your programs should have launched automatically when &kde; restarted. + +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. + + + + +Adding Programs and Shortcut Icons to Your &kmenu; and Panel + +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. + + +Adding menu entries + +&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 &Alt;F2 and entering kappfinder to see it in action — operation is very straightforward. + +&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. + +To add your favourite programs to the &kde; menu, you can use the KDE Menu Editor. To start it, use the &kmenu; and choose SettingsMenu Editor. + +A window will open showing the existing &kmenu; on the left, and an empty menu entry dialogue on the right + +For this example, we will be adding an entry for the Gimp under the Graphics submenu. If you already have a Gimp entry there and don't want a new one, you can still follow through this example, but just don't click the Apply when you are done. + + +Navigate down the left hand tree to the Graphics entry. + +Click on it once with the left mouse button to expand the entry. + + +Click the icon labelled New Item in the toolbar, or choose FileNew Item in the menu bar. + + +In the dialogue box that pops up, enter the name you want your new menu entry to have. For this example, enter Gimp.Then press OK in the dialogue. + + +Click on the new Gimp menu entry that was created for you under the Graphics submenu. The menu entry dialogue to the right will now change to be mostly empty, except for the name you already gave. + + +Fill in an optional Comment. You might like to put An image editor for the example. Text entered here will be shown as a tool-tip in the &kmenu;. + + +Enter in the box labelled Command, the command you would type on the command line to open your application. For this example, this is gimp. 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. + + +If you want the application to operate from a particular folder (for example, for Gimp to begin its Load Image dialogue in a particular place) enter this path in the box labelled Work Path. This is optional. + + +If you wish to change the icon from the default unknown, click on the icon to the right of the dialogue, to open a standard &kde; icon chooser. + + +Some applications must be run in a terminal window (for example Pine). If this is the case, check the appropriate check box. + + +If you want to run your application as a different user, check the box labelled Run as a different user and enter the appropriate user name in the text box. + + +If you're happy with your menu entry, press Apply. If you would like to start over, press Reset. + + + +And that's all. You now have a new menu entry. + + + + +Shortcut Icons + +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. + +To create a shortcut on the &kicker; panel, you have some choices: Drag-and-drop, or via a menu. + + +Adding a shortcut icon with the menu +Click on the &kicon; and choose Panel MenuAddApplication . +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 Home folder or &konqueror;. Click on the program you want. + + + +A new icon will appear on the panel. Click on it, and the program will start. + +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. + +What happens when you drag an item to your panel depends on what kind of item it is: + + + +If you drag a folder... A menu will pop up giving you a choice of Add as a File Manager URL or Add as a QuickBrowser. 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. + + + +If you drag a shortcut from your desktop... +It will be copied to the panel. + + + +If you drag a document... +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. + + + +In any case, if you want to move the icon, click on it using the &RMB; and choose Move Name of Button 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 Remove Name of Button. + + + + + +Creating New Files On Your Desktop + +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. + +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 /home/stupiddog, so my Desktop folder is /home/stupiddog/Desktop. Everything you save there will be put on your desktop. + +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 & drop and the file manager, see the chapter Moving files with drag & drop. + + + + +Placing Links on Your Desktop + +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? + + + +Using &MIME; Types and File Associations + +&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 .mod files could be set to start &noatun;, .html files could open a &konqueror; window showing the file, and a core file can be viewed with the &khexedit; by simply clicking on the core file. + + +Although &MIME; types are very powerful, they are not without dangers. Playing around with &MIME; types as the system administrator (root) can damage a &kde; system so severely that it cannot be restarted! In this example, you will create your personal &MIME; style, which is only relevant for you. It will only affect other users if you copy or move it to $KDEDIR/share/mimelnk. + + +To link a certain file type with a particular application: + + + +Make sure the application you want to start this file type has an entry in the &kmenu;. + +In &konqueror; find or make a file with the extension you wish to link. + +Right click on the file, and choose Properties from the context menu and then press the tiny button with an icon next to the Type resulting properties dialogue. Or, choose EditEdit File Type... in the &konqueror; menu bar. + +Add file masks for the application by clicking the Add button, and entering the file pattern you want. Remember that &UNIX; is case sensitive, so you may need to add variations - *.mp3 may need *.MP3 added as well, for example. Add as many masks as you like in this way. + +Add a description if you like. This is optional. + +In the section labelled Application Preference Order, press the Add 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. + +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 Move Up and Move Down buttons. + +If you're satisfied with your choices, you can click the Apply 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 OK to save your changes and close the dialogue box, or Cancel if you have changed your mind and just want to close the dialogue box. + + +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. + + +&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 gunzip won't operate on files that aren't named .gz. + +&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 ^clientname*. Then any files that have clientname at the beginning (the ^ character means starts with...) will be opened with the application you choose. + + + + + + +Using the Trash Can + +Under normal circumstances, deleting a file under &UNIX; is something which cannot be undone. However, with &kde;, you can choose Move to Trash instead of Delete. This will move the file into the Trash Folder, which, by default, is accessible as an icon on your desktop. In the Trash 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 Empty trashcan, otherwise you might run out of disk space because the files still need space. Note, however, that once you empty the Trash Folder, the files contained therein are lost forever. + + + + diff --git a/tde-i18n-en_GB/docs/tdebase/userguide/first-impressions.docbook b/tde-i18n-en_GB/docs/tdebase/userguide/first-impressions.docbook new file mode 100644 index 00000000000..1328a2e0170 --- /dev/null +++ b/tde-i18n-en_GB/docs/tdebase/userguide/first-impressions.docbook @@ -0,0 +1,470 @@ + +First Impressions + + +Origin unknown +You see to sea to see all that you can see is sea + + +First impressions are so important -- this is not only true for Agatha Christie's famous thriller The Mousetrap -- 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. + + +Starting &kde; + +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: + +startx + + +If the installation was successful, the &kde; desktop should appear after a few seconds of initialisation. + +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. + +If you have not done so already, we recommend changing your X display manager from xdm to &kdm;, which includes the same functionality, but with the advanced features of the K Desktop Environment. + +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;. + + + + +Desktop Components + +After everything has come up, take some time to explore the new environment. If you have already worked with &Windows;, OS/2 or &MacOS;, many things should look familiar to you. The main visible parts of &kde; that you will see are the desktop itself, and the panel. + + + +Panel + +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. + + + +&kicon; button +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 the K Menu Editor, 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 left mouse button. + + + +Virtual Desktop buttons +When you start &kde; for the first time, note the four buttons labelled, appropriately enough, 1, 2, 3 and 4. These represent your four desktops. Just click one of them. Don't worry; though they have disappeared, 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 Well, on the first desktop, I will write the &kde; User Guide. On the second desktop I'll run the meinproc documentation compiler and see my results while compiling my &Linux; kernel on the third desktop, and reading my email on the fourth. + + +Icon bar + +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 Konsole terminal emulator and to the documents you use often. For information on how to add icons to the taskbar, read Adding icons to your taskbar. +&kde; by default installs several commonly used buttons, including links to &khelpcenter;, &kwrite; and &kcontrol;. + + +Time and date +At the far right end of the &kde; panel, you can always see the time and date. + + +The task list + +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 right 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. + + + + + +Using Windows + + + +Window menu + +Right 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 right 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: + + + +Move +Lets you move the window with your mouse. Click on the left mouse button when you have the window where you want it to be. + + +Resize +Enables you to make the window smaller or larger. Move your mouse around and click when you are satisfied with the new size. + + +Minimise +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. + + +Maximise +This will expand the window to the largest size possible. Note that &kde; will take the size of your virtual desktop, which means that the window could be bigger than your screen. + + +Shade +Roll 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 Shade again, or double click in the titlebar. + + +Advanced +Here you can find menu options that allow you to manipulate how windows may cover each other up, and more: + + + +Keep Above Others +Selecting this will keep this window on top of all other applications, even when it does not have the focus. + + +Keep Below Others +Selecting this will keep this window below all others, even when it does have the focus. + + +Fullscreen +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 &Alt; to switch to another window or &Ctrl; to switch to another virtual desktop. +To revert from fullscreen mode, you can use the &Alt;F3 shortcut to show the window operations menu and deselect AdvancedFullscreen . + + + +No Border + +Remove the window decoration and border from this window. This is useful for monitor 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 xterm and &konsole; windows. +To revert from no border mode, you can use the &Alt;F3 shortcut to show the window operations menu and deselect AdvancedNo Border . + + + + +Store Window Settings +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. + + + + + + +To Desktop +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 Desktop Button on the &kde; Panel. Selecting All Desktops will make the window sticky - it will display on all desktops at once, so you can alway see this window. + + +Configure Window Behaviour... +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 Keramik. +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. + + + +Close +This will close the window. Sometimes the application will allow you to save your work, but in some cases (⪚, 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. +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 kill 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. + + + + + + + + +Window Decoration Buttons + +Sticky button +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 To DesktopAll Desktops in the Window Menu, but requires fewer steps to invoke. + + +Title bar +The title bar containing the name of the window can be double-clicked in order to shade it. Use the right mouse button: The Window menu 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. + + +Minimise, Maximise and Close Buttons +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. +At the far left of the titlebar (with the default window decoration) is a button to close the window. + + + +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.) + +Using the menu bar of each &kde; window is easy. Just click on what you want to do, and it will be done. + +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 right mouse button and a context menu will appear, allowing you to put the menu bar on the top, left, right, or bottom of the window. You can also hide the menubar by selecting Flat + + + + +Getting Help + +Help is available basically everywhere: On the desktop, just use the right mouse button and choose HelpKDesktop Handbook. On the &kde; panel, open the application menu and choose Help. Every &kde; program has a help menu. + + + + + diff --git a/tde-i18n-en_GB/docs/tdebase/userguide/getting-started.docbook b/tde-i18n-en_GB/docs/tdebase/userguide/getting-started.docbook new file mode 100644 index 00000000000..65641835014 --- /dev/null +++ b/tde-i18n-en_GB/docs/tdebase/userguide/getting-started.docbook @@ -0,0 +1,581 @@ + +Getting Started + + +Help for one of the toughest riddles in The 7th Guest +Using only what you see, can you get from A to B? + + +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 — it's a full fledged environment. + + +Editing Files + +Since you do not only have &kde; applications installed on your system, you probably know the mess of editing ASCII 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 ASCII 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 ASCII files of your own. + + +Opening a Window Containing Your Home Folder + +Click on the &kicon; button and choose Home (Personal Files). 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 Show Hidden Files from the View menu. + +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 hidden files — files or folders beginning with a period. + + + + +The File Manager Screen + +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. + +On the top, there is a Location menu which contains functions to open and close file manager windows. You can also print the current contents. + +Want to visit the Internet? There are several paths you can take. You could choose LocationOpen Location (or press &Ctrl;O) and enter a &URL;. + +The simplest way however, is to simply type in the address you want to go to in the location bar itself. + +For example, if you want to visit the &kde; homepage, enter http://www.kde.org. You can also quickly transfer files over &FTP; using this method. &kde; is Internet ready, 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. + + +The Edit menu offers functions to select, copy and move files. We will use them later. Already having used the View menu, you have probably seen that you can view the content in many different ways. Just play around a bit and see what happens. + +You will undoubtedly find the Bookmarks 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. + +The Tools menu helps you find the notorious file-that-I-put-somewhere-I-do-not-remember-anymore. + + + + +Navigating Through Folders + +We will now pick one of your configuration files and edit it. First, we must change the folder in the File Manager. + +&konqueror; started with your home folder as the top of the tree. 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. + +You can quickly display the / or root folder several ways: click the small folder icon beside the navigation pane to switch to a full filesystem tree, use the Up arrow on the toolbar above to go to the top of your filesystem in the right hand pane, or type in / in the location bar. + +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. + +Scroll down the navigation pane on the left side of the window until you find the folder /etc. Double-click on etc. You will see a long list of files in the right window. + + + + +Opening A File + +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 root or superuser. We are going to practice on a file that will not hurt anything if a mistake is made, called motd. + +Scroll down until you find the file motd and click on it with the right mouse button. In the context menu, select Open With. A new menu will pop up. Choose &kwrite;. Voila! + +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 Editors section, and chosen another editor, or simply double click the file to open it in the default editor. + +In the meantime, you have the file /etc/motd open in &kwrite; and we're ready to do some editing. + + + + +The Editor Screen + +The more you work with &kde;, the more you will notice that most screens and applications look and feel the same. The &kwrite; File 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. + +The Edit 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 Settings Menu, you can customise the editor in many different ways. For example, you can increase the font size to suit your monitor resolution — and your eyes. Of course, as in any other &kde; application, you find a Help Menu, offering you on-line help whenever you need it. + + + + +Using the Editor + +Most motd files contain useless stuff like Do not forget to back up your data or Do not annoy the system manager. 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 &Shift;Arrows or by using the mouse with the left button pressed. Use the Edit Menu to cut and paste text. Enter whatever you want, or use the following (great) example: + +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. + + + + +Saving Your Work + +Now that you have changed the motd file, it is time to save the file, putting the changes into effect. To do this, you can use either the File Menu, or you can use the Save Icon on the toolbar. + +At this point, reality hits us. You need to have root permission to save the changes to this file. &kde; handles this by asking you for the root password. + +You probably don't really want to save this file, so you can press Cancel in the password dialogue and Cancel again in the save dialogue. + +Finally, finish your work by closing the editor and file manager window. You can do this by clicking the X button on the top left of the window, by using the window menu of the title bar, or by choosing File Quit. Simple and elegant, isn't it? + + + + +Creating New Files + +As with everything in &kde;, there are several ways to create a new file. You could open up the file manager, right click on an empty space in a folder you own, and choose Create NewFileText File.... A new empty file will appear, which you can open just like any other. You can even do this right on the desktop itself. + +More often you are already in an application and want to start a new file. Most &kde; applications offer a FileNew menu item, and an icon on the toolbar to complement it. A new empty document will appear that you can immediately begin working in. + +Both these approaches have advantages, so use the one that is most practical at the time. + + + + + + +Moving Files With Drag and Drop + +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 — a procedure called drag and drop allows you to copy and move files more quickly and easily. + + +Opening Two File Manager Windows + +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 (WindowNavigation Panel or press F9). + + + + +Dragging a File From One Window To Another + +In the first window, open the /etc folder and scroll until you see the motd file we modified in the previous section. + +In the second window, open your home folder. + +Click on the motd file. Hold your left mouse button and drag your file into your home folder. Release the left mouse button (this is called dropping the file). You will be presented up to four options: Copy Here, Move Here, Link Here and Cancel. In this example, since you are not root, you cannot move the file, so this option is not presented. Link Here will create a symbolic link to the file, while Copy Here and Move Here do exactly what they say. Select Copy Here. You should now have a copy of the motd file in your home folder. + + + + + +Using Command Line And Terminals + +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. + + +Quick Command Line + +Pressing &Alt; F2 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. + + + + +The &UNIX; Terminal Emulator + +From the application menu, choose SystemTerminal . A terminal window will open. Here you can use regular &UNIX; shell commands: ls, cat, less, and so forth. Using the Settings menu, you can customise the terminal emulator to suit your needs. + + + + + +Finding Your Lost Files + +Everyone has undoubtedly encountered the following problem: You start ftp, 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. + + +Starting &kfind; + +Starting &kfind; is simple: Choose Find Files in the &kmenu;. &kfind; uses an interface part you probably have not yet met in &kde;: tabs. When &kfind; starts, you see that Name/Location is selected. When you click on Date Range, 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. + + + + +Finding a File by Knowing Parts of Its Name + +As long as you know a bit of the file name, searching is easy. Select the Name/Location tab, and enter the file name in the Named field. Wildcards may be used as needed. As a test, type *.tar.gz. By default, the search begins in your home folder, but you can select any starting folder you wish by clicking on the Look in or Browse.... To start searching, press the Find 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 Named field, or no files ending with a .tar.gz extension are located on your machine. + + + + +Finding a File by More Complex Criteria + +There are many categories you can use to make your search more precise. The more you know about the file, the better are your chances of finding it. + + + +Date Range + +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. + + + +File Type in the Contents tab. +If you know that the file was of a special type (⪚, a tar/gzip archive or a jpeg picture), you can tell &kfind; to find only this type of file. + + +Containing text in the Advanced tab + +You can specify text that the file must contain. + + + +File size is, in the Properties tab +If you know the file size, you can limit your search in this regard, as well. + + + +&kfind; has many more options to refine searches, explore them all! + + + + + +Using Multiple Desktops + +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 — at least in the office where I work. + +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. + +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 right mouse button, choose To Desktop, and select the desktop where you would like the window moved. + + + + +Quitting &kde; + +To quit working with &kde;, you can use the Logout 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 the notes for logging out. + + + + \ No newline at end of file diff --git a/tde-i18n-en_GB/docs/tdebase/userguide/history.docbook b/tde-i18n-en_GB/docs/tdebase/userguide/history.docbook new file mode 100644 index 00000000000..6b5bff13bf4 --- /dev/null +++ b/tde-i18n-en_GB/docs/tdebase/userguide/history.docbook @@ -0,0 +1,186 @@ + +A Short Guided Tour of &kde;'s History + + +The CEO of a big software company, at the beginning of the 80s...(apocryphal) +640KB ought to be enough for everybody + + + +Before &kde; + +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: + +find /var/spool/news -name '[0-9]*' -exec cat {} \; | more + + +Although fast and relatively efficient, this couldn't be called user friendly. Today, there are many good front ends available, such as tin 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. + +The configuration of programs is also often difficult. While compiling is usually done with a command line such as ./configure && make && make 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. + +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 RAM and more disk space. Often the new version provides functions few people really need. + +&kde; is different. 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. + + + + + +What &kde; Can Do For You + +&kde; is designed for everyone. + +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. + +No matter what your level of experience with &UNIX; or any other operating system, &kde; brings you: + + + +A good looking, easy to use desktop environment. + + +A powerful, easy to use file manager + + +An equally powerful and easy to use web browser + + +A simple, centralised configuration + + +A comprehensive list of applications, so you can be productive within minutes of your first &kde; login. + + +Online help to support you in every situation. + + +Consistency of interface. Menus are in the same place across applications, keybindings behave the same way, toolbar icons, once learned, always work the same. + + + + + + +The Background Of &kde; + +In October 1996, German LyX 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. + +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. + +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. + +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 SSL 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;. + +The developers and users communicate primarily via several mailing lists, as described in the Mailing Lists section. If you would like to help, please do, &kde; is driven by volunteer contribution, and you are always welcome to take part. + + + + +How To Get New Components + +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. + +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 http://www.kde.org/ftpmirrors.html. + +On the &FTP; servers, the folder unstable 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 stable folder, where we put Beta and release versions. + +If you are interested in developing &kde; applications of your own, you should visit http://developer.kde.org/" where you will find a wealth of information, including tutorials, API guides to the &kde; libraries, and much more. You should also visit Troll Tech's server (http://www.trolltech.com) which features a great deal of information concerning the &Qt; library used by &kde;. You will probably find it valuable to join the &kde; developer mailing list. + + + + + \ No newline at end of file diff --git a/tde-i18n-en_GB/docs/tdebase/userguide/index.cache.bz2 b/tde-i18n-en_GB/docs/tdebase/userguide/index.cache.bz2 new file mode 100644 index 00000000000..a6889c0662e Binary files /dev/null and b/tde-i18n-en_GB/docs/tdebase/userguide/index.cache.bz2 differ diff --git a/tde-i18n-en_GB/docs/tdebase/userguide/index.docbook b/tde-i18n-en_GB/docs/tdebase/userguide/index.docbook new file mode 100644 index 00000000000..d1d8b2db1ee --- /dev/null +++ b/tde-i18n-en_GB/docs/tdebase/userguide/index.docbook @@ -0,0 +1,116 @@ + + + + + + + + + + + + + + + +]> + + + +K Desktop Environment + + +The KDE Team + +MalcolmHunter
malcolm.hunter@gmx.co.uk
Conversion to British English + + +2003-10-19 +3.2 + + +2000200120022003 +The KDE Team + + +&GPLNotice; + + + +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. + + +KDE +user +guide + + + +&introduction; +&history; + +&first-impressions; +&getstarted; +&about-desktop; +&shortcuts; +&ug-faq; +&more-help; +&staff; +¬ices-and-trademarks; + + + diff --git a/tde-i18n-en_GB/docs/tdebase/userguide/installation.docbook b/tde-i18n-en_GB/docs/tdebase/userguide/installation.docbook new file mode 100644 index 00000000000..73a92b8eba3 --- /dev/null +++ b/tde-i18n-en_GB/docs/tdebase/userguide/installation.docbook @@ -0,0 +1,729 @@ + +Installation + + +Linus Torvalds, after finding one of his file systems smashed by a new Beta kernel +Core dumping fsck's tend to make me nervous + + +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 (.*) files in your home folder and the folder /usr/X11/lib/X11/xdm. + + +Requirements + +Before installing KDE, ascertain that your system fulfills the following requirements: + + + +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. + +Some free hard disk space on the partition where /opt/kde 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 /usr/src. + +A running X11 system with or without xdm. 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 the XFree86 web site for more information on how to get and install the X Window System, or contact your UNIX vendor support. + +The &Qt; libraries, version 3.2 or higher. You can obtain these at Troll Tech's FTP Server in tgz format. + + + +A warning before you start: Before upgrading from a previous version of &kde;, we recommend that you do the following: + +cd /opt/kde +tar + + + + + + +Linux: Installing RPMs for RedHat, Caldera and SuSE. + +Using RPMs is the easiest method to get KDE up and running. Just visit your favourite KDE mirror and visit the folder /pub/kde/stable/distribution/rpm. 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. + +The basic system consists of the files kde-component.architecture.rpm 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. + +Next, start installing with the base package. If you are installing KDE for the first time, use + +rpm tdesupport.arch.rpm +rpm tdelibs.arch.rpm +rpm tdebase.arch.rpm + + +It is important that these components are installed in the order listed, and that they are installed before any other KDE component. + +If you are upgrading from a previous release, try rpm kde-component.arch.rpm + + + +Once again, the order given above should be preserved, and the given components should be installed before any other KDE components. + +This will unpack the base distribution and install it by default in /opt/kde. + +If the installation of the base packages has been successful, you can install the remaining packages (use instead of once again to update an existing version) the same way. + + + + +Linux: Installing <acronym +>DEB</acronym +>s for debian + +The installation for a Debian system is also rather straightforward. You will only find KDE 2.0 packages for Debian 2.2 (Potato) and 3.0 (Woody). We describe here how to install packages for Debian 2.2, the stable version, since Debian 3.0 is still in development. However, the installation for both versions, is almost identical. The main difference is that KDE is officially included in Debian 3.0 and you do not need to specify any special location to find the deb packages for KDE. + +The 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 /etc/apt/sources.list. You should add to that file the following line: http://kde.tdyc.com/ stable kde2 + + +Then you have to update your local package database so that your system knows that there are new packages available. Type the following command: + +apt-get + + +Finally you should install the KDE base components. This is accomplished by typing: + +apt-get + + +If you want to install other components you should try some, or all of these options: + +apt-get +apt-get +apt-get +apt-get +apt-get +apt-get +apt-get +apt-get +apt-get +apt-get +apt-get + + +You may also be interested in installing your language. + +apt-get + +where xx has to be substituted by the country code. + +The control files for some KDE applications will be placed at /etc/kde2, the executables will go in /usr/bin and most of the auxiliary files in /usr/share under different folders. + +If you are upgrading from a previous version of KDE you should perform the following steps. First, update file /etc/apt/sources.list by changing the line with the location of KDE packages with line: http://kde.tdyc.com/ stable kde2. Second update your package database: + +apt-get + + +Finally install the KDE base system: + +apt-get +apt-get + + +If you want to install more KDE components try some, or all of these options. + +apt-get +apt-get +apt-get +apt-get +apt-get +apt-get +apt-get +apt-get +apt-get +apt-get +apt-get + + + + + +Using Source Compilation to Install on Top of Other Systems + +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. + +In order to compile and install KDE properly, you need to have the following items installed on your hard disk: + + +An ANSI-C compiler, e.g. the GNU C compiler. +An ANSI-C++ compiler, e.g. GNU C++. +The make utility. +Qt development version 2.2 or higher. +X11 development version (include files are often missing) + + +Once you have all the needed helper applications, go to your favourite KDE mirror and retrieve the following files from the folder /pub/kde/stable/newest version: + + +tdesupport-version.tar.gz +tdelibs-version.tar.gz + +tdebase-version.tar.gz +any other packages you wish to install. We advise you to get at least tdeutils. + + +In all cases above, version stands for the current version number. Once you have downloaded all you need, extract these files to /usr/src. This process should yield the following folder structure: + + +/usr/src/tdesupport +/usr/src/tdelibs +/usr/src/tdebase +/usr/src/... (any other packages) + + +Make sure you have write permissions to /opt/kde. + +Next you must compile and install the packages using the following: + + +cd into the folder of the package, you want to install (see above) +./configure (with the options you want to apply) +make +make install + + +Apply the above steps to every package you want to install. + +These instructions can be used for almost every source package available, not just KDE packages. + +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 configure in tdelibs: + + + 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 +... + + + +Several options are not required and are only useful as workarounds for known problems (⪚ ). Since some are important options, for instance --with-shadow, you should always check the available options. + +An important option is . 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 /usr/local/kde . If you want to install &kde; into /opt/kde, you have to use configure . + +If you have installed the &Qt; libraries in an uncommon place, for instance in $HOME/src/qt, you must use configure . By default configure looks in the most common places for &Qt; before it gives up. + +If you have problems that you are not able to solve, send a copy of the config.log file to the address given in the offending package's README file. + +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). + +If you want to take advantage of multiprocessor systems, try make instead of make. + + +Platform Specific Building Notes + + +Linux + +For &Linux;, most of the utilities needed to build &kde; can be found either at ftp://sunsite.unc.edu/pub/Linux/GCC or ftp://sunsite.unc.edu/pub/GNU. The Qt libraries can be found at ftp://ftp.troll.no/pub/qt/source, available as source code. Detailed instructions on how to install them are provided. Include files for X11 programs should be available at ftp://ftp.xfree86.org in the xdevel section. + + + + + + +Required Changes To Your Configuration Files +After you have placed the KDE binaries into their destination folder, there are a few adjustments you must make to your startup scripts. +The following procedure was tested on SuSE Linux 5.0, and should be compatible with the other popular UNIX's as well. Always make backups of configuration files before changing them! Add the following to the end of your /etc/profile: + +export PATH=$PATH:/opt/kde/bin +export KDEDIR=/opt/kde + + +Next, edit the .xinitrc file in your home folder. Look for the line that calls your window manager and replace it with starttde. +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 Using Source Compilation to Install on Top of Other Systems for more information. +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 the KDE mailing lists + + + diff --git a/tde-i18n-en_GB/docs/tdebase/userguide/intro.docbook b/tde-i18n-en_GB/docs/tdebase/userguide/intro.docbook new file mode 100644 index 00000000000..e1900a1800b --- /dev/null +++ b/tde-i18n-en_GB/docs/tdebase/userguide/intro.docbook @@ -0,0 +1,34 @@ + +Introduction + +Welcome to the K Desktop Environment User Guide. + +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. + +Included is a table of shortcuts, and some tips and tricks intended to help you find your way around quickly and efficiently. + +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 — what you learn in this manual and in your own exploration of &kde;'s interface is consistent and readily transferable between &kde; applications. + +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. + + + \ No newline at end of file diff --git a/tde-i18n-en_GB/docs/tdebase/userguide/more-help.docbook b/tde-i18n-en_GB/docs/tdebase/userguide/more-help.docbook new file mode 100644 index 00000000000..a62047b4dab --- /dev/null +++ b/tde-i18n-en_GB/docs/tdebase/userguide/more-help.docbook @@ -0,0 +1,68 @@ + +Further Help + + +Other Sources for Help + +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. + +You can subscribe at the web pages listed below: + + + +&kde; announcements - http://mail.kde.org/mailman/listinfo/kde-announce + +&kde; users' mailing list - http://mail.kde.org/mailman/listinfo/kde + +KDE developers' mailing list - http://mail.kde.org/mailman/listinfo/kde-devel + +KDE look and feel discussions - http://mail.kde.org/mailman/listinfo/kde-look + +KDE licensing questions - http://mail.kde.org/mailman/listinfo/kde-licensing + +KDE Documenters' list - http://mail.kde.org/mailman/listinfo/kde-doc-english + + +Many &kde; applications and sub-projects maintain more specific lists for themselves. You can find a complete list of archives at http://lists.kde.org/. + + + + diff --git a/tde-i18n-en_GB/docs/tdebase/userguide/notices-trademarks.docbook b/tde-i18n-en_GB/docs/tdebase/userguide/notices-trademarks.docbook new file mode 100644 index 00000000000..49fda79a921 --- /dev/null +++ b/tde-i18n-en_GB/docs/tdebase/userguide/notices-trademarks.docbook @@ -0,0 +1,110 @@ + +Legal Notices + +Licence + +&kde; is open source software, and all of &kde; is released under free licenses such as the GPL. + + + + +Trademarks + + + +All trademarks mentioned on this web server or in &kde; documentation are recognised as belonging to their respective owners, including but not limited to: + + +&AIX; is a registered trademark of IBM Corporation +&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. +&Handspring; and &Visor; are trademarks of Handspring, Inc. and may be registered in certain jurisdictions. +&Hewlett-Packard;, &HP; &LaserJet;,&HP-UX; PCL, PCL 5 and PCL 6 are U.S. registered trademarks of Hewlett Packard Company. +&IRIX; is a registered trademark and &SGI; is a trademark of Silicon Graphics, Inc. +&Java; and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. +&Jini; and all Jini-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the US and other countries. +&Linux; is a registered trademark of Linus Torvalds +&LinuxPPC; is a trademark of LinuxPPC Inc. +&Mac; is a trademark of Apple Computer Inc., registered in the United States and other countries. +&Mandrake; and &Linux-Mandrake; are trademarks of MandrakeSoft. +&Netscape; is a registered trademark of Netscape Communications Corporation in the United States and other countries. +&NeXTSTEP; is a trademark of NeXT Software, Inc., registered in the U.S. and other countries. +&PalmOS;, &HotSync; and &PalmPilot; are registered trademarks of Palm, Inc. +&PostScript; is a registered trademark of Adobe Systems Incorporated. +&Qt; is a trademark of Trolltech AS +&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. +&Sendmail; is a registered trademark of Sendmail Inc. +&Solaris;, Sun and SunOS are trademarks of Sun Microsystems Inc. +&SuSE; is a registered trademark of SuSE AG +&ThreeCom; is a registered trademark of 3com corporation in the United States and other countries. +&Motif;, &UNIX; and the X device are registered trademark of The Open Group in the United States and other countries +&Microsoft; and &Windows; are registered trademarks of the Microsoft Corporation +XFree86 is pending trademark registration by The XFree86 Project, Inc. + + + + + + + \ No newline at end of file diff --git a/tde-i18n-en_GB/docs/tdebase/userguide/shortcuts.docbook b/tde-i18n-en_GB/docs/tdebase/userguide/shortcuts.docbook new file mode 100644 index 00000000000..39b1c62c17f --- /dev/null +++ b/tde-i18n-en_GB/docs/tdebase/userguide/shortcuts.docbook @@ -0,0 +1,357 @@ + +Tips & Tricks for Your Daily Work + + +Fortune Cookies +Everyone can make an omelette with eggs. The trick is to make one with none. + + +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 ASCII style. However, there are some ways you can do your work more elegantly, saving you time for the truly important things, like &ksirtet;. + + +Shortcut Table + + + + +&Alt;Tab or &Alt;&Shift;Tab +Cycle through the windows + + + +&Ctrl;Tab or &Ctrl;&Shift;Tab +Cycle through your desktops + + + +&Alt;F2 +Mini Command line + + + +&Alt;F3 +Window Menu + + + +&Alt;F4 +Close the current window + + + +&Ctrl;F{1..8} +Switch to a specific desktop + + + +&Ctrl;&Alt;Esc +Window destroyer (every window you click on will be destroyed). Press this key combination again to cancel the killer cursor. + + + +&Ctrl;&Alt;Backspace +This exits &kde; (without saving!) Use this as a last resort + + +&Ctrl;&Alt;Numpad + +Cycles to the next screen resolution. You need to configure this in your &X-Server; configuration for it to work. + + + +&Ctrl;&Alt;Numpad - +Cycles to the previous screen resolution. You need to configure this in your &X-Server; configuration for it to work. + + + + + + +Mouse Techniques + +Note these are defaults only, and you can customise them to your liking. + + + + +Clicking on the border or the titlebar + + + + +Left +Activates and raises the window. + + + +Middle +Lowers the window + + + +Right +Shows the Window menu if the window is active, otherwise activates the window. + + + + + + +Doubleclick on the window title +Shades the window (rolls it up so only the titlebar is visible). + + + +Drag on the titlebar +Moves the window around. + + + +Drag on corners or edges +Resizes the window. + + + +&Alt;Left Button +Moves the window around. + + + +&Alt;Middle Button +Raises the window. + + + +&Alt;Right Button +Resizes the window in the direction you drag the mouse. + + + +Click on the Icon on the top left +Close the application + + +Click on the Sticky Button +toggles sticky + + + +Clicking on Maximise + + + +Left +Maximises the window + + +Middle +Maximises only vertically + + +Right +Maximises horizontally + + + + + + + + + + \ No newline at end of file diff --git a/tde-i18n-en_GB/docs/tdebase/userguide/staff.docbook b/tde-i18n-en_GB/docs/tdebase/userguide/staff.docbook new file mode 100644 index 00000000000..ae37ce0d813 --- /dev/null +++ b/tde-i18n-en_GB/docs/tdebase/userguide/staff.docbook @@ -0,0 +1,151 @@ + +Epilogue + + +The end of Evita +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... + +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. + + +The K Documentation Staff + +This User Guide has been updated for 3.0, and is currently maintained by Lauri Watts lauri@kde.org + +Others who have contributed to this guide. + +Pablo de Vicente vicente@oan.es, who updated the section regarding installing on Debian for KDE 2.0 +Andreas Buschka andi@circe.tops.net +Robert D. Williams rwilliam@kde.org +Poul Gerhard +John Waalkes +Vernon Wells +Kay Lutz +Stephan Kulow + + + + +We still need people! + +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 . If you would like to help, please do so! We are still looking for helpers in the following departments: + + +Development (Libraries and Applications) +Documentation +Graphics +Beta-Testing +and everywhere else, too :-) + + + + + +Legal notices + +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. + + + + +Sources of information used during the creation of this book + +During the creation of this documentation, the authors used the following sources for information: + + +The KDE Mailing lists +Various README and HTML help files that came with the KDE components + + + + + +Licence +&underGPL; + + \ No newline at end of file diff --git a/tde-i18n-en_GB/docs/tdebase/userguide/ug-faq.docbook b/tde-i18n-en_GB/docs/tdebase/userguide/ug-faq.docbook new file mode 100644 index 00000000000..9a94f503c70 --- /dev/null +++ b/tde-i18n-en_GB/docs/tdebase/userguide/ug-faq.docbook @@ -0,0 +1,129 @@ + +Frequently Asked Questions About &kde; + + +Batman Animated Series +What are you? +I'm your worst nightmare... + + +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! + + + + + +What does &kde; stand for? +Originally the K stood for Kool, nowadays the K has no meaning and &kde; simply stands for the K Desktop Environment. &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. + + + +I cannot compile package xxx + + +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 CVS. For most users, using a released version is much more practical. + +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 README 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. + + + + + +What version of &kde; should I use for a stable desktop? +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 (⪚ 3.2) is the best way to encourage stability on your &kde; desktop. + + + + + +But I heard that my problem/wishlist item is already in CVS. I want to get my hands on the new features, why shouldn't I try CVS? + + +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;. + +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 CVS versions. Be prepared for things to break occasionally, CVS gives you a snapshot of source code that is currently being worked on. + +These are daily snapshots of whatever the developers are working on, and some things are guaranteed to be broken. + + +Do not rely on CVS snapshots to maintain operational desktops. You will get burned eventually! + + + + + + + + + \ No newline at end of file -- cgit v1.2.1