diff options
| author | Timothy Pearson <kb9vqf@pearsoncomputing.net> | 2011-11-21 02:23:03 -0600 |
|---|---|---|
| committer | Timothy Pearson <kb9vqf@pearsoncomputing.net> | 2011-11-21 02:23:03 -0600 |
| commit | 9b58d35185905f8334142bf4988cb784e993aea7 (patch) | |
| tree | f83ec30722464f6e4d23d6e7a40201d7ef5b6bf4 /tde-i18n-en_GB/docs/kdebase/faq | |
| download | tde-i18n-9b58d35185905f8334142bf4988cb784e993aea7.tar.gz tde-i18n-9b58d35185905f8334142bf4988cb784e993aea7.zip | |
Initial import of extracted KDE i18n tarballs
Diffstat (limited to 'tde-i18n-en_GB/docs/kdebase/faq')
20 files changed, 4892 insertions, 0 deletions
diff --git a/tde-i18n-en_GB/docs/kdebase/faq/Makefile.am b/tde-i18n-en_GB/docs/kdebase/faq/Makefile.am new file mode 100644 index 00000000000..15208dfc8a8 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdebase/faq/Makefile.am @@ -0,0 +1,4 @@ +KDE_LANG = en_GB +SUBDIRS = $(AUTODIRS) +KDE_DOCS = khelpcenter/faq +KDE_MANS = AUTO diff --git a/tde-i18n-en_GB/docs/kdebase/faq/Makefile.in b/tde-i18n-en_GB/docs/kdebase/faq/Makefile.in new file mode 100644 index 00000000000..f704845000c --- /dev/null +++ b/tde-i18n-en_GB/docs/kdebase/faq/Makefile.in @@ -0,0 +1,635 @@ +# Makefile.in generated by automake 1.10.1 from Makefile.am. +# KDE tags expanded automatically by am_edit - $Revision: 483858 $ +# @configure_input@ + +# Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, +# 2003, 2004, 2005, 2006, 2007, 2008 Free Software Foundation, Inc. +# This Makefile.in is free software; the Free Software Foundation +# gives unlimited permission to copy and/or distribute it, +# with or without modifications, as long as this notice is preserved. + +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY, to the extent permitted by law; without +# even the implied warranty of MERCHANTABILITY or FITNESS FOR A +# PARTICULAR PURPOSE. + +@SET_MAKE@ +VPATH = @srcdir@ +pkgdatadir = $(datadir)/@PACKAGE@ +pkglibdir = $(libdir)/@PACKAGE@ +pkgincludedir = $(includedir)/@PACKAGE@ +am__cd = CDPATH="$${ZSH_VERSION+.}$(PATH_SEPARATOR)" && cd +install_sh_DATA = $(install_sh) -c -m 644 +install_sh_PROGRAM = $(install_sh) -c +install_sh_SCRIPT = $(install_sh) -c +INSTALL_HEADER = $(INSTALL_DATA) +transform = $(program_transform_name) +NORMAL_INSTALL = : +PRE_INSTALL = : +POST_INSTALL = : +NORMAL_UNINSTALL = : +PRE_UNINSTALL = : +POST_UNINSTALL = : +subdir = docs/kdebase/faq +DIST_COMMON = $(srcdir)/Makefile.am $(srcdir)/Makefile.in +ACLOCAL_M4 = $(top_srcdir)/aclocal.m4 +am__aclocal_m4_deps = $(top_srcdir)/acinclude.m4 \ + $(top_srcdir)/configure.in +am__configure_deps = $(am__aclocal_m4_deps) $(CONFIGURE_DEPENDENCIES) \ + $(ACLOCAL_M4) +mkinstalldirs = $(SHELL) $(top_srcdir)/mkinstalldirs +CONFIG_HEADER = $(top_builddir)/config.h +CONFIG_CLEAN_FILES = +SOURCES = +DIST_SOURCES = +#>- RECURSIVE_TARGETS = all-recursive check-recursive dvi-recursive \ +#>- html-recursive info-recursive install-data-recursive \ +#>- install-dvi-recursive install-exec-recursive \ +#>- install-html-recursive install-info-recursive \ +#>- install-pdf-recursive install-ps-recursive install-recursive \ +#>- installcheck-recursive installdirs-recursive pdf-recursive \ +#>- ps-recursive uninstall-recursive +#>+ 7 +RECURSIVE_TARGETS = all-recursive check-recursive dvi-recursive \ + html-recursive info-recursive install-data-recursive \ + install-dvi-recursive install-exec-recursive \ + install-html-recursive install-info-recursive \ + install-pdf-recursive install-ps-recursive install-recursive \ + installcheck-recursive installdirs-recursive pdf-recursive \ + ps-recursive uninstall-recursive nmcheck-recursive bcheck-recursive +RECURSIVE_CLEAN_TARGETS = mostlyclean-recursive clean-recursive \ + distclean-recursive maintainer-clean-recursive +ETAGS = etags +CTAGS = ctags +DIST_SUBDIRS = $(SUBDIRS) +#>- DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST) +#>+ 1 +DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST) $(KDE_DIST) +ACLOCAL = @ACLOCAL@ +AMTAR = @AMTAR@ +ARTSCCONFIG = @ARTSCCONFIG@ +AUTOCONF = @AUTOCONF@ +AUTODIRS = @AUTODIRS@ +AUTOHEADER = @AUTOHEADER@ +AUTOMAKE = @AUTOMAKE@ +AWK = @AWK@ +CONF_FILES = @CONF_FILES@ +CYGPATH_W = @CYGPATH_W@ +DCOPIDL = @DCOPIDL@ +DCOPIDL2CPP = @DCOPIDL2CPP@ +DCOPIDLNG = @DCOPIDLNG@ +DCOP_DEPENDENCIES = @DCOP_DEPENDENCIES@ +DEFS = @DEFS@ +ECHO_C = @ECHO_C@ +ECHO_N = @ECHO_N@ +ECHO_T = @ECHO_T@ +GMSGFMT = @GMSGFMT@ +INSTALL = @INSTALL@ +INSTALL_DATA = @INSTALL_DATA@ +INSTALL_PROGRAM = @INSTALL_PROGRAM@ +INSTALL_SCRIPT = @INSTALL_SCRIPT@ +INSTALL_STRIP_PROGRAM = @INSTALL_STRIP_PROGRAM@ +KCFG_DEPENDENCIES = @KCFG_DEPENDENCIES@ +KCONFIG_COMPILER = @KCONFIG_COMPILER@ +KDECONFIG = @KDECONFIG@ +KDE_EXTRA_RPATH = @KDE_EXTRA_RPATH@ +KDE_RPATH = @KDE_RPATH@ +KDE_XSL_STYLESHEET = @KDE_XSL_STYLESHEET@ +LIBOBJS = @LIBOBJS@ +LIBS = @LIBS@ +LN_S = @LN_S@ +LTLIBOBJS = @LTLIBOBJS@ +MAKEINFO = @MAKEINFO@ +MAKEKDEWIDGETS = @MAKEKDEWIDGETS@ +MCOPIDL = @MCOPIDL@ +MEINPROC = @MEINPROC@ +MKDIR_P = @MKDIR_P@ +MSGFMT = @MSGFMT@ +PACKAGE = @PACKAGE@ +PACKAGE_BUGREPORT = @PACKAGE_BUGREPORT@ +PACKAGE_NAME = @PACKAGE_NAME@ +PACKAGE_STRING = @PACKAGE_STRING@ +PACKAGE_TARNAME = @PACKAGE_TARNAME@ +PACKAGE_VERSION = @PACKAGE_VERSION@ +PATH_SEPARATOR = @PATH_SEPARATOR@ +SET_MAKE = @SET_MAKE@ +SHELL = @SHELL@ +STRIP = @STRIP@ +TOPSUBDIRS = @TOPSUBDIRS@ +VERSION = @VERSION@ +XGETTEXT = @XGETTEXT@ +XMLLINT = @XMLLINT@ +X_RPATH = @X_RPATH@ +abs_builddir = @abs_builddir@ +abs_srcdir = @abs_srcdir@ +abs_top_builddir = @abs_top_builddir@ +abs_top_srcdir = @abs_top_srcdir@ +am__leading_dot = @am__leading_dot@ +am__tar = @am__tar@ +am__untar = @am__untar@ +#>- bindir = @bindir@ +#>+ 2 +DEPDIR = .deps +bindir = @bindir@ +build_alias = @build_alias@ +builddir = @builddir@ +datadir = @datadir@ +datarootdir = @datarootdir@ +docdir = @docdir@ +dvidir = @dvidir@ +exec_prefix = @exec_prefix@ +host_alias = @host_alias@ +htmldir = @htmldir@ +includedir = @includedir@ +infodir = @infodir@ +install_sh = @install_sh@ +kde_appsdir = @kde_appsdir@ +kde_bindir = @kde_bindir@ +kde_confdir = @kde_confdir@ +kde_datadir = @kde_datadir@ +kde_htmldir = @kde_htmldir@ +kde_icondir = @kde_icondir@ +kde_kcfgdir = @kde_kcfgdir@ +kde_libs_htmldir = @kde_libs_htmldir@ +kde_libs_prefix = @kde_libs_prefix@ +kde_locale = @kde_locale@ +kde_mimedir = @kde_mimedir@ +kde_moduledir = @kde_moduledir@ +kde_servicesdir = @kde_servicesdir@ +kde_servicetypesdir = @kde_servicetypesdir@ +kde_sounddir = @kde_sounddir@ +kde_styledir = @kde_styledir@ +kde_templatesdir = @kde_templatesdir@ +kde_wallpaperdir = @kde_wallpaperdir@ +kde_widgetdir = @kde_widgetdir@ +kdeinitdir = @kdeinitdir@ +libdir = @libdir@ +libexecdir = @libexecdir@ +localedir = @localedir@ +localstatedir = @localstatedir@ +mandir = @mandir@ +mkdir_p = @mkdir_p@ +oldincludedir = @oldincludedir@ +pdfdir = @pdfdir@ +prefix = @prefix@ +program_transform_name = @program_transform_name@ +psdir = @psdir@ +sbindir = @sbindir@ +sharedstatedir = @sharedstatedir@ +srcdir = @srcdir@ +sysconfdir = @sysconfdir@ +target_alias = @target_alias@ +top_builddir = @top_builddir@ +top_srcdir = @top_srcdir@ +xdg_appsdir = @xdg_appsdir@ +xdg_directorydir = @xdg_directorydir@ +xdg_menudir = @xdg_menudir@ +KDE_LANG = en_GB +#>- SUBDIRS = $(AUTODIRS) +#>+ 1 +SUBDIRS =. +KDE_DOCS = khelpcenter/faq +KDE_MANS = AUTO +#>- all: all-recursive +#>+ 1 +all: docs-am all-recursive + +.SUFFIXES: +$(srcdir)/Makefile.in: $(srcdir)/Makefile.am $(am__configure_deps) +#>- @for dep in $?; do \ +#>- case '$(am__configure_deps)' in \ +#>- *$$dep*) \ +#>- cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh \ +#>- && exit 0; \ +#>- exit 1;; \ +#>- esac; \ +#>- done; \ +#>- echo ' cd $(top_srcdir) && $(AUTOMAKE) --gnu docs/kdebase/faq/Makefile'; \ +#>- cd $(top_srcdir) && \ +#>- $(AUTOMAKE) --gnu docs/kdebase/faq/Makefile +#>+ 12 + @for dep in $?; do \ + case '$(am__configure_deps)' in \ + *$$dep*) \ + cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh \ + && exit 0; \ + exit 1;; \ + esac; \ + done; \ + echo ' cd $(top_srcdir) && $(AUTOMAKE) --gnu docs/kdebase/faq/Makefile'; \ + cd $(top_srcdir) && \ + $(AUTOMAKE) --gnu docs/kdebase/faq/Makefile + cd $(top_srcdir) && perl ../scripts/admin/am_edit -p../scripts/admin docs/kdebase/faq/Makefile.in +.PRECIOUS: Makefile +Makefile: $(srcdir)/Makefile.in $(top_builddir)/config.status + @case '$?' in \ + *config.status*) \ + cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh;; \ + *) \ + echo ' cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__depfiles_maybe)'; \ + cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__depfiles_maybe);; \ + esac; + +$(top_builddir)/config.status: $(top_srcdir)/configure $(CONFIG_STATUS_DEPENDENCIES) + cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh + +$(top_srcdir)/configure: $(am__configure_deps) + cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh +$(ACLOCAL_M4): $(am__aclocal_m4_deps) + cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh + +# This directory's subdirectories are mostly independent; you can cd +# into them and run `make' without going through this Makefile. +# To change the values of `make' variables: instead of editing Makefiles, +# (1) if the variable is set in `config.status', edit `config.status' +# (which will cause the Makefiles to be regenerated when you run `make'); +# (2) otherwise, pass the desired values on the `make' command line. +$(RECURSIVE_TARGETS): + @failcom='exit 1'; \ + for f in x $$MAKEFLAGS; do \ + case $$f in \ + *=* | --[!k]*);; \ + *k*) failcom='fail=yes';; \ + esac; \ + done; \ + dot_seen=no; \ + target=`echo $@ | sed s/-recursive//`; \ + list='$(SUBDIRS)'; for subdir in $$list; do \ + echo "Making $$target in $$subdir"; \ + if test "$$subdir" = "."; then \ + dot_seen=yes; \ + local_target="$$target-am"; \ + else \ + local_target="$$target"; \ + fi; \ + (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS) $$local_target) \ + || eval $$failcom; \ + done; \ + if test "$$dot_seen" = "no"; then \ + $(MAKE) $(AM_MAKEFLAGS) "$$target-am" || exit 1; \ + fi; test -z "$$fail" + +$(RECURSIVE_CLEAN_TARGETS): + @failcom='exit 1'; \ + for f in x $$MAKEFLAGS; do \ + case $$f in \ + *=* | --[!k]*);; \ + *k*) failcom='fail=yes';; \ + esac; \ + done; \ + dot_seen=no; \ + case "$@" in \ + distclean-* | maintainer-clean-*) list='$(DIST_SUBDIRS)' ;; \ + *) list='$(SUBDIRS)' ;; \ + esac; \ + rev=''; for subdir in $$list; do \ + if test "$$subdir" = "."; then :; else \ + rev="$$subdir $$rev"; \ + fi; \ + done; \ + rev="$$rev ."; \ + target=`echo $@ | sed s/-recursive//`; \ + for subdir in $$rev; do \ + echo "Making $$target in $$subdir"; \ + if test "$$subdir" = "."; then \ + local_target="$$target-am"; \ + else \ + local_target="$$target"; \ + fi; \ + (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS) $$local_target) \ + || eval $$failcom; \ + done && test -z "$$fail" +tags-recursive: + list='$(SUBDIRS)'; for subdir in $$list; do \ + test "$$subdir" = . || (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS) tags); \ + done +ctags-recursive: + list='$(SUBDIRS)'; for subdir in $$list; do \ + test "$$subdir" = . || (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS) ctags); \ + done + +ID: $(HEADERS) $(SOURCES) $(LISP) $(TAGS_FILES) + list='$(SOURCES) $(HEADERS) $(LISP) $(TAGS_FILES)'; \ + unique=`for i in $$list; do \ + if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \ + done | \ + $(AWK) '{ files[$$0] = 1; nonemtpy = 1; } \ + END { if (nonempty) { for (i in files) print i; }; }'`; \ + mkid -fID $$unique +tags: TAGS + +TAGS: tags-recursive $(HEADERS) $(SOURCES) $(TAGS_DEPENDENCIES) \ + $(TAGS_FILES) $(LISP) + tags=; \ + here=`pwd`; \ + if ($(ETAGS) --etags-include --version) >/dev/null 2>&1; then \ + include_option=--etags-include; \ + empty_fix=.; \ + else \ + include_option=--include; \ + empty_fix=; \ + fi; \ + list='$(SUBDIRS)'; for subdir in $$list; do \ + if test "$$subdir" = .; then :; else \ + test ! -f $$subdir/TAGS || \ + tags="$$tags $$include_option=$$here/$$subdir/TAGS"; \ + fi; \ + done; \ + list='$(SOURCES) $(HEADERS) $(LISP) $(TAGS_FILES)'; \ + unique=`for i in $$list; do \ + if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \ + done | \ + $(AWK) '{ files[$$0] = 1; nonempty = 1; } \ + END { if (nonempty) { for (i in files) print i; }; }'`; \ + if test -z "$(ETAGS_ARGS)$$tags$$unique"; then :; else \ + test -n "$$unique" || unique=$$empty_fix; \ + $(ETAGS) $(ETAGSFLAGS) $(AM_ETAGSFLAGS) $(ETAGS_ARGS) \ + $$tags $$unique; \ + fi +ctags: CTAGS +CTAGS: ctags-recursive $(HEADERS) $(SOURCES) $(TAGS_DEPENDENCIES) \ + $(TAGS_FILES) $(LISP) + tags=; \ + list='$(SOURCES) $(HEADERS) $(LISP) $(TAGS_FILES)'; \ + unique=`for i in $$list; do \ + if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \ + done | \ + $(AWK) '{ files[$$0] = 1; nonempty = 1; } \ + END { if (nonempty) { for (i in files) print i; }; }'`; \ + test -z "$(CTAGS_ARGS)$$tags$$unique" \ + || $(CTAGS) $(CTAGSFLAGS) $(AM_CTAGSFLAGS) $(CTAGS_ARGS) \ + $$tags $$unique + +GTAGS: + here=`$(am__cd) $(top_builddir) && pwd` \ + && cd $(top_srcdir) \ + && gtags -i $(GTAGS_ARGS) $$here + +distclean-tags: + -rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags + +#>- distdir: $(DISTFILES) +#>+ 1 +distdir: distdir-nls $(DISTFILES) + @srcdirstrip=`echo "$(srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \ + topsrcdirstrip=`echo "$(top_srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \ + list='$(DISTFILES)'; \ + dist_files=`for file in $$list; do echo $$file; done | \ + sed -e "s|^$$srcdirstrip/||;t" \ + -e "s|^$$topsrcdirstrip/|$(top_builddir)/|;t"`; \ + case $$dist_files in \ + */*) $(MKDIR_P) `echo "$$dist_files" | \ + sed '/\//!d;s|^|$(distdir)/|;s,/[^/]*$$,,' | \ + sort -u` ;; \ + esac; \ + for file in $$dist_files; do \ + if test -f $$file || test -d $$file; then d=.; else d=$(srcdir); fi; \ + if test -d $$d/$$file; then \ + dir=`echo "/$$file" | sed -e 's,/[^/]*$$,,'`; \ + if test -d $(srcdir)/$$file && test $$d != $(srcdir); then \ + cp -pR $(srcdir)/$$file $(distdir)$$dir || exit 1; \ + fi; \ + cp -pR $$d/$$file $(distdir)$$dir || exit 1; \ + else \ + test -f $(distdir)/$$file \ + || cp -p $$d/$$file $(distdir)/$$file \ + || exit 1; \ + fi; \ + done + list='$(DIST_SUBDIRS)'; for subdir in $$list; do \ + if test "$$subdir" = .; then :; else \ + test -d "$(distdir)/$$subdir" \ + || $(MKDIR_P) "$(distdir)/$$subdir" \ + || exit 1; \ + distdir=`$(am__cd) $(distdir) && pwd`; \ + top_distdir=`$(am__cd) $(top_distdir) && pwd`; \ + (cd $$subdir && \ + $(MAKE) $(AM_MAKEFLAGS) \ + top_distdir="$$top_distdir" \ + distdir="$$distdir/$$subdir" \ + am__remove_distdir=: \ + am__skip_length_check=: \ + distdir) \ + || exit 1; \ + fi; \ + done +check-am: all-am +check: check-recursive +all-am: Makefile +installdirs: installdirs-recursive +installdirs-am: +install: install-recursive +install-exec: install-exec-recursive +install-data: install-data-recursive +#>- uninstall: uninstall-recursive +#>+ 1 +uninstall: uninstall-docs uninstall-nls uninstall-recursive + +install-am: all-am + @$(MAKE) $(AM_MAKEFLAGS) install-exec-am install-data-am + +installcheck: installcheck-recursive +install-strip: + $(MAKE) $(AM_MAKEFLAGS) INSTALL_PROGRAM="$(INSTALL_STRIP_PROGRAM)" \ + install_sh_PROGRAM="$(INSTALL_STRIP_PROGRAM)" INSTALL_STRIP_FLAG=-s \ + `test -z '$(STRIP)' || \ + echo "INSTALL_PROGRAM_ENV=STRIPPROG='$(STRIP)'"` install +mostlyclean-generic: + +clean-generic: + +distclean-generic: + -test -z "$(CONFIG_CLEAN_FILES)" || rm -f $(CONFIG_CLEAN_FILES) + +maintainer-clean-generic: + @echo "This command is intended for maintainers to use" + @echo "it deletes files that may require special tools to rebuild." +#>- clean: clean-recursive +#>+ 1 +clean: kde-rpo-clean clean-recursive + +#>- clean-am: clean-generic mostlyclean-am +#>+ 1 +clean-am: clean-docs clean-bcheck clean-generic mostlyclean-am + +distclean: distclean-recursive + -rm -f Makefile +distclean-am: clean-am distclean-generic distclean-tags + +dvi: dvi-recursive + +dvi-am: + +html: html-recursive + +info: info-recursive + +info-am: + +#>- install-data-am: +#>+ 1 +install-data-am: install-docs install-nls + +install-dvi: install-dvi-recursive + +install-exec-am: + +install-html: install-html-recursive + +install-info: install-info-recursive + +install-man: + +install-pdf: install-pdf-recursive + +install-ps: install-ps-recursive + +installcheck-am: + +maintainer-clean: maintainer-clean-recursive + -rm -f Makefile +maintainer-clean-am: distclean-am maintainer-clean-generic + +mostlyclean: mostlyclean-recursive + +mostlyclean-am: mostlyclean-generic + +pdf: pdf-recursive + +pdf-am: + +ps: ps-recursive + +ps-am: + +uninstall-am: + +.MAKE: $(RECURSIVE_CLEAN_TARGETS) $(RECURSIVE_TARGETS) install-am \ + install-strip + +.PHONY: $(RECURSIVE_CLEAN_TARGETS) $(RECURSIVE_TARGETS) CTAGS GTAGS \ + all all-am check check-am clean clean-generic ctags \ + ctags-recursive distclean distclean-generic distclean-tags \ + distdir dvi dvi-am html html-am info info-am install \ + install-am install-data install-data-am install-dvi \ + install-dvi-am install-exec install-exec-am install-html \ + install-html-am install-info install-info-am install-man \ + install-pdf install-pdf-am install-ps install-ps-am \ + install-strip installcheck installcheck-am installdirs \ + installdirs-am maintainer-clean maintainer-clean-generic \ + mostlyclean mostlyclean-generic pdf pdf-am ps ps-am tags \ + tags-recursive uninstall uninstall-am + +# Tell versions [3.59,3.63) of GNU make to not export all variables. +# Otherwise a system limit (for SysV at least) may be exceeded. +.NOEXPORT: + +#>+ 2 +KDE_DIST=desktop.docbook moreinfo.docbook about.docbook configkde.docbook install.docbook winmng.docbook Makefile.in contrib.docbook tips.docbook nonkdeapps.docbook getkde.docbook intro.docbook index.docbook notrelated.docbook panel.docbook filemng.docbook kdeapps.docbook Makefile.am misc.docbook index.cache.bz2 + +#>+ 24 +index.cache.bz2: $(srcdir)/index.docbook $(KDE_XSL_STYLESHEET) misc.docbook tips.docbook panel.docbook contrib.docbook intro.docbook kdeapps.docbook nonkdeapps.docbook winmng.docbook notrelated.docbook index.docbook about.docbook desktop.docbook install.docbook configkde.docbook getkde.docbook filemng.docbook moreinfo.docbook + @if test -n "$(MEINPROC)"; then echo $(MEINPROC) --check --cache index.cache.bz2 $(srcdir)/index.docbook; $(MEINPROC) --check --cache index.cache.bz2 $(srcdir)/index.docbook; fi + +docs-am: index.cache.bz2 + +install-docs: docs-am install-nls + $(mkinstalldirs) $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/faq + @if test -f index.cache.bz2; then \ + echo $(INSTALL_DATA) index.cache.bz2 $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/faq/; \ + $(INSTALL_DATA) index.cache.bz2 $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/faq/; \ + elif test -f $(srcdir)/index.cache.bz2; then \ + echo $(INSTALL_DATA) $(srcdir)/index.cache.bz2 $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/faq/; \ + $(INSTALL_DATA) $(srcdir)/index.cache.bz2 $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/faq/; \ + fi + -rm -f $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/faq/common + $(LN_S) $(kde_libs_htmldir)/$(KDE_LANG)/common $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/faq/common + +uninstall-docs: + -rm -rf $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/faq + +clean-docs: + -rm -f index.cache.bz2 + + +#>+ 13 +install-nls: + $(mkinstalldirs) $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/faq + @for base in misc.docbook tips.docbook panel.docbook contrib.docbook intro.docbook kdeapps.docbook nonkdeapps.docbook winmng.docbook notrelated.docbook index.docbook about.docbook desktop.docbook install.docbook configkde.docbook getkde.docbook filemng.docbook moreinfo.docbook ; do \ + echo $(INSTALL_DATA) $$base $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/faq/$$base ;\ + $(INSTALL_DATA) $(srcdir)/$$base $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/faq/$$base ;\ + done + +uninstall-nls: + for base in misc.docbook tips.docbook panel.docbook contrib.docbook intro.docbook kdeapps.docbook nonkdeapps.docbook winmng.docbook notrelated.docbook index.docbook about.docbook desktop.docbook install.docbook configkde.docbook getkde.docbook filemng.docbook moreinfo.docbook ; do \ + rm -f $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/khelpcenter/faq/$$base ;\ + done + + +#>+ 5 +distdir-nls: + for file in misc.docbook tips.docbook panel.docbook contrib.docbook intro.docbook kdeapps.docbook nonkdeapps.docbook winmng.docbook notrelated.docbook index.docbook about.docbook desktop.docbook install.docbook configkde.docbook getkde.docbook filemng.docbook moreinfo.docbook ; do \ + cp $(srcdir)/$$file $(distdir); \ + done + +#>+ 15 +force-reedit: + @for dep in $?; do \ + case '$(am__configure_deps)' in \ + *$$dep*) \ + cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh \ + && exit 0; \ + exit 1;; \ + esac; \ + done; \ + echo ' cd $(top_srcdir) && $(AUTOMAKE) --gnu docs/kdebase/faq/Makefile'; \ + cd $(top_srcdir) && \ + $(AUTOMAKE) --gnu docs/kdebase/faq/Makefile + cd $(top_srcdir) && perl ../scripts/admin/am_edit -p../scripts/admin docs/kdebase/faq/Makefile.in + + +#>+ 21 +clean-bcheck: + rm -f *.bchecktest.cc *.bchecktest.cc.class a.out + +bcheck: bcheck-recursive + +bcheck-am: + @for i in ; do \ + if test $(srcdir)/$$i -nt $$i.bchecktest.cc; then \ + echo "int main() {return 0;}" > $$i.bchecktest.cc ; \ + echo "#include \"$$i\"" >> $$i.bchecktest.cc ; \ + echo "$$i"; \ + if ! $(CXX) $(DEFS) -I. -I$(srcdir) -I$(top_builddir) $(INCLUDES) $(AM_CPPFLAGS) $(CPPFLAGS) $(CXXFLAGS) $(KDE_CXXFLAGS) --dump-class-hierarchy -c $$i.bchecktest.cc; then \ + rm -f $$i.bchecktest.cc; exit 1; \ + fi ; \ + echo "" >> $$i.bchecktest.cc.class; \ + perl $(top_srcdir)/admin/bcheck.pl $$i.bchecktest.cc.class || { rm -f $$i.bchecktest.cc; exit 1; }; \ + rm -f a.out; \ + fi ; \ + done + + +#>+ 3 +final: + $(MAKE) all-am + +#>+ 3 +final-install: + $(MAKE) install-am + +#>+ 3 +no-final: + $(MAKE) all-am + +#>+ 3 +no-final-install: + $(MAKE) install-am + +#>+ 3 +kde-rpo-clean: + -rm -f *.rpo + +#>+ 3 +nmcheck: +nmcheck-am: nmcheck diff --git a/tde-i18n-en_GB/docs/kdebase/faq/about.docbook b/tde-i18n-en_GB/docs/kdebase/faq/about.docbook new file mode 100644 index 00000000000..02fc73b3111 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdebase/faq/about.docbook @@ -0,0 +1,69 @@ +<!-- +<?xml version="1.0" ?> +<!DOCTYPE chapter PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" + "dtd/kdex.dtd"> +--> + +<chapter id="about"> +<title +>About this <acronym +>FAQ</acronym +></title> + +<qandaset> +<qandaentry> +<question> +<para +>What can I do to help out with this <acronym +>FAQ</acronym +>?</para> +</question> + +<answer> + +<para +>First, send us any errors that you may find. Also, any suggestions that you might have, are appreciated. Better yet, send us everything that you think is unclear, and if possible, send us what you think would be a clearer solution. Our email address is <email +>kde-doc-english@kde.org</email +>. </para> + +<para +>Second, send us your solutions of those frequently-asked questions which are still not in this <acronym +>FAQ</acronym +>. We will put them in as soon as possible.</para> + +<para +>Last but not least, please make full use of this <acronym +>FAQ</acronym +>. Read this <acronym +>FAQ</acronym +> (and other relevant documentation) well before asking questions on the various &kde; mailing lists or newsgroups.</para> + +<note +><para +>You might also want to consider becoming a <acronym +>FAQ</acronym +> maintainer. Please refer to <xref linkend="FAQ-maintainer-HOWTO"/> for more details. </para +></note> + +</answer> +</qandaentry> + +<qandaentry> +<question id="FAQ-maintainer-HOWTO"> +<para +>How do I become a <acronym +>FAQ</acronym +> maintainer?</para> +</question> + +<answer> +<para +>Actually, it is very easy to become an <acronym +>FAQ</acronym +> maintainer, and we are always in need of fresh blood. :-) Just send us an email at <email +>kde-doc-english@kde.org</email +>. </para> +</answer> +</qandaentry> +</qandaset> +</chapter> diff --git a/tde-i18n-en_GB/docs/kdebase/faq/configkde.docbook b/tde-i18n-en_GB/docs/kdebase/faq/configkde.docbook new file mode 100644 index 00000000000..c819342b0ff --- /dev/null +++ b/tde-i18n-en_GB/docs/kdebase/faq/configkde.docbook @@ -0,0 +1,352 @@ +<!-- +<?xml version="1.0" ?> +<!DOCTYPE chapter PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" "dtd/kdex.dtd"> +--> +<chapter id="configure"> +<title +>Configuring &kde;</title> + +<qandaset> +<qandaentry> +<question> +<para +>How do I set the language used by &kde;?</para> +</question> + +<answer> +<para +>There are two ways to set the language &kde; uses in the messages it will display:</para> + +<variablelist> +<varlistentry +><term +>Using the <application +>&kde; Control Centre</application +></term> +<listitem +><para +>Fire up the <application +>&kde; Control Centre</application +> and select <guimenu +>Regional & Accessibility</guimenu +> followed by <guimenuitem +>Country/Region & Language</guimenuitem +>. You can select your language and location here. If &kde; cannot find a translation in the first language chosen, it will fall back on the default language. This is usually (American) English by default.</para> +<note +><para +>Using the <application +>&kde; Control Centre</application +> is the preferred way of choosing languages in &kde;.</para +></note +></listitem> +</varlistentry> +<varlistentry +><term +>Using the <envar +>LANG</envar +> environment variable</term> +<listitem +><para +>The second method uses the standard locale setting on your system. To change the language, simply set the environment variable <envar +>LANG</envar +> accordingly. For example, if your shell is <application +>bash</application +>, execute <userinput +><command +>export</command +> <envar +>LANG</envar +>=de</userinput +> to set German as the language used.</para +></listitem> +</varlistentry> +</variablelist> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>Is there any keyboard switcher for international keyboards for &kde;?</para> +</question> +<answer> +<para +>Yes, you can configure it using the <application +>&kde; Control Centre</application +> <guimenu +>Regional & Accessibility</guimenu +> <guimenuitem +>Keyboard Layout</guimenuitem +> configuration page. </para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>How do I replace the standard text login screen with the &kde; login screen?</para> +</question> +<answer> +<note +><para +>Your distribution/&UNIX; flavour may have its own setup tools to change this (⪚ <application +>YaST</application +> on &SuSE; &Linux;). This will be the safest way to enable the &kde; login screen. However, if for some reason you do not wish to use these tools, the following instructions may be useful.</para +></note> +<para +>First, you need to change to the <quote +>xdm runlevel</quote +> (runlevel 5 on &RedHat; and &SuSE; systems) by editing your <filename +>/etc/inittab</filename +> file. In the file, you should have a line saying <userinput +>id:3:initdefault:</userinput +>. Change it to <userinput +>id:5:initdefault:</userinput +>. Now, at the end of the file, comment out the following line: <literal +>x:5:respawn:/usr/bin/X11/xdm -nodaemon</literal +> and replace it with <userinput +>x:5:respawn:<replaceable +>/opt/kde/</replaceable +>bin/kdm -nodaemon</userinput +>. <note +><para +>The location of &kdm; may differ on your system.</para +></note +></para> +<para +>For changes to take effect immediately, type <command +>init 5</command +> (for &RedHat; systems) at the shell prompt. <caution +><para +>It is risky to initiate a graphical login without checking beforehand whether it works. If it fails to work, you would be in for a hard time getting back....</para +></caution +></para> +</answer> +<answer> +<para +>For FreeBSD, you should edit the file <filename +>/etc/ttys</filename +> and change one of the lines that look like <programlisting +>ttyv8 "/usr/X11R6/bin/xdm -nodaemon" xterm off secure</programlisting +> to instead say <userinput +>ttyv8 "/usr/local/bin/kdm -nodaemon" xterm off secure</userinput +>.</para> +</answer> +</qandaentry> + +<qandaentry> +<question> + +<para +>I would like to click the &LMB; anywhere on the desktop and have the <guimenu +>K</guimenu +> menu displayed.</para> +</question> +<answer> +<para +>Open the <application +>&kde; Control Centre</application +> and choose <menuchoice +><guisubmenu +>Desktop</guisubmenu +> <guisubmenu +>Behaviour</guisubmenu +></menuchoice +>. You can now choose the behaviour of mouse clicks on the desktop. To have the <guimenu +>K</guimenu +> menu open from a single &LMB; click, change the entry labelled <guilabel +>Left button</guilabel +> to say <guilabel +>Application Menu</guilabel +>.</para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>Where do I find information regarding &kde; themes?</para> +</question> +<answer> +<para +>Go to <ulink url="http://kde.themes.org/" +>http://kde.themes.org/</ulink +> or <ulink url="http://www.kde-look.org" +>http://www.kde-look.org</ulink +>.</para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>How do I change &MIME; Types?</para> +</question> +<answer> +<para +>If you are using &konqueror;, do this instead: first, open a &konqueror; window and choose <menuchoice +><guimenu +>Settings</guimenu +><guimenuitem +>Configure Konqueror</guimenuitem +></menuchoice +>, then <guilabel +>File Associations</guilabel +>. Find the type you want to change (⪚ <literal +>text/english</literal +> or <literal +>image/gif</literal +>), and set the application preference order to whatever you want.</para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>&kde; (&kdm;) does not read my <filename +>.bash_profile</filename +>!</para> +</question> +<answer> +<para +>The login managers<application +>xdm</application +> and &kdm; do not run a login shell, so <filename +>.profile</filename +>, <filename +>.bash_profile</filename +>, &etc; are not sourced. When the user logs in, <application +>xdm</application +> runs <command +>Xstartup</command +> as root and then <command +>Xsession</command +> as user. So the normal practice is to add statements in <filename +>Xsession</filename +> to source the user profile. Please edit your <filename +>Xsession</filename +> and <filename +>.xsession</filename +> files.</para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>How do I use &TrueType; fonts in &kde;?</para> +</question> +<answer> + +<para +>You need to install &TrueType; font support into your &X-Window; configuration. Please take a look at <ulink url="http://x.themes.org/" +>x.themes.org</ulink +> for the fonts, and <ulink url="http://www.dcs.ed.ac.uk/home/jec/programs/xfsft/" +>xfsft: &TrueType; Font Support For X11</ulink +> or <ulink url="http://X-TT.dsl.gr.jp/" +>X-&TrueType; Server Project Home Page</ulink +> for the font servers.</para> + +<para +>If you have a bunch of &TrueType; fonts from &Microsoft; &Windows;, edit the <filename +>XF86Config</filename +> file to get the fonts from the font folder. Then just tell &kde; to use these new fonts with the font administrator utility.</para> + +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>Is it possible to enter, show and work with the Euro Symbol in &kde;?</para> +</question> +<answer> +<para +>Yes and no. For details, look here: <ulink url="http://www.koffice.org/kword/euro.php" +>http://www.koffice.org/kword/euro.php</ulink +>.</para> +</answer> +</qandaentry> + +<qandaentry> +<question +><para +>How do I run a program at &kde; startup?</para +></question> + +<answer +><para +>There are many ways to do that. If what you want to do is to run some scripts that would set some environment variables (for example, to start <command +>gpg-agent</command +>, <command +>ssh-agent</command +> and others), you can put these scripts into <filename class="directory" +>$<envar +>KDEHOME</envar +>/env/</filename +> and make sure their names end in <literal role="extension" +>.sh</literal +>. $<envar +>KDEHOME</envar +> is usually a folder named <filename class="directory" +>.kde</filename +> (note the period at the beginning) in your home folder. If you want scripts to be executed for all &kde; users, you can put them under <filename class="directory" +>$<envar +>KDEDIR</envar +>/env/</filename +>, where $<envar +>KDEDIR</envar +> is the prefix &kde; was installed to (you can find this out using the command <userinput +><command +>kde-config</command +> --prefix</userinput +>).</para> +<para +>If you wish to start a program after &kde; has started, you may want to use the <filename class="directory" +>Autostart</filename +> folder. To add entries to the <filename class="directory" +>Autostart</filename +> folder: <orderedlist> +<listitem +><para +>Open &konqueror;.</para> +</listitem> +<listitem +><para +>Select <menuchoice +><guimenu +>Go</guimenu +><guimenuitem +>Autostart</guimenuitem +> </menuchoice +> from the menubar.</para> +</listitem> +<listitem +><para +>Right-click in the window view area and select <menuchoice +><guisubmenu +>Create New</guisubmenu +><guisubmenu +>File</guisubmenu +><guimenuitem +>Link to Application</guimenuitem +> </menuchoice +></para> +</listitem> +<listitem +><para +>Click on the <guilabel +>Application</guilabel +> tab in the window that appears and enter the name of the command to run in the <guilabel +>Command</guilabel +> text box.</para> +</listitem> +</orderedlist> +</para> + +</answer> +</qandaentry> + + +</qandaset> +</chapter> diff --git a/tde-i18n-en_GB/docs/kdebase/faq/contrib.docbook b/tde-i18n-en_GB/docs/kdebase/faq/contrib.docbook new file mode 100644 index 00000000000..8bff6911cd5 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdebase/faq/contrib.docbook @@ -0,0 +1,249 @@ +<!-- +<?xml version="1.0" ?> +<!DOCTYPE chapter PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" + "dtd/kdex.dtd"> +--> + + +<chapter id="contribute"> +<title +>Contributing</title> + +<qandaset> +<qandaentry> +<question> +<para +>How can I contribute to &kde;?</para> +</question> +<answer> +<para +>&kde; is a free software project that lives from voluntary contributions. Everybody is encouraged to contribute to &kde;. Not only programmers are welcome. There are many ways in which you can help to improve &kde;:</para> +<itemizedlist> +<listitem +><para +>Test the software.</para +></listitem> +<listitem +><para +>Send in bug reports. For more information on this, see <link linkend="bug-report" +>How do I submit a bug report?</link +>.</para +></listitem> +<listitem +><para +>Write documentation or help files. You can get some information by visiting the <ulink url="http://i18n.kde.org/doc/" +>&kde; Editorial Team Home Page</ulink +>.</para +></listitem> +<listitem +><para +>Translate programs, documentation, and help files. For more information on this, you should visit <ulink url="http://i18n.kde.org" +>The &kde; Translators' and Documenters' Web Site</ulink +>.</para +></listitem> +<listitem +><para +>Draw nice icons or compose sound effects. You can visit the <ulink url="http://artist.kde.org/" +>&kde; artists page</ulink +> to find out more.</para +></listitem> +<listitem +><para +>Write articles and books about &kde;. If you want to help spread the word about &kde;, simply send an email to <email +>kde-pr@kde.org</email +>. This will get you in touch with the &kde; public relations volunteers.</para +></listitem> +<listitem +><para +>Program new &kde; applications. Please refer to <xref linkend="programming"/> for more information.</para +></listitem> +<listitem +><para +>Of course, sponsors are also welcome. :-)</para +></listitem> +</itemizedlist> +<para +>There are several places to look for more information if you want to get involved in the development. The first step is to subscribe to some of the <ulink url="http://www.kde.org/mailinglists/" +>mailing lists</ulink +>. You will soon see something that can be improved or added.</para> +</answer> +</qandaentry> + +<qandaentry> +<question id="bug-report"> +<para +>How do I submit a bug report?</para> +</question> +<answer> +<para +>There is a bug tracking system available at <ulink url="http://bugs.kde.org" +>http://bugs.kde.org</ulink +>. The system features a wizard to submit new bug reports and a list of all known bugs.</para> +<para +>The easiest way to submit a bug is to select <menuchoice +><guimenu +>Help</guimenu +><guimenuitem +>Report Bug...</guimenuitem +></menuchoice +> from the menu bar of the application with the bug. This will open a small dialogue box with a link to the bug tracking system. Please make sure to follow the instructions of the bug reporting wizard.</para> +</answer> +</qandaentry> + +<qandaentry> +<question id="programming"> +<para +>I want to program for &kde;. What should I do first?</para> +</question> +<answer> +<para +>Everybody is encouraged to develop software for &kde;. What you should do first depends strongly on your experience, ⪚ whether you have already learned C++ or have experience with the &Qt; toolkit and so on.</para> +<para +>To get into &kde; programming, you will need some basic tools: <application +>automake</application +>, <application +>autoconf</application +>, and <application +>egcs</application +>. You should look to <ulink url="http://developer.kde.org/" +>http://developer.kde.org/</ulink +> for more tips.</para> +<para +>Another excellent resource for learning &kde; programming is the &Qt; online tutorials. These are installed along with &Qt;. To view them, open <filename +>$<envar +>QTDIR</envar +>/doc/html/index.html</filename +> in &konqueror; and bookmark it. The tutorials can be found under "Using Qt". The source code for each lesson can be found in the <filename class="directory" +>$<envar +>QTDIR</envar +>/tutorial</filename +> directory.</para> +<para +>There is, however, one thing that everybody interested in programming for &kde; should do: <emphasis +>subscribe to the developers mailing list</emphasis +>. To subscribe, you have to send an email to <ulink url="mailto:kde-devel-request@kde.org" +>kde-devel-request@kde.org</ulink +> with the subject <userinput +>subscribe <replaceable +>your_email_address</replaceable +></userinput +>. <important +><para +>Please read <link linkend="subscribe" +>How to subscribe/unsubscribe to these lists</link +> carefully. Everything said there applies to the development list as well.</para +></important +></para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>How do I get access to the <acronym +>CVS</acronym +>?</para> +</question> +<answer> +<para +>The &kde; project uses <acronym +>CVS</acronym +> to develop the core parts of the software. Usually, when you have changed one of the parts (⪚ fixed a bug), and you want to commit this change, the best way is to create a patch against a current snapshot and send this patch to the developer/maintainer of the respective program.</para> +<para +>If you are doing this more or less regularly, you can ask Stephan Kulow, <email +>coolo@kde.org</email +> for direct access to the <acronym +>CVS</acronym +> server. But be aware that more users will slow down <acronym +>CVS</acronym +> access for all developers, so we want to keep the number of people with direct <acronym +>CVS</acronym +> access reasonably small. But feel free to ask!</para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>I am just curious. Can I have read-only access to the <acronym +>CVS</acronym +>?</para> +</question> +<answer> +<para +>Yes. It is possible to get read-only access to the <acronym +>CVS</acronym +> repository with <application +>cvsup</application +> or <application +>cvs</application +> utility. You can find more information about how to set up <application +>cvsup</application +> for the &kde; repository from <ulink url="http://developer.kde.org/source/cvsup.html" +>How to use <application +>cvsup</application +> to get &kde;</ulink +>.</para> +<para +>In addition, anonymous <acronym +>CVS</acronym +> service is also available. To find out more about how to set up and use anonymous <acronym +>CVS</acronym +>, please see <ulink url="http://developer.kde.org/source/anoncvs.html" +>here</ulink +>.</para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>Are there any <application +>cvs</application +> mirror sites for &kde;?</para> +</question> +<answer> +<para +>Yes. The main &kde; server is normally very busy. Please take a look at <ulink url="http://developer.kde.org/source/cvsupmirrors.html" +>http://developer.kde.org/source/cvsupmirrors.html</ulink +> and <ulink url="http://developer.kde.org/source/anoncvs.html" +>http://developer.kde.org/source/anoncvs.html</ulink +> for the list of available mirrors.</para +> +<para +>Once you have selected a new <application +>cvsup</application +> server, simply replace <screen +> +*default host=cvs.kde.org +</screen +> with <screen +> +*default host=cvsup.your.new.host +</screen +> in your <application +>cvsup</application +> script.</para> +<para +>The instructions to change the anoncvs server can be found on <ulink url="http://developer.kde.org/source/anoncvs.html" +>http://developer.kde.org/source/anoncvs.html</ulink +>, too. </para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>How do I go about translating &kde; programs into my native language?</para> +</question> +<answer> +<para +>Look at the <ulink url="http://i18n.kde.org" +>The &kde; Translators' and Documenters' Web Site</ulink +> to see whether your program is already translated (most are). Otherwise you will find information there on how to do it yourself.</para> +</answer> +</qandaentry> +</qandaset> +</chapter> + + diff --git a/tde-i18n-en_GB/docs/kdebase/faq/desktop.docbook b/tde-i18n-en_GB/docs/kdebase/faq/desktop.docbook new file mode 100644 index 00000000000..b95a8a96dbc --- /dev/null +++ b/tde-i18n-en_GB/docs/kdebase/faq/desktop.docbook @@ -0,0 +1,151 @@ +<!-- +<?xml version="1.0" ?> +<!DOCTYPE chapter PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" + "dtd/kdex.dtd"> +--> + +<chapter id="desktop"> +<title +>The desktop</title> + +<qandaset> +<qandaentry> +<question> +<para +>How do I add an application to the desktop?</para> +</question> +<answer> + +<para +>Just choose the desired application from the <guimenu +>K</guimenu +> menu and drag and drop it to the Desktop. </para +> +<para +>For applications not listed in the <guimenu +>K</guimenu +> menu, use the &RMB; on the desktop and choose <menuchoice +><guimenuitem +>Create New</guimenuitem +><guisubmenu +>File</guisubmenu +> <guimenuitem +>Link to Application...</guimenuitem +></menuchoice +> and fill in the configuration for the application you want to link to. </para> + +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>How do I mount/unmount a device from the desktop?</para> +</question> +<answer> + +<para +>First, make sure you are allowed to <command +>mount</command +>/<command +>umount</command +> the relevant device as a user. </para> +<para +>Then you can add any device via &RMB; on the desktop and then choosing <guimenuitem +>Create New</guimenuitem +>. </para> + +</answer> +</qandaentry> + + +<qandaentry> +<question> +<para +>Where are the icons kept?</para> +</question> +<answer> +<para +>The icons can be found only in <filename class="directory" +>$<envar +>KDEDIRS</envar +>/share/icons</filename +> or <filename class="directory" +>$<envar +>HOME</envar +>/.kde/share/icons</filename +> or <filename class="directory" +>$<envar +>HOME</envar +>/.kde2/share/icons</filename +>. To use icons stored in other locations, you must either copy them into one of the above-mentioned fixed &kde; locations or make symlinks.</para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>How do I use the mouse scroll wheel in &kde;?</para> +</question> +<answer> +<para +>Mouse wheel support comes with &Qt; 2.0 and above, so &kde; based on that will automatically support the use of the mouse scroll wheel.</para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>Why can't I get system sound to work, like for opening windows?</para> +</question> +<answer> +<para +>System sound currently does not work on non-FreeBSD and non-&Linux; systems. This is being worked on. If you use FreeBSD or &Linux;, you have found a bug, so please report it.</para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>How do I launch applications in a particular desktop?</para> +</question> +<answer> +<para +>&kde; comes with a program called &kstart;. To start an <application +>xterm</application +> on the second desktop and then activate it use: <userinput +><command +>kstart</command +> <option +>--desktop 2 --activate --window "xterm" </option +>xterm</userinput +>.</para> +<para +>Note that the <option +>--window</option +> option is important. It takes an argument which is a regular expression matching the title of the window to apply the settings to.</para> +<para +>Please read <command +>kstart</command +> <option +>--help-all</option +> for more magic available with &kstart; (and there is an abundance). </para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>Where do I save my files if I want them to appear directly on the desktop?</para> +</question> +<answer> +<para +><filename class="directory" +>$<envar +>HOME</envar +>/Desktop</filename +>. You might need to refresh your desktop after you have saved your files.</para> +</answer> +</qandaentry> +</qandaset> +</chapter> diff --git a/tde-i18n-en_GB/docs/kdebase/faq/filemng.docbook b/tde-i18n-en_GB/docs/kdebase/faq/filemng.docbook new file mode 100644 index 00000000000..c37cb3ef23d --- /dev/null +++ b/tde-i18n-en_GB/docs/kdebase/faq/filemng.docbook @@ -0,0 +1,380 @@ +<!-- <?xml version="1.0" ?> +<!DOCTYPE chapter PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" + "dtd/kdex.dtd" +> --> + +<chapter id="filemanager"> +<title +>The File Manager and Web Browser</title> + +<para +>The file manager and web browser of &kde; is &konqueror;. The &konqueror; home page is located at <ulink url="http://www.konqueror.org" +>http://www.konqueror.org</ulink +> where a &konqueror; specific <acronym +>FAQ</acronym +> can be found.</para> + +<qandaset> +<qandaentry> +<question> +<para +>How do I use &konqueror; as a web browser with a proxy?</para> +</question> +<answer> +<para +>&konqueror; can be used with &HTTP; and &FTP; proxies. To set up the proxy server in &konqueror;, just select <menuchoice +><guimenu +>Settings</guimenu +><guisubmenu +>Configure &konqueror;...</guisubmenu +></menuchoice +> from the &konqueror; menu and go to the <guilabel +>Proxy</guilabel +> tab.</para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>How can I change the appearance of a folder in &konqueror;?</para> +</question> +<answer> +<para +>Right-click the folder, select <guimenuitem +>Properties</guimenuitem +>, click on the large icon in the dialogue which appears and choose another icon.</para> +<para +>To change the icon displayed for entries in the <guimenu +>K Menu</guimenu +>, use the <application +>Menu Editor</application +>, located at <menuchoice +><guisubmenu +>Settings</guisubmenu +><guimenuitem +>Menu Editor</guimenuitem +></menuchoice +>. </para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>How can I do non-anonymous &FTP; transfers with &konqueror;?</para> +</question> +<answer> +<para +>Normally, if you enter a &URL; like <userinput +>ftp://<replaceable +>ftp.somehost.com</replaceable +></userinput +>, &konqueror; will attempt an anonymous login to the &FTP; server. If you want to login as a particular user, enter a &URL; like <userinput +>ftp://<replaceable +>username@ftp.somehost.com</replaceable +></userinput +> instead. &konqueror; will ask for your password and connect to the server.</para> +</answer> +</qandaentry> + +<qandaentry +> <question +> <para +>What are <option +>%i</option +> and <option +>%m</option +> in the Execute line?</para +> </question +> <answer> +<para +>They are used by all &kde; applications (since they are implemented in <classname +>KApplication</classname +> and all good &kde; programs create a <classname +>KApplication</classname +> object before they even look at the command line arguments).</para +> <para +>A standard line for a &kde; application looks like this: <userinput +><command +>foo</command +> <option +>... %i %m -caption \"%c\"</option +></userinput +>. Pretty confusing, but it has been designed in that way so that it can integrate legacy, non-&kde; applications as smoothly as possible. &konqueror;, when executing the line above, will extend the command to <userinput +><command +><replaceable +>foo</replaceable +></command +> <option +>-icon something.png -miniicon something_mini.png -caption \"The Foo\"</option +></userinput +>. Both the icon and the mini-icon as well as "The Foo" are properties defined in the <filename +>.desktop</filename +> file. If the icons are not defined, they simply default to the executable name <replaceable +>foo</replaceable +>.</para> + +<para +>This way a user can change these things in &kmenuedit; for his or her applications. The <option +>-caption</option +> option is important, because no user will accept that the menu item <guimenuitem +>Editor</guimenuitem +> starts something called <guilabel +>kedit-0.9pl4-build47</guilabel +>. Instead, he expects a window called <guilabel +>Editor</guilabel +>. Furthermore these names are localised, <abbrev +>i.e.</abbrev +> an American user launches <guimenuitem +>CD-Player</guimenuitem +> and gets a window called <guilabel +>CD-Player</guilabel +> while a German user launches <guimenuitem +>CD-Spieler</guimenuitem +> and gets a window called <guilabel +>CD-Spieler</guilabel +>.</para> + +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>How do I specify the startup folder for &konqueror;?</para> +</question> +<answer> + +<para +>Using the &RMB;, click on the Home icon and choose <guimenuitem +>Properties</guimenuitem +>. Under the <guilabel +>Application</guilabel +> tab you will probably find something like <command +>kfmclient openProfile filemanagement</command +>; just append <filename class="directory" +>file:/whereever/you/want</filename +> with the folder you would like &konqueror; to start in.</para> + +</answer> +</qandaentry> + +<qandaentry> +<question id="nsbookmark"> +<para +>How do I import &Netscape; bookmarks?</para> +</question> +<answer> +<para +>There is no need to import anything at all. &Netscape; bookmarks are automatically available under the <guimenu +>Bookmarks</guimenu +> menu in &konqueror; with no configuration on your part necessary. The <application +>Bookmark Editor</application +> is able to convert &Netscape; bookmarks to the format used by &konqueror;, if you want this.</para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>How do I fool a site into believing &konqueror; is &Netscape; or some other browser?</para> +</question> +<answer> +<para +>In &konqueror;, select <menuchoice +><guimenu +>Settings</guimenu +><guimenuitem +>Configure Konqueror...</guimenuitem +></menuchoice +> and in the configuration dialogue, select <guilabel +>Browser Identification</guilabel +>. Default and site-specific browser identifications can be set from here.</para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>How do I configure &konqueror; to run &Java; applets?</para> +</question> +<answer> +<para +>Choose <menuchoice +><guimenu +>Settings</guimenu +><guimenuitem +>Configure &konqueror;...</guimenuitem +></menuchoice +> from &konqueror;'s menubar and then select <guilabel +>Java & Javascript</guilabel +>. Set the <guilabel +>Path to Java executable</guilabel +> correctly. If it doesn't work, please check the <ulink url="http://www.konqueror.org/javahowto/" +>Konqueror + Java HOWTO</ulink +>.</para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>What is this new <guilabel +>Smart</guilabel +> policy for JavaScript web popups?</para> +</question> +<answer> +<para +>This new policy attempts to block intrusive JavaScript popup windows. If the user does not click on a button or submit a form to trigger the popup, then the popup is not permitted. Some sites will open a second new window from within the first and in that case, the second window will not show. </para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>Why doesn't my banking site work with &konqueror;? It pops up a new window with the login screen in other browsers, but not in &konqueror;.</para> +</question> +<answer> +<para +>Make sure you have Javascript enabled, and the default JavaScript web popups policy set to <guilabel +>Ask</guilabel +> or <guilabel +>Allow</guilabel +>. The <guilabel +>Smart</guilabel +> policy is not always sufficient for some banks. Many banks also require &Java; support. You can find more help on enabling this at <ulink url="http://www.konqueror.org/" +>http://www.konqueror.org/</ulink +>. </para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>Why can't &konqueror; render &GIF; images?</para> +</question> +<answer> +<para +>It is because you did not enable &GIF; support in &Qt;. Please see <xref linkend="gif"/> for more details.</para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>How do I rename files?</para> +</question> +<answer> +<para +>Simply <mousebutton +>right</mousebutton +> click on the file and select <guimenuitem +>Rename</guimenuitem +> or click once on an already selected file. The default keyboard shortcut to rename a file is <keycap +>F2</keycap +>.</para> +</answer> +</qandaentry> + +<qandaentry> +<question +><para +>When I try to open a web page with &konqueror;, I get the message: <quote +>There appears to be a configuration error. You have associated Konqueror with text/html, but it cannot handle this file type.</quote +></para> +</question> +<answer> +<para +>You need to make sure that the embedding settings for the text/html <acronym +>MIME</acronym +> type are correct: <orderedlist> +<listitem +><para +>In &konqueror;, go to <menuchoice +><guimenu +>Settings</guimenu +><guimenuitem +>Configure Konqueror</guimenuitem +></menuchoice +> and then to the <guilabel +>File Associations</guilabel +> page.</para +></listitem> +<listitem +><para +>Open text->html in the tree view.</para +></listitem> +<listitem +><para +>Click on the <guilabel +>Embedding</guilabel +> tab. Make sure that <guilabel +>Left Click Action</guilabel +> is set to <guilabel +>Show file in embedded viewer</guilabel +>, and that <guilabel +>KHTML (khtml)</guilabel +> is at the top of <guilabel +>Services Preference Order.</guilabel +></para +></listitem> +</orderedlist> +</para> +<para +>Try opening a website in Konqueror. It should now work.</para> +</answer> +</qandaentry> + +<qandaentry> +<question +><para +>How do I configure the programs that &konqueror; uses to open different types of files?</para +></question> +<answer> +<para +>In order to configure file associations, you should go to the &kcontrolcenter; and choose the item <guimenuitem +>File Associations</guimenuitem +> under the category <guimenu +>KDE Components</guimenu +>.</para> +<para +>Suppose the default <acronym +>PDF</acronym +> viewer is now &kghostview; and you would prefer to use <application +>KPDF</application +> as a viewer. You would simply type <userinput +>pdf</userinput +> in the search box at the top of the dialogue, choose <guimenuitem +>pdf</guimenuitem +> in the <guimenu +>application</guimenu +> group and move <application +>KPDF</application +> up. In the <guilabel +>Embedding</guilabel +> tab you can also choose which component other applications will use to display files (for example, when viewing files in &konqueror; or using &ark;'s embedded viewer). </para> +</answer> +</qandaentry> + + +</qandaset> +</chapter> + +<!-- Keep this comment at the end of the file +Local variables: +mode: xml +sgml-omittag:nil +sgml-shorttag:nil +sgml-namecase-general:nil +sgml-general-insert-case:lower +sgml-minimize-attributes:nil +sgml-always-quote-attributes:t +sgml-indent-step:0 +sgml-indent-data:true +sgml-parent-document:("index.docbook" "book" "chapter") +sgml-exposed-tags:nil +sgml-local-catalogs:nil +sgml-local-ecat-files:nil +End: +--> diff --git a/tde-i18n-en_GB/docs/kdebase/faq/getkde.docbook b/tde-i18n-en_GB/docs/kdebase/faq/getkde.docbook new file mode 100644 index 00000000000..a059b9b7204 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdebase/faq/getkde.docbook @@ -0,0 +1,111 @@ +<!-- +<?xml version="1.0" ?> +<!DOCTYPE chapter PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" + "dtd/kdex.dtd"> +--> + +<chapter id="getting-kde"> +<title +>Getting &kde;</title> + +<qandaset> +<qandaentry> +<question id="where-to-get-kde"> +<para +>Where do I get &kde;?</para> +</question> +<answer> +<!-- This needs a rewrite including informations about the latest version (link to the info page?)--> +<para +>The main distribution site for &kde; is <ulink url="ftp://ftp.kde.org/" +>ftp.kde.org</ulink +>. However, this site is often under heavy load, so you might prefer to use <ulink url="http://download.kde.org/" +>download.kde.org</ulink +> which automatically redirects you to the mirror nearest to you. You can also have a look at the list of <ulink url="http://www.kde.org/ftpmirrors.html" +> &kde; mirror sites</ulink +>.</para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>Are there &Linux; distributions that include &kde;?</para> +</question> +<answer> +<para +>Yes, major &Linux; distributions already ship &kde;. As building a distribution takes some time, they might not always contain the latest version, but for a start or to avoid downloading from the Internet, they do provide a good starting point. </para> +<para +>You can find an up-to-date list of distributions that ship with &kde; <ulink url="http://www.kde.org/download/distributions.php" +>here</ulink +>. </para> + +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>What is the current version?</para> +</question> +<answer> + +<para +>Currently, the latest stable version is 3.2</para> + +<para +>The <ulink url="http://www.kde.org/info/3.2.php" +>&kde; 3.2 Info Page</ulink +> contains a lot of information specific to this release.</para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>Where do I find &kde; snapshots?</para> +</question> +<answer> +<para +>You can get the latest snapshots from <ulink url="ftp://ftp.kde.org/pub/kde/unstable/snapshots" +>ftp://ftp.kde.org/pub/kde/unstable/snapshots</ulink +>. You might also want to consider setting up your own <acronym +>CVS</acronym +> client in order to maintain the latest snapshot at all times. Please refer to <ulink url="http://developer.kde.org/source/anoncvs.html" +>Anonymous <acronym +>CVS</acronym +> and &kde;</ulink +> for further information. </para> + +</answer> +</qandaentry> + +<qandaentry> +<question id="where-to-get-qt"> +<para +>Where do I get &Qt;?</para> +</question> +<answer> +<para +>&Qt; is a product of the Norwegian company Trolltech. You can always get the latest &Qt; version from their <ulink url="ftp://ftp.trolltech.com" +>&FTP; server</ulink +>.</para> +<para +>And with most up-to-date &Linux; distributions, &Qt; is already included. Please see <xref linkend="prerequisites"/> for the version of &Qt; you need.</para> +</answer> +</qandaentry> + +<qandaentry> +<question id="qt"> +<para +>What is &Qt;, by the way?</para> +</question> +<answer> +<para +>&Qt; is a C++-based class library to build user interfaces. It also includes many utility classes like string classes and classes to handle input and output. It provides most of the widgets you will see in a &kde; application: menus, buttons, sliders, &etc;. &Qt; is a cross-platform library that allows you to write code that will compile on &UNIX; systems as well as &Windows; and embedded devices. You can learn more about &Qt; at <ulink url="http://www.trolltech.com" +>http://www.trolltech.com</ulink +>.</para> +</answer> +</qandaentry> +</qandaset> +</chapter> diff --git a/tde-i18n-en_GB/docs/kdebase/faq/index.cache.bz2 b/tde-i18n-en_GB/docs/kdebase/faq/index.cache.bz2 Binary files differnew file mode 100644 index 00000000000..7c34043ad24 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdebase/faq/index.cache.bz2 diff --git a/tde-i18n-en_GB/docs/kdebase/faq/index.docbook b/tde-i18n-en_GB/docs/kdebase/faq/index.docbook new file mode 100644 index 00000000000..a8f4568ddb4 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdebase/faq/index.docbook @@ -0,0 +1,167 @@ +<?xml version="1.0" ?> +<!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" + "dtd/kdex.dtd" [ + <!ENTITY kappname "&kde; Frequently Asked Questions"> + <!ENTITY % addindex "IGNORE"> + <!ENTITY % British-English "INCLUDE" +> <!-- change language only here --> + <!ENTITY faq-about SYSTEM "about.docbook"> + <!ENTITY faq-intro SYSTEM "intro.docbook"> + <!ENTITY faq-getkde SYSTEM "getkde.docbook"> + <!ENTITY faq-install SYSTEM "install.docbook"> + <!ENTITY faq-panel SYSTEM "panel.docbook"> + <!ENTITY faq-desktop SYSTEM "desktop.docbook"> + <!ENTITY faq-winmng SYSTEM "winmng.docbook"> + <!ENTITY faq-filemng SYSTEM "filemng.docbook"> + <!ENTITY faq-configkde SYSTEM "configkde.docbook"> + <!ENTITY faq-kdeapps SYSTEM "kdeapps.docbook"> + <!ENTITY faq-nonkdeapps SYSTEM "nonkdeapps.docbook"> + <!ENTITY faq-tips SYSTEM "tips.docbook"> + <!ENTITY faq-misc SYSTEM "misc.docbook"> + <!ENTITY faq-notrelated SYSTEM "notrelated.docbook"> + <!ENTITY faq-moreinfo SYSTEM "moreinfo.docbook"> + <!ENTITY faq-contrib SYSTEM "contrib.docbook"> + <!ENTITY faq-credits SYSTEM "credits.docbook"> + + +]> +<!--Time-stamp: "2001-09-03 00:10:00 endres"--> +<book lang="&language;"> + +<bookinfo> +<title +>&kde; Frequently Asked Questions</title> + +<authorgroup> +<author> +<surname +>The &kde; Team</surname> +</author> +<othercredit role="translator" +><firstname +>Malcolm</firstname +><surname +>Hunter</surname +><affiliation +><address +><email +>malcolm.hunter@gmx.co.uk</email +></address +></affiliation +><contrib +>Conversion to British English</contrib +></othercredit +> + +</authorgroup> + +<copyright> +<year +>1997</year> +<year +>1998</year> +<year +>1999</year> +<year +>2000</year> +<year +>2001</year> +<year +>2003</year> +<year +>2004</year> +<holder +>The &kde; Team</holder> +</copyright> + +<legalnotice +>&FDLNotice;</legalnotice> + +<date +>2004-09-07</date> +<releaseinfo +>3.3</releaseinfo> + +<abstract> +<para +>This is a compilation of the most frequently asked questions about the K Desktop Environment. Please report any bugs, inconsistencies, or omissions you find in this &FAQ; to <email +>kde-doc-english@kde.org</email +>. Please do not mail your questions to this list. Post them to the &kde; mailing lists and newsgroups instead. They are monitored for this &FAQ;.</para +> </abstract> + +<keywordset> +<keyword +>KDE</keyword> +<keyword +>FAQ</keyword> +<keyword +>question</keyword> +<keyword +>answer</keyword> +</keywordset> +</bookinfo> + +&faq-about; +&faq-intro; +&faq-getkde; +&faq-install; +&faq-panel; +&faq-desktop; +&faq-winmng; +&faq-filemng; +&faq-configkde; +&faq-kdeapps; +&faq-nonkdeapps; +&faq-tips; +&faq-misc; +&faq-moreinfo; +&faq-contrib; + +<chapter id="credits"> +<title +>Credits and Licence</title> + +<para +>The current &FAQ; maintainers are:</para> + +<itemizedlist> +<listitem +><para +>Rainer Endres <email +>endres@kde.org</email +></para +></listitem> +</itemizedlist> + +<para +>Many of the answers in this &FAQ; are taken from the various &kde; mailing lists and newsgroups. Here is a <emphasis +>big</emphasis +> thank you to all of you who have contributed answers that eventually appear in this &FAQ;.</para> + +<para +>Special thanks go to the former &FAQ; maintainer, who has written most of the stuff in here, and did a tremendous job: Mr. Lee Wee Tiong </para> + + +<para +>Conversion to British English: Malcolm Hunter <email +>malcolm.hunter@gmx.co.uk</email +></para +> +&underFDL; </chapter> + +&documentation.index; +</book> +<!-- +Local Variables: +sgml-minimize-attributes:nil +sgml-general-insert-case:lower +sgml-omittag:t +sgml-shorttag:t +sgml-namecase-general:t +sgml-always-quote-attributes:t +sgml-indent-step:2 +sgml-indent-data:nil +sgml-parent-document:nil +sgml-exposed-tags:nil +End: +--> diff --git a/tde-i18n-en_GB/docs/kdebase/faq/install.docbook b/tde-i18n-en_GB/docs/kdebase/faq/install.docbook new file mode 100644 index 00000000000..ce1e2bf0b7e --- /dev/null +++ b/tde-i18n-en_GB/docs/kdebase/faq/install.docbook @@ -0,0 +1,1035 @@ +<!-- <?xml version="1.0" ?> +<!DOCTYPE chapter PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" + "dtd/kdex.dtd" +> --> + + +<chapter id="install"> +<title +>Installation instructions</title> + +<para +>These are the generic installation instructions for the K Desktop Environment. Please complement your reading with the <filename +>README</filename +>s and <filename +>INSTALL</filename +>s that come along with the package. Please read them carefully and try to help yourself out if anything goes wrong. If you need further assistance, consider joining the &kde; mailing lists (see our web site instructions for joining the &kde; <ulink url="http://www.kde.org/mailinglists/" +>mailing lists</ulink +>) or newsgroups.</para> + + +<qandaset> + + +<qandaentry> +<question> +<para +>To the would-be converts</para> +</question> +<answer> + +<para +>So you have heard the rumours. Or you have seen the screenshots. And you are dying to get hold of &kde;. But you know next to nothing about this whole <quote +>alternative OS</quote +> business. Don't worry! You only need to do some (well, maybe not some) reading, that's all!</para> + +<para +>&kde; does not run on any version of &Microsoft; &Windows; or OS/2 (yet). To run &kde;, you need to have a &UNIX; system. Please refer to <xref linkend="platform"/> for more details.</para> + +<para +>Decide on a platform and set it up for your system. This <acronym +>FAQ</acronym +> can not help you with this, since &kde;<ulink url="http://www.kde.org" +> runs on many &UNIX;</ulink +> platforms. </para> + +<!-- Taken out because we can not help with all platforms and KDEisnotLINUX --> + +<para +>Finally, you are ready to commence the &kde; installation. Please start reading from the next section. To get &kde;, please refer to <xref linkend="where-to-get-kde"/>. Last but not least, if you encounter any problems while installing &kde;, please do not hesitate to make use of the &kde; <link linkend="mailing-lists" +>mailing lists</link +> and <link linkend="newsgroups" +>newsgroups</link +>. But do bear this in mind: no question is too silly to ask, but some are too silly to answer, especially when they are already answered in this <acronym +>FAQ</acronym +>.</para> +<para +>Good luck and have fun!</para> + +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>Available package formats</para> +</question> +<answer> + + +<para +>You can find several kinds of binary and source packages for different distributions and operating systems on the &kde-ftp;. The binary packages are not made by the &kde; Team, but by the distributors themselves, or some dedicated individuals. Please refer to <ulink url="http://dot.kde.org/986933826/" +>&kde; Package Policy Explained</ulink +> for information about the &kde; Package Policy. The only <quote +>official</quote +> release is the source tar.bz2 packages. Please refer to the <filename +>README</filename +>s and <filename +>INSTALL</filename +>s in the several binaries folders. For a list of the available packages for a release, refer to the relevant info page. For the latest release this is the <ulink url="http://www.kde.org/info/3.2.php" +>&kde; 3.2 Info Page</ulink +>.</para> + +</answer> +</qandaentry> + +<qandaentry> +<question id="prerequisites"> +<para +>Prerequisites</para> +</question> +<answer> + +<!-- rewrite to make it more general, pointing to the according webpages? --> + +<para +>For &kde; 3.2, you need the &Qt; library version 3.2 or greater. Please make sure you download the correct &Qt;. You will also need the header files, if you want to compile &kde; yourself. They are all available, at no cost, from <ulink url="http://www.trolltech.com/products/download" +>http://www.trolltech.com/download</ulink +>. In addition, there are optional libraries that might improve &kde; if installed on your system. An example is OpenSSL which will enable &konqueror; to browse web pages securely and is needed in a version +>=0.9.6. These should be provided by your distributor; if not, ask for an update.</para> + +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>Description of the base packages</para> +</question> +<answer> +<para +>The base distribution currently consists of eleven packages. Some are required, while others are optional. Each package is available in each of the aforementioned package formats.</para> +<variablelist> +<varlistentry> +<term +>kdelibs</term> +<listitem> +<para +>Required</para> +<para +>This package contains shared libraries that are needed by all &kde; applications.</para> +</listitem> +</varlistentry> +<varlistentry> +<term +>kdebase</term> +<listitem> +<para +>Required</para> +<para +>This package contains the base applications that form the core of the K Desktop Environment like the window manager, the terminal emulator, the control centre, the file manager, and the panel.</para> +</listitem> +</varlistentry> +<varlistentry> +<term +>&arts;</term> +<listitem> +<para +>Required</para> +<para +>The &arts; sound server. A powerful, network transparent sound server.</para> +</listitem> +</varlistentry> +<varlistentry> +<term +>kdeaddons</term> +<listitem> +<para +>Optional</para> +<para +>Various plugins for &kate;, &kicker;, &knewsticker;, &konqueror; and &noatun; </para> +</listitem> +</varlistentry> +<varlistentry> +<term +>kdeartwork</term> +<listitem> +<para +>Optional</para> +<para +>Additional wallpapers, themes, styles, sounds ...</para> +</listitem> +</varlistentry> +<varlistentry> +<term +>kdebindings</term> +<listitem> +<para +>Optional</para> +<para +>Various bindings for other languages, including &Java;, Perl, Python, ...</para> +</listitem> +</varlistentry> +<varlistentry> +<term +>kdegames</term> +<listitem> +<para +>Optional</para> +<para +>Various games like &kmahjongg;, &ksnake;, &kasteroids;, and &kpatience;.</para> +</listitem> +</varlistentry> +<varlistentry> +<term +>kdegraphics</term> +<listitem> +<para +>Optional</para> +<para +>Various graphics-related programs like &PostScript; previewer, &DVI; previewer, and a drawing program.</para> +</listitem> +</varlistentry> +<varlistentry> +<term +>kdeutils</term> +<listitem> +<para +>Optional</para> +<para +>Various desktop tools like a calculator, an editor and other nifty stuff.</para> +</listitem> +</varlistentry> +<varlistentry> +<term +>kdemultimedia</term> +<listitem> +<para +>Optional</para> +<para +>Multimedia applications like a &CD; player and a mixer.</para> +</listitem> +</varlistentry> +<varlistentry> +<term +>kdenetwork</term> +<listitem> +<para +>Optional</para> +<para +>Network applications. Currently contains the mail program &kmail;, the news reader &knode;, and several other network-related programs.</para> +</listitem> +</varlistentry> +<varlistentry> +<term +>kdeadmin</term> +<listitem> +<para +>Optional</para> +<para +>System administration programs.</para> +</listitem> +</varlistentry> +<varlistentry> +<term +>kdeedu</term> +<listitem> +<para +>Educational and entertaining applications for &kde;'s younger users. </para> +</listitem> +</varlistentry> +<varlistentry> +<term +>kdetoys</term> +<listitem> +<para +>Optional</para> +<para +>Toys!</para> +</listitem> +</varlistentry> +<varlistentry> +<term +>kdevelop</term> +<listitem> +<para +>Optional</para> +<para +>A complete Integrated Development Environment for &kde; and Qt</para> +</listitem> +</varlistentry> +</variablelist> + +<para +>&arts; and then kdelibs should be installed before everything else, and kdeaddons last. The other packages can be installed in any arbitrary order.</para> + +<para +>Most package management tools will let you put all these packages in one folder and install them all at once, figuring out the dependencies as they go.</para> + +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>Installation instructions for the different package formats</para> +</question> +<answer> +<para +><important> +<para +>Please do not forget to read the <filename +>README</filename +> and <filename +>INSTALL</filename +> files if they are available.</para> +</important +></para> +<variablelist> +<varlistentry> +<term +>Installation of the Debian packages</term> +<listitem> +<para +>The Debian packages install in accordance with the upcoming <acronym +>FHS</acronym +> (File Hierarchy Standard).</para> +<procedure> +<step performance="required" +><para +>become superuser</para +></step> +<step performance="required" +><para +>run <command +>dpkg <option +>-i <replaceable +>packagename.deb</replaceable +></option +></command +> for every package you want to install.</para +></step> +</procedure> +</listitem> +</varlistentry> +<varlistentry> +<term +>Installation of the <acronym +>RPM</acronym +> packages</term> +<listitem> +<procedure> +<title +>To install binary <acronym +>RPM</acronym +>s</title> +<step performance="required" +><para +>become superuser</para +></step> +<step performance="required" +><para +>execute <command +>rpm <option +>-ivh <replaceable +>packagename.rpm</replaceable +></option +></command +></para +></step> +</procedure> +</listitem> +</varlistentry> +<varlistentry> +<term +>Installation of the source <filename +>.tar.bz2</filename +> files</term> +<listitem> +<para +>Since there are always changes and updates to the way &kde; is compiled, please refer to <ulink url="http://developer.kde.org/build/index.html" +>Download and Install from Source</ulink +> for the most up to date installation instructions for the source packages. </para> +<para +>The general approach should work in most cases though. </para> +<para +>The source <filename +>.tar.bz2</filename +> package installs into <filename class="directory" +>/usr/local/kde</filename +> by default. You can override this setting by using the <option +>--prefix</option +> option of the <filename +>configure</filename +> script.</para> +<procedure> +<step performance="required" +><para +>unpack the packages with <command +>tar <option +>jxvf <replaceable +>packagename.tar.bz2</replaceable +></option +></command +></para +></step> +<step performance="required" +><para +>change folder to the package folder: <command +>cd <replaceable +>packagename</replaceable +></command +></para +></step> +<step performance="required" +><para +>configure the package: <command +>./configure</command +> <note +><para +>Some packages (notably kdebase) have special configuration options that might be applicable to your installation. Type <command +>./configure <option +>--help</option +></command +> to see the available options.</para +></note +></para +></step> +<step performance="required" +><para +>build the package: <command +>make</command +></para +></step> +<step performance="required" +><para +>install the package: <command +>su <option +>-c "make install"</option +></command +> (if you aren't already root). If you already are, just type <command +>make <option +>install</option +></command +>.</para +></step> +</procedure> +</listitem> +</varlistentry> +</variablelist> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>Post-installation procedures</para> +</question> +<answer> +<para +>First of all, please make sure that you have added &kde;'s binary installation folder (⪚ <filename class="directory" +>/usr/local/kde/bin</filename +>) to your <envar +>PATH</envar +> and &kde;'s library installation folder to your <envar +>LD_LIBRARY_PATH</envar +> (only necessary on systems that do not support rpath; on &Linux; &ELF;, it should work without). This environment variable may be called differently on some systems, ⪚ it is called <envar +>SHLIB_PATH</envar +> on &IRIX;. Then set the environment variable <envar +>KDEDIR</envar +> to the base of your &kde; tree, ⪚ <filename class="directory" +>/usr/local/kde</filename +>. <caution +> <para +>Please bear in mind that it is unwise to set <envar +>LD_LIBRARY_PATH</envar +> blindly. In the vast majority of cases it is unnecessary and can do more harm than good. There is a web page written by <ulink url="mailto:barr@cis.ohio-state.edu" +>Dave Barr</ulink +> explaining the evils of <envar +>LD_LIBRARY_PATH</envar +> and it can be found at <ulink url="http://www.cis.ohio-state.edu/~barr/ldpath.html" +>http://www.cis.ohio-state.edu/~barr/ldpath.html</ulink +>.</para> +</caution> +</para> +<para +>Even though you can use most of the &kde; applications simply by calling them, you can only benefit fully from &kde;'s advanced features if you use the &kde; window manager and its helper programs.</para> +<para +>In order to make it easy for you, we have provided a simple script called <filename +>startkde</filename +> which gets installed in <filename class="directory" +>$<envar +>KDEDIR</envar +>/bin</filename +> and is therefore in your path.</para> +<para +>Edit the file <filename +>.xinitrc</filename +> in your home folder (make a backup copy first!), remove everything that looks like calling a window manager, and insert <command +>startkde</command +> instead. Restart the &X-Server;. If you use &kdm;/<application +>xdm</application +>, you will have to edit the file <filename +>.xsession</filename +> instead of <filename +>.xinitrc</filename +>. And if there is no <filename +>.xinitrc</filename +> or <filename +>.xsession</filename +> in your home folder, simply create a new one with just one line containing <command +>startkde</command +>. <note +> <para +>Some systems (notably &RedHat; &Linux;) use <filename +>.Xclients</filename +> instead.</para> +</note +></para> +<para +>This should present you with a new shining &kde; desktop. You can now start to explore the wonderful world of &kde;. In case you want to read some documentation first, there is a highly recommended <ulink url="http://www.kde.org/documentation/quickstart/index.html" +>Quick Start guide</ulink +> available. Furthermore, every application has an online help that is available via the <guimenu +>help</guimenu +> menu.</para> +</answer> +</qandaentry> + + +<qandaentry> +<question> +<para +>Should I remove old version xyz before installing a new one?</para> +</question> +<answer> +<para +>In principle, this is not necessary. <acronym +>RPM</acronym +> and Debian packages should take care of all dependencies.</para> +<para +>If you compile the source code yourself, you should take more care. Instructions for running two different versions of &kde; on the same system are given at <ulink url="http://developer.kde.org/build/kde2-and-kde3.html" +>http://developer.kde.org/build/kde2-and-kde3.html</ulink +>. However, please note that running two different versions of &kde; from source can lead to problems if you are not careful. </para> +</answer> +</qandaentry> + +<qandaentry> +<question id="startkde"> +<para +>How do I start &kde;?</para> +</question> +<answer> +<para +>The most comfortable method to start &kde; is to use the <filename +>startkde</filename +> script. Simply put the line <command +>startkde</command +> at the end of your <filename +>.xsession</filename +> file (or your <filename +>.xinitrc</filename +> or <filename +>.Xclients</filename +> file if you are not using &kdm; or <application +>xdm</application +>). Please also remove the lines that start your previous window manager. If there is no <filename +>.xsession</filename +>, <filename +>.xinitrc</filename +>, or <filename +>.Xclients</filename +> in your home folder, simply create a new one that contains just one line: <command +>startkde</command +>.</para> +</answer> +</qandaentry> +<!-- Still needed? +<qandaentry> +<question> +<para +>Whenever I start &kde;, it complains about "shadow passwords". +Why?</para> +</question> +<answer> +<para +>When your system uses shadow passwords, the screensaver can only +run properly if the suid bit is set. This bit gives the screensavers +root privileges, which are needed to access the shadow passwords. +<caution +><para +>The screensavers might be configured to secure the +machine until the password is entered.</para +></caution +></para> +<procedure> +<title +>Setting the suid bit on the screensavers</title> +<step performance="required" +><para +>become root</para +></step> +<step performance="required" +><para +><command +>chown root +$<envar +>KDEDIR</envar +>/bin/*.kss</command +></para +></step> +<step performance="required" +><para +><command +>chmod u+s +$<envar +>KDEDIR</envar +>/bin/*.kss</command +></para +></step> +</procedure> +<para +>Alternatively, if you compile &kde; from source, you can use +<command +>./configure <option +>with-shadow</option +></command +> to +configure kdebase. Then the suid bit is set automatically during +<command +>make install</command +>.</para> +</answer> +</qandaentry> +--> +<qandaentry> +<question> +<para +>Is it possible to install &kde; in a user folder?</para> +</question> +<answer> +<para +>Yes, you can install &kde; in any folder you want. What you have to do depends on the kind of packages you want to install:</para> +<procedure +><title +>Source packages</title> +<step performance="required" +><para +>Configure and install the package using <command +>configure <option +>--prefix=<replaceable +>/users/myhome/kde</replaceable +></option +>; make; make install</command +> to install into <filename class="directory" +>/users/myhome/kde</filename +>.</para +></step> +<step performance="required" +><para +>Add the following to your init files. Please note that if it is not necessary for you to set <envar +>LD_LIBRARY_PATH</envar +>, it is better to leave it out.</para> + +<para +>For csh or tcsh:</para> +<programlisting +>setenv KDEDIR /users/myhome/kde + +if ( $?LD_LIBRARY_PATH ) then + setenv LD_LIBRARY_PATH $KDEDIR/lib:$LD_LIBRARY_PATH +else + setenv LD_LIBRARY_PATH $KDEDIR/lib +endif + +if ( ! $?LIBRARY_PATH ) then + setenv LIBRARY_PATH $LD_LIBRARY_PATH +endif +</programlisting> +<para +>For <application +>bash</application +>:</para> +<programlisting +>KDEDIR=/users/myhome/kde +PATH=$KDEDIR/bin:$PATH +LD_LIBRARY_PATH=$KDEDIR/lib:$LD_LIBRARY_PATH +LIBRARY_PATH=$LD_LIBRARY_PATH +export KDEDIR PATH LD_LIBRARY_PATH LIBRARY_PATH +</programlisting +></step> +</procedure> +<procedure +><title +><acronym +>RPM</acronym +> packages</title> +<step performance="required" +><para +><command +>rpm</command +> allows you to use the <option +>--prefix</option +> option to select the folder you want to install to. For example, executing <command +>rpm <option +>-i --prefix=<replaceable +>/users/myhome/kde package.rpm</replaceable +></option +></command +> will install the package to <filename class="directory" +>/users/myhome/kde</filename +>.</para +></step> +</procedure> +<para +><note> +<para +>Although &kde; will run from a user folder, there are some problems with programs that require suid root, ⪚ the programs in the kdeadmin package. But since they are not meant to be run by users in the first place, this is nothing to worry about.</para> +<para +>However, on systems using shadow passwords, the screensavers have to be suid root to enable password access for unlocking the screen, so this option will not work.</para> +</note +></para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +><command +>startkde</command +> fails with <errorname +>can not connect to X server</errorname +>. What is wrong?</para> +</question> +<answer> +<para +>You probably tried to start the X server with <command +>startkde</command +>. The X server is started with <command +>startx</command +>. <command +>startkde</command +> is the script that should be run from your <filename +>.xinitrc</filename +>, <filename +>.xsession</filename +>, or <filename +>.Xclients</filename +> to activate the window manager and the necessary server daemons for &kde;. See also <xref linkend="startkde"/>.</para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>&kde; on &AIX;?</para> +</question> +<answer> +<para +><acronym +>IBM</acronym +> now officially support &kde; on &AIX;. You can find details at <ulink url="http://www.ibm.com/servers/aix/products/aixos/linux/index.html" +>http://www.ibm.com/servers/aix/products/aixos/linux/index.html</ulink +>. There is also some older information at <ulink url="http://space.twc.de/~stefan/kde/aix.html" +>http://space.twc.de/~stefan/kde/aix.html</ulink +>.</para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>&kde; on a laptop?</para> +</question> +<answer> +<para +>If you can get &X-Window; to run on your laptop, you should not have any problem getting &kde; to run on it. In addition, you might find the following links helpful:</para> +<itemizedlist> +<listitem> +<para +><ulink url="http://www.linux-laptop.net/" +>http://www.linux-laptop.net/</ulink +></para> +</listitem> +<listitem> +<para +><ulink url="http://www.sanpei.org/Laptop-X/note-list.html" +>http://www.sanpei.org/Laptop-X/note-list.html</ulink +></para> +</listitem> +</itemizedlist> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>I have a neomagic chipset in my laptop. Is there anything special I should do to run &kde;?</para> +</question> +<answer> +<para +>On some laptops using the 2160 chipset (MagicGraph 128XD) the following options in <filename +>XF86Config</filename +> are needed to avoid a lock-up of the graphic engine:</para> +<screen +>Option "XaaNoScanlineImageWriteRect" + Option "XaaNoScanlineCPUToScreenColorExpandFill"</screen> + +<para +>If you have experienced desktop hangs while using &kde; please try this option.</para +> +</answer +> +</qandaentry> + +<qandaentry> +<question> +<para +>I do not like the default &kde; folder after installation. How do I move it without breaking anything?</para> +</question> +<answer> +<para +>Assuming the default is <filename class="directory" +>/opt/kde</filename +> and you want to move it to <filename class="directory" +>/usr/local/kde</filename +>, here's what you have to do:</para> +<procedure> +<step performance="required" +><para +>change to superuser if you aren't already</para +></step> +<step performance="required" +><para +><command +>mv /opt/kde /usr/local/kde</command +></para +></step> +<step performance="required" +><para +><command +>ln -s /usr/local/kde /opt/kde</command +></para +></step> +</procedure> +<para +>This will put all your &kde; files in <filename class="directory" +>/usr/local/kde</filename +> but everything is still accessible from <filename class="directory" +>/opt/kde</filename +>.</para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>What files can I delete from my &kde; install folder? Can all the <filename +>*.h</filename +>, <filename +>*.c</filename +> and <filename +>*.o</filename +> files be safely removed?</para> +</question> +<answer> +<para +>There should not be any need to keep the <filename +>.c</filename +> and <filename +>.o</filename +> files, but you might want to keep the <filename +>.h</filename +> files, as they are used by includes if you ever want to compile your own &kde; programs. But if you wish to add patches to the source programs as they become available (rather than downloading everything again), then they should stay.</para +> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>Will I lose my current settings when I upgrade &kde;?</para> +</question> +<answer> + +<para +>No. In most cases &kde; will be able to transport your settings intact. You may need to reenter passwords in some applications (such as &kmail; or &knode;) but most other settings will be safe.</para> + +<para +>There were mixed reports of results between some previous versions of &kde;. To be safe, you may like to back up your entire &kde; configuration. </para> + +<para +>Settings are kept in the <filename class="directory" +>$<envar +>HOME</envar +>/.kde</filename +> or <filename class="directory" +>$<envar +>HOME</envar +>/.kde2</filename +> subfolder in your home folder. Copy your old <filename class="directory" +>.kde</filename +>/<filename class="directory" +>.kde2</filename +> folder to a backup location, install &kde; 3.2, and then copy back any necessary mail and news settings. That said, most people can make a direct upgrade, without removing the old <filename class="directory" +>.kde</filename +> folder, without a hitch.</para> +<para +>You can override the use of <filename class="directory" +>$<envar +>HOME</envar +>/.kde</filename +> by setting the $<envar +>KDEHOME</envar +> variable.</para +> +</answer> +</qandaentry> + +<qandaentry id="greyscreen"> +<question> +<para +>I upgraded &kde; and it seemed to go fine, but when I start it, I get a blank grey screen, and nothing happens. There are errors in the console about DCOPserver. What's going on?</para> +</question> + +<answer> +<para +>&kde; uses several temporary files during its operation. These are usually to be found in the following locations:</para> +<itemizedlist> +<listitem +><para +><filename +>~/.DCOPserver-*</filename +> (there are usually two of these; one is a symlink to the other)</para +></listitem> +<listitem +><para +><filename +>~/.kde/socket-<replaceable +>hostname</replaceable +></filename +></para +></listitem> +<listitem +><para +><filename +>~/.kde/tmp-<replaceable +>hostname</replaceable +></filename +> which is normally a symlink to the next file:</para +></listitem> +<listitem +><para +><filename +>/tmp/tmp-kde-<replaceable +>USER</replaceable +></filename +></para +></listitem> +<listitem +><para +><filename +>~/.kde/socket-<replaceable +>hostname</replaceable +></filename +> which is also normally a symlink to:</para +></listitem> +<listitem +><para +><filename +>/tmp/ksocket-<replaceable +>USER</replaceable +></filename +></para +></listitem> +</itemizedlist> + +<para +>If the symlinks get broken, usually because a <command +>cron</command +> or shutdown script is emptying out the <filename class="directory" +>/tmp</filename +> folder, then strange things will happen. These files, and the symlinks, will all be created automatically at the start of &kde; so you can safely remove them <emphasis +>while &kde; is not running</emphasis +>.</para> + +<para +>If you are only getting a grey screen when you start &kde;, or if you get an error message telling you to <errorname +>Check your installation</errorname +>, then shut down X and delete all the files listed above, then try to restart X.</para> + +<para +>Normally (&ie; when not upgrading between &kde; versions) it's quite safe to leave these files intact, and you may shave a few seconds off your &kde; startup time by doing so.</para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>Compiling kdebase gives me a <errorname +>bin/sh: msgfmt: command not found</errorname +> error!</para> +</question> +<answer> +<para +>You need the &GNU; <application +>msgfmt</application +> which is part of the &GNU; i18n package <application +>gettext</application +>. You should be able to download it from any &GNU; mirror.</para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>How do I uninstall &kde; applications compiled from source?</para> +</question> +<answer> +<para +>You can uninstall your programs by typing <command +>make uninstall</command +> in the folder where you did <command +>make install</command +>. If you have already deleted that folder, then there is only one way, and it is not good: go to <filename class="directory" +>$<envar +>KDEDIR</envar +>/bin</filename +> and start deleting files one by one.</para> +<para +>If you expect to find yourself in this situation, you might want to consider a program such as &GNU; <application +>stow</application +>, found at <ulink url="http://www.gnu.org/software/stow/stow.html" +>http://www.gnu.org/software/stow/stow.html</ulink +>.</para> +</answer> +</qandaentry> + +<qandaentry> +<question id="gif"> +<para +>What is up with &GIF; support?</para> +</question> +<answer> +<para +>This has to do with issues with Unisys' &LZW; patent. &GIF; support is turned off from &Qt; 1.44 onwards by default. When you want to use &GIF;s and have the relevant license, recompile &Qt; with &GIF; support. <command +>./configure <option +>-gif</option +></command +>.</para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>How do I install &kde; themes?</para> +</question> +<answer> +<para +>Theme support in &kde; has been discontinued with this version. However, there are many opportunities to personalise and add eye candy to &kde; Look at, for example, <guilabel +>Appearance & Themes</guilabel +> in &kcontrol;. </para> +</answer> +</qandaentry> +</qandaset> +</chapter> diff --git a/tde-i18n-en_GB/docs/kdebase/faq/intro.docbook b/tde-i18n-en_GB/docs/kdebase/faq/intro.docbook new file mode 100644 index 00000000000..e86f7cb2e80 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdebase/faq/intro.docbook @@ -0,0 +1,100 @@ +<!-- +<?xml version="1.0" ?> +<!DOCTYPE chapter PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" + "dtd/kdex.dtd"> +--> + +<chapter id="introduction"> +<title +>Introduction</title> + +<qandaset> +<qandaentry> +<question> +<para +>What is &kde;?</para> +</question> +<answer> +<para +>&kde; is the K Desktop Environment. It is a project initiated by <ulink url="mailto:ettrich@kde.org" +>Matthias Ettrich</ulink +> in 1996. The aim of the &kde; project is to connect the power of the &UNIX; operating systems with the comfort of a modern user interface.</para> +<para +>In short, &kde; will bring &UNIX; to the desktop!</para> +<para +>If you want further information about &kde;, have a look at <ulink url="http://www.kde.org/whatiskde/index.html" +>What is &kde;?</ulink +></para> +</answer> +</qandaentry> + +<qandaentry> +<question id="platform"> +<para +>On which platforms can I expect &kde; to work?</para> +</question> +<answer> +<para +>&kde; is a Desktop Environment for all flavours of &UNIX;. While it is true that most &kde; developers use &Linux;, &kde; runs smoothly on a wide range of systems. You may, however, need to tweak the source code a bit to get &kde; to compile on a not-so-popular variant of &UNIX;, or if you are not using the &GNU; development tools, in particular the &gcc; compiler.</para> +<para +>For an almost complete list of systems &kde; is running on, please refer to <ulink url="http://promo.kde.org/kde_systems.php" +>this list of systems for KDE</ulink +> </para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>Is &kde; a window manager?</para> +</question> +<answer> +<para +>No, &kde; is not a window manager. While &kde; includes a very sophisticated window manager (&kwin;), &kde; is much more than that. It is a full-blown Integrated Desktop Environment.</para> +<para +>&kde; provides a complete desktop environment, including a web browser, a file manager, a window manager, a help system, a configuration system, uncountable tools and utilities, and an ever increasing number of applications, including but not limited to mail and news clients, drawing programs, a &PostScript; and a &DVI; viewer and so forth.</para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>Is &kde; a <acronym +>CDE</acronym +>, &Windows; 95 or &Mac; <acronym +>OS</acronym +> clone?</para> +</question> +<answer> +<para +>No, &kde; is not a clone. Specifically &kde; is not a <acronym +>CDE</acronym +> or &Windows; clone. While the &kde; developers have and will continue to glean the best features from all existing desktop environments, &kde; is a truly unique environment that has and will continue to go its own way.</para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>Is &kde; free software?</para> +</question> +<answer> +<para +>Yes, &kde; is free software according to the &GNU; General Public Licence. All &kde; libraries are available under the <acronym +>LGPL</acronym +> making commercial software development for the &kde; desktop possible, but all &kde; applications are licensed under the <acronym +>GPL</acronym +>.</para> +<para +>&kde; uses the <link linkend="qt" +>&Qt; C++ crossplatform toolkit</link +>, which is also released (since version 2.2) under the <acronym +>GPL</acronym +>.</para> +<para +>It is absolutely legal to make &kde; and &Qt; available on &CD-ROM; free of charge. No runtime fees of any kind are incurred.</para> +</answer> +</qandaentry> +</qandaset> +</chapter> + diff --git a/tde-i18n-en_GB/docs/kdebase/faq/kdeapps.docbook b/tde-i18n-en_GB/docs/kdebase/faq/kdeapps.docbook new file mode 100644 index 00000000000..5cdf93b53b5 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdebase/faq/kdeapps.docbook @@ -0,0 +1,240 @@ +<!-- +<?xml version="1.0" ?> +<!DOCTYPE chapter PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" + "dtd/kdex.dtd"> +--> + +<chapter id="applications"> +<title +>&kde; applications</title> + +<qandaset> +<qandaentry> +<question> +<para +>&kppp;</para> +</question> +<answer> + +<para +>Many &kde; users report problems using &kppp;. But before you complain about &kppp;, make sure you have already checked the following:</para> + +<itemizedlist> +<listitem +><para +>Can you dialup to your <acronym +>ISP</acronym +> without using &kppp;? If you cannot, then perhaps &kppp; is not the culprit after all.</para +></listitem> +<listitem +><para +>Have you gone through the &kppp; documentation at least three times and followed its instructions and trouble-shooting suggestions?</para +></listitem> +</itemizedlist> +<para +>The &kppp; documentation can be accessed through the <application +>&kde; Help Centre</application +>. Last, but not least, the &kppp; homepage is at <ulink url="http://ktown.kde.org/~kppp/" +>http://ktown.kde.org/~kppp/</ulink +>.</para> +<para +>Now, if you still encounter problems, here's what might help you solve them:</para> +<variablelist> +<varlistentry +><term +>How do I change the &MTU; setting in &kppp;?</term> +<listitem +><para +>Open up the &kppp; dialogue box and select <guibutton +>Setup</guibutton +>. Choose an existing account and click <guibutton +>Edit</guibutton +>, or <guibutton +>New</guibutton +> to create a new dialup account. Select the <guilabel +>Dial</guilabel +> tab and click <guibutton +>Arguments</guibutton +>. Type what you want to change in the Argument textbox (⪚ <userinput +>mtu 296</userinput +>) and click <guibutton +>Add</guibutton +>. When you are satisfied, click <guibutton +>Close</guibutton +>.</para> +<para +>To check whether the options <quote +>took</quote +>, do one of the following:</para> +<itemizedlist> +<listitem> +<para +>In a terminal window, run <userinput +><command +>/sbin/ifconfig</command +> ppp0</userinput +> and look at the reported &MTU; in the output. It should match your request.</para> +</listitem> +<listitem +><para +>Add <option +>debug</option +> and <option +>kdebug</option +> (each on a separate line) to your <filename +>/etc/ppp/options</filename +> file and restart your &PPP; session. You will find debugging messages in <filename +>/var/log/messages</filename +>, including &MRU; and &MTU; settings.</para +></listitem> +</itemizedlist> +<para +>If you want, the &MRU; and &MTU; settings can be added to the <filename +>options</filename +> file, one complete setting per line, no quotes or dashes.</para +></listitem> +</varlistentry> +<varlistentry> +<term +>&kppp; connects at a slower speed than normal.</term> +<listitem +><para +>The following might do the trick:</para> +<itemizedlist> +<listitem +><para +>Try executing <command +>setserial spd_hi</command +>.</para +></listitem> +<listitem +><para +>The default &MTU; value is 1500, which maybe too large for a dialup connection. Try changing it to a smaller value like <userinput +>296</userinput +> or <userinput +>576</userinput +>.</para +></listitem> +<listitem +><para +>Check in your <filename class="directory" +>$<envar +>HOME</envar +>/.kde/share/config</filename +> for the <filename +>kppprc</filename +>. Ensure the correct modem speed is actually defined there.</para +></listitem> +</itemizedlist +></listitem> +</varlistentry> +</variablelist> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>&konsole;</para> +</question> +<answer> +<variablelist> + +<varlistentry> +<term +>How do I page-up or page-down?</term> +<listitem +><para +>Use <keycombo action="simul" +> <keycap +>Shift</keycap +><keycap +>Page Up</keycap +></keycombo +> and <keycombo action="simul" +><keycap +>Shift</keycap +><keycap +>Pg Dn</keycap +></keycombo +>. </para +></listitem> +</varlistentry> + +<varlistentry> +<term +>How do I perform a simple <quote +>copy</quote +> from &konsole; to anything else?</term> +<listitem +><para +>When I do a <command +>ls</command +>, first I select with the mouse the desired text, press <keycombo action="simul" +>&Ctrl;<keycap +>C</keycap +></keycombo +>, then I make the target application active, point the mouse to the relevant part and press <keycombo action="simul" +>&Ctrl;<keycap +>V</keycap +></keycombo +>. Alternatively, highlight the text by dragging with the &LMB; down and paste by clicking with the &MMB; (or both buttons if you are using a 2 button mouse with 3 button emulation). </para +></listitem> +</varlistentry> + +<varlistentry> +<term +>Why can't &konsole; find the <quote +>9x15</quote +> and the 2 <quote +>console</quote +> bitmap fonts installed with &kde;?</term> +<listitem> + +<para +><application +>FontConfig</application +> must find the three fonts installed in: <filename class="directory" +>$<envar +>KDEDIR</envar +>/share/fonts</filename +>. If the &kde; install does not install these fonts in a directory that already exists (⪚ <filename class="directory" +>/usr/share/fonts</filename +>) then you must add this directory to the configuration file <filename class="directory" +>/etc/fonts/local.conf</filename +>. This should be the first line after <quote +><fontconfig></quote +>. For example: <programlisting> +<fontconfig> +<dir>/usr/kde3/share/fonts</dir> +</fontconfig> +</programlisting +> After adding the directory, run (as root): <userinput +><command +>fc-cache</command +> -v</userinput +> and check that it found the directory.</para> +</listitem> +</varlistentry> + +</variablelist> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>&kmail;</para> +</question> +<answer> +<para +>&kmail; has its own home page at <ulink url="http://kmail.kde.org" +>http://kmail.kde.org</ulink +> where an <acronym +>FAQ</acronym +> is available.</para> +</answer> +</qandaentry> + +</qandaset> +</chapter> diff --git a/tde-i18n-en_GB/docs/kdebase/faq/misc.docbook b/tde-i18n-en_GB/docs/kdebase/faq/misc.docbook new file mode 100644 index 00000000000..a2ae1725981 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdebase/faq/misc.docbook @@ -0,0 +1,327 @@ +<!-- +<?xml version="1.0" ?> +<!DOCTYPE chapter PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" + "dtd/kdex.dtd"> +--> + +<chapter id="misc"> +<title +>Miscellaneous questions</title> + +<qandaset> +<qandaentry> +<question> +<para +>Why does &kde; use &Qt;?</para> +</question> +<answer> +<para +>&Qt; is a very sophisticated toolkit that provides everything that is needed to build a modern user interface. &Qt; is written in C++, thus allowing object-oriented development which ensures efficiency and code reuse in a project the size and scope of &kde;. In our opinion there is no better toolkit available for &UNIX; systems and that it would have been a grave mistake to try to build &kde; on anything but the best.</para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>Why does &kde; not use gtk, xforms, xlib, whatever?</para> +</question> +<answer> +<para +>There are a number of toolkits available. To provide a consistent user interface and to keep used resources such as memory to a minimum, &kde; can use only one of them. &Qt; was selected for the reasons mentioned above.</para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>But &Qt; isn't free, is it?</para> +</question> +<answer> +<para +>It is! As of September 4, 2000, version 2.2 of the &Qt; libraries were licensed under the <acronym +>GPL</acronym +>, thereby fulfiling all aspects of <quote +>free software</quote +>.</para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>Does &kde; have terminal emulators with transparent background?</para> +</question> +<answer> +<para +>Yes and no. &konsole; has the ability to simulate transparency by redrawing the background of the window inside the &konsole; window. This gives the illusion of transparency, but if you place &konsole; on top of another window, the transparency is lost. <ulink url="http://www.eterm.org" +>Eterm</ulink +> should work fine under &kde; if you desire more complete transparency.</para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>How do I create icons for non-&kde; applications that I can put in the <guimenu +>K</guimenu +> menu? Where do these icons go?</para> +</question> +<answer> +<para +>Create them using your favourite image manipulator, for example, <application +>GIMP</application +>, or the <application +>&kde; Icon Editor</application +> and put them in <filename class="directory" +>$<envar +>KDEDIR</envar +>/share/icons(/mini)</filename +> or <filename class="directory" +>$<envar +>HOME</envar +>/.kde/share/icons(/mini)</filename +>. </para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>What about &kde; programs that do not have icons? How do I get them into the menu?</para> +</question> +<answer> +<para +>Use &kmenuedit;. To access it use the &RMB; on the <guibutton +>K</guibutton +> button and select <guimenu +>Menu Editor</guimenu +>.</para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>Does &kde; have a graphical &FTP; client?</para> +</question> +<answer> +<para +>Yes, and it is none other than your favourite file manager, &konqueror;. You can drag and drop remote files into local folders.</para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>How do I exit &kde;?</para> +</question> +<answer> +<para +>Simply click on the <guibutton +>K</guibutton +> button and select <guimenu +>Logout</guimenu +>. In addition, if you <mousebutton +>right</mousebutton +> click on an empty area of the desktop, you will be presented with a menu containing logout as one of the options. <note +><para +>Depending on your configuration of the &X-Window;, <keycombo action="simul" +>&Ctrl;&Alt;&Backspace;</keycombo +> might also do the trick by killing the X server, but its use prevents session management and cannot be recommended.</para +></note +></para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>Is there a program that checks for new mails at my <acronym +>ISP</acronym +> if and only if I am online?</para> +</question> +<answer> +<para +>&korn; will do the job. If you are not connected, it will just sit there (idling).</para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>Is it really necessary to upgrade to the latest version?</para> +</question> +<answer> +<para +>We recommend to always use the latest stable release. If you don't, it will probably be difficult to get answers to your questions. If you have a problem with an old version, the answer will probably be <quote +>Please upgrade and try again</quote +>. Note that new versions also sometimes fix security problems.</para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>How do I copy and paste in &kde;?</para> +</question> +<answer> +<para +>The simplest method is to use your mouse:</para> +<procedure> +<step performance="required" +><para +>Highlight the text you want to copy by holding down the &LMB; and dragging across the text.</para +></step> +<step performance="required" +><para +>Go to the destination area; depending on your configuration, you might need to click it using the &LMB; to give it focus.</para +></step> +<step performance="required" +><para +>Click the &MMB; to paste. If you have a two button mouse and are emulating a three button mouse, push both buttons simultaneously.</para +></step> +</procedure> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>How do I convert the default &RedHat; menus into a menu in the <guimenu +>K</guimenu +> menu?</para> +</question> +<answer> +<para +>Click on the <guibutton +>K</guibutton +> button and select <menuchoice +><guimenu +>System</guimenu +><guimenuitem +>Appfinder</guimenuitem +></menuchoice +>.</para> +</answer> +</qandaentry> + +<qandaentry> +<question id="CVS"> +<para +>What is <acronym +>CVS</acronym +>?</para> +</question> +<answer> +<para +>It stands for Concurrent Versions System. It is a version control system and is based on <acronym +>RCS</acronym +> (Revision Control System), but offers more functionality. It is used to maintain source code under development. It will keep multiple versions of things (handy if you broke something and have to back up and get a clean old version), and allows people remote access over the Net to pick up the latest source code and even to check in new files if they have permission. It is also open source (you pay for support if you want it), and since it is free it is the system of choice for people writing more free products, such as &kde;.</para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>Does &kde; support dual screen (Xinerama)?</para> +</question> +<answer> +<para +>Yes, you need to have a multi-headed X server (⪚ MetroX or XFree86 4.0 and above) and a &kde; +>= 2.2.1 </para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>Why does Drag and Drop not work with Xinerama?</para> +</question> +<answer> +<para +>You should upgrade to XFree86 4.2.0 for this to work properly.</para> +</answer> +</qandaentry> + + +<qandaentry> +<question> +<para +>How do I check which version of &kde; I am using?</para> +</question> +<answer> +<para +>Fire up your <application +>&kde; Control Centre</application +>. It comes up with an Info Screen including the version of &kde; The &kde; version is also included in the application's <guimenuitem +>About</guimenuitem +> dialogue. </para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>Can I write commercial software for &kde;?</para> +</question> +<answer> +<para +>You can use the &kde; libraries to write <quote +>commercial and closed source</quote +> as well as <quote +>commercial and open source</quote +> software. If you write open source software you can use the &Qt; free edition. But if you write closed source software you may not use the &Qt; free edition; you need to obtain the &Qt; professional edition from Troll Tech. </para +> <para +>If you want more information, please contact <ulink url="http://www.trolltech.com" +>Troll Tech</ulink +> directly.</para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>How do I go about creating themes and icons?</para> +</question> +<answer> +<para +>Go see <ulink url="http://artist.kde.org" +>http://artist.kde.org</ulink +>.</para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>Is <application +>KLyX</application +> dead?</para> +</question> +<answer> +<para +>Yes. But future versions of <application +>LyX</application +> will be &GUI; independent. Check the progress of the various &GUI; frontends <ulink url="http://devel.lyx.org/guii.php3" +>here</ulink +>.</para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>How can I get to know about development updates?</para> +</question> +<answer> +<para +>You might want to subscribe to the various &kde; mailing lists available, especially kde-cvs, which lists all commits done to the &kde; <acronym +>CVS</acronym +> repository. Check <ulink url="http://lists.kde.org" +>http://lists.kde.org</ulink +> if you want to read without subscribing.</para> +</answer> +</qandaentry> +</qandaset> +</chapter> + diff --git a/tde-i18n-en_GB/docs/kdebase/faq/moreinfo.docbook b/tde-i18n-en_GB/docs/kdebase/faq/moreinfo.docbook new file mode 100644 index 00000000000..ee77ff73614 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdebase/faq/moreinfo.docbook @@ -0,0 +1,253 @@ +<!-- +<?xml version="1.0" ?> +<!DOCTYPE chapter PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" + "dtd/kdex.dtd"> +--> + +<chapter id="more-info"> +<title +>Getting more information</title> + +<qandaset> +<qandaentry> +<question> +<para +>Where is the &kde; homepage?</para> +</question> +<answer> +<para +>The &kde; homepage is located at <ulink url="http://www.kde.org" +>http://www.kde.org</ulink +>. If you prefer a local mirror, there are several to choose from. For a current list of web site mirrors sorted by location, please visit <ulink url="http://www.kde.org/mirrors/web.php" +>http://www.kde.org/mirrors/web.php</ulink +>.</para> +</answer> +</qandaentry> + +<qandaentry> +<question id="mailing-lists"> +<para +>Is there a &kde; mailing list?</para> +</question> +<answer> +<para +>There are several &kde; mailing lists. Each focuses on a different aspect of &kde;. Some are for developers, so they are not discussed in detail. Some of the more important lists that users might be interested in are:</para> +<variablelist> +<varlistentry +><term +>kde</term> +<listitem +><para +>This is the main &kde; mailing list for general discussions.</para +></listitem> +</varlistentry> +<varlistentry +><term +>kde-announce</term> +<listitem +><para +>This list is used to announce new versions of &kde; as well as new tools and applications.</para +></listitem> +</varlistentry> +<varlistentry +><term +>kde-look</term> +<listitem +><para +>This is the list that deals with questions about look and feel, and general user interface considerations.</para +></listitem> +</varlistentry> +</variablelist> +<para +>For the complete list of mailing lists available, please refer to <ulink url="http://www.kde.org/mailinglists/" +>http://www.kde.org/mailinglists/</ulink +>.</para> +<para +>Please note that it is not a good idea to ask questions which are already answered in this &FAQ;.</para> +</answer> +</qandaentry> + +<qandaentry> +<question id="subscribe"> +<para +>How do I subscribe/unsubscribe to these lists?</para> +</question> +<answer> +<para +>To subscribe, send an email to list-request, that is:</para> +<itemizedlist> +<listitem +><para +><ulink +url="mailto:kde-request@kde.org" +>kde-request@kde.org</ulink +></para +></listitem> +<listitem +><para +><ulink url="mailto:kde-announce-request@kde.org" +>kde-announce-request@kde.org</ulink +></para +></listitem> +<listitem +><para +><ulink +url="mailto:kde-user-request@kde.org" +>kde-user-request@kde.org</ulink +></para +></listitem> +<listitem +><para +><ulink url="mailto:kde-look-request@kde.org" +>kde-look-request@kde.org</ulink +></para +></listitem> +</itemizedlist> +<para +>The email must contain <userinput +>subscribe <replaceable +>your_email_address</replaceable +></userinput +> in the subject.</para> +<para +>To unsubscribe, send an email to list-request, that is:</para> +<itemizedlist> +<listitem +><para +><ulink url="mailto:kde-request@kde.org" +>kde-request@kde.org</ulink +></para +></listitem> +<listitem +><para +><ulink url="mailto:kde-announce-request@kde.org" +>kde-announce-request@kde.org</ulink +></para +></listitem> +<listitem +><para +><ulink url="mailto:kde-user-request@kde.org" +>kde-user-request@kde.org</ulink +></para +></listitem> +<listitem +><para +><ulink url="mailto:kde-look-request@kde.org" +>kde-look-request@kde.org</ulink +></para +></listitem> +</itemizedlist> +<para +>The email must contain <userinput +>unsubscribe <replaceable +>your_email_address</replaceable +></userinput +> in the subject. <important +><para +>Never send subscribe/unsubscribe request to the mailing lists directly! Use the list-request instead.</para +></important +></para> +<para +>There is also a complete list of all &kde;-related mailing lists, and a web interface for subscribing and unsubscribing located at <ulink url="http://master.kde.org/mailman/listinfo" +>http://master.kde.org/mailman/listinfo</ulink +>.</para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>Is there a mailing list archive?</para> +</question> +<answer> + +<para +>Yes, there is a searchable mailing list archive hosted by <ulink url="http://www.progressive-comp.com" +>Progressive Computer Concepts</ulink +>. The &URL; is <ulink url="http://lists.kde.org" +>http://lists.kde.org</ulink +>. There you will see a folder listing of the mailing lists. Note that you can only do a subject/author search at this level. You probably will not find what you want doing this kind of search.</para> + +<para +>To do a body search, you have to enter one of the mailing lists. Just click on the folder you want to search (⪚ <quote +>kde</quote +> or <quote +>kde-user</quote +>) and then the pull-down menu by the search box will default to <quote +>Body</quote +> searches. To be thorough, you should probably search the <quote +>kde</quote +>, <quote +>kde-user</quote +>, and <quote +>kde-devel</quote +> folders. </para> + +</answer> +</qandaentry> + +<qandaentry> +<question id="newsgroups"> +<para +>Is there a newsgroup about &kde;?</para> +</question> +<answer> +<para +>Yes, there is! It is at <literal +>comp.windows.x.kde</literal +>. In addition, there is also a German newsgroup at <literal +>de.alt.comp.kde</literal +>. Please note that it is not a good idea to ask questions which are already answered in this &FAQ;.</para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>Are there any other &kde;-related &FAQ;s?</para> +</question> +<answer> +<para +>Yes. Here is a list of them:</para> +<itemizedlist> +<listitem +><para +><ulink +url="http://www.kde.org/info/faq.php" +>&kde; &FAQ;</ulink +></para +></listitem> +<listitem +><para +><ulink +url="http://konqueror.org/faq/" +>&konqueror; &FAQ;</ulink +></para +></listitem> +<listitem +><para +><ulink +url="http://www.arts-project.org/doc/manual/index.html" +>aRts sound server documentation</ulink +></para +></listitem> + +<!-- Removed because the kmail FAQ is part of the KMail manual and not a --> +<!-- separate document +<listitem +><para +><ulink +url="http://kmail.kde.org/manual/faq.html" +>&kmail; +&FAQ;</ulink +></para +></listitem> +--> + +</itemizedlist> +</answer> +</qandaentry> + +</qandaset> +</chapter> + diff --git a/tde-i18n-en_GB/docs/kdebase/faq/nonkdeapps.docbook b/tde-i18n-en_GB/docs/kdebase/faq/nonkdeapps.docbook new file mode 100644 index 00000000000..911b619b63f --- /dev/null +++ b/tde-i18n-en_GB/docs/kdebase/faq/nonkdeapps.docbook @@ -0,0 +1,67 @@ +<!-- +<?xml version="1.0" ?> +<!DOCTYPE chapter PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" + "dtd/kdex.dtd"> +--> + +<chapter id="non-kde-apps"> +<title +>&kde; with non-&kde; applications</title> + +<!-- FIXME: This seems to be obsolete. The only similar option is "Apply *colors* to --> +<!-- non-kde apps" --> +<qandaset> +<qandaentry> +<question> +<para +>My non-&kde; applications like &Emacs; and <application +>kterm</application +> are running amok with strange colours!</para> +</question> +<answer> +<para +>Start the <application +>&kde; Control Centre</application +> and in <guimenu +>Appearance & Themes</guimenu +><guisubmenu +>Colours</guisubmenu +> uncheck the <guilabel +>Apply colours to non-KDE applications</guilabel +> checkbox and click <guibutton +>Apply</guibutton +>.</para> +</answer> +</qandaentry> + +<qandaentry> +<question +><para +>How can I set my default web browser to be something other than &konqueror;?</para +></question> +<answer> +<para +>If you are using &kde; 3.3 or later, open up the &kcontrolcenter; and navigate to the <menuchoice +><guimenu +>KDE Components</guimenu +><guimenuitem +>Component Chooser</guimenuitem +></menuchoice +> panel. Select <guilabel +>Web Browser</guilabel +> from the list on the left, then select <guilabel +>Open http and https URLs in the following browser:</guilabel +> and type in the name of the browser (⪚ <application +>mozilla</application +>, <application +>firefox</application +>, <application +>opera</application +>, &etc;) in the textbox.</para> +</answer> +</qandaentry> + + + +</qandaset> +</chapter> diff --git a/tde-i18n-en_GB/docs/kdebase/faq/notrelated.docbook b/tde-i18n-en_GB/docs/kdebase/faq/notrelated.docbook new file mode 100644 index 00000000000..3439bc16594 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdebase/faq/notrelated.docbook @@ -0,0 +1,309 @@ +<!-- if you want to validate this file separately, uncomment this prolog: + +<?xml version="1.0" ?> +<!DOCTYPE chapter PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" + "dtd/kdex.dtd"> + +--> + +<chapter id="not-kde"> +<title +>Not really &kde;-related, but frequently asked nevertheless.</title> + +<qandaset> +<qandaentry> +<question> +<para +>How do I change the screen resolution?</para> +</question> +<answer> +<para +>Use <keycombo action="simul" +>&Ctrl;&Alt;<keycap +>+</keycap +></keycombo +> and <keycombo action="simul" +>&Ctrl;&Alt;<keycap +>-</keycap +></keycombo +> to cycle through the resolutions you have defined in <filename +>XF86Config</filename +> (maybe under <filename class="directory" +>/etc/X11</filename +>; poke around first). If you prefer to get your hands dirty, you can always edit the file directly. By placing your favourite resolution at the beginning (or making it the only one listed), &X-Window; will always start up with that resolution. <caution +><para +>Always make a backup copy of your <filename +>XF86Config</filename +> file <emphasis +>before</emphasis +> you start editing it. Errors in this file can render &X-Window; unusable.</para +></caution> +<note +><para +>These instructions are only valid if you are running version 3.3.x of the XFree86 server. If you are running XFree86 4.x, you must consult with the <ulink url="http://xfree.org" +>XFree86(TM): Home Page</ulink +>.</para +></note +></para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>How do I change the colour depth?</para> +</question> +<answer> +<para +>There is no way you can do this on the fly. You can either start &X-Window; using <command +>startx <option +> -bpp <replaceable +>number</replaceable +></option +></command +> where <replaceable +>number</replaceable +> can be 8, 16, 24 or 32, depending on the depth you want. Alternatively, if you are using <application +>xdm</application +>/&kdm;, you need to edit <filename +>/etc/X11/xdm/Xservers</filename +> (may vary) and enter <userinput +>:0 local /usr/X11R6/bin/X -bpp 16</userinput +> for 16 bit colour depth.</para> +<para +>You can also edit the <filename +>XF86Config</filename +> file and add a line like <userinput +>DefaultColorDepth <replaceable +>number</replaceable +></userinput +> to Section "Screen". The next time you start X, it will run with the newly-configured colour depth.</para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>What can I do if I am using a 2-button mouse?</para> +</question> +<answer> +<para +>Go buy a 3-button one, or use third button emulation. The third button is emulated by pressing both the &LMB; and the &RMB; together. You would need to enable <option +>Emulate3Buttons</option +> in your <filename +>XF86Config</filename +> file. </para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>What is a "sticky" window?</para> +</question> +<answer> +<para +>In a virtual desktop environment with multiple virtual desktops, a "sticky" window will stay put on the screen when you switch between desktops, as if sticking to the glass of the screen. <application +>Xclock</application +> is a typical candidate for sticking, as you need to run only one instance of it, and it always stays with you. </para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>How do I replace the "X" mouse pointer with an arrow?</para> +</question> +<answer> +<para +>The various types of cursor available in X are defined in <filename class="headerfile" +>X11/cursorfont.h</filename +>. You can change it using <command +>xsetroot -cursor_name <replaceable +>name_of_cursor</replaceable +></command +>. For example, I have the following in my <filename +>.Xclients</filename +>:</para> +<screen +>xsetroot -cursor_name left_ptr +</screen> +<para +>This will create the common left-angled pointer. To see other alternatives, type <command +>xfd -fn cursor</command +>. And of course, do not forget that <command +>man xsetroot</command +> is your friend.</para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>How do I extract/install diff files?</para> +</question> +<answer> +<para +>To generate a context-diff suitable for patching, use <command +>diff -u <replaceable +>old-file new-file</replaceable +> > <replaceable +>patchfile</replaceable +></command +>. To apply the diff to a file (<abbrev +>i.e.</abbrev +> "patch the file"), execute <command +>patch < <replaceable +>patchfile</replaceable +></command +>.</para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>How do I get &Linux; to mount the floppy device for use with both DOS and ext2 formatted floppies?</para> +</question> +<answer> +<para +>Just specify the filesystem type as auto in <filename +>/etc/fstab</filename +>. Auto detection works fine for DOS and ext2.</para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>How do I start &kde; with the <keycap +>Num Lock</keycap +> on?</para> +</question> +<answer> +<para +>Have you tried <command +>man setleds</command +>? In addition, you might want to edit your <filename +>$<envar +>HOME</envar +>/.Xmodmap</filename +> and put the following lines in:</para> +<screen +>! redefines numeric keypad to be used without NumLock +keycode 79 = 7 +keycode 80 = 8 +keycode 81 = 9 + +keycode 83 = 4 +keycode 84 = 5 +keycode 85 = 6 + +keycode 87 = 1 +keycode 88 = 2 +keycode 89 = 3 + +keycode 90 = 0 +keycode 91 = comma +keycode 86 = plus + +! deactivates NumLock key +keycode 77 = +</screen> +<para +>Other possible alternatives:</para> +<itemizedlist> +<listitem +><para +><application +>xkeycaps</application +>: <mousebutton +>right</mousebutton +> clicking should allow edits. You may have to do this as root.</para +></listitem> +<listitem +><para +><command +>man XF86Config</command +> and look under section Keyboard.</para +></listitem> +<listitem +><para +>Install <application +>NumLockX</application +>, which is available from <ulink url="http://dforce.sh.cvut.cz/~seli/en/numlockx" +>http://dforce.sh.cvut.cz/~seli/en/numlockx</ulink +>.</para +></listitem> +</itemizedlist> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>How do I take window or desktop screenshots?</para> +</question> +<answer> +<para +>Use &ksnapshot;.</para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>Is there a tool to make webpages?</para> +</question> +<answer> +<para +>Yes, and there are a lot of them out there, including <application +>StarOffice</application +>, <application +>&Netscape; Composer</application +>, and <application +>XEmacs</application +>. There are also many &kde; applications. To find the most current list, go to <ulink url="http://kde-apps.org" +>kde-apps.org: The Latest in &kde; Applications</ulink +> and search for <emphasis +>web development</emphasis +>. Try as many as possible and choose the one most suitable to your needs.</para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>What do all those acronyms like AFAIK mean?</para> +</question> +<answer> +<para +><screen +>AAMOF: as a matter of fact +AFAIK: as far as I know +AISE: as I see it +BFN: bye for now +BION: believe it or not +BRB: be right back +BTW: by the way +CMIIW: correct me if I am wrong +FUD: fear, uncertainty, and doubt +FWIW: for what it's worth +FYI: for your information +HTH: hope this helps +IIRC: if I recall correctly +IMHO: in my humble opinion +LOL: laughing out loud +MYOB: mind your own business +PITA: pain in the ass +ROTFL: rolling on the floor laughing +RTFM: read the fine manual +SOP: standard operating procedure +TIA: thanks in advance +YMMV: your mileage may vary +</screen +></para> +</answer> +</qandaentry> +</qandaset> +</chapter> diff --git a/tde-i18n-en_GB/docs/kdebase/faq/panel.docbook b/tde-i18n-en_GB/docs/kdebase/faq/panel.docbook new file mode 100644 index 00000000000..b70fcd47355 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdebase/faq/panel.docbook @@ -0,0 +1,107 @@ +<!-- +<?xml version="1.0" ?> +<!DOCTYPE chapter PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" + "dtd/kdex.dtd"> +--> + +<chapter id="panel"> +<title +>The panel</title> + +<qandaset> +<qandaentry> +<question> +<para +>How do I add applications to the &kde; panel (&kicker;)?</para> +</question> +<answer> +<para +>There are several ways to add an application to the panel, of which the easiest is to right-click on the panel, and from the context menu which appears, select <menuchoice +><guimenu +>Panel Menu</guimenu +><guisubmenu +>Add</guisubmenu +><guisubmenu +>Application Button</guisubmenu +></menuchoice +> and then the application for which you want to add a link.</para> +<para +>For more ways of adding buttons to the panel, refer to the &kicker; Handbook.</para> + +</answer> +</qandaentry> + +<!-- Since I don't know the answer for this in KDE 2.2.1 I have to comment it out --> +<!-- +<qandaentry> +<question> +<para +>Is it possible to change the <guibutton +>K</guibutton +> button of +the panel to another picture?</para> +</question +>/ +<answer> +<para +>Look for +<filename +>$<envar +>HOME</envar +>/.kde/share/apps/kicker/pics/go.png</filename +> and +<filename +>$<envar +>HOME</envar +>/.kde/share/apps/kicker/pics/mini/go.png</filename> +and replace them. Do not forget to flatten the replacements to one +layer, or else you will not see anything. Create the folders if +they do not already exist. Then restart &kicker;.</para> +</answer> +</qandaentry> +--> + +<qandaentry> +<question +><para +>My desktop panel has disappeared. How can I get it back?</para> +</question> + +<answer> + +<para +>The panel disappearing is usually due to it crashing. This is most often caused by loading an applet that has a fatal bug or due to a bad installation of &kde; and/or the panel.</para> + +<para +>The easiest way to get the panel back is to launch the <guilabel +>Run Command</guilabel +> window by pressing <keycombo action="simul" +>&Alt;<keycap +>F2</keycap +> </keycombo +> and entering <userinput +><command +>kicker</command +></userinput +> and then pressing the <guibutton +>OK</guibutton +> button.</para> + +<para +>If the panel continues to disappear, you may wish to either remove or edit by hand your <filename +>$<envar +>KDEHOME</envar +>/share/config/kickerrc</filename +> file, where <filename class="directory" +>$<envar +>KDEHOME</envar +></filename +> is usually <filename class="directory" +>~/.kde</filename +>. If you choose to edit it by hand, start by removing the applet entry groups.</para> + +</answer> +</qandaentry> + +</qandaset> +</chapter> diff --git a/tde-i18n-en_GB/docs/kdebase/faq/tips.docbook b/tde-i18n-en_GB/docs/kdebase/faq/tips.docbook new file mode 100644 index 00000000000..9f7b4e80e26 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdebase/faq/tips.docbook @@ -0,0 +1,207 @@ +<!-- +<?xml version="1.0" ?> +<!DOCTYPE chapter PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" + "dtd/kdex.dtd"> +--> + +<chapter id="tips"> +<title +>Useful tips</title> + +<qandaset> +<qandaentry> +<question> +<para +>Reading documentation in &kde;</para> +</question> +<answer> +<para +>Pop up the <guilabel +>Run Command</guilabel +> window (<keycombo action="simul" +>&Alt;<keycap +>F2</keycap +></keycombo +> by default) and type: <itemizedlist> +<listitem> +<para +><command +>man:<replaceable +>command</replaceable +></command +> for man pages. It even unpacks on the fly if the man pages are gzipped.</para> +</listitem> + +<listitem> +<para +><command +>info:<replaceable +>command</replaceable +></command +> for info pages.</para> +</listitem> + +<listitem> +<para +><command +>help:<replaceable +>kdeappname</replaceable +></command +> for &kde; application help pages.</para> +</listitem> + +</itemizedlist> +</para> + +<para +>You can also enter any of these in the <guilabel +>Location</guilabel +> text box in &konqueror;.</para> +<para +>Or you can use the <application +>&kde; Help Centre</application +> if you are using &kde; 2. Simply start the <application +>&kde; Help Centre</application +> by clicking on the icon (the blue book with the yellow key) on the toolbar. Once the <application +>&kde; Help Centre</application +> has loaded, the window on the left will contain an entry called <guilabel +>Unix manual pages</guilabel +>. Click once on this entry, and you can browse through all the installed manual pages on your system.</para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>Move or resize windows quickly</para> +</question> +<answer> +<para +>To move a window, use <keycombo action="simul" +>&Alt;<mousebutton +>left</mousebutton +></keycombo +> mouse button. <keycombo action="simul" +>&Alt;<mousebutton +>right</mousebutton +></keycombo +> mouse button will resize the window. Last but not least, <keycombo action="simul" +>&Alt;<mousebutton +>middle</mousebutton +></keycombo +> mouse button raises/lowers the window. The <application +>&kde; Control Centre</application +> allows you to change these mouse bindings.</para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>Killing windows in &kde;</para> +</question> +<answer> +<para +>There is a standard keybinding (<keycombo action="simul" +>&Ctrl;&Alt;&Esc;</keycombo +>) that gives you a skull & crossbones cursor. Click that cursor on a window to kill it. The keybindings are viewable/changeable from the <application +>&kde; Control Centre</application +>. <caution +><para +>Using this option kills the program forcibly. Data may be lost, and some processes related to the program may remain active. Use only as a last resort.</para +></caution> +<!-- fixme: use only if necessary; processes might remain --></para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>What if something is so wrong that I ca not even get the skull & crossbones cursor? How do I get out of a total lockup?</para> +</question> +<answer> +<para +>These kind of locks tend to occur when an application locks up while it has a so called <quote +>mouse/keyboard grab</quote +>. When that happens you can try to select a virtual text console with <keycombo action="simul" +>&Ctrl;&Alt;<keycap +>F1</keycap +></keycombo +> and login. With the following command you will get a list of all running processes:</para> + +<screen +><userinput +> <command +>ps</command +> <option +>-aux</option +> | <command +>more</command +></userinput +></screen> + +<para +>By killing the process that has the mousegrab, your desktop will come to life again. Unfortunately you ca not see which process that is, so you will have to find out through trial and error. To kill a process use:</para> + +<screen +><userinput +> <command +>kill</command +> <option +>-9</option +> <replaceable +>pid</replaceable +></userinput +></screen> + +<para +>Here <replaceable +>pid</replaceable +> is the process id of the process, which is the first number on each line reported by <command +>ps</command +> <option +>-aux</option +>.</para> + +<para +>You can switch back to the desktop with <keycombo action="simul" +>&Ctrl;&Alt;<keycap +>F7</keycap +></keycombo +> (or <keycap +>F8</keycap +> through <keycap +>F9</keycap +> depending on your operating system) to see if things work again. When you press <keycombo action="simul" +>&Alt;<keycap +>Tab</keycap +></keycombo +> you should get a response from the window manager. If not, you need to get back to the text console and try to kill another process.</para> + +<para +>Good candidates to kill are: the application you were working with, &kicker;, &klipper; and &kdesktop;.</para> +</answer> +</qandaentry> + +<!-- fixme: how to do in KDE2.x +<qandaentry> +<question> +<para +>Switching window managers on the fly in &kde; 1.x</para> +</question> +<answer> +<para +>If you want to switch your window manager on the fly, type the +following into a terminal window: <command +>kwmcom +go:<replaceable +>blackbox</replaceable +></command +>. This switches to +Blackbox, but you can substitute any window manager you like.</para> +</answer> +</qandaentry> +--> + +</qandaset> +</chapter> diff --git a/tde-i18n-en_GB/docs/kdebase/faq/winmng.docbook b/tde-i18n-en_GB/docs/kdebase/faq/winmng.docbook new file mode 100644 index 00000000000..f2761a96dd7 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdebase/faq/winmng.docbook @@ -0,0 +1,129 @@ +<!-- +<?xml version="1.0" ?> +<!DOCTYPE chapter PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" + "dtd/kdex.dtd"> +--> + + + +<chapter id="windowmanager"> +<title +>The window manager</title> + +<para +>The default window manager provided by &kde; is the K Window Manager (&kwin;). Please read <quote +>The K Window Manager Handbook</quote +> (which should be accessible from the <application +>&kde; Help Centre</application +>) for usage information.</para> + +<qandaset> +<qandaentry> +<question> +<para +>Are there keyboard shortcuts for &kwin; operations?</para> +</question> +<answer> +<para +>Yes. Please refer to "The K Window Manager Handbook" for the list of shortcuts available.</para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>Can I define my own set of keyboard shortcuts?</para> +</question> +<answer> +<para +>Yes. Launch the <application +>&kde; Control Centre</application +> and select <menuchoice +><guimenu +>Regional & Accessibility</guimenu +><guimenuitem +>Keyboard Shortcuts</guimenuitem +></menuchoice +> to configure window manager bindings like maximising windows, &etc;. </para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>When I "iconify" a window, it disappears. Where does it go?</para> +</question> +<answer> +<para +>With many &X-Window; &GUI;s, the minimise button (a little dot) will erase the window that the program is running in and create, instead, an icon on the desktop. &kde; does not do this. Instead, when a window is iconified it is simply hidden (but the program is still running).</para> +<para +>There are a few ways to access <quote +>disappeared</quote +> windows:</para> +<itemizedlist> +<listitem> +<para +>If you are running the taskbar part of &kicker;, you can choose to have a list of tasks displayed on your desktop. Iconified tasks will have their names displayed in grey.</para> +</listitem> +<listitem> +<para +>If you click the &MMB; on the root window (&ie;, the background of the desktop), &kwin; will give you a list of all available tasks.</para> +</listitem> +</itemizedlist> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>How do I maximise windows only vertically or horizontally?</para> +</question> +<answer> +<para +>Provided your window is not already maximised, clicking on the maximise button with the &LMB;/&MMB;/&RMB; will maximise fully/vertically/horizontally respectively.</para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>What is <quote +>shading</quote +> a window?</para> +</question> +<answer> +<para +>By <quote +>shading</quote +> a window we mean <quote +>rolling up</quote +> the window leaving just the title bar visible. You can do this by double clicking on the window title bar.</para> +</answer> +</qandaentry> + +<!-- Not sure this is still applicable +<qandaentry> +<question> +<para +>Is it possible to have FVWM2-like shadow frameworks for the +placement of windows?</para> +</question> +<answer> +<para +>Yes. Run <application +>&kde; Control Center</application +> and select <guimenu +>Look and Feel</guimenu> +followed by <guisubmenu +>Window Behavior</guisubmenu +> and finally +<guimenuitem +>Advanced</guimenuitem +>. There is a dialog option that +allows you to set the placement policy you want.</para> +</answer> +</qandaentry> +--> +</qandaset> +</chapter> + |