diff options
Diffstat (limited to 'tde-i18n-en_GB/docs/kdeedu')
99 files changed, 21770 insertions, 0 deletions
diff --git a/tde-i18n-en_GB/docs/kdeedu/Makefile.am b/tde-i18n-en_GB/docs/kdeedu/Makefile.am new file mode 100644 index 00000000000..f781297a70f --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/Makefile.am @@ -0,0 +1,4 @@ +KDE_LANG = en_GB +SUBDIRS = $(AUTODIRS) +KDE_DOCS = AUTO +KDE_MANS = AUTO diff --git a/tde-i18n-en_GB/docs/kdeedu/Makefile.in b/tde-i18n-en_GB/docs/kdeedu/Makefile.in new file mode 100644 index 00000000000..d39df6d05af --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/Makefile.in @@ -0,0 +1,587 @@ +# 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/kdeedu +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 =. kstars klatin kturtle kmplot +KDE_DOCS = AUTO +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/kdeedu/Makefile'; \ +#>- cd $(top_srcdir) && \ +#>- $(AUTOMAKE) --gnu docs/kdeedu/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/kdeedu/Makefile'; \ + cd $(top_srcdir) && \ + $(AUTOMAKE) --gnu docs/kdeedu/Makefile + cd $(top_srcdir) && perl ../scripts/admin/am_edit -p../scripts/admin docs/kdeedu/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) + @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 + +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-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: + +install-dvi: install-dvi-recursive + +install-exec-am: + +install-html: install-html-recursive + +install-info: install-info-recursive + +install-man: + +install-pdf: install-pdf-recursive + +install-ps: install-ps-recursive + +installcheck-am: + +maintainer-clean: maintainer-clean-recursive + -rm -f Makefile +maintainer-clean-am: distclean-am maintainer-clean-generic + +mostlyclean: mostlyclean-recursive + +mostlyclean-am: mostlyclean-generic + +pdf: pdf-recursive + +pdf-am: + +ps: ps-recursive + +ps-am: + +uninstall-am: + +.MAKE: $(RECURSIVE_CLEAN_TARGETS) $(RECURSIVE_TARGETS) install-am \ + install-strip + +.PHONY: $(RECURSIVE_CLEAN_TARGETS) $(RECURSIVE_TARGETS) CTAGS GTAGS \ + all all-am check check-am clean clean-generic ctags \ + ctags-recursive distclean distclean-generic distclean-tags \ + distdir dvi dvi-am html html-am info info-am install \ + install-am install-data install-data-am install-dvi \ + install-dvi-am install-exec install-exec-am install-html \ + install-html-am install-info install-info-am install-man \ + install-pdf install-pdf-am install-ps install-ps-am \ + install-strip installcheck installcheck-am installdirs \ + installdirs-am maintainer-clean maintainer-clean-generic \ + mostlyclean mostlyclean-generic pdf pdf-am ps ps-am tags \ + tags-recursive uninstall uninstall-am + +# Tell versions [3.59,3.63) of GNU make to not export all variables. +# Otherwise a system limit (for SysV at least) may be exceeded. +.NOEXPORT: + +#>+ 2 +KDE_DIST=Makefile.in Makefile.am + +#>+ 2 +docs-am: + +#>+ 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/kdeedu/Makefile'; \ + cd $(top_srcdir) && \ + $(AUTOMAKE) --gnu docs/kdeedu/Makefile + cd $(top_srcdir) && perl ../scripts/admin/am_edit -p../scripts/admin docs/kdeedu/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/kdeedu/klatin/Makefile.am b/tde-i18n-en_GB/docs/kdeedu/klatin/Makefile.am new file mode 100644 index 00000000000..f781297a70f --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/klatin/Makefile.am @@ -0,0 +1,4 @@ +KDE_LANG = en_GB +SUBDIRS = $(AUTODIRS) +KDE_DOCS = AUTO +KDE_MANS = AUTO diff --git a/tde-i18n-en_GB/docs/kdeedu/klatin/Makefile.in b/tde-i18n-en_GB/docs/kdeedu/klatin/Makefile.in new file mode 100644 index 00000000000..31db619cdd4 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/klatin/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/kdeedu/klatin +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 = AUTO +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/kdeedu/klatin/Makefile'; \ +#>- cd $(top_srcdir) && \ +#>- $(AUTOMAKE) --gnu docs/kdeedu/klatin/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/kdeedu/klatin/Makefile'; \ + cd $(top_srcdir) && \ + $(AUTOMAKE) --gnu docs/kdeedu/klatin/Makefile + cd $(top_srcdir) && perl ../scripts/admin/am_edit -p../scripts/admin docs/kdeedu/klatin/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=adjectives.docbook nouns.docbook numbers.docbook index.docbook verbs.docbook Makefile.in Makefile.am pronouns.docbook index.cache.bz2 + +#>+ 24 +index.cache.bz2: $(srcdir)/index.docbook $(KDE_XSL_STYLESHEET) adjectives.docbook index.docbook pronouns.docbook nouns.docbook verbs.docbook numbers.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)/klatin + @if test -f index.cache.bz2; then \ + echo $(INSTALL_DATA) index.cache.bz2 $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/klatin/; \ + $(INSTALL_DATA) index.cache.bz2 $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/klatin/; \ + elif test -f $(srcdir)/index.cache.bz2; then \ + echo $(INSTALL_DATA) $(srcdir)/index.cache.bz2 $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/klatin/; \ + $(INSTALL_DATA) $(srcdir)/index.cache.bz2 $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/klatin/; \ + fi + -rm -f $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/klatin/common + $(LN_S) $(kde_libs_htmldir)/$(KDE_LANG)/common $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/klatin/common + +uninstall-docs: + -rm -rf $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/klatin + +clean-docs: + -rm -f index.cache.bz2 + + +#>+ 13 +install-nls: + $(mkinstalldirs) $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/klatin + @for base in adjectives.docbook index.docbook pronouns.docbook nouns.docbook verbs.docbook numbers.docbook ; do \ + echo $(INSTALL_DATA) $$base $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/klatin/$$base ;\ + $(INSTALL_DATA) $(srcdir)/$$base $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/klatin/$$base ;\ + done + +uninstall-nls: + for base in adjectives.docbook index.docbook pronouns.docbook nouns.docbook verbs.docbook numbers.docbook ; do \ + rm -f $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/klatin/$$base ;\ + done + + +#>+ 5 +distdir-nls: + for file in adjectives.docbook index.docbook pronouns.docbook nouns.docbook verbs.docbook numbers.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/kdeedu/klatin/Makefile'; \ + cd $(top_srcdir) && \ + $(AUTOMAKE) --gnu docs/kdeedu/klatin/Makefile + cd $(top_srcdir) && perl ../scripts/admin/am_edit -p../scripts/admin docs/kdeedu/klatin/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/kdeedu/klatin/adjectives.docbook b/tde-i18n-en_GB/docs/kdeedu/klatin/adjectives.docbook new file mode 100644 index 00000000000..fa210644c49 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/klatin/adjectives.docbook @@ -0,0 +1,436 @@ +<!-- Please don't translate Latin words --> +<!-- Please translate the following --> +<sect1 id="adjectives"> +<title +>KLatin Notes - Adjectives</title> + +<para +>Adjectives are words to describe nouns, and so they agree with the nouns. Agreeing means that they match the noun they refer to in three ways: gender, number and case. </para> + +<table frame="none"> +<!--Please translate title--> +<title +>1st and 2nd Declension Adjectives (212)</title> +<tgroup cols="4" colsep="1" rowsep="1"> +<colspec colname="c1"/> +<tbody> +<row> +<!-- Please translate SINGULAR and Like--> +<entry +>SINGULAR</entry> +<entry +>Like Servus</entry> +<entry +>Like Puella</entry> +<entry +>Like Bellum</entry> +</row> +<row> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +</row> +<row> +<!-- Please translate the first entry of each row--> +<entry +>Nominative</entry> +<entry +>bon-us</entry> +<entry +>bon-a</entry> +<entry +>bon-um</entry> +</row> +<row> +<entry +>Vocative</entry> +<entry +>bon-e</entry> +<entry +>bon-a</entry> +<entry +>bon-um</entry> +</row> +<row> +<entry +>Accusative</entry> +<entry +>bon-um</entry> +<entry +>bon-am</entry> +<entry +>bon-um</entry> +</row> +<row> +<entry +>Genitive</entry> +<entry +>bon-i</entry> +<entry +>bon-ae</entry> +<entry +>bon-i</entry> +</row> +<row> +<entry +>Dative</entry> +<entry +>bon-o</entry> +<entry +>bon-ae</entry> +<entry +>bon-o</entry> +</row> +<row> +<entry +>Ablative</entry> +<entry +>bon-o</entry> +<entry +>bon-a</entry> +<entry +>bon-o</entry> +</row> +<row> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +</row> +<row> +<!-- Please translate the first entry of each row--> +<entry +>PLURAL</entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +</row> +<row> +<entry +>Nominative</entry> +<entry +>bon-i</entry> +<entry +>bon-ae</entry> +<entry +>bon-a</entry> +</row> +<row> +<entry +>Vocative</entry> +<entry +>bon-i</entry> +<entry +>bon-ae</entry> +<entry +>bon-a</entry> +</row> +<row> +<entry +>Accusative</entry> +<entry +>bon-os</entry> +<entry +>bon-as</entry> +<entry +>bon-a</entry> +</row> +<row> +<entry +>Genitive</entry> +<entry +>bon-orum</entry> +<entry +>bon-arum</entry> +<entry +>bon-orum</entry> +</row> +<row> +<entry +>Dative</entry> +<entry +>bon-is</entry> +<entry +>bon-is</entry> +<entry +>bon-is</entry> +</row> +<row> +<entry +>Ablative</entry> +<entry +>bon-is</entry> +<entry +>bon-is</entry> +<entry +>bon-is</entry> +</row> +</tbody> +</tgroup> +</table> + +<table frame="none"> +<!--Please translate the title--> +<title +>3rd Declension Adjectives (333)</title> + +<tgroup cols="4" colsep="1" rowsep="1"> +<colspec colname="c1"/> +<tbody> +<row> +<!-- Please translate SINGULAR and Like--> +<entry +>SINGULAR</entry> +<entry +>Like Rex</entry> +<entry +>Like Rex</entry> +<entry +>Like Opus</entry> +</row> +<row> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +</row> +<row> +<!-- Please translate the first entry of each row--> +<entry +>Nominative</entry> +<entry +>trist-is</entry> +<entry +>trist-is</entry> +<entry +>trist-e</entry> +</row> +<row> +<entry +>Vocative</entry> +<entry +>trist-is</entry> +<entry +>trist-is</entry> +<entry +>trist-e</entry> +</row> +<row> +<entry +>Accusative</entry> +<entry +>trist-em</entry> +<entry +>trist-em</entry> +<entry +>trist-e</entry> +</row> +<row> +<entry +>Genitive</entry> +<entry +>trist-i</entry> +<entry +>trist-i</entry> +<entry +>trist-is</entry> +</row> +<row> +<entry +>Dative</entry> +<entry +>trist-is</entry> +<entry +>trist-is</entry> +<entry +>trist-i</entry> +</row> +<row> +<entry +>Ablative</entry> +<entry +>trist-i</entry> +<entry +>trist-i</entry> +<entry +>trist-i</entry> +</row> +<row> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +</row> +<row> +<!-- Please translate the first entry of each row--> +<entry +>PLURAL</entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +</row> +<row> +<entry +>Nominative</entry> +<entry +>trist-es</entry> +<entry +>trist-es</entry> +<entry +>trist-ia</entry> +</row> +<row> +<entry +>Vocative</entry> +<entry +>trist-es</entry> +<entry +>trist-es</entry> +<entry +>trist-ia</entry> +</row> +<row> +<entry +>Accusative</entry> +<entry +>trist-es</entry> +<entry +>trist-es</entry> +<entry +>trist-ia</entry> +</row> +<row> +<entry +>Genitive</entry> +<entry +>trist-ium</entry> +<entry +>trist-ium</entry> +<entry +>trist-ium</entry> +</row> +<row> +<entry +>Dative</entry> +<entry +>trist-ibus</entry> +<entry +>trist-ibus</entry> +<entry +>trist-ibus</entry> +</row> +<row> +<entry +>Ablative</entry> +<entry +>trist-ibus</entry> +<entry +>trist-ibus</entry> +<entry +>trist-ibus</entry> +</row> +</tbody> +</tgroup> +</table> + +<table frame="none"> +<!-- Please translate the title --> +<title +>Comparison of Adjectives</title> +<!-- Please translate --> +<tgroup cols="4" colsep="1" rowsep="1"> +<colspec colname="c1"/> +<tbody> +<row> +<entry +>Positive</entry> +<entry +>Comparative</entry> +<entry +>Superlative</entry> +<entry +>Notes</entry> +</row> +<row> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +</row> +<row> +<entry +>Normal form of Adjective</entry> +<!--Please stop translating --> +<entry +>Stem + ior,-ius</entry> +<entry +>Stem + issimus,-a,-um</entry> +<entry +></entry> +</row> +<row> +<entry +></entry> +<entry +></entry> +<entry +>Stem + rimus,-a,-um</entry> +<entry +>For adjectives which end with <emphasis +>-er</emphasis +>. For example: acer-rimus,-a,-um</entry> +</row> +<row> +<entry +></entry> +<entry +></entry> +<entry +>Stem + limus,-a,-um</entry> +<entry +>For adjectives which end with <emphasis +>-ilis</emphasis +>. For example: facil-limus,-a,-um</entry> +</row> +<row> +<entry +></entry> +<entry +></entry> +<entry +>Per/Prae + Adjective</entry> +<entry +></entry> +</row> +</tbody> +</tgroup> +</table> +</sect1> + diff --git a/tde-i18n-en_GB/docs/kdeedu/klatin/index.cache.bz2 b/tde-i18n-en_GB/docs/kdeedu/klatin/index.cache.bz2 Binary files differnew file mode 100644 index 00000000000..5caa3857eb9 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/klatin/index.cache.bz2 diff --git a/tde-i18n-en_GB/docs/kdeedu/klatin/index.docbook b/tde-i18n-en_GB/docs/kdeedu/klatin/index.docbook new file mode 100644 index 00000000000..ad1eaf9a1f6 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/klatin/index.docbook @@ -0,0 +1,668 @@ +<?xml version="1.0" ?> +<!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" "dtd/kdex.dtd" [ + <!ENTITY kapp "&klatin;" +><!-- replace klatin here --> + <!ENTITY kappname "&klatin;"> + <!ENTITY package "kdeedu"> + <!ENTITY kwordquiz "<application +>KWordQuiz</application +>"> + <!ENTITY kvtml "<acronym +>KVTML</acronym +>"> + <!--<!ENTITY klatin-index SYSTEM "klatin-index.docbook" +>--> + <!ENTITY numbers SYSTEM "numbers.docbook"> + <!ENTITY verbs SYSTEM "verbs.docbook"> + <!ENTITY adjectives SYSTEM "adjectives.docbook"> + <!ENTITY nouns SYSTEM "nouns.docbook"> + <!ENTITY pronouns SYSTEM "pronouns.docbook"> + <!ENTITY % addindex "IGNORE"> + <!ENTITY % British-English "INCLUDE" +><!-- change language only here --> +]> + +<book lang="&language;"> + +<bookinfo> +<title +>The &klatin; Handbook</title> + +<authorgroup> +<author +><firstname +>George</firstname +> <surname +>Wright</surname +> <affiliation +> <address +><email +>gwright@users.sourceforge.net</email +></address> +</affiliation> +</author> +<othercredit role="developer" +><firstname +>Anne-Marie</firstname +> <surname +>Mahfouf</surname +> <affiliation +> <address +><email +>annma@kde.org</email +></address> +</affiliation> +<contrib +>Help in documentation</contrib> +</othercredit> +</authorgroup> + +<othercredit role="translator" +><firstname +>Andrew </firstname +><surname +>Coles</surname +><affiliation +><address +><email +>andrew_coles@yahoo.co.uk</email +></address +></affiliation +><contrib +>Conversion to British English</contrib +></othercredit +> + +<copyright> +<year +>2001-2004</year> +<holder +>George Wright</holder> +</copyright> + +<legalnotice +>&FDLNotice;</legalnotice> + +<date +>2004-08-23</date> +<releaseinfo +>0.9</releaseinfo> + +<abstract> +<para +>&klatin; is a &kde; application to help revise/teach Latin. </para> +</abstract> + +<keywordset> +<keyword +>KDE</keyword> +<keyword +>kdeedu</keyword> +<keyword +>KLatin</keyword> +<keyword +>Latin</keyword> +<keyword +>education</keyword> +<keyword +>language</keyword> +<keyword +>latin</keyword> +</keywordset> + +</bookinfo> + +<chapter id="introduction"> +<title +>Introduction</title> + +<para +>&klatin; is a program to help revise Latin. There are three <quote +>sections</quote +> in which different aspects of the language can be revised. These are the vocabulary, grammar and verb testing sections. In addition there is a set of revision notes that can be used for self-guided revision. </para> +<para +>In the vocabulary section an &XML; file is loaded containing various words and their local language translations. &klatin; asks you what each of these words translate into. The questions take place in a multiple-choice environment. </para> +<para +>In the grammar and verb sections &klatin; asks for a particular part of a noun or a verb, such as the <quote +>ablative singular</quote +>, or the <quote +>1st person indicative passive plural</quote +>, and is not multiple choice. </para> +</chapter> + +<chapter id="using-klatin"> +<title +>Using &klatin;</title> + +<para +>When you start &klatin;, you are greeted by four options that you can choose from. </para> + +<screenshot> +<screeninfo +>&klatin; main screen, directly after the first start</screeninfo> +<mediaobject> +<imageobject> +<imagedata fileref="klatin1.png" format="PNG"/> +</imageobject> +<textobject> +<phrase +>&klatin; main screen</phrase> +</textobject> +</mediaobject> +</screenshot> + +<para +>The first one, <guilabel +>Vocabulary</guilabel +>, is a multiple-choice vocabulary tester. </para> + +<screenshot> +<screeninfo +>&klatin; vocabulary section</screeninfo> +<mediaobject> +<imageobject> +<imagedata fileref="klatin2.png" format="PNG"/> +</imageobject> +<textobject> +<phrase +>&klatin; vocabulary</phrase> +</textobject> +</mediaobject> +</screenshot> + +<para +>After you finish your test, a results screen is displayed. </para> + +<screenshot> +<screeninfo +>&klatin; vocabulary results</screeninfo> +<mediaobject> +<imageobject> +<imagedata fileref="results.png" format="PNG"/> +</imageobject> +<textobject> +<phrase +>&klatin; results</phrase> +</textobject> +</mediaobject> +</screenshot> + +<para +>The second, <guilabel +>Grammar</guilabel +> tests you on grammatical parts of nouns. </para> + +<screenshot> +<screeninfo +>&klatin; grammar section</screeninfo> +<mediaobject> +<imageobject> +<imagedata fileref="klatin3.png" format="PNG"/> +</imageobject> +<textobject> +<phrase +>&klatin; grammar</phrase> +</textobject> +</mediaobject> +</screenshot> + +<para +><guilabel +>Verbs</guilabel +> is almost the same as the <guilabel +>Grammar</guilabel +> section, except that it tests you on verb forms. </para> + +<screenshot> +<screeninfo +>&klatin; verbs section</screeninfo> +<mediaobject> +<imageobject> +<imagedata fileref="klatin4.png" format="PNG"/> +</imageobject> +<textobject> +<phrase +>&klatin; verbs</phrase> +</textobject> +</mediaobject> +</screenshot +> + +<para +>The fourth section, <guilabel +>Revision</guilabel +>, loads &konqueror; into the &klatin; revision notes section. </para> + +<para +>In addition to the options, you can also launch these sections via the menubar, in the <guimenu +>Section</guimenu +>. </para> + +<para +>The configuration dialog for &klatin; can be accessed by choosing <menuchoice +><guimenu +>Settings</guimenu +><guimenuitem +>Configure &klatin;...</guimenuitem +></menuchoice +> from the menu. In the <guilabel +>Vocabulary</guilabel +> page, you can set whether you want the test to take place from your language into Latin, or vice versa. You can also choose the default file which you want to use to test your vocabulary on, and you can also set how many questions you want to be tested on. </para> + +</chapter> + +<chapter id="klatin-mainwindow"> +<title +>The &klatin; main window</title> +<para +>The &klatin; main window consists of four option buttons to choose which section to enter, and a menubar.</para> +<para +>Choose from the <guilabel +>Revision Sections</guilabel +> list a section and click <guibutton +>Start!</guibutton +> to start the chosen section.</para> + +<para +>When you are finished with that section, click <guibutton +>Back</guibutton +> to return to &klatin;'s main menu.</para> + +</chapter> + +<chapter id="commands"> +<title +>Command Reference</title> +<sect1 id="menu-file"> +<title +>The <guimenu +>File</guimenu +> Menu</title> + +<variablelist> +<varlistentry> +<term +><menuchoice +><shortcut +> <keycombo action="simul" +>&Ctrl;<keycap +>Q</keycap +></keycombo +> </shortcut +> <guimenu +>File</guimenu +> <guimenuitem +>Quit</guimenuitem +> </menuchoice +></term> +<listitem +><para +><action +>Quits</action +> &klatin;</para +></listitem> +</varlistentry> +</variablelist> +</sect1> + +<sect1 id="menu-section"> +<title +>The <guimenu +>Section</guimenu +> Menu</title> +<variablelist> +<varlistentry> +<term +><menuchoice +><guimenu +>Section</guimenu +> <guimenuitem +>Load Vocabulary File</guimenuitem +> </menuchoice +></term> +<listitem +><para +><action +>Loads</action +> a new vocabulary file. This menu is only enabled if you are in the Vocabulary section</para +></listitem> +</varlistentry> + +<varlistentry> +<term +><menuchoice +><guimenu +>Section</guimenu +> <guimenuitem +>Load Vocabulary</guimenuitem +> </menuchoice +></term> +<listitem +><para +><action +>Loads</action +> the vocabulary section</para +></listitem> +</varlistentry> + +<varlistentry> +<term +><menuchoice +><guimenu +>Section</guimenu +> <guimenuitem +>Load Grammar</guimenuitem +> </menuchoice +></term> +<listitem +><para +><action +>Loads</action +> the grammar section</para +></listitem> +</varlistentry> + +<varlistentry> +<term +><menuchoice +><guimenu +>Section</guimenu +> <guimenuitem +>Load Verbs</guimenuitem +> </menuchoice +></term> +<listitem +><para +><action +>Loads</action +> the verbs section</para +></listitem> +</varlistentry> + +<varlistentry> +<term +><menuchoice +><guimenu +>Section</guimenu +> <guimenuitem +>Load Revision</guimenuitem +> </menuchoice +></term> +<listitem +><para +><action +>Loads</action +> the revision section</para +></listitem> +</varlistentry> + + +</variablelist> + +</sect1> +<sect1 id="menu-settings"> +<title +>The <guimenu +>Settings</guimenu +> Menu</title> + +<variablelist> +<varlistentry> +<term +><menuchoice +><guimenu +>Settings</guimenu +> <guimenuitem +>Configure Shortcuts...</guimenuitem +> </menuchoice +></term> +<listitem +><para +><action +>Configure</action +> the keyboard keys you use to access the different actions.</para> +</listitem> +</varlistentry> + +<varlistentry> +<term +><menuchoice +><guimenu +>Settings</guimenu +> <guimenuitem +>Configure &klatin;...</guimenuitem +> </menuchoice +></term> +<listitem +><para +><action +>Display</action +> the &klatin; settings dialogue </para +></listitem> +</varlistentry> + +</variablelist> + +</sect1> + +<sect1 id="menu-help"> +<title +>The <guimenu +>Help</guimenu +> Menu</title> +&help.menu.documentation; </sect1> +</chapter> + +<chapter id="translation"> +<title +>Translation Guide to &klatin;</title> + +<para +>Only the vocabulary files have to be translated in your language. The vocabulary files use the &kvtml; format, which is the same as other programs such as &kwordquiz; use. &kwordquiz; is very useful as you can create the vocabulary files in that and load them directly into &klatin;. </para> +<para +>Below is explained how you can translate &klatin; vocabulary files. At the moment, the files are only in English. </para> +<sect1 id="translate_vocab"> +<title +>How To Translate &klatin; vocabulary files</title> +<procedure> +<step> +<para +>Get the latest &klatin; code from CVS or a latest release. The words are stored in <filename class="directory" +>source_dir_of_kdeedu/klatin/klatin/data/vocab/en/</filename +> in files like <filename +>A.kvtml</filename +> for Latin words beginning with A, <filename +>BC.kvtml</filename +> for Latin words beginning with B and C and so on. </para> +</step> + +<step> +<para +>Create a new subdirectory in <filename class="directory" +>data/vocab/</filename +> named as your language code (for example, <filename class="directory" +>fr</filename +> for French, <filename class="directory" +>ja</filename +> for Japanese). Copy all the English vocabulary files there as well as the <filename +>Makefile.am</filename +>. Edit the <filename +>Makefile.am</filename +> and replace <quote +>en</quote +> with your language code. </para> +</step> + +<step> +<para +>In <filename class="directory" +>data/vocab/<replaceable +>your_language_code</replaceable +></filename +>, edit all the files and translate the English words, &ie; those that are between the <sgmltag class="starttag" +>t</sgmltag +> and <sgmltag class="endtag" +>t</sgmltag +> tags. </para> +</step> +<step> +<para +>Commit your files to CVS HEAD or tar them and send them to George <email +>gwright@users.sourceforge.net</email +> or to Anne-Marie <email +>annma@kde.org</email +>. </para> +</step> +</procedure> +</sect1> +</chapter> + +<chapter id="developers"> +<title +>Developer's Guide to &klatin;</title> +<sect1 id="add_files"> +<title +>Create new vocabulary files</title> +<para +>The &klatin; vocabulary database system is very easy to extend. Just look at the files and you'll understand! It uses the &kvtml; format, which is the same as other programs such as &kwordquiz; use. So you can open &kwordquiz; and use it to create the vocabulary files. </para> +<para +>You can save your new files in the corresponding folder depending on what language they refer to in <filename class="directory" +>.kde/share/apps/klatin/data/vocab/<replaceable +>language_code</replaceable +>/</filename +>. For example, English &kvtml; files are kept in a directory called <filename class="directory" +>en</filename +>, German files in <filename class="directory" +>de</filename +>, and so on. You can also send me your files so I can add them in the next &klatin; release. </para> +</sect1> +<!-- FIXME: They will still need specifically outlining --> +</chapter> + +<chapter id="credits"> + +<title +>Credits and Licence</title> + +<para +>&klatin; </para> +<para +>Program copyright 2001-2004 George Wright <email +>gwright@users.sourceforge.net</email +> </para> +<para +>Contributors: <itemizedlist> + +<listitem +><para +>Neil Stevens <email +>neil@qualityassistant.org</email +></para> +</listitem> +<listitem +><para +>Anne-Marie Mahfouf <email +>annma@kde.org</email +></para> +</listitem> +<listitem +><para +>Mark Westcott <email +>mark@houseoffish.org</email +></para> +</listitem> + +</itemizedlist> +</para> + +<para +>Documentation copyright 2001-2004 George Wright <email +>gwright@users.sourceforge.net</email +> </para> + +<para +>Andrew Coles<email +>andrew_coles@yahoo.co.uk</email +></para +> +&underFDL; &underGPL; </chapter> + +<chapter id="klatin-index"> +<title +>&klatin; notes</title> + +<para +>Welcome to the &klatin; notes section. This is aimed to help you in your revision and covers the English <acronym +>GCSE</acronym +> syllabus (England). </para> + +<para +>Here are the different sections you can get help for: </para> + +<itemizedlist> +<listitem +><para +><link +linkend="numbers" +>Latin numbers</link> +</para +></listitem> +<listitem +><para +><link +linkend="verbs" +>Latin verbs</link> +</para +></listitem> +<listitem +><para +><link +linkend="nouns" +>Latin nouns</link> +</para +></listitem> +<listitem +><para +><link +linkend="adjectives" +>Latin adjectives</link> +</para +></listitem> +<listitem +><para +><link +linkend="pronouns" +>Latin pronouns</link> +</para +></listitem> +</itemizedlist> +&numbers; &verbs; &nouns; &adjectives; &pronouns; </chapter> + +<appendix id="installation"> +<title +>Installation</title> + +<sect1 id="getting-klatin"> +<title +>How to obtain &klatin;</title> +&install.intro.documentation; </sect1> + +<sect1 id="compilation"> +<title +>Compilation and Installation</title> +&install.compile.documentation; </sect1> + +</appendix> + +&documentation.index; +</book> +<!-- +Local Variables: +mode: sgml +sgml-minimize-attributes:nil +sgml-general-insert-case:lower +sgml-indent-step:0 +sgml-indent-data:nil +End: +--> + diff --git a/tde-i18n-en_GB/docs/kdeedu/klatin/nouns.docbook b/tde-i18n-en_GB/docs/kdeedu/klatin/nouns.docbook new file mode 100644 index 00000000000..8a180766639 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/klatin/nouns.docbook @@ -0,0 +1,367 @@ +<!-- Please don't translate Latin words --> +<!-- Please translate --> +<sect1 id="nouns"> +<title +>KLatin Notes - Nouns </title> + +<para +>Nouns, like verbs, are divided into groups, called <emphasis +>declensions</emphasis +>. There are five declensions and three genders: masculine, feminine and neuter. </para> +<para +>The stem of a noun is the basic part of the noun that does not change. To get the stem of a noun, take the genitive singular of the noun and take off its ending. For example: the stem of <emphasis +>puella</emphasis +> is <emphasis +>puell</emphasis +>; while the stem of <emphasis +>rex</emphasis +> is <emphasis +>reg</emphasis +>, because its genitive is <emphasis +>reg-is</emphasis +>. </para> + +<sect2 id="listing"> +<title +>Latin Nouns</title> + +<table frame="none"> +<title +>Noun listings</title> +<tgroup cols="9" colsep="1" rowsep="1"> +<colspec colname="c1"/> +<tbody> +<row> +<!-- Please translate --> +<entry +>SINGULAR</entry> +<entry +>1st Feminine</entry> +<entry +>2nd Masculine</entry> +<entry +>2nd Neuter</entry> +<entry +>3rd Masc/Fem</entry> +<entry +>3rd Neuter</entry> +<entry +>4th Masculine</entry> +<entry +>4th Neuter</entry> +<entry +>5th Feminine</entry> +</row> +<row> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +</row> +<row> +<!--From now on please just translate first entry of each row--> +<entry +>Nominative</entry> +<entry +>puell-a</entry> +<entry +>serv-us</entry> +<entry +>bell-um</entry> +<entry +><emphasis +>rex</emphasis +></entry> +<entry +>opus</entry> +<entry +>grad-us</entry> +<entry +>genu</entry> +<entry +>res</entry> +</row> +<row> +<entry +>Vocative</entry> +<entry +>puell-a</entry> +<entry +>serv-e</entry> +<entry +>bell-um</entry> +<entry +><emphasis +>rex</emphasis +></entry> +<entry +>opus</entry> +<entry +>grad-us</entry> +<entry +>genu</entry> +<entry +>res</entry> +</row> +<row> +<entry +>Accusative</entry> +<entry +>puell-am</entry> +<entry +>serv-um</entry> +<entry +>bell-um</entry> +<entry +>reg-em</entry> +<entry +>opus</entry> +<entry +>grad-um</entry> +<entry +>genu</entry> +<entry +>re-m</entry> +</row> +<row> +<entry +>Genitive</entry> +<entry +>puell-ae</entry> +<entry +>serv-i</entry> +<entry +>bell-i</entry> +<entry +>reg-is</entry> +<entry +>oper-is</entry> +<entry +>grad-us</entry> +<entry +>gen-u</entry> +<entry +>re-i</entry> +</row> +<row> +<entry +>Dative</entry> +<entry +>puell-ae</entry> +<entry +>serv-o</entry> +<entry +>bell-o</entry> +<entry +>reg-i</entry> +<entry +>oper-i</entry> +<entry +>grad-ui</entry> +<entry +>gen-u</entry> +<entry +>re-i</entry> +</row> +<row> +<entry +>Ablative</entry> +<entry +>puell-a</entry> +<entry +>serv-o</entry> +<entry +>bell-o</entry> +<entry +>reg-e</entry> +<entry +>oper-e</entry> +<entry +>grad-u</entry> +<entry +>gen-u</entry> +<entry +>re</entry> +</row> + +<row> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +</row> +<row> +<!-- Please translate only the first entry of each row --> +<entry +>PLURAL</entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +</row> +<row> +<entry +>Nominative</entry> +<entry +>puell-ae</entry> +<entry +>serv-i</entry> +<entry +>bell-a</entry> +<entry +>reg-es</entry> +<entry +>oper-a</entry> +<entry +>grad-us</entry> +<entry +>gen-ua</entry> +<entry +>res</entry> +</row> +<row> +<entry +>Vocative</entry> +<entry +>puell-ae</entry> +<entry +>serv-i</entry> +<entry +>bell-a</entry> +<entry +>reg-es</entry> +<entry +>oper-a</entry> +<entry +>grad-us</entry> +<entry +>gen-ua</entry> +<entry +>res</entry> +</row> +<row> +<entry +>Accusative</entry> +<entry +>puell-as</entry> +<entry +>serv-os</entry> +<entry +>bell-a</entry> +<entry +>reg-es</entry> +<entry +>oper-a</entry> +<entry +>grad-us</entry> +<entry +>gen-ua</entry> +<entry +>res</entry> +</row> +<row> +<entry +>Genitive</entry> +<entry +>puell-arum</entry> +<entry +>serv-orum</entry> +<entry +>bell-orum</entry> +<entry +>reg-um</entry> +<entry +>oper-um</entry> +<entry +>grad-uum</entry> +<entry +>gen-uum</entry> +<entry +>re-rum</entry> +</row> +<row> +<entry +>Dative</entry> +<entry +>puell-is</entry> +<entry +>serv-is</entry> +<entry +>bell-is</entry> +<entry +>reg-ibus</entry> +<entry +>oper-ibus</entry> +<entry +>grad-ibus</entry> +<entry +>gen-ibus</entry> +<entry +>re-bus</entry> +</row> +<row> +<entry +>Ablative</entry> +<entry +>puell-is</entry> +<entry +>serv-is</entry> +<entry +>bell-is</entry> +<entry +>reg-ibus</entry> +<entry +>oper-ibus</entry> +<entry +>grad-ibus</entry> +<entry +>gen-ibus</entry> +<entry +>re-bus</entry> +</row> +</tbody> +</tgroup> +</table> + +</sect2> +</sect1> diff --git a/tde-i18n-en_GB/docs/kdeedu/klatin/numbers.docbook b/tde-i18n-en_GB/docs/kdeedu/klatin/numbers.docbook new file mode 100644 index 00000000000..2fef0ebc4d4 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/klatin/numbers.docbook @@ -0,0 +1,340 @@ +<!-- Please don't translate Latin words --> +<!-- Please translate --> +<sect1 id="numbers"> +<title +>KLatin Notes - Numbers </title> + +<para +>The Romans had a particular set of numerals and had names for each of their numbers. In this section are listed some numbers and their corresponding symbol. </para> +<table frame="none"> +<title +>Numbers</title> +<!-- translators: don't translate the following --> +<tgroup cols="3" colsep="1" rowsep="1"> +<colspec colname="c1"/> +<tbody> +<row> +<entry +>1</entry> +<entry +>I</entry> +<entry +>unus</entry> +</row> +<row> +<entry +>2</entry> +<entry +>II</entry> +<entry +>duo</entry> +</row> +<row> +<entry +>3</entry> +<entry +>III</entry> +<entry +>tres</entry> +</row> +<row> +<entry +>4</entry> +<entry +>IV</entry> +<entry +>quattuor</entry> +</row> +<row> +<entry +>5</entry> +<entry +>V</entry> +<entry +>quinque</entry> +</row> +<row> +<entry +>6</entry> +<entry +>VI</entry> +<entry +>sex</entry> +</row> +<row> +<entry +>7</entry> +<entry +>VII</entry> +<entry +>septem</entry> +</row> +<row> +<entry +>8</entry> +<entry +>VIII</entry> +<entry +>octo</entry> +</row> +<row> +<entry +>9</entry> +<entry +>IX</entry> +<entry +>novem</entry> +</row> +<row> +<entry +>10</entry> +<entry +>X</entry> +<entry +>decem</entry> +</row> +<row> +<entry +>11</entry> +<entry +>XI</entry> +<entry +>undecim</entry> +</row> +<row> +<entry +>12</entry> +<entry +>XII</entry> +<entry +>duodecim</entry> +</row> +<row> +<entry +>13</entry> +<entry +>XIII</entry> +<entry +>tredecim</entry> +</row> +<row> +<entry +>14</entry> +<entry +>XIV</entry> +<entry +>quattuordecim</entry> +</row> +<row> +<entry +>15</entry> +<entry +>XV</entry> +<entry +>quindecim</entry> +</row> +<row> +<entry +>16</entry> +<entry +>XVI</entry> +<entry +>sedecim</entry> +</row> +<row> +<entry +>17</entry> +<entry +>XVII</entry> +<entry +>septendecim</entry> +</row> +<row> +<entry +>18</entry> +<entry +>XVIII</entry> +<entry +>duodeviginti</entry> +</row> +<row> +<entry +>19</entry> +<entry +>XIX</entry> +<entry +>undeviginti</entry> +</row> +<row> +<entry +>20</entry> +<entry +>XX</entry> +<entry +>viginti</entry> +</row> +<row> +<entry +>21</entry> +<entry +>XXI</entry> +<entry +>vigintiunus</entry> +</row> +<row> +<entry +>22</entry> +<entry +>XXII</entry> +<entry +>vigintiduo</entry> +</row> +<row> +<entry +>30</entry> +<entry +>XXX</entry> +<entry +>triginta</entry> +</row> +<row> +<entry +>40</entry> +<entry +>XL</entry> +<entry +>quadraginta</entry> +</row> +<row> +<entry +>50</entry> +<entry +>L</entry> +<entry +>quinquaginta</entry> +</row> +<row> +<entry +>60</entry> +<entry +>LX</entry> +<entry +>sexaginta</entry> +</row> +<row> +<entry +>70</entry> +<entry +>LXX</entry> +<entry +>septuaginta</entry> +</row> +<row> +<entry +>80</entry> +<entry +>LXXX</entry> +<entry +>octoginta</entry> +</row> +<row> +<entry +>90</entry> +<entry +>XC</entry> +<entry +>nonaginta</entry> +</row> +<row> +<entry +>100</entry> +<entry +>C</entry> +<entry +>centum</entry> +</row> +<row> +<entry +>200</entry> +<entry +>CC</entry> +<entry +>ducenti</entry> +</row> +<row> +<entry +>300</entry> +<entry +>CCC</entry> +<entry +>trecenti</entry> +</row> +<row> +<entry +>400</entry> +<entry +>CD</entry> +<entry +>quadrigenti</entry> +</row> +<row> +<entry +>500</entry> +<entry +>D</entry> +<entry +>quingenti</entry> +</row> +<row> +<entry +>600</entry> +<entry +>DC</entry> +<entry +>sescenti</entry> +</row> +<row> +<entry +>700</entry> +<entry +>DCC</entry> +<entry +>septigenti</entry> +</row> +<row> +<entry +>800</entry> +<entry +>DCCC</entry> +<entry +>octigenti</entry> +</row> +<row> +<entry +>900</entry> +<entry +>CM</entry> +<entry +>nongenti</entry> +</row> +<row> +<entry +>1000</entry> +<entry +>M</entry> +<entry +>mille</entry> +</row> +<row> +<entry +>2000</entry> +<entry +>MM</entry> +<entry +>duo milia</entry> +</row> +</tbody> +</tgroup> +</table> + +</sect1> diff --git a/tde-i18n-en_GB/docs/kdeedu/klatin/pronouns.docbook b/tde-i18n-en_GB/docs/kdeedu/klatin/pronouns.docbook new file mode 100644 index 00000000000..4d3edb21703 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/klatin/pronouns.docbook @@ -0,0 +1,523 @@ +<!-- Please translate the following --> +<sect1 id="pronouns"> +<title +>KLatin Notes - Pronouns </title> +<para +>Here are some pronouns. </para> + +<table frame="none"> +<title +>Personal Pronouns</title> +<!-- Please don't translate the following until next title --> +<tgroup cols="2" colsep="1" rowsep="1"> +<colspec colname="c1"/> +<tbody> +<!-- Translate the following two entries --> +<row> +<entry +><emphasis +>Me</emphasis +></entry> +<entry +><emphasis +>You</emphasis +></entry> +</row> + +<row> +<entry +>ego</entry> +<entry +>tu</entry> +</row> +<row> +<entry +>me</entry> +<entry +>te</entry> +</row> +<row> +<entry +>mei</entry> +<entry +>tui</entry> +</row> +<row> +<entry +>mihi</entry> +<entry +>tibi</entry> +</row> +<row> +<entry +>me</entry> +<entry +>te</entry> +</row> +<row> +<entry +></entry> +<entry +></entry> +</row> +<!-- Translate the following two entries --> +<row> +<entry +><emphasis +>We</emphasis +></entry> +<entry +><emphasis +>You (Pl)</emphasis +></entry> +</row> +<row> +<entry +>nos</entry> +<entry +>vos</entry> +</row> +<row> +<entry +>nos</entry> +<entry +>vos</entry> +</row> +<row> +<entry +>nostri/nostrum</entry> +<entry +>vestri/vestrum</entry> +</row> +<row> +<entry +>nobis</entry> +<entry +>vobis</entry> +</row> +<row> +<entry +>nobis</entry> +<entry +>vobis</entry> +</row> +</tbody> +</tgroup> +</table> + +<table frame="none"> +<!-- Please translate title--> +<title +>3rd Person Personal Pronouns</title> +<!-- Please don't translate the following until next title--> +<tgroup cols="4" colsep="1" rowsep="1"> +<colspec colname="c1"/> +<tbody> +<!-- Translate the following entry --> +<row> +<entry +></entry> +<entry +><emphasis +>He,</emphasis +></entry> +<entry +><emphasis +>She,</emphasis +></entry> +<entry +><emphasis +>It</emphasis +></entry> +</row> +<row> +<entry +>SINGULAR</entry> +<entry +>is</entry> +<entry +>ea</entry> +<entry +>id</entry> +</row> +<row> +<entry +></entry> +<entry +>eum</entry> +<entry +>eum</entry> +<entry +>id</entry> +</row> +<row> +<entry +></entry> +<entry +>eius</entry> +<entry +>eius</entry> +<entry +>eius</entry> +</row> +<row> +<entry +></entry> +<entry +>ei</entry> +<entry +>ei</entry> +<entry +>ei</entry> +</row> +<row> +<entry +></entry> +<entry +>eo</entry> +<entry +>ea</entry> +<entry +>eo</entry> +</row> +<row> +<entry +>PLURAL</entry> +<entry +>ei</entry> +<entry +>eae</entry> +<entry +>ea</entry> +</row> +<row> +<entry +></entry> +<entry +>eos</entry> +<entry +>eas</entry> +<entry +>ea</entry> +</row> +<row> +<entry +></entry> +<entry +>eorum</entry> +<entry +>earum</entry> +<entry +>eorum</entry> +</row> +<row> +<entry +></entry> +<entry +>eis</entry> +<entry +>eis</entry> +<entry +>eis</entry> +</row> +<row> +<entry +></entry> +<entry +>eis</entry> +<entry +>eis</entry> +<entry +>eis</entry> +</row> +</tbody> +</tgroup> +</table> + +<table frame="none"> +<!-- Please translate the title--> +<title +>Demonstrative Pronouns</title> +<!-- Please don't translate the following --> +<tgroup cols="4" colsep="1" rowsep="1"> +<colspec colname="c1"/> +<tbody> +<!-- Translate the following entry --> +<row> +<entry +><emphasis +>This</emphasis +></entry> +</row> +<row> +<entry +>SINGULAR</entry> +<entry +>hic</entry> +<entry +>haec</entry> +<entry +>hoc</entry> +</row> +<row> +<entry +></entry> +<entry +>hunc</entry> +<entry +>hanc</entry> +<entry +>hoc</entry> +</row> +<row> +<entry +></entry> +<entry +>huius</entry> +<entry +>huius</entry> +<entry +>huius</entry> +</row> +<row> +<entry +></entry> +<entry +>huic</entry> +<entry +>huic</entry> +<entry +>huic</entry> +</row> +<row> +<entry +></entry> +<entry +>hoc</entry> +<entry +>hac</entry> +<entry +>hoc</entry> +</row> +<row> +<entry +>PLURAL</entry> +<entry +>hi</entry> +<entry +>hae</entry> +<entry +>haec</entry> +</row> +<row> +<entry +></entry> +<entry +>hos</entry> +<entry +>has</entry> +<entry +>heac</entry> +</row> +<row> +<entry +></entry> +<entry +>horum</entry> +<entry +>harum</entry> +<entry +>horum</entry> +</row> +<row> +<entry +></entry> +<entry +>his</entry> +<entry +>his</entry> +<entry +>his</entry> +</row> +<row> +<entry +></entry> +<entry +>his</entry> +<entry +>his</entry> +<entry +>his</entry> +</row> +<row> +<entry +></entry> +<entry +></entry> +<entry +></entry> +</row> +<!-- Translate the following entry --> +<row> +<entry +><emphasis +>That</emphasis +></entry> +</row> +<row> +<entry +>SINGULAR</entry> +<entry +>ille</entry> +<entry +>illa</entry> +<entry +>illud</entry> +</row> +<row> +<entry +></entry> +<entry +>illum</entry> +<entry +>illam</entry> +<entry +>illud</entry> +</row> +<row> +<entry +></entry> +<entry +>illius</entry> +<entry +>illius</entry> +<entry +>illius</entry> +</row> +<row> +<entry +></entry> +<entry +>illi</entry> +<entry +>illi</entry> +<entry +>illi</entry> +</row> +<row> +<entry +></entry> +<entry +>illo</entry> +<entry +>illa</entry> +<entry +>illo</entry> +</row> +<row> +<entry +>PLURAL</entry> +<entry +>illi</entry> +<entry +>illae</entry> +<entry +>illa</entry> +</row> +<row> +<entry +></entry> +<entry +>illos</entry> +<entry +>illas</entry> +<entry +>illa</entry> +</row> +<row> +<entry +></entry> +<entry +>illorum</entry> +<entry +>illarum</entry> +<entry +>illorum</entry> +</row> +<row> +<entry +></entry> +<entry +>illis</entry> +<entry +>illis</entry> +<entry +>illis</entry> +</row> +<row> +<entry +></entry> +<entry +>illis</entry> +<entry +>illis</entry> +<entry +>illis</entry> +</row> +</tbody> +</tgroup> +</table> + +<table frame="none"> +<title +>Negative Pronouns</title> +<!-- Please don't translate the following until next title --> +<tgroup cols="2" colsep="1" rowsep="1"> +<colspec colname="c1"/> +<tbody> +<!-- Translate the following two entries --> +<row> +<entry +><emphasis +>Noone</emphasis +></entry> +<entry +><emphasis +>Nothing</emphasis +></entry> +</row> +<row> +<entry +>nemo</entry> +<entry +>nihil</entry> +</row> +<row> +<entry +>neminem</entry> +<entry +>nihil/nil</entry> +</row> +<row> +<entry +>nullius/neminis</entry> +<entry +>nullius rei</entry> +</row> +<row> +<entry +>nemini/nulli</entry> +<entry +>nulli rei</entry> +</row> +<row> +<entry +>nullo/nemine</entry> +<entry +>nulla re</entry> +</row> +</tbody> +</tgroup> +</table> + +</sect1> diff --git a/tde-i18n-en_GB/docs/kdeedu/klatin/verbs.docbook b/tde-i18n-en_GB/docs/kdeedu/klatin/verbs.docbook new file mode 100644 index 00000000000..2585211cf0b --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/klatin/verbs.docbook @@ -0,0 +1,2131 @@ +<!-- Translators: please don't translate Latin words --> +<sect1 id="verbs"> +<!-- Please translate --> +<title +>KLatin Notes - Verbs </title> + +<para +>All languages have verbs. Latin verbs are divided into four categories, called <emphasis +>conjugations</emphasis +>. These conjugations are divisions of verbs that, generally, use the same stem formation and have the same endings. </para> + +<para +>The stem of a verb is the basic part of the verb that does not change. For example, the stem of <emphasis +>moneo</emphasis +> is <emphasis +>mone</emphasis +>. To get the stem of the verb, take the first person singular of the verb, and take off the -o ending. The verb <quote +>sum</quote +> (I am) is totally irregular, and does not have a consistent stem. </para> + +<table frame="none"> +<!-- Please translate the title--> +<title +>Verb listings - Indicative Active</title> +<tgroup cols="6" colsep="1" rowsep="1"> +<colspec colname="c1"/> +<tbody> +<row> +<!-- Please translate --> +<entry +>TENSE</entry> +<entry +>1st</entry> +<entry +>2nd</entry> +<entry +>3rd</entry> +<entry +>4th</entry> +<entry +>SUM - I</entry> +</row> +<row> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +</row> +<row> +<!-- translate only the first entry of each row if there is one --> +<entry +>PRESENT</entry> +<entry +>am-o</entry> +<entry +>mone-o</entry> +<entry +>reg-o</entry> +<entry +>audi-o</entry> +<entry +>sum</entry> +</row> +<row> +<entry +></entry> +<entry +>ama-s</entry> +<entry +>mone-s</entry> +<entry +>regi-s</entry> +<entry +>audi-s</entry> +<entry +>es</entry> +</row> +<row> +<entry +>I love, am loving</entry> +<entry +>ama-t</entry> +<entry +>mone-t</entry> +<entry +>regi-t</entry> +<entry +>audi-t</entry> +<entry +>est</entry> +</row> +<row> +<entry +></entry> +<entry +>ama-mus</entry> +<entry +>mone-mus</entry> +<entry +>regi-mus</entry> +<entry +>audi-mus</entry> +<entry +>sumus</entry> +</row> +<row> +<entry +></entry> +<entry +>ama-tis</entry> +<entry +>mone-tis</entry> +<entry +>regi-tis</entry> +<entry +>audi-tis</entry> +<entry +>estis</entry> +</row> +<row> +<entry +></entry> +<entry +>ama-nt</entry> +<entry +>mone-nt</entry> +<entry +>regu-nt</entry> +<entry +>audi-unt</entry> +<entry +>sunt</entry> +</row> +<row> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +</row> +<row> +<!-- Please translate only the first entry of each row if there is one --> +<entry +>FUTURE</entry> +<entry +>ama-bo</entry> +<entry +>mone-bo</entry> +<entry +>reg-am</entry> +<entry +>audi-am</entry> +<entry +>ero</entry> +</row> +<row> +<entry +></entry> +<entry +>ama-bis</entry> +<entry +>mone-bis</entry> +<entry +>reg-es</entry> +<entry +>audi-es</entry> +<entry +>eris</entry> +</row> +<row> +<entry +>I will love</entry> +<entry +>ama-bit</entry> +<entry +>mone-bit</entry> +<entry +>reg-et</entry> +<entry +>audi-et</entry> +<entry +>erit</entry> +</row> +<row> +<entry +></entry> +<entry +>ama-bimus</entry> +<entry +>mone-bimus</entry> +<entry +>reg-emus</entry> +<entry +>audi-emus</entry> +<entry +>erimus</entry> +</row> +<row> +<entry +></entry> +<entry +>ama-bitis</entry> +<entry +>mone-bitis</entry> +<entry +>reg-etis</entry> +<entry +>audi-etis</entry> +<entry +>eritis</entry> +</row> +<row> +<entry +></entry> +<entry +>ama-bunt</entry> +<entry +>mone-bunt</entry> +<entry +>reg-ent</entry> +<entry +>audi-ent</entry> +<entry +>erunt</entry> +</row> +<row> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +</row> +<row> +<!-- Please translate only the first entry of each row if there is one --> +<entry +>IMPERFECT</entry> +<entry +>ama-bam</entry> +<entry +>mone-bam</entry> +<entry +>rege-bam</entry> +<entry +>audi-bam</entry> +<entry +>eram</entry> +</row> +<row> +<entry +></entry> +<entry +>ama-bas</entry> +<entry +>mone-bas</entry> +<entry +>rege-bas</entry> +<entry +>audi-bas</entry> +<entry +>eras</entry> +</row> +<row> +<entry +>I was loving</entry> +<entry +>ama-bat</entry> +<entry +>mone-bat</entry> +<entry +>rege-bat</entry> +<entry +>audi-bat</entry> +<entry +>erat</entry> +</row> +<row> +<entry +>I used to love</entry> +<entry +>ama-bamus</entry> +<entry +>mone-bamus</entry> +<entry +>rege-bamus</entry> +<entry +>audi-bamus</entry> +<entry +>eramus</entry> +</row> +<row> +<entry +>I began to love</entry> +<entry +>ama-batis</entry> +<entry +>mone-batis</entry> +<entry +>rege-batis</entry> +<entry +>audi-batis</entry> +<entry +>eratis</entry> +</row> +<row> +<entry +></entry> +<entry +>ama-bant</entry> +<entry +>mone-bant</entry> +<entry +>rege-bant</entry> +<entry +>audi-bant</entry> +<entry +>erant</entry> +</row> +<row> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +</row> +<row> +<!-- Please translate only the first entry of each row if there is one --> +<entry +>PERFECT</entry> +<entry +>amav-i</entry> +<entry +>monu-i</entry> +<entry +>rex-i</entry> +<entry +>audiv-i</entry> +<entry +>fu-i</entry> +</row> +<row> +<entry +></entry> +<entry +>amav-isti</entry> +<entry +>monu-isti</entry> +<entry +>rex-isti</entry> +<entry +>audiv-isti</entry> +<entry +>fu-isti</entry> +</row> +<row> +<entry +>I have loved</entry> +<entry +>amav-it</entry> +<entry +>monu-it</entry> +<entry +>rex-it</entry> +<entry +>audiv-it</entry> +<entry +>fu-it</entry> +</row> +<row> +<entry +></entry> +<entry +>amav-imus</entry> +<entry +>monu-imus</entry> +<entry +>rex-imus</entry> +<entry +>audiv-imus</entry> +<entry +>fu-imus</entry> +</row> +<row> +<entry +></entry> +<entry +>amav-istis</entry> +<entry +>monu-istis</entry> +<entry +>rex-istis</entry> +<entry +>audiv-istis</entry> +<entry +>fu-istis</entry> +</row> +<row> +<entry +></entry> +<entry +>amav-erunt</entry> +<entry +>monu-erunt</entry> +<entry +>rex-erunt</entry> +<entry +>audiv-erunt</entry> +<entry +>fu-erunt</entry> +</row> +<row> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +</row> +<row> +<!-- Please translate only the first entry of each row if there is one --> +<entry +>FUTURE PERFECT</entry> +<entry +>amav-ero</entry> +<entry +>monu-ero</entry> +<entry +>rex-ero</entry> +<entry +>audiv-ero</entry> +<entry +>fu-ero</entry> +</row> +<row> +<entry +></entry> +<entry +>amav-eris</entry> +<entry +>monu-eris</entry> +<entry +>rex-eris</entry> +<entry +>audiv-eris</entry> +<entry +>fu-eris</entry> +</row> +<row> +<entry +>I will have loved</entry> +<entry +>amav-erit</entry> +<entry +>monu-erit</entry> +<entry +>rex-erit</entry> +<entry +>audiv-erit</entry> +<entry +>fu-erit</entry> +</row> +<row> +<entry +></entry> +<entry +>amav-erimus</entry> +<entry +>monu-erimus</entry> +<entry +>rex-erimus</entry> +<entry +>audiv-erimus</entry> +<entry +>fu-erimus</entry> +</row> +<row> +<entry +></entry> +<entry +>amav-eritis</entry> +<entry +>monu-eritis</entry> +<entry +>rex-eritis</entry> +<entry +>audiv-eritis</entry> +<entry +>fu-eritis</entry> +</row> +<row> +<entry +></entry> +<entry +>amav-erint</entry> +<entry +>monu-erint</entry> +<entry +>rex-erint</entry> +<entry +>audiv-erint</entry> +<entry +>fu-erint</entry> +</row> +<row> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +</row> +<row> +<!-- Please translate only the first entry of each row if there is one --> +<entry +>PLUPERFECT</entry> +<entry +>amav-eram</entry> +<entry +>monu-eram</entry> +<entry +>rex-eram</entry> +<entry +>audiv-eram</entry> +<entry +>fu-eram</entry> +</row> +<row> +<entry +></entry> +<entry +>amav-eras</entry> +<entry +>monu-eras</entry> +<entry +>rex-eras</entry> +<entry +>audiv-eras</entry> +<entry +>fu-eras</entry> +</row> +<row> +<entry +>I had loved</entry> +<entry +>amav-erat</entry> +<entry +>monu-erat</entry> +<entry +>rex-erat</entry> +<entry +>audiv-erat</entry> +<entry +>fu-erat</entry> +</row> +<row> +<entry +></entry> +<entry +>amav-eramus</entry> +<entry +>monu-eramus</entry> +<entry +>rex-eramus</entry> +<entry +>audiv-eramus</entry> +<entry +>fu-eramus</entry> +</row> +<row> +<entry +></entry> +<entry +>amav-eratis</entry> +<entry +>monu-eratis</entry> +<entry +>rex-eratis</entry> +<entry +>audiv-eratis</entry> +<entry +>fu-eratis</entry> +</row> +<row> +<entry +></entry> +<entry +>amav-erant</entry> +<entry +>monu-erant</entry> +<entry +>rex-erant</entry> +<entry +>audiv-erant</entry> +<entry +>fu-erant</entry> +</row> +</tbody> +</tgroup> +</table> + + +<table frame="none"> +<!-- Please translate the title--> +<title +>Verb listings - Subjunctive Active</title> +<tgroup cols="6" colsep="1" rowsep="1"> +<colspec colname="c1"/> +<tbody> +<row> +<!-- Please translate --> +<entry +>TENSE</entry> +<entry +>1st</entry> +<entry +>2nd</entry> +<entry +>3rd</entry> +<entry +>4th</entry> +<entry +>SUM - I</entry> +</row> +<row> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +</row> +<row> +<!-- translate only the first entry of each row if there is one --> +<entry +>PRESENT</entry> +<entry +>ame-m</entry> +<entry +>monea-m</entry> +<entry +>rega-m</entry> +<entry +>audi-o</entry> +<entry +>sim</entry> +</row> +<row> +<entry +></entry> +<entry +>ame-s</entry> +<entry +>monea-s</entry> +<entry +>rega-s</entry> +<entry +>audi-s</entry> +<entry +>sis</entry> +</row> +<row> +<entry +></entry> +<entry +>ame-t</entry> +<entry +>monea-t</entry> +<entry +>rega-t</entry> +<entry +>audi-t</entry> +<entry +>sit</entry> +</row> +<row> +<entry +></entry> +<entry +>ame-mus</entry> +<entry +>monea-mus</entry> +<entry +>rega-mus</entry> +<entry +>audi-mus</entry> +<entry +>simus</entry> +</row> +<row> +<entry +></entry> +<entry +>ame-tis</entry> +<entry +>monea-tis</entry> +<entry +>rega-tis</entry> +<entry +>audi-tis</entry> +<entry +>sitis</entry> +</row> +<row> +<entry +></entry> +<entry +>ame-nt</entry> +<entry +>monea-nt</entry> +<entry +>rega-nt</entry> +<entry +>audi-unt</entry> +<entry +>sint</entry> +</row> +<row> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +</row> +<row> +<!-- Please translate only the first entry of each row if there is one --> +<entry +>IMPERFECT</entry> +<entry +>ama-rem</entry> +<entry +>mone-rem</entry> +<entry +>rege-rem</entry> +<entry +>audi-rem</entry> +<entry +>essem</entry> +</row> +<row> +<entry +></entry> +<entry +>ama-res</entry> +<entry +>mone-res</entry> +<entry +>rege-res</entry> +<entry +>audi-res</entry> +<entry +>esset</entry> +</row> +<row> +<entry +></entry> +<entry +>ama-ret</entry> +<entry +>mone-ret</entry> +<entry +>rege-ret</entry> +<entry +>audi-ret</entry> +<entry +>esset</entry> +</row> +<row> +<entry +></entry> +<entry +>ama-remus</entry> +<entry +>mone-remus</entry> +<entry +>rege-remus</entry> +<entry +>audi-remus</entry> +<entry +>essemus</entry> +</row> +<row> +<entry +></entry> +<entry +>ama-retis</entry> +<entry +>mone-retis</entry> +<entry +>rege-retis</entry> +<entry +>audi-retis</entry> +<entry +>essetis</entry> +</row> +<row> +<entry +></entry> +<entry +>ama-rent</entry> +<entry +>mone-rent</entry> +<entry +>rege-rent</entry> +<entry +>audi-rent</entry> +<entry +>essent</entry> +</row> +<row> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +</row> +<row> +<!-- Please translate only the first entry of each row if there is one --> +<entry +>PERFECT</entry> +<entry +>amav-erim</entry> +<entry +>monu-erim</entry> +<entry +>rex-erim</entry> +<entry +>audiv-erim</entry> +<entry +>fu-erim</entry> +</row> +<row> +<entry +></entry> +<entry +>amav-eris</entry> +<entry +>monu-eris</entry> +<entry +>rex-eris</entry> +<entry +>audiv-eris</entry> +<entry +>fu-eris</entry> +</row> +<row> +<entry +></entry> +<entry +>amav-erit</entry> +<entry +>monu-erit</entry> +<entry +>rex-erit</entry> +<entry +>audiv-erit</entry> +<entry +>fu-erit</entry> +</row> +<row> +<entry +></entry> +<entry +>amav-erimus</entry> +<entry +>monu-erimus</entry> +<entry +>rex-erimus</entry> +<entry +>audiv-erimus</entry> +<entry +>fu-erimus</entry> +</row> +<row> +<entry +></entry> +<entry +>amav-eritis</entry> +<entry +>monu-eritis</entry> +<entry +>rex-eritis</entry> +<entry +>audiv-eritis</entry> +<entry +>fu-eritis</entry> +</row> +<row> +<entry +></entry> +<entry +>amav-erint</entry> +<entry +>monu-erint</entry> +<entry +>rex-erint</entry> +<entry +>audiv-erint</entry> +<entry +>fu-erint</entry> +</row> +<row> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +</row> +<row> +<!-- Please translate only the first entry of each row if there is one --> +<entry +>PLUPERFECT</entry> +<entry +>amav-issem</entry> +<entry +>monu-issem</entry> +<entry +>rex-issem</entry> +<entry +>audiv-issem</entry> +<entry +>fu-issem</entry> +</row> +<row> +<entry +></entry> +<entry +>amav-isses</entry> +<entry +>monu-isses</entry> +<entry +>rex-isses</entry> +<entry +>audiv-isses</entry> +<entry +>fu-isses</entry> +</row> +<row> +<entry +></entry> +<entry +>amav-isset</entry> +<entry +>monu-isset</entry> +<entry +>rex-isset</entry> +<entry +>audiv-isset</entry> +<entry +>fu-isset</entry> +</row> +<row> +<entry +></entry> +<entry +>amav-issemus</entry> +<entry +>monu-issemus</entry> +<entry +>rex-issemus</entry> +<entry +>audiv-issemus</entry> +<entry +>fu-issemus</entry> +</row> +<row> +<entry +></entry> +<entry +>amav-issetis</entry> +<entry +>monu-issetis</entry> +<entry +>rex-issetis</entry> +<entry +>audiv-issetis</entry> +<entry +>fu-issetis</entry> +</row> +<row> +<entry +></entry> +<entry +>amav-issent</entry> +<entry +>monu-issent</entry> +<entry +>rex-issent</entry> +<entry +>audiv-issent</entry> +<entry +>fu-issent</entry> +</row> +</tbody> +</tgroup> +</table> + +<table frame="none"> +<!-- Please translate the title--> +<title +>Verb listings - Imperative Active</title> +<tgroup cols="6" colsep="1" rowsep="1"> +<colspec colname="c1"/> +<tbody> +<row> +<!-- Please translate --> +<entry +>TENSE</entry> +<entry +>1st</entry> +<entry +>2nd</entry> +<entry +>3rd</entry> +<entry +>4th</entry> +<entry +>SUM - I</entry> +</row> +<row> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +</row> +<row> +<!-- translate only the first entry of each row if there is one --> +<entry +>PRESENT</entry> +<entry +>am-a</entry> +<entry +>mon-e</entry> +<entry +>reg-e</entry> +<entry +>aud-i</entry> +<entry +>es</entry> +</row> +<row> +<entry +></entry> +<entry +>am-ate</entry> +<entry +>mon-ete</entry> +<entry +>reg-ite</entry> +<entry +>aud-ite</entry> +<entry +>este</entry> +</row> +<row> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +</row> +<row> +<!-- Please translate only the first entry of each row if there is one --> +<entry +>FUTURE</entry> +<entry +>am-ato</entry> +<entry +>mon-eto</entry> +<entry +>reg-ito</entry> +<entry +>aud-ito</entry> +<entry +>esto</entry> +</row> +<row> +<entry +></entry> +<entry +>am-ato</entry> +<entry +>mon-eto</entry> +<entry +>reg-ito</entry> +<entry +>aud-ito</entry> +<entry +>esto</entry> +</row> +<row> +<entry +></entry> +<entry +>am-atote</entry> +<entry +>mon-etote</entry> +<entry +>reg-itote</entry> +<entry +>aud-itote</entry> +<entry +>estote</entry> +</row> +<row> +<entry +></entry> +<entry +>am-anto</entry> +<entry +>mon-ento</entry> +<entry +>reg-unto</entry> +<entry +>aud-iunto</entry> +<entry +>sunto</entry> +</row> +</tbody> +</tgroup> +</table> + +<table frame="none"> +<!-- Please translate the title--> +<title +>Verb listings - Gerund Active</title> +<tgroup cols="5" colsep="1" rowsep="1"> +<colspec colname="c1"/> +<tbody> +<row> +<entry +></entry> +<entry +>1st</entry> +<entry +>2nd</entry> +<entry +>3rd</entry> +<entry +>4th</entry> +</row> +<row> +<entry +>Accusative</entry> +<entry +>(ad) am-andum</entry> +<entry +>(ad) mon-endum</entry> +<entry +>(ad) reg-endum</entry> +<entry +>(ad) aud-iendum</entry> +</row> +<row> +<entry +>Genitive</entry> +<entry +>am-andi</entry> +<entry +>mon-endi</entry> +<entry +>reg-endi</entry> +<entry +>aud-iendi</entry> +</row> +<row> +<entry +>Dative</entry> +<entry +>am-ando</entry> +<entry +>mon-endo</entry> +<entry +>reg-endo</entry> +<entry +>aud-iendo</entry> +</row> +<row> +<entry +>Ablative</entry> +<entry +>am-ando</entry> +<entry +>mon-endo</entry> +<entry +>reg-endo</entry> +<entry +>aud-iendo</entry> +</row> +</tbody> +</tgroup> +</table> + +<table frame="none"> +<!-- Please translate the title--> +<title +>Verb listings - Infinitive Active</title> +<tgroup cols="6" colsep="1" rowsep="1"> +<colspec colname="c1"/> +<tbody> +<row> +<entry +>TENSE</entry> +<entry +>1st</entry> +<entry +>2nd</entry> +<entry +>3rd</entry> +<entry +>4th</entry> +<entry +>SUM - I</entry> +</row> +<row> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +</row> +<row> +<entry +>PRESENT</entry> +<entry +>am-are</entry> +<entry +>mon-ere</entry> +<entry +>reg-ere</entry> +<entry +>aud-ire</entry> +<entry +>esse</entry> +</row> +<row> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +</row> +<row> +<entry +>PERFECT</entry> +<entry +>amav-isse</entry> +<entry +>monu-isse</entry> +<entry +>rex-isse</entry> +<entry +>audiv-isse</entry> +<entry +>fu-isse</entry> +</row> +</tbody> +</tgroup> +</table> + +<table frame="none"> +<!-- Please translate the title--> +<title +>Verb listings - Participle Active</title> +<tgroup cols="6" colsep="1" rowsep="1"> +<colspec colname="c1"/> +<tbody> +<row> +<entry +>TENSE</entry> +<entry +>1st</entry> +<entry +>2nd</entry> +<entry +>3rd</entry> +<entry +>4th</entry> +<entry +>SUM - I</entry> +</row> +<row> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +</row> +<row> +<entry +>PRESENT</entry> +<entry +>am-ans,-antis</entry> +<entry +>mon-ens,-entis</entry> +<entry +>reg-ens,-entis</entry> +<entry +>aud-iens,-ientis</entry> +<entry +></entry> +</row> +<row> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +</row> +<row> +<entry +>FUTURE</entry> +<entry +>amat-urus,-a,-um</entry> +<entry +>monit-urus,-a,-um</entry> +<entry +>rect-urus,-a,-um</entry> +<entry +>audit-urus,-a,-um</entry> +<entry +>futurus,-a,-um</entry> +</row> +</tbody> +</tgroup> +</table> + +<table frame="none"> +<!-- Please translate the title--> +<title +>Verb listings - Indicative Passive</title> +<tgroup align="center" cols="5" colsep="1" rowsep="1"> +<colspec colname="c1"/> +<tbody> +<row> +<!-- Please translate --> +<entry +>TENSE</entry> +<entry +>1st</entry> +<entry +>2nd</entry> +<entry +>3rd</entry> +<entry +>4th</entry> +</row> +<row> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +</row> +<row> +<!-- Please translate only the first entry of each row if there is one --> +<entry +>PRESENT</entry> +<entry +>am-or</entry> +<entry +>mone-or</entry> +<entry +>reg-or</entry> +<entry +>audi-or</entry> +</row> +<row> +<entry +></entry> +<entry +>ama-ris</entry> +<entry +>mone-ris</entry> +<entry +>reg-eris</entry> +<entry +>audi-eris</entry> +</row> +<row> +<entry +>I am loved</entry> +<entry +>ama-tur</entry> +<entry +>mone-tur</entry> +<entry +>regi-tur</entry> +<entry +>audi-tur</entry> +</row> +<row> +<entry +></entry> +<entry +>ama-mur</entry> +<entry +>mone-mur</entry> +<entry +>regi-mur</entry> +<entry +>audi-mur</entry> +</row> +<row> +<entry +></entry> +<entry +>ama-mini</entry> +<entry +>mone-mini</entry> +<entry +>regi-mini</entry> +<entry +>audi-mini</entry> +</row> +<row> +<entry +></entry> +<entry +>ama-ntur</entry> +<entry +>mone-ntur</entry> +<entry +>regu-ntur</entry> +<entry +>audiu-unt</entry> +</row> +<row> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +</row> +<row> +<!-- Please translate only the first entry of each row if there is one --> +<entry +>FUTURE</entry> +<entry +>ama-bor</entry> +<entry +>mone-bor</entry> +<entry +>reg-ar</entry> +<entry +>audi-ar</entry> +</row> +<row> +<entry +></entry> +<entry +>ama-beris</entry> +<entry +>mone-beris</entry> +<entry +>reg-eris</entry> +<entry +>audi-eris</entry> +</row> +<row> +<entry +>I will be loved</entry> +<entry +>ama-bitur</entry> +<entry +>mone-bitur</entry> +<entry +>reg-etur</entry> +<entry +>audi-etur</entry> +</row> +<row> +<entry +></entry> +<entry +>ama-bimur</entry> +<entry +>mone-bimur</entry> +<entry +>reg-emur</entry> +<entry +>audi-emur</entry> +</row> +<row> +<entry +></entry> +<entry +>ama-bimini</entry> +<entry +>mone-bimini</entry> +<entry +>reg-emini</entry> +<entry +>audi-emini</entry> +</row> +<row> +<entry +></entry> +<entry +>ama-buntur</entry> +<entry +>mone-buntur</entry> +<entry +>reg-entur</entry> +<entry +>audi-entur</entry> +</row> +<row> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +</row> +<row> +<!-- Please translate only the first entry of each row if there is one --> +<entry +>IMPERFECT</entry> +<entry +>ama-bar</entry> +<entry +>mone-bar</entry> +<entry +>rege-bar</entry> +<entry +>audie-bar</entry> +</row> +<row> +<entry +></entry> +<entry +>ama-baris</entry> +<entry +>mone-baris</entry> +<entry +>rege-baris</entry> +<entry +>audie-baris</entry> +</row> +<row> +<entry +>I was loved</entry> +<entry +>ama-batur</entry> +<entry +>mone-batur</entry> +<entry +>rege-batur</entry> +<entry +>audie-batur</entry> +</row> +<row> +<entry +></entry> +<entry +>ama-bamur</entry> +<entry +>mone-bamur</entry> +<entry +>rege-bamur</entry> +<entry +>audie-bamur</entry> +</row> +<row> +<entry +></entry> +<entry +>ama-bamini</entry> +<entry +>mone-bamini</entry> +<entry +>rege-bamini</entry> +<entry +>audie-bamini</entry> +</row> +<row> +<entry +></entry> +<entry +>ama-bantur</entry> +<entry +>mone-bantur</entry> +<entry +>rege-bantur</entry> +<entry +>audie-bantur</entry> +</row> +<row> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +</row> +<row> +<!-- Please translate only the first entry of each row if there is one --> +<entry +>PERFECT</entry> +<entry +>amatus sum</entry> +<entry +>monitus sum</entry> +<entry +>rectus sum</entry> +<entry +>auditus sum</entry> +</row> +<row> +<entry +></entry> +<entry +>amatus es</entry> +<entry +>monitus es</entry> +<entry +>rectus es</entry> +<entry +>auditus es</entry> +</row> +<row> +<entry +>I have been loved</entry> +<entry +>amatus est</entry> +<entry +>monitus est</entry> +<entry +>rectus est</entry> +<entry +>auditus est</entry> +</row> +<row> +<entry +></entry> +<entry +>amati sumus</entry> +<entry +>moniti sumus</entry> +<entry +>recti sumus</entry> +<entry +>auditi sumus</entry> +</row> +<row> +<entry +></entry> +<entry +>amati estis</entry> +<entry +>moniti estis</entry> +<entry +>recti estis</entry> +<entry +>auditi estis</entry> +</row> +<row> +<entry +></entry> +<entry +>amati sunt</entry> +<entry +>moniti sunt</entry> +<entry +>recti sunt</entry> +<entry +>auditi sunt</entry> +</row> +<row> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +</row> +<row> +<!-- Please translate only the first entry of each row if there is one --> +<entry +>FUTURE PERFECT</entry> +<entry +>amatus ero</entry> +<entry +>monitus ero</entry> +<entry +>rectus ero</entry> +<entry +>auditus ero</entry> +</row> +<row> +<entry +></entry> +<entry +>amatus eris</entry> +<entry +>monitus eris</entry> +<entry +>rectus eris</entry> +<entry +>auditus eris</entry> +</row> +<row> +<entry +>I will have been loved</entry> +<entry +>amatus erit</entry> +<entry +>monitus erit</entry> +<entry +>rectus erit</entry> +<entry +>auditus erit</entry> +</row> +<row> +<entry +></entry> +<entry +>amati erimus</entry> +<entry +>moniti erimus</entry> +<entry +>recti erimus</entry> +<entry +>auditi erimus</entry> +</row> +<row> +<entry +></entry> +<entry +>amati eritis</entry> +<entry +>moniti eritis</entry> +<entry +>recti eritis</entry> +<entry +>auditi eritis</entry> +</row> +<row> +<entry +></entry> +<entry +>amati erunt</entry> +<entry +>moniti erunt</entry> +<entry +>recti erunt</entry> +<entry +>auditi erunt</entry> +</row> +<row> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +</row> +<row> +<!-- Please translate only the first entry of each row if there is one --> +<entry +>PLUPERFECT</entry> +<entry +>amatus eram</entry> +<entry +>monitus eram</entry> +<entry +>rectus eram</entry> +<entry +>auditus eram</entry> +</row> +<row> +<entry +></entry> +<entry +>amatus eras</entry> +<entry +>monitus eras</entry> +<entry +>rectus eras</entry> +<entry +>auditus eras</entry> +</row> +<row> +<entry +>I had been loved</entry> +<entry +>amatus erat</entry> +<entry +>monitus erat</entry> +<entry +>rectus erat</entry> +<entry +>auditus erat</entry> +</row> +<row> +<entry +></entry> +<entry +>amati eramus</entry> +<entry +>moniti eramus</entry> +<entry +>recti eramus</entry> +<entry +>auditi eramus</entry> +</row> +<row> +<entry +></entry> +<entry +>amati eratis</entry> +<entry +>moniti eratis</entry> +<entry +>recti eratis</entry> +<entry +>auditi eratis</entry> +</row> +<row> +<entry +></entry> +<entry +>amati erant</entry> +<entry +>moniti erant</entry> +<entry +>recti erant</entry> +<entry +>auditi erant</entry> +</row> +</tbody> +</tgroup> +</table> + +<table frame="none"> +<!-- Please translate the title--> +<title +>Verb listings - Gerundive Passive</title> +<tgroup cols="4" colsep="1" rowsep="1"> +<colspec colname="c1"/> +<tbody> +<row> +<entry +>1st</entry> +<entry +>2nd</entry> +<entry +>3rd</entry> +<entry +>4th</entry> +</row> +<row> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +</row> +<row> +<entry +>am-andus,-a,-um</entry> +<entry +>mon-endus,-a,-um</entry> +<entry +>reg-endus,-a,-um</entry> +<entry +>aud-iendus,-a,-um</entry> +</row> +</tbody> +</tgroup> +</table> + +<table frame="none"> +<!-- Please translate the title--> +<title +>Verb listings - Infinitive Passive</title> +<tgroup cols="5" colsep="1" rowsep="1"> +<colspec colname="c1"/> +<tbody> +<row> +<entry +>TENSE</entry> +<entry +>1st</entry> +<entry +>2nd</entry> +<entry +>3rd</entry> +<entry +>4th</entry> +</row> +<row> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +</row> +<row> +<entry +>PRESENT</entry> +<entry +>am-ari</entry> +<entry +>mon-eri</entry> +<entry +>reg-i</entry> +<entry +>aud-iri</entry> +</row> +<row> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +</row> +<row> +<entry +>PERFECT</entry> +<entry +>amat-um,-am,-um esse</entry> +<entry +>monit-um,-am,-um esse</entry> +<entry +>rect-um,-am,-um esse</entry> +<entry +>audit-um,-am,-um esse</entry> +</row> +<row> +<entry +></entry> +<entry +>amat-os,-as,-a esse</entry> +<entry +>monit-os,-as,-a esse</entry> +<entry +>rect-os,-as,-a esse</entry> +<entry +>audit-os,-as,-a esse</entry> +</row> +<row> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +<entry +></entry> +</row> +<row> +<entry +>FUTURE</entry> +<entry +>amat-um iri</entry> +<entry +>monit-um iri</entry> +<entry +>rect-um iri</entry> +<entry +>audit-um iri</entry> +</row> +</tbody> +</tgroup> +</table> + +</sect1> diff --git a/tde-i18n-en_GB/docs/kdeedu/kmplot/Makefile.am b/tde-i18n-en_GB/docs/kdeedu/kmplot/Makefile.am new file mode 100644 index 00000000000..f781297a70f --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kmplot/Makefile.am @@ -0,0 +1,4 @@ +KDE_LANG = en_GB +SUBDIRS = $(AUTODIRS) +KDE_DOCS = AUTO +KDE_MANS = AUTO diff --git a/tde-i18n-en_GB/docs/kdeedu/kmplot/Makefile.in b/tde-i18n-en_GB/docs/kdeedu/kmplot/Makefile.in new file mode 100644 index 00000000000..eba6524caa1 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kmplot/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/kdeedu/kmplot +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 = AUTO +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/kdeedu/kmplot/Makefile'; \ +#>- cd $(top_srcdir) && \ +#>- $(AUTOMAKE) --gnu docs/kdeedu/kmplot/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/kdeedu/kmplot/Makefile'; \ + cd $(top_srcdir) && \ + $(AUTOMAKE) --gnu docs/kdeedu/kmplot/Makefile + cd $(top_srcdir) && perl ../scripts/admin/am_edit -p../scripts/admin docs/kdeedu/kmplot/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=firststeps.docbook developer.docbook index.docbook using.docbook install.docbook Makefile.in configuration.docbook credits.docbook menu.docbook introduction.docbook commands.docbook Makefile.am reference.docbook index.cache.bz2 + +#>+ 24 +index.cache.bz2: $(srcdir)/index.docbook $(KDE_XSL_STYLESHEET) commands.docbook configuration.docbook reference.docbook index.docbook using.docbook menu.docbook firststeps.docbook introduction.docbook credits.docbook developer.docbook install.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)/kmplot + @if test -f index.cache.bz2; then \ + echo $(INSTALL_DATA) index.cache.bz2 $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kmplot/; \ + $(INSTALL_DATA) index.cache.bz2 $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kmplot/; \ + elif test -f $(srcdir)/index.cache.bz2; then \ + echo $(INSTALL_DATA) $(srcdir)/index.cache.bz2 $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kmplot/; \ + $(INSTALL_DATA) $(srcdir)/index.cache.bz2 $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kmplot/; \ + fi + -rm -f $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kmplot/common + $(LN_S) $(kde_libs_htmldir)/$(KDE_LANG)/common $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kmplot/common + +uninstall-docs: + -rm -rf $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kmplot + +clean-docs: + -rm -f index.cache.bz2 + + +#>+ 13 +install-nls: + $(mkinstalldirs) $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kmplot + @for base in commands.docbook configuration.docbook reference.docbook index.docbook using.docbook menu.docbook firststeps.docbook introduction.docbook credits.docbook developer.docbook install.docbook ; do \ + echo $(INSTALL_DATA) $$base $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kmplot/$$base ;\ + $(INSTALL_DATA) $(srcdir)/$$base $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kmplot/$$base ;\ + done + +uninstall-nls: + for base in commands.docbook configuration.docbook reference.docbook index.docbook using.docbook menu.docbook firststeps.docbook introduction.docbook credits.docbook developer.docbook install.docbook ; do \ + rm -f $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kmplot/$$base ;\ + done + + +#>+ 5 +distdir-nls: + for file in commands.docbook configuration.docbook reference.docbook index.docbook using.docbook menu.docbook firststeps.docbook introduction.docbook credits.docbook developer.docbook install.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/kdeedu/kmplot/Makefile'; \ + cd $(top_srcdir) && \ + $(AUTOMAKE) --gnu docs/kdeedu/kmplot/Makefile + cd $(top_srcdir) && perl ../scripts/admin/am_edit -p../scripts/admin docs/kdeedu/kmplot/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/kdeedu/kmplot/commands.docbook b/tde-i18n-en_GB/docs/kdeedu/kmplot/commands.docbook new file mode 100644 index 00000000000..ff3cfda6893 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kmplot/commands.docbook @@ -0,0 +1,622 @@ +<chapter id="commands"> +<title +>Command Reference</title +> + +<sect1 id="a-file-menu"> +<title +>The <guimenu +>File</guimenu +> Menu</title> + +<variablelist> + +<varlistentry> +<term> +<menuchoice +><shortcut +> <keycombo action="simul" +>&Ctrl;<keycap +>N</keycap +></keycombo +> </shortcut +> <guimenu +>File</guimenu +> <guimenuitem +>New</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +><action +>Starts a new Plot by clearing the coordinate system and resetting the function parser.</action +></para +> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><shortcut +> <keycombo action="simul" +>&Ctrl;<keycap +>O</keycap +></keycombo +></shortcut +> <guimenu +>File</guimenu +> <guimenuitem +>Open...</guimenuitem +></menuchoice +></term> +<listitem +><para +><action +>Opens an existing document.</action> +</para +></listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><shortcut +><keycombo action="simul" +>&Ctrl;<keycap +>S</keycap +></keycombo +></shortcut +> <guimenu +>File</guimenu +> <guimenuitem +>Save</guimenuitem +></menuchoice +></term> +<listitem +><para +><action +>Saves the document.</action +></para +></listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><guimenu +>File</guimenu +> <guimenuitem +>Save As...</guimenuitem +></menuchoice +></term> +<listitem +><para +><action +>Saves the document under another name.</action +></para +></listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><shortcut +> <keycombo action="simul" +>&Ctrl;<keycap +>P</keycap +></keycombo +> </shortcut +> <guimenu +>File</guimenu +> <guimenuitem +>Print...</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +><action +>Sends the plot to a printer or file.</action +></para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><shortcut +><keycombo action="simul" +> &Ctrl;<keycap +>Q</keycap +> </keycombo +></shortcut +> <guimenu +>File</guimenu +> <guimenuitem +>Quit</guimenuitem +></menuchoice +></term> +<listitem +><para +><action +>Exits</action +> &kmplot;.</para +></listitem> +</varlistentry> +</variablelist> +</sect1> + +<sect1 id="a-view-menu"> +<title +>The <guimenu +>Edit</guimenu +> Menu</title> + +<variablelist> +<varlistentry> +<term +><menuchoice +><guimenu +>Edit</guimenu +><guimenuitem +>Colours...</guimenuitem +> </menuchoice +></term> +<listitem +><para +>Displays the <guilabel +>Colour Settings</guilabel +> dialogue box. See <xref linkend="configuration"/>. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term +><menuchoice +><guimenu +>Edit</guimenu +><guimenuitem +>Coordinate System...</guimenuitem +> </menuchoice +></term> +<listitem +><para +>Displays the <guilabel +>Coordinate System</guilabel +> dialogue box. See <xref linkend="configuration"/>. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term +><menuchoice +><guimenu +>Edit</guimenu +><guimenuitem +>Scaling...</guimenuitem +> </menuchoice +></term> +<listitem +><para +>Displays the <guilabel +>Scaling Settings</guilabel +> dialogue box. See <xref linkend="configuration"/>. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term +><menuchoice +><guimenu +>Edit</guimenu +><guimenuitem +>Fonts...</guimenuitem +> </menuchoice +></term> +<listitem +><para +>Displays the <guilabel +>Font Settings</guilabel +> dialogue box. See <xref linkend="configuration"/>. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term +><menuchoice +><guimenu +>Edit</guimenu +><guimenuitem +>Coordinate System I</guimenuitem +> </menuchoice +></term> +<listitem +><para +>Show both positive and negative x- and y-values on the grid. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term +><menuchoice +><guimenu +>Edit</guimenu +><guimenuitem +>Coordinate System II</guimenuitem +> </menuchoice +></term> +<listitem +><para +>Show positive and negative y-values, but positive x-values only </para> +</listitem> +</varlistentry> + +<varlistentry> +<term +><menuchoice +><guimenu +>Edit</guimenu +><guimenuitem +>Coordinate System III</guimenuitem +> </menuchoice +></term> +<listitem +><para +>Show only positive x- and y-values. </para> +</listitem> +</varlistentry> +</variablelist> +</sect1> + +<sect1 id="a-functions-menu"> +<title +>The <guimenu +>Plot</guimenu +> Menu</title> + +<variablelist> +<varlistentry> +<term> +<menuchoice +><guimenu +>Functions</guimenu +> <guimenuitem +>New Function Plot...</guimenuitem +> </menuchoice> +</term> +<listitem +><para +>Opens the dialogue for creating a new function plot. See <xref linkend="using-kmplot"/>.</para +></listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><guimenu +>Functions</guimenu +> <guimenuitem +>New Parametric Plot...</guimenuitem +> </menuchoice> +</term> +<listitem +><para +>Opens the dialogue for creating a new parametric plot. See <xref linkend="using-kmplot"/>.</para +></listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><guimenu +>Functions</guimenu +> <guimenuitem +>New Polar Plot...</guimenuitem +> </menuchoice> +</term> +<listitem +><para +>Opens the dialogue for creating a new polar plot. See <xref linkend="using-kmplot"/>.</para +></listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><guimenu +>Functions</guimenu +> <guimenuitem +>Edit Plots...</guimenuitem +> </menuchoice> +</term> +<listitem +><para +>Displays the functions dialogue. There you can add, edit and remove functions. See <xref linkend="using-kmplot"/>.</para +></listitem> +</varlistentry> + +</variablelist> + +</sect1> + +<sect1 id="a-zoom-menu"> +<title +>The <guimenu +>Zoom</guimenu +> Menu</title> +<para +>The first five items in the menu change zoom-mode.</para> +<variablelist> +<varlistentry> +<term> +<menuchoice +><guimenu +>Zoom</guimenu +> <guimenuitem +>No Zoom</guimenuitem +> </menuchoice> +</term> +<listitem +><para +>Disable the zoom-mode.</para +></listitem> +</varlistentry> +</variablelist> + + +<variablelist> +<varlistentry> +<term> +<menuchoice +><guimenu +>Zoom</guimenu +> <guimenuitem +>Zoom rectangular</guimenuitem +> </menuchoice> +</term> +<listitem +><para +>Let the user draw a rectangle. The minimum and maximum values will be set to the coordinates of the rectangle.</para +></listitem> +</varlistentry> +</variablelist> + +<variablelist> +<varlistentry> +<term> +<menuchoice +><guimenu +>Zoom</guimenu +> <guimenuitem +>Zoom in</guimenuitem +> </menuchoice> +</term> +<listitem +><para +>The minimum and maximum values will come closer to each other and the selected point in the graph will be centred.</para +></listitem> +</varlistentry> +</variablelist> + +<variablelist> +<varlistentry> +<term> +<menuchoice +><guimenu +>Zoom</guimenu +> <guimenuitem +>Zoom out</guimenuitem +> </menuchoice> +</term> +<listitem +><para +>The minimum and maximum values will be more separated from each other and the selected point in the graph will be centred.</para +></listitem> +</varlistentry> +</variablelist> + +<variablelist> +<varlistentry> +<term> +<menuchoice +><guimenu +>Zoom</guimenu +> <guimenuitem +>Centre a point</guimenuitem +> </menuchoice> +</term> +<listitem +><para +>The selected point in the graph will be centred.</para +></listitem> +</varlistentry> +</variablelist> + +<variablelist> +<varlistentry> +<term> +<menuchoice +><guimenu +>Zoom</guimenu +> <guimenuitem +>Fit widget to trigonometric functions</guimenuitem +> </menuchoice> +</term> +<listitem +><para +>The scale will be adapted to trigonometric functions. This works both for radians and degrees.</para +></listitem> +</varlistentry> +</variablelist> + +</sect1> + + +<sect1 id="a-settings-menu"> +<title +>The <guimenu +>Settings</guimenu +> Menu</title> + +<variablelist> +<varlistentry> +<term +><menuchoice +><guimenu +>Settings</guimenu +> <guimenuitem +>Show Toolbar</guimenuitem +> </menuchoice +></term> +<listitem> +<para +><action +>Toggle on and off the display of the toolbar.</action +> The default is on.</para> +</listitem> +</varlistentry> + +<varlistentry> +<term +><menuchoice +><guimenu +>Settings</guimenu +> <guimenuitem +>Show Statusbar</guimenuitem +> </menuchoice +></term> +<listitem> +<para +><action +>Toggle on and off the display of the statusbar at the bottom of the &kmplot; main window.</action +> The default is on.</para> +</listitem> +</varlistentry> + +<varlistentry> +<term +><menuchoice +><guimenu +>Settings</guimenu +> <guimenuitem +>Configure Shortcuts...</guimenuitem +> </menuchoice +></term> +<listitem> +<para +><action +>Personalise the keybindings</action +> for &kmplot;.</para> +</listitem> +</varlistentry> + +<varlistentry> +<term +><menuchoice +><guimenu +>Settings</guimenu +> <guimenuitem +>Configure Toolbars...</guimenuitem +> </menuchoice +></term> +<listitem> +<para +><action +>Personalise the toolbars</action +> for &kmplot;.</para> +</listitem> +</varlistentry> + +<varlistentry> +<term +><menuchoice +><guimenu +>Settings</guimenu +> <guimenuitem +>Configure &kmplot;</guimenuitem +> </menuchoice +></term> +<listitem> +<para +><action +>Customise</action +> &kmplot;. The options available to you are described in <xref linkend="configuration"/>.</para> +</listitem> +</varlistentry> +</variablelist> + +</sect1> + +<sect1 id="a-tools-menu"> +<title +>The <guimenu +>Tools</guimenu +> Menu</title> + +<para +>This menu constains some tools for the functions that can be useful:</para> + +<variablelist> +<varlistentry> +<term +><menuchoice +><guimenu +>Tools</guimenu +> <guimenuitem +>Get y-value</guimenuitem +> </menuchoice +></term> +<listitem> +<para +>Let the user get the y-value from a specific x-value. At the moment, only plot functions are supported. Type a value or expression in the textbox under "X:". In the list below all the available functions are shown. Press the "Calculate" button to find the function's y-value. The result will be shown in the y-value box.</para> +</listitem> +</varlistentry> +</variablelist> +</sect1> + +<sect1 id="a-help-menu"> +<title +>The <guimenu +>Help</guimenu +> Menu</title> + +<para +>&kmplot; has a standard &kde; <guimenu +>Help</guimenu +> as described below, with one addition:</para> + +<variablelist> +<varlistentry> +<term +><menuchoice +><guimenu +>Help</guimenu +> <guimenuitem +>Names...</guimenuitem +> </menuchoice +></term> +<listitem> +<para +>Opens a window with a list of the predefined function names and constants that &kmplot; knows.</para> +</listitem> +</varlistentry> +</variablelist> + +<para +>The standard &kde; <guimenu +>Help</guimenu +> entries are:</para> +&help.menu.documentation; </sect1> + + +</chapter> +<!-- +Local Variables: +mode: sgml +sgml-minimize-attributes:nil +sgml-general-insert-case:lower +sgml-indent-step:0 +sgml-indent-data:nil +sgml-parent-document:("index.docbook" "BOOK" "CHAPTER") +End: +--> diff --git a/tde-i18n-en_GB/docs/kdeedu/kmplot/configuration.docbook b/tde-i18n-en_GB/docs/kdeedu/kmplot/configuration.docbook new file mode 100644 index 00000000000..89ed12f53c0 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kmplot/configuration.docbook @@ -0,0 +1,277 @@ +<chapter id="configuration"> +<title +>Configuring &kmplot;</title +> +<para +>To access the &kmplot; configuration dialogue, select <menuchoice +><guimenu +>Settings</guimenu +><guimenuitem +>Configure KmPlot...</guimenuitem +></menuchoice +>. A number of settings can also be changed from options in the <guimenu +>Edit</guimenu +> menu, as well. </para> + +<note> +<para +>Settings changed in the &kmplot; configuration dialogue become the default for &kmplot;, and only take effect when a new plot is started. Settings changed in the <guimenu +>View</guimenu +> menu take effect immediately, but do not persist after &kmplot; is exited.</para> +</note> + +<sect1 id="general-config"> +<title +><guilabel +>General</guilabel +> Configuration</title> +<para +>Here you can set global settings which automatic will be saved when you exit &kmplot;. In the first tab you can set calculation-precision, angle-mode (radians and degrees), background colour and zoom in and zoom out factors. </para +><para +>The second tab let you define you own constants. &kmplot; saves the constains in the same file as KCalc does. That means you can create a constant in &kmplot;, close the program and load it in KCalc and vice versa. &kmplot; only supports constant names that consist one capital character and if you in KCalc define a constant name that is not one character, the name will be truncated. E.g, if you already have the constants "apple" and "bananas" in KCalc, they will be renamed to "A" and "B" in &kmplot;.</para> + +<screenshot> +<screeninfo +>Here is a screenshot of the &kmplot; welcome window</screeninfo> + <mediaobject> + <imageobject> + <imagedata fileref="settingsdlg.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>Screenshot</phrase> + </textobject> + </mediaobject> +</screenshot> + +</sect1> + + +<sect1 id="colors-config"> +<title +><guilabel +>Colours</guilabel +> Configuration</title> +<para +>In the <guilabel +>Coords</guilabel +> tab of the <guilabel +>Colours</guilabel +> configuration option, you can change the colours of the axes and grid of the main &kmplot; area.</para> +<para +>In the <guilabel +>Functions</guilabel +> tab, you can change the colours used for the graphs of the ten functions allowed in &kmplot;.</para> +</sect1> + +<sect1 id="coords-config"> +<title +><guilabel +>Coords</guilabel +> Configuration</title> + +<sect2 id="axes-config"> +<title +>The <guilabel +>Axes</guilabel +> Configuration</title> +<para> +<variablelist> + +<varlistentry> +<term +><guilabel +>X-Axis</guilabel +></term> +<listitem> +<para +>Sets the range for the x-axis scale. You can choose one of the predefined ranges, or select <guilabel +>Custom</guilabel +> to make your own. Note that in the <guilabel +>Custom</guilabel +> boxes, you can use the predefined functions and constants (see <xref linkend="func-predefined"/>) as the extremes of the range (⪚, set <guilabel +>min:</guilabel +> to <userinput +>2*pi</userinput +>). You can even use functions you have defined to set the extremes of the axis range. For example, if you have defined a function <userinput +>f(x)=x^2</userinput +>, you could set <guilabel +>min:</guilabel +> to <userinput +>f(3)</userinput +>, which would make the lower end of the range equal to 9.</para> +</listitem> +</varlistentry> + +<varlistentry> +<term +><guilabel +>Y-Axis</guilabel +></term> +<listitem> +<para +>Sets the range for the y-axis. See <quote +>X-Axis</quote +> above.</para> +</listitem> +</varlistentry> + +<varlistentry> +<term +><guilabel +>Axes line width</guilabel +></term> +<listitem> +<para +>Sets the width of the lines representing the axes.</para> +</listitem> +</varlistentry> + +<varlistentry> +<term +><guilabel +>Tic width</guilabel +></term> +<listitem> +<para +>Sets the width of the lines representing tics on the axes.</para> +</listitem> +</varlistentry> + +<varlistentry> +<term +><guilabel +>Tic length</guilabel +></term> +<listitem> +<para +>Sets the length of the lines representing tics on the axes.</para> +</listitem> +</varlistentry> + +<varlistentry> +<term +><guilabel +>Labels</guilabel +></term> +<listitem> +<para +>If checked, the names (x, y) of the axes are shown on the plot.</para> +</listitem> +</varlistentry> + +</variablelist> +</para> + +</sect2> + +<sect2 id="grid-config"> +<title +>The <guilabel +>Grid</guilabel +> Configuration</title> +<para +>You can set the <guilabel +>Grid Style</guilabel +> to one of four options: <variablelist> + +<varlistentry> +<term +><guilabel +>No Grid</guilabel +></term> +<listitem> +<para +>No gridlines are drawn on the plot area</para> +</listitem> +</varlistentry> + +<varlistentry> +<term +><guilabel +>Lines</guilabel +></term> +<listitem> +<para +>Straight lines form a grid of squares on the plot area.</para> +</listitem> +</varlistentry> + +<varlistentry> +<term +><guilabel +>Crosses</guilabel +></term> +<listitem> +<para +>Crosses are drawn to indicate points where x and y have integer values (⪚, (1,1), (4,2) &etc;).</para> +</listitem> +</varlistentry> + +<varlistentry> +<term +><guilabel +>Polar Grid</guilabel +></term> +<listitem> +<para +>Lines of constant radius and of constant angle are drawn on the plot area.</para> +</listitem> +</varlistentry> +</variablelist> +</para> +<para +>The <guilabel +>Line width</guilabel +> option is used to set the width of the lines of the grid.</para> +</sect2> + +<sect2 id="font-config"> +<title +>The <guilabel +>Fonts</guilabel +> Configuration</title> +<para +><guilabel +>Header table</guilabel +> sets the font for the information table shown in &kmplot; printouts, and <guilabel +>Axes labels</guilabel +> sets the font used for all labels on the axes in the plot area.</para> +</sect2> + +</sect1> + +<sect1 id="scaling-config"> +<title +><guilabel +>Scaling</guilabel +> Configuration</title> + +<para +>For each axis, you can set the <guilabel +>Scaling</guilabel +> and <guilabel +>Printing</guilabel +> of one tic. The <guilabel +>Scaling</guilabel +> option selects how many units apart the axis tics will be (and therefore, how far apart grid lines will be drawn), and the <guilabel +>Printing</guilabel +> option selects the length of one tic when displayed on the screen or printed. In this way, these options can be used to change the size of the graph on screen or on a page: For example, doubling the <guilabel +>Printing</guilabel +> setting whilst keeping the <guilabel +>Scaling</guilabel +> setting the same will result in the graph doubling in in height or width.</para> +</sect1> + +</chapter> + +<!-- +Local Variables: +mode: sgml +sgml-minimize-attributes:nil +sgml-general-insert-case:lower +sgml-indent-step:0 +sgml-indent-data:nil +sgml-parent-document:("index.docbook" "BOOK" "CHAPTER") +End: +--> diff --git a/tde-i18n-en_GB/docs/kdeedu/kmplot/credits.docbook b/tde-i18n-en_GB/docs/kdeedu/kmplot/credits.docbook new file mode 100644 index 00000000000..4bfbcd13e51 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kmplot/credits.docbook @@ -0,0 +1,66 @@ +<chapter id="credits"> +<title +>Credits and Licence</title> + +<para +>&kmplot; </para> + +<para +>Program copyright 2000-2002 Klaus-Dieter Möller <email +>kd.moeller@t-online.de</email +> </para> + +<itemizedlist> +<title +>Contributors</title> + <listitem> + <para +><acronym +>CVS</acronym +>: Robert Gogolok <email +>mail@robert-gogoloh.de</email +></para> + </listitem> + <listitem> + <para +>Porting &GUI; to &kde; 3 and Translating: Matthias Messmer <email +>bmlmessmer@web.de</email +></para> + </listitem> + <listitem> + <para +>Various improvements: Fredrik Edemar <email +>f_edemar@linux.se</email +></para> + </listitem +> +</itemizedlist> + +<para +>Documentation copyright 2000--2002 by Klaus-Dieter Möller <email +>kd.moeller@t-online.de</email +>. </para> +<para +>Documentation extended and updated for &kde; 3.2 by &Philip.Rodrigues; &Philip.Rodrigues.mail;.</para> +<para +>Documentation extended and updated for &kde; 3.3 by &Philip.Rodrigues; &Philip.Rodrigues.mail; and Fredrik Edemar <email +>f_edemar@linux.se</email +>.</para> +<para +>Andrew Coles<email +>andrew_coles@yahoo.co.uk</email +></para +> +&underFDL; &underGPL; </chapter> + +<!-- +Local Variables: +mode: sgml +sgml-minimize-attributes:nil +sgml-general-insert-case:lower +sgml-indent-step:0 +sgml-indent-data:nil +sgml-parent-document:("index.docbook" "BOOK" "CHAPTER") +End: +--> + diff --git a/tde-i18n-en_GB/docs/kdeedu/kmplot/developer.docbook b/tde-i18n-en_GB/docs/kdeedu/kmplot/developer.docbook new file mode 100644 index 00000000000..926abaf07b7 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kmplot/developer.docbook @@ -0,0 +1,24 @@ +<chapter id="developers"> +<title +>Developer's Guide to &kmplot;</title> + +<para +>If you want to contribute to &kmplot; feel free to send a mail to <email +>kd.moeller@t-online.de</email +> or <email +>f_edemar@linux.se</email +> </para> + +</chapter> + +<!-- +Local Variables: +mode: sgml +sgml-minimize-attributes:nil +sgml-general-insert-case:lower +sgml-indent-step:0 +sgml-indent-data:nil +sgml-parent-document:("index.docbook" "BOOK" "CHAPTER") +End: +--> + diff --git a/tde-i18n-en_GB/docs/kdeedu/kmplot/firststeps.docbook b/tde-i18n-en_GB/docs/kdeedu/kmplot/firststeps.docbook new file mode 100644 index 00000000000..2bd4bc1b9cb --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kmplot/firststeps.docbook @@ -0,0 +1,81 @@ +<chapter id="first-steps"> +<title +>First Steps With &kmplot;</title> + +<sect1 id="simple-function-plot"> +<title +>Simple Function Plot</title> + +<para +>In the main toolbar there is a simple text box in which you can enter a function expression. Simply enter: <screen +><userinput +>x^2</userinput +></screen +> and press &Enter;. This will draw the plot of y=x^2 in the coordinate system. Enter another expression in the text box like <screen +><userinput +>5*sin(x)</userinput +></screen +> and another plot will be added. </para> + +<para +>Click on one of the lines you have just plotted. Now the cross hair gets the colour of the plot and is attached to the plot. You can use the mouse to move the cross hair along the plot. In the status bar at the bottom of the window the coordinates of the current position is displayed. Note that if the plot touches the x-axis the root will be displayed in the status bar, too.</para> + +<para +>Click the mouse again and the cross hair will be detached from the plot.</para> +</sect1> + +<sect1 id="edit-properties"> +<title +>Edit Properties</title> + +<para +>Let us make some changes to the function and change the colour of the plot.</para> + +<para +>You can edit all functions with the <menuchoice +><guimenu +>Plot</guimenu +><guimenuitem +>Edit Plots...</guimenuitem +> </menuchoice +> menu entry. A dialogue appears which lists all the functions that you have plotted. Notice that &kmplot; has automatically found a unique function name for your expressions and completed the expression to a function equation.</para> + +<para +>Select <guilabel +>f(x)=x^2</guilabel +> in the list. A double click or pressing the <guibutton +>Edit</guibutton +> button will show you a dialogue window. Here you have access to a lot of options. Let us rename the function and move the plot 5 units down. Change the function equation to <screen +><userinput +>parabola(x)=x^2-5</userinput +></screen> +</para> + +<para +>Select another colour for the plot using the <guibutton +>Color</guibutton +> button. Finally press <guibutton +>OK</guibutton +> and your changes take effect in the coordinate system.</para> + +<note +><para +>All changes can be undone until you press <guibutton +>OK</guibutton +> in the <guilabel +>Edit Plots</guilabel +> dialogue.</para> +</note> + +</sect1> +</chapter> +<!-- +Local Variables: +mode: sgml +sgml-minimize-attributes:nil +sgml-general-insert-case:lower +sgml-indent-step:0 +sgml-indent-data:nil +sgml-parent-document:("index.docbook" "BOOK" "CHAPTER") +End: +--> diff --git a/tde-i18n-en_GB/docs/kdeedu/kmplot/index.cache.bz2 b/tde-i18n-en_GB/docs/kdeedu/kmplot/index.cache.bz2 Binary files differnew file mode 100644 index 00000000000..e75d2912587 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kmplot/index.cache.bz2 diff --git a/tde-i18n-en_GB/docs/kdeedu/kmplot/index.docbook b/tde-i18n-en_GB/docs/kdeedu/kmplot/index.docbook new file mode 100644 index 00000000000..de3770c7a7e --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kmplot/index.docbook @@ -0,0 +1,158 @@ +<?xml version="1.0" ?> +<!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" +"dtd/kdex.dtd" [ + <!ENTITY kappname "&kmplot;" +><!-- replace kmplot here --> + <!ENTITY package "kdeedu"> + <!ENTITY introduction SYSTEM "introduction.docbook"> + <!ENTITY firststeps SYSTEM "firststeps.docbook"> + <!ENTITY using SYSTEM "using.docbook"> + <!ENTITY commands SYSTEM "commands.docbook"> + <!ENTITY menu SYSTEM "menu.docbook"> + <!ENTITY developer SYSTEM "developer.docbook"> + <!ENTITY credits SYSTEM "credits.docbook"> + <!ENTITY install SYSTEM "install.docbook"> + <!ENTITY reference SYSTEM "reference.docbook"> + <!ENTITY configuration SYSTEM "configuration.docbook"> + <!ENTITY % addindex "IGNORE"> + <!ENTITY % British-English "INCLUDE" +><!-- change language only here --> +]> +<!-- The language must NOT be changed here. --> + +<book lang="&language;"> + +<bookinfo> +<title +>The &kmplot; Handbook</title> +<authorgroup> +<author +><firstname +>Klaus-Dieter</firstname +> <othername +></othername +> <surname +>Möller</surname +> <affiliation +> <address +><email +>kd.moeller@t-online.de</email +></address> +</affiliation> +</author> +<author +>&Philip.Rodrigues; &Philip.Rodrigues.mail; </author> +</authorgroup> + +<othercredit role="translator" +><firstname +>Andrew</firstname +><surname +>Coles</surname +><affiliation +><address +><email +>andrew_coles@yahoo.co.uk</email +></address +></affiliation +><contrib +>Conversion to British English</contrib +></othercredit +> + +<copyright> +<year +>2000</year +><year +>2001</year +><year +>2002</year> +<holder +>Klaus-Dieter Möller</holder> +</copyright> + +<copyright> +<year +>2003</year> +<holder +>&Philip.Rodrigues; &Philip.Rodrigues.mail;</holder> +</copyright> + +<legalnotice +>&FDLNotice;</legalnotice> + +<date +>2003-09-25</date> +<releaseinfo +>1.0</releaseinfo> + +<!-- Abstract about this handbook --> + +<abstract> +<para +>&kmplot; is a mathematical function plotter for the &kde; Desktop.</para> +<para +> <inlinemediaobject +><imageobject +><imagedata +fileref="edu-logo.png" +format="PNG"/></imageobject +></inlinemediaobject +> &kmplot; is part of the KDE-EDU Project: <ulink url="http://edu.kde.org/" +>http://edu.kde.org/</ulink +></para +></abstract> + + +<keywordset> +<keyword +>KDE</keyword> +<keyword +>KMPlot</keyword> +<keyword +>EDU</keyword> +<keyword +>edutainment</keyword> +<keyword +>plotting</keyword> +<keyword +>math</keyword> +</keywordset> + +</bookinfo> + +&introduction; +&firststeps; +&using; +&configuration; +&reference; +&commands; +&developer; +&credits; +&install; + +&documentation.index; +</book> +<!-- +Local Variables: +mode: sgml +sgml-minimize-attributes:nil +sgml-general-insert-case:lower +sgml-indent-step:0 +sgml-indent-data:nil +End: +--> + + + + + + + + + + + + + + diff --git a/tde-i18n-en_GB/docs/kdeedu/kmplot/install.docbook b/tde-i18n-en_GB/docs/kdeedu/kmplot/install.docbook new file mode 100644 index 00000000000..63119be75fe --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kmplot/install.docbook @@ -0,0 +1,38 @@ +<appendix id="installation"> +<title +>Installation</title> + +&install.intro.documentation; + +<mediaobject> +<imageobject +> +<imagedata fileref="edu-logo.png" format="PNG"/> +</imageobject> +</mediaobject> + +<para +>&kmplot; is part of the &kde; EDU Project: <ulink url="http://edu.kde.org/" +>http://edu.kde.org/</ulink +></para> + +<para +>&kmplot; has its own homepage on <ulink url="http://kmplot.sourceforge.net" +>SourceForge</ulink +>. You can also find archives of older versions of &kmplot; there, for example, for &kde; 2.x</para> + +&install.compile.documentation; + +</appendix> +<!-- +Local Variables: +mode: sgml +sgml-minimize-attributes:nil +sgml-general-insert-case:lower +sgml-indent-step:0 +sgml-indent-data:nil +sgml-parent-document:("index.docbook" "BOOK" "CHAPTER") +End: +--> + + diff --git a/tde-i18n-en_GB/docs/kdeedu/kmplot/introduction.docbook b/tde-i18n-en_GB/docs/kdeedu/kmplot/introduction.docbook new file mode 100644 index 00000000000..bd019128b9e --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kmplot/introduction.docbook @@ -0,0 +1,58 @@ +<chapter id="introduction"> +<title +>Introduction</title> + +<para +>&kmplot; is a mathematical function plotter for the &kde; Desktop. It has a powerful built-in parser. You can plot different functions simultaneously and combine them to build new functions.</para> + +<screenshot> +<screeninfo +>Examples</screeninfo> +<mediaobject> +<imageobject> +<imagedata fileref="threeplots.png" format="PNG"/> +</imageobject> +<textobject> +<phrase +>Examples</phrase> +</textobject> +</mediaobject> +</screenshot> + +<para +>&kmplot; supports parametric functions and functions in polar coordinates. Several grid modes are supported. Plots may be printed with high precision in the correct scale.</para> + +<para +>&kmplot; also provides some numerical an visual features like: <itemizedlist +> <listitem +><para +>Filling and calculating the area between the plot and the first axis</para +> </listitem +> <listitem +><para +>Finding maximum and minimum values</para +> </listitem +> <listitem +><para +>Changing function parameters dynamically</para +> </listitem +> <listitem +><para +>Plotting derivatives and integral functions.</para +> </listitem +> </itemizedlist +> These features help in learning the relationship between mathematical functions and their graphical representation in a coordinate system.</para> + +</chapter> + + +<!-- +Local Variables: +mode: sgml +sgml-minimize-attributes:nil +sgml-general-insert-case:lower +sgml-indent-step:0 +sgml-indent-data:nil +sgml-parent-document:("index.docbook" "BOOK" "CHAPTER") +End: +--> diff --git a/tde-i18n-en_GB/docs/kdeedu/kmplot/menu.docbook b/tde-i18n-en_GB/docs/kdeedu/kmplot/menu.docbook new file mode 100644 index 00000000000..a95730f1f30 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kmplot/menu.docbook @@ -0,0 +1,279 @@ +<chapter id="menu-entries"> +<title +>The Menu Entries</title> + +<sect1 id="file-menu"> +<title +>The <guimenu +>File</guimenu +> Menu</title> +<para> +<variablelist> + +<varlistentry> + <term> + <menuchoice +><shortcut +> <keycombo action="simul" +>&Ctrl;<keycap +>N</keycap +></keycombo +> </shortcut +> <guimenu +>File</guimenu +> <guimenuitem +>New</guimenuitem +> </menuchoice> + </term> + <listitem> + <para +><action +>Starts a new Plot by clearing the coordinate system and resetting the function parser.</action +></para +> + </listitem> +</varlistentry> + +<varlistentry> + <term> + <menuchoice +><shortcut +> <keycombo action="simul" +>&Ctrl;<keycap +>S</keycap +></keycombo +> </shortcut +> <guimenu +>File</guimenu +> <guimenuitem +>Save</guimenuitem +> </menuchoice> + </term> + <listitem> + <para> + <action +>Saves the document</action> + </para> + </listitem> +</varlistentry> + +<varlistentry> + <term> + <menuchoice +><guimenu +>File</guimenu +> <guimenuitem +>Save As...</guimenuitem +> </menuchoice> + </term> + <listitem> + <para> + <action +>Saves the document to a specific file</action> + </para> + </listitem> +</varlistentry> + +<varlistentry> + <term> + <menuchoice +><shortcut +> <keycombo action="simul" +>&Ctrl;<keycap +>P</keycap +></keycombo +> </shortcut +> <guimenu +>File</guimenu +> <guimenuitem +>Print...</guimenuitem +> </menuchoice> + </term> + <listitem> + <para +><action +>Sends the plot to the printer or to a file</action +></para> + </listitem> +</varlistentry> + +<varlistentry> + <term> + <menuchoice +><shortcut +> <keycombo action="simul" +>&Ctrl;<keycap +>Q</keycap +></keycombo +> </shortcut +> <guimenu +>File</guimenu +> <guimenuitem +>Quit</guimenuitem +> </menuchoice> + </term> + <listitem> + <para +><action +>Quits</action +> &kmplot;</para> + </listitem> +</varlistentry> +</variablelist> +</para> + +</sect1> + +<sect1 id="func-menu"> +<title +>The <guimenu +>Functions</guimenu +> Menu</title> + +<variablelist> +<varlistentry> + <term> + <menuchoice +><guimenu +>Functions</guimenu +> <guimenuitem +> Functions </guimenuitem +> </menuchoice> + </term> + <listitem> + <para +><guiicon +><inlinemediaobject +> <imageobject +> <imagedata fileref="kfkt.png" format="PNG"/> </imageobject +> </inlinemediaobject +> </guiicon +> <action +>Shows the Functions Dialogue Window where you can enter the function equations and some attributes of the plot.</action +></para +> + </listitem> +</varlistentry> + +</variablelist> +</sect1> + +<sect1 id="settings-menu"> +<title +>The <guimenu +>Settings</guimenu +> Menu</title> + +<para +>It contains the standard entries for enabling/disabling the toolbar and the statusbar. In addition there are the following options: </para> + +<variablelist> + +<varlistentry> + <term> + <menuchoice +><guimenu +>Settings</guimenu +> <guimenuitem +>Axes...</guimenuitem +> </menuchoice> + </term> + <listitem> + <para +><action +>...</action +></para> + </listitem> +</varlistentry> + +<varlistentry> + <term> + <menuchoice +><guimenu +>Settings</guimenu +> <guimenuitem +>Scale...</guimenuitem +> </menuchoice> + </term> + <listitem> + <para +><action +>...</action +></para> + </listitem> +</varlistentry> + +<varlistentry> + <term> + <menuchoice +><guimenu +>Settings</guimenu +> <guimenuitem +>Grid...</guimenuitem +> </menuchoice> + </term> + <listitem> + <para +><action +>...</action +></para> + </listitem> +</varlistentry> + +<varlistentry> + <term> + <menuchoice +><guimenu +>Settings</guimenu +> <guimenuitem +>Step...</guimenuitem +> </menuchoice> + </term> + <listitem> + <para +><action +>...</action +></para> + </listitem> +</varlistentry> + +</variablelist> + +</sect1> + +<sect1 id="help-menu"> +<title +>The <guimenu +>Help</guimenu +> Menu</title> + +<para +>&kmplot; has a standard &kde; <guimenu +>Help</guimenu +> as described below, with one addition:</para> + +<variablelist> +<varlistentry> +<term +><menuchoice +><guimenu +>Help</guimenu +> <guimenuitem +>Names...</guimenuitem +> </menuchoice +></term> +<listitem> +<para +>Opens a window with a list of function names, to help you remember them.</para> +</listitem> +</varlistentry> +</variablelist> + +<para +>The standard &kde; <guimenu +>Help</guimenu +> entries are:</para> +&help.menu.documentation; </sect1> +</chapter> + + diff --git a/tde-i18n-en_GB/docs/kdeedu/kmplot/reference.docbook b/tde-i18n-en_GB/docs/kdeedu/kmplot/reference.docbook new file mode 100644 index 00000000000..652d63e0869 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kmplot/reference.docbook @@ -0,0 +1,330 @@ +<chapter id="reference"> +<title +>&kmplot; Reference</title> + +<!-- +<mediaobject> +<imageobject> +<imagedata fileref="kfkt.png" format="PNG"/> +</imageobject> +</mediaobject> + +<para +>This menu entry or toolbar button opens the Functions Editor. Here +you can enter up to 10 functions or +function groups. The parser knows <firstterm +>explicit</firstterm +> and +<firstterm +>parametric</firstterm +> form. With specific extensions it +is possible to add first and second derivatives and to choose values +for the function group parameter.</para> +--> + +<sect1 id="func-syntax"> +<title +>Function Syntax</title> + +<para +>Some syntax rules must be complied with:</para> + +<screen +><userinput +>name(var1[, var2])=term [;extensions]</userinput +> +</screen> + + +<variablelist> +<varlistentry> +<term +>name</term> +<listitem> + +<para +>The function name. If the first character is <quote +>r</quote +> the parser assumes that you are using polar coordinates. If the first character is <quote +>x</quote +> (for instance <quote +>xfunc</quote +>) the parser expects a second function with a leading <quote +>y</quote +> (here <quote +>yfunc</quote +>) to define the function in parametric form. </para> +</listitem> +</varlistentry> +<varlistentry> +<term +>var1</term> +<listitem +><para +>The function's variable</para +></listitem> +</varlistentry> +<varlistentry> +<term +>var2</term +> +<listitem +><para +>The function <quote +>group parameter</quote +>. It must be separated from the function's variable by a comma. You can use the group parameter to, for example, plot a number of graphs from one function. The parameter values can be selected manually or you can choose to have a slider bar that controls one parameter. By changing the value of the slider the value parameter will be changed. The slider can be set to an integer between 0 and 100.</para +></listitem> +</varlistentry> +<varlistentry> +<term +>term</term> +<listitem +><para +>The expression defining the function.</para +></listitem> +</varlistentry> +</variablelist> +</sect1> + +<sect1 id="func-predefined"> +<title +>Predefined Function Names and Constants</title> + +<para +>All the predefined functions and constants that &kmplot; knows can be shown by selecting <menuchoice +><guimenu +>Help</guimenu +><guimenuitem +>Names</guimenuitem +> </menuchoice +>. They are: <variablelist> + +<varlistentry> +<term +>sqr, sqrt</term> +<listitem> +<para +>Return the square and square root of a number, respectively.</para> +</listitem> +</varlistentry> + +<varlistentry> +<term +>exp, ln</term> +<listitem> +<para +>Return the exponential and natural logarithm of a number, respectively.</para> +</listitem> +</varlistentry> + +<varlistentry> +<term +>log</term> +<listitem> +<para +>Returns the logarithm to base 10 of a number.</para> +</listitem> +</varlistentry> + +<varlistentry> +<term +>sin, arcsin</term> +<listitem> +<para +>Return the sine and inverse sine of a number, respectively. Note that the argument to sin and the return value of arcsin are in radians.</para> +</listitem> +</varlistentry> + +<varlistentry> +<term +>cos, arccos</term> +<listitem> +<para +>Return the cosine and inverse cosine of a number, respectively. Also in radians.</para> +</listitem> +</varlistentry> + +<varlistentry> +<term +>tan, arctan</term> +<listitem> +<para +>Return the tangent and inverse tangent of a number, respectively. Also in radians.</para> +</listitem> +</varlistentry> + +<varlistentry> +<term +>sinh, arcsinh</term> +<listitem> +<para +>Return the hyperbolic sine and inverse hyperbolic sine of a number, respectively.</para> +</listitem> +</varlistentry> + +<varlistentry> +<term +>cosh, arccosh</term> +<listitem> +<para +>Return the hyperbolic cosine and inverse hyperbolic cosine of a number, respectively.</para> +</listitem> +</varlistentry> + +<varlistentry> +<term +>tanh, arctanh</term> +<listitem> +<para +>Return the hyperbolic tangent and inverse hyperbolic tangent of a number, respectively.</para> +</listitem> +</varlistentry> + +<varlistentry> +<term +>sin, arcsin</term> +<listitem> +<para +>Return the sine and inverse sine of a number, respectively. Note that the argument to sin and the return value of arcsin are in radians.</para> +</listitem> +</varlistentry> + +<varlistentry> +<term +>cos, arccos</term> +<listitem> +<para +>Return the cosine and inverse cosine of a number, respectively. Also in radians.</para> +</listitem> +</varlistentry> + +<varlistentry> +<term +>pi, e</term> +<listitem> +<para +>Constants representing &pgr; (3.14159...) and e (2.71828...), respectively.</para> +</listitem> +</varlistentry> + +</variablelist> +</para> + +<para +>These functions and constants and even all user defined functions can be used to determine the axes settings as well. See <xref linkend="axes-config"/>. </para> + +</sect1> + +<sect1 id="math-syntax"> +<title +>Mathematical Syntax</title> +<para +>&kmplot; uses a common way of expressing mathematical functions, so you should have no trouble working it out. The operators &kmplot; understands are, in order of decreasing precedence: <variablelist> + +<varlistentry> +<term +>^</term> +<listitem +><para +>The caret symbol performs exponentiation. ⪚, <userinput +>2^4</userinput +> returns 16.</para> +</listitem> +</varlistentry> + +<varlistentry> +<term +>*, /</term> +<listitem> +<para +>The asterisk and slash symbols perform multiplication and division . ⪚, <userinput +>3*4/2</userinput +> returns 6.</para> +</listitem> +</varlistentry> + +<varlistentry> +<term +>+, -</term> +<listitem +><para +>The plus and minus symbols perform addition and subtraction. ⪚, <userinput +>1+3-2</userinput +> returns 2.</para> +</listitem> +</varlistentry> + +</variablelist> +</para> +<para +>Note the precedence, which means that if parentheses are not used, exponentiation is performed before multiplication/division, which is performed before addition/subtraction. So <userinput +>1+2*4^2</userinput +> returns 33, and not, say 144. To override this, use parentheses. To use the above example, <userinput +>((1+2)*4)^2</userinput +> <emphasis +>will</emphasis +> return 144. </para> +</sect1> + +<!-- +<sect1 id="coord-system"> +<title +>Coordinate Systems</title> + +<para +><inlinemediaobject> +<imageobject> +<imagedata fileref="ksys1.png" format="PNG"/> +</imageobject> +</inlinemediaobject +></para> + +<para> +<inlinemediaobject> +<imageobject> +<imagedata fileref="ksys2.png" format="PNG"/> +</imageobject> +</inlinemediaobject +></para> + +<para> +<inlinemediaobject> +<imageobject> +<imagedata fileref="ksys3.png" format="PNG"/> +</imageobject> +</inlinemediaobject +></para> +--> +<sect1 id="coord-area" +><title +>Plotting Area</title> +<para +>By default, explicitly given functions are plotted for the whole of the visible part of the x-axis. You can specify an other range in the edit-dialogue for the function. For every pixel on the x-axis &kmplot; calculates a function value. If the plotting area contains the resulting point it is connected to the last drawn point by a line. </para> +<para +>Parametric functions are plotted for parameter values from 0 up to 2&pgr;. You can set the plotting range in the dialogue for the function too. </para> +</sect1> + +<sect1 id="coord-cross"> +<title +>Cross Hair Cursor</title> +<para +>While the mouse cursor is over the plotting area the cursor changes to a cross hair. The current coordinates can be seen at the intersections with the coordinate axes and also in the status bar at the bottom of the main window. </para> +<para +>You can trace a function's values more precisely by clicking onto or next to a graph. The selected function is shown in the statusbar in the right column. The cross hair then will be caught and be coloured in the same colour as the graph. If the graph has the same colour as the background colour, the cross hair will have the inverted colour of the background. When moving the mouse or pressing the keys Left or Right the cross hair will follow the function and you see the current x- and y-value. If the cross hair is close to y-axis, the root-value is shown in the statusbar. You can switch function with the Up and Down keys. A second click anywhere in the window or pressing any non-navigating key will leave this trace mode. </para> +<para +>Note that tracing is only possible with explicitly given functions. The coordinates are always displayed according to a Cartesian system of coordinates. Neither non-single-point parametric functions nor functions given in polar coordinates can be traced in this way. </para> + +</sect1> + +</chapter> + +<!-- +Local Variables: +mode: sgml +sgml-minimize-attributes:nil +sgml-general-insert-case:lower +sgml-indent-step:0 +sgml-indent-data:nil +sgml-parent-document:("index.docbook" "BOOK" "CHAPTER") +End: +--> diff --git a/tde-i18n-en_GB/docs/kdeedu/kmplot/using.docbook b/tde-i18n-en_GB/docs/kdeedu/kmplot/using.docbook new file mode 100644 index 00000000000..1f0e7611dd3 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kmplot/using.docbook @@ -0,0 +1,384 @@ +<chapter id="using-kmplot"> +<title +>Using &kmplot;</title> + +<para +>&kmplot; deals with named functions, which can be specified in terms of Cartesian coordinates (called <quote +>explicit functions</quote +>), polar coordinates or as parametric functions. To enter a function, choose <menuchoice +><guimenu +>Plot</guimenu +><guimenuitem +>Edit Plots...</guimenuitem +> </menuchoice +>. You can also enter new functions in the <guilabel +>Function equation</guilabel +> text box in the main &kmplot; window. The text box can handle explicit and polar functions. Each function you enter must have a unique name (&ie;, a name that is not taken by any of the existing functions displayed in the list box). A function name will be automatically generated if you do not specify one.</para> + +<para +>For more information on &kmplot; functions, see <xref linkend="reference"/>. </para> + +<screenshot> +<screeninfo +>Here is a screenshot of the &kmplot; welcome window</screeninfo> + <mediaobject> + <imageobject> + <imagedata fileref="main.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>Screenshot</phrase> + </textobject> + </mediaobject> +</screenshot> + +<sect1 id="function-types"> +<title +>Function Types</title> + +<sect2 id="explicit-functions"> +<title +>Explicit Functions</title> +<para +>To enter an explicit function (&ie;, a function in the form y=f(x)) into &kmplot;, just enter it in the following form: <screen> +<userinput +><replaceable +>f</replaceable +>(<replaceable +>x</replaceable +>)=<replaceable +>expression</replaceable +></userinput> +</screen +> Where: <itemizedlist> +<listitem +><para +><replaceable +>f</replaceable +> is the name of the function, and can be any string of letters and numbers you like, provided it does not start with any of the letters x, y or r (since these are used for parametric and polar functions).</para> +</listitem> + +<listitem +><para +><replaceable +>x</replaceable +> is the x-coordinate, to be used in the expression following the equals sign. It is in fact a dummy variable, so you can use any variable name you like, but the effect will be the same.</para> +</listitem> + +<listitem> +<para +><replaceable +>expression</replaceable +> is the expression to be plotted, given in appropriate syntax for &kmplot;. See <xref linkend="math-syntax"/>. </para> +</listitem> + +</itemizedlist> +</para> +<para +>As an example, to draw the graph of y=x<superscript +>2</superscript +>+2x, enter the following into the functions dialogue of &kmplot;: <screen +>f(x)=x^2+2x +</screen> +</para> +</sect2> + +<sect2 id="parametric-functions"> +<title +>Parametric Functions</title> +<para +>Parametric functions are those in which the x and y coordinates are defined by separate functions of another variable, often called t. To enter a parametric function in &kmplot;, follow the procedure as for an explicit function, but prefix the name of the function describing the x-coordinate with the letter x, and the function describing the y-coordinate with the letter y. As with explicit functions, you may use any variable name you wish for the parameter. To draw a parametric function, you must go to <guimenu +>Functions</guimenu +><guimenuitem +>New Parametric Plot...</guimenuitem +>. A function name will be created automatic if you do not specify one.</para> +<para +>As an example, suppose you want to draw a circle, which has parametric equations x=sin(t), y=cos(t). In the &kmplot; functions dialogue, do the following: <orderedlist +> <listitem +><para +>Open the parametric plot dialogue with <menuchoice +><guimenu +>Plot</guimenu +><guimenuitem +>New Parametric Plot...</guimenuitem +> </menuchoice +>.</para +> </listitem +> <listitem +><para +>Enter a name for the function, say, <userinput +>circle</userinput +>, in the <guilabel +>Name</guilabel +> box. The names of the x and y functions change to match this name: the x function becomes <guilabel +>xcircle(t)</guilabel +> and the y function becomes <guilabel +>ycircle(t)</guilabel +>.</para +> </listitem +> <listitem +> <para +>In the x and y boxes, enter the appropriate equations, &ie;, <guilabel +>xcircle(t)=</guilabel +><userinput +>sin(t)</userinput +> and <guilabel +>ycircle(t)=</guilabel +><userinput +>cos(t)</userinput +>.</para +> </listitem +> </orderedlist +> Click on <guibutton +>OK</guibutton +> and the function will be drawn. </para> +<para +>You can set some further options for the plot in this dialogue: <variablelist> + +<varlistentry> +<term +><guilabel +>Hide</guilabel +></term> +<listitem> +<para +>If this option is selected, the plot is not drawn, but &kmplot; remembers the function definition, so you can use it to define other functions.</para> +</listitem> +</varlistentry> + +<varlistentry> +<term +><guilabel +>Custom Plot Range</guilabel +></term> +<listitem> +<para +>If this option is selected, you can change the maximum and minimum values of the parameter t for which the function is plotted using the <guilabel +>min</guilabel +> and <guilabel +>max</guilabel +> boxes.</para> +</listitem> +</varlistentry> + +<varlistentry> +<term +><guilabel +>Line width</guilabel +></term> +<listitem> +<para +>With this option you can set the width of the line drawn on the plot area, in units of 0.1mm.</para> +</listitem> +</varlistentry> + +<varlistentry> +<term +><guilabel +>Colour</guilabel +></term> +<listitem> +<para +>Click on the colour box and pick a colour in the dialogue that appears. The line on the plot will be drawn in this colour.</para> +</listitem> +</varlistentry> +</variablelist> +</para> +</sect2> + +<sect2 id="polar-functions"> +<title +>Entering Functions in Polar Coordinates</title> + +<para +>Polar coordinates represent a point by its distance from the origin (usually called r), and the angle a line from the origin to the point makes with the x-axis (usually represented by the Greek letter theta). To enter functions in polar coordinates, use the menu entry <menuchoice +><guimenu +>Plot</guimenu +><guimenuitem +>New Polar Plot...</guimenuitem +> </menuchoice +>. In the box labelled <guilabel +>r</guilabel +>, complete the function definition, including the name of the theta variable you want to use, ⪚, to draw the Archimedes' spiral r=theta, enter: <screen> +<userinput> +(theta)=theta +</userinput> +</screen +> so that the whole line reads <quote +>r(theta)=theta</quote +>. Note that you can use any name for the theta variable, so <quote +>r(foo)=foo</quote +> would have produced exactly the same output. </para> + +</sect2> + +</sect1> + +<sect1 id="combining-functions"> +<title +>Combining Functions</title> +<para +>Functions can be combined to produce new ones. Simply enter the functions after the equals sign in an expression as if the functions were variables. For example, if you have defined functions f(x) and g(x), you can plot the sum of f and g with: <screen +><userinput> +sum(x)=f(x)+g(x) +</userinput +> +</screen> +</para> +<para +>Note that you can only combine functions of the same type, ⪚ an explicit function cannot be combined with a polar function.</para> +</sect1> + +<sect1 id="function-appearance"> +<title +>Changing the appearance of functions</title> + +<para +>To change the appearance of a function's graph on the main plot window, select the function in the <guilabel +>Edit Plots</guilabel +> dialogue, and click on the <guibutton +>Edit</guibutton +> button. In the dialogue which appears, you can change the line width in the text box, and the colour of the function's graph by clicking on the colour button at the bottom. If you are editing an explicit function, you will see a dialogue with three tabs. In the first one you specify the equation of the function. The <guilabel +>Derivatives</guilabel +> tab lets you draw the first and second derivative to the function. With the <guilabel +>Integral</guilabel +> tab you can draw the integral of the function which is calculated using Euler's method. </para> +<para +>Another way to edit a function is to right click on the graph. In the popup menu that appears, choose <guibutton +>Edit</guibutton +></para> + +<para +>For more information on the popup menu, see <xref linkend="popupmenu"/>. </para> +</sect1> + +<sect1 id="popupmenu"> +<title +>Popup menu</title> + +<para +>When right-clicking on a plot function or a single-point parametric plot function a popup menu will appear. In the menu there are seven items available:</para> + +<variablelist> +<varlistentry> +<term +><menuchoice +><guimenuitem +>Hide</guimenuitem> +</menuchoice +></term> +<listitem> +<para +>Hides the selected graph. Other plots of the graph's function will still be shown.</para> +</listitem> +</varlistentry> + +<varlistentry> +<term +><menuchoice +><guimenuitem +>Remove</guimenuitem> +</menuchoice +></term> +<listitem> +<para +>Removes the function. All its graphs will disappear.</para> +</listitem> +</varlistentry> + +<varlistentry> +<term +><menuchoice +><guimenuitem +>Edit</guimenuitem> +</menuchoice +></term> +<listitem> +<para +>Shows the editor dialogue for the selected function.</para> +</listitem> +</varlistentry> +</variablelist> + +<para +>For plot functions the following four items are also available:</para> + +<variablelist> +<varlistentry> +<term +><menuchoice +><guimenuitem +>Get y-value</guimenuitem> +</menuchoice +></term> +<listitem> +<para +>Opens a dialogue in which you can find the y-value corresponding to a specific x-value. The selected graph will be highlighted in the dialogue. Enter an x value in the <guilabel +>X</guilabel +> box, and click on <guibutton +>Find</guibutton +> (or press &Enter;). The corresponding y value will be shown under <guilabel +>Y</guilabel +>. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term +><menuchoice +><guimenuitem +>Search for Minimum Value</guimenuitem> +</menuchoice +></term> +<listitem> +<para +>Find the minimum value of the graph in a specified range. The selected graph will be highlighted in the dialogue that appears. Enter the lower and upper boundaries of the region in which you want to search for a minimum, and click <guibutton +>Find</guibutton +>. The x and y values at the minimum will be shown.</para> +</listitem> +</varlistentry> + +<varlistentry> +<term +><menuchoice +><guimenuitem +>Search for Maximum Value</guimenuitem> +</menuchoice +></term> +<listitem> +<para +>This is the same as <guimenuitem +>Search for minimum value</guimenuitem +> above, but finds maximum values instead of minima. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term +><menuchoice +><guimenuitem +>Area Under Graph</guimenuitem> +</menuchoice +></term> +<listitem> +<para +>Draws the area between the graph and the x-axis. The selected graph will be highlighted in the new dialogue that appears. For more information on the Search for Area Under Graph-feature, see <xref linkend="a-tools-menu"/>.</para> +</listitem> +</varlistentry> +</variablelist> + + +</sect1> + + +</chapter> +<!-- +Local Variables: +mode: sgml +sgml-minimize-attributes:nil +sgml-general-insert-case:lower +sgml-indent-step:0 +sgml-indent-data:nil +sgml-parent-document:("index.docbook" "BOOK" "CHAPTER") +End: +--> diff --git a/tde-i18n-en_GB/docs/kdeedu/kstars/Makefile.am b/tde-i18n-en_GB/docs/kdeedu/kstars/Makefile.am new file mode 100644 index 00000000000..f781297a70f --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kstars/Makefile.am @@ -0,0 +1,4 @@ +KDE_LANG = en_GB +SUBDIRS = $(AUTODIRS) +KDE_DOCS = AUTO +KDE_MANS = AUTO diff --git a/tde-i18n-en_GB/docs/kdeedu/kstars/Makefile.in b/tde-i18n-en_GB/docs/kdeedu/kstars/Makefile.in new file mode 100644 index 00000000000..a7182419358 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kstars/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/kdeedu/kstars +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 = AUTO +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/kdeedu/kstars/Makefile'; \ +#>- cd $(top_srcdir) && \ +#>- $(AUTOMAKE) --gnu docs/kdeedu/kstars/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/kdeedu/kstars/Makefile'; \ + cd $(top_srcdir) && \ + $(AUTOMAKE) --gnu docs/kdeedu/kstars/Makefile + cd $(top_srcdir) && perl ../scripts/admin/am_edit -p../scripts/admin docs/kdeedu/kstars/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=flux.docbook calc-sidereal.docbook geocoords.docbook scriptbuilder.docbook altvstime.docbook stars.docbook indi.docbook calc-apcoords.docbook index.docbook calc-geodetic.docbook calc-horizontal.docbook horizon.docbook calc-dayduration.docbook julianday.docbook calc-angdist.docbook utime.docbook calculator.docbook calc-ecliptic.docbook timezones.docbook credits.docbook csphere.docbook faq.docbook commands.docbook config.docbook hourangle.docbook spiralgalaxies.docbook ai-contents.docbook blackbody.docbook calc-julianday.docbook solarsys.docbook dcop.docbook lightcurves.docbook zenith.docbook index.cache.bz2 luminosity.docbook colorandtemp.docbook leapyear.docbook dumpmode.docbook wut.docbook tools.docbook calc-equinox.docbook ecliptic.docbook retrograde.docbook calc-eqgal.docbook magnitude.docbook greatcircle.docbook install.docbook astroinfo.docbook parallax.docbook Makefile.in details.docbook cequator.docbook darkmatter.docbook quicktour.docbook calc-precess.docbook meridian.docbook calc-planetcoords.docbook sidereal.docbook skycoords.docbook precession.docbook cpoles.docbook jmoons.docbook Makefile.am equinox.docbook ellipticalgalaxies.docbook + +#>+ 24 +index.cache.bz2: $(srcdir)/index.docbook $(KDE_XSL_STYLESHEET) calculator.docbook leapyear.docbook cpoles.docbook darkmatter.docbook solarsys.docbook geocoords.docbook astroinfo.docbook calc-equinox.docbook commands.docbook colorandtemp.docbook quicktour.docbook calc-ecliptic.docbook cequator.docbook scriptbuilder.docbook greatcircle.docbook ai-contents.docbook parallax.docbook horizon.docbook lightcurves.docbook stars.docbook luminosity.docbook wut.docbook calc-julianday.docbook blackbody.docbook index.docbook timezones.docbook ellipticalgalaxies.docbook utime.docbook magnitude.docbook flux.docbook calc-planetcoords.docbook calc-eqgal.docbook credits.docbook calc-sidereal.docbook csphere.docbook faq.docbook hourangle.docbook equinox.docbook dumpmode.docbook sidereal.docbook precession.docbook julianday.docbook jmoons.docbook install.docbook skycoords.docbook meridian.docbook config.docbook tools.docbook altvstime.docbook details.docbook calc-precess.docbook calc-horizontal.docbook retrograde.docbook dcop.docbook calc-dayduration.docbook spiralgalaxies.docbook indi.docbook calc-geodetic.docbook calc-angdist.docbook calc-apcoords.docbook ecliptic.docbook zenith.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)/kstars + @if test -f index.cache.bz2; then \ + echo $(INSTALL_DATA) index.cache.bz2 $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kstars/; \ + $(INSTALL_DATA) index.cache.bz2 $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kstars/; \ + elif test -f $(srcdir)/index.cache.bz2; then \ + echo $(INSTALL_DATA) $(srcdir)/index.cache.bz2 $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kstars/; \ + $(INSTALL_DATA) $(srcdir)/index.cache.bz2 $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kstars/; \ + fi + -rm -f $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kstars/common + $(LN_S) $(kde_libs_htmldir)/$(KDE_LANG)/common $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kstars/common + +uninstall-docs: + -rm -rf $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kstars + +clean-docs: + -rm -f index.cache.bz2 + + +#>+ 13 +install-nls: + $(mkinstalldirs) $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kstars + @for base in calculator.docbook leapyear.docbook cpoles.docbook darkmatter.docbook solarsys.docbook geocoords.docbook astroinfo.docbook calc-equinox.docbook commands.docbook colorandtemp.docbook quicktour.docbook calc-ecliptic.docbook cequator.docbook scriptbuilder.docbook greatcircle.docbook ai-contents.docbook parallax.docbook horizon.docbook lightcurves.docbook stars.docbook luminosity.docbook wut.docbook calc-julianday.docbook blackbody.docbook index.docbook timezones.docbook ellipticalgalaxies.docbook utime.docbook magnitude.docbook flux.docbook calc-planetcoords.docbook calc-eqgal.docbook credits.docbook calc-sidereal.docbook csphere.docbook faq.docbook hourangle.docbook equinox.docbook dumpmode.docbook sidereal.docbook precession.docbook julianday.docbook jmoons.docbook install.docbook skycoords.docbook meridian.docbook config.docbook tools.docbook altvstime.docbook details.docbook calc-precess.docbook calc-horizontal.docbook retrograde.docbook dcop.docbook calc-dayduration.docbook spiralgalaxies.docbook indi.docbook calc-geodetic.docbook calc-angdist.docbook calc-apcoords.docbook ecliptic.docbook zenith.docbook ; do \ + echo $(INSTALL_DATA) $$base $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kstars/$$base ;\ + $(INSTALL_DATA) $(srcdir)/$$base $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kstars/$$base ;\ + done + +uninstall-nls: + for base in calculator.docbook leapyear.docbook cpoles.docbook darkmatter.docbook solarsys.docbook geocoords.docbook astroinfo.docbook calc-equinox.docbook commands.docbook colorandtemp.docbook quicktour.docbook calc-ecliptic.docbook cequator.docbook scriptbuilder.docbook greatcircle.docbook ai-contents.docbook parallax.docbook horizon.docbook lightcurves.docbook stars.docbook luminosity.docbook wut.docbook calc-julianday.docbook blackbody.docbook index.docbook timezones.docbook ellipticalgalaxies.docbook utime.docbook magnitude.docbook flux.docbook calc-planetcoords.docbook calc-eqgal.docbook credits.docbook calc-sidereal.docbook csphere.docbook faq.docbook hourangle.docbook equinox.docbook dumpmode.docbook sidereal.docbook precession.docbook julianday.docbook jmoons.docbook install.docbook skycoords.docbook meridian.docbook config.docbook tools.docbook altvstime.docbook details.docbook calc-precess.docbook calc-horizontal.docbook retrograde.docbook dcop.docbook calc-dayduration.docbook spiralgalaxies.docbook indi.docbook calc-geodetic.docbook calc-angdist.docbook calc-apcoords.docbook ecliptic.docbook zenith.docbook ; do \ + rm -f $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kstars/$$base ;\ + done + + +#>+ 5 +distdir-nls: + for file in calculator.docbook leapyear.docbook cpoles.docbook darkmatter.docbook solarsys.docbook geocoords.docbook astroinfo.docbook calc-equinox.docbook commands.docbook colorandtemp.docbook quicktour.docbook calc-ecliptic.docbook cequator.docbook scriptbuilder.docbook greatcircle.docbook ai-contents.docbook parallax.docbook horizon.docbook lightcurves.docbook stars.docbook luminosity.docbook wut.docbook calc-julianday.docbook blackbody.docbook index.docbook timezones.docbook ellipticalgalaxies.docbook utime.docbook magnitude.docbook flux.docbook calc-planetcoords.docbook calc-eqgal.docbook credits.docbook calc-sidereal.docbook csphere.docbook faq.docbook hourangle.docbook equinox.docbook dumpmode.docbook sidereal.docbook precession.docbook julianday.docbook jmoons.docbook install.docbook skycoords.docbook meridian.docbook config.docbook tools.docbook altvstime.docbook details.docbook calc-precess.docbook calc-horizontal.docbook retrograde.docbook dcop.docbook calc-dayduration.docbook spiralgalaxies.docbook indi.docbook calc-geodetic.docbook calc-angdist.docbook calc-apcoords.docbook ecliptic.docbook zenith.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/kdeedu/kstars/Makefile'; \ + cd $(top_srcdir) && \ + $(AUTOMAKE) --gnu docs/kdeedu/kstars/Makefile + cd $(top_srcdir) && perl ../scripts/admin/am_edit -p../scripts/admin docs/kdeedu/kstars/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/kdeedu/kstars/ai-contents.docbook b/tde-i18n-en_GB/docs/kdeedu/kstars/ai-contents.docbook new file mode 100644 index 00000000000..84d694de674 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kstars/ai-contents.docbook @@ -0,0 +1,200 @@ +<sect1 id="ai-contents"> +<title +>AstroInfo: Table of Contents</title> + +<itemizedlist +><title +>The Sky and Coordinate Systems</title> + <listitem +><para +><link linkend="ai-skycoords" +>Celestial Coordinate Systems</link +></para +></listitem> + <listitem +><para +><link linkend="ai-cequator" +>Celestial Equator</link +></para +></listitem> + <listitem +><para +><link linkend="ai-cpoles" +>Celestial Poles</link +></para +></listitem> + <listitem +><para +><link linkend="ai-csphere" +>Celestial Sphere</link +></para +></listitem> + <listitem +><para +><link linkend="ai-ecliptic" +>The Ecliptic</link +></para +></listitem> + <listitem +><para +><link linkend="ai-equinox" +>The Equinoxes</link +></para +></listitem> + <listitem +><para +><link linkend="ai-geocoords" +>Geographic Coordinates</link +></para +></listitem> + <listitem +><para +><link linkend="ai-greatcircle" +>Great Circles</link +></para +></listitem> + <listitem +><para +><link linkend="ai-horizon" +>The Horizon</link +></para +></listitem> + <listitem +><para +><link linkend="ai-hourangle" +>Hour Angle</link +></para +></listitem> + <listitem +><para +><link linkend="ai-meridian" +>Local Meridian</link +></para +></listitem +> + <listitem +><para +><link linkend="ai-precession" +>Precession</link +></para +></listitem> + <listitem +><para +><link linkend="ai-zenith" +>The Zenith</link +></para +></listitem> +</itemizedlist> + +<itemizedlist +><title +>Time</title> + <listitem +><para +><link linkend="ai-julianday" +>Julian Day</link +></para +></listitem> + <listitem +><para +><link linkend="ai-leapyear" +>Leap Years</link +></para +></listitem> + <listitem +><para +><link linkend="ai-sidereal" +>Sidereal Time</link +></para +></listitem> + <listitem +><para +><link linkend="ai-timezones" +>Time Zones</link +></para +></listitem> + <listitem +><para +><link linkend="ai-utime" +>Universal Time</link +></para +></listitem> +</itemizedlist> + +<itemizedlist +><title +>Physics</title> + <listitem +><para +><link linkend="ai-blackbody" +>Blackbody Radiation</link +></para +></listitem> + <listitem +><para +><link linkend="ai-darkmatter" +>Dark Matter</link +></para +></listitem> + <listitem +><para +><link linkend="ai-flux" +>Flux</link +></para +></listitem> + <listitem +><para +><link linkend="ai-luminosity" +>Luminosity</link +></para +></listitem> + <listitem +><para +><link linkend="ai-parallax" +>Parallax</link +></para +></listitem> + <listitem +><para +><link linkend="ai-retrograde" +>Retrograde Motion</link +></para +></listitem> +</itemizedlist> + +<itemizedlist +><title +>Astrophysics</title> + <listitem +><para +><link linkend="ai-ellipgal" +>Elliptical Galaxies</link +></para +></listitem> + <listitem +><para +><link linkend="ai-spiralgal" +>Spiral Galaxies</link +></para +></listitem> + <listitem +><para +><link linkend="ai-magnitude" +>The Magnitude Scale</link +></para +></listitem> + <listitem +><para +><link linkend="ai-stars" +>Stars: An Introductory FAQ</link +></para +></listitem> + <listitem +><para +><link linkend="ai-colorandtemp" +>Star Colours and Temperatures</link +></para +></listitem> +</itemizedlist> + +</sect1> diff --git a/tde-i18n-en_GB/docs/kdeedu/kstars/altvstime.docbook b/tde-i18n-en_GB/docs/kdeedu/kstars/altvstime.docbook new file mode 100644 index 00000000000..5761864a34e --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kstars/altvstime.docbook @@ -0,0 +1,77 @@ +<sect1 id="tool-altvstime"> +<title +>Altitude vs. Time Tool</title> +<indexterm +><primary +>Tools</primary> +<secondary +>Altitude vs. Time Tool</secondary> +</indexterm> + +<screenshot> +<screeninfo +>The Altitude vs. Time Tool </screeninfo> +<mediaobject> + <imageobject> + <imagedata fileref="altvstime.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>Altitude vs. Time Plotter</phrase> + </textobject> +</mediaobject> +</screenshot> + +<para +>This tool plots the altitude of any objects as a function of time, for any date and location on Earth. The top section is a graphical plot of altitude angle on the vertical axis, and time on the horizontal axis. The time is shown both as standard local time along the bottom, and <link linkend="ai-sidereal" +>sidereal time</link +> along the top. The bottom half of the graph is shaded green to indicate that points in this region are below the horizon. </para> +<para +>There are a few ways to add curves to the plot. The simplest way to add the curve of an existing object is to simply type its name in the <guilabel +>Name</guilabel +> input field, and press Enter, or the <guibutton +>Plot</guibutton +> button. If the text you enter is found in the object database, the object's curve is added to the graph. You can also press the <guibutton +>Browse</guibutton +> button to open the <link linkend="findobjects" +>Find Object Window</link +> to select an object from the list of known objects. If you want to add a point that does not exist in the object database, simply enter a name for the point, and then fill in the coordinates in the <guilabel +>RA</guilabel +> and <guilabel +>Dec</guilabel +> input fields. Then press the <guibutton +>Plot</guibutton +> button to add the curve for your custom object to the plot (note that you have to pick a name that does not already exist in the object database for this to work). </para> +<para +>When you add an object to the plot, its altitude vs. time curve is plotted with a thick white line, and its name is added to the listbox at the lower right. Any objects that were already present are plotted with a thinner red curve. You can choose which object is plotted with the thick white curve by highlighting its name in the listbox. </para> +<para +>These curves show the objects' Altitude (angle above the <link linkend="ai-horizon" +>horizon</link +>) as a function of time. When a curve passes from the lower half to the upper half, the object has risen; when it falls back to the lower half, it has set. For example, in the screenshot, the minor planet <firstterm +>Quaoar</firstterm +> is rising at around 15:30 local time, and is setting at about 00:30. </para> +<para +>The Altitude of an object depends on both where you are on Earth, and on the Date. By default, the Tool adopts the Location and Date from the current KStars settings. You can change these parameters in the <guilabel +>Date & Location</guilabel +> Tab. To change the Location, you can press the <guibutton +>Choose City...</guibutton +> button to open the <link linkend="setgeo" +>Set Geographic Location</link +> Window, or enter Longitude and Latitude values manually in the input fields, and press the <guibutton +>Update</guibutton +> button. To change the Date, use the <guilabel +>Date</guilabel +> picker widget, then press <guibutton +>Update</guibutton +>. Note that any curves you had already plotted will be automatically updated when you change the Date and/or Location. </para> + +<tip> +<para +>Exercise:</para> +<para +>Plot the Sun's Altitude curve. Make sure the geographic location is not near the equator. Change the Date to some time in June, and then again to sometime in January. You can see easily why we have seasons; in the winter, the Sun is above the horizon for less time (the days are shorter), and its altitude is never very high. </para> +</tip> + + +</sect1> + diff --git a/tde-i18n-en_GB/docs/kdeedu/kstars/astroinfo.docbook b/tde-i18n-en_GB/docs/kdeedu/kstars/astroinfo.docbook new file mode 100644 index 00000000000..d054cd6c01b --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kstars/astroinfo.docbook @@ -0,0 +1,9 @@ +<chapter id="astroinfo"> +<title +>The AstroInfo Project</title> + +<para +>Here you can find a collection of short articles that explain various astronomical concepts used in &kstars;. From coordinate systems to celestial mechanics, you can find answers to your questions here. </para +><para +>The articles sometimes also contain exercises that you can perform with &kstars; to illustrate the concept behind the article. </para> +&contents; &skycoords; &cequator; &cpoles; &csphere; &ecliptic; &equinox; &geocoords; &greatcircle; &horizon; &hourangle; &meridian; &precession; &zenith; &julianday; &leapyear; &sidereal; &timezones; &utime; &blackbody; &darkmatter; &flux; &luminosity; ¶llax; &retrograde; &ellipgal; &spiralgal; &magnitude; &stars; &colorandtemp; </chapter> diff --git a/tde-i18n-en_GB/docs/kdeedu/kstars/blackbody.docbook b/tde-i18n-en_GB/docs/kdeedu/kstars/blackbody.docbook new file mode 100644 index 00000000000..9d9603657f8 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kstars/blackbody.docbook @@ -0,0 +1,126 @@ +<sect1 id="ai-blackbody"> + +<sect1info> + +<author +><firstname +>Jasem</firstname +> <surname +>Mutlaq</surname +> <affiliation +><address +> <email +>mutlaqja@ku.edu</email> +</address +></affiliation> +</author> +</sect1info> + +<title +>Blackbody Radiation</title> +<indexterm +><primary +>Blackbody Radiation</primary> +<seealso +>Star Colours and Temperatures</seealso> +</indexterm> + +<para +>A <firstterm +>blackbody</firstterm +> refers to an opaque object that emits <firstterm +>thermal radiation</firstterm +>. A perfect blackbody is one that absorbs all incoming light and does not reflect any. At room temperature, such an object would appear to be perfectly black (hence the term <emphasis +>blackbody</emphasis +>). However, if heated to a high temperature, a blackbody will begin to glow with <firstterm +>thermal radiation</firstterm +>. </para> + +<para +>In fact, all objects emit thermal radiation (as long as their temperature is above Absolute Zero, or -273.15 degrees Celsius), but no object emits thermal radiation perfectly; rather, they are better at emitting/absorbing some wavelengths of light than others. These uneven efficiencies make it difficult to study the interaction of light, heat and matter using normal objects. </para> + +<para +>Fortunately, it is possible to construct a nearly-perfect blackbody. Construct a box made of a thermally conductive material, such as metal. The box should be completely closed on all sides, so that the inside forms a cavity that does not receive light from the surroundings. Then, make a small hole somewhere on the box. The light coming out of this hole will almost perfectly resemble the light from an ideal blackbody, for the temperature of the air inside the box. </para> + +<para +>At the beginning of the 20th century, scientists Lord Rayleigh, and Max Planck (among others) studied the blackbody radiation using such a device. After much work, Planck was able to empirically describe the intensity of light emitted by a blackbody as a function of wavelength. Furthermore, he was able to describe how this spectrum would change as the temperature changed. Planck's work on blackbody radiation is one of the areas of physics that led to the foundation of the wonderful science of Quantum Mechanics, but that is unfortunately beyond the scope of this article. </para> + +<para +>What Planck and the others found was that as the temperature of a blackbody increases, the total amount of light emitted per second increases, and the wavelength of the spectrum's peak shifts to bluer colours (see Figure 1). </para> + +<para> +<mediaobject> +<imageobject> +<imagedata fileref="blackbody.png" format="PNG"/> +</imageobject> +<caption +><para +><phrase +>Figure 1</phrase +></para +></caption> +</mediaobject> +</para> + +<para +>For example, an iron bar becomes orange-red when heated to high temperatures and its colour progressively shifts toward blue and white as it is heated further. </para> + +<para +>In 1893, German physicist Wilhelm Wien quantified the relationship between blackbody temperature and the wavelength of the spectral peak with the following equation: </para> + +<para> +<mediaobject> +<imageobject> +<imagedata fileref="lambda_max.png" format="PNG"/> +</imageobject> +</mediaobject> +</para> + +<para +>where T is the temperature in Kelvin. Wien's law (also known as Wien's displacement law) states that the wavelength of maximum emission from a blackbody is inversely proportional to its temperature. This makes sense; shorter-wavelength (higher-frequency) light corresponds to higher-energy photons, which you would expect from a higher-temperature object. </para> + +<para +>For example, the sun has an average temperature of 5800 K, so its wavelength of maximum emission is given by: <mediaobject +> <imageobject> +<imagedata fileref="lambda_ex.png" format="PNG"/> +</imageobject> +</mediaobject> +</para> + +<para +>This wavelengths falls in the green region of the visible light spectrum, but the sun's continuum radiates photons both longer and shorter than lambda(max) and the human eyes perceives the sun's colour as yellow/white. </para> + +<para +>In 1879, Austrian physicist Stephan Josef Stefan showed that the luminosity, L, of a black body is proportional to the 4th power of its temperature T. </para> + +<para> +<mediaobject> +<imageobject> +<imagedata fileref="luminosity.png" format="PNG"/> +</imageobject> +</mediaobject> +</para> + +<para +>where A is the surface area, alpha is a constant of proportionality, and T is the temperature in Kelvin. That is, if we double the temperature (e.g. 1000 K to 2000 K) then the total energy radiated from a blackbody increase by a factor of 2^4 or 16. </para> + +<para +>Five years later, Austrian physicist Ludwig Boltzman derived the same equation and is now known as the Stefan-Boltzman law. If we assume a spherical star with radius R, then the luminosity of such a star is </para> + +<para> +<mediaobject> +<imageobject> +<imagedata fileref="luminosity_ex.png" format="PNG"/> +</imageobject> +</mediaobject> +</para> + +<para +>where R is the star radius in cm, and the alpha is the Stefan-Boltzman constant, which has the value: <mediaobject +> <imageobject> +<imagedata fileref="alpha.png" format="PNG"/> +</imageobject> +</mediaobject> +</para> + +</sect1> diff --git a/tde-i18n-en_GB/docs/kdeedu/kstars/calc-angdist.docbook b/tde-i18n-en_GB/docs/kdeedu/kstars/calc-angdist.docbook new file mode 100644 index 00000000000..15de62623e9 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kstars/calc-angdist.docbook @@ -0,0 +1,39 @@ +<sect2 id="calc-angdist"> +<title +>Angular Distance module</title> +<indexterm +><primary +>Tools</primary> +<secondary +>Astrocalculator</secondary> +<tertiary +>Angular Distance module</tertiary> +</indexterm> + +<screenshot> +<screeninfo +>The Angular Distance calculator module </screeninfo> +<mediaobject> + <imageobject> + <imagedata fileref="calc-angdist.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>Angular Distance</phrase> + </textobject> +</mediaobject> +</screenshot> + +<para +>The Angular Distance tool is used to measure the angle between any two points on the sky. You simply specify the <link linkend="equatorial" +>Equatorial coordinates</link +> of the desired pair of points, and then press the <guibutton +>Compute</guibutton +> button to obtain the angle between the two points. </para> +<para +>There is also a Batch mode for this module. In batch mode, you specify an input filename which contains four numbers per line: the RA and Dec values for pairs of points. Alternatively, you can specify a single value for any of these four coordinates in the calculator panel (the corresponding values in the input file should be skipped if they are specified in the calculator). </para> +<para +>Once you have specified the input filename and an output filename, simply press the <guibutton +>Run</guibutton +> button to generate the output file. </para> +</sect2> diff --git a/tde-i18n-en_GB/docs/kdeedu/kstars/calc-apcoords.docbook b/tde-i18n-en_GB/docs/kdeedu/kstars/calc-apcoords.docbook new file mode 100644 index 00000000000..03471f5fccc --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kstars/calc-apcoords.docbook @@ -0,0 +1,45 @@ +<sect2 id="calc-apcoords"> +<title +>Apparent Coordinates module</title> +<indexterm +><primary +>Tools</primary> +<secondary +>Astrocalculator</secondary> +<tertiary +>Apparent Coordinates module</tertiary> +</indexterm> + +<screenshot> +<screeninfo +>The Apparent Coordinates calculator module </screeninfo> +<mediaobject> + <imageobject> + <imagedata fileref="calc-apcoords.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>Apparent Coordinates</phrase> + </textobject> +</mediaobject> +</screenshot> + +<para +>The Apparent Coordinates module converts the <firstterm +>catalogue coordinates</firstterm +> of a point in the sky to its <firstterm +>apparent coordinates</firstterm +> for any date. The coordinates of objects in the sky are not fixed, because of <link linkend="ai-precession" +>precession</link +>, nutation and aberration. This module takes these effects into account. </para> +<para +>To use the module, first enter the desired target date and time in the <guilabel +>Target Time/Date</guilabel +> section. Then, enter the catalogue coordinates in the <guilabel +>Catalog Coordinates</guilabel +> section. You can also specify the catalogue's epoch here (usually 2000.0 for modern object catalogues). Finally, press the <guibutton +>Compute</guibutton +> button, and the object's coordinates for the target date will be displayed in the <guilabel +>Apparent Coordinates</guilabel +> section. </para> +</sect2> diff --git a/tde-i18n-en_GB/docs/kdeedu/kstars/calc-dayduration.docbook b/tde-i18n-en_GB/docs/kdeedu/kstars/calc-dayduration.docbook new file mode 100644 index 00000000000..956b3a8c41d --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kstars/calc-dayduration.docbook @@ -0,0 +1,31 @@ +<sect2 id="calc-dayduration"> +<title +>Day Duration module</title> +<indexterm +><primary +>Tools</primary> +<secondary +>Astrocalculator</secondary> +<tertiary +>Day Duration module</tertiary> +</indexterm> + +<screenshot> +<screeninfo +>The Day Duration calculator module </screeninfo> +<mediaobject> + <imageobject> + <imagedata fileref="calc-daylength.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>Day Duration</phrase> + </textobject> +</mediaobject> +</screenshot> + +<para +>This module computes the length of day as well as sunrise, sun-transit (noon), and sunset times for any calendar date, for any location on Earth. First fill in the desired geographic coordinates and date, then press the <guibutton +>Compute</guibutton +> button. </para> +</sect2> diff --git a/tde-i18n-en_GB/docs/kdeedu/kstars/calc-ecliptic.docbook b/tde-i18n-en_GB/docs/kdeedu/kstars/calc-ecliptic.docbook new file mode 100644 index 00000000000..28487e4dfb4 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kstars/calc-ecliptic.docbook @@ -0,0 +1,45 @@ +<sect2 id="calc-ecliptic"> +<title +>Ecliptic Coordinates module</title> +<indexterm +><primary +>Tools</primary> +<secondary +>Astrocalculator</secondary> +<tertiary +>Ecliptic Coordinates module</tertiary> +</indexterm> + +<screenshot> +<screeninfo +>The Ecliptic Coordinates calculator module </screeninfo> +<mediaobject> + <imageobject> + <imagedata fileref="calc-ecliptic.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>Ecliptic Coordinates</phrase> + </textobject> +</mediaobject> +</screenshot> + +<para +>This module converts between <link linkend="equatorial" +>Equatorial coordinates</link +> and <link linkend="ecliptic" +>Ecliptic coordinates</link +>. First, select which coordinates should be taken as input values in the <guilabel +>Choose Input Coordinates</guilabel +> section. Then, fill in the corresponding coordinate values in either the <guilabel +>Ecliptic coordinates</guilabel +> or <guilabel +>Equatorial coordinates</guilabel +> section. Finally, press the <guibutton +>Compute</guibutton +> button, and the complementary coordinates will be filled in. </para> +<para +>The module contains a batch mode for converting several coordinate pairs at once. You must construct an input file in which each line contains two values: the input coordinate pairs (either Equatorial or Ecliptic). Then specify which coordinates you are using as input, and identify the input and output filenames. Finally, press the <guibutton +>Run</guibutton +> button to generate the output file, which will contain the converted coordinates (Equatorial or Ecliptic; the complement of what you chose as the input values). </para> +</sect2> diff --git a/tde-i18n-en_GB/docs/kdeedu/kstars/calc-eqgal.docbook b/tde-i18n-en_GB/docs/kdeedu/kstars/calc-eqgal.docbook new file mode 100644 index 00000000000..9c53a0b0e64 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kstars/calc-eqgal.docbook @@ -0,0 +1,42 @@ +<sect2 id="calc-eqgal"> +<title +>Equatorial/Galactic Coordinates module</title> +<indexterm +><primary +>Tools</primary> +<secondary +>Astrocalculator</secondary> +<tertiary +>Equatorial/Galactic Coordinates module</tertiary> +</indexterm> + +<screenshot> +<screeninfo +>The Equatorial/Galactic Coordinates calculator module </screeninfo> +<mediaobject> + <imageobject> + <imagedata fileref="calc-eqgal.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>Equatorial/Galactic Coordinates</phrase> + </textobject> +</mediaobject> +</screenshot> + +<para +>This module converts from <link linkend="equatorial" +>Equatorial coordinates</link +> to <link linkend="galactic" +>Galactic coordinates</link +>, and vice versa. First, select which coordinates should be taken as input values in the <guilabel +>Input Selection</guilabel +> section. Then, fill in the corresponding coordinate values in either the <guilabel +>Galactic coordinates</guilabel +> or <guilabel +>Equatorial coordinates</guilabel +> section. Finally, press the <guibutton +>Compute</guibutton +> button, and the complementary coordinates will be filled in. </para> +</sect2> + diff --git a/tde-i18n-en_GB/docs/kdeedu/kstars/calc-equinox.docbook b/tde-i18n-en_GB/docs/kdeedu/kstars/calc-equinox.docbook new file mode 100644 index 00000000000..04ab0393713 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kstars/calc-equinox.docbook @@ -0,0 +1,37 @@ +<sect2 id="calc-equinox"> +<title +>Equinoxes and Solstices module</title> +<indexterm +><primary +>Tools</primary> +<secondary +>Astrocalculator</secondary> +<tertiary +>Equinoxes and Solstices module</tertiary> +</indexterm> + +<screenshot> +<screeninfo +>The Equinoxes and Solstices calculator module </screeninfo> +<mediaobject> + <imageobject> + <imagedata fileref="calc-equinox.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>Equinoxes and Solstices</phrase> + </textobject> +</mediaobject> +</screenshot> + +<para +>The <link linkend="ai-equinox" +>Equinoxes</link +> and Solstices module calculates the date and time of an equinox or solstice for a given year. You specify which event (Spring Equinox, Summer Solstice, Autumn Equinox or Winter Solstice) should be investigated, and the year. Then press the <guibutton +>Compute</guibutton +> button to obtain the date and time of the event, and the length of the corresponding season, in days. </para> +<para +>There is a batch mode for this module. To use it, simply generate an input file whose lines each contain a year for which the Equinox and Solstice data will be computed. Then specify the input and output filenames, and press the <guibutton +>Run</guibutton +> button to generate the output file. Each line in the output file contains the input year, the date and time of each event, and the length of each season. </para> +</sect2> diff --git a/tde-i18n-en_GB/docs/kdeedu/kstars/calc-geodetic.docbook b/tde-i18n-en_GB/docs/kdeedu/kstars/calc-geodetic.docbook new file mode 100644 index 00000000000..0419968435f --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kstars/calc-geodetic.docbook @@ -0,0 +1,45 @@ +<sect2 id="calc-geodetic"> +<title +>Geodetic Coordinates module</title> +<indexterm +><primary +>Tools</primary> +<secondary +>Astrocalculator</secondary> +<tertiary +>Geodetic Coordinates module</tertiary> +</indexterm> + +<screenshot> +<screeninfo +>The Geodetic Coordinates calculator module </screeninfo> +<mediaobject> + <imageobject> + <imagedata fileref="calc-geodetic.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>Geodetic Coordinates</phrase> + </textobject> +</mediaobject> +</screenshot> + +<para +>The normal <link linkend="ai-geocoords" +>geographic coordinate system</link +> assumes that the Earth is a perfect sphere. This is nearly true, so for most purposes geographic coordinates are fine. If very high precision is required, then we must take the true shape of the Earth into account. The Earth is an ellipsoid; the distance around the equator is about 0.3% longer than a <link linkend="ai-greatcircle" +>Great Circle</link +> that passes through the poles. The <firstterm +>Geodetic Coordinate system</firstterm +> takes this ellipsoidal shape into account, and expresses the position on the Earth's surface in Cartesian coordinates (X, Y, and Z). </para> +<para +>To use the module, first select which coordinates you will use as input in the <guilabel +>Input Selection</guilabel +> section. Then, fill in the input coordinates in either the <guilabel +>Cartesian Coordinates</guilabel +> section or the <guilabel +>Geographic Coordinates</guilabel +> section. When you press the <guibutton +>Compute</guibutton +> button, the corresponding coordinates will be filled in. </para> +</sect2> diff --git a/tde-i18n-en_GB/docs/kdeedu/kstars/calc-horizontal.docbook b/tde-i18n-en_GB/docs/kdeedu/kstars/calc-horizontal.docbook new file mode 100644 index 00000000000..da36d32fc0e --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kstars/calc-horizontal.docbook @@ -0,0 +1,42 @@ +<sect2 id="calc-horiz"> +<title +>Horizontal Coordinates module</title> +<indexterm +><primary +>Tools</primary> +<secondary +>Astrocalculator</secondary> +<tertiary +>Horizontal Coordinates module</tertiary> +</indexterm> + +<screenshot> +<screeninfo +>The Horizontal Coordinates calculator module </screeninfo> +<mediaobject> + <imageobject> + <imagedata fileref="calc-horizontal.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>Horizontal Coordinates</phrase> + </textobject> +</mediaobject> +</screenshot> + +<para +>This module converts from <link linkend="equatorial" +>Equatorial coordinates</link +> to <link linkend="horizontal" +>Horizontal coordinates</link +>. First, select the date, time, and geographic coordinates for the calculation in the <guilabel +>Input Data</guilabel +> section. Then, fill in the equatorial coordinates to be converted and their catalogue epoch in the <guilabel +>Equatorial Coordinates</guilabel +> section. When you press the <guibutton +>Compute</guibutton +> button, the corresponding Horizontal coordinates will be presented in the <guilabel +>Horizontal Coordinates</guilabel +> section. </para> +</sect2> + diff --git a/tde-i18n-en_GB/docs/kdeedu/kstars/calc-julianday.docbook b/tde-i18n-en_GB/docs/kdeedu/kstars/calc-julianday.docbook new file mode 100644 index 00000000000..bd8b957c38d --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kstars/calc-julianday.docbook @@ -0,0 +1,45 @@ +<sect2 id="calc-julian"> +<title +>Julian Day module</title> +<indexterm +><primary +>Tools</primary> +<secondary +>Astrocalculator</secondary> +<tertiary +>Julian Day module</tertiary> +</indexterm> + +<screenshot> +<screeninfo +>The Julian Day calculator module </screeninfo> +<mediaobject> + <imageobject> + <imagedata fileref="calc-julian.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>Julian Day</phrase> + </textobject> +</mediaobject> +</screenshot> + +<para +>This module converts between the calendar date, the <link linkend="ai-julianday" +>Julian Day</link +> and the <firstterm +>Modified Julian Day</firstterm +>. The Modified Julian Day is simply equal to the Julian Day - 2,400,000.5. </para +><para +>To use the module, select which of the three dates will be the input, and then fill in its value. Then press the <guibutton +>Compute</guibutton +> button, and the corresponding values for the other two date systems will be displayed. </para> + +<tip> +<para +>Exercise:</para> +<para +>What calendar date does MJD = 0.0 correspond to? </para> +</tip> + +</sect2> diff --git a/tde-i18n-en_GB/docs/kdeedu/kstars/calc-planetcoords.docbook b/tde-i18n-en_GB/docs/kdeedu/kstars/calc-planetcoords.docbook new file mode 100644 index 00000000000..0188d75b90b --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kstars/calc-planetcoords.docbook @@ -0,0 +1,43 @@ +<sect2 id="calc-planetcoords"> +<title +>Planet Coordinates module</title> +<indexterm +><primary +>Tools</primary> +<secondary +>Astrocalculator</secondary> +<tertiary +>Planet Coordinates module</tertiary> +</indexterm> + +<screenshot> +<screeninfo +>The Planet Coordinates calculator module </screeninfo> +<mediaobject> + <imageobject> + <imagedata fileref="calc-planetcoords.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>Planet Coordinates</phrase> + </textobject> +</mediaobject> +</screenshot> + +<para +>The Planet Coordinates module computes positional data for any major solar system body, for any time and date and any geographic location. Simply select the <guilabel +>solar system body</guilabel +> from the drop-down list, and specify the desired date, time and geographic coordinates (these values are preset to the current &kstars; settings). Then press the <guibutton +>Compute</guibutton +> button to determine the <link linkend="equatorial" +>Equatorial</link +>, <link linkend="horizontal" +>Horizontal</link +> and <link linkend="ecliptic" +>Ecliptic</link +> coordinates of the body. </para> +<para +>There is a batch mode for this module. You must construct an input file in which each line specifies values for the input parameters (solar system body, date, time, longitude, and latitude). You may choose to specify a constant value for some of the parameters in the calculator window (these parameters should be skipped in the input file). You may also specify which of the output parameters (Equatorial, Horizontal and Ecliptic coordinates) should be calculated. Finally, specify the input and output filenames, and press the <guibutton +>Run</guibutton +> button to generate the output file with the computed values. </para> +</sect2> diff --git a/tde-i18n-en_GB/docs/kdeedu/kstars/calc-precess.docbook b/tde-i18n-en_GB/docs/kdeedu/kstars/calc-precess.docbook new file mode 100644 index 00000000000..27195079140 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kstars/calc-precess.docbook @@ -0,0 +1,43 @@ +<sect2 id="calc-precess"> +<title +>Precession module</title> +<indexterm +><primary +>Tools</primary> +<secondary +>Astrocalculator</secondary> +<tertiary +>Precession module</tertiary> +</indexterm> + +<screenshot> +<screeninfo +>The Precession calculator module </screeninfo> +<mediaobject> + <imageobject> + <imagedata fileref="calc-precess.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>Precession</phrase> + </textobject> +</mediaobject> +</screenshot> + +<para +>This module is similar to the <link linkend="calc-apcoords" +>Apparent Coordinates module</link +>, but it only applies the effect of <link linkend="ai-precession" +>precession</link +>, not of nutation or aberration. </para> +<para +>To use the module, first enter the input coordinates and their epoch in the <guilabel +>Original Coordinates</guilabel +> section. You must also fill in the target epoch in the <guilabel +>Precessed Coordinates</guilabel +> section. Then, press the <guibutton +>Compute</guibutton +> button, and the object's coordinates, precessed to the target Epoch, are presented in the <guilabel +>Precessed Coordinates</guilabel +> section. </para> +</sect2> diff --git a/tde-i18n-en_GB/docs/kdeedu/kstars/calc-sidereal.docbook b/tde-i18n-en_GB/docs/kdeedu/kstars/calc-sidereal.docbook new file mode 100644 index 00000000000..77a4ebb6112 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kstars/calc-sidereal.docbook @@ -0,0 +1,37 @@ +<sect2 id="calc-sidereal"> +<title +>Sidereal Time module</title> +<indexterm +><primary +>Tools</primary> +<secondary +>Astrocalculator</secondary> +<tertiary +>Sidereal Time module</tertiary> +</indexterm> + +<screenshot> +<screeninfo +>The Sidereal Time calculator module </screeninfo> +<mediaobject> + <imageobject> + <imagedata fileref="calc-sidereal.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>Sidereal Time</phrase> + </textobject> +</mediaobject> +</screenshot> + +<para +>This module converts between <link linkend="ai-utime" +>Universal Time</link +> and Local <link linkend="ai-sidereal" +>Sidereal Time</link +>. First, select whether you will use Universal Time or Sidereal Time as an input value in the <guilabel +>Input Selection</guilabel +> section. You must also specify a geographic longitude, and a date for the calculation, in addition to either the Universal Time or the Sidereal Time value. When you press the <guibutton +>Compute</guibutton +> button, the corresponding value for the other Time will be displayed. </para> +</sect2> diff --git a/tde-i18n-en_GB/docs/kdeedu/kstars/calculator.docbook b/tde-i18n-en_GB/docs/kdeedu/kstars/calculator.docbook new file mode 100644 index 00000000000..b36104194c3 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kstars/calculator.docbook @@ -0,0 +1,102 @@ +<sect1 id="tool-calculator"> +<title +>The Astrocalculator</title> +<indexterm +><primary +>Tools</primary> +<secondary +>Astrocalculator</secondary> +</indexterm> + +<para +>The &kstars; Astrocalculator provides several modules that give you direct access to algorithms used by the program. The modules are organised by subject: <itemizedlist +><title +>Coordinate Converters</title> +<listitem +><para +><link linkend="calc-angdist" +>Angular Distance</link +></para +></listitem> +<listitem +><para +><link linkend="calc-apcoords" +>Apparent Coordinates</link +></para +></listitem> +<listitem +><para +><link linkend="calc-ecliptic" +>Ecliptic Coordinates</link +></para +></listitem> +<listitem +><para +><link linkend="calc-eqgal" +>Equatorial/Galactic Coordinates</link +></para +></listitem> +<listitem +><para +><link linkend="calc-horiz" +>Horizontal Coordinates</link +></para +></listitem> +<listitem +><para +><link linkend="calc-precess" +>Precession</link +></para +></listitem> +</itemizedlist> +<itemizedlist +><title +>Earth Coordinates</title> +<listitem +><para +><link linkend="calc-geodetic" +>Geodetic Coordinates</link +></para +></listitem> +</itemizedlist> +<itemizedlist +><title +>Solar System</title> +<listitem +><para +><link linkend="calc-planetcoords" +>Planets Coordinates</link +></para +></listitem> +</itemizedlist> +<itemizedlist +><title +>Time Calculators</title> +<listitem +><para +><link linkend="calc-dayduration" +>Day Duration</link +></para +></listitem> +<listitem +><para +><link linkend="calc-equinox" +>Equinoxes and Solstices</link +></para +></listitem> +<listitem +><para +><link linkend="calc-julian" +>Julian Day</link +></para +></listitem> +<listitem +><para +><link linkend="calc-sidereal" +>Sidereal Time</link +></para +></listitem> +</itemizedlist> +</para> +&calc-angdist; &calc-apcoords; &calc-ecliptic; &calc-eqgal; &calc-horiz; &calc-precess; &calc-geodetic; &calc-planetcoords; &calc-dayduration; &calc-equinox; &calc-julian; &calc-sidereal; </sect1> + diff --git a/tde-i18n-en_GB/docs/kdeedu/kstars/cequator.docbook b/tde-i18n-en_GB/docs/kdeedu/kstars/cequator.docbook new file mode 100644 index 00000000000..112cc4f234a --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kstars/cequator.docbook @@ -0,0 +1,34 @@ +<sect1 id="ai-cequator"> +<sect1info> +<author +><firstname +>Jason</firstname +> <surname +>Harris</surname +> </author> +</sect1info> +<title +>The Celestial Equator</title> +<indexterm +><primary +>Celestial Equator</primary> +<seealso +>Equatorial Coordinates</seealso> +</indexterm> +<para +>The <firstterm +>Celestial Equator</firstterm +> is an imaginary <link linkend="ai-greatcircle" +>great circle</link +> on the <link linkend="ai-csphere" +>celestial sphere</link +>. The celestial equator is the fundamental plane of the <link linkend="equatorial" +>Equatorial Coordinate System</link +>, so it is defined as the locus of points with Declination of zero degrees. It is also the projection of the Earth's equator onto the sky. </para> +<para +>The Celestial Equator and the <link linkend="ai-ecliptic" +>Ecliptic</link +> are set at an angle of 23.5 degrees in the sky. The points where they intersect are the Vernal and Autumnal <link linkend="ai-equinox" +>Equinoxes</link +>. </para> +</sect1> diff --git a/tde-i18n-en_GB/docs/kdeedu/kstars/colorandtemp.docbook b/tde-i18n-en_GB/docs/kdeedu/kstars/colorandtemp.docbook new file mode 100644 index 00000000000..bf4663dbcd8 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kstars/colorandtemp.docbook @@ -0,0 +1,125 @@ +<sect1 id="ai-colorandtemp"> + +<sect1info> + +<author +><firstname +>Jasem</firstname +> <surname +>Mutlaq</surname +> <affiliation +><address +> <email +>mutlaqja@ku.edu</email> +</address +></affiliation> +</author> +</sect1info> + +<title +>Star Colours and Temperatures</title> +<indexterm +><primary +>Star Colours and Temperatures</primary> +<seealso +>Blackbody Radiation</seealso +> <seealso +>Magnitude Scale</seealso +> </indexterm> + +<para +>Stars appear to be exclusively white at first glance. But if we look carefully, we can notice a range of colours: blue, white, red and even gold. In the winter constellation of Orion, a beautiful contrast is seen between the red Betelgeuse at Orion's "armpit" and the blue Bellatrix at the shoulder. What causes stars to exhibit different colours remained a mystery until two centuries ago, when Physicists gained enough understanding of the nature of light and the properties of matter at immensely high temperatures. </para> + +<para +>Specifically, it was the physics of <link linkend="ai-blackbody" +>blackbody radiation</link +> that enabled us to understand the variation of stellar colours. Shortly after blackbody radiation was understood, it was noticed that the spectra of stars look extremely similar to blackbody radiation curves of various temperatures, ranging from a few thousand Kelvin to ~50,000 Kelvin. The obvious conclusion is that stars are similar to blackbodies, and that the colour variation of stars is a direct consequence of their surface temperatures. </para> + +<para +>Cool stars (i.e., Spectral Type K and M) radiate most of their energy in the red and infrared region of the electromagnetic spectrum and thus appear red, while hot stars (i.e., Spectral Type O and B) emit mostly at blue and ultra-violet wavelengths, making them appear blue or white. </para> + +<para +>To estimate the surface temperature of a star, we can use the known relationship between the temperature of a blackbody, and the wavelength of light where its spectrum peaks. That is, as you increase the temperature of a blackbody, the peak of its spectrum moves to shorter (bluer) wavelengths of light. This is illustrated in Figure 1 where the intensity of three hypothetical stars is plotted against wavelength. The "rainbow" indicates the range of wavelengths that are visible to the human eye. </para> + +<para> +<mediaobject> +<imageobject> + <imagedata fileref="star_colors.png" format="PNG"/> +</imageobject> +<caption +><para +><phrase +>Figure 1</phrase +></para +></caption> +</mediaobject> +</para> + +<para +>This simple method is conceptually correct, but it cannot be used to obtain stellar temperatures accurately, because stars are <emphasis +>not</emphasis +> perfect blackbodies. The presence of various elements in the star's atmosphere will cause certain wavelengths of light to be absorbed. Because these absorption lines are not uniformly distributed over the spectrum, they can skew the position of the spectral peak. Moreover, obtaining a usable spectrum of a star is a time-intensive process and is prohibitively inefficient for large samples of stars. </para> + +<para +>An alternative method utilises photometry to measure the intensity of light passing through different filters. Each filter allows <emphasis +>only</emphasis +> a specific part of the spectrum of light to pass through while rejecting all others. A widely used photometric system is called the <firstterm +>Johnson UBV system</firstterm +>. It employs three bandpass filters: U ("Ultra-violet"), B ("Blue"), and V ("Visible"); each occupying different regions of the electromagnetic spectrum. </para> + +<para +>The process of UBV photometry involves using light sensitive devices (such as film or CCD cameras) and aiming a telescope at a star to measure the intensity of light that passes through each of the filters individually. This procedure gives three apparent brightnesses or <link linkend="ai-flux" +>fluxes</link +> (amount of energy per cm^2 per second) designated by Fu, Fb, and Fv. The ratio of fluxes Fu/Fb and Fb/Fv is a quantitative measure of the star's "colour", and these ratios can be used to establish a temperature scale for stars. Generally speaking, the larger the Fu/Fb and Fb/Fv ratios of a star, the hotter its surface temperature. </para> + +<para +>For example, the star Bellatrix in Orion has Fb/Fv = 1.22, indicating that it is brighter through the B filter than through the V filter. furthermore, its Fu/Fb ratio is 2.22, so it is brightest through the U filter. This indicates that the star must be very hot indeed, since the position of its spectral peak must be somewhere in the range of the U filter, or at an even shorter wavelength. The surface temperature of Bellatrix (as determined from comparing its spectrum to detailed models that account for its absorption lines) is about 25,000 Kelvin. </para> + +<para +>We can repeat this analysis for the star Betelgeuse. Its Fb/Fv and Fu/Fb ratios are 0.15 and 0.18, respectively, so it is brightest in V and dimmest in U. So, the spectral peak of Betelgeuse must be somewhere in the range of the V filter, or at an even longer wavelength. The surface temperature of Betelgeuse is only 2,400 Kelvin. </para> + +<para +>Astronomers prefer to express star colours in terms of a difference in <link linkend="ai-magnitude" +>magnitudes</link +>, rather than a ratio of <link linkend="ai-flux" +>fluxes</link +>. Therefore, going back to blue Bellatrix we have a colour index equal to </para> + +<para +>B - V = -2.5 log (Fb/Fv) = -2.5 log (1.22) = -0.22, </para> + +<para +>Similarly, the colour index for red Betelgeuse is </para> + +<para +>B - V = -2.5 log (Fb/Fv) = -2.5 log (0.18) = 1.85 </para> + +<para +>The colour indices, like the <link linkend="ai-magnitude" +>magnitude scale</link +>, run backward. <emphasis +>Hot and blue</emphasis +> stars have <emphasis +>smaller and negative</emphasis +> values of B-V than the cooler and redder stars. </para> + +<para +>An Astronomer can then use the colour indices for a star, after correcting for reddening and interstellar extinction, to obtain an accurate temperature of that star. The relationship between B-V and temperature is illustrated in Figure 2. </para> + +<para> +<mediaobject> +<imageobject> + <imagedata fileref="color_indices.png"/> +</imageobject> +<caption +><para +><phrase +>Figure 2</phrase +></para +></caption> +</mediaobject> +</para> + +<para +>The Sun with surface temperature of 5,800 K has a B-V index of 0.62. </para> +</sect1> diff --git a/tde-i18n-en_GB/docs/kdeedu/kstars/commands.docbook b/tde-i18n-en_GB/docs/kdeedu/kstars/commands.docbook new file mode 100644 index 00000000000..3bd50192ba4 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kstars/commands.docbook @@ -0,0 +1,1895 @@ +<chapter id="commands"> +<title +>Command Reference</title> + +<sect1 id="kstars-menus"> +<title +>Menu Commands</title> +<indexterm +><primary +>Commands</primary +><secondary +>Menu</secondary +></indexterm> + +<sect2 id="filemenu"> +<title +><guimenu +>File</guimenu +> Menu</title> + +<variablelist> +<varlistentry> +<term +><menuchoice +><shortcut +> <keycombo action="simul" +>&Ctrl;<keycap +>N</keycap +></keycombo +> </shortcut +> <guimenu +>File</guimenu +> <guimenuitem +>New Window</guimenuitem +> </menuchoice +></term> +<listitem +><para +>Open another &kstars; window </para +></listitem> +</varlistentry> + +<varlistentry> +<term +><menuchoice +><shortcut +> <keycombo action="simul" +>&Ctrl;<keycap +>W</keycap +></keycombo +> </shortcut +> <guimenu +>File</guimenu +> <guimenuitem +>Close Window</guimenuitem +> </menuchoice +></term> +<listitem +><para +>Close &kstars; window </para +></listitem> +</varlistentry> + +<varlistentry> +<term +><menuchoice +><shortcut +> <keycombo action="simul" +>&Ctrl;<keycap +>D</keycap +></keycombo +> </shortcut +> <guimenu +>File</guimenu +> <guimenuitem +>Download Data...</guimenuitem +> </menuchoice +></term> +<listitem +><para +>Open the <guilabel +>Download Extra Data</guilabel +> tool </para +></listitem> +</varlistentry> + +<varlistentry> +<term +><menuchoice +><shortcut +> <keycombo action="simul" +>&Ctrl;<keycap +>O</keycap +></keycombo +> </shortcut +> <guimenu +>File</guimenu +> <guimenuitem +>Open FITS...</guimenuitem +> </menuchoice +></term> +<listitem +><para +>Open a FITS image in the FITS Editor tool </para +></listitem> +</varlistentry> + +<varlistentry> +<term +><menuchoice +><shortcut +> <keycombo action="simul" +>&Ctrl;<keycap +>I</keycap +></keycombo +> </shortcut +> <guimenu +>File</guimenu +> <guimenuitem +>Save Sky Image...</guimenuitem +> </menuchoice +></term> +<listitem +><para +>Create image on disk from current display </para +></listitem> +</varlistentry> + +<varlistentry> +<term +><menuchoice +><shortcut +> <keycombo action="simul" +>&Ctrl;<keycap +>R</keycap +></keycombo +> </shortcut +> <guimenu +>File</guimenu +> <guimenuitem +>Run Script...</guimenuitem +> </menuchoice +></term> +<listitem +><para +>Run the specified KStars script </para +></listitem> +</varlistentry> + +<varlistentry> +<term +><menuchoice +><shortcut +> <keycombo action="simul" +>&Ctrl;<keycap +>P</keycap +></keycombo +> </shortcut +> <guimenu +>File</guimenu +> <guimenuitem +>Print...</guimenuitem +> </menuchoice +></term> +<listitem +><para +>Send the current sky map to the printer (or to a PostScript/PDF file) </para +></listitem> +</varlistentry> + +<varlistentry> +<term +><menuchoice +><shortcut +> <keycombo action="simul" +>&Ctrl;<keycap +>Q</keycap +></keycombo +> </shortcut +> <guimenu +>File</guimenu +> <guimenuitem +>Quit</guimenuitem +> </menuchoice +></term> +<listitem +><para +>Quit &kstars; </para +></listitem> +</varlistentry> +</variablelist> + +</sect2> + +<sect2 id="timemenu"> +<title +><guimenu +>Time</guimenu +> Menu</title> + +<variablelist> +<varlistentry> +<term +><menuchoice +><shortcut +> <keycombo action="simul" +>&Ctrl;<keycap +>E</keycap +></keycombo +> </shortcut +> <guimenu +>Time</guimenu +> <guimenuitem +>Set Time to Now</guimenuitem +> </menuchoice +></term> +<listitem +><para +>Sync time to system clock</para +></listitem> +</varlistentry> + +<varlistentry> +<term +><menuchoice +><shortcut +> <keycombo action="simul" +>&Ctrl;<keycap +>S</keycap +></keycombo +> </shortcut +> <guimenu +>Time</guimenu +> <guimenuitem +>Set Time...</guimenuitem +> </menuchoice +></term> +<listitem +><para +>Set time and date</para +></listitem> +</varlistentry> + +<varlistentry> +<term +><menuchoice +><guimenu +>Time</guimenu +> <guimenuitem +>Start/Stop Clock</guimenuitem +> </menuchoice +></term> +<listitem +><para +>Toggle whether time passes</para +></listitem> +</varlistentry> +</variablelist> + +</sect2> + +<sect2 id="pointmenu"> +<title +><guimenu +>Pointing</guimenu +> Menu</title> + +<variablelist> +<varlistentry> +<term +><menuchoice +><shortcut +> <keycap +>Z</keycap +> </shortcut +> <guimenu +>Pointing</guimenu +> <guimenuitem +>Zenith</guimenuitem +> </menuchoice +></term> +<listitem +><para +>Centre the display at the <link linkend="ai-zenith" +>Zenith</link +> point (straight up) </para +></listitem> +</varlistentry> + +<varlistentry> +<term +><menuchoice +><shortcut +> <keycap +>N</keycap +> </shortcut +> <guimenu +>Pointing</guimenu +> <guimenuitem +>North</guimenuitem +> </menuchoice +></term> +<listitem +><para +>Centre the display above the North point on the horizon</para +></listitem> +</varlistentry> + +<varlistentry> +<term +><menuchoice +><shortcut +> <keycap +>E</keycap +> </shortcut +> <guimenu +>Pointing</guimenu +> <guimenuitem +>East</guimenuitem +> </menuchoice +></term> +<listitem +><para +>Centre the display above the East point on the horizon</para +></listitem> +</varlistentry> + +<varlistentry> +<term +><menuchoice +><shortcut +> <keycap +>S</keycap +> </shortcut +> <guimenu +>Pointing</guimenu +> <guimenuitem +>South</guimenuitem +> </menuchoice +></term> +<listitem +><para +>Centre the display above the South point on the horizon</para +></listitem> +</varlistentry> + +<varlistentry> +<term +><menuchoice +><shortcut +> <keycap +>W</keycap +> </shortcut +> <guimenu +>Pointing</guimenu +> <guimenuitem +>West</guimenuitem +> </menuchoice +></term> +<listitem +><para +>Centre the display above the West point on the horizon</para +></listitem> +</varlistentry> + +<varlistentry> +<term +><menuchoice +><shortcut +> <keycombo action="simul" +>&Ctrl;<keycap +>M</keycap +></keycombo +> </shortcut +> <guimenu +>Pointing</guimenu +> <guimenuitem +>Set Focus Manually...</guimenuitem +> </menuchoice +></term> +<listitem +><para +>Centre the display on specific <link linkend="ai-skycoords" +>sky coordinates</link +> </para +></listitem> +</varlistentry> + +<varlistentry> +<term +><menuchoice +><shortcut +> <keycombo action="simul" +>&Ctrl;<keycap +>F</keycap +></keycombo +> </shortcut +> <guimenu +>Pointing</guimenu +> <guimenuitem +>Find Object</guimenuitem +> </menuchoice +></term> +<listitem +><para +>Locate an object by name using the <link linkend="findobjects" +>Find Object Window</link +></para +></listitem> +</varlistentry> + +<varlistentry> +<term +><menuchoice +><shortcut +> <keycombo action="simul" +>&Ctrl;<keycap +>T</keycap +></keycombo +> </shortcut +> <guimenu +>Pointing</guimenu +> <guimenuitem +>Engage/Stop Tracking</guimenuitem +> </menuchoice +></term> +<listitem +><para +>Toggle tracking on/off. While tracking, the display will remain centred on the current position or object.</para +></listitem> +</varlistentry> +</variablelist> + +</sect2> + +<sect2 id="viewmenu"> +<title +><guimenu +>View</guimenu +> Menu</title> + +<variablelist> +<varlistentry> +<term +><menuchoice +><shortcut +> <keycap +>+</keycap +> </shortcut +> <guimenu +>View</guimenu +> <guimenuitem +>Zoom in</guimenuitem +> </menuchoice +></term> +<listitem +><para +>Zooms view in</para +></listitem> +</varlistentry> + +<varlistentry> +<term +><menuchoice +><shortcut +> <keycap +>-</keycap +> </shortcut +> <guimenu +>View</guimenu +> <guimenuitem +>Zoom out</guimenuitem +> </menuchoice +></term> +<listitem +><para +>Zooms view out</para +></listitem> +</varlistentry> + +<varlistentry> +<term +><menuchoice +><shortcut +> <keycombo action="simul" +>&Ctrl;<keycap +>Z</keycap +></keycombo +> </shortcut +> <guimenu +>View</guimenu +> <guimenuitem +>Default Zoom</guimenuitem +> </menuchoice +></term> +<listitem +><para +>Restore the default Zoom setting</para +></listitem> +</varlistentry> + +<varlistentry> +<term +><menuchoice +><shortcut +> <keycombo action="simul" +>&Ctrl;&Shift;<keycap +>Z</keycap +></keycombo +> </shortcut +> <guimenu +>View</guimenu +> <guimenuitem +>Zoom to Angular Size...</guimenuitem +> </menuchoice +></term> +<listitem +><para +>Zoom to specified field-of-view angle</para +></listitem> +</varlistentry> + +<varlistentry> +<term +><menuchoice +><shortcut +> <keycombo action="simul" +>&Ctrl;&Shift;<keycap +>F</keycap +></keycombo +> </shortcut +> <guimenu +>View</guimenu +> <guimenuitem +>Full Screen Mode</guimenuitem +> </menuchoice +></term> +<listitem +><para +>Toggle full-screen mode</para +></listitem> +</varlistentry> + +<varlistentry> +<term +><menuchoice +><shortcut +> <keycap +>Space</keycap +> </shortcut +> <guimenu +>View</guimenu +> <guimenuitem +>Horizontal/Equatorial Coordinates</guimenuitem +> </menuchoice +></term> +<listitem +><para +>Toggle between the <link linkend="horizontal" +>Horizontal</link +> and <link linkend="equatorial" +>Equatorial</link +> <link linkend="ai-skycoords" +>Coordinate Systems</link +></para +></listitem> +</varlistentry> +</variablelist> +</sect2> + +<sect2 id="devicemenu"> +<title +><guimenu +>Devices</guimenu +> Menu</title> + +<variablelist> + +<varlistentry> +<term +><menuchoice +><guimenu +>Devices</guimenu +> <guimenuitem +>Telescope Wizard...</guimenuitem +> </menuchoice +></term> +<listitem +><para +>Opens the <guilabel +>Telescope Wizard</guilabel +>, which provides a step-by-step guide to help you connect to your telescope and control it with &kstars;.</para +></listitem> +</varlistentry> + +<varlistentry> +<term +><menuchoice +><guimenu +>Devices</guimenu +> <guimenuitem +>Capture Image Sequence...</guimenuitem +> </menuchoice +></term> +<listitem +><para +>Acquire images from a CCD camera or webcam device</para +></listitem> +</varlistentry> + +<varlistentry> +<term +><menuchoice +><guimenu +>Devices</guimenu +> <guimenuitem +>Device Manager</guimenuitem +> </menuchoice +></term> +<listitem +><para +>Opens up the device manager, which allows you to start/shutdown device drivers and connect to remote INDI servers.</para +></listitem> +</varlistentry> + +<varlistentry> +<term +><menuchoice +><guimenu +>Devices</guimenu +> <guimenuitem +>INDI Control Panel</guimenuitem +> </menuchoice +></term> +<listitem +><para +>Opens up INDI Control Panel, which allows you to control all the features supported by a device.</para +></listitem> +</varlistentry> + +<varlistentry> +<term +><menuchoice +><guimenu +>Devices</guimenu +> <guimenuitem +>Configure INDI</guimenuitem +> </menuchoice +></term> +<listitem +><para +>Opens up a dialogue to configure INDI-related features such as automatic device updates.</para +></listitem> +</varlistentry> + +</variablelist> +</sect2> + +<sect2 id="toolmenu"> +<title +><guimenu +>Tools</guimenu +> Menu</title> + +<variablelist> +<varlistentry> +<term +><menuchoice +><shortcut +> <keycombo action="simul" +>&Ctrl;<keycap +>C</keycap +></keycombo +> </shortcut +> <guimenu +>Tools</guimenu +> <guimenuitem +>Calculator...</guimenuitem +> </menuchoice +></term> +<listitem> +<para +>Opens the <link linkend="tool-calculator" +>AstroCalculator</link +> Tool, which provides full access to many of the mathematical functions used by &kstars;. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term +><menuchoice +><shortcut +> <keycombo action="simul" +>&Ctrl;<keycap +>V</keycap +></keycombo +> </shortcut +> <guimenu +>Tools</guimenu +> <guimenuitem +>AAVSO Light Curves...</guimenuitem +> </menuchoice +></term> +<listitem> +<para +>Opens the <link linkend="tool-aavso" +>AAVSO Light Curve Generator</link +> Tool, which allows you to download a light curve for any variable star from the American Association of Variable Star Observers. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term +><menuchoice +><shortcut +> <keycombo action="simul" +>&Ctrl;<keycap +>A</keycap +></keycombo +> </shortcut +> <guimenu +>Tools</guimenu +> <guimenuitem +>Altitude vs. Time...</guimenuitem +> </menuchoice +></term> +<listitem> +<para +>Opens the <link linkend="tool-altvstime" +>Altitude vs. Time</link +> Tool, which can plot curves representing the altitude of any object as a function of time. This is useful for planning observing sessions. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term +><menuchoice +><shortcut +> <keycombo action="simul" +>&Ctrl;<keycap +>U</keycap +></keycombo +> </shortcut +> <guimenu +>Tools</guimenu +> <guimenuitem +>What's Up Tonight...</guimenuitem +> </menuchoice +></term> +<listitem> +<para +>Opens the <link linkend="tool-whatsup" +>What's Up Tonight</link +> Tool, which presents a summary of the objects which are observable from your location on a given date. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term +><menuchoice +><shortcut +> <keycombo action="simul" +>&Ctrl;<keycap +>B</keycap +></keycombo +> </shortcut +> <guimenu +>Tools</guimenu +> <guimenuitem +>Script Builder...</guimenuitem +> </menuchoice +></term> +<listitem> +<para +>Opens the <link linkend="tool-scriptbuilder" +>Script Builder</link +> Tool, which provides a GUI interface for building &kstars; DCOP scripts. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term +><menuchoice +><shortcut +> <keycombo action="simul" +>&Ctrl;<keycap +>Y</keycap +></keycombo +> </shortcut +> <guimenu +>Tools</guimenu +> <guimenuitem +>Solar System...</guimenuitem +> </menuchoice +></term> +<listitem> +<para +>Opens the <link linkend="tool-solarsys" +>Solar System Viewer</link +>, which displays an overhead view of the solar system on the current simulation date. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term +><menuchoice +><shortcut +> <keycombo action="simul" +>&Ctrl;<keycap +>J</keycap +></keycombo +> </shortcut +> <guimenu +>Tools</guimenu +> <guimenuitem +>Jupiter's Moons...</guimenuitem +> </menuchoice +></term> +<listitem> +<para +>Opens the <link linkend="tool-jmoons" +>Jupiter Moons Tool</link +>, which displays the positions of Jupiter's four brightest moons as a function of time. </para> +</listitem> +</varlistentry> + +</variablelist> +</sect2> + +<sect2 id="settingmenu"> +<title +><guimenu +>Settings</guimenu +> Menu</title> + +<variablelist> +<varlistentry> +<term +><menuchoice +><guimenu +>Settings</guimenu +> <guisubmenu +>Info Boxes</guisubmenu +> <guimenuitem +>Hide/Show Info Boxes</guimenuitem +> </menuchoice +></term> +<listitem +><para +>Toggle display of all three Info Boxes </para +></listitem> +</varlistentry> + +<varlistentry> +<term +><menuchoice +><guimenu +>Settings</guimenu +> <guisubmenu +>Info Boxes</guisubmenu +> <guimenuitem +>Hide/Show Time</guimenuitem +> </menuchoice +></term> +<listitem +><para +>Toggle display of the Time Info Box </para +></listitem> +</varlistentry> + +<varlistentry> +<term +><menuchoice +><guimenu +>Settings</guimenu +> <guisubmenu +>Info Boxes</guisubmenu +> <guimenuitem +>Hide/Show Focus</guimenuitem +> </menuchoice +></term> +<listitem +><para +>Toggle display of the Focus Info Box </para +></listitem> +</varlistentry> + +<varlistentry> +<term +><menuchoice +><guimenu +>Settings</guimenu +> <guisubmenu +>Info Boxes</guisubmenu +> <guimenuitem +>Hide/Show Location</guimenuitem +> </menuchoice +></term> +<listitem +><para +>Toggle display of the Location Info Box </para +></listitem> +</varlistentry> + +<varlistentry> +<term +><menuchoice +><guimenu +>Settings</guimenu +> <guisubmenu +>Toolbars</guisubmenu +> <guimenuitem +>Hide/Show Main Toolbar</guimenuitem +> </menuchoice +></term> +<listitem +><para +>Toggle display of the Main Toolbar </para +></listitem> +</varlistentry> + +<varlistentry> +<term +><menuchoice +><guimenu +>Settings</guimenu +> <guisubmenu +>Toolbars</guisubmenu +> <guimenuitem +>Hide/Show View Toolbar</guimenuitem +> </menuchoice +></term> +<listitem +><para +>Toggle display of the View Toolbar </para +></listitem> +</varlistentry> + +<varlistentry> +<term +><menuchoice +><guimenu +>Settings</guimenu +> <guisubmenu +>Statusbar</guisubmenu +> <guimenuitem +>Hide/Show Statusbar</guimenuitem +> </menuchoice +></term> +<listitem +><para +>Toggle display of the Statusbar </para +></listitem> +</varlistentry> + +<varlistentry> +<term +><menuchoice +><guimenu +>Settings</guimenu +> <guisubmenu +>Statusbar</guisubmenu +> <guimenuitem +>Hide/Show Az/Alt field</guimenuitem +> </menuchoice +></term> +<listitem +><para +>Toggle display of the mouse cursor's horizontal coordinates in the statusbar </para +></listitem> +</varlistentry> + +<varlistentry> +<term +><menuchoice +><guimenu +>Settings</guimenu +> <guisubmenu +>Statusbar</guisubmenu +> <guimenuitem +>Hide/Show RA/Dec field</guimenuitem +> </menuchoice +></term> +<listitem +><para +>Toggle display of the mouse cursor's horizontal coordinates in the statusbar </para +></listitem> +</varlistentry> + +<varlistentry> +<term +><menuchoice +><guimenu +>Settings</guimenu +> <guisubmenu +>Colour Schemes</guisubmenu +> </menuchoice +></term> +<listitem +><para +>This submenu contains all of the defined colour schemes, including your custom schemes. Select any item to set that colour scheme. </para +></listitem> +</varlistentry> + +<varlistentry> +<term +><menuchoice +><guimenu +>Settings</guimenu +> <guisubmenu +>FOV Symbols</guisubmenu +> </menuchoice +></term> +<listitem +><para +>This submenu lists the available field-of-view (FOV) Symbols. The FOV Symbol is drawn at the centre of the display. You may choose from the list of predefined symbols (No symbol, 7x35 Binoculars, One degree, or HST WFPC2), or you may define your own symbols (or modify existing symbols) using the <guimenuitem +>Edit FOV symbols...</guimenuitem +> item. </para +></listitem> +</varlistentry> + +<varlistentry> +<term +><menuchoice +><shortcut +> <keycombo action="simul" +>&Ctrl;<keycap +>G</keycap +></keycombo +> </shortcut +> <guimenu +>Settings</guimenu +> <guimenuitem +>Set Geographic Location...</guimenuitem +> </menuchoice +></term> +<listitem> +<para +>Select a new <link linkend="setgeo" +>geographic location</link +> </para> +</listitem> +</varlistentry> + +<varlistentry> +<term +><menuchoice +><guimenu +>Settings</guimenu +> <guimenuitem +>Configure &kstars;...</guimenuitem +> </menuchoice +></term> +<listitem +><para +>Modify <link linkend="config" +>configuration options</link +></para +></listitem> +</varlistentry> +</variablelist> +</sect2> + +<sect2 id="helpmenu"> +<title +><guimenu +>Help</guimenu +> Menu</title> +&help.menu.documentation; </sect2> + +<sect2 id="popup-menu"> +<title +>Popup Menu</title> +<indexterm +><primary +>Popup Menu</primary +><secondary +>Description</secondary +></indexterm> + +<para +>The <mousebutton +>right</mousebutton +> click popup menu is context-sensitive, meaning its content varies depending on what kind of object you click on. We list all possible popup menu items here, with the relevant object type [in brackets].</para> + +<variablelist> +<varlistentry> +<term +>[All]</term> +<listitem +><para +>Identification and type: The top one to three lines are devoted to the name(s) of the object and its type. For stars, the Spectral Type is also shown here. </para +></listitem> +</varlistentry> + +<varlistentry> +<term +>[All]</term> +<listitem +><para +>Rise, Transit and Set times for the object on the current simulation date are shown on the next three lines. </para +></listitem> +</varlistentry> + +<varlistentry> +<term +>[All]</term> +<listitem +><para +><guimenuitem +>Centre and Track</guimenuitem +>: Centre the display on this location, and engage tracking. Equivalent to double-clicking. </para +></listitem> +</varlistentry> + +<varlistentry> +<term +>[All]</term> +<listitem +><para +><guimenuitem +>Angular Distance To...</guimenuitem +>: Enter "angular distance mode". In this mode, a dotted line is drawn from the first target object to the current mouse position. When you invoke the popup menu of a second object, this item will read <guilabel +>Compute Angular Distance</guilabel +>. Selecting this item will display the angular distance between the two objects in the statusbar. You can press the <keycap +>Esc</keycap +> key to exit angular distance mode without measuring an angle. </para +></listitem> +</varlistentry> + +<varlistentry> +<term +>[All]</term> +<listitem +><para +><guimenuitem +>Details</guimenuitem +>: Open the <link linkend="tool-details" +>Object Details window</link +> for this object. </para +></listitem> +</varlistentry> + +<varlistentry> +<term +>[All]</term> +<listitem +><para +><guimenuitem +>Attach Label</guimenuitem +>: Attach a permanent name label to the object. If the object already has a label attached, this item will read <guilabel +>Remove Label</guilabel +>. </para +></listitem> +</varlistentry> + +<varlistentry> +<term +>[All]</term> +<listitem +><para +><guimenuitem +>Show ... Image</guimenuitem +>: download an image of the object from the internet, and display it in the Image Viewer tool. The "..." text is replaced by a short description of the image's source. An object may have multiple image links available in its popup menu. </para +></listitem> +</varlistentry> + +<varlistentry> +<term +>[All]</term> +<listitem +><para +><guimenuitem +>... Page</guimenuitem +>: Display a webpage about the object in your default web browser. The "..." text is replaced by a short description of the page. An object may have multiple web links available in its popup menu. </para +></listitem> +</varlistentry> + +<varlistentry> +<term +>[All Named Objects]</term> +<listitem +><para> +<indexterm +><primary +>Objects in the Sky</primary> +<secondary +>Internet Links</secondary> +<tertiary +>Customising</tertiary +></indexterm> +<guimenuitem +>Add Link...</guimenuitem +>: This allows you to add your own custom links to the popup menu of any object. It opens a small window in which you enter the &URL; of the link, and the text you want to appear in the popup menu. There is also a pair of radio buttons which allow you to specify whether the &URL; is an image or an <acronym +>HTML</acronym +> document, so &kstars; knows whether to launch the web browser or the image viewer. You can use this to add links to files on your local disk, so this feature could be used to attach observing logs or other custom information to objects in &kstars;. Your custom links are automatically loaded whenever &kstars; starts up, and they are stored in the folder <filename class="directory" +>~/.kde/share/apps/kstars/</filename +>, in files <filename +>myimage_url.dat</filename +> and <filename +>myinfo_url.dat</filename +>. If you build an extensive list of custom links, consider submitting them to us, we would like to include them in the next version of &kstars;! </para> +</listitem> +</varlistentry> +</variablelist> + +</sect2> +</sect1> + +<sect1 id="kstars-keys"> +<title +>Keyboard Commands</title> +<indexterm +><primary +>Commands</primary> +<secondary +>Keyboard</secondary +></indexterm> + +<sect2 id="nav-keys"> +<title +>Navigation Keys</title> +<indexterm +><primary +>Navigation Controls</primary> +<secondary +>Keyboard</secondary +></indexterm> + +<variablelist> +<varlistentry +><term +>Arrow Keys</term> +<listitem +><para +>Use the arrow keys to pan the display. Holding down the &Shift; key doubles the scrolling speed. </para +></listitem +></varlistentry> + +<varlistentry> +<term +><keycap +>+</keycap +> / <keycap +>-</keycap +></term> +<listitem +><para +>Zoom In/Out</para +></listitem> +</varlistentry> + +<varlistentry> +<term +><keycombo action="simul" +>&Ctrl;<keycap +>Z</keycap +></keycombo +></term> +<listitem +><para +>Restore the default Zoom setting</para +></listitem> +</varlistentry> + +<varlistentry> +<term +><keycombo action="simul" +>&Ctrl;&Shift;<keycap +>Z</keycap +></keycombo +></term> +<listitem +><para +>Zoom to specified field-of-view angle</para +></listitem> +</varlistentry> + +<varlistentry> +<term +>0–9</term> +<listitem +><para +>Center Display on a major Solar System body: <itemizedlist> +<listitem +><para +>0: Sun</para +></listitem> +<listitem +><para +>1: Mercury</para +></listitem> +<listitem +><para +>2: Venus</para +></listitem> +<listitem +><para +>3: Moon</para +></listitem> +<listitem +><para +>4: Mars</para +></listitem> +<listitem +><para +>5: Jupiter</para +></listitem> +<listitem +><para +>6: Saturn</para +></listitem> +<listitem +><para +>7: Uranus</para +></listitem> +<listitem +><para +>8: Neptune</para +></listitem> +<listitem +><para +>9: Pluto</para +></listitem> +</itemizedlist> +</para +></listitem> +</varlistentry> + +<varlistentry> +<term +><keycap +>Z</keycap +></term> +<listitem +><para +>Centre the display at the <link linkend="ai-zenith" +>Zenith</link +> Point (straight up)</para +></listitem> +</varlistentry> + +<varlistentry> +<term +><keycap +>N</keycap +></term> +<listitem +><para +>Centre the display above the North point on the horizon</para +></listitem> +</varlistentry> + +<varlistentry> +<term +><keycap +>E</keycap +></term> +<listitem +><para +>Centre the display above the East point on the horizon</para +></listitem> +</varlistentry> + +<varlistentry> +<term +><keycap +>S</keycap +></term> +<listitem +><para +>Centre the display above the South point on the horizon</para> +</listitem> +</varlistentry> + +<varlistentry> +<term +><keycap +>W</keycap +></term> +<listitem +><para +>Centre the display above the West point on the horizon</para +></listitem> +</varlistentry> + +<varlistentry> +<term +><keycombo action="simul" +>&Ctrl;<keycap +>F</keycap +></keycombo +></term> +<listitem +><para +>Open the <link linkend="findobjects" +>Find Object window</link +>, for specifying a sky object on which to centre</para +></listitem> +</varlistentry> + +<varlistentry +><term +><keycombo action="simul" +>&Ctrl;<keycap +>M</keycap +></keycombo> +</term> +<listitem +><para +>Open the <guilabel +>Set Manual Focus</guilabel +> tool, for specifying RA/Dec or Az/Alt coordinates on which to centre</para +></listitem> +</varlistentry> + +<varlistentry> +<term +><keycombo action="simul" +>&Ctrl;<keycap +>T</keycap +></keycombo +></term> +<listitem +><para +>Toggle tracking mode</para +></listitem> +</varlistentry> + +<varlistentry> +<term +><keycap +><</keycap +></term> +<listitem +><para +>Advance the simulation clock backwards by one time step</para> +</listitem> +</varlistentry> + +<varlistentry> +<term +><keycap +>></keycap +></term> +<listitem +><para +>Advance the simulation clock forwards by one time step</para> +</listitem> +</varlistentry> + +</variablelist> + +</sect2> + +<sect2 id="menu-keys"> +<title +>Menu Shortcuts</title> + +<variablelist> +<varlistentry> +<term +><keycombo action="simul" +>&Ctrl;<keycap +>N</keycap +></keycombo +></term> +<listitem +><para +>Open a new &kstars; window</para +></listitem> +</varlistentry> + +<varlistentry> +<term +><keycombo action="simul" +>&Ctrl;<keycap +>W</keycap +></keycombo +></term> +<listitem +><para +>Close a &kstars; window</para +></listitem> +</varlistentry> + +<varlistentry> +<term +><keycombo action="simul" +>&Ctrl;<keycap +>D</keycap +></keycombo +></term> +<listitem +><para +>Download extra data</para +></listitem> +</varlistentry> + +<varlistentry> +<term +><keycombo action="simul" +>&Ctrl;<keycap +>O</keycap +></keycombo +></term> +<listitem +><para +>Open a FITS image in the FITS Editor</para +></listitem> +</varlistentry> + +<varlistentry> +<term +><keycombo action="simul" +>&Ctrl;<keycap +>I</keycap +></keycombo +></term> +<listitem +><para +>Export sky image to a file</para +></listitem> +</varlistentry> + +<varlistentry> +<term +><keycombo action="simul" +>&Ctrl;<keycap +>R</keycap +></keycombo +></term> +<listitem +><para +>Run a &kstars; DCOP script</para +></listitem> +</varlistentry> + +<varlistentry> +<term +><keycombo action="simul" +>&Ctrl;<keycap +>P</keycap +></keycombo +></term> +<listitem +><para +>Print the current sky map</para +></listitem> +</varlistentry> + +<varlistentry> +<term +><keycombo action="simul" +>&Ctrl;<keycap +>Q</keycap +></keycombo +></term> +<listitem +><para +>Quit &kstars;</para +></listitem> +</varlistentry> + +<varlistentry> +<term +><keycombo action="simul" +>&Ctrl;<keycap +>E</keycap +></keycombo +></term> +<listitem +><para +>Sync the simulation clock with the current system time</para +></listitem> +</varlistentry> + +<varlistentry> +<term +><keycombo action="simul" +>&Ctrl;<keycap +>S</keycap +></keycombo +></term> +<listitem +><para +>Set the simulation clock to a specified Time and Date</para +></listitem> +</varlistentry> + +<varlistentry> +<term +><keycombo action="simul" +>&Ctrl;&Shift;<keycap +>F</keycap +></keycombo +></term> +<listitem +><para +>Toggle full-screen mode</para +></listitem> +</varlistentry> + +<varlistentry +><term +><keycap +>Space</keycap +></term> +<listitem +><para +>Toggle between the <link linkend="horizontal" +>Horizontal</link +> and <link linkend="equatorial" +>Equatorial</link +> <link linkend="ai-skycoords" +>Coordinate Systems</link +> </para +></listitem +></varlistentry> + +<varlistentry> +<term +><keycap +>F1</keycap +></term> +<listitem +><para +>Open the &kstars; Handbook</para +></listitem> +</varlistentry> +</variablelist> +</sect2> + +<sect2 id="tools-keys"> +<title +>Opening Tools</title> + +<variablelist> +<varlistentry> +<term +><keycombo action="simul" +>&Ctrl;<keycap +>G</keycap +></keycombo +></term> +<listitem +><para +>Open the <link linkend="setgeo" +>Set Geographic Location</link +> window</para +></listitem> +</varlistentry> + +<varlistentry> +<term +><keycombo action="simul" +>&Ctrl;<keycap +>C</keycap +></keycombo +></term> +<listitem +><para +>Open the <link linkend="tool-calculator" +>AstroCalculator</link +> </para +></listitem> +</varlistentry> + +<varlistentry> +<term +><keycombo action="simul" +>&Ctrl;<keycap +>V</keycap +></keycombo +></term> +<listitem +><para +>Open the <link linkend="tool-aavso" +>AAVSO Lightcurve Generator</link +></para +></listitem> +</varlistentry> + +<varlistentry> +<term +><keycombo action="simul" +>&Ctrl;<keycap +>A</keycap +></keycombo +></term> +<listitem +><para +>Open the <link linkend="tool-altvstime" +>Altitude vs. Time</link +> tool</para +></listitem> +</varlistentry> + +<varlistentry> +<term +><keycombo action="simul" +>&Ctrl;<keycap +>U</keycap +></keycombo +></term> +<listitem +><para +>Open the <link linkend="tool-whatsup" +>What's Up Tonight?</link +> tool </para +></listitem> +</varlistentry> + +<varlistentry> +<term +><keycombo action="simul" +>&Ctrl;<keycap +>B</keycap +></keycombo +></term> +<listitem +><para +>Open the <link linkend="tool-scriptbuilder" +>Script Builder</link +> tool</para +></listitem> +</varlistentry> + +<varlistentry> +<term +><keycombo action="simul" +>&Ctrl;<keycap +>Y</keycap +></keycombo +></term> +<listitem +><para +>Open the <link linkend="tool-solarsys" +>Solar System Viewer</link +> </para +></listitem> +</varlistentry> + +<varlistentry> +<term +><keycombo action="simul" +>&Ctrl;<keycap +>J</keycap +></keycombo +></term> +<listitem +><para +>Open the <link linkend="tool-jmoons" +>Jupiter Moons</link +> tool</para +></listitem> +</varlistentry> + +</variablelist> +</sect2> +</sect1> + +<sect1 id="kstars-mouse"> +<title +>Mouse Commands</title> +<indexterm +><primary +>Commands</primary> +<secondary +>Mouse</secondary +></indexterm> +<indexterm +><primary +>Navigation Controls</primary> +<secondary +>Mouse</secondary +></indexterm> + +<variablelist> +<varlistentry +><term +>Moving the mouse</term> +<listitem +><para +>The sky coordinates (RA/Dec and Az/Alt) of the mouse cursor are updated in the status bar </para +></listitem> +</varlistentry> + +<varlistentry +><term +>"Hovering" the mouse</term> +<listitem +><para +>A temporary name label is attached to the object nearest to the mouse cursor. </para +></listitem> +</varlistentry> + +<varlistentry +><term +>Left-clicking</term> +<listitem> +<para> +<indexterm +><primary +>Objects in the Sky</primary> +<secondary +>Identifying</secondary +></indexterm> +The object nearest the mouse click is identified in the status bar. </para +></listitem> +</varlistentry> + +<varlistentry +><term +>Double-clicking</term> +<listitem> +<para> +<indexterm +><primary +>Objects in the Sky</primary> +<secondary +>Centring</secondary +></indexterm> +Centre and track on the location or object nearest the mouse click. Double-clicking on an Info Box will <quote +>shade</quote +> it to show/hide extra information. </para +></listitem> +</varlistentry> + +<varlistentry +><term +>Right-clicking</term> +<listitem> +<para> +<indexterm +><primary +>Objects in the Sky</primary> +<secondary +>Invoking Popup Menu for</secondary +></indexterm> +Open the <link linkend="popup-menu" +>popup menu</link +> for the location or object nearest the mouse cursor. </para +></listitem> +</varlistentry> + +<varlistentry +><term +>Scrolling the mouse wheel</term> +<listitem +><para +>Zoom the display in or out. If you do not have a mouse wheel, you can hold the middle mouse button and drag vertically. </para +></listitem> +</varlistentry> + +<varlistentry +><term +>Click-and-dragging</term> +<listitem +><para> + <variablelist> + <varlistentry +><term +>Dragging the sky map</term> + <listitem +><para +>Pan the display, following the drag motion. </para +></listitem +></varlistentry> + <varlistentry +><term +>&Ctrl;+dragging the sky map</term> + <listitem +><para +>Define a rectangle in the map. When the mouse button is released, the display is zoomed in to match the field-of-view to the bounds of the rectangle. </para +></listitem +></varlistentry> + <varlistentry +><term +>Dragging an Info Box</term> + <listitem +><para +>The Info Box is repositioned in the map. Info Boxes will <quote +>stick</quote +> to window edges, so that they remain on the edge when the window is resized. </para +></listitem +></varlistentry> + </variablelist> +</para +></listitem> +</varlistentry> +</variablelist> + +</sect1> +</chapter> diff --git a/tde-i18n-en_GB/docs/kdeedu/kstars/config.docbook b/tde-i18n-en_GB/docs/kdeedu/kstars/config.docbook new file mode 100644 index 00000000000..e58e0a78325 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kstars/config.docbook @@ -0,0 +1,497 @@ +<chapter id="config"> +<title +>Configuring &kstars;</title> + +<sect1 id="setgeo"> +<title +>Setting the Geographic Location</title> + +<para +>Here is a screenshot of the <guilabel +>Set Geographic Location</guilabel +> window: <screenshot> +<screeninfo +>Changing the Geographic Location</screeninfo> +<mediaobject> + <imageobject> + <imagedata fileref="geolocator.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>Set Location Window</phrase> + </textobject> +</mediaobject> +</screenshot> +</para> + +<para +>There is a list of over 2500 predefined cities available to choose from. You set your location by highlighting a city from this list. Each city is represented in the world map as a small dot, and when a city is highlighted in the list, a red crosshairs appears on its location in the map. </para> + +<para> +<indexterm +><primary +>Geographic Location Tool</primary> +<secondary +>Filtering</secondary +></indexterm> +It is not practical to scroll through the full list of 2500 locations, looking for a specific city. To make searches easier, the list can be filtered by entering text in the boxes below the map. For example, in the screenshot, the text <quote +>Ba</quote +> appears in the <guilabel +>City Filter</guilabel +> box, while <quote +>M</quote +> has been entered in the <guilabel +>Province Filter</guilabel +> box, and <quote +>USA</quote +> is in the <guilabel +>Country Filter</guilabel +> box. Note that all of the cities displayed in the list have city, province and country names that begin with the entered filter strings, and that the message below the filter boxes indicates that 7 cities are matched by the filters. Also notice that the dots representing these seven cities in the map have been coloured white, while the unmatched cities remain grey. </para +><para +>The list can also be filtered by location in the map. Clicking anywhere in the world map will show only those cities within two degrees of the clicked location. At this time, you can search by name, or by location, but not both at once. In other words, when you click on the map, the name filters are ignored, and vice versa. </para +><para> +<indexterm +><primary +>Geographic Location Tool</primary> +<secondary +>Custom locations</secondary +></indexterm> +The <link linkend="ai-geocoords" +>longitude, latitude</link +> and <link linkend="ai-timezones" +>time zone</link +> information for the currently-selected location are displayed in the boxes at the bottom of the window. If you feel that any of these values are inaccurate, you can modify them and press the <guibutton +>Add to List</guibutton +> button to record your custom version of the location. You can also define a completely new location by pressing the <guibutton +>Clear Fields</guibutton +> button, and entering the data for the new location. Note that all fields except the optional <guilabel +>State/Province</guilabel +> must be filled before the new location can be added to the list. &kstars; will automatically load your custom locations for all future sessions. Please note, at this point, the only way to remove a custom location is to remove the appropriate line from the file <filename +>~/.kde/share/apps/kstars/mycities.dat</filename +>. </para +><para +>If you add custom locations (or modify existing ones), please send us your <filename +>mycities.dat</filename +> file so that we can add your locations to the master list. </para> +</sect1> + +<sect1 id="settime"> +<title +>Setting the Time</title> +<para> +<indexterm +><primary +>Date and Time</primary> +<secondary +>The simulation clock</secondary +></indexterm> +When &kstars; starts up, the time is set to your computer's system clock, and the &kstars; clock is running to keep up with the real time. If you want to stop the clock, select <guimenuitem +>Stop Clock</guimenuitem +> from the <guimenu +>Time</guimenu +> menu, or simply click on the <guiicon +>Pause</guiicon +> icon in the toolbar. You can make the clock run slower or faster than normal, or even make it run backward, using the time-step spinbox in the toolbar. This spinbox has two sets of up/down buttons. The first one will step through all 83 available time steps, one by one. The second one will skip to the next higher (or lower) unit of time, which allows you to make large timestep changes more quickly. </para> +<para> +<indexterm +><primary +>Date and Time</primary> +<secondary +>Setting</secondary +></indexterm> +You can set the time and date by selecting <guimenuitem +>Set Time...</guimenuitem +> from the <guimenu +>Time</guimenu +> menu, or by pressing the <guiicon +>time</guiicon +> icon in the toolbar. The <guilabel +>Set Time</guilabel +> window uses a standard &kde; Date Picker widget, coupled with three spinboxes for setting the hours, minutes and seconds. If you want to re-synchronise the simulation clock back to the current CPU time, just select <guimenuitem +>Set Time to Now</guimenuitem +> from the <guimenu +>Time</guimenu +> menu.</para> + +<note +><para> +<indexterm +><primary +>Date and Time</primary> +<secondary +>Extended range of dates</secondary +></indexterm> +&kstars; can accept very remote dates beyond the usual limits imposed by QDate. Currently, you can set the date between the years -50000 and +50000. We may extend this range even further in future releases. However, please be aware that the accuracy of the simulation becomes more and more degraded as more remote dates are examined. This is especially true for the positions of solar system bodies. </para +></note> +</sect1> + +<sect1 id="viewops"> +<title +>The Configure &kstars; Window</title> +<para> +<indexterm +><primary +>Configure &kstars; window</primary +></indexterm +> The <guilabel +>Configure &kstars;</guilabel +> window allows you to modify a wide range of display options. You can access the window with the <guiicon +>configure</guiicon +> toolbar icon, or by selecting <guimenuitem +>Configure &kstars;...</guimenuitem +> from the <guimenu +>Settings</guimenu +> menu. The window is depicted below: <screenshot> +<screeninfo +>Configure &kstars; Window</screeninfo> +<mediaobject> + <imageobject> + <imagedata fileref="viewops.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>Configure &kstars; Window</phrase> + </textobject> +</mediaobject> +</screenshot> +</para> + +<para +>The <guilabel +>Configure &kstars;</guilabel +> window is divided into five tabs: <guilabel +>Catalogues</guilabel +>, <guilabel +>Guides</guilabel +>, <guilabel +>Solar System</guilabel +>, <guilabel +>Colours</guilabel +> and <guilabel +>Advanced</guilabel +>. </para> +<para> +<indexterm +><primary +>Configure &kstars; window</primary> +<secondary +>Catalogues Tab</secondary +></indexterm> +In the <guilabel +>Catalogues</guilabel +> tab, you determine which object catalogues are displayed in the map. The <guilabel +>Stars</guilabel +> section also allows you to set the <quote +>faint <link linkend="ai-magnitude" +>magnitude</link +> limit</quote +> for stars, and the <link linkend="ai-magnitude" +>magnitude</link +> limit for displaying the names and/or magnitudes of stars. Below the stars section, the <guilabel +>Deep-Sky Objects</guilabel +> section controls the display of several non-stellar object catalogues. By default, the list includes the Messier, NGC and IC catalogues. You can add your own custom object catalogues by pressing the <guibutton +>Add Custom Catalog</guibutton +> button. For detailed instructions on preparing a catalogue data file, see the <filename +>README.customize</filename +> file that ships with &kstars;. </para> +<para> +<indexterm +><primary +>Configure &kstars; window</primary> +<secondary +>Solar System Tab</secondary +></indexterm> +In the <guilabel +>Solar System</guilabel +> tab, you can specify whether the Sun, Moon, planets, comets and asteroids are displayed, and whether the major bodies are drawn as coloured circles or actual images. You can also toggle whether solar system bodies have name labels attached, and control how many of the comets and asteroids get name labels. There is an option to automatically attach a temporary <quote +>orbit trail</quote +> whenever a solar system body is tracked, and another to toggle whether the colour of the orbit trail fades into the background sky colour. </para> +<para> +<indexterm +><primary +>Configure &kstars; window</primary> +<secondary +>Guides Tab</secondary +></indexterm> +The <guilabel +>Guides</guilabel +> tab lets you toggle whether non-objects are displayed (&ie;, constellation lines, constellation names, the Milky Way contour, the <link linkend="ai-cequator" +>celestial equator</link +>, <link linkend="ai-ecliptic" +>the ecliptic</link +>, <link linkend="ai-horizon" +>the horizon line</link +>, and the opaque ground). You can also choose whether you would like to see Latin constellation names, <acronym +>IAU</acronym +>-standard three-letter abbreviations, or constellation names using your local language. </para> +<para> +<indexterm +><primary +>Configure &kstars; window</primary> +<secondary +>Colours Tab</secondary +></indexterm> +<indexterm +><primary +>Colour Schemes</primary> +<secondary +>Customising</secondary +></indexterm> +The <guilabel +>Colours</guilabel +> tab allows you to set the colour scheme, and to define custom colour schemes. The tab is split into two panels: </para> +<para +>The left panel shows a list of all display items with adjustable colours. Click on any item to bring up a colour selection window to adjust its colour. Below the list is the <guilabel +>Star Colour Mode</guilabel +> selection box. By default, &kstars; draws stars with a <link linkend="ai-colorandtemp" +>realistic colour</link +> tint according to the spectral type of the star. However, you may also choose to draw the stars as solid white, black or red circles. If you are using the realistic star colours, you can set the saturation level of the star colours with the <guilabel +>Star Colour Intensity</guilabel +> spinbox. </para> +<para +>The right panel lists the defined colour schemes. There are four predefined schemes: the <guilabel +>Default</guilabel +> scheme, <guilabel +>Star Chart</guilabel +>, which uses black stars on a white background, <guilabel +>Night Vision</guilabel +>, which uses only shades of red in order to protect dark-adapted vision, and <guilabel +>Moonless Night</guilabel +>, a more realistic, dark theme. Additionally, you can save the current colour settings as a custom scheme by clicking the <guibutton +>Save Current Colors</guibutton +> button. It will prompt you for a name for the new scheme, and then your scheme will appear in the list in all future &kstars; sessions. To remove a custom scheme, simply highlight it in the list, and press the <guibutton +>Remove Colour Scheme</guibutton +> button. </para +><para> +<indexterm +><primary +>Configure &kstars; window</primary> +<secondary +>Advanced Tab</secondary +></indexterm> +The <guilabel +>Advanced</guilabel +> Tab provides fine-grained control over the more subtle behaviours of &kstars;. </para +><para> +<indexterm +><primary +>Atmospheric Refraction</primary +></indexterm +> The <guilabel +>Correct for atmospheric refraction</guilabel +> checkbox controls whether the positions of objects are corrected for the effects of the atmosphere. Because the atmosphere is a spherical shell, light from outer space is <quote +>bent</quote +> as it passes through the atmosphere to our telescopes or eyes on the Earth's surface. The effect is largest for objects near the horizon, and actually changes the predicted rise or set times of objects by a few minutes. In fact, when you <quote +>see</quote +> a sunset, the Sun's actual position is already well below the horizon; atmospheric refraction makes it seem as if the Sun is still in the sky. Note that atmospheric refraction is never applied if you are using <guilabel +>Equatorial coordinates</guilabel +>. </para +><para> +<indexterm +><primary +>Animated Slewing</primary +></indexterm +> The <guilabel +>Use animating slewing</guilabel +> checkbox controls how the display changes when a new focus position is selected in the map. By default, you will see the sky drift or <quote +>slew</quote +> to the new position; if you untick this option, then the display will instead <quote +>snap</quote +> immediately to the new focus position. </para +><para> +<indexterm +><primary +>Objects in the Sky</primary> +<secondary +>Labelling</secondary> +<tertiary +>Automatic</tertiary> +</indexterm> +If the <guilabel +>Attach label to centred object</guilabel +> checkbox is selected, then a name label will automatically be attached to an object when it is being tracked by the program. The label will be removed when the object is no longer being tracked. Note that you can also manually attach a persistent name label to any object with its <link linkend="popup-menu" +>popup menu</link +>. </para +><para> +<indexterm +><primary +>Objects in the Sky</primary> +<secondary +>Hiding</secondary +></indexterm> +There are three situations when &kstars; must redraw the sky display very rapidly: when a new focus position is selected (and <guilabel +>Use animated slewing</guilabel +> is checked), when the sky is dragged with the mouse, and when the time step is large. In these situations, the positions of all objects must be recomputed as rapidly as possible, which can put a large load on the <abbrev +>CPU</abbrev +>. If the <abbrev +>CPU</abbrev +> cannot keep up with the demand, then the display will seem sluggish or jerky. To mitigate this, &kstars; will hide certain objects during these rapid-redraw situations, as long as the <guilabel +>Hide objects while moving</guilabel +> checkbox is selected. The timestep threshold above which objects will be hidden is determined by the <guilabel +>Also hide if timescale greater than:</guilabel +> timestep-spinbox. You can specify the objects that should be hidden in the <guilabel +>Configure Hidden Objects</guilabel +> group box. </para> +</sect1> + +<sect1 id="customize"> +<title +>Customising the Display</title> + +<para +>There are several ways to modify the display to your liking.</para> +<itemizedlist> +<listitem +><para> +<indexterm +><primary +>Colour Schemes</primary +><secondary +>Selecting</secondary +></indexterm> +Select a different colour scheme in the <menuchoice +><guimenu +>Settings</guimenu +><guimenuitem +>Colour Schemes</guimenuitem +></menuchoice +> menu. There are four predefined colour schemes, and you can define your own in the <link linkend="config" +><guilabel +>Configure &kstars;</guilabel +></link +> window. </para +></listitem> +<listitem +><para> +<indexterm +><primary +>Toolbars</primary> +<secondary +>Customising</secondary +></indexterm> +Toggle whether the Toolbars are drawn in the <menuchoice +><guimenu +>Settings</guimenu +><guimenuitem +>Toolbars</guimenuitem +></menuchoice +> menu. Like most KDE toolbars, they can also be dragged around and anchored on any window edge, or even detached from the window completely. </para +></listitem> +<listitem +><para> +<indexterm +><primary +>Info Boxes</primary +><secondary +>Customising</secondary +></indexterm> +<indexterm +><primary +>Info Boxes</primary +><secondary +>Shading</secondary +></indexterm> +Toggle whether the Info Boxes are drawn in the <menuchoice +><guimenu +>Settings</guimenu +><guimenuitem +>Info Boxes</guimenuitem +></menuchoice +> menu. In addition, you can manipulate the three Info Boxes with the mouse. Each box has additional lines of data that are hidden by default. You can toggle whether these additional lines are visible by double-clicking a box to <quote +>shade</quote +> it. Also, you can reposition a box by dragging it with the mouse. When a box hits a window edge, it will <quote +>stick</quote +> to the edge when the window is resized. </para +></listitem> +<listitem> +<para> +<indexterm +><primary +>Field-of-View Symbols</primary +><secondary +>Description</secondary +></indexterm> +Choose an <quote +>FOV Symbol</quote +> using the <menuchoice +><guimenu +>Settings</guimenu +><guimenuitem +>FOV Symbols</guimenuitem +></menuchoice +> menu. <firstterm +>FOV</firstterm +> is an acronym for <quote +>field-of-view</quote +>. An FOV symbol is drawn at the centre of the window to indicate where the display is pointing. Different symbols have different angular sizes; you can use a symbol to show what the view through a particular telescope would look like. For example, if you choose the <quote +>7x35 Binoculars</quote +> FOV symbol, then a circle is drawn on the display that is 9.2 degrees in diameter; this is the field-of-view for 7x35 binoculars. </para> +<para> +<indexterm +><primary +>Field-of-View Symbols</primary +><secondary +>Customising</secondary +></indexterm> +You can define your own FOV symbols (or modify the existing symbols) using the <guimenuitem +>Edit FOV Symbols...</guimenuitem +> menu item, which launches the FOV Editor: </para> +<screenshot> +<screeninfo +>Field-of-View Symbols Editor</screeninfo> +<mediaobject> + <imageobject> + <imagedata fileref="fovdialog.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>FOV Symbol Editor</phrase> + </textobject> +</mediaobject> +</screenshot> + +<para +>The list of defined FOV symbols is displayed on the left. On the right are buttons for adding a new symbol, editing the highlighted symbol's properties, and removing the highlighted symbol from the list. Note that you can even modify or remove the four predefined symbols (if you remove all symbols, the four defaults will be restored the next time you start &kstars;). Below these three buttons is a graphical preview display showing the highlighted symbol from the list. When the <guibutton +>New...</guibutton +> or <guibutton +>Edit...</guibutton +> button is pressed, the <guilabel +>New FOV Symbol</guilabel +> window is opened: </para> + +<screenshot> +<screeninfo +>New Field-of-View Symbol</screeninfo> +<mediaobject> + <imageobject> + <imagedata fileref="newfov.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>New FOV Symbol</phrase> + </textobject> +</mediaobject> +</screenshot> + +<para> +<indexterm +><primary +>Field-of-View Symbols</primary +><secondary +>Defining New</secondary +></indexterm> +This window lets you modify the four properties that define a FOV symbol: name, size, shape and colour. The angular size for the symbol can either be entered directly in the <guilabel +>Field of View</guilabel +> edit box, or you can use the Eyepiece/Camera Tabs to calculate the field-of-view angle, given parameters of your telescope/eyepiece or telescope/camera setup. The four available shapes are: Circle, Square, Crosshairs, and Bullseye. Once you have specified all four parameters, press <guibutton +>Ok</guibutton +>, and the symbol will appear in the list of defined symbols. It will also be available from the <guimenu +>Settings</guimenu +> | <guisubmenu +>FOV</guisubmenu +> menu. </para> +</listitem> +</itemizedlist> + +</sect1> + +</chapter> diff --git a/tde-i18n-en_GB/docs/kdeedu/kstars/cpoles.docbook b/tde-i18n-en_GB/docs/kdeedu/kstars/cpoles.docbook new file mode 100644 index 00000000000..062494cefea --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kstars/cpoles.docbook @@ -0,0 +1,64 @@ +<sect1 id="ai-cpoles"> +<sect1info> +<author +><firstname +>Jason</firstname +> <surname +>Harris</surname +> </author> +</sect1info> +<title +>The Celestial Poles</title> +<indexterm +><primary +>Celestial Poles</primary> +<seealso +>Equatorial Coordinates</seealso> +</indexterm> +<para +>The sky appears to drift overhead from east to west, completing a full circuit around the sky in 24 (<link linkend="ai-sidereal" +>Sidereal</link +>) hours. This phenomenon is due to the spinning of the Earth on its axis. The Earth's spin axis intersects the <link linkend="ai-csphere" +>Celestial Sphere</link +> at two points. These points are the <firstterm +>Celestial Poles</firstterm +>. As the Earth spins; they remain fixed in the sky, and all other points seem to rotate around them. The celestial poles are also the poles of the <link linkend="equatorial" +>Equatorial Coordinate System</link +>, meaning they have <firstterm +>Declinations</firstterm +> of +90 degrees and -90 degrees (for the North and South celestial poles, respectively). </para +><para +>The North Celestial Pole currently has nearly the same coordinates as the bright star <firstterm +>Polaris</firstterm +> (which is Latin for <quote +>Pole Star</quote +>). This makes Polaris useful for navigation: not only is it always above the North point of the horizon, but its <link linkend="horizontal" +>Altitude</link +> angle is always (nearly) equal to the observer's <link linkend="ai-geocoords" +>Geographic Latitude</link +> (however, Polaris can only be seen from locations in the Northern hemisphere). </para +><para +>The fact that Polaris is near the pole is purely a coincidence. In fact, because of <link linkend="ai-precession" +>Precession</link +>, Polaris is only near the pole for a small fraction of the time. </para> +<tip> +<para +>Exercises:</para> +<para +>Use the <guilabel +>Find Object</guilabel +> window (<keycombo action="simul" +>&Ctrl;<keycap +>F</keycap +></keycombo +>) to locate Polaris. Notice that its Declination is almost (but not exactly) +90 degrees. Compare the Altitude reading when focused on Polaris to your location's geographic latitude. They are always within one degree of each other. They are not exactly the same because Polaris isn't exactly at the Pole. (you can point exactly at the pole by switching to Equatorial coordinates, and pressing the up-arrow key until the sky stops scrolling). </para +><para +>Use the <guilabel +>Time Step</guilabel +> spinbox in the toolbar to accelerate time to a step of 100 seconds. You can see the entire sky appears to rotate around Polaris, while Polaris itself remains nearly stationary. </para +><para +>We said that the celestial pole is the pole of the Equatorial coordinate system. What do you think is the pole of the horizontal (Altitude/Azimuth) coordinate system? (The <link linkend="ai-zenith" +>Zenith</link +>). </para> +</tip> +</sect1> diff --git a/tde-i18n-en_GB/docs/kdeedu/kstars/credits.docbook b/tde-i18n-en_GB/docs/kdeedu/kstars/credits.docbook new file mode 100644 index 00000000000..ee7bded9340 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kstars/credits.docbook @@ -0,0 +1,111 @@ +<chapter id="credits"> +<title +>Credits and Licence</title> + +<para +>&kstars;</para> +<para +>Program copyright 2001-2003 The &kstars; Team <email +>kstars@30doradus.org</email +> </para> + +<para +>The &kstars; Team: <itemizedlist> +<listitem +><para +>Jason Harris <email +>kstars@30doradus.org</email +></para> +</listitem> +<listitem +><para +>Jasem Mutlaq <email +>mutlaqja@ku.edu</email +></para> +</listitem> +<listitem +><para +>Pablo de Vicente <email +>pvicentea@wanadoo.es</email +></para> +</listitem> +<listitem +><para +>Heiko Evermann <email +>heiko@evermann.de</email +></para> +</listitem> +<listitem +><para +>Thomas Kabelmann <email +>tk78@gmx.de</email +></para> +</listitem> +<listitem +><para +>Mark Hollomon <email +>mhh@mindspring.com</email +></para> +</listitem> +<listitem +><para +>Carsten Niehaus <email +>cniehaus@gmx.de</email +></para> +</listitem> +</itemizedlist> +</para> + +<para +>Data Sources: <itemizedlist> +<listitem> +<para +>Object catalogues and planet position tables: <ulink url="http://adc.gsfc.nasa.gov" +>NASA Astronomical Data Center</ulink +></para> +</listitem> +<listitem> +<para +>Detailed credit information for all of the images used in the program is presented in the file README.images </para> +</listitem> +</itemizedlist> +</para> +<para +>References: <itemizedlist> +<listitem +><para +><quote +>Practical Astronomy With Your Calculator</quote +> by Peter Duffet-Smith</para +></listitem> +<listitem +><para +><quote +>Astronomical Algorithms</quote +> by Jean Meeus</para +></listitem> +</itemizedlist> +</para> + +<para +>Special thanks: To the &kde; and &Qt; developers for providing the world with a peerless set of free <acronym +>API</acronym +> libraries. To the <application +>KDevelop</application +> team, for their excellent <acronym +>IDE</acronym +>, which made developing &kstars; so much easier and more fun. To everyone on the <application +>KDevelop</application +> message board, the &kde; mailing lists, and on irc.kde.org, for answering our frequent questions. Thank you to Anne-Marie Mahfouf, for inviting &kstars; to join the &kde;-Edu module. Finally, thanks to everyone who has submitted bug reports and other feedback. Thank you, everyone. </para> + +<para +>Documentation copyright 2001-2003 Jason Harris and the KStars Team <email +>kstars@30doradus.org</email +> </para> + +<para +>Andrew Coles<email +>andrew_coles@yahoo.co.uk</email +></para +> +&underFDL; &underGPL; </chapter> diff --git a/tde-i18n-en_GB/docs/kdeedu/kstars/csphere.docbook b/tde-i18n-en_GB/docs/kdeedu/kstars/csphere.docbook new file mode 100644 index 00000000000..9237efa55e7 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kstars/csphere.docbook @@ -0,0 +1,28 @@ +<sect1 id="ai-csphere"> +<sect1info> +<author +><firstname +>Jason</firstname +> <surname +>Harris</surname +> </author> +</sect1info> +<title +>The Celestial Sphere</title> +<indexterm +><primary +>Celestial Sphere</primary> +<seealso +>Celestial Coordinate Systems</seealso> +</indexterm> +<para +>The celestial sphere is an imaginary sphere of gigantic radius, centred on the Earth. All objects which can be seen in the sky can be thought of as lying on the surface of this sphere. </para +><para +>Of course, we know that the objects in the sky are not on the surface of a sphere centred on the Earth, so why bother with such a construct? Everything we see in the sky is so very far away, that their distances are impossible to gauge just by looking at them. Since their distances are indeterminate, you only need to know the <emphasis +>direction</emphasis +> toward the object to locate it in the sky. In this sense, the celestial sphere model is a very practical model for mapping the sky. </para +><para +>The directions toward various objects in the sky can be quantified by constructing a <link linkend="ai-skycoords" +>Celestial Coordinate System</link +>. </para> +</sect1> diff --git a/tde-i18n-en_GB/docs/kdeedu/kstars/darkmatter.docbook b/tde-i18n-en_GB/docs/kdeedu/kstars/darkmatter.docbook new file mode 100644 index 00000000000..688ca6eb6a1 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kstars/darkmatter.docbook @@ -0,0 +1,86 @@ +<sect1 id="ai-darkmatter"> + +<sect1info> +<author +><firstname +>Jasem</firstname +> <surname +>Mutlaq</surname +> <affiliation +><address +> <email +>mutlaqja@ku.edu</email> +</address +></affiliation> +</author> +</sect1info> + +<title +>Dark Matter</title> +<indexterm +><primary +>Dark Matter</primary> +</indexterm> + +<para +>Scientists are now quite comfortable with the idea that 90% of the mass is the universe is in a form of matter that cannot be seen. </para> + +<para +>Despite comprehensive maps of the nearby universe that cover the spectrum from radio to gamma rays, we are only able to account of 10% of the mass that must be out there. As Bruce H. Margon, an astronomer at the University of Washington, told the New York Times in 2001: <citation +>It's a fairly embarrassing situation to admit that we can't find 90 percent of the universe</citation +>. </para> + +<para +>The term given this <quote +>missing mass</quote +> is <firstterm +>Dark Matter</firstterm +>, and those two words pretty well sum up everything we know about it at this point. We know there is <quote +>Matter</quote +>, because we can see the effects of its gravitational influence. However, the matter emits no detectable electromagnetic radiation at all, hence it is <quote +>Dark</quote +>. There exist several theories to account for the missing mass ranging from exotic subatomic particles, to a population of isolated black holes, to less exotic brown and white dwarfs. The term <quote +>missing mass</quote +> might be misleading, since the mass itself is not missing, just its light. But what is exactly dark matter and how do we really know it exists, if we cannot see it? </para> + +<para +>The story began in 1933 when Astronomer Fritz Zwicky was studying the motions of distant and massive clusters of galaxies, specifically the Coma cluster and the Virgo cluster. Zwicky estimated the mass of each galaxy in the cluster based on their luminosity, and added up all of the galaxy masses to get a total cluster mass. He then made a second, independent estimate of the cluster mass, based on measuring the spread in velocities of the individual galaxies in the cluster. To his suprise, this second <firstterm +>dynamical mass</firstterm +> estimate was <emphasis +>400 times</emphasis +> larger than the estimate based on the galaxy light. </para> + +<para +>Although the evidence was strong at Zwicky's time, it was not until the 1970s that scientists began to explore this discrepancy comprehensively. It was at this time that the existence of Dark Matter began to be taken seriously. The existence of such matter would not only resolve the mass deficit in galaxy clusters; it would also have far more reaching consequences for the evolution and fate of the universe itself. </para> + +<para +>Another phenomenon that suggested the need for dark matter is the rotational curves of <firstterm +>Spiral Galaxies</firstterm +>. Spiral Galaxies contain a large population of stars that orbit the Galactic centre on nearly circular orbits, much like planets orbit a star. Like planetary orbits, stars with larger galactic orbits are expected to have slower orbital speeds (this is just a statement of Kepler's 3rd Law). Actually, Kepler's 3rd Law only applies to stars near the perimeter of a Spiral Galaxy, because it assumes the mass enclosed by the orbit to be constant. </para> + +<para +>However, astronomers have made observations of the orbital speeds of stars in the outer parts of a large number of spiral galaxies, and none of them follow Kepler's 3rd Law as expected. Instead of falling off at larger radii, the orbital speeds remain remarkably constant. The implication is that the mass enclosed by larger-radius orbits increases, even for stars that are apparently near the edge of the galaxy. While they are near the edge of the luminous part of the galaxy, the galaxy has a mass profile that apparently continues well beyond the regions occupied by stars. </para> + +<para +>Here is another way to think about it: Consider the stars near the perimeter of a spiral galaxy, with typical observed orbital velocities of 200 kilometers per second. If the galaxy consisted of only the matter that we can see, these stars would very quickly fly off from the galaxy, because their orbital speeds are four times larger than the galaxy's escape velocity. Since galaxies are not seen to be spinning apart, there must be mass in the galaxy that we are not accounting for when we add up all the parts we can see. </para> + +<para +>Several theories have surfaced in literature to account for the missing mass such as <acronym +>WIMP</acronym +>s (Weakly Interacting Massive Particles), <acronym +>MACHO</acronym +>s (MAssive Compact Halo Objects), primordial black holes, massive neutrinos, and others; each with their pros and cons. No single theory has yet been accepted by the astronomical community, because we so far lack the means to conclusively test one theory against the other. </para> + +<tip> +<para +>You can see the galaxy clusters that Professor Zwicky studied to discover Dark Matter. Use the &kstars; Find Object Window (<keycombo action="simul" +>&Ctrl;<keycap +>F</keycap +></keycombo +>) to centre on <quote +>M 87</quote +> to find the Virgo Cluster, and on <quote +>NGC 4884</quote +> to find the Coma Cluster. You may have to zoom in to see the galaxies. Note that the Virgo Cluster appears to be much larger on the sky. In reality, Coma is the larger cluster; it only appears smaller because it is further away. </para> +</tip> +</sect1> diff --git a/tde-i18n-en_GB/docs/kdeedu/kstars/dcop.docbook b/tde-i18n-en_GB/docs/kdeedu/kstars/dcop.docbook new file mode 100644 index 00000000000..ffae09c3af5 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kstars/dcop.docbook @@ -0,0 +1,248 @@ +<chapter id="dcop"> +<title +>Scripting KStars: The DCOP Interface</title> +<para +>One of the goals of &kstars; is to provide the ability to playback complicated behaviours from a script. This will allow you to create <quote +>virtual tours</quote +> of the heavens, and will enable teachers to construct classroom demos to illustrate certain astronomical concepts. It is already possible to write such scripts for &kstars;, although not all of the desired functions have been included. Also, while we will eventually have a GUI-based script builder tool, the scripts must currently be written by hand. This chapter will explain how to write &kstars; scripts. </para> +<para +>The &kde; architecture provides the necessary framework for scriptable applications via the <abbrev +>DCOP</abbrev +> interface. <abbrev +>DCOP</abbrev +> stands for <quote +>Desktop Communication Protocol</quote +>; through <abbrev +>DCOP</abbrev +>, &kde; applications can be controlled by other applications, from a terminal prompt, or through a text script. </para> + +<sect1 id="dcop-interface"> +<title +>DCOP Functions</title> +<para +>The &kstars; <abbrev +>DCOP</abbrev +> Interface includes the following functions: <itemizedlist> +<listitem +><para +><function +> lookTowards( const QString direction )</function +>: Point the display focus in a direction specified by the argument. This can be the name of any object in the sky, or one of the following directional words or abbreviations: zenith (or z), north (n), northeast (ne), east (e), southeast (se), south (s), southwest(sw), west(w), northwest (nw). </para +></listitem> + +<listitem +><para +><function +> setRaDec( double ra, double dec )</function +>: Point the display focus at the specified equatorial coordinates. </para +></listitem> + +<listitem +><para +><function +> setAltAz(double alt, double az)</function +>: Point the display focus at the specified horizontal coordinates. </para +></listitem> + +<listitem +><para +><function +> zoomIn()</function +>: Increase the display's Zoom level. </para +></listitem> + +<listitem +><para +><function +> zoomOut()</function +>: Decrease the display's Zoom level. </para +></listitem> + +<listitem +><para +><function +> defaultZoom()</function +>: Reset the display to Zoom level = 3 (the default). </para +></listitem> + +<listitem +><para +><function +> setLocalTime(int yr, int mth, int day, int hr, int min, int sec)</function +>: Set the simulation clock to the specified date and time. </para +></listitem> + +<listitem +><para +><function +> waitFor( double t )</function +>: Pause for t seconds before continuing with subsequent script commands. </para +></listitem> + +<listitem +><para +><function +> waitForKey( const QString k )</function +>: Halt the script execution until the user presses the specified key. At this point, you cannot specify combination keystrokes (such as <keycombo action="simul" +>&Ctrl;<keycap +>C</keycap +></keycombo +>); just use simple keys. You can type <quote +>space</quote +> to indicate the spacebar. </para +></listitem> + +<listitem +><para +><function +> setTracking( bool track )</function +>: Toggle whether tracking mode is engaged. </para +></listitem> + +<listitem +><para +><function +> changeViewOption( const QString option, const QString value )</function +>: Adjust a view option. There are dozens and dozens of options available; basically everything you can change in the <guilabel +>Configure &kstars; Window</guilabel +> can be changed here as well. The first argument is the name of the option (the names are taken from the <filename +>kstarsrc</filename +> configuration file), and the second argument is the desired value. The argument parser is designed to be robust, so if you accidentally send it bad data it should fail gracefully. </para +></listitem> + +<listitem +><para +><function +> setGeoLocation( const QString city, const QString province, const QString country )</function +>: Change the observing location to the specified city. If no city matching the argument strings is found, then nothing happens. </para +></listitem> + +<listitem +><para +><function +> stop()</function +> [clock]: Halt the simulation clock. </para +></listitem> + +<listitem +><para +><function +> start()</function +> [clock]: Start the simulation clock. </para +></listitem> + +<listitem +><para +><function +> setScale(float s)</function +> [clock]: Set the rate of the simulation clock. s=1.0 corresponds to real time; 2.0 is twice as fast as real-time, etc. </para +></listitem> +</itemizedlist> +</para> +</sect1> + +<sect1 id="dcop-test"> +<title +>Testing the DCOP Functions</title> +<para +>You can try out the DCOP functions very easily using the <application +>kdcop</application +> program. When you run <application +>kdcop</application +>, you will see a tree-list of all running programs; if &kstars; is running it will be listed. Most of the <abbrev +>DCOP</abbrev +> functions are listed under the <quote +>KStarsInterface</quote +> heading, but the clock functions are listed under <quote +>clock</quote +>. Double-click on any function to execute it. If the function requires arguments, a window will open in which you can input the values. </para> +</sect1> + +<sect1 id="dcop-script"> +<title +>Writing a DCOP Script</title> +<para +><abbrev +>DCOP</abbrev +> functions can also be called from the UNIX command line, and these can be encapsulated in a script. We will create an example script that switches to Equatorial coordinates, points the display at the Moon, zooms in a bit, and accelerates the clock to 1 hour per second. After tracking the Moon for 20 seconds, the clock is paused and the display zooms out. You can use this script as a template for making new scripts. I will list the entire script first, and then explain its various parts. </para> +<para> +<programlisting +>#!/bin/bash +#KStars script: Track the Moon! +# +KSTARS=`dcopfind -a 'kstars*'` +MAIN=KStarsInterface +CLOCK=clock#1 +dcop $KSTARS $MAIN changeViewOption UseAltAz false +dcop $KSTARS $MAIN lookTowards Moon +dcop $KSTARS $MAIN defaultZoom +dcop $KSTARS $MAIN zoomIn +dcop $KSTARS $MAIN zoomIn +dcop $KSTARS $MAIN zoomIn +dcop $KSTARS $MAIN zoomIn +dcop $KSTARS $MAIN zoomIn +dcop $KSTARS $CLOCK setScale 3600. +dcop $KSTARS $CLOCK start +dcop $KSTARS $MAIN waitFor 20. +dcop $KSTARS $CLOCK stop +dcop $KSTARS $MAIN defaultZoom +## +</programlisting> +</para> +<para +>Save this script to a file. The filename can be anything you like; I suggest something descriptive like <filename +>trackmoon.kstars</filename +>. Then type the following command to make the script executable: <userinput +><command +>chmod</command +> <option +>a+x</option +> <parameter +>trackmoon.kstars</parameter +> </userinput +>. The script can then be executed at any time by typing <userinput +><command +>./trackmoon.kstars</command +></userinput +> in the folder which contains the script. Note that the script will only work if an instance of &kstars; is already running. You can use the <command +>dcopstart</command +> command in a script to launch a new instance &kstars;. </para> +<para +>Now to the explanation of the script. The top line identifies the file as a <command +>BASH</command +> shell script. The following two lines are <firstterm +>comments</firstterm +> (any line beginning with <quote +>#</quote +> is a comment, and is ignored by the shell). The next three lines define some convenience variables that will be used later. The <varname +>KSTARS</varname +> variable identifies the currently-running &kstars; process, using the <command +>dcopfind</command +> command. <varname +>MAIN</varname +> and <varname +>CLOCK</varname +> identify the two <abbrev +>DCOP</abbrev +> interfaces associated with &kstars;. </para> +<para +>The remainder of the script is the actual list of <abbrev +>DCOP</abbrev +> calls. The first command sets the display to use Equatorial coordinates by setting the <quote +>UseAltAz</quote +> option to <quote +>false</quote +> (again, you can see a list of all options that <quote +>changeViewOption</quote +> can use by examining your <filename +>kstarsrc</filename +> configuration file). The next command centres the display on the Moon, and automatically engages tracking. We then set the default zoom level, and then zoom in five times. Next, the clock's timescale is set to 1 hour per second (3600 seconds is one hour), and the clock is started (in case it was not already running). The next line pauses the script for 20 seconds while we track the Moon as it moves across the sky. Finally, we stop the clock and reset the zoom level to its default setting. </para> +<para +>We hope you enjoy the scripting abilities of KStars. If you create an interesting script, please email it to <email +>kstars@30doradus.org</email +>; we would like to see what you have done, and may post some scripts on our webpage. Also, if you have any ideas for how to improve scripting (or any part of &kstars;), let us know at <email +>kstars-devel@lists.sourceforge.net</email +> or submit a wishlist item to bugzilla. </para> +</sect1> +</chapter> + diff --git a/tde-i18n-en_GB/docs/kdeedu/kstars/details.docbook b/tde-i18n-en_GB/docs/kdeedu/kstars/details.docbook new file mode 100644 index 00000000000..bb45fc9477f --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kstars/details.docbook @@ -0,0 +1,110 @@ +<sect1 id="tool-details"> +<title +>Object Details Window</title> +<indexterm +><primary +>Tools</primary> +<secondary +>Object Details Window</secondary +></indexterm> +<indexterm +><primary +>Objects in the Sky</primary> +<secondary +>Details</secondary +></indexterm> + +<screenshot> +<screeninfo +>The Object Details Window </screeninfo> +<mediaobject> + <imageobject> + <imagedata fileref="detaildialog.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>Object Details Window</phrase> + </textobject> +</mediaobject> +</screenshot> + +<para +>The Object Details Window presents advanced data available about a specific object in the sky. To access this tool, <mousebutton +>right</mousebutton +>-click on any object, and select the <guimenuitem +>Details...</guimenuitem +> item from the popup menu. </para> +<para +>The window is divided into a number of Tabs. In the <guilabel +>General</guilabel +> Tab, we present basic data about the current object. This includes names and catalogue designations, object type, and <link linkend="ai-magnitude" +>magnitude</link +> (brightness). Also shown are the object's Equatorial and Horizontal coordinates, as well as its rise, set and transit times. </para> +<para> +<indexterm +><primary +>Objects in the Sky</primary> +<secondary +>Internet Links</secondary> +<tertiary +>Customising</tertiary +></indexterm> +In the <guilabel +>Links</guilabel +> tab, you can manage the internet links associated with this object. The Image and Information links associated with the object are listed. These are the links that appear in the popup menu when the object is <mousebutton +>right</mousebutton +>-clicked. You can add custom links to the object with the <guibutton +>Add Link...</guibutton +> button. This will open a window in which you fill in the URL and link text for the new link (you can also test the URL in the web browser from this window). Keep in mind that the custom link can easily point to a file on your local disk, so you can use this feature to index your personal astronomical images or observing logs. </para> +<para +>You can also modify or remove any link using the <guibutton +>Edit Link...</guibutton +> and <guibutton +>Remove Link...</guibutton +> buttons. </para> +<para +>The <guilabel +>Advanced</guilabel +> Tab allows you to query professional astronomical databases on the internet for information regarding the current object. To use these databases, simply highlight the desired database in the list, and press the <guibutton +>View</guibutton +> button to see the results of your query in a web browser window. The query is made using the primary name of the object you clicked on to open the Details Dialogue. The following databases are available for querying: <itemizedlist> +<listitem +><para +>High Energy Astrophysical Archive (HEASARC). Here you can retrieve data about the current object from a number of <quote +>High-energy</quote +> observatories, which covers the Ultraviolet, X-ray and Gamma Ray portions of the electromagnetic spectrum.</para +></listitem> +<listitem +><para +>Multimission Archive at Space Telescope (MAST). The Space Telescope Science Institute provides access to the entire collection of images and spectra taken with the Hubble Space Telescope, as well as several other space-based observatories. </para +></listitem> +<listitem +><para +>NASA Astrophysical Data System (ADS). This incredible bibliographic database encompass the entire body of literature published in international peer-review Journals about astronomy and astrophysics. The database is divided into four general subject areas (Astronomy and Astrophysics, Astrophysics Preprints, Instrumentation, and Physics and Geophysics). Each of these has three sub-nodes that query the database in different ways. <quote +>Keyword search</quote +> will return articles which listed the object's name as a keyword. <quote +>Title word search</quote +> will return articles which included the object name in their Title, and the <quote +>Title & Keyword search</quote +> uses both options together. </para +></listitem> +<listitem +><para +>NASA/IPAC Extragalactic Database (NED). NED provides encapsulated data and bibliographic links about extragalactic objects. You should only use NED if your target is extragalactic; &ie; if it is itself a galaxy. </para +></listitem> +<listitem +><para +>Set of Identifications, Measurements, and Bibliography for Astronomical Data (SIMBAD). SIMBAD is similar to NED, except it provides data about all kinds of objects, not just galaxies. </para +></listitem> +<listitem +><para +>SkyView provides images from All-Sky surveys that have been performed in dozens of different parts of the spectrum, from Gamma Rays to the Radio. The &kstars; interface will retrieve an image from any of these surveys, centred on the selected object. </para +></listitem> +</itemizedlist> +</para> +<para +>Finally, in the <guilabel +>Log</guilabel +> Tab, you can type in some text that will remain associated with this object's Details window. You could use this to attach personal observing notes, for example. </para> +</sect1> + diff --git a/tde-i18n-en_GB/docs/kdeedu/kstars/dumpmode.docbook b/tde-i18n-en_GB/docs/kdeedu/kstars/dumpmode.docbook new file mode 100644 index 00000000000..065de625931 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kstars/dumpmode.docbook @@ -0,0 +1,76 @@ +<chapter id="dumpmode"> +<title +>Command-Line mode for Image Generation</title> +<indexterm +><primary +>Image-dump Mode</primary +></indexterm> + +<para +>You can use &kstars; to generate an image of the sky without actually launching the <acronym +>GUI</acronym +> portion of the program. To use this feature, start &kstars; from a command prompt using arguments to specify the filename for the image, as well as the desired image dimensions: <cmdsynopsis +><command +>kstars</command +> <arg choice="plain" +>--dump</arg +> <arg +>--filename <replaceable +>kstars.png</replaceable +></arg +> <arg +>--height <replaceable +>640</replaceable +></arg +> <arg +>--width <replaceable +>480</replaceable +></arg +> <arg +>--script <replaceable +>myscript.kstars</replaceable +></arg +> </cmdsynopsis> +</para> +<para +>If no filename is specified, it generates a file named <filename +>kstars.png</filename +>. It will attempt to generate an image that matches the extension of your filename. The following extensions are recognised: <quote +>png</quote +>, <quote +>jpg</quote +>, <quote +>jpeg</quote +>, <quote +>gif</quote +>, <quote +>pnm</quote +>, and <quote +>bmp</quote +>. If the filename extension is not recognised, it defaults to the <acronym +>PNG</acronym +> image type. </para> +<para +>Likewise, if the image width and height are not specified, they default to 640 and 480, respectively. </para> +<para +>By default, &kstars; will read in the options values stored in your <filename +>$KDEHOME/share/config/kstarsrc</filename +> file to determine where the image will be centred, and how it is rendered. This means you need to run &kstars; in normal GUI mode, and exit the program when it is set up with the desired options for the generated images. This is not very flexible, so we also provide the ability to execute a &kstars; <acronym +>DCOP</acronym +> script to set the scene before generating the image. The filename you specify as the script argument should be a valid &kstars; <acronym +>DCOP</acronym +> script, such as one created with the <link linkend="tool-scriptbuilder" +>Script Builder Tool</link +>. The script can be used to set where the image is pointing, set the geographic location, set the time and date, change the Zoom level and adjust other view options. Some of the <acronym +>DCOP</acronym +> functions make no sense in non-GUI mode (such as <function +>waitForKey()</function +>); if these functions are encountered while parsing the script, they are simply ignored. </para> +<para +>As an alternative to having to execute a &kstars; <acronym +>DCOP</acronym +> script, we will provide an argument to specify an alternate <filename +>kstarsrc</filename +> config file, in a future version of &kstars;. </para> + +</chapter> diff --git a/tde-i18n-en_GB/docs/kdeedu/kstars/ecliptic.docbook b/tde-i18n-en_GB/docs/kdeedu/kstars/ecliptic.docbook new file mode 100644 index 00000000000..1b256948263 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kstars/ecliptic.docbook @@ -0,0 +1,56 @@ +<sect1 id="ai-ecliptic"> +<sect1info> +<author +><firstname +>John</firstname +> <surname +>Cirillo</surname +> </author> +</sect1info> +<title +>The Ecliptic</title> +<indexterm +><primary +>Ecliptic</primary> +<seealso +>Ecliptic Coordinates</seealso> +</indexterm> +<para +>The ecliptic is an imaginary <link linkend="ai-greatcircle" +>Great Circle</link +> on the <link linkend="ai-csphere" +>Celestial Sphere</link +> along which the Sun appears to move over the course of a year. Of course, it is really the Earth's orbit around the Sun causing the change in the Sun's apparent direction. The ecliptic is inclined from the <link linkend="ai-cequator" +>Celestial Equator</link +> by 23.5 degrees. The two points where the Ecliptic crosses the Celestial Equator are known as the <link linkend="ai-equinox" +>Equinoxes</link +>. </para +><para +>Since our solar system is relatively flat, the orbits of the planets are also close to the plane of the ecliptic. In addition, the constellations of the zodiac are located along the ecliptic. This makes the ecliptic a very useful line of reference to anyone attempting to locate the planets or the constellations of the zodiac, since they all literally <quote +>follow the Sun</quote +>. </para +><para +>Because of the 23.5-degree tilt of the Ecliptic, the <firstterm +>Altitude</firstterm +> of the Sun at noon changes over the course of the year, as it follows the path of the Ecliptic across the sky. This causes the seasons. In the Summer, the Sun is high in the sky at noon, and it remains above the <link linkend="ai-horizon" +>Horizon</link +> for more than twelve hours. Whereas, in the winter, the Sun is low in the sky at noon, and remains above the Horizon for less than twelve hours. In addition, sunlight is received at the Earth's surface at a more direct angle in the Summer, which means that a given area at the surface receives more energy per second in the Summer than in Winter. The differences in day duration and in energy received per unit area lead to the differences in temperature we experience in Summer and Winter. </para> +<tip> +<para +>Exercises:</para> +<para +>Make sure your location is set to somewhere that is not very near the equator for these experiments. Open the <guilabel +>Configure &kstars;</guilabel +> window, and switch to Horizontal coordinates, with the Opaque Ground shown. Open the <guilabel +>Set Time</guilabel +> window (<keycombo action="simul" +>&Ctrl;<keycap +>S</keycap +></keycombo +>),and change the Date to sometime in the middle of Summer, and the Time to 12:00 Noon. Back in the Main Window, point toward the Southern Horizon (press <keycap +>S</keycap +>). Note the height of the Sun above the Horizon at Noon in the Summer. Now, change the Date to something in the middle of Winter (but keep the Time at 12:00 Noon). The Sun is now much lower in the Sky. You will also notice that the day durations are different if you open the <guilabel +>What's Up Tonight?</guilabel +> tool for each date. </para> +</tip> +</sect1> diff --git a/tde-i18n-en_GB/docs/kdeedu/kstars/ellipticalgalaxies.docbook b/tde-i18n-en_GB/docs/kdeedu/kstars/ellipticalgalaxies.docbook new file mode 100644 index 00000000000..37bad450a7e --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kstars/ellipticalgalaxies.docbook @@ -0,0 +1,98 @@ +<sect1 id="ai-ellipgal"> +<sect1info> +<author +><firstname +>Jasem</firstname +> <surname +>Mutlaq</surname +> <affiliation +><address +> <email +>mutlaqja@ku.edu</email> +</address +></affiliation> +</author> +</sect1info> + +<title +>Elliptical Galaxies</title> +<indexterm +><primary +>Elliptical Galaxies</primary> +</indexterm> + +<para +>Elliptical galaxies are spheroidal concentrations of billions of stars that resemble Globular Clusters on a grand scale. They have very little internal structure; the density of stars declines smoothly from the concentrated centre to the diffuse edge, and they can have a broad range of ellipticities (or aspect ratios). They typically contain very little interstellar gas and dust, and no young stellar populations (although there are exceptions to these rules). Edwin Hubble referred to Elliptical galaxies as <quote +>early-type</quote +> galaxies, because he thought that they evolved to become Spiral Galaxies (which he called <quote +>late-type</quote +> galaxies). Astronomers actually now believe the opposite is the case (&ie;, that Spiral galaxies can turn into Elliptical galaxies), but Hubble's early- and late-type labels are still used. </para> + +<para +>Once thought to be a simple galaxy type, ellipticals are now known to be quite complex objects. Part of this complexity is due to their amazing history: ellipticals are thought to be the end product of the merger of two Spiral galaxies. You can view a computer simulation MPEG movie of such a merger at <ulink url="http://oposite.stsci.edu/pubinfo/pr/2002/11/vid/v0211d3.mpg" +> this NASA HST webpage</ulink +> (warning: the file is 3.4 MB). </para> + +<para +>Elliptical galaxies span a very wide range of sizes and luminosities, from giant Ellipticals hundreds of thousands of light years across and nearly a trillion times brighter than the sun, to dwarf Ellipticals just a bit brighter than the average globular cluster. They are divided to several morphological classes: </para> + +<variablelist> +<varlistentry> +<term +>cD galaxies:</term> +<listitem +><para +>Immense and bright objects that can measure nearly 1 Megaparsec (3 million light years) across. These titans are only found near the centres of large, dense clusters of galaxies, and are likely the result of many galaxy mergers.</para +></listitem> +</varlistentry> + +<varlistentry> +<term +>Normal Elliptical galaxies</term> +<listitem +><para +>Condensed Object with relatively high central surface brightness. They include the giant ellipticals (gE'e), intermediate-luminosity ellipticals (E's), and compact ellipticals.</para +></listitem> +</varlistentry> + +<varlistentry> +<term +>Dwarf elliptical galaxies (dE's)</term> +<listitem +><para +>This class of galaxies is fundamentally different from normal ellipticals. Their diameters on the order of 1 to 10 kiloparsec with surface brightness that is much lower than normal ellipticals, giving them a much more diffuse appearance. They display the same characteristic gradual decline of star density from a relatively dense core out to a diffuse periphery.</para +></listitem> +</varlistentry> + +<varlistentry> +<term +>Dwarf spheroidal galaxies (dSph's)</term> +<listitem +><para +>Extreme low-luminosity, low surface-brightness and have only been observed in the vicinity of the Milky Way, and possibly other very nearby galaxy groups, such as the Leo group. Their absolute magnitudes are only -8 to -15 mag. The Draco dwarf spheroidal galaxy has an absolute magnitude of -8.6, making it fainter than the average globular cluster in the Milky Way! </para +></listitem> +</varlistentry> + +<varlistentry> +<term +>Blue compact dwarf galaxies (BCD's)</term> +<listitem> +<para +>Small galaxies that are unusually blue. Thehave photometric colors of B-V = 0.0 to 0.30 mag, which is typical for relatively young stars of <firstterm +>spectral type</firstterm +> A. This suggests that BCDs are currently actively forming stars. These systems also have abundant interstellar gas (unlike other Elliptical galaxies). </para +></listitem> +</varlistentry> +</variablelist> + +<tip> +<para +>You can see examples of Elliptical galaxies in &kstars;, using the Find Object window (<keycombo action="simul" +>&Ctrl;<keycap +>F</keycap +></keycombo +>). Search for NGC 4881, which is the Giant cD galaxy in the Coma cluster of galaxies. M 86 is a normal Elliptical galaxy in the Virgo cluster of galaxies. M 32 is a dwarf Elliptical that is a satellite of our neighbour, the Andromeda galaxy (M 31). M 110 is another satellite of M 31 that is a borderline dwarf spheroidal galaxy (<quote +>borderline</quote +> because it is somewhat brighter than most other dwarf spheroidals). </para> +</tip> +</sect1> diff --git a/tde-i18n-en_GB/docs/kdeedu/kstars/equinox.docbook b/tde-i18n-en_GB/docs/kdeedu/kstars/equinox.docbook new file mode 100644 index 00000000000..8b4a0611550 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kstars/equinox.docbook @@ -0,0 +1,44 @@ +<sect1 id="ai-equinox"> +<sect1info> +<author +><firstname +>Jason</firstname +> <surname +>Harris</surname +> </author> +</sect1info> +<title +>The Equinoxes</title> +<indexterm +><primary +>Equinoxes</primary> +<seealso +>Celestial Equator</seealso +> <seealso +>Ecliptic</seealso +> </indexterm> +<para +>Most people know the Vernal and Autumnal Equinoxes as calendar dates, signifying the beginning of the Northern hemisphere's Spring and Autumn, respectively. Did you know that the equinoxes are also positions in the sky? </para +><para +>The <link linkend="ai-cequator" +>Celestial Equator</link +> and the <link linkend="ai-ecliptic" +>Ecliptic</link +> are two <link linkend="ai-greatcircle" +>Great Circles</link +> on the <link linkend="ai-csphere" +>Celestial Sphere</link +>, set at an angle of 23.5 degrees. The two points where they intersect are called the <firstterm +>Equinoxes</firstterm +>. The <firstterm +>Vernal Equinox</firstterm +> has coordinates RA=0.0 hours, Dec=0.0 degrees. The <firstterm +>Autumnal Equinox</firstterm +> has coordinates RA=12.0 hours, Dec=0.0 degrees. </para +><para +>The Equinoxes are important for marking the seasons. Because they are on the <link linkend="ai-ecliptic" +>Ecliptic</link +>, the Sun passes through each equinox every year. When the Sun passes through the Vernal Equinox (usually on March 21st), it crosses the <link linkend="ai-cequator" +>Celestial Equator</link +> from South to North, signifying the end of Winter for the Northern hemisphere. Similarly, whenthe Sun passes through the Autumnal Equinox (usually on September 21st), it crosses the Celestial Equator from North to South, signifying the end of Winter for the Southern hemisphere. </para> +</sect1> diff --git a/tde-i18n-en_GB/docs/kdeedu/kstars/faq.docbook b/tde-i18n-en_GB/docs/kdeedu/kstars/faq.docbook new file mode 100644 index 00000000000..e9c663aec38 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kstars/faq.docbook @@ -0,0 +1,192 @@ +<chapter id="faq"> +<title +>Questions and Answers</title> +&reporting.bugs; &updating.documentation; <qandaset id="faqlist"> + +<qandaentry> +<question> +<para +>What is the &kstars; Icon?</para> +</question> +<answer> +<para +>The <guiicon +>&kstars; Icon</guiicon +> is a sextant, a handheld telescope which was used by navigators on sailing ships back when the stars were important for navigation. By carefully reckoning the positions of the stars, the navigator could get an accurate estimate of the ship's current <link linkend="ai-geocoords" +>longitude and latitude</link +>. </para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>What do the different symbols for deep-sky objects mean?</para> +</question> +<answer> +<para +>The symbol indicates the object type: <itemizedlist> +<listitem +><para +>dotted circle: Open Cluster</para +></listitem> +<listitem +><para +>cross-in-circle: Globular Cluster</para +></listitem> +<listitem +><para +>box: Gaseous Nebula</para +></listitem> +<listitem +><para +>diamond: Supernova Remnant</para +></listitem> +<listitem +><para +>circle with outer lines: Planetary Nebula</para +></listitem> +<listitem +><para +>ellipse: Galaxy</para +></listitem> +</itemizedlist> +</para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>What do the different colours of Deep-sky objects mean?</para> +</question> +<answer> +<para +>Generally, the different colours indicate to which catalogue the object belongs (Messier, NGC or IC). However, some objects have a different colour which indicates that there are extra images available in the <link linkend="popup-menu" +>popup menu</link +> (the default <quote +>extras</quote +> colour is red). </para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>Why are there so many more U.S. cities than in other countries? Is it a conspiracy? </para> +</question> +<answer> +<para +>It may be a conspiracy, but &kstars; is not involved! We were unable to find a single longitude/latitude database that covers the globe equitably. We are currently working on adding many more non-U.S. cities to the database. We have already received city lists from users in Norway, Italy and Korea. If you can contribute to this effort, please let us know. </para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>Why can I not display the ground when using Equatorial Coordinates</para> +</question> +<answer> +<para +>The short answer is, this is a temporary limitation. There is a problem when constructing the filled polygon that represents the ground when in Equatorial mode. However, it does not make too much sense to draw the ground in equatorial coordinates, which is why this fix has been given a low priority. </para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>Why do some objects disappear when I am scrolling the display? </para> +</question> +<answer> +<para +>When the display is in motion, &kstars; must recompute the screen coordinates of every object in its database, which involves some pretty heavy trigonometry. When scrolling the display (either with the arrow keys or by dragging with the mouse), the display may become slow and jerky, because the computer is having trouble keeping up. By excluding many of the objects, the computational load is greatly reduced, which allows for smoother scrolling. You can turn off this feature in the <guilabel +>Configure &kstars;</guilabel +> window, and you can also configure which objects get hidden. </para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>I do not understand all the terms used in &kstars;. Where can I learn more about the astronomy behind the program?</para> +</question> +<answer> +<para +>The &kstars; Handbook includes the <link linkend="astroinfo" +>AstroInfo Project</link +>; a series of short, hyperlinked articles about astronomical topics that can be explored and illustrated with &kstars;. AstroInfo is a community effort, like GNUpedia or Everything2. If you'd like to contribute to AstroInfo, please join our mailing list: <email +>kstars-info@lists.sourceforge.net</email +>. </para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>How accurate/precise is &kstars;?</para> +</question> +<answer> +<para +>&kstars; is pretty accurate, but it is not (yet) as precise as it can possibly be. The problem with high-precision calculations is that you start having to deal with a large number of complicating factors. If you are not a professional astronomer, you will probably never have a problem with its accuracy or precision. </para> +<para +>Here is a list of some of the complicating factors which limit the program's precision: <itemizedlist +> <listitem> +<para +>Planet positions are only accurate for dates within 4000 years or so of the current epoch. The planet positions are predicted using a Fourier-like analysis of their orbits, as observed over the past few centuries. We learnt in school that planets follow simple elliptical orbits around the Sun, but this is not strictly true. It would be true only if there was only one planet in the Solar system, and if the Sun and the planet were both point masses. As it is, the planets are constantly tugging on each other, perturbing the orbits slightly, and tidal effects also induce precessional wobbling. In fact, recent analysis suggests that the planets' orbits may not even be stable in the long term (i.e., millions or billions of years). As a rule of thumb, you can expect the position of a planet to be accurate to a few arcseconds between the dates -2000 and 6000. </para +><para +>Pluto is the exception to this; its position is perhaps ten times less precise than the positions of the other planets. Still, for dates near the present epoch, its position can be trusted to about an arcsecond. </para +><para +>The moon's position is the most difficult to predict to high precision. This is because its motion is quite perturbed by the Earth. Also, since it is so nearby, even minute effects that would be undetectable in more distant bodies are easily apparent in the moon. </para +><para +>The objects with the worst long-term precision in the program are the comets and asteroids. We use a very simplistic orbital model for the minor planets that does not include third-body perturbations. Therefore, their positions can only be trusted for dates near the present epoch. Even for the present epoch, one can expect positional errors among the minor planets of order 10 arcseconds or more. </para> +</listitem> +</itemizedlist> +</para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>Why do I have to download an improved NGC/IC catalogue and Messier object images? Why not just include them as part of the &kstars; distribution?</para> +</question> +<answer> +<para +>The author of the downloadable NGC/IC catalogue has released it with the restriction that it may not be used commercially. For most &kstars; users, this is not a problem. However, it is technically against the &kstars; license (the <acronym +>GPL</acronym +>) to restrict usage in this way. We removed the Messier object images from the standard distribution for two reasons: to simply reduce the size of &kstars;, and also because of similar licensing concerns with a couple of the images. The inline images are significantly compressed to a very low quality from their original form, so I doubt there is a real copyright concern, but I did obtain explicit permission from the images' authors to use the few images for which there was any question about it (see <filename +>README.images</filename +>). Still, just to be absolutely safe, I removed them from the standard distribution, and marked the download archive as being "free for non-commercial use". </para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>I am really enjoying the beautiful images I have downloaded through &kstars;! I would like to share them with the world; can I publish a calendar featuring these images (or are there any usage restrictions on the images)?</para> +</question> +<answer> +<para +>It depends on the image, but many of the images restrict against commercial usage. The Image Viewer's statusbar will usually contain information about the image's copyright holder, and what usage restrictions apply. As a rule of thumb: anything published by NASA is in the public domain (including all HST images). For everything else, you can pretty safely assume that the images may not be used commercially without permission. When in doubt, contact the image's copyright holder directly. </para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>Can I help contribute to future versions of &kstars;?</para> +</question> +<answer> +<para +>Yes, definitely! Introduce yourself on our mailing list: <email +>kstars-devel@kde.org</email +>. If you want to help with the coding, download the latest <ulink url="http://edu.kde.org/kstars/cvs.html" +>CVS</ulink +> version of the code and dive right in. There are several README files in the distribution that explain some of the code's subsystems. If you need ideas of what to work on, see the TODO file. You can submit patches to kstars-devel, and feel free to post any questions you have about the code there as well. </para +><para +>If you are not into coding, we can still use your help with i18n, docs, AstroInfo articles, URL links, bug reports and feature requests. </para> +</answer> +</qandaentry> + +</qandaset> +</chapter> diff --git a/tde-i18n-en_GB/docs/kdeedu/kstars/flux.docbook b/tde-i18n-en_GB/docs/kdeedu/kstars/flux.docbook new file mode 100644 index 00000000000..a59d1e7210b --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kstars/flux.docbook @@ -0,0 +1,77 @@ +<sect1 id="ai-flux"> + +<sect1info> + +<author +><firstname +>Jasem</firstname +> <surname +>Mutlaq</surname +> <affiliation +><address +> <email +>mutlaqja@ku.edu</email> +</address +></affiliation> +</author> +</sect1info> + +<title +>Flux</title> +<indexterm +><primary +>Flux</primary> +<seealso +>Luminosity</seealso> +</indexterm> + +<para +>The <firstterm +>flux</firstterm +> is the amount of energy that passes through a unit area each second. </para> + +<para +>Astronomers use flux to denote the apparent brightness of a celestial body. The apparent brightness is defined as the the amount of light received from a star above the earth atmosphere passing through a unit area each second. Therefore, the apparent brightness is simply the flux we receive from a star. </para> + +<para +>The flux measures the <emphasis +>rate of flow</emphasis +> of energy that passes through each cm^2 (or any unit area) of an object's surface each second. The detected flux depends on the distance from the source that radiates the energy. This is because the energy has to spread over a volume of space before it reaches us. Let us assume that we have an imaginary balloon that encloses a star. Each dot on the balloon represents a unit of energy emitted from the star. Initially, the dots in an area of one cm^2 are in close proximity to each other and the flux (energy emitted per square centimetre per second) is high. After a distance d, the volume and surface area of the balloon increased causing the dots to <emphasis +>spread away</emphasis +> from each. Consequently, the number of dots (or energy) enclosed in one cm^2 has decreased as illustrated in Figure 1. </para> + +<para> +<mediaobject> +<imageobject> +<imagedata fileref="flux.png" format="PNG"/> +</imageobject> +<caption +><para +><phrase +>Figure 1</phrase +></para +></caption> +</mediaobject> +</para> + +<para +>The flux is inversely proportional to distance by a simple r^2 relation. Therefore, if the distance is doubled, we receive 1/2^2 or 1/4th of the original flux. From a fundamental standpoint, the flux is the <link linkend="ai-luminosity" +>luminosity</link +> per unit area: <mediaobject +> <imageobject> +<imagedata fileref="flux1.png" format="PNG"/> +</imageobject> +</mediaobject> +</para> + +<para +>where (4 * PI * R^2) is the surface area of a sphere (or a balloon!) with a radius R. Flux is measured in Watts/m^2/s or as commonly used by astronomers: Ergs/cm^2/s. For example, the luminosity of the sun is L = 3.90 * 10^26 W. That is, in one second the sun radiates 3.90 * 10^26 joules of energy into space. Thus, the flux we receive passing through one square centimetre from the sun at a distance of one AU (1.496 * 10^13 cm) is: </para> + +<para> +<mediaobject> +<imageobject> +<imagedata fileref="flux2.png" format="PNG"/> +</imageobject> +</mediaobject> +</para> +</sect1> diff --git a/tde-i18n-en_GB/docs/kdeedu/kstars/geocoords.docbook b/tde-i18n-en_GB/docs/kdeedu/kstars/geocoords.docbook new file mode 100644 index 00000000000..5f8d87bf8a7 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kstars/geocoords.docbook @@ -0,0 +1,66 @@ +<sect1 id="ai-geocoords"> +<sect1info> +<author +><firstname +>Jason</firstname +> <surname +>Harris</surname +> </author> +</sect1info> +<title +>Geographic Coordinates</title> +<indexterm +><primary +>Geographic Coordinate System</primary +></indexterm> +<indexterm +><primary +>Longitude</primary +><see +>Geographic Coordinate System</see +></indexterm> +<indexterm +><primary +>Latitude</primary +><see +>Geographic Coordinate System</see +></indexterm> +<para +>Locations on Earth can be specified using a spherical coordinate system. The geographic (<quote +>earth-mapping</quote +>) coordinate system is aligned with the spin axis of the Earth. It defines two angles measured from the centre of the Earth. One angle, called the <firstterm +>Latitude</firstterm +>, measures the angle between any point and the Equator. The other angle, called the <firstterm +>Longitude</firstterm +>, measures the angle <emphasis +>along</emphasis +> the Equator from an arbitrary point on the Earth (Greenwich, England is the accepted zero-longitude point in most modern societies). </para +><para +>By combining these two angles, any location on Earth can be specified. For example, Baltimore, Maryland (USA) has a latitude of 39.3 degrees North, and a longitude of 76.6 degrees West. So, a vector drawn from the centre of the Earth to a point 39.3 degrees above the Equator and 76.6 degrees west of Greenwich, England will pass through Baltimore. </para +><para +>The Equator is obviously an important part of this coordinate system; it represents the <emphasis +>zeropoint</emphasis +> of the latitude angle, and the halfway point between the poles. The Equator is the <firstterm +>Fundamental Plane</firstterm +> of the geographic coordinate system. <link linkend="ai-skycoords" +>All Spherical Coordinate Systems</link +> define such a Fundamental Plane. </para +><para +>Lines of constant Latitude are called <firstterm +>Parallels</firstterm +>. They trace circles on the surface of the Earth, but the only parallel that is a <link linkend="ai-greatcircle" +>Great Circle</link +> is the Equator (Latitude=0 degrees). Lines of constant Longitude are called <firstterm +>Meridians</firstterm +>. The Meridian passing through Greenwich is the <firstterm +>Prime Meridian</firstterm +> (longitude=0 degrees). Unlike Parallels, all Meridians are great circles, and Meridians are not parallel: they intersect at the north and south poles. </para> +<tip> +<para +>Exercise:</para> +<para +>What is the longitude of the North Pole? Its latitude is 90 degrees North. </para> +<para +>This is a trick question. The Longitude is meaningless at the north pole (and the south pole too). It has all longitudes at the same time. </para> +</tip> +</sect1> diff --git a/tde-i18n-en_GB/docs/kdeedu/kstars/greatcircle.docbook b/tde-i18n-en_GB/docs/kdeedu/kstars/greatcircle.docbook new file mode 100644 index 00000000000..5d6783ddc24 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kstars/greatcircle.docbook @@ -0,0 +1,32 @@ +<sect1 id="ai-greatcircle"> +<sect1info> +<author +><firstname +>Jason</firstname +> <surname +>Harris</surname +> </author> +</sect1info> +<title +>Great Circles</title> +<indexterm +><primary +>Great Circles</primary> +<seealso +>Celestial Sphere</seealso> +</indexterm> +<para +>Consider a sphere, such as the Earth, or the <link linkend="ai-csphere" +>Celestial Sphere</link +>. The intersection of any plane with the sphere will result in a circle on the surface of the sphere. If the plane happens to contain the centre of the sphere, the intersection circle is a <firstterm +>Great Circle</firstterm +>. Great circles are the largest circles that can be drawn on a sphere. Also, the shortest path between any two points on a sphere is always along a great circle. </para +><para +>Some examples of great circles on the celestial sphere include: the <link linkend="ai-horizon" +>Horizon</link +>, the <link linkend="ai-cequator" +>Celestial Equator</link +>, and the <link linkend="ai-ecliptic" +>Ecliptic</link +>. </para> +</sect1> diff --git a/tde-i18n-en_GB/docs/kdeedu/kstars/horizon.docbook b/tde-i18n-en_GB/docs/kdeedu/kstars/horizon.docbook new file mode 100644 index 00000000000..03968069fd8 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kstars/horizon.docbook @@ -0,0 +1,30 @@ +<sect1 id="ai-horizon"> +<sect1info> +<author +><firstname +>Jason</firstname +> <surname +>Harris</surname +> </author> +</sect1info> +<title +>The Horizon</title> +<indexterm +><primary +>Horizon</primary> +<seealso +>Horizontal Coordinates</seealso> +</indexterm> +<para +>The <firstterm +>Horizon</firstterm +> is the line that separates Earth from Sky. More precisely, it is the line that divides all of the directions you can possibly look into two categories: those which intersect the Earth, and those which do not. At many locations, the Horizon is obscured by trees, buildings, mountains &etc;. However, if you are on a ship at sea, the Horizon is strikingly apparent. </para +><para +>The horizon is the <firstterm +>Fundamental Plane</firstterm +> of the <link linkend="horizontal" +>Horizontal Coordinate System</link +>. In other words, it is the locus of points which have an <firstterm +>Altitude</firstterm +> of zero degrees. </para> +</sect1> diff --git a/tde-i18n-en_GB/docs/kdeedu/kstars/hourangle.docbook b/tde-i18n-en_GB/docs/kdeedu/kstars/hourangle.docbook new file mode 100644 index 00000000000..19d3e1b1a58 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kstars/hourangle.docbook @@ -0,0 +1,46 @@ +<sect1 id="ai-hourangle"> +<sect1info> +<author +><firstname +>Jason</firstname +> <surname +>Harris</surname +> </author> +</sect1info> +<title +>Hour Angle</title> +<indexterm +><primary +>Hour Angle</primary> +<seealso +>Local Meridian</seealso +> <seealso +>Sidereal Time</seealso +> </indexterm> +<para +>As explained in the <link linkend="ai-sidereal" +>Sidereal Time</link +> article, the <firstterm +>Right Ascension</firstterm +> of an object indicates the Sidereal Time at which it will transit across your <link linkend="ai-meridian" +>Local Meridian</link +>. An object's <firstterm +>Hour Angle</firstterm +> is defined as the difference between the current Local Sidereal Time and the Right Ascension of the object: </para +><para +><abbrev +>HA</abbrev +><subscript +>obj</subscript +> = <abbrev +>LST</abbrev +> - <abbrev +>RA</abbrev +><subscript +>obj</subscript +> </para +><para +>Thus, the object's Hour Angle indicates how much Sidereal Time has passed since the object was on the Local Meridian. It is also the angular distance between the object and the meridian, measured in hours (1 hour = 15 degrees). For example, if an object has an hour angle of 2.5 hours, it transited across the Local Meridian 2.5 hours ago, and is currently 37.5 degrees West of the Meridian. Negative Hour Angles indicate the time until the <emphasis +>next</emphasis +> transit across the Local Meridian. Of course, an Hour Angle of zero means the object is currently on the Local Meridian. </para> +</sect1> diff --git a/tde-i18n-en_GB/docs/kdeedu/kstars/index.cache.bz2 b/tde-i18n-en_GB/docs/kdeedu/kstars/index.cache.bz2 Binary files differnew file mode 100644 index 00000000000..8cc3ccb32a8 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kstars/index.cache.bz2 diff --git a/tde-i18n-en_GB/docs/kdeedu/kstars/index.docbook b/tde-i18n-en_GB/docs/kdeedu/kstars/index.docbook new file mode 100644 index 00000000000..67ef9fda045 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kstars/index.docbook @@ -0,0 +1,323 @@ +<?xml version="1.0" ?> +<!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.1.2-Based Variant V1.0//EN" "dtd/kdex.dtd" [ + <!ENTITY kappname "&kstars;"> + <!ENTITY package "kdeedu"> + <!ENTITY astroinfo SYSTEM "astroinfo.docbook"> + <!ENTITY blackbody SYSTEM "blackbody.docbook"> + <!ENTITY calc-angdist SYSTEM "calc-angdist.docbook"> + <!ENTITY calc-apcoords SYSTEM "calc-apcoords.docbook"> + <!ENTITY calc-ecliptic SYSTEM "calc-ecliptic.docbook"> + <!ENTITY calc-eqgal SYSTEM "calc-eqgal.docbook"> + <!ENTITY calc-equinox SYSTEM "calc-equinox.docbook"> + <!ENTITY calc-horiz SYSTEM "calc-horizontal.docbook"> + <!ENTITY calc-planetcoords SYSTEM "calc-planetcoords.docbook"> + <!ENTITY calc-precess SYSTEM "calc-precess.docbook"> + <!ENTITY calc-geodetic SYSTEM "calc-geodetic.docbook"> + <!ENTITY calc-dayduration SYSTEM "calc-dayduration.docbook"> + <!ENTITY calc-julian SYSTEM "calc-julianday.docbook"> + <!ENTITY calc-sidereal SYSTEM "calc-sidereal.docbook"> + <!ENTITY calculator SYSTEM "calculator.docbook"> + <!ENTITY cequator SYSTEM "cequator.docbook"> + <!ENTITY colorandtemp SYSTEM "colorandtemp.docbook"> + <!ENTITY commands SYSTEM "commands.docbook"> + <!ENTITY config SYSTEM "config.docbook"> + <!ENTITY contents SYSTEM "ai-contents.docbook"> + <!ENTITY cpoles SYSTEM "cpoles.docbook"> + <!ENTITY credits SYSTEM "credits.docbook"> + <!ENTITY csphere SYSTEM "csphere.docbook"> + <!ENTITY darkmatter SYSTEM "darkmatter.docbook"> + <!ENTITY dumpmode SYSTEM "dumpmode.docbook"> + <!ENTITY ecliptic SYSTEM "ecliptic.docbook"> + <!ENTITY ellipgal SYSTEM "ellipticalgalaxies.docbook"> + <!ENTITY equinox SYSTEM "equinox.docbook"> + <!ENTITY faq SYSTEM "faq.docbook"> + <!ENTITY flux SYSTEM "flux.docbook"> + <!ENTITY geocoords SYSTEM "geocoords.docbook"> + <!ENTITY greatcircle SYSTEM "greatcircle.docbook"> + <!ENTITY horizon SYSTEM "horizon.docbook"> + <!ENTITY hourangle SYSTEM "hourangle.docbook"> + <!ENTITY indi SYSTEM "indi.docbook"> + <!ENTITY install SYSTEM "install.docbook"> + <!ENTITY julianday SYSTEM "julianday.docbook"> + <!ENTITY leapyear SYSTEM "leapyear.docbook"> + <!ENTITY lightcurves SYSTEM "lightcurves.docbook"> + <!ENTITY luminosity SYSTEM "luminosity.docbook"> + <!ENTITY magnitude SYSTEM "magnitude.docbook"> + <!ENTITY meridian SYSTEM "meridian.docbook"> + <!ENTITY parallax SYSTEM "parallax.docbook"> + <!ENTITY precession SYSTEM "precession.docbook"> + <!ENTITY quicktour SYSTEM "quicktour.docbook"> + <!ENTITY retrograde SYSTEM "retrograde.docbook"> + <!ENTITY sidereal SYSTEM "sidereal.docbook"> + <!ENTITY skycoords SYSTEM "skycoords.docbook"> + <!ENTITY spiralgal SYSTEM "spiralgalaxies.docbook"> + <!ENTITY stars SYSTEM "stars.docbook"> + <!ENTITY timezones SYSTEM "timezones.docbook"> + <!ENTITY tool-aavso SYSTEM "lightcurves.docbook"> + <!ENTITY tool-altvstime SYSTEM "altvstime.docbook"> + <!ENTITY tool-calculator SYSTEM "calculator.docbook"> + <!ENTITY tool-details SYSTEM "details.docbook"> + <!ENTITY tool-whatsup SYSTEM "wut.docbook"> + <!ENTITY tool-scriptbuilder SYSTEM "scriptbuilder.docbook"> + <!ENTITY tool-solarsys SYSTEM "solarsys.docbook"> + <!ENTITY tool-jmoons SYSTEM "jmoons.docbook"> + <!ENTITY tools SYSTEM "tools.docbook"> + <!ENTITY utime SYSTEM "utime.docbook"> + <!ENTITY zenith SYSTEM "zenith.docbook"> + <!ENTITY % addindex "INCLUDE"> + <!ENTITY % British-English "INCLUDE" +><!-- change language only here --> +]> + +<book lang="&language;"> +<title +>The &kstars; Handbook</title> +<bookinfo> + +<authorgroup> +<author +><firstname +>Jason</firstname +> <surname +>Harris</surname +> <affiliation +> <address +><email +>kstars@30doradus.org</email +></address> +</affiliation> +</author> + +<othercredit role="developer" +><firstname +>Heiko</firstname +> <surname +>Evermann</surname +> <affiliation +> <address +><email +>heiko@evermann.de</email +></address> +</affiliation> +<contrib +>Core Developer</contrib> +</othercredit> + +<othercredit role="developer" +><firstname +>Thomas</firstname +> <surname +>Kabelmann</surname +> <affiliation +> <address +><email +>tk78@gmx.de</email +></address> +</affiliation> +<contrib +>Core Developer</contrib> +</othercredit> + +<othercredit role="developer" +><firstname +>Pablo</firstname +> <surname +>de Vicente</surname +> <affiliation +> <address +><email +>pvicentea@wanadoo.es</email +></address> +</affiliation> +<contrib +>Core Developer</contrib> +</othercredit> + +<othercredit role="developer" +><firstname +>Jasem</firstname +> <surname +>Mutlaq</surname +> <affiliation +> <address +><email +>mutlaqja@ikarustech.com</email +></address> +</affiliation> +<contrib +>Core Developer</contrib> +</othercredit> + +<othercredit role="developer" +><firstname +>Carsten</firstname +> <surname +>Niehaus</surname +> <affiliation +> <address +><email +>cniehaus@gmx.de</email +></address> +</affiliation> +<contrib +>Core Developer</contrib> +</othercredit> + +<othercredit role="developer" +><firstname +>Mark</firstname +> <surname +>Holloman</surname +> <affiliation +> <address +><email +>mhh@mindspring.com</email +></address> +</affiliation> +<contrib +>Core Developer</contrib> +</othercredit> + +</authorgroup> + +<othercredit role="translator" +><firstname +>Andrew</firstname +><surname +>Coles</surname +><affiliation +><address +><email +>andrew_coles@yahoo.co.uk</email +></address +></affiliation +><contrib +>Conversion to British English</contrib +></othercredit +> + +<copyright> +<year +>2001</year +><year +>2002</year +><year +>2003</year> +<holder +>Jason Harris and the KStars Team</holder> +</copyright> + +<legalnotice +>&FDLNotice;</legalnotice> + +<date +>2002-10-08</date> +<releaseinfo +>1.0</releaseinfo> + +<abstract> +<para +>&kstars; is a graphical desktop planetarium for KDE. It depicts an accurate simulation of the night sky, including stars, constellations, star clusters, nebulae, galaxies, all planets, the Sun, the Moon, comets and asteroids. You can see the sky as it appears from any location on Earth, on any date. The user interface is highly intuitive and flexible; the display can be panned and zoomed with the mouse, and you can easily identify objects and track their motion across the sky. &kstars; includes many powerful features, yet the interface is clean and simple, and fun to use. </para> +</abstract> + +<keywordset> +<keyword +>KDE</keyword> +<keyword +>kdeedu</keyword> +<keyword +>Astronomy</keyword> +<keyword +>KStars</keyword> +</keywordset> + +</bookinfo> + +<chapter id="introduction"> +<title +>Introduction</title> + +<para +>&kstars; lets you explore the night sky from the comfort of your computer chair. It provides an accurate graphical representation of the night sky for any date, from any location on Earth. The display includes 126,000 stars to 9th magnitude (well below the naked-eye limit), 13,000 deep-sky objects (Messier, NGC, and IC catalogs), all planets, the Sun and Moon, hundreds of comets and asteroids, the Milky Way, 88 constellations, and guide lines such as the <link linkend="ai-cequator" +>celestial equator</link +>, the <link linkend="ai-horizon" +>horizon</link +> and the <link linkend="ai-ecliptic" +>ecliptic</link +>. </para> +<para +>However, &kstars; is more than a simple night-sky simulator. The display provides a compelling interface to a number of tools with which you can learn more about astronomy and the night sky. There is a customised <link linkend="popup-menu" +>popup menu</link +> attached to each displayed object, which displays object-specific information and actions. Hundreds of objects provide links in their popup menus to informative webpages and beautiful images taken by the Hubble Space Telescope and other observatories. </para +><para +>From an object's popup menu, you can open its <link linkend="tool-details" +>Detailed Information Window</link +>, where you can examine positional data about the object, and query a huge treasury of online databases for professional-grade astronomical data and literature references about the object. You can even attach your own internet links, images and text notes, making &kstars; a graphical front-end to your observing logs and your personal astronomical notebook. </para> +<para +>Our <link linkend="tool-calculator" +>Astrocalculator</link +> tool provides direct access to many of the algorithms the program uses behind the scenes, including coordinate converters and time calculators. The <link linkend="tool-aavso" +>AAVSO Lightcurve Generator</link +> tool will download a lightcurve for any of the 6000+ variable stars monitored by the American Association of Variable Star Observers (AAVSO). The lightcurves are generated <quote +>on the fly</quote +> by querying the AAVSO server directly, ensuring that you have the very latest data points. </para> +<para +>You can plan an observing session using our <link linkend="tool-altvstime" +>Altitude vs. Time</link +> tool, which will plot curves representing the Altitude as a function of time for any group of objects. If that is too much detail, we also provide a <link linkend="tool-whatsup" +>What's Up Tonight?</link +> tool that summarises the objects that you will be able to see from your location on any given night. </para> +<para +>&kstars; also provides a <link linkend="tool-solarsys" +>Solar System Viewer</link +>, which shows the current configuration of the major planets in our solar system. There is also a <link linkend="tool-jmoons" +>Jupiter Moons Tool</link +> which shows the positions of Jupiter's four largest moons as a function of time. </para> +<para +>Our primary goal is to make &kstars; an interactive educational tool for learning about astronomy and the night sky. To this end, the &kstars; Handbook includes the <link linkend="astroinfo" +>AstroInfo Project</link +>, a series of short, hyperlinked articles on astronomical topics that can be explored with &kstars;. In addition, &kstars; includes DCOP functions that allow you to <link linkend="tool-scriptbuilder" +>write complex scripts</link +>, making &kstars; a powerful "demo engine" for classroom use or general illustration of astronomical topics. </para> +<para +>You can even control telescopes with &kstars;, using the elegant and powerful <link linkend="indi" +>INDI</link +> hardware interface. &kstars; supports several popular telescopes including Meade's LX200 family and Celestron GPS. Several popular CCD cameras, webcams and computerised focusers are also supported. Simple slew/track commands are integrated directly into the main window's popup menu, and the INDI Control Panel provides full access to all of your telescope's functions. INDI's Client/Server architecture allows for seamless control of any number of <link linkend="indi-kstars-setup" +>local</link +> or <link linkend="indi-remote-control" +>remote</link +> telescopes using a single &kstars; session. </para> +<para +>We are very interested in your feedback; please report bugs or feature requests to the &kstars; development mailing list: <email +>kstars-devel@kde.org</email +>. You can also use the automated bug reporting tool, accessible from the Help menu. </para> +</chapter> + +&quicktour; <!--A Quick Tour of KStars--> +&config; <!--Configuring KStars--> +&commands; <!--Command Reference--> +&astroinfo; <!--AstroInfo Articles--> +&tools; <!--KStars Tools--> +&dumpmode; <!--Command-line image-dump mode--> +&indi; <!-- INDI--> +&faq; <!--Questions and Answers--> +&credits; <!--Credits and License--> +&install; <!--Installation--> + +<index id='doc-index' +></index> +<!-- For DocBook 4.2, remove the above line and use this instead +&documentation.index; +--> +</book> +<!-- +Local Variables: +mode: sgml +sgml-minimize-attributes:nil +sgml-general-insert-case:lower +sgml-indent-step:0 +sgml-indent-data:nil +End: +--> + + diff --git a/tde-i18n-en_GB/docs/kdeedu/kstars/indi.docbook b/tde-i18n-en_GB/docs/kdeedu/kstars/indi.docbook new file mode 100644 index 00000000000..d608b666029 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kstars/indi.docbook @@ -0,0 +1,1050 @@ +<chapter id="indi"> +<title +>Astronomical Device Control with <acronym +>INDI</acronym +></title> +<indexterm +><primary +>INDI Control</primary> +<secondary +>Overview</secondary> +</indexterm> + +<para +>KStars provides an interface to configure and control astronomical instruments via the <acronym +><link linkend="what-is-indi" +>INDI</link +></acronym +> protocol.</para> + +<para +>The <acronym +>INDI</acronym +> protocol supports a variety of astronomical instruments such as CCD cameras and focusers. Currently, KStars supports the following devices:</para> + +<table id="device-table" pgwide="1" frame="all"> +<title +>Supported Telescopes</title> +<tgroup cols="3" colsep="1" rowsep="1"> +<thead> +<row> +<entry +>Telescope</entry> +<entry +>Device driver</entry> +<entry +>Version</entry> +</row> +</thead> +<tbody> +<row> +<entry +>LX200 8"-12" Classic</entry> +<entry +>LX200 Classic</entry> +<entry +>0.5</entry> +</row> +<row> +<entry +>Autostar based telescopes</entry> +<entry +>LX200 Autostar</entry> +<entry +>0.5</entry> +</row> +<row> +<entry +>LX200 GPS 8"-16"</entry> +<entry +>LX200 GPS</entry> +<entry +>0.5</entry> +</row> +<row> +<entry +>LX200 Classic 16"</entry> +<entry +>LX00 16"</entry> +<entry +>0.5</entry> +</row> +<row> +<entry +>NexStar GPS, CGE, AS-GT</entry> +<entry +>Celestron GPS</entry> +<entry +>0.5</entry> +</row> +<row> +<entry +>New GT, NexStar 5i/8i</entry> +<entry +>Celestron GPS</entry> +<entry +>0.5</entry> +</row> +<row> +<entry +>Astro-Physics AP</entry> +<entry +>LX200 Generic</entry> +<entry +>0.1</entry> +</row> +<row> +<entry +>Astro-Electronic FS-2</entry> +<entry +>LX200 Generic</entry> +<entry +>0.1</entry> +</row> +<row> +<entry +>Losmandy Gemini</entry> +<entry +>LX200 Generic</entry> +<entry +>0.1</entry> +</row> +<row> +<entry +>Mel Bartels Controllers</entry> +<entry +>LX200 Generic</entry> +<entry +>0.1</entry> +</row> +</tbody> +</tgroup> +</table> +<para +></para> +<table id="focuser-table" pgwide="1" frame="all"> +<title +>Supported Focusers</title> +<tgroup cols="3" colsep="1" rowsep="1"> +<thead> +<row> +<entry +>Focuser</entry> +<entry +>Device driver</entry> +<entry +>Version</entry> +</row> +</thead> +<tbody> +<row> +<entry +>Meade LX200GPS Microfocuser</entry> +<entry +>LX200 GPS</entry> +<entry +>0.1</entry> +</row> +<row> +<entry +>Meade 1206 Primary Mirror Focuser</entry> +<entry +>LX200 Generic</entry> +<entry +>0.1</entry> +</row> +<row> +<entry +>JMI NGF Series</entry> +<entry +>LX200 Generic</entry> +<entry +>0.1</entry> +</row> +<row> +<entry +>JMI MOTOFOCUS</entry> +<entry +>LX200 Generic</entry> +<entry +>0.1</entry> +</row> +</tbody> +</tgroup> +</table> + +<note> +<title +>Focuser connection</title> +<para +>The focusers must be connected to the focuser port in the LX200 GPS, Autostar or Classic telescopes <emphasis +>only</emphasis +>.</para> +</note> + +<para +></para> +<table id="ccd-table" pgwide="1" frame="all"> +<title +>Supported CCDs</title> +<tgroup cols="3" colsep="1" rowsep="1"> +<thead> +<row> +<entry +>CCD</entry> +<entry +>Device driver</entry> +<entry +>Version</entry> +</row> +</thead> +<tbody> +<row> +<entry +>Finger Lakes Instruments CCDs</entry> +<entry +>fliccd</entry> +<entry +>0.1</entry> +</row> +</tbody> +</tgroup> +</table> + +<para +></para> +<table id="video-table" pgwide="1" frame="all"> +<title +>Supported Webcams</title> +<tgroup cols="3" colsep="1" rowsep="1"> +<thead> +<row> +<entry +>Webcam</entry> +<entry +>Device driver</entry> +<entry +>Version</entry> +</row> +</thead> +<tbody> +<row> +<entry +>Any Video4Linux compatible device</entry> +<entry +>v4ldriver</entry> +<entry +>0.1</entry> +</row> +<row> +<entry +>Philips webcam</entry> +<entry +>v4lphilips</entry> +<entry +>0.1</entry> +</row> +</tbody> +</tgroup> +</table> + +<sect1 id="indi-kstars-setup"> +<title +>INDI Setup</title> +<indexterm +><primary +>INDI</primary> +<secondary +>Setup</secondary> +</indexterm> +<para +>KStars can control local and remote devices seamlessly via the <link linkend="what-is-indi" +>INDI</link +> server/client architecture. INDI devices may be run in three different modes:</para> + +<orderedlist> +<listitem +><para +>Local: The local mode the most common and is used to control local device (&ie; a device attached to your machine).</para +></listitem> +<listitem +><para +>Server: The server mode establishes an INDI server for a particular device and waits for connections from remote clients. You cannot operate server devices, you can only start and shut them down.</para +></listitem> +<listitem +><para +>Client: The client mode is used to connect to remote INDI servers running INDI devices. You can control remote devices seamlessly like local devices.</para +></listitem> +</orderedlist> + +<para +>You can run local device, establish INDI servers, and connect to remote clients from the <guimenuitem +>Device Manager</guimenuitem +> in the <guimenu +>Devices</guimenu +> menu.</para> + +<para +>Here is a screenshot of the <guilabel +>Device Manager</guilabel +> window:</para> + +<screenshot> +<screeninfo +>Running device drivers</screeninfo> +<mediaobject> +<imageobject> +<imagedata fileref="devicemanager.png" format="PNG"/> +</imageobject> +<textobject> +<phrase +>Start device drivers</phrase> +</textobject> +</mediaobject> +</screenshot> + +<para +>You can run devices by browsing the device tree, selecting a specific device, and then clicking on the <guibutton +>Run Service button</guibutton +>. You can select the operation mode, either local or server as defined above.</para> + +<para +>To control remove devices, refer to the <link linkend="indi-remote-control" +>remote device control</link +> section.</para> +</sect1> + +<sect1 id="indi-telescope-setup"> +<title +>Telescope Setup</title> +<indexterm +><primary +>INDI</primary> +<secondary +>Setup</secondary> +</indexterm> + +<para +>Most telescopes are equipped with <hardware +>RS232</hardware +> interface for remote control. Connect the RS232 jack in your telescope to your computer's <hardware +>Serial/USB</hardware +> port. Traditionally, the RS232 connects to the serial port of your computer, but since many new laptops abandoned the serial port in favour of <hardware +>USB/FireWire</hardware +> ports, you might need to obtain a Serial to USB adaptor to use with new laptops.</para> + +<para +>After connecting your telescope to the Serial/USB port, turn your telescope on. It is <emphasis +>highly</emphasis +> recommended that you download and install the latest firmware for your telescope controller.</para> + +<para +>The telescope needs to be aligned before it can be used properly. Align your telescope (one or two stars alignment) as illustrated in your telescope manual.</para> + +<para +>&kstars; needs to verify time and location settings before connecting to the telescope. This insures proper tracking and synchronisation between the telescope and &kstars;. The following steps will enable you to connect to a device that is connected to your computer. To connect and control remote devices, please refer to <link linkend="indi-remote-control" +>remote device control</link +> section.</para> + +<para +>You can use the Telescope Setup Wizard and it will verify all the required information in the process. It can automatically scan ports for attached telescopes. You can run the wizard by selecting <guimenuitem +>Telescope Setup Wizard</guimenuitem +> from the <guimenu +>Devices</guimenu +> menu.</para> + +<para +>Alternatively, you can connect to a local telescope by performing the following steps:</para> + +<orderedlist> +<listitem +><para +>Set your geographical location. Open the <guilabel +>Set Geographic Location</guilabel +> window by selecting <guimenuitem +>Set Geographic Location...</guimenuitem +> from the <guimenu +>Settings</guimenu +> menu, or by pressing the <guiicon +>Globe</guiicon +> icon in the toolbar, or by pressing <keycombo action="simul" +>&Ctrl;<keycap +>g</keycap +></keycombo +>.</para> +</listitem> +<listitem +><para +>Set your local time and date. You can change to any time or date by selecting <guimenuitem +>Set Time...</guimenuitem +> from the <guimenu +>Time</guimenu +> menu, or by pressing the <guiicon +>time</guiicon +> icon in the toolbar. The <guilabel +>Set Time</guilabel +> window uses a standard &kde; Date Picker widget, coupled with three spinboxes for setting the hours, minutes and seconds. If you ever need to reset the clock back to the current time, just select <guimenuitem +>Set Time to Now</guimenuitem +> from the <guimenu +>Time</guimenu +> menu.</para> +</listitem> +<listitem> +<para +>Click on the <guimenu +>Devices</guimenu +> menu and select the <guimenuitem +>Device Manager</guimenuitem +>.</para> +</listitem> +<listitem> +<para +>Under the <guilabel +>Device</guilabel +> column, select your telescope model.</para> +</listitem> +<listitem> +<para +><mousebutton +>Right</mousebutton +>-click on the device and select <guilabel +>Run Service</guilabel +>.</para> +</listitem> +<listitem> +<para +>Click <guibutton +>Ok</guibutton +> to close the Device Manager Dialogue.</para> +</listitem> +</orderedlist> + +<note id="geo-time-note"> +<title +>Frequent Settings</title> +<para +>You do not need to set the geographic location and time every time you connect to a telescope. Only adjust the settings as needed.</para +></note> + +<para +>You are now ready to use the device features, &kstars; conveniently provides two interchangeable GUI interfaces for controlling telescopes:</para> + +<orderedlist> +<title +>Controlling your telescope</title> +<listitem> +<para +><guilabel +>Sky map Control</guilabel +>: For each device you run in the <guilabel +>Device Manager</guilabel +>, a corresponding entry will show up in popup menu that allows you to control the properties of the device. You can issue commands like <command +>Slew, Sync,</command +> and <command +>Track</command +> directly from the sky map. </para> +<para +>Here is a screenshot of the popup menu with an active LX200 Classic device:</para> +<screenshot> +<screeninfo +>Controlling devices from sky map</screeninfo> +<mediaobject> +<imageobject> +<imagedata fileref="skymapdevice.png" format="PNG"/> +</imageobject> +</mediaobject> +</screenshot> +</listitem> + +<listitem> +<para +><guilabel +>INDI Control Panel</guilabel +>: The panel offers the user with all the features supported by a device. </para> + +<para +>The panel is divided into three main sections:</para> +<itemizedlist> +<listitem> +<para +><guilabel +>Device tabs</guilabel +>: Each additional active device occupies a tab in the INDI panel. Multiple devices can run simultaneously without affecting the operation of other devices. </para> +</listitem> +<listitem> +<para +><guilabel +>Property view</guilabel +>: Properties are the key element in INDI architecture. Each device defines a set of properties to communicate with the client. The current position of the telescope is an example of a property. Semantically similar properties are usually contained in logical blocks or groupings. </para> +</listitem> +<listitem> +<para +><guilabel +>Log viewers</guilabel +>: Devices report their status and acknowledge commands by sending INDI messages. Each device has its own log view, and all devices share one generic log viewer. A device usually sends messages to its device driver only, but a device is permitted to send a generic message when appropriate. </para> +</listitem> +</itemizedlist> +<screenshot> +<screeninfo +>INDI Control Panel</screeninfo> +<mediaobject> +<imageobject> +<imagedata fileref="indicontrolpanel.png" format="PNG"/> +</imageobject> +</mediaobject> +</screenshot> +</listitem> +</orderedlist> + +<para +>You are not restricted on using one interface over another as they can be both used simultaneously. Actions from the <guilabel +>Sky map</guilabel +> are automatically reflected in the <guilabel +>INDI Control Panel</guilabel +> and vice versa.</para> + +<para +>To connect to your telescope, you can either select <guimenuitem +>Connect</guimenuitem +> from your device popup menu or alternatively, you can press <guibutton +>Connect</guibutton +> under your device tab in the <guilabel +>INDI Control Panel</guilabel +>.</para> + +<important +><para +>By default, KStars will try to connect to the <constant +>/dev/ttyS0</constant +> port. To change the connection port, select <guilabel +>INDI Control Panel</guilabel +> from the <guimenu +>Devices</guimenu +> menu and change the port under your device tab.</para +></important> + +<para +>&kstars; automatically updates the telescope's longitude, latitude, and time based on current settings in &kstars;. You can enable/disable these updates from <guimenuitem +>Configure INDI</guimenuitem +> dialogue under the <guimenu +>Devices</guimenu +> menu. </para> + +<para +>If &kstars; communicates successfully with the telescope, it will retrieve the current <abbrev +>RA</abbrev +> and <abbrev +>DEC</abbrev +> from the telescope and will display a crosshair on the sky map indicating the telescope position.</para> + +<note id="indi-sync"> +<title +>Synchronising your telescope</title> +<para +>If you aligned your telescope and the last alignment star was, for example, Vega, then the crosshair should be centred around Vega. If the crosshair was off target, then you can <mousebutton +>right</mousebutton +>-click Vega from the sky map and select <command +>Sync</command +> from your telescope menu. This action will instruct the telescope to synchronise its internal coordinates to match those of Vega, and the telescope's crosshair should now be centred around Vega. </para> +</note> + +<para +>That is it: your telescope is ready to explore the heavens.</para> + +<warning> +<title +>WARNING</title> +<para +>Never use the telescope to look at the sun. Looking at the sun might cause irreversible damage to your eyes and as well as your equipment.</para> +</warning> +</sect1> + +<sect1 id="indi-other-setup"> +<title +>CCD and Video-Capture Setup</title> +<indexterm +><primary +>CCD Video Control</primary> +<secondary +>Setup</secondary> +</indexterm> + +<para +>KStars supports Finger Lakes instruments CCDs and any Video4Linux compatible device. Philips webcam extended features are supported as well.</para> +<para +>You can run CCD and Video Capture devices from the <guimenuitem +>Device Manager</guimenuitem +> in the <guimenu +>Devices</guimenu +> menu. Like all INDI devices, some of the device controls will be accessible from the skymap. The device can be controlled fully from the <guimenuitem +>INDI Control Panel.</guimenuitem +></para> + +<para +>The standard format for image capture is FITS. Once an image is captured and downloaded, it will be displayed in the KStars FITSViewer. To capture a sequence of images, use the <guimenuitem +>Capture Image Sequence</guimenuitem +> tool from the <guimenu +>Devices</guimenu +> menu. This tool is inactive until you establish a connection to an image device.</para> +</sect1> + +<sect1 id="indi-concepts"> +<title +>INDI Concepts</title> +<indexterm +><primary +>Telescope Control</primary> +<secondary +>Concepts</secondary> +</indexterm> + +<para +>The INDI control panel offers many device properties not accessible from the sky map. The properties offered differ from one device to another. Nevertheless, all properties share common features that constrains how they are displayed and used:</para> + +<itemizedlist> +<listitem> +<para +>Permission: All properties can either be read-only, write-only, or read and write enabled. An example of a read-write property is the telescope's Right Ascension. You can enter a new Right Ascension and the telescope, based on current settings, will either slew or sync to the new input. Furthermore, when the telescope slews, its Right Ascension gets updated and sent back to the client.</para +><para +></para> +</listitem> +<listitem> +<para +>State: Prefixed to each property is a state indicator (round LED). Each property has a state and an associated colour code:</para> +<table frame="top" +><title +>INDI State colour code</title> +<tgroup cols="3" colsep="1" rowsep="1"> +<thead> +<row> +<entry +>State</entry> +<entry +>Colour</entry> +<entry +>Description</entry> +</row> +</thead> +<tbody> +<row> +<entry +>Idle</entry> +<entry +>Grey</entry> +<entry +>Device is performing no action with respect to this property</entry> +</row> +<row> +<entry +>Ok</entry> +<entry +>Green</entry> +<entry +>Last operation performed on this property was successful and active</entry> +</row> +<row> +<entry +>Busy</entry> +<entry +>Yellow</entry> +<entry +>The property is performing an action</entry> +</row> +<row> +<entry +>Alert</entry> +<entry +>Red</entry> +<entry +>The property is in critical condition and needs immediate attention</entry> + </row> + </tbody> +</tgroup> +</table> +<para +></para> +<para +>The device driver updates the property state in real-time when necessary. For example, if the telescope is in the process of slewing to a target, then the RA/DEC properties will be signalled as <guilabel +>Busy</guilabel +>. When the slew process is completed successfully, the properties will be signalled as <guilabel +>Ok</guilabel +>.</para +><para +></para> +</listitem> +<listitem> +<para +>Context: Numerical properties can accept and process numbers in two formats: decimal and sexagesimal. The sexagesimal format is convenient when expressing time or equatorial/geographical coordinates. You can use any format at your convenience. For example, all the following numbers are equal:</para> +<itemizedlist> +<listitem +><para +>-156.40</para +></listitem> +<listitem +><para +>-156:24:00</para +></listitem> +<listitem +><para +>-156:24</para +><para +></para +></listitem> +</itemizedlist> +</listitem> +<listitem> +<para +>Time: The standard time for all INDI-related communications is Universal Time UTC specified as YYYY-MM-DDTHH:MM:SS in accord with ISO 8601. &kstars; communicates the correct UTC time with device drivers automatically. You can enable/disable automatic time updates from the <guimenuitem +>Configure INDI</guimenuitem +> dialogue under the <guimenu +>Devices</guimenu +> menu. </para> +</listitem> +</itemizedlist> +</sect1> + +<sect1 id="indi-remote-control"> +<title +>Remote Device Control</title> +<indexterm +><primary +>Telescope Control</primary> +<secondary +>Remote Devices</secondary> +</indexterm> + +<para +>KStars provides a simple yet powerful layer for remote device control. A detailed description of the layer is described in the INDI <ulink url="http://www.clearskyinstitute.com/INDI/INDI.pdf" +>white paper</ulink +>.</para> + +<para +>You need to configure both the server and client machines for remote control:</para> + +<orderedlist> +<listitem> +<para +>Server: To prepare a device for remote control, follow the same steps in the <link linkend="indi-kstars-setup" +>local/server</link +> setup. When you start a device service in the <guimenu +>Device Manager</guimenu +>, a port number is displayed under the <guilabel +>Listening port</guilabel +> column. In addition to the port number, you also need the hostname or IP address of your server. </para> +<para +></para> +</listitem> +<listitem> +<para +>Client: Select the <guimenuitem +>Device Manager</guimenuitem +> from the <guimenu +>Device</guimenu +> menu and click on the <guilabel +>Client</guilabel +> tab. You can add, modify, or delete hosts under the <guilabel +>Client</guilabel +> tab. Add a host by clicking on the <guibutton +>Add</guibutton +> button. Enter the hostname/IP address of the server in the <guilabel +>Host</guilabel +> field, and enter the port number obtained from the <emphasis +>server</emphasis +> machine in step 1. </para> +</listitem> +</orderedlist> + +<screenshot> +<screeninfo +>INDI Client</screeninfo> +<mediaobject> +<imageobject> +<imagedata fileref="indiclient.png" format="PNG"/> +</imageobject> +</mediaobject> +</screenshot> + +<para +>After you add a host, right click on the host to <guimenuitem +>Connect</guimenuitem +> or <guimenuitem +>Disconnect</guimenuitem +>. If a connection is established, you can control the telescope from the <guilabel +>Sky map</guilabel +> or <guilabel +>INDI Control Panel</guilabel +> exactly as described in the <link linkend="indi-kstars-setup" +>local/server</link +> section. It is as easy at that. </para> + +<sect2 id="indi-commandline"> +<title +>Running an INDI server from the command line</title> +<para +>While &kstars; allows you to easily deploy an INDI server; you can launch an INDI server from the command line. </para> + +<para +>Since INDI is an independent backend component, you can run an INDI server on a host without KStars. INDI can be compiled separately to run on remote hosts. Furthermore, device drivers log messages to <constant +>stderr</constant +> and that can be helpful in a debugging situation. The syntax for INDI server is as following:</para> + +<para +>$ <command +>indiserver</command +> [options] [<filename +>driver</filename +> ...]</para> + +<para +>Options:</para> +<para +>-p p : alternate IP port, default 7624</para> +<para +>-r n : max restart attempts, default 2</para> +<para +>-v : more verbose to stderr</para> + +<para +>For example, if you want to start an INDI server running an LX200 GPS driver and listening to connections on port 8000, you would run the following command:</para> + +<para +>$ <command +>indiserver</command +> -p 8000 <filename +>lx200gps</filename +></para> +</sect2> + +<sect2 id="indi-secure-remote"> +<title +>Secure Remote Operation</title> + +<para +>Suppose we want to run an indiserver with INDI drivers on a remote host, <constant +>remote_host</constant +>, and connect them to &kstars; running on the local machine.</para> + +<para +>From the local machine log onto the remote host, <constant +>remote_host</constant +>, by typing:</para> + +<para +>$ <command +>ssh</command +> -L <varname +>local_port</varname +>:<constant +>remote_host</constant +>:<varname +>remote_port</varname +></para> + +<para +>This binds the <varname +>local_port</varname +> on the local machine to the <varname +>remote_port</varname +> on the <constant +>remote_host</constant +>. After logging in, run indiserver on the remote host:</para> + +<para +>$ <command +>indiserver</command +> -p <varname +>remote_port</varname +> [<filename +>driver</filename +>...]</para> + +<para +>Back on the local machine, start &kstars; then open the <guimenuitem +>Device Manager</guimenuitem +> and add a host under the <guilabel +>Client</guilabel +> tab. The host should be the local host (usually 127.0.0.1) and the port number should be the <varname +>local_port</varname +> used in the steps above. <mousebutton +>Right</mousebutton +>-click on the host and select <guimenuitem +>Connect</guimenuitem +> from the popup menu. &kstars; will connect to the remote INDI server securely. The host information will be saved for future sessions.</para> +</sect2> +</sect1> + +<sect1 id="indi-faq"> +<title +>INDI Frequently Asked Questions</title> +<indexterm +><primary +>Telescope Control</primary> +<secondary +><acronym +>FAQ</acronym +></secondary> +</indexterm> + +<qandaset defaultlabel="qanda"> +<qandaentry> +<question id="what-is-indi"> +<para +>What is INDI?</para> +</question> +<answer> +<para +><acronym +>INDI</acronym +> is the <ulink url="http://indi.sourceforge.net" +> Instrument-Neutral-Distributed-Interface</ulink +> control protocol developed by <author +><firstname +>Elwood</firstname +><surname +>C. Downey</surname +></author +> of <ulink url="http://www.clearskyinstitute.com/" +>ClearSky Institute</ulink +>. &kstars; employs device drivers that are compatible with the INDI protocol. INDI has many advantages including loose coupling between hardware devices and software drivers. Clients that use the device drivers (like &kstars;) are completely unaware of the device capabilities. In run time, &kstars; communicates with the device drivers and builds a completely dynamical GUI based on services provided by the device. Therefore, new device drivers can be written or updated and KStars can take full advantage of them without any changes on the client side.</para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>Do you plan to support more devices? </para> +</question> +<answer> +<para +>Yes. We plan to support major CCD cameras and focusers and extend support for more telescopes. If you would like INDI to support a particular device, please send an email to <email +>indi-devel@lists.sourceforge.net</email +> </para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>I do not have a serial port, how can I connect to the telescope?</para> +</question> +<answer> +<para +>Many modern laptops do not have a serial port. You will need a Serial To USB adaptor that is supported under Linux. For example, <trademark +>Keyspan</trademark +>'s USA-19QW Serial to USB adaptor is well supported under Linux and had been tested with &kstars;. You need to refer to your adaptor's documentation to find which ports they provide (e.g. <constant +>/dev/ttyUSB0 .... /dev/ttyUSB9</constant +>). </para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>When I try to <guibutton +>Connect</guibutton +>, &kstars; reports that the telescope is not connected to the serial/USB port. What can I do? </para> +</question> +<answer> +<para +>This message is triggered when &kstars; cannot communicate with the telescope. Here are few things you can do:</para> + + <orderedlist> + <listitem> +<para +>Check that you have both reading and writing permission for the port you are trying to connect to.</para> + </listitem> + <listitem> +<para +>Check the connection cable, make sure it is in good condition and test it with other applications.</para> + </listitem> + <listitem> +<para +>Check your telescope power, make sure the power is on and that the telescope is getting enough power.</para> + </listitem> + <listitem> +<para +>Set the correct port in the <guilabel +>INDI Control Panel</guilabel +> under the <guimenu +>Devices</guimenu +> menu. The default port is <constant +>/dev/ttyS0</constant +></para> + </listitem> + <listitem> + <para +>Restart &kstars; and retry again.</para> + </listitem> + </orderedlist> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>&kstars; reports that the telescope is online and ready, but I cannot find the telescope's crosshair, where is it?</para> +</question> +<answer> +<para +>&kstars; retrieves the telescopes RA and DEC coordinates upon connection. If your alignment was performed correctly, then you should see the crosshair around your target in the Sky Map. However, the RA and DEC coordinates provided by the telescope may be incorrect (even below the horizon) and you need to <link linkend="indi-sync" +>Sync</link +> your telescope to your current target.</para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>The telescope is moving erratically or not moving at all. What can I do?</para> +</question> +<answer> +<para +>This behaviour is mostly due to incorrect settings, please verify the following check list:</para> +<orderedlist> +<listitem> +<para +>Is the telescope aligned?</para> +</listitem> +<listitem> +<para +>Is the telescope alignment mode correct? Use <guilabel +>INDI Control Panel</guilabel +> to check and change these settings (<constant +>Alt/Az,Polar, Land</constant +>).</para> +</listitem> +<listitem> +<para +>Are the telescope's time and date settings correct?</para> +</listitem> +<listitem> +<para +>Are the telescope's longitude and latitude settings correct?</para> +</listitem> +<listitem> +<para +>Is the telescope's UTC offset correct?</para> +</listitem> +<listitem> +<para +>Are the telescope's RA and DEC axis locked firmly?</para> +</listitem> +<listitem> +<para +>Is the telescope's N/S switch (when applicable) setup correctly for your hemisphere?</para> +</listitem> +<listitem> +<para +>Is the cable between the telescope and computer in good condition?</para> +</listitem> +</orderedlist> + +<para +>If you think all settings are correct but the telescope still moves erratically or not at all, then please send a report to <email +>kstars-devel@kde.org</email +></para> +</answer> +</qandaentry> +</qandaset> +</sect1> +</chapter> diff --git a/tde-i18n-en_GB/docs/kdeedu/kstars/install.docbook b/tde-i18n-en_GB/docs/kdeedu/kstars/install.docbook new file mode 100644 index 00000000000..4d4fba9599b --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kstars/install.docbook @@ -0,0 +1,138 @@ +<appendix id="installation"> +<title +>Installation</title> + +<sect1 id="getting-kstars"> +<title +>How to obtain &kstars;</title> +<para +>&kstars; is distributed with &kde; as part of the kdeedu "Edutainment" module. </para> +<para +>We also occasionally make an independent release. These independent releases will be available as a gzipped tar archive from the following website: <ulink url="http://prdownloads.sourceforge.net/kstars/" +>http://prdownloads.sourceforge.net/kstars/</ulink +>. </para> +<para +>Independent releases are announced through the <email +>kstars-announce@lists.sourceforge.net</email +> mailing list. Releases are also posted to <ulink url="http://edu.kde.org/kstars" +>the &kstars; home page</ulink +>, <ulink url="http://www.kde-apps.org/content/show.php?content=9862" +>kde-apps.org</ulink +>, and <ulink url="http://freshmeat.net/projects/kstars" +>freshmeat.net</ulink +>. </para> +<para +>&kstars; is been packaged by many Linux/BSD distributions, including Redhat, Suse, and Mandrake. Some distributions package &kstars; as a separate application, some just provide a kdeedu package, which includes &kstars;. </para +><para +>If you would like the latest CVS development version of &kstars;, please follow <ulink url="http://edu.kde.org/kstars/cvs.html" +>these instructions</ulink +>. </para> +</sect1> + +<sect1 id="requirements"> +<title +>Requirements</title> +<para +>In order to successfully run &kstars;, you need &kde; +>=3.2 and &Qt; +>=3.2. </para> +<para +>To compile &kstars;, you will also have to have the following packages installed: <itemizedlist> +<listitem +><para +>kdelibs-devel</para +></listitem> +<listitem +><para +>qt-devel</para +></listitem> +<listitem +><para +>zlib-devel</para +></listitem> +<listitem +><para +>fam-devel</para +></listitem> +<listitem +><para +>png-devel</para +></listitem> +<listitem +><para +>jpeg-devel</para +></listitem> +<listitem +><para +>autoconf ( +>=2.5)</para +></listitem> +</itemizedlist +></para> + +<para +>On my system, &kstars; uses about 60 MB of system memory with the default settings. Most of this usage is due to the loaded object databases. You can dramatically reduce the memory footprint by reducing the faint limit for stars in the Configuration Window, or eliminating catalogs of objects (NGC, IC, comets, asteroids, &etc;). If &kstars; is idling, it uses very little <acronym +>CPU</acronym +>; but it will use as much as you have got when panning or zooming. </para> +</sect1> + +<sect1 id="compilation"> +<title +>Compilation and Installation</title> + +<para +>In order to compile and install &kstars; on your system, type the following in the base folder of the unpacked &kstars; distribution: <screen width="40" +><prompt +>%</prompt +> <userinput +>./configure --prefix=$KDEDIR</userinput> +<prompt +>%</prompt +> <userinput +>make</userinput> +<prompt +>%</prompt +> <userinput +>make install</userinput +> +</screen> +</para +><para +>Please do not forget the prefix argument to configure. If your <envar +>KDEDIR</envar +> variable is not set, set prefix to whatever folder &kde; is installed in: this is usually either <filename class="directory" +>/usr</filename +>, <filename class="directory" +>/opt/kde</filename +>, or <filename class="directory" +>/opt/kde3</filename +>. Also, make sure you do the last step as <systemitem class="username" +>root</systemitem +>. </para +><para +>&kstars; uses <command +>autoconf</command +> and <command +>automake</command +>, so you should not have trouble compiling it. Should you run into problems please report them to the &kstars; mailing list <email +>kstars-devel@kde.org</email +>. </para> +</sect1> + +<sect1 id="configuration"> +<title +>Configuration</title> +<para +>At this point, there are no special configuration options or requirements. If &kstars; complains that there are missing data files, become <systemitem class="username" +>root</systemitem +> and manually copy all files in <filename class="directory" +>kstars/data/</filename +> to <filename class="directory" +>$(KDEDIR)/apps/kstars/</filename +> (If you do not have <systemitem class="username" +>root</systemitem +> privileges, copy them to <filename class="directory" +>~/.kde/share/apps/kstars/.</filename +>) </para> +</sect1> +</appendix> diff --git a/tde-i18n-en_GB/docs/kdeedu/kstars/jmoons.docbook b/tde-i18n-en_GB/docs/kdeedu/kstars/jmoons.docbook new file mode 100644 index 00000000000..63869ce059c --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kstars/jmoons.docbook @@ -0,0 +1,39 @@ +<sect1 id="tool-jmoons"> +<title +>Jupiter Moons Tool</title> +<indexterm +><primary +>Tools</primary> +<secondary +>Jupiter Moons Tool</secondary> +</indexterm> + +<screenshot> +<screeninfo +>The Jupiter Moons Tool </screeninfo> +<mediaobject> + <imageobject> + <imagedata fileref="jmoons.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>Jupiter Moons Tool</phrase> + </textobject> +</mediaobject> +</screenshot> + +<para +>This tool displays the positions of Jupiter's four largest moons (Io, Europa, Ganymede, and Callisto) relative to Jupiter, as a function of time. Time is plotted vertically; the units are days and <quote +>time=0.0</quote +> corresponds to the current simulation time. The horizontal axis displays the angular offset from Jupiter's position, in arcminutes. The offset is measured along the direction of Jupiter's equator. Each moon's position as a function of time traces a sinusoidal path in the plot, as the moon orbits around Jupiter. Each track is assigned a different colour to distinguish it from the others; the name labels at the top of the window indicate the colour used by each moon. </para +><para +>The plot can be manipulated with the keyboard. The time axis can be expanded or compressed using the <keycap +>+</keycap +> and <keycap +>-</keycap +> keys. The time displayed at the center of the window can be changed with the <keycap +>[</keycap +> and <keycap +>]</keycap +> keys. </para> +</sect1> diff --git a/tde-i18n-en_GB/docs/kdeedu/kstars/julianday.docbook b/tde-i18n-en_GB/docs/kdeedu/kstars/julianday.docbook new file mode 100644 index 00000000000..06e2832eb59 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kstars/julianday.docbook @@ -0,0 +1,78 @@ +<sect1 id="ai-julianday"> +<sect1info> +<author +><firstname +>John</firstname +> <surname +>Cirillo</surname +> </author> +</sect1info> +<title +>Julian Day</title> +<indexterm +><primary +>Julian Day</primary> +</indexterm> +<para +>Julian Days are a way of reckoning the current date by a simple count of the number of days that have passed since some remote, arbitrary date. This number of days is called the <firstterm +>Julian Day</firstterm +>, abbreviated as <abbrev +>JD</abbrev +>. The starting point, <abbrev +>JD=0</abbrev +>, is January 1, 4713 BC (or -4712 January 1, since there was no year '0'). Julian Days are very useful because they make it easy to determine the number of days between two events by simply subtracting their Julian Day numbers. Such a calculation is difficult for the standard (Gregorian) calendar, because days are grouped into months, which contain a variable number of days, and there is the added complication of <link linkend="ai-leapyear" +>Leap Years</link +>. </para +><para +>Converting from the standard (Gregorian) calendar to Julian Days and vice versa is best left to a special program written to do this, such as the &kstars; <link linkend="tool-calculator" +>Astrocalculator</link +>. However, for those interested, here is a simple example of a Gregorian to Julian day converter: </para +><para +><abbrev +>JD</abbrev +> = <abbrev +>D</abbrev +> - 32075 + 1461*( <abbrev +>Y</abbrev +> + 4800 + ( <abbrev +>M</abbrev +> - 14 ) / 12 ) / 4 + 367*( <abbrev +>M</abbrev +> - 2 - ( <abbrev +>M</abbrev +> - 14 ) / 12 * 12 ) / 12 - 3*( ( <abbrev +>Y</abbrev +> + 4900 + ( <abbrev +>M</abbrev +> - 14 ) / 12 ) / 100 ) / 4 </para +><para +>where <abbrev +>D</abbrev +> is the day (1-31), <abbrev +>M</abbrev +> is the Month (1-12), and <abbrev +>Y</abbrev +> is the year (1801-2099). Note that this formula only works for dates between 1801 and 2099. More remote dates require a more complicated transformation. </para +><para +>An example Julian Day is: <abbrev +>JD</abbrev +> 2440588, which corresponds to 1 Jan, 1970. </para +><para +>Julian Days can also be used to tell time; the time of day is expressed as a fraction of a full day, with 12:00 noon (not midnight) as the zero point. So, 3:00 pm on 1 Jan 1970 is <abbrev +>JD</abbrev +> 2440588.125 (since 3:00 pm is 3 hours since noon, and 3/24 = 0.125 day). Note that the Julian Day is always determined from <link linkend="ai-utime" +>Universal Time</link +>, not Local Time. </para +><para +>Astronomers use certain Julian Day values as important reference points, called <firstterm +>Epochs</firstterm +>. One widely-used epoch is called J2000; it is the Julian Day for 1 Jan, 2000 at 12:00 noon = <abbrev +>JD</abbrev +> 2451545.0. </para +><para +>Much more information on Julian Days is available on the internet. A good starting point is the <ulink url="http://aa.usno.navy.mil/faq/docs/JD_Formula.html" +>U.S. Naval Observatory</ulink +>. If that site is not available when you read this, try searching for <quote +>Julian Day</quote +> with your favourite search engine. </para> +</sect1> diff --git a/tde-i18n-en_GB/docs/kdeedu/kstars/leapyear.docbook b/tde-i18n-en_GB/docs/kdeedu/kstars/leapyear.docbook new file mode 100644 index 00000000000..cf855c7534b --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kstars/leapyear.docbook @@ -0,0 +1,58 @@ +<sect1 id="ai-leapyear"> +<sect1info> +<author +><firstname +>Jason</firstname +> <surname +>Harris</surname +> </author> +</sect1info> +<title +>Leap Years</title> +<indexterm +><primary +>Leap Years</primary> +</indexterm> +<para +>The Earth has two major components of motion. First, it spins on its rotational axis; a full spin rotation takes one <firstterm +>Day</firstterm +> to complete. Second, it orbits around the Sun; a full orbital rotation takes one <firstterm +>Year</firstterm +> to complete. </para +><para +>There are normally 365 days in one <emphasis +>calendar</emphasis +> year, but it turns out that a <emphasis +>true</emphasis +> year (&ie;, a full orbit of the Earth around the Sun; also called a <firstterm +>tropical year</firstterm +>) is a little bit longer than 365 days. In other words, in the time it takes the Earth to complete one orbital circuit, it completes 365.24219 spin rotations. Do not be too surprised by this; there is no reason to expect the spin and orbital motions of the Earth to be synchronised in any way. However, it does make marking calendar time a bit awkward.... </para +><para +>What would happen if we simply ignored the extra 0.24219 rotation at the end of the year, and simply defined a calendar year to always be 365.0 days long? The calendar is basically a charting of the Earth's progress around the Sun. If we ignore the extra bit at the end of each year, then with every passing year, the calendar date lags a little more behind the true position of Earth around the Sun. In just a few decades, the dates of the solstices and equinoxes will have drifted noticeably. </para +><para +>In fact, it used to be that all years <emphasis +>were</emphasis +> defined to have 365.0 days, and the calendar <quote +>drifted</quote +> away from the true seasons as a result. In the year 46 <abbrev +>BCE</abbrev +>, Julius Caeser established the <firstterm +>Julian Calendar</firstterm +>, which implemented the world's first <firstterm +>leap years</firstterm +>: He decreed that every 4th year would be 366 days long, so that a year was 365.25 days long, on average. This basically solved the calendar drift problem. </para +><para +>However, the problem wasn't completely solved by the Julian calendar, because a tropical year isn't 365.25 days long; it's 365.24219 days long. You still have a calendar drift problem, it just takes many centuries to become noticeable. And so, in 1582, Pope Gregory XIII instituted the <firstterm +>Gregorian calendar</firstterm +>, which was largely the same as the Julian Calendar, with one more trick added for leap years: even Century years (those ending with the digits <quote +>00</quote +>) are only leap years if they are divisible by 400. So, the years 1700, 1800, and 1900 were not leap years (though they would have been under the Julian Calendar), whereas the year 2000 <emphasis +>was</emphasis +> a leap year. This change makes the average length of a year 365.2425 days. So, there is still a tiny calendar drift, but it amounts to an error of only 3 days in 10,000 years. The Gregorian calendar is still used as a standard calendar throughout most of the world. </para> +<note> +<para +>Fun Trivia: When Pope Gregory instituted the Gregorian Calendar, the Julian Calendar had been followed for over 1500 years, and so the calendar date had already drifted by over a week. Pope Gregory re-synchronised the calendar by simply <emphasis +>eliminating</emphasis +> 10 days: in 1582, the day after October 4th was October 15th! </para> +</note> +</sect1> diff --git a/tde-i18n-en_GB/docs/kdeedu/kstars/lightcurves.docbook b/tde-i18n-en_GB/docs/kdeedu/kstars/lightcurves.docbook new file mode 100644 index 00000000000..19b1b5d7a4d --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kstars/lightcurves.docbook @@ -0,0 +1,223 @@ +<sect1 id="tool-aavso"> + +<sect1info> +<author +><firstname +>Aaron</firstname +> <surname +>Price</surname +> <affiliation +><address +> <email +>aavso@aavso.org</email> +</address +></affiliation> +</author> +</sect1info> + +<title +>AAVSO Light Curves</title> +<indexterm +><primary +>Tools</primary> +<secondary +>AAVSO Lightcurve Generator</secondary> +</indexterm> + +<screenshot> +<screeninfo +>The AAVSO Lightcurves Tool </screeninfo> +<mediaobject> + <imageobject> + <imagedata fileref="aavso.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>AAVSO Lightcurves</phrase> + </textobject> +</mediaobject> +</screenshot> + +<sect2 id="aavso-intro"> +<title +>Introduction</title> +<para +>&kstars; can display light curves for variable stars from the observing program of the <ulink url="http://www.aavso.org" +>American Association of Variable Star Observers</ulink +> (<abbrev +>AAVSO</abbrev +>). This program monitors over 6,000 variable stars and consists of 10 million observations going back almost a century. &kstars; downloads the very latest data directly from the <abbrev +>AAVSO</abbrev +> database via the Internet, so a network connection is required to use this tool. </para> +<para +>To use the tool, select a variable star either by <firstterm +>designation</firstterm +> or name in the left panel, and set the start and end dates to be plotted. In the right panel, select the type of data that should be plotted (see below). When you have made you selections, press the <guibutton +>Retrieve Curve</guibutton +> button. &kstars; will automatically connect to the AAVSO server, which will generate the lightcurve plot and send it to your computer for display. A sample lightcurve plot is shown below: </para> + +<screenshot> +<screeninfo +>A Sample Lightcurve </screeninfo> +<mediaobject> + <imageobject> + <imagedata fileref="lightcurve.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>Sample Lightcurve</phrase> + </textobject> +</mediaobject> +</screenshot> + +<para +>Please not these light curves should <emphasis +>NEVER</emphasis +> be used in research, papers, presentations, publications, &etc;. They are only meant to be used as a source of info for &kstars;. They have not been validated and passed the <abbrev +>AAVSO</abbrev +>'s strict quality control measures. We will be glad to give you good raw data simply by requesting it at <ulink url="http://www.aavso.org/adata/onlinedata/" +>http://www.aavso.org/adata/onlinedata/</ulink +>. </para> +<para +>Specific questions about the data in the light curves can be sent to <email +>aavso@aavso.org</email +>. </para> +</sect2> + +<sect2 id="aavso-about"> +<title +>About Variable Stars</title> +<para +><firstterm +>Variable stars</firstterm +> are stars that change in brightness. A <firstterm +>light curve</firstterm +> is a plot of a variable star's brightness over time. By looking at a light curve you can see how the star has behaved in the past and try to predict how it will behave in the future. Astronomers also use this data to model astrophysical processes in the star. This important to help us understand how stars work. </para> +</sect2> + +<sect2 id="aavso-data"> +<title +>The Data</title> + +<para +>Here is a summary of the various types of data available in the light curves: <itemizedlist +> +<listitem +><para +><firstterm +>Visual Observation</firstterm +>: This is an observation of a variable star by an observer with a regular telescope. It means that an observer saw the star at Y brightness on X date and time.</para +></listitem> + +<listitem +><para +><firstterm +>Fainter than</firstterm +>: Sometimes the star is too faint to be seen by the observer. When that happens, the observer reports the faintest star seen in the field. These are called <quote +>fainter thans</quote +> because the variable star was fainter than the brightness reported.</para +></listitem> + +<listitem +><para +><firstterm +>Average</firstterm +>: This is a computed running average of all the data reported. The <firstterm +>bin</firstterm +> number tells the computer how many days to use in each average calculation. This will need to be adjusted based on the frequency of observations. The error bars represent the 1 sigma standard deviation of error.</para +></listitem> + +<listitem +><para +><firstterm +>CCDV</firstterm +>: These are observations reported using a <abbrev +>CCD</abbrev +> with a Johnson <abbrev +>V</abbrev +> filter. <abbrev +>CCDV</abbrev +> observations tend to be more accurate than visual (but not always).</para +></listitem> + +<listitem +><para +><firstterm +>CCDB</firstterm +>: <abbrev +>CCD</abbrev +> observations with a Johnson <abbrev +>B</abbrev +> filter.</para +></listitem> + +<listitem +><para +><firstterm +>CCDI</firstterm +>: <abbrev +>CCD</abbrev +> observations with a Cousins <abbrev +>Ic</abbrev +> filter.</para +></listitem> + +<listitem +><para +><firstterm +>CCDR</firstterm +>: <abbrev +>CCD</abbrev +> observations with a Cousins <abbrev +>R</abbrev +> filter.</para +></listitem> + +<listitem +><para +><firstterm +>Discrepant Data</firstterm +>: This is data that has been flagged by an <abbrev +>AAVSO</abbrev +> staff member as being discrepant following <abbrev +>HQ</abbrev +> rules for data validation. Contact <email +>aavso@aavso.org</email +> for more information.</para +></listitem> + +<listitem +><para +><firstterm +>Dates</firstterm +>: The observational database the light curves are based on is updated every 10 minutes so you can get data in near real-time. Right now light curve data is only available back to 1961, but this will likely be expanded further back in time in the future.</para +></listitem> + +</itemizedlist> +</para> +</sect2> + +<sect2 id="aavso-update"> +<title +>Updating your local copy of Variable Stars</title> +<para +>The <abbrev +>AAVSO</abbrev +> publishes the <ulink url="http://www.aavso.org/valnam.txt" +>full list of variable stars</ulink +> in their monitoring program. This file is updated monthly with newly discovered variable stars. To sync the list that &kstars; uses with the <abbrev +>AAVSO</abbrev +> master list, click on the <guibutton +>Update List</guibutton +> button in the <abbrev +>AAVSO</abbrev +> dialogue. &kstars; will then attempt to connect to the <abbrev +>AAVSO</abbrev +> database and download the latest list. </para> +<note> +<para +>The customised data stream provided by the AAVSO was implemented for &kstars; by Aaron Price. Thank you, Aaron! </para> +</note> +</sect2> +</sect1> + diff --git a/tde-i18n-en_GB/docs/kdeedu/kstars/luminosity.docbook b/tde-i18n-en_GB/docs/kdeedu/kstars/luminosity.docbook new file mode 100644 index 00000000000..fcb119a70ee --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kstars/luminosity.docbook @@ -0,0 +1,44 @@ +<sect1 id="ai-luminosity"> + +<sect1info> + +<author +><firstname +>Jasem</firstname +> <surname +>Mutlaq</surname +> <affiliation +><address +> <email +>mutlaqja@ku.edu</email> +</address +></affiliation> +</author> +</sect1info> + +<title +>Luminosity</title> +<indexterm +><primary +>Luminosity</primary> +<seealso +>Flux</seealso> +</indexterm> + +<para +><firstterm +>Luminosity</firstterm +> is the amount of energy emitted by a star each second. </para> + +<para +>All stars radiate light over a broad range of frequencies in the electromagnetic spectrum from the low energy radio waves up to the highly energetic gamma rays. A star that emits predominately in the ultra-violet region of the spectrum produces a total amount of energy magnitudes larger than that produced in a star that emits principally in the infrared. Therefore, luminosity is a measure of energy emitted by a star over all wavelengths. The relationship between wavelength and energy was quantified by Einstein as E = h * v where v is the frequency, h is the Planck constant, and E is the photon energy in joules. That is, shorter wavelengths (and thus higher frequencies) correspond to higher energies. </para> + +<para +>For example, a wavelength of lambda = 10 meter lies in the radio region of the electromagnetic spectrum and has a frequency of f = c / lambda = 3 * 10^8 m/s / 10 = 30 MHz where c is the speed of light. The energy of this photon is E = h * v = 6.625 * 10^-34 J s * 30 Mhz = 1.988 * 10^-26 joules. On the other hand, visible light has much shorter wavelengths and higher frequencies. A photon that has a wavelength of lambda = 5 * 10^-9 meters (A greenish photon) has an energy E = 3.975 * 10^-17 joules which is over a billion times higher than the energy of a radio photon. Similarly, a photon of red light (wavelength lambda = 700 nm) has less energy than a photon of violet light (wavelength lambda = 400 nm). </para> + +<para +>Luminosity depends both on temperature and surface area. This makes sense because a burning log radiates more energy than a match, even though both have the same temperature. Similarly, an iron rod heated to 2000 degrees emits more energy than when it is heated to only 200 degrees. </para> + +<para +>Luminosity is a very fundamental quantity in Astronomy and Astrophysics. Much of what is learnt about celestial objects comes from analysing their light. This is because the physical processes that occur inside stars gets recorded and transmitted by light. Luminosity is measured in units of energy per second. Astronomers prefer to use Ergs, rather than Watts, when quantifying luminosity. </para> +</sect1> diff --git a/tde-i18n-en_GB/docs/kdeedu/kstars/magnitude.docbook b/tde-i18n-en_GB/docs/kdeedu/kstars/magnitude.docbook new file mode 100644 index 00000000000..11c6ed98044 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kstars/magnitude.docbook @@ -0,0 +1,60 @@ +<sect1 id="ai-magnitude"> +<sect1info> +<author +><firstname +>Girish</firstname +> <surname +>V</surname +> </author> +</sect1info> +<title +>Magnitude Scale</title> +<indexterm +><primary +>Magnitude Scale</primary> +<seealso +>Flux</seealso +> <seealso +>Star Colours and Temperatures</seealso +> </indexterm> +<para +>2500 years ago, the ancient Greek astronomer Hipparchus classified the brightnesses of visible stars in the sky on a scale from 1 to 6. He called the very brightest stars in the sky <quote +>first magnitude</quote +>, and the very faintest stars he could see <quote +>sixth magnitude</quote +>. Amazingly, two and a half millenia later, Hipparchus's classification scheme is still widely used by astronomers, although it has since been modernised and quantified.</para> +<note +><para +>The magnitude scale runs backwards to what you might expect: brighter stars have <emphasis +>smaller</emphasis +> magnitudes than fainter stars). </para> +</note> +<para +>The modern magnitude scale is a quantitative measurement of the <firstterm +>flux</firstterm +> of light coming from a star, with a logarithmic scaling: </para +><para +>m = m_0 - 2.5 log (F / F_0) </para +><para +>If you do not understand the maths, this just says that the magnitude of a given star (m) is different from that of some standard star (m_0) by 2.5 times the logarithm of their flux ratio. The 2.5 *log factor means that if the flux ratio is 100, the difference in magnitudes is 5 mag. So, a 6th magnitude star is 100 times fainter than a 1st magnitude star. The reason Hipparchus's simple classification translates to a relatively complex function is that the human eye responds logarithmically to light. </para +><para +>There are several different magnitude scales in use, each of which serves a different purpose. The most common is the apparent magnitude scale; this is just the measure of how bright stars (and other objects) look to the human eye. The apparent magnitude scale defines the star Vega to have magnitude 0.0, and assigns magnitudes to all other objects using the above equation, and a measure of the flux ratio of each object to Vega. </para +><para +>It is difficult to understand stars using just the apparent magnitudes. Imagine two stars in the sky with the same apparent magnitude, so they appear to be equally bright. You cannot know just by looking if the two have the same <emphasis +>intrinsic</emphasis +> brightness; it is possible that one star is intrinsically brighter, but further away. If we knew the distances to the stars (see the <link linkend="ai-parallax" +>parallax</link +> article), we could account for their distances and assign <firstterm +>Absolute magnitudes</firstterm +> which would reflect their true, intrinsic brightness. The absolute magnitude is defined as the apparent magnitude the star would have if observed from a distance of 10 parsecs (1 parsec is 3.26 light-years, or 3.1 x 10^18 cm). The absolute magnitude (M) can be determined from the apparent magnitude (m) and the distance in parsecs (d) using the formula: </para +><para +>M = m + 5 - 5 * log(d) (note that M=m when d=10). </para +><para +>The modern magnitude scale is no longer based on the human eye; it is based on photographic plates and photoelectric photometers. With telescopes, we can see objects much fainter than Hipparchus could see with his unaided eyes, so the magnitude scale has been extended beyond 6th magnitude. In fact, the Hubble Space Telescope can image stars nearly as faint as 30th magnitude, which is one <emphasis +>trillion</emphasis +> times fainter than Vega. </para +><para +>A final note: the magnitude is usually measured through a colour filter of some kind, and these magnitudes are denoted by a subscript describing the filter (&ie;, m_V is the magnitude through a <quote +>visual</quote +> filter, which is greenish; m_B is the magnitude through a blue filter; m_pg is the photographic plate magnitude &etc;). </para> +</sect1> diff --git a/tde-i18n-en_GB/docs/kdeedu/kstars/meridian.docbook b/tde-i18n-en_GB/docs/kdeedu/kstars/meridian.docbook new file mode 100644 index 00000000000..067464da584 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kstars/meridian.docbook @@ -0,0 +1,41 @@ +<sect1 id="ai-meridian"> +<sect1info> +<author +><firstname +>Jason</firstname +> <surname +>Harris</surname +> </author> +</sect1info> +<title +>The Local Meridian</title> +<indexterm +><primary +>Local Meridian</primary> +<seealso +>Hour Angle</seealso +> <seealso +>Celestial Sphere</seealso +> </indexterm> +<para +>The Local Meridian is an imaginary <link linkend="ai-greatcircle" +>Great Circle</link +> on the <link linkend="ai-csphere" +>Celestial Sphere</link +> that is perpendicular to the local <link linkend="ai-horizon" +>Horizon</link +>. It passes through the North point on the Horizon, through the <link linkend="ai-cpoles" +>Celestial Pole</link +>, up to the <link linkend="ai-zenith" +>Zenith</link +>, and through the South point on the Horizon. </para +><para +>Because it is fixed to the local Horizon, stars will appear to drift past the Local Meridian as the Earth spins. You can use an object's <link linkend="equatorial" +>Right Ascension</link +> and the <link linkend="ai-sidereal" +>Local Sidereal Time</link +> to determine when it will cross your Local Meridian (see <link linkend="ai-hourangle" +>Hour Angle</link +>). </para> +</sect1> + diff --git a/tde-i18n-en_GB/docs/kdeedu/kstars/parallax.docbook b/tde-i18n-en_GB/docs/kdeedu/kstars/parallax.docbook new file mode 100644 index 00000000000..ad19aa1c039 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kstars/parallax.docbook @@ -0,0 +1,62 @@ +<sect1 id="ai-parallax"> +<sect1info> +<author +><firstname +>James</firstname +> <surname +>Lindenschmidt</surname +> </author> +</sect1info> +<title +>Parallax</title> +<indexterm +><primary +>Parallax</primary +></indexterm> +<indexterm +><primary +>Astronomical Unit</primary +><see +>Parallax</see +></indexterm> +<indexterm +><primary +>Parsec</primary +><see +>Parallax</see +></indexterm> + <para +><firstterm +>Parallax</firstterm +> is the apparent change of an observed object's position caused by a shift in the observer's position. As an example, hold your hand in front of you at arm's length, and observe an object on the other side of the room behind your hand. Now tilt your head to your right shoulder, and your hand will appear on the left side of the distant object. Tilt your head to your left shoulder, and your hand will appear to shift to the right side of the distant object. </para> + <para +>Because the Earth is in orbit around the Sun, we observe the sky from a constantly moving position in space. Therefore, we should expect to see an <firstterm +>annual parallax</firstterm +> effect, in which the positions of nearby objects appear to <quote +>wobble</quote +> back and forth in response to our motion around the Sun. This does in fact happen, but the distances to even the nearest stars are so great that you need to make careful observations with a telescope to detect it<footnote +><para +>The ancient Greek astronomers knew about parallax; because they could not observe an annual parallax in the positions of stars, they concluded that the Earth could not be in motion around the Sun. What they did not realise was that the stars are millions of times further away than the Sun, so the parallax effect is impossible to see with the unaided eye.</para +></footnote +>. </para> + <para +>Modern telescopes allow astronomers to use the annual parallax to measure the distance to nearby stars, using triangulation. The astronomer carefully measures the position of the star on two dates, spaced six months apart. The nearer the star is to the Sun, the larger the apparent shift in its position will be between the two dates. </para> + <para +>Over the six-month period, the Earth has moved through half its orbit around the Sun; in this time its position has changed by 2 <firstterm +>Astronomical Units</firstterm +> (abbreviated AU; 1 AU is the distance from the Earth to the Sun, or about 150 million kilometers). This sounds like a really long distance, but even the nearest star to the Sun (alpha Centauri) is about 40 <emphasis +>trillion</emphasis +> kilometers away. Therefore, the annual parallax is very small, typically smaller than one <firstterm +>arcsecond</firstterm +>, which is only 1/3600 of one degree. A convenient distance unit for nearby stars is the <firstterm +>parsec</firstterm +>, which is short for "parallax arcsecond". One parsec is the distance a star would have if its observed parallax angle was one arcsecond. It is equal to 3.26 light-years, or 31 trillion kilometers<footnote +><para +>Astronomers like this unit so much that they now use <quote +>kiloparsecs</quote +> to measure galaxy-scale distances, and <quote +>Megaparsecs</quote +> to measure intergalactic distances, even though these distances are much too large to have an actual, observable parallax. Other methods are required to determine these distances</para +></footnote +>. </para> +</sect1> diff --git a/tde-i18n-en_GB/docs/kdeedu/kstars/precession.docbook b/tde-i18n-en_GB/docs/kdeedu/kstars/precession.docbook new file mode 100644 index 00000000000..354fa09447b --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kstars/precession.docbook @@ -0,0 +1,56 @@ +<sect1 id="ai-precession"> +<sect1info> +<author +><firstname +>Jason</firstname +> <surname +>Harris</surname +> </author> +</sect1info> +<title +>Precession</title> +<indexterm +><primary +>Precession</primary> +</indexterm> +<para +><firstterm +>Precession</firstterm +> is the gradual change in the direction of the Earth's spin axis. The spin axis traces a cone, completing a full circuit in 26,000 years. If you have ever spun a top or a dreidel, the <quote +>wobbling</quote +> rotation of the top as it spins is precession. </para +><para +>Because the direction of the Earth's spin axis changes, so does the location of the <link linkend="ai-cpoles" +>Celestial Poles</link +>. </para +><para +>The reason for the Earth's precession is complicated. The Earth is not a perfect sphere, it is a bit flattened, meaning the <link linkend="ai-greatcircle" +>Great Circle</link +> of the equator is longer than a <quote +>meridonal</quote +> great circle that passes through the poles. Also, the Moon and Sun lie outside the Earth's Equatorial plane. As a result, the gravitational pull of the Moon and Sun on the oblate Earth induces a slight <emphasis +>torque</emphasis +> in addition to a linear force. This torque on the spinning body of the Earth leads to the precessional motion. </para> +<tip> +<para +>Exercise:</para> +<para +>Precession is easiest to see by observing the <link linkend="ai-cpoles" +>Celestial Pole</link +>. To find the pole, first switch to Equatorial Coordinates in the <guilabel +>Configure &kstars;</guilabel +> window, and then hold down the <keycap +>Up arrow</keycap +> key until the display stops scrolling. The declination displayed in the centre of the <guilabel +>Info Panel</guilabel +> should be +90 degrees, and the bright star Polaris should be nearly at the centre of the screen. Try slewing with the left and right arrow keys. Notice that the sky appears to rotate around the Pole. </para +><para +>We will now demonstrate Precession by changing the Date to a very remote year, and observing that the location of the Celestial Pole is no longer near Polaris. Open the <guilabel +>Set Time</guilabel +> window (<keycombo action="simul" +>&Ctrl;<keycap +>S</keycap +></keycombo +>), and set the date to the year 8000 (currently, &kstars; cannot handle dates much more remote than this, but this date is sufficient for our purposes). Notice that the sky display is now centred at a point between the constellations Cygnus and Cepheus. Verify that this is actually the pole by slewing left and right: the sky rotates about this point; in the year 8000, the North celestial pole will no longer be near Polaris. </para> +</tip> +</sect1> diff --git a/tde-i18n-en_GB/docs/kdeedu/kstars/quicktour.docbook b/tde-i18n-en_GB/docs/kdeedu/kstars/quicktour.docbook new file mode 100644 index 00000000000..229195bf066 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kstars/quicktour.docbook @@ -0,0 +1,335 @@ +<chapter id="using-kstars"> +<title +>A Quick Tour of &kstars;</title> + +<para +>This chapter presents a guided tour of &kstars;, introducing many of its important features. </para> + +<screenshot> +<screeninfo +>Here is a screenshot of the &kstars; main window: </screeninfo> +<mediaobject> + <imageobject> + <imagedata fileref="screen1.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>Main Window</phrase> + </textobject> +</mediaobject> +</screenshot> + +<para +>The above screenshot shows a typical view of the KStars program. You can see the sky display centered on Betelgeuse, the brightest star in the constellation Orion. Orion has just risen above the eastern horizon. Stars are displayed with <link linkend="ai-colorandtemp" +>realistic colors</link +> and relative brightnesses. M 42, the Orion Nebula, is visible on the right side of the screen, just above the horizon. If you look closely, you can also see the Sun and the planet Mercury in the upper left. In three corners of the sky display, there are on-screen text labels displaying data on the current time (<quote +>LT: 06:44:58 20 June 2004</quote +>), the current Geographic Location (<quote +>Tucson, Arizona, USA</quote +>), and the current object in the center of the display (<quote +>Focused on: Betelgeuse (alpha Orionis)</quote +>). Above the sky display, there are two toolbars. The main toolbar contains shortcuts for <link linkend="kstars-menus" +>menu functions</link +>, as well as a time-step widget which controls how fast the simulation clock runs. The view toolbar contains buttons that toggle the display of different kinds of objects in the sky. At the bottom of the window, there is a status bar which displays the name of any object you click on, and the <link linkend="ai-skycoords" +>sky coordinates</link +> (both Right Ascension/Declination and Azimuth/Altitude) of the mouse cursor. </para> + +<sect1 id="startwizard"> +<title +>The Setup Wizard</title> +<para> +<indexterm +><primary +>Setup Wizard</primary +></indexterm +> The first time you run KStars, you will be presented with a Setup Wizard, which allows you to easily set your geographic location and download some extra data files. You can press the <guilabel +>Finish</guilabel +> button at any time to exit the Setup Wizard. </para> + +<para +>The first page of the Setup Wizard allows you to choose the starting geographic location, by selecting from the list of the 2500+ known locations on the right side of the window. The list of locations can be filtered to match the text you enter in the <guilabel +>City</guilabel +>, <guilabel +>Province</guilabel +>, and <guilabel +>Country</guilabel +> edit boxes. If your desired location is not present in the list, you can select a nearby city instead for now. Later on, you can add your precise location manually using the <link linkend="setgeo" +>Set Geographic Location tool</link +>. Once you have selected a starting location, press the <guilabel +>Next</guilabel +> button. </para> + +<para +>The second page of the Setup Wizard allows you to download extra data that are not included with the standard distribution of &kstars;. Simply press the <guilabel +>Download Extra Data</guilabel +> button to open the <guilabel +>Get New Stuff</guilabel +> tool. When you are all done, press the <guilabel +>Finish</guilabel +> button in the Setup Wizard to start exploring &kstars;. </para> + +<note> +<para +>The Download Extra Data tool is only available if you have KDE 3.3.x installed. </para> +</note> +</sect1> + +<sect1 id="lookaround"> +<title +>Have a Look Around</title> +<para> +<indexterm +><primary +>Navigation Controls</primary> +<secondary +>Basics</secondary +></indexterm> +Now that we have the time and location set, let us have a look around. You can pan the display using the arrow keys. If you hold down the &Shift; key before panning, the scrolling speed is doubled. The display can also be panned by clicking and dragging with the mouse. Note that while the display is scrolling, not all objects are displayed. This is done to cut down on the <acronym +>CPU</acronym +> load of recomputing object positions, which makes the scrolling smoother (you can configure what gets hidden while scrolling in the <link linkend="config" +>Configure &kstars;</link +> window). There are seven ways to change the magnification (or <firstterm +>Zoom level</firstterm +>) of the display:</para> + +<orderedlist> +<listitem> + <para +>Use the <keycap +>+</keycap +> and <keycap +>-</keycap +> keys</para> +</listitem> +<listitem> + <para +>Press the Zoom In/Zoom Out buttons in the toolbar</para> +</listitem> +<listitem> + <para +>Select <guimenuitem +>Zoom In</guimenuitem +>/<guimenuitem +>Zoom Out</guimenuitem +> from the <guimenu +>View</guimenu +> menu</para> +</listitem> +<listitem> + <para +>Select <guimenuitem +>Zoom to Angular Size...</guimenuitem +> from the <guimenu +>View</guimenu +> menu. This allows you to specify the the field-of-view angle for the display, in degrees.</para> +</listitem> +<listitem> + <para +>Use the scroll wheel on your mouse</para> +</listitem> +<listitem> + <para +>Drag the mouse up and down with the &MMB; pressed.</para> +</listitem> +<listitem> + <para +>Hold down &Ctrl; while dragging the mouse. This will allow you to define a rectangle in the map. When you release the mouse button, the display will zoom to match the rectangle.</para> +</listitem> +</orderedlist> + +<para +>Notice that as you zoom in, you can see fainter stars than at lower zoom settings.</para> + +<para +>Zoom out until you can see a green curve; this represents your local <link linkend="ai-horizon" +>horizon</link +>. If you have not adjusted the default &kstars; configuration, the display will be solid green below the horizon, representing the solid ground of the Earth. There is also a white curve, which represents the <link linkend="ai-cequator" +>celestial equator</link +>, and a tan curve, which represents the <link linkend="ai-ecliptic" +>Ecliptic</link +>, the path that the Sun appears to follow across the sky over the course of a year. The Sun is always found somewhere along the Ecliptic, and the planets are never far from it. </para> +</sect1> + +<sect1 id="skyobjects"> +<title +>Objects in the Sky</title> +<para> +<indexterm +><primary +>Objects in the Sky</primary> +<secondary +>Overview</secondary +></indexterm> +&kstars; displays thousands of celestial objects: stars, planets, comets, asteroids, clusters, nebulae and galaxies. You can interact with displayed objects to perform actions on them or obtain more information about them. Clicking on an object will identify it in the status bar, and simply hovering the mouse cursor on an object will label it temporarily in the map. Double-clicking will re-centre the display on the object and begin tracking it (so that it will remain centred as time passes). <mousebutton +>Right</mousebutton +> clicking an object opens the object's popup menu, which provides more options. </para> + +<sect2 id="popupquick"> +<title +>The Popup Menu</title> +<indexterm +><primary +>Popup Menu</primary +><secondary +>Example</secondary +></indexterm> + +<para +>Here is an example of the <mousebutton +>right</mousebutton +> click popup menu, for the Orion Nebula: </para> + +<screenshot> +<screeninfo +>Popup Menu for M 42</screeninfo> +<mediaobject> + <imageobject> + <imagedata fileref="popup.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>Popup Menu for M 42</phrase> + </textobject> +</mediaobject> +</screenshot> + +<para +>The appearance of the popup menu depends somewhat on the kind of object you <mousebutton +>right</mousebutton +>-click on, but the basic structure is listed below. You can get <link linkend="popup-menu" +>more detailed information about the popup menu</link +>. </para> + +<para +>The top section contains information labels (which are not selectable). The top one to three labels display the object's name(s) and object type. The next three labels show the object's rise, transit and set times. If the rise and set times say "circumpolar", it means that the object is always above the horizon for the present location. </para> +<para +>The middle section contains items for performing actions on the object, such as <guimenuitem +>Center and Track</guimenuitem +>, <guimenuitem +>Angular Distance To...</guimenuitem +> (which enters the Angular Distance Mode, allowing you to measure the angle between objects in the sky), <guimenuitem +>Details...</guimenuitem +> (which opens the object's <link linkend="tool-details" +>Object Details window</link +>), <guimenuitem +>Attach Label</guimenuitem +> and <guimenuitem +>Add/Remove Trail</guimenuitem +> (only available for Solar System bodies). </para> +<para> +<indexterm +><primary +>Objects in the Sky</primary> +<secondary +>Internet Links</secondary> +<seealso +>Popup Menu</seealso +></indexterm> +The bottom section contains links to images and/or informative webpages about the selected object. If you know of an additional &URL; with information or an image of the object, you can add a custom link to the object's popup menu using the <guimenuitem +>Add Link...</guimenuitem +> item. </para> +</sect2> + +<sect2 id="findobjects"> +<title +>Finding Objects</title> +<indexterm +><primary +>Find Object Tool</primary +></indexterm> +<indexterm +><primary +>Objects in the Sky</primary> +<secondary +>Finding by Name</secondary +></indexterm> +<para +>You can search for named objects using the <guilabel +>Find Object</guilabel +> tool, which can be opened by clicking on the <guiicon +>search</guiicon +> icon in the toolbar, by selecting <guimenuitem +>Find Object...</guimenuitem +> from the <guimenu +>Pointing</guimenu +> menu, or by pressing <keycombo action="simul" +>&Ctrl;<keycap +>F</keycap +></keycombo +>. The <guilabel +>Find Object</guilabel +> window is shown below: <screenshot> +<screeninfo +>Find Object Window</screeninfo> +<mediaobject> + <imageobject> + <imagedata fileref="find.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>Find Object Window</phrase> + </textobject> +</mediaobject> +</screenshot> +</para> + +<para +>The window contains a list of all the named objects that &kstars; is aware of. Many of the objects only have a numeric catalogue name (for example, NGC 3077), but some objects have a common name as well (for example, Whirlpool Galaxy). You can filter the list by name and by object type. To filter by name, enter a string in the edit box at the top of the window; the list will then only contain names which start with that string. To filter by type, select a type from the combo box at the bottom of the window. </para +><para +>To centre the display on an object, highlight the desired object in the list, and press <guibutton +>Ok</guibutton +>. Note that if the object is below the horizon, the program will warn you that you may not see anything except the ground (you can make the ground invisible in the <guilabel +>Display Options</guilabel +> window, or by pressing the <guiicon +>Ground</guiicon +> button in the View toolbar). </para> +<para> +<indexterm +><primary +>Objects in the Sky</primary> +<secondary +>Tracking</secondary +></indexterm> +&kstars; will automatically begin tracking on an object whenever one is centred in the display, either by using the <guilabel +>Find Object</guilabel +> window, by double-clicking on it, or by selecting <guimenuitem +>Center and Track</guimenuitem +> from its <mousebutton +>right</mousebutton +>-click popup menu. You can disengage tracking by panning the display, pressing the <guiicon +>Lock</guiicon +> icon in the Main toolbar, or selecting <guimenuitem +>Track Object</guimenuitem +> from the <guimenu +>Pointing</guimenu +> menu. </para> + +<note> +<para> +<indexterm +><primary +>Orbit Trails</primary> +<secondary +>Attached to centred object</secondary> +</indexterm> +When tracking on a Solar System body, &kstars; will automatically attach an <quote +>orbit trail</quote +>, showing the path of the body across the sky. You will likely need to change the clock's timestep to a large value (such as <quote +>1 day</quote +>) to see the trail. </para> +</note> + +<para +>This concludes the tour of &kstars;, although we have only scratched the surface of the available features. &kstars; includes many useful <link linkend="tools" +>astronomy tools</link +>, it can directly <link linkend="indi" +>control your telescope</link +>, and it offers a wide variety of <link linkend="config" +>configuration and customization</link +> options. In addition, this Handbook includes the <link linkend="astroinfo" +>AstroInfo Project</link +>, a series of short, interlinked articles explaining some of the celestial and astrophysical concepts behind &kstars;. </para> + +</sect2> +</sect1> +</chapter> diff --git a/tde-i18n-en_GB/docs/kdeedu/kstars/retrograde.docbook b/tde-i18n-en_GB/docs/kdeedu/kstars/retrograde.docbook new file mode 100644 index 00000000000..b60374831cd --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kstars/retrograde.docbook @@ -0,0 +1,31 @@ +<sect1 id="ai-retrograde"> +<sect1info> +<author +><firstname +>John</firstname +> <surname +>Cirillo</surname +> </author> +</sect1info> +<title +>Retrograde Motion</title> +<indexterm +><primary +>Retrograde Motion</primary> +</indexterm> + +<para +><firstterm +>Retrograde Motion</firstterm +> is the orbital motion of a body in a direction opposite that which is normal to spatial bodies within a given system. </para +><para +>When we observe the sky, we expect most objects to appear to move in a particular direction with the passing of time. The apparent motion of most bodies in the sky is from east to west. However it is possible to observe a body moving west to east, such as an artificial satellite or space shuttle that is orbiting eastward. This orbit is considered Retrograde Motion. </para +><para +>Retrograde Motion is most often used in reference to the motion of the outer planets (Mars, Jupiter, Saturn, and so forth). Though these planets appear to move from east to west on a nightly basis in response to the spin of the Earth, they are actually drifting slowly eastward with respect to the stationary stars, which can be observed by noting the position of these planets for several nights in a row. This motion is normal for these planets, however, and not considered Retrograde Motion. However, since the Earth completes its orbit in a shorter period of time than these outer planets, we occasionally overtake an outer planet, like a faster car on a multiple-lane highway. When this occurs, the planet we are passing will first appear to stop its eastward drift, and it will then appear to drift back toward the west. This is Retrograde Motion, since it is in a direction opposite that which is typical for planets. Finally, as the Earth swings past the the planet in its orbit, they appear to resume their normal west-to-east drift on successive nights. </para +><para +>This Retrograde Motion of the planets puzzled ancient Greek astronomers, and was one reason why they named these bodies <quote +>planets</quote +> which in Greek means <quote +>wanderers</quote +>. </para> +</sect1> diff --git a/tde-i18n-en_GB/docs/kdeedu/kstars/scriptbuilder.docbook b/tde-i18n-en_GB/docs/kdeedu/kstars/scriptbuilder.docbook new file mode 100644 index 00000000000..35e08cfb438 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kstars/scriptbuilder.docbook @@ -0,0 +1,154 @@ +<sect1 id="tool-scriptbuilder"> +<title +>The Script Builder Tool</title> +<indexterm +><primary +>Tools</primary> +<secondary +>Script Builder</secondary> +</indexterm> + +<para +>KDE applications can be controlled externally from another program, from a console prompt, or from a shell script using the Desktop COmmunication Protocol (<abbrev +>DCOP</abbrev +>). KStars takes advantage of this feature to allow rather complex behaviours to be scripted and played back at any time. This can be used, for example, to create a classroom demo to illustrate an astronomical concept. </para> +<para +>The problem with DCOP scripts is, writing them is a bit like programming, and can seem a daunting task to those who do not have programming experience. The Script Builder Tool provides a <abbrev +>GUI</abbrev +> point-and-click interface for constructing KStars DCOP scripts, making it very easy to create complex scripts. </para> + +<sect2 id="sb-intro"> +<title +>Introduction to the Script Builder</title> + +<para +>Before explaining how to use the Script Builder, I provide a very brief introduction to all of the <abbrev +>GUI</abbrev +> components; for more infomation, use the "What's This?" function. </para> + +<screenshot> +<screeninfo +>The Script Builder Tool </screeninfo> +<mediaobject> + <imageobject> + <imagedata fileref="scriptbuilder.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>Script Builder Tool</phrase> + </textobject> +</mediaobject> +</screenshot> + +<para +>The Script Builder is shown in the above screenshot. The box on the left is the <firstterm +>Current Script box</firstterm +>; it shows the list of commands that comprise the current working script. The box on the right is the <firstterm +>Function Browser</firstterm +>; it displays the list of all available script functions. Below the Function Browser, there is a small panel which will display short documentation about the script function highlighted in the Function Browser. The panel below the Current Script box is the <firstterm +>Function Arguments panel</firstterm +>; when a function is highlighted in the Current Script box, this panel will contain items for specifying values for any arguments that the highlighted function requires. </para +><para +>Along the top of the window, there is a row of buttons which operate on the script as a whole. From left to right, they are: <guibutton +>New Script</guibutton +>, <guibutton +>Open Script</guibutton +>, <guibutton +>Save Script</guibutton +>, <guibutton +>Save Script As...</guibutton +>, and <guibutton +>Test Script</guibutton +>. The function of these buttons should be obvious, except perhaps the last button. Pressing <guibutton +>Test Script</guibutton +> will attempt to run the current script in the main KStars window. You should move the Script Builder window out of the way before pressing this, so you can see the results. </para +><para +>In the centre of the window, there is a column of buttons which operate on individual script functions. From top to bottom, they are: <guibutton +>Add Function</guibutton +>, <guibutton +>Remove Function</guibutton +>, <guibutton +>Copy Function</guibutton +>, <guibutton +>Move Up</guibutton +>, and <guibutton +>Move Down</guibutton +>. <guibutton +>Add Function</guibutton +> adds the currently-highlighted function in the Function Browser to the Current Script box (you can also add a function by double-clicking on it). The rest of the buttons operate on the function highlighted in the Current Script box, either removing it, duplicating it, or changing its position in the current script. </para> +</sect2> + +<sect2 id="sb-using"> +<title +>Using the Script Builder</title> +<para +>In order to illustrate using the Script Builder, we present a small tutorial example where we make a script that tracks the Moon while the clock runs at an accelerated rate. </para +><para +>If we are going to track the Moon, we will need to point the display at it first. The <firstterm +>lookToward</firstterm +> function is used to do this. Highlight this function in the Function Browser, and note the documentation displayed in the panel below the Browser. Press the <guibutton +>Add Function</guibutton +> button to add this function to the Current Script box. The Function Arguments panel will now contain a combobox labelled <quote +>dir</quote +>, short for direction. This is the direction in which the display should be pointed. The combobox contains only the cardinal compass points, not the Moon or any other objects. You can either enter <quote +>Moon</quote +> in the box manually, or press the <guibutton +>Object</guibutton +> button to use the <guilabel +>Find Object</guilabel +> window to select the Moon from the list of named objects. Note that, as usual, centring on an object automatically engages object-tracking mode, so there is no need to add the <firstterm +>setTracking</firstterm +> function after lookToward. </para +><para +>Now that we have taken care of pointing at the Moon, we next want to make time pass at an accelerated rate. Use the <firstterm +>setClockScale</firstterm +> function for this. Add it to the script by double-clicking on it in the Function Browser. The Function Arguments panel contains a timestep spinbox for setting the desired time step for the simulation clock. Change the timestep to 3 hours. </para +><para +>OK, we have pointed at the Moon and accelerated the clock. Now we just want the script to wait for several seconds while the display tracks on the Moon. Add the <firstterm +>waitFor</firstterm +> function to the script, and use the Function Arguments panel to specify that it should wait for 20 seconds before continuing. </para +><para +>To finish up, let us reset the clock's timestep to the normal value of 1 second. Add another instance of setClockScale, and set its value to 1 sec. </para +><para +>Actually, we are not quite done yet. We should probably make sure that the display is using Equatorial coordinates before the script tracks the Moon with an accelerated time step. Otherwise, if the display is using Horizontal coordinates, it will rotate very quickly through large angles as the Moon rises and sets. This can be very confusing, and is avoided by setting the View Option <firstterm +>UseAltAz</firstterm +> to <quote +>false</quote +>. To change any View Option, use the <firstterm +>changeViewOption</firstterm +> function. Add this function to the script, and examine the Function Arguments panel. There is a combobox which contains the list of all options which can be adjusted by changeViewOption. Since we know we want the UseAltAz option, we could simply select it from the combobox. However, the list is quite long, and there is no explanation of what each item is for. It therefore may be easier to press the <guibutton +>Browse Tree</guibutton +> button, which will open a window containing a tree view of the available options, organised by topic. In addition, each item has a short explanation of what the option does, and the data type of the option's value. We find UseAltAz under the <guilabel +>Skymap options</guilabel +> category. Just highlight this item and press <guibutton +>OK</guibutton +>, and it will be selected in the combobox of the Function Arguments panel. Finally, make its value <quote +>false</quote +> or <quote +>0</quote +>. </para +><para +>One more step: changing UseAltAz at the end of the script does us no good; we need this to be changed before anything else happens. So, make sure this function is highlighted in the Current Script box, and press the <guibutton +>Move Up</guibutton +> button until it is the first function. </para +><para +>Now that we have finished the script, we should save it to disk. Press the <guibutton +>Save Script</guibutton +> button. This will first open a window in which you can provide a name for the script, and fill in your name as the author. Enter <quote +>Tracking the Moon</quote +> for a name, and your name as the author, and press <guibutton +>OK</guibutton +>. Next, you will see the standard &kde; Save File dialog. Specify a filename for the script and press <guibutton +>OK</guibutton +> to save the script. Note that if your filename does not end with <quote +>.kstars</quote +>, this suffix will be automatically attached. If you are curious, you can examine the script file with any text editor. </para +><para +>Now that we have a completed script, we can run it in a couple of ways. From a console prompt, you can simply execute the script as long as an instance of KStars is currently running. Alternatively, you can execute the script from within KStars using the <guimenuitem +>Run Script</guimenuitem +> item in the <guimenu +>File</guimenu +> menu. </para> +</sect2> + +</sect1> diff --git a/tde-i18n-en_GB/docs/kdeedu/kstars/sidereal.docbook b/tde-i18n-en_GB/docs/kdeedu/kstars/sidereal.docbook new file mode 100644 index 00000000000..a545518c5c6 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kstars/sidereal.docbook @@ -0,0 +1,87 @@ +<sect1 id="ai-sidereal"> +<sect1info> +<author +><firstname +>Jason</firstname +> <surname +>Harris</surname +> </author> +</sect1info> +<title +>Sidereal Time</title> +<indexterm +><primary +>Sidereal Time</primary> +<seealso +>Hour Angle</seealso> +</indexterm> +<para +><firstterm +>Sidereal Time</firstterm +> literally means <quote +>star time</quote +>. The time we are used to using in our everyday lives is Solar Time. The fundamental unit of Solar Time is a <firstterm +>Day</firstterm +>: the time it takes the Sun to travel 360 degrees around the sky, due to the rotation of the Earth. Smaller units of Solar Time are just divisions of a Day: </para +><para> +<itemizedlist> +<listitem +><para +>1/24 Day = 1 Hour</para +></listitem> +<listitem +><para +>1/60 Hour = 1 Minute</para +></listitem> +<listitem +><para +>1/60 Minute = 1 Second</para +></listitem> +</itemizedlist> +</para +><para +>However, there is a problem with Solar Time. The Earth does not actually spin around 360 degrees in one Solar Day. The Earth is in orbit around the Sun, and over the course of one day, it moves about one Degree along its orbit (360 degrees/365.25 Days for a full orbit = about one Degree per Day). So, in 24 hours, the direction toward the Sun changes by about a Degree. Therefore, the Earth has to spin 361 degrees to make the Sun look like it has travelled 360 degrees around the Sky. </para +><para +>In astronomy, we are concerned with how long it takes the Earth to spin with respect to the <quote +>fixed</quote +> stars, not the Sun. So, we would like a timescale that removes the complication of Earth's orbit around the Sun, and just focuses on how long it takes the Earth to spin 360 degrees with respect to the stars. This rotational period is called a <firstterm +>Sidereal Day</firstterm +>. On average, it is 4 minutes shorter than a Solar Day, because of the extra 1 degree the Earth spins in a Solar Day. Rather than defining a Sidereal Day to be 23 hours, 56 minutes, we define Sidereal Hours, Minutes and Seconds that are the same fraction of a Day as their Solar counterparts. Therefore, one Solar Second = 1.00278 Sidereal Seconds. </para +><para +>The Sidereal Time is useful for determining where the stars are at any given time. Sidereal Time divides one full spin of the Earth into 24 Sidereal Hours; similarly, the map of the sky is divided into 24 Hours of <firstterm +>Right Ascension</firstterm +>. This is no coincidence; Local Sidereal Time (<acronym +>LST</acronym +>) indicates the Right Ascension on the sky that is currently crossing the <link linkend="ai-meridian" +>Local Meridian</link +>. So, if a star has a Right Ascension of 05h 32m 24s, it will be on your meridian at LST=05:32:24. More generally, the difference between an object's <acronym +>RA</acronym +> and the Local Sidereal Time tells you how far from the Meridian the object is. For example, the same object at LST=06:32:24 (one Sidereal Hour later), will be one Hour of Right Ascension west of your meridian, which is 15 degrees. This angular distance from the meridian is called the object's <link linkend="ai-hourangle" +>Hour Angle</link +>. </para> +<tip> +<para +>The Local Sidereal Time is displayed by &kstars; in the <guilabel +>Time Info Box</guilabel +>, with the label <quote +>ST</quote +> (you have to <quote +>unshade</quote +> the box by double-clicking it in order to see the sidereal time). Note that the changing sidereal seconds are not synchronised with the changing Local Time and Universal Time seconds. In fact, if you watch the clocks for a while, you will notice that the Sidereal seconds really are slightly shorter than the LT and UT seconds. </para +><para +>Point to the <link linkend="ai-zenith" +>Zenith</link +> (press <keycap +>Z</keycap +> or select <guimenuitem +>Zenith</guimenuitem +> from the <guimenu +>Location</guimenu +> menu). The Zenith is the point on the sky where you are looking <quote +>straight up</quote +> from the ground, and it is a point on your <link linkend="ai-meridian" +>Local Meridian</link +>. Note the Right Ascension of the Zenith: it is exactly the same as your Local Sidereal Time. </para> +</tip> +</sect1> + diff --git a/tde-i18n-en_GB/docs/kdeedu/kstars/skycoords.docbook b/tde-i18n-en_GB/docs/kdeedu/kstars/skycoords.docbook new file mode 100644 index 00000000000..fca764c8f3a --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kstars/skycoords.docbook @@ -0,0 +1,192 @@ +<sect1 id="ai-skycoords"> +<sect1info> +<author +><firstname +>Jason</firstname +> <surname +>Harris</surname +> </author> +</sect1info> +<title +>Celestial Coordinate Systems</title> +<para> +<indexterm +><primary +>Celestial Coordinate Systems</primary> +<secondary +>Overview</secondary +></indexterm> +A basic requirement for studying the heavens is determining where in the sky things are. To specify sky positions, astronomers have developed several <firstterm +>coordinate systems</firstterm +>. Each uses a coordinate grid projected on the <link linkend="ai-csphere" +>Celestial Sphere</link +>, in analogy to the <link linkend="ai-geocoords" +>Geographic coordinate system</link +> used on the surface of the Earth. The coordinate systems differ only in their choice of the <firstterm +>fundamental plane</firstterm +>, which divides the sky into two equal hemispheres along a <link linkend="ai-greatcircle" +>great circle</link +>. (the fundamental plane of the geographic system is the Earth's equator). Each coordinate system is named for its choice of fundamental plane. </para> + +<sect2 id="equatorial"> +<title +>The Equatorial Coordinate System</title> +<indexterm +><primary +>Celestial Coordinate Systems</primary> +<secondary +>Equatorial Coordinates</secondary> +<seealso +>Celestial Equator</seealso +> <seealso +>Celestial Poles</seealso +> <seealso +>Geographic Coordinate System</seealso +> </indexterm> +<indexterm +><primary +>Right Ascension</primary +><see +>Equatorial Coordinates</see +></indexterm> +<indexterm +><primary +>Declination</primary +><see +>Equatorial Coordinates</see +></indexterm> + +<para +>The <firstterm +>Equatorial coordinate system</firstterm +> is probably the most widely used celestial coordinate system. It is also the most closely related to the <link linkend="ai-geocoords" +>Geographic coordinate system</link +>, because they use the same fundamental plane, and the same poles. The projection of the Earth's equator onto the celestial sphere is called the <link linkend="ai-cequator" +>Celestial Equator</link +>. Similarly, projecting the geographic Poles onto the celestial sphere defines the North and South <link linkend="ai-cpoles" +>Celestial Poles</link +>. </para +><para +>However, there is an important difference between the equatorial and geographic coordinate systems: the geographic system is fixed to the Earth; it rotates as the Earth does. The Equatorial system is fixed to the stars<footnote id="fn-precess" +><para +>actually, the equatorial coordinates are not quite fixed to the stars. See <link linkend="ai-precession" +>precession</link +>. Also, if <link linkend="ai-hourangle" +>Hour Angle</link +> is used in place of Right Ascension, then the Equatorial system is fixed to the Earth, not to the stars.</para +></footnote +>, so it appears to rotate across the sky with the stars, but of course it is really the Earth rotating under the fixed sky. </para +><para +>The <firstterm +>latitudinal</firstterm +> (latitude-like) angle of the Equatorial system is called <firstterm +>Declination</firstterm +> (Dec for short). It measures the angle of an object above or below the Celestial Equator. The <firstterm +>longitudinal</firstterm +> angle is called the <firstterm +>Right Ascension</firstterm +> (<acronym +>RA</acronym +> for short). It measures the angle of an object East of the <link linkend="ai-equinox" +>Vernal Equinox</link +>. Unlike longitude, Right Ascension is usually measured in hours instead of degrees, because the apparent rotation of the Equatorial coordinate system is closely related to <link linkend="ai-sidereal" +>Sidereal Time</link +> and <link linkend="ai-hourangle" +>Hour Angle</link +>. Since a full rotation of the sky takes 24 hours to complete, there are (360 degrees / 24 hours) = 15 degrees in one Hour of Right Ascension. </para> +</sect2> + +<sect2 id="horizontal"> +<title +>The Horizontal Coordinate System</title> + +<indexterm +><primary +>Celestial Coordinate Systems</primary> +<secondary +>Horizontal Coordinates</secondary> +<seealso +>Horizon</seealso +> <seealso +>Zenith</seealso +> </indexterm> +<indexterm +><primary +>Azimuth</primary +><see +>Horizontal Coordinates</see +></indexterm> +<indexterm +><primary +>Altitude</primary +><see +>Horizontal Coordinates</see +></indexterm> +<para +>The Horizontal coordinate system uses the observer's local <link linkend="ai-horizon" +>horizon</link +> as the Fundamental Plane. This conveniently divides the sky into the upper hemisphere that you can see, and the lower hemisphere that you can't (because the Earth is in the way). The pole of the upper hemisphere is called the <link linkend="ai-zenith" +>Zenith</link +>. The pole of the lower hemisphere is called the <firstterm +>nadir</firstterm +>. The angle of an object above or below the horizon is called the <firstterm +>Altitude</firstterm +> (Alt for short). The angle of an object around the horizon (measured from the North point, toward the East) is called the <firstterm +>Azimuth</firstterm +>. The Horizontal Coordinate System is sometimes also called the Alt/Az Coordinate System. </para +><para +>The Horizontal Coordinate System is fixed to the Earth, not the Stars. Therefore, the Altitude and Azimuth of an object changes with time, as the object appears to drift across the sky. In addition, because the Horizontal system is defined by your local horizon, the same object viewed from different locations on Earth at the same time will have different values of Altitude and Azimuth. </para +><para +>Horizontal coordinates are very useful for determining the Rise and Set times of an object in the sky. When an object has Altitude=0 degrees, it is either Rising (if its Azimuth is < 180 degrees) or Setting (if its Azimuth is > 180 degrees). </para> +</sect2> + +<sect2 id="ecliptic"> +<title +>The Ecliptic Coordinate System</title> + +<indexterm +><primary +>Celestial Coordinate Systems</primary> +<secondary +>Ecliptic Coordinates</secondary> +<seealso +>Ecliptic</seealso> +</indexterm> +<para +>The Ecliptic coordinate system uses the <link linkend="ai-ecliptic" +>Ecliptic</link +> for its Fundamental Plane. The Ecliptic is the path that the Sun appears to follow across the sky over the course of a year. It is also the projection of the Earth's orbital plane onto the Celestial Sphere. The latitudinal angle is called the <firstterm +>Ecliptic Latitude</firstterm +>, and the longitudinal angle is called the <firstterm +>Ecliptic Longitude</firstterm +>. Like Right Ascension in the Equatorial system, the zeropoint of the Ecliptic Longitude is the <link linkend="ai-equinox" +>Vernal Equinox</link +>. </para +><para +>What do you think such a coordinate system would be useful for? If you guessed charting solar system objects, you are right! Each of the planets (except Pluto) orbits the Sun in roughly the same plane, so they always appear to be somewhere near the Ecliptic (&ie;, they always have small ecliptic latitudes). </para> +</sect2> + +<sect2 id="galactic"> +<title +>The Galactic Coordinate System</title> + +<indexterm +><primary +>Celestial Coordinate Systems</primary> +<secondary +>Galactic Coordinates</secondary> +</indexterm> +<para> +<indexterm +><primary +>Milky Way</primary +></indexterm +> The Galactic coordinate system uses the <firstterm +>Milky Way</firstterm +> as its Fundamental Plane. The latitudinal angle is called the <firstterm +>Galactic Latitude</firstterm +>, and the longitudinal angle is called the <firstterm +>Galactic Longitude</firstterm +>. This coordinate system is useful for studying the Galaxy itself. For example, you might want to know how the density of stars changes as a function of Galactic Latitude, to how much the disk of the Milky Way is flattened. </para> +</sect2> +</sect1> diff --git a/tde-i18n-en_GB/docs/kdeedu/kstars/solarsys.docbook b/tde-i18n-en_GB/docs/kdeedu/kstars/solarsys.docbook new file mode 100644 index 00000000000..9acaf75e8ba --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kstars/solarsys.docbook @@ -0,0 +1,35 @@ +<sect1 id="tool-solarsys"> +<title +>Solar System Viewer</title> +<indexterm +><primary +>Tools</primary> +<secondary +>Solar System Viewer</secondary> +</indexterm> + +<screenshot> +<screeninfo +>The Solar System Viewer </screeninfo> +<mediaobject> + <imageobject> + <imagedata fileref="solarsystem.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>Solar System Viewer</phrase> + </textobject> +</mediaobject> +</screenshot> + +<para +>This tool displays a model of our solar system as seen from above, for the current date and time in the main window. The Sun is drawn as a yellow dot in the centre of the plot, and the orbits of the planets are drawn as circles with correct relative diameters, centred on the Sun. The current position of each planet along its orbit is drawn as a coloured dot along with a name label. The display can be zoomed in and out with the <keycap +>+</keycap +> and <keycap +>-</keycap +> keys. </para> +<note> +<para +>The current version of this tool shows a very simplified model of the solar system; we are planning on several improvements in future versions. For example, the orbits will be displayed as ellipses, not perfect circles. We will also make it possible to recenter the display at any location (currently, the centre is fixed at the Sun), and allow the date to be changed, including the ability to animate the display with a variable timestep. Finally, we would like to add comets and asteroids as well. </para> +</note> +</sect1> diff --git a/tde-i18n-en_GB/docs/kdeedu/kstars/spiralgalaxies.docbook b/tde-i18n-en_GB/docs/kdeedu/kstars/spiralgalaxies.docbook new file mode 100644 index 00000000000..2f2b099a9f9 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kstars/spiralgalaxies.docbook @@ -0,0 +1,92 @@ +<sect1 id="ai-spiralgal"> + +<sect1info> +<author +><firstname +>Mike</firstname +> <surname +>Choatie</surname +> </author> +</sect1info> + +<title +>Spiral Galaxies</title> +<indexterm +><primary +>Spiral Galaxies</primary> +</indexterm> + +<para +>Spiral galaxies are huge collections of billions of stars, most of which are flattened into a disk shape, with a bright, spherical bulge of stars at its centre. Within the disk, there are typically bright arms where the youngest, brightest stars are found. These arms wind out from the centre in a spiral pattern, giving the galaxies their name. Spiral galaxies look a bit like hurricanes, or like water flowing down a drain. They are some of the most beautiful objects in the sky. </para> +<para +>Galaxies are classified using a <quote +>tuning fork diagram</quote +>. The end of the fork classifies <link linkend="ai-ellipgal" +>elliptical galaxies</link +> on a scale from the roundest, which is an E0, to those that appear most flattened, which is rated as E7. The <quote +>tines</quote +> of the tuning fork are where the two types of spiral galaxies are classified: normal spirals, and <quote +>barred</quote +> spirals. A barred spiral is one whose nuclear bulge is stretched out into a line, so it literally looks like it has a <quote +>bar</quote +> of stars in its centre. </para +><para +>Both types of spiral galaxies are sub-classified according to the prominence of their central <quote +>bulge</quote +> of stars, their overall surface brightness, and how tightly their spiral arms are wound. These characteristics are related, so that an Sa galaxy has a large central bulge, a high surface brightness, and tightly-wound spiral arms. An Sb galaxy has a smaller bulge, a dimmer disk, and looser arms than an Sa, and so on through Sc and Sd. Barred galaxies use the same classification scheme, indicated by types SBa, SBb, SBc, and SBd. </para +><para +>There is another class of galaxy called S0, which is morphologically a transitional type between true spirals and ellipticals. Its spiral arms are so tightly wound as to be indistinguishable; S0 galaxies have disks with a uniform brightness. They also have an extremely dominant bulge. </para +><para +>The Milky Way galaxy, which is home to earth and all of the stars in our sky, is a Spiral Galaxy, and is believed to be a barred spiral. The name <quote +>Milky Way</quote +> refers to a band of very faint stars in the sky. This band is the result of looking in the plane of our galaxy's disk from our perspective inside it. </para +><para +>Spiral galaxies are very dynamic entities. They are hotbeds of star formation, and contain many young stars in their disks. Their central bulges tend to be made of older stars, and their diffuse halos are made of the very oldest stars in the Universe. Star formation is active in the disks because that is where the gas and dust are most concentrated; gas and dust are the building blocks of star formation. </para +><para +>Modern telescopes have revealed that many Spiral galaxies harbour supermassive black holes at their centres, with masses that can exceed that of a billion Suns. Both elliptical and spiral galaxies are known to contain these exotic objects; in fact many astronomers now believe that <emphasis +>all</emphasis +> large galaxies contain a supermassive black hole in their nucleus. Our own Milky Way is known to harbour a black hole in its core with a mass millions of times bigger than a star's mass. </para> + +<tip> +<para +>There are many fine examples of spiral galaxies to be found in &kstars;, and many have beautiful images available in their <link linkend="popup-menu" +>popup menu</link +>. You can find them by using the <link linkend="findobjects" +>Find Object</link +> window. Here is a list of some spiral galaxies with nice images available: <itemizedlist> +<listitem +><para +>M 64, the Black-Eye Galaxy (type Sa)</para +></listitem> +<listitem +><para +>M 31, the Andromeda Galaxy (type Sb)</para +></listitem> +<listitem +><para +>M 81, Bode's Galaxy (type Sb)</para +></listitem> +<listitem +><para +>M 51, the Whirlpool Galaxy (type Sc)</para +></listitem> +<listitem +><para +>NGC 300 (type Sd) [use DSS image link]</para +></listitem> +<listitem +><para +>M 83 (type SBa)</para +></listitem> +<listitem +><para +>NGC 1530 (type SBb)</para +></listitem> +<listitem +><para +>NGC 1073 (type SBc)</para +></listitem> +</itemizedlist> +</para> +</tip> +</sect1> diff --git a/tde-i18n-en_GB/docs/kdeedu/kstars/stars.docbook b/tde-i18n-en_GB/docs/kdeedu/kstars/stars.docbook new file mode 100644 index 00000000000..914651780ab --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kstars/stars.docbook @@ -0,0 +1,113 @@ +<sect1 id="ai-stars"> +<sect1info> +<author +><firstname +>Jason</firstname +> <surname +>Harris</surname +> </author> +</sect1info> +<title +>Stars: An Introductory <acronym +>FAQ</acronym +></title> +<indexterm +><primary +>Stars</primary +></indexterm> + +<qandaset id="stars-faq"> + +<qandaentry> +<question> +<para +>What are the stars?</para> +</question> +<answer> +<para +><firstterm +>Stars</firstterm +> are gigantic, self-gravitating spheres of (mostly) Hydrogen gas. Stars are also thermonuclear engines; nuclear fusion takes place deep in the cores of stars, where the density is extreme and the temperature reaches tens of millions of degrees Celsius. </para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>Is the Sun a star?</para> +</question> +<answer> +<para +>Yes, the Sun is a star. It is the dominant centrepiece of our solar system. Compared to other stars, our Sun is rather ordinary; it appears to be so much bigger and brighter to us because it is millions of times closer than any other star. </para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>Why do stars shine?</para> +</question> +<answer> +<para +>The short answer is: star shine because they are very hot. It is really no more complicated than that. Any object heated to thousands of degrees will radiate light, just like stars do. </para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>The obvious next question is: why are stars so hot?</para> +</question> +<answer> +<para +>This is a tougher question. The usual answer is that stars get their heat from the thermonuclear fusion reactions in their cores. However, this cannot be the ultimate cause for the stars' heat, because a star must be hot in the first place for nuclear fusion to be triggered. Fusion can only sustain the hot temperature; it cannot make a star hot. A more correct answer is that stars are hot because they have collapsed. Stars form from diffuse gaseous nebulae; as the nebulous gas condenses to form a star, the gravitational potential energy of the material is released, first as kinetic energy, and ultimately as heat as the density increases. </para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>Are stars all the same?</para> +</question> +<answer> +<para +>Stars have many things in common: they are all collapsed spheres of hot, dense gas (mostly Hydrogen), and nuclear fusion reactions are occurring at or near the centres of every star in the sky. </para +><para +>However, stars also show a great diversity in some properties. The brightest stars shine almost 100 million times as brightly as the faintest stars. Stars range in surface temperature from only a few thousand degrees to almost 50,000 degrees Celsius. These differences are largely due to differences in mass: massive stars are both hotter and brighter than lower-mass stars. The temperature and Luminosity also depend on the <emphasis +>evolutionary state</emphasis +> of the star. </para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>What is the Main Sequence?</para> +</question> +<answer> +<para +><indexterm +><primary +>Main sequence</primary +></indexterm +> The main sequence is the evolutionary state of a star when it is fusing Hydrogen in its core. This is the first (and longest) stage of a star's life (not including protostar phases). What happens to a star after it runs out of core Hydrogen is addressed in the stellar evolution article (coming soon). </para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>How long do stars last?</para> +</question> +<answer> +<para +>The lifetime of a star depends very much on its mass. More massive stars are hotter and shine much more brightly, causing them to consume their nuclear fuel much more rapidly. The largest stars (roughly 100 times as massive as the Sun), will run out of fuel in only a few million years; while the smallest stars (roughly ten percent the mass of the Sun), with their much more frugal consumption rate, will shine on (albeit dimly) for <emphasis +>trillions</emphasis +> of years. Note that this is much longer than the Universe has yet been in existence. </para> +</answer> +</qandaentry> + +</qandaset> +</sect1> + + diff --git a/tde-i18n-en_GB/docs/kdeedu/kstars/timezones.docbook b/tde-i18n-en_GB/docs/kdeedu/kstars/timezones.docbook new file mode 100644 index 00000000000..f899dd74681 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kstars/timezones.docbook @@ -0,0 +1,32 @@ +<sect1 id="ai-timezones"> +<sect1info> +<author +><firstname +>Jason</firstname +> <surname +>Harris</surname +> </author> +</sect1info> +<title +>Time Zones</title> +<indexterm +><primary +>Time Zones</primary> +</indexterm> +<para +>The Earth is round, and it is always half-illuminated by the Sun. However, because the Earth is spinning, the half that is illuminated is always changing. We experience this as the passing of days wherever we are on the Earth's surface. At any given instant, there are places on the Earth passing from the dark half into the illuminated half (which is seen as <emphasis +>dawn</emphasis +> on the surface). At the same instant, on the opposite side of the Earth, points are passing from the illuminated half into darkness (which is seen as <emphasis +>dusk</emphasis +> at those locations). So, at any given time, different places on Earth are experiencing different parts of the day. Thus, Solar time is defined locally, so that the clock time at any location describes the part of the day consistently. </para +><para +>This localisation of time is accomplished by dividing the globe into 24 vertical slices called <firstterm +>Time Zones</firstterm +>. The Local Time is the same within any given zone, but the time in each zone is one Hour <emphasis +>earlier</emphasis +> than the time in the neighboring Zone to the East. Actually, this is a idealised simplification; real Time Zone boundaries are not straight vertical lines, because they often follow national boundaries and other political considerations. </para +><para +>Note that because the Local Time always increases by an hour when moving between Zones to the East, by the time you move through all 24 Time Zones, you are a full day ahead of where you started. We deal with this paradox by defining the <firstterm +>International Date Line</firstterm +>, which is a Time Zone boundary in the Pacific Ocean, between Asia and North America. Points just to the East of this line are 24 hours behind the points just to the West of the line. This leads to some interesting phenomena. A direct flight from Australia to California arrives before it departs. Also, the islands of Fiji straddle the International Date Line, so if you have a bad day on the West side of Fiji, you can go over to the East side of Fiji and have a chance to live the same day all over again. </para> +</sect1> diff --git a/tde-i18n-en_GB/docs/kdeedu/kstars/tools.docbook b/tde-i18n-en_GB/docs/kdeedu/kstars/tools.docbook new file mode 100644 index 00000000000..60bd3929c42 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kstars/tools.docbook @@ -0,0 +1,61 @@ +<chapter id="tools"> +<title +>KStars Tools</title> +<para> +<indexterm +><primary +>Tools</primary +></indexterm +> &kstars; comes with a number of tools that allow you to explore some more advanced aspects of astronomy and the night sky. </para> + +<itemizedlist> +<listitem +><para +><link linkend="tool-details" +>Object Details</link +></para +></listitem> +<listitem +><para +><link linkend="tool-calculator" +>Astrocalculator</link +></para +></listitem> +<listitem +><para +><link linkend="tool-aavso" +>AAVSO Lightcurves</link +></para +></listitem> +<listitem +><para +><link linkend="tool-altvstime" +>Altitude vs. Time Plotter</link +></para +></listitem> +<listitem +><para +><link linkend="tool-whatsup" +>What's Up Tonight?</link +></para +></listitem> +<listitem +><para +><link linkend="tool-scriptbuilder" +>Script Builder</link +></para +></listitem> +<listitem +><para +><link linkend="tool-solarsys" +>Solar System Viewer</link +></para +></listitem> +<listitem +><para +><link linkend="tool-jmoons" +>Jupiter Moons Tool</link +></para +></listitem> +</itemizedlist> +&tool-details; &tool-calculator; &tool-aavso; &tool-altvstime; &tool-whatsup; &tool-scriptbuilder; &tool-solarsys; &tool-jmoons; </chapter> diff --git a/tde-i18n-en_GB/docs/kdeedu/kstars/utime.docbook b/tde-i18n-en_GB/docs/kdeedu/kstars/utime.docbook new file mode 100644 index 00000000000..7319b1cd1fe --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kstars/utime.docbook @@ -0,0 +1,54 @@ +<sect1 id="ai-utime"> +<sect1info> +<author +><firstname +>Jason</firstname +> <surname +>Harris</surname +> </author> +</sect1info> +<title +>Universal Time</title> +<indexterm +><primary +>Universal Time</primary> +<seealso +>Time Zones</seealso> +</indexterm> +<para +>The time on our clocks is essentially a measurement of the current position of the Sun in the sky, which is different for places at different Longitudes because the Earth is round (see <link linkend="ai-timezones" +>Time Zones</link +>). </para +><para +>However, it is sometimes necessary to define a global time, one that is the same for all places on Earth. One way to do this is to pick a place on the Earth, and adopt the Local Time at that place as the <firstterm +>Universal Time</firstterm +>, abbreviated <abbrev +>UT</abbrev +>. (The name is a bit of a misnomer, since Universal Time has little to do with the Universe. It would perhaps be better to think of it as <emphasis +>global time</emphasis +>). </para +><para +>The geographic location chosen to represent Universal Time is Greenwich, England. The choice is arbitrary and historical. Universal Time became an important concept when European ships began to sail the wide open seas, far from any known landmarks. A navigator could reckon the ship's longitude by comparing the Local Time (as measured from the Sun's position) to the time back at the home port (as kept by an accurate clock on board the ship). Greenwich was home to England's Royal Observatory, which was charged with keeping time very accurately, so that ships in port could re-calibrate their clocks before setting sail. </para> +<tip> +<para +>Exercise:</para> +<para +>Set the geographic location to <quote +>Greenwich, England</quote +> using the <guilabel +>Set Location</guilabel +> window (<keycombo action="simul" +>&Ctrl;<keycap +>G</keycap +></keycombo +>). Note that the Local Time (<abbrev +>LT</abbrev +>)and the Universal Time (<abbrev +>UT</abbrev +>) are now the same. </para +><para +>Further Reading: The history behind the construction of the first clock that was accurate and stable enough to be used on ships to keep Universal Time is a fascinating tale, and one told expertly in the book <quote +>Longitude</quote +>, by Dava Sobel. </para> +</tip> +</sect1> diff --git a/tde-i18n-en_GB/docs/kdeedu/kstars/wut.docbook b/tde-i18n-en_GB/docs/kdeedu/kstars/wut.docbook new file mode 100644 index 00000000000..2e89188362a --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kstars/wut.docbook @@ -0,0 +1,56 @@ +<sect1 id="tool-whatsup"> +<title +>What's Up Tonight? Tool</title> +<indexterm +><primary +>Tools</primary> +<secondary +>What's Up Tonight? Tool</secondary> +</indexterm> + +<screenshot> +<screeninfo +>The What's Up Tonight Tool </screeninfo> +<mediaobject> + <imageobject> + <imagedata fileref="wut.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>What's Up Tonight?</phrase> + </textobject> +</mediaobject> +</screenshot> + +<para +>The <quote +>What's Up Tonight?</quote +> (WUT) tool displays a list of objects that will be visible at night from any location, on any date. By default, the Date and Location are taken from the current settings in the main window, but you can change either value using the <guibutton +>Change Date</guibutton +> and <guibutton +>Change Location</guibutton +> buttons at the top of the WUT window. </para> +<para +>The WUT tool also displays a short almanac of data for the selected date: the rise and set times for the Sun and moon, the duration of the night and the Moon's illumination fraction. </para> +<para +>Below the almanac is where the object information is displayed. The objects are organised into type categories. Select an object type in the box labelled <guilabel +>Choose a Category</guilabel +>, and all objects of that type which are above the horizon on the selected night will be displayed in the box labelled <guilabel +>Matching Objects</guilabel +>. For example, in the screenshot, the <guilabel +>Planets</guilabel +> category has been selected, and four planets which are up on the selected night are displayed (Mars, Neptune, Pluto, and Uranus). When an object in the list is selected, its rise, set and transit times are displayed in the lower-right panel. In addition, you can press the <guibutton +>Object Details...</guibutton +> button to open the <link linkend="tool-details" +>Object Details window</link +> for that object. </para> +<para +>By default, the WUT will display objects which are above the horizon between sunset and midnight (i.e., <quote +>in the evening</quote +>). You can choose to show objects which are up between midnight and dawn (<quote +>in the morning</quote +>), or between dusk and dawn (<quote +>any time tonight</quote +>) using the combobox near the top of the window. </para> +</sect1> + diff --git a/tde-i18n-en_GB/docs/kdeedu/kstars/zenith.docbook b/tde-i18n-en_GB/docs/kdeedu/kstars/zenith.docbook new file mode 100644 index 00000000000..a466a29e333 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kstars/zenith.docbook @@ -0,0 +1,44 @@ +<sect1 id="ai-zenith"> +<sect1info> +<author +><firstname +>Jason</firstname +> <surname +>Harris</surname +> </author> +</sect1info> +<title +>The Zenith</title> +<indexterm +><primary +>Zenith</primary> +<seealso +>Horizontal Coordinates</seealso> +</indexterm> +<para +>The Zenith is the point in the sky where you are looking when you look <quote +>straight up</quote +> from the ground. More precisely, it is the point on the sky with an <firstterm +>Altitude</firstterm +> of +90 Degrees; it is the Pole of the <link linkend="horizontal" +>Horizontal Coordinate System</link +>. Geometrically, it is the point on the <link linkend="ai-csphere" +>Celestial Sphere</link +> intersected by a line drawn from the centre of the Earth through your location on the Earth's surface. </para +><para +>The Zenith is, by definition, a point along the <link linkend="ai-meridian" +>Local Meridian</link +>. </para> +<tip> +<para +>Exercise:</para> +<para +>You can point to the Zenith by pressing <keycap +>Z</keycap +> or by selecting <guimenuitem +>Zenith</guimenuitem +> from the <guimenu +>Location</guimenu +> menu. </para> +</tip> +</sect1> diff --git a/tde-i18n-en_GB/docs/kdeedu/kturtle/Makefile.am b/tde-i18n-en_GB/docs/kdeedu/kturtle/Makefile.am new file mode 100644 index 00000000000..f781297a70f --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kturtle/Makefile.am @@ -0,0 +1,4 @@ +KDE_LANG = en_GB +SUBDIRS = $(AUTODIRS) +KDE_DOCS = AUTO +KDE_MANS = AUTO diff --git a/tde-i18n-en_GB/docs/kdeedu/kturtle/Makefile.in b/tde-i18n-en_GB/docs/kdeedu/kturtle/Makefile.in new file mode 100644 index 00000000000..75796b01261 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kturtle/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/kdeedu/kturtle +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 = AUTO +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/kdeedu/kturtle/Makefile'; \ +#>- cd $(top_srcdir) && \ +#>- $(AUTOMAKE) --gnu docs/kdeedu/kturtle/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/kdeedu/kturtle/Makefile'; \ + cd $(top_srcdir) && \ + $(AUTOMAKE) --gnu docs/kdeedu/kturtle/Makefile + cd $(top_srcdir) && perl ../scripts/admin/am_edit -p../scripts/admin docs/kdeedu/kturtle/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=index.docbook programming-reference.docbook getting-started.docbook glossary.docbook index.cache.bz2 translator-guide.docbook Makefile.in using-kturtle.docbook Makefile.am + +#>+ 24 +index.cache.bz2: $(srcdir)/index.docbook $(KDE_XSL_STYLESHEET) glossary.docbook index.docbook using-kturtle.docbook programming-reference.docbook getting-started.docbook translator-guide.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)/kturtle + @if test -f index.cache.bz2; then \ + echo $(INSTALL_DATA) index.cache.bz2 $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kturtle/; \ + $(INSTALL_DATA) index.cache.bz2 $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kturtle/; \ + elif test -f $(srcdir)/index.cache.bz2; then \ + echo $(INSTALL_DATA) $(srcdir)/index.cache.bz2 $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kturtle/; \ + $(INSTALL_DATA) $(srcdir)/index.cache.bz2 $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kturtle/; \ + fi + -rm -f $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kturtle/common + $(LN_S) $(kde_libs_htmldir)/$(KDE_LANG)/common $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kturtle/common + +uninstall-docs: + -rm -rf $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kturtle + +clean-docs: + -rm -f index.cache.bz2 + + +#>+ 13 +install-nls: + $(mkinstalldirs) $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kturtle + @for base in glossary.docbook index.docbook using-kturtle.docbook programming-reference.docbook getting-started.docbook translator-guide.docbook ; do \ + echo $(INSTALL_DATA) $$base $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kturtle/$$base ;\ + $(INSTALL_DATA) $(srcdir)/$$base $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kturtle/$$base ;\ + done + +uninstall-nls: + for base in glossary.docbook index.docbook using-kturtle.docbook programming-reference.docbook getting-started.docbook translator-guide.docbook ; do \ + rm -f $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kturtle/$$base ;\ + done + + +#>+ 5 +distdir-nls: + for file in glossary.docbook index.docbook using-kturtle.docbook programming-reference.docbook getting-started.docbook translator-guide.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/kdeedu/kturtle/Makefile'; \ + cd $(top_srcdir) && \ + $(AUTOMAKE) --gnu docs/kdeedu/kturtle/Makefile + cd $(top_srcdir) && perl ../scripts/admin/am_edit -p../scripts/admin docs/kdeedu/kturtle/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/kdeedu/kturtle/getting-started.docbook b/tde-i18n-en_GB/docs/kdeedu/kturtle/getting-started.docbook new file mode 100644 index 00000000000..d14539ae964 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kturtle/getting-started.docbook @@ -0,0 +1,292 @@ +<chapter id="getting-started"> +<title +>Getting Started</title> +<para +>When you start &kturtle; you will see something like this: <screenshot +> <screeninfo +>Here is a screenshot of &kturtle; when you start it for the first time</screeninfo +> <mediaobject +> <imageobject +> <imagedata fileref="mainwindow.png" format="PNG"/> </imageobject +> <textobject +> <phrase +>&kturtle; Main window</phrase +> </textobject +> </mediaobject +> </screenshot +> In this Getting Started guide we assume that the language of the &logo; commands is English. You can change this language in <menuchoice +><guimenu +>Settings</guimenu +><guimenuitem +>Configure &kturtle;...</guimenuitem +></menuchoice +> in the <guilabel +>Language</guilabel +> section. Be aware that the language you set here for &kturtle; is the one you use to type the &logo; commands.</para> + +<sect1 id="first-steps"> +<title +>First steps with &logo;: meet the Turtle!</title> +<para +>You must have noticed the turtle is in the middle of the canvas: you are just about to learn how to control it using commands in the code editor.</para> + +<sect2 id="the-turtle-moves"> +<title +>The Turtle Moves</title> +<para +>Let us start by getting the turtle moving. Our turtle can do 3 types of moves, (1) it can go forwards and backwards, (2) it can turn left and right and (3) it can go directly to a position on the screen. Try this for example:</para> +<para> +<screen +>forward 90 +turnleft 90 +</screen> +Type or copy-paste the code to the code editor and execute it (using <link linkend="file-execute" +><menuchoice +><guimenu +>File</guimenu +><guimenuitem +>Execute Commands</guimenuitem +></menuchoice +></link +>) to see the result.</para> + +<para +>When you typed and executed the commands like above in the code editor you might have noticed one or more of the following things:</para> +<orderedlist> +<listitem +><para +>That — after executing the commands — the turtle moves up, draws a line, and then turns a quarter turn to the left. This because you have used the <link linkend="forward" +><userinput +>forward</userinput +></link +> and the <link linkend="turnleft" +><userinput +>turnleft</userinput +></link +> commands.</para> +</listitem> +<listitem> +<para +>That the colour of the code changed while you where typing it: this feature is called <emphasis +>intuitive highlighting</emphasis +> — different types of commands are highlighted differently. This makes reading large blocks of code more easy.</para> +</listitem> +<listitem> +<para +>That the turtle draws a thin black line.</para> +</listitem> +<listitem> +<para +>Maybe you got an error message. This could simply mean two things: you could have made a mistake while copying the commands, or you should still set the correct language for the &logo; commands (you can do that by choosing <menuchoice +><guimenu +>Settings</guimenu +><guimenuitem +>Configure &kturtle;...</guimenuitem +></menuchoice +>, in the <guilabel +>Language</guilabel +> section).</para> +</listitem> +</orderedlist> + +<para +>You will likely understand that <userinput +>forward 90</userinput +> commanded the turtle to move forward leaving a line, and that <userinput +>turnleft 90</userinput +> commanded the turtle to turn 90 <glossterm linkend="degrees" +>degrees</glossterm +> to the left.</para> + +<para +>Please see the following links to the reference manual for a complete explanation of the new commands: <userinput +>forward</userinput +>, <userinput +>backward</userinput +>, <userinput +>turnleft</userinput +>, and <userinput +>turnright</userinput +>.</para> +</sect2> + +<sect2 id="more-examples"> +<title +>More examples</title> +<para +>The first example was very simple, so let us go on!</para> + +<para> +<!--translators: if it's not already there, you can copy/paste the translated code below and save it in arrow.logo in your examples folder: kde-i18n/language-code/data/kdeedu/kturtle/ --> +<screen +>canvassize 200,200 +canvascolour 0,0,0 +pencolour 255,0,0 +penwidth 5 +clear + +go 20,20 +direction 135 + +forward 200 +turnleft 135 +forward 100 +turnleft 135 +forward 141 +turnleft 135 +forward 100 +turnleft 45 + +go 40, 100 +</screen> +Again you can type or copy-paste the code to the code editor or open the <filename +>arrow.logo</filename +> file in the <guimenu +>Open examples</guimenu +> folder and execute it (using <link linkend="file-execute" +><menuchoice +><guimenu +>File</guimenu +><guimenuitem +>Execute Commands</guimenuitem +></menuchoice +></link +>) to see the result. In the next examples you are expected to know the drill.</para> + +<para +>You might have noticed that this second example uses a lot more code. You have also seen a couple of new commands. Here a short explanation of all the new commands:</para> + +<para +><userinput +>canvassize 200,200</userinput +> sets the canvas width and height to 200 <glossterm linkend="pixels" +>pixels</glossterm +>. The width and the height are equal, so the canvas will be a square.</para> + +<para +><userinput +>canvascolour 0,0,0</userinput +> makes the canvas black. <userinput +>0,0,0</userinput +> is an <glossterm linkend="rgb" +>RGB-combination</glossterm +> where all values are set to <userinput +>0</userinput +>, which results in black.</para> + +<para +><userinput +>pencolor 255,0,0</userinput +> sets the color of the pen to red. <userinput +>255,0,0</userinput +> is an <glossterm linkend="rgb" +>RGB-combination</glossterm +> where only the red value is set to <userinput +>255</userinput +> (fully on) while the others (green and blue) are set to <userinput +>0</userinput +> (fully off). This results in a bright shade of red.</para> + +<para +><userinput +>penwidth 5</userinput +> sets the width (the size) of the pen to <userinput +>5</userinput +> <glossterm linkend="pixels" +>pixels</glossterm +>. From now on every line the turtle draw will have a thickness of <userinput +>5</userinput +>, until we change the <userinput +>penwidth</userinput +> to something else.</para> + +<para +><userinput +>clear</userinput +> clear the canvas, that is all it does.</para> + +<para +><userinput +>go 20,20</userinput +> commands the turtle to go to a certain place on the canvas. Counted from the upper left corner, this place is 20 <glossterm linkend="pixels" +>pixels</glossterm +> across from the left, and 20 <glossterm linkend="pixels" +>pixels</glossterm +> down from the top of the canvas. Note that using the <userinput +>go</userinput +> command the turtle will not draw a line.</para> + +<para +><userinput +>direction 135</userinput +> set the turtle's direction. The <userinput +>turnleft</userinput +> and <userinput +>turnright</userinput +> commands change the turtle's angle starting from its current direction. The <userinput +>direction</userinput +> command changes the turtle's angle from zero, and thus is not relative to the turtle previous direction.</para> + +<para +>After the <userinput +>direction</userinput +> command a lot of <userinput +>forward</userinput +> and <userinput +>turnleft</userinput +> commands follow. These command do the actual drawing.</para> + +<para +>At last another <userinput +>go</userinput +> command is used to move the turtle aside.</para> + +<para +>Make sure you follow the links to the reference. The reference explains each command more thoroughly.</para> + +</sect2> +</sect1> + + + +<!-- EXTRA SECTIONS CAN BE ADDED TO THE "GETTING STARTED" + +<sect1 id="calculations"> +<title +>Simple Calculations</title> +<para> +Not yet written +</para> +</sect1> +<sect1 id="using_variables"> +<title +>Using Variables: creating 'number containers'</title> +<para> +Not yet written +</para> +</sect1> +<sect1 id="using_strings"> +<title +>Using strings: creating 'text containers'</title> +<para> +Not yet written +</para> +</sect1> +<sect1 id="logic"> +<title +>Logic: asking the computer simple questions</title> +<para> +Not yet written +</para> +</sect1> +<sect1 id="recursion"> +<title +>Recursion: the Turtle is using itself</title> +<para> +Draw a maze for example +</para> +</sect1 +>--> + + +</chapter>
\ No newline at end of file diff --git a/tde-i18n-en_GB/docs/kdeedu/kturtle/glossary.docbook b/tde-i18n-en_GB/docs/kdeedu/kturtle/glossary.docbook new file mode 100644 index 00000000000..22af4ab935a --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kturtle/glossary.docbook @@ -0,0 +1,406 @@ +<chapter id="Glossary"> +<title +>Glossary</title> + +<para +>In this chapter you will find an explanation of most of the <quote +>uncommon</quote +> words that are used in the handbook.</para> + +<glosslist> +<glossentry id="degrees"> +<glossterm +>degrees</glossterm> +<glossdef +><para +>Degrees are units to measure angles or turns. A full turn is 360 degrees, a half turn 180 degrees and a quarter turn 90 degrees. The commands <userinput +>turnleft</userinput +>, <userinput +>turnright</userinput +> and <userinput +>direction</userinput +> need an input in degrees.</para +></glossdef> +</glossentry> + +<glossentry id="input-output"> +<glossterm +>input and output of commands</glossterm> +<glossdef +><para +>Some commands take input, some commands give output, some commands take input <emphasis +>and</emphasis +> give output and some commands neither take input nor give output.</para> +<para +>Some examples of commands that only take input are: <screen> +forward 50 +pencolour 255,0,0 +print "Hello!" +</screen +> The <userinput +>forward</userinput +> command takes <userinput +>50</userinput +> as input. <userinput +>forward</userinput +> needs this input to know how many <glossterm linkend="pixels" +>pixels</glossterm +> it should go forward. <userinput +>pencolor</userinput +> takes a colour as input and <userinput +>print</userinput +> takes a string (a piece of text) as input. Please note that the input can also be a container. The next example illustrates this: <screen +>x = 50 +print x +str = "hello!" +print str +</screen +></para> + +<para +>Now some examples of commands that give output: <screen> +x = inputwindow "Please type something and press OK... thanks!" +r = random 1,100 +</screen +> The <userinput +>inputwindow</userinput +> command takes a string as input, and outputs the number or string that is entered. As you can see, the output of <userinput +>inputwindow</userinput +> is stored in the container <userinput +>x</userinput +>. The <userinput +>random</userinput +> command also gives output. In this case it outputs a number between 1 and 100. The output of the random is again stored in a container, named <userinput +>r</userinput +>. Note that the containers <userinput +>x</userinput +> and <userinput +>r</userinput +> are not used in the example code above.</para> + +<para +>There are also commands that neither need input nor give output. Here are some examples: <screen +>clear +penup +wrapon +hide +</screen> +</para +></glossdef> +</glossentry> + +<glossentry id="intuitive-highlighting"> +<glossterm +>intuitive highlighting</glossterm> +<glossdef +><para +>This is a feature of &kturtle; that makes coding even easier. With intuitive highlighting the code that you write gets a colour that indicates what type of code it is. In the next list you will find the different types of code and the colour they get in <link linkend="the-code-editor" +>the code editor</link +>. <table> +<title +>Different types of code and their highlight colour</title> +<tgroup cols="3"> +<tbody> +<row> +<entry +>regular commands</entry> +<entry +>dark green</entry> +<entry +>The regular commands are described <link linkend="commands" +>here</link +>.</entry> +</row> +<row> +<entry +>execution controllers</entry> +<entry +>black (bold)</entry> +<entry +>The special commands control execution, read more on them <link linkend="controlling-execution" +>here</link +>.</entry> +</row> +<row> +<entry +>comments</entry> +<entry +>dark yellow</entry> +<entry +>Lines that are commented start with a comment characters (#). These lines are ignored when the code is executed. Comments allow the programmer to explain a bit about his code or can be used to temporarily prevent a certain piece of code from executing.</entry> +</row> +<row> +<entry +>brackets [, ]</entry> +<entry +>light green (bold)</entry> +<entry +>Brackets are used to group portions of code. Brackets are often used together with <link linkend="controlling-execution" +>execution controllers</link +>.</entry> +</row> +<row> +<entry +>the <link linkend="learn" +>learn</link +> command</entry> +<entry +>light green (bold)</entry> +<entry +>The <link linkend="learn" +>learn</link +> command is used to create new commands.</entry> +</row> +<row> +<entry +>numbers</entry> +<entry +>blue</entry> +<entry +>Numbers, well not much to say about them.</entry> +</row> +<row> +<entry +>strings</entry> +<entry +>dark red</entry> +<entry +>Not much to say about (text) strings either, except that they always start and end with the double quotes (").</entry> +</row> +<row> +<entry +>mathematical characters</entry> +<entry +>grey</entry> +<entry +>These are the mathematical characters: +, -, *, /, (, and ). Read more about them <link linkend="math" +>here</link +>.</entry> +</row> +<row> +<entry +>questions characters</entry> +<entry +>blue (bold)</entry> +<entry +>Read more about questions <link linkend="questions" +>here</link +>.</entry> +</row> +<row> +<entry +>question glue-words</entry> +<entry +>pink</entry> +<entry +>Read more about the question glue-words (and, or, not) <link linkend="question-glue" +>here</link +>.</entry> +</row> +<row> +<entry +>regular text</entry> +<entry +>black</entry> +<entry +></entry> +</row> +</tbody> +</tgroup> +</table> +</para +></glossdef> +</glossentry> + +<glossentry id="pixels"> +<glossterm +>pixels</glossterm> +<glossdef +><para +>A pixel is a dot on the screen. If you look very close you will see that the screen of your monitor uses pixels. All images on the screen are built with these pixels. A pixel is the smallest thing that can be drawn on the screen.</para> +<para +>A lot of commands need a number of pixels as input. These commands are: <userinput +>forward</userinput +>, <userinput +>backward</userinput +>, <userinput +>go</userinput +>, <userinput +>gox</userinput +>, <userinput +>goy</userinput +>, <userinput +>canvassize</userinput +> and <userinput +>penwidth</userinput +>.</para +></glossdef> +</glossentry> + +<glossentry id="rgb"> +<glossterm +>RGB combinations (colour codes)</glossterm> +<glossdef +><para +>RGB combinations are used to describe colours. The <quote +>R</quote +> stand for <quote +>red</quote +>, the <quote +>G</quote +> stands for <quote +>green</quote +> and the <quote +>B</quote +> stands for <quote +>blue</quote +>. An example of an RGB combination is <userinput +>255,0,0</userinput +>: the first value (<quote +>red</quote +>) is 255 and the others are 0, so this represents a bright shade of red. Each value of an RGB combination has to be in the range 0 to 255. Here a small list of some often used colours: <table frame="none"> +<title +>Often used RGB combinations</title> +<tgroup cols="2" colsep="5" rowsep="1"> +<colspec colname="c1"/> +<tbody> +<row +><entry +><userinput +>0,0,0</userinput +></entry +><entry +>black</entry +></row> +<row +><entry +><userinput +>255,255,255</userinput +></entry +><entry +>white</entry +></row> +<row +><entry +><userinput +>255,0,0</userinput +></entry +><entry +>red</entry +></row> +<row +><entry +><userinput +>150,0,0</userinput +></entry +><entry +>dark red</entry +></row> +<row +><entry +><userinput +>0,255,0</userinput +></entry +><entry +>green</entry +></row> +<row +><entry +><userinput +>0,0,255</userinput +></entry +><entry +>blue</entry +></row> +<row +><entry +><userinput +>0,255,255</userinput +></entry +><entry +>light blue</entry +></row> +<row +><entry +><userinput +>255,0,255</userinput +></entry +><entry +>pink</entry +></row> +<row +><entry +><userinput +>255,255,0</userinput +></entry +><entry +>yellow</entry +></row> +</tbody> +</tgroup> +</table> +</para> +<para +>To easily find the RGB combinations of a colour you should try the colour picker! You can open the colour picker using <link linkend="tools-color-picker" +><menuchoice +><guimenu +>Tools</guimenu +><guimenuitem +>Colour Picker</guimenuitem +></menuchoice +></link +>.</para> +<para +>Two commands need an RGB combination as input: these commands are <userinput +>canvascolour</userinput +> and <userinput +>pencolour</userinput +>.</para +></glossdef> +</glossentry> + +<glossentry id="sprite"> +<glossterm +>sprite</glossterm> +<glossdef +><para +>A sprite is a small picture that can be moved around the screen. Our beloved turtle, for instance, is a sprite.</para> +<para +>Note: with this version of &kturtle; the sprite cannot be changed from a turtle into something else. Future versions of &kturtle; will be able to do this.</para +></glossdef> +</glossentry> + +<glossentry id="wrapping"> +<glossterm +>wrapping</glossterm> +<glossdef +><para +>Wrapping is what happens when the turtle draws something that is to big to fix in on the canvas and wrapping is set <quote +>on</quote +>. <screenshot +> <screeninfo +>This is what happens when wrapping is <quote +>on</quote +></screeninfo +> <mediaobject +> <imageobject +> <imagedata fileref="wrapping.png" format="PNG"/> </imageobject +> <textobject +> <phrase +>An example of wrapping</phrase +> </textobject +> </mediaobject +> </screenshot +> When the turtle moves off a border of the canvas it is instantly taken to the opposite border so it can continue its move. This way the turtle will always stay on the screen while it moves. This happens when wrapping is on.</para> +<para +>Wrapping can be turned on and off with the <userinput +>wrapon</userinput +> and <userinput +>wrapoff</userinput +> commands. When &kturtle; starts wrapping is turned on by default.</para +></glossdef> +</glossentry> + +</glosslist> + +</chapter>
\ No newline at end of file diff --git a/tde-i18n-en_GB/docs/kdeedu/kturtle/index.cache.bz2 b/tde-i18n-en_GB/docs/kdeedu/kturtle/index.cache.bz2 Binary files differnew file mode 100644 index 00000000000..966f31c3551 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kturtle/index.cache.bz2 diff --git a/tde-i18n-en_GB/docs/kdeedu/kturtle/index.docbook b/tde-i18n-en_GB/docs/kdeedu/kturtle/index.docbook new file mode 100644 index 00000000000..d9eed1f3758 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kturtle/index.docbook @@ -0,0 +1,305 @@ +<?xml version="1.0" ?> +<!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" "dtd/kdex.dtd" [ + <!ENTITY kturtle "KTurtle"> + <!ENTITY kapp "&kturtle;" +><!-- replace kturtle here --> + <!ENTITY kappname "&kturtle;"> + <!ENTITY package "kdeedu"> + <!ENTITY logo "Logo"> + <!ENTITY % addindex "IGNORE"> + <!ENTITY % British-English "INCLUDE" +><!-- change language only here --> + <!ENTITY using-kturtle SYSTEM "using-kturtle.docbook"> + <!ENTITY getting-started SYSTEM "getting-started.docbook"> + <!ENTITY programming-reference SYSTEM "programming-reference.docbook"> + <!ENTITY translator-guide SYSTEM "translator-guide.docbook"> + <!ENTITY glossary SYSTEM "glossary.docbook"> +]> + +<book lang="&language;"> + +<bookinfo> +<title +>The &kturtle; Handbook</title> + +<authorgroup> +<author +><firstname +>Cies</firstname +> <surname +>Breijs</surname +> <affiliation +> <address +><email +>cies # showroommama ! nl</email +></address> +</affiliation> +</author> +<author +><firstname +>Anne-Marie</firstname +> <surname +>Mahfouf</surname +> <affiliation +> <address +><email +>annma@kde.org</email +></address> +</affiliation> +</author> +</authorgroup> + +<othercredit role="translator" +><firstname +>Andrew</firstname +><surname +>Coles</surname +><affiliation +><address +><email +>andrew_coles@yahoo.co.uk</email +></address +></affiliation +><contrib +>Conversion to British English</contrib +></othercredit +> + +<copyright> +<year +>2004</year> +<holder +>Cies Breijs</holder> +</copyright> + +<legalnotice +>&FDLNotice;</legalnotice> + +<date +>2004-10-5</date> +<releaseinfo +>0.2.1</releaseinfo> + +<abstract> +<para +>&kturtle; is an educational programming environment using the &logo; programming language. </para> +</abstract> + +<keywordset> +<keyword +>KDE</keyword> +<keyword +>kdeedu</keyword> +<keyword +>KTurtle</keyword> +<keyword +>education</keyword> +<keyword +>language</keyword> +<keyword +>native</keyword> +<keyword +>programming</keyword> +<keyword +>code</keyword> +<keyword +>Logo</keyword> +<keyword +>instructions</keyword> +<keyword +>turtle</keyword> +</keywordset> + +</bookinfo> + +<chapter id="introduction"> +<title +>Introduction</title> + +<para +>&kturtle; is an educational programming environment using the &logo; programming language. It tries to make programming as easy and accessible as possible. This makes &kturtle; suitable for teaching kids the basics of maths, geometry and... programming. The commands used to program are in the style of the &logo; programming language. The unique feature of &logo; is that the commands are often translated into the speaking language of the programmer.</para> + +<para +>&kturtle; is named after <quote +>the turtle</quote +> that plays a central role in the programming environment. The user programs the turtle, using the &logo; commands, to draw a picture on <link linkend="the-canvas" +>the canvas</link +>.</para> + +<sect1 id="what-is-logo"> +<title +>What is &logo;?</title> +<para +>The first version &logo; programming language was created by Seymour Papert of MIT Artificial Intelligence Laboratory in 1967 as an offshoot of the LISP programming language. From then many versions of &logo; have been released. By 1980 &logo; was gaining momentum, with versions for MSX, Commodore, Atari, Apple II and IBM PC systems. These versions were mainly for educational purposes. LCSI released <application +>MacLogo</application +> in 1985 as a tool for professional programmers, but it never caught on. MIT is still maintaining a site on &logo; which can be found on <ulink url="http://el.media.mit.edu/logo-foundation/" +>http://el.media.mit.edu/logo-foundation/</ulink +>.</para> + +<para +>Today there are several versions of &logo; around which can easily be found on <ulink url="http://el.media.mit.edu/logo-foundation/" +>MIT's &logo; site</ulink +> and by a simple <ulink url="http://www.google.com/search?q=logo+programming+kids" +>Google search</ulink +>. This version of &logo; (&kturtle;) is only focused on the educational qualities of the programming language and will not try to suit professional programmers' needs.</para> +</sect1> + +<sect1 id="features-of-kturtle"> +<title +>Features of &kturtle;</title> +<para +>&kturtle; has some nice features that make starting to program a breeze. See here some of the highlights of &kturtle; feature set: <itemizedlist> +<listitem +><para +>An integrated &logo; interpreter, so no need to download any other program. </para +></listitem> +<listitem +><para +>A powerful editor for the &logo; commands with intuitive syntax highlighting, line numbering and more. </para +></listitem> +<listitem +><para +><link linkend="the-canvas" +>The canvas</link +> can be saved as an image or printed. </para +></listitem> +<listitem +><para +>Context help for all &logo; commands: Just press <keysym +>F1</keysym +>. </para +></listitem> +<listitem +><para +>The &logo; commands are fully translatable (currently only English, Dutch, French, German and Swedish are supported). </para +></listitem> +<listitem +><para +>Full-screen mode. </para +></listitem> +<listitem +><para +>Many integrated, internationalised example &logo; programs make it easy to get started. </para +></listitem> +</itemizedlist> +</para> +</sect1> +</chapter> + +&using-kturtle; + +&getting-started; + +&programming-reference; + +&glossary; + +&translator-guide; + +<chapter id="credits"> + +<title +>Credits and Licence</title> + +<para +>&kturtle; </para> +<para +>Program copyright 2003-2004 Cies Breijs <email +>cies # showroommama ! nl</email +></para> +<para +>Contributors: <itemizedlist> +<listitem +><para +>Coding help, editor part: Anne-Marie Mahfouf <email +>annma@kde.org</email +></para> +</listitem> +<listitem +><para +>Author of <application +>wsbasic</application +> (<ulink url="http://wsbasic.sourceforge.net" +>http://wsbasic.sourceforge.net</ulink +>) which is the base for the interpreter of &kturtle;: Walter Schreppers <email +>Walter.Schreppers@ua.ac.be</email +></para> +</listitem> +<listitem +><para +>German Data Files: Matthias Meßmer <email +>bmlmessmer@web.de</email +></para> +</listitem> +<listitem +><para +>Swedish Data Files: Stefan Asserhäll <email +>stefan.asserhal@telia.com</email +></para> +</listitem> +</itemizedlist> +</para> + +<para +>Documentation copyright 2004 <itemizedlist> +<listitem +><para +>Cies Briej <email +>cies # showroommama ! nl</email +> </para +></listitem> +<listitem +><para +>Anne-Marie Mahfouf <email +>annma@kde.org</email +> </para +></listitem> +<listitem +><para +>Some proofreading changes by &Philip.Rodrigues; &Philip.Rodrigues.mail;</para> +</listitem> +<listitem +><para +>Updated translation how-to and some proofreading changes by Andrew Coles <email +>andrew_coles@yahoo.co.uk</email +></para> +</listitem> + +</itemizedlist> +</para> +<para +>Andrew Coles<email +>andrew_coles@yahoo.co.uk</email +></para +> +&underFDL; &underGPL; </chapter> + + + +<appendix id="installation"> +<title +>Installation</title> + +<sect1 id="getting-kturtle"> +<title +>How to obtain &kturtle;</title> +&install.intro.documentation; </sect1> + +<sect1 id="compilation"> +<title +>Compilation and Installation</title> +&install.compile.documentation; </sect1> + +</appendix> + +&documentation.index; +</book> +<!-- +Local Variables: +mode: sgml +sgml-minimize-attributes:nil +sgml-general-insert-case:lower +sgml-indent-step:0 +sgml-indent-data:nil +End: +-->
\ No newline at end of file diff --git a/tde-i18n-en_GB/docs/kdeedu/kturtle/programming-reference.docbook b/tde-i18n-en_GB/docs/kdeedu/kturtle/programming-reference.docbook new file mode 100644 index 00000000000..5e459b562f1 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kturtle/programming-reference.docbook @@ -0,0 +1,1209 @@ +<chapter id="reference"> +<title +>&kturtle;'s &logo; Programming Reference</title> + +<sect1 id="commands"> +<title +>Commands</title> +<para +>Using commands you tell the turtle or &kturtle; to do something. Some commands need input, some give output. In this section we explain all the commands that can be used in &kturtle;.</para> + +<sect2 id="moving-the-turtle"> +<title +>Moving the turtle</title> +<para +>There are several commands to move the turtle over the screen.</para> + + <variablelist> + <anchor id="forward"/> + <varlistentry> + <term +>forward</term> + <listitem +><para +><screen +>forward X</screen> +<userinput +>forward</userinput +> moves the turtle forward by the amount of X pixels. When the pen is down the turtle will leave a trail. <userinput +>forward</userinput +> can be abbreviated to <userinput +>fw</userinput +></para +></listitem> + </varlistentry> + </variablelist> + <variablelist> + <anchor id="backward"/> + <varlistentry> + <term +>backward</term> + <listitem +><para +><screen +>backward X</screen> +<userinput +>backward</userinput +> moves the turtle backward by the amount of X pixels. When the pen is down the turtle will leave a trail. <userinput +>backward</userinput +> can be abbreviated to <userinput +>bw</userinput +>.</para +></listitem> + </varlistentry> + </variablelist> + <variablelist> + <anchor id="turnleft"/> + <varlistentry> + <term +>turnleft</term> + <listitem +><para +><screen +>turnleft X</screen> +<userinput +>turnleft</userinput +> commands the turtle to turn an amount of X degrees to the left. <userinput +>turnleft</userinput +> can be abbreviated to <userinput +>tl</userinput +>.</para +></listitem> + </varlistentry> + </variablelist> + <variablelist> + <anchor id="turnright"/> + <varlistentry> + <term +>turnright</term> + <listitem +><para +><screen +>turnright X</screen> +<userinput +>turnright</userinput +>the turtle to turn an amount of X degrees to the right. <userinput +>turnright</userinput +> can be abbreviated to <userinput +>tr</userinput +>.</para +></listitem> + </varlistentry> + </variablelist> + <variablelist> + <anchor id="direction"/> + <varlistentry> + <term +>direction</term> + <listitem +><para +><screen +>direction X</screen> +<userinput +>direction</userinput +> set the turtle's direction to an amount of X degrees counting from zero, and thus is not relative to the turtle's previous direction. <userinput +>direction</userinput +> can be abbreviated to <userinput +>dir</userinput +>.</para +></listitem> + </varlistentry> + </variablelist> + <variablelist> + <anchor id="center"/> + <varlistentry> + <term +>centre</term> + <listitem +><para +><screen +>centre</screen> +<userinput +>centre</userinput +> moves the turtle to the centre on the canvas.</para +></listitem> + </varlistentry> + </variablelist> + <variablelist> + <anchor id="go"/> + <varlistentry> + <term +>go</term> + <listitem +><para +><screen +>go X,Y</screen> +<userinput +>go</userinput +> commands the turtle to go to a certain place on the canvas. This place is X <glossterm linkend="pixels" +>pixels</glossterm +> from the left of the canvas, and Y <glossterm linkend="pixels" +>pixels</glossterm +> form the top of the canvas. Note that using the <userinput +>go</userinput +> command the turtle will not draw a line.</para +></listitem> + </varlistentry> + </variablelist> + <variablelist> + <anchor id="gox"/> + <varlistentry> + <term +>gox</term> + <listitem +><para +><screen +>gox X</screen> +<userinput +>gox</userinput +> using this command the turtle will move to X <glossterm linkend="pixels" +>pixels</glossterm +> from the left of the canvas whilst staying at the same height.</para +></listitem> + </varlistentry> + </variablelist> + <variablelist> + <anchor id="goy"/> + <varlistentry> + <term +>goy</term> + <listitem +><para +><screen +>goy Y</screen> +<userinput +>gox</userinput +> using this command the turtle will move to Y <glossterm linkend="pixels" +>pixels</glossterm +> from the top of the canvas whilst staying at the same distance from the left border of the canvas.</para +></listitem> + </varlistentry> + </variablelist> +</sect2> + +<sect2 id="pen"> +<title +>The turtle has a pen</title> +<para +>The turtle has a pen that draws a line when the turtle moves. There are a few commands to control the pen. In this section we explain these commands.</para> + <variablelist> + <anchor id="penup"/> + <varlistentry> + <term +>penup</term> + <listitem +><para +><screen +>penup</screen> +<userinput +>penup</userinput +> lifts the pen from the canvas. When the pen is <quote +>up</quote +> no line will be drawn when the turtle moves. See also <userinput +>pendown</userinput +>. <userinput +>penup</userinput +> can be abbreviated to <userinput +>pu</userinput +>.</para +></listitem> + </varlistentry> + </variablelist> + <variablelist> + <anchor id="pendown"/> + <varlistentry> + <term +>pendown</term> + <listitem +><para +><screen +>pendown</screen> +<userinput +>pendown</userinput +> presses the pen down on the canvas. When the pen is press <quote +>down</quote +> on the canvas a line will be drawn when the turtle moves. See also <userinput +>penup</userinput +>.<userinput +>pendown</userinput +> can be abbreviated to <userinput +>pd</userinput +>.</para +></listitem> + </varlistentry> + </variablelist> + <variablelist> + <anchor id="penwidth"/> + <varlistentry> + <term +>penwidth</term> + <listitem +><para +><screen +>penwidth X</screen> +<userinput +>penwidth</userinput +> sets the width of the pen (the line width) to an amount of X <glossterm linkend="pixels" +>pixels</glossterm +>. <userinput +>penwidth</userinput +> can be abbreviated to <userinput +>pw</userinput +>.</para +></listitem> + </varlistentry> + </variablelist> + <variablelist> + <anchor id="pencolor"/> + <varlistentry> + <term +>pencolour</term> + <listitem +><para +><screen +>pencolour R,G,B</screen> +<userinput +>pencolor</userinput +> sets the color of the pen. <userinput +>pencolor</userinput +> takes an <glossterm linkend="rgb" +>RGB combination</glossterm +> as input. <userinput +>pencolor</userinput +> can be abbreviated to <userinput +>pc</userinput +>.</para +></listitem> + </varlistentry> + </variablelist> +</sect2> + +<sect2 id="canvas"> +<title +>Commands to control the canvas</title> +<para +>There are several commands to control the canvas.</para> + <variablelist> + <anchor id="canvassize"/> + <varlistentry> + <term +>canvassize</term> + <listitem +><para +><screen +>canvassize X,Y</screen> +With the <userinput +>canvassize</userinput +> command you can set the size of the canvas. It takes X and Y as input, where X is the new canvas width in <glossterm linkend="pixels" +>pixels</glossterm +>, and Y is the new height of the canvas in <glossterm linkend="pixels" +>pixels</glossterm +>. <userinput +>canvassize</userinput +> can be abbreviated to <userinput +>cs</userinput +>.</para +></listitem> + </varlistentry> + </variablelist> + <variablelist> + <anchor id="canvascolor"/> + <varlistentry> + <term +>canvascolour</term> + <listitem +><para +><screen +>canvascolour R,G,B</screen> +<userinput +>canvascolor</userinput +> set the color of the canvas. <userinput +>canvascolor</userinput +> takes an <glossterm linkend="rgb" +>RGB combination</glossterm +> as input. <userinput +>canvascolor</userinput +> can be abbreviated to <userinput +>cc</userinput +>.</para +></listitem> + </varlistentry> + </variablelist> + <variablelist> + <anchor id="wrapon"/> + <varlistentry> + <term +>wrapon</term> + <listitem +><para +><screen +>wrapon</screen> +With the <userinput +>wrapon</userinput +> command you can set <glossterm linkend="wrapping" +>wrapping</glossterm +> <quote +>on</quote +> for the canvas. Please see the glossary if you want to know what <glossterm linkend="wrapping" +>wrapping</glossterm +> is.</para +></listitem> + </varlistentry> + </variablelist> + <variablelist> + <anchor id="wrapoff"/> + <varlistentry> + <term +>wrapoff</term> + <listitem +><para +><screen +>wrapoff</screen> +With the <userinput +>wrapoff</userinput +> command you can set <glossterm linkend="wrapping" +>wrapping</glossterm +> <quote +>off</quote +> for the canvas: this means the turtle can move off the canvas and can get <quote +>lost</quote +>. Please see the glossary if you want to know what <glossterm linkend="wrapping" +>wrapping</glossterm +> is.</para +></listitem> + </varlistentry> + </variablelist> +</sect2> + +<sect2 id="clean"> +<title +>Commands to clean up</title> +<para +>There are two commands to clean up the canvas after you have made a mess.</para> + <variablelist> + <anchor id="clear"/> + <varlistentry> + <term +>clear</term> + <listitem +><para +><screen +>clear</screen> +With <userinput +>clear</userinput +> you can clean all drawings from the canvas. All other things remain: the position and angle of the turtle, the canvascolor, the visibility of the turtle, and the canvas size. <userinput +>clear</userinput +> can be abbreviated to <userinput +>ccl</userinput +>.</para +></listitem> + </varlistentry> + </variablelist> + <variablelist> + <anchor id="reset"/> + <varlistentry> + <term +>reset</term> + <listitem +><para +><screen +>reset</screen> +<userinput +>reset</userinput +> cleans much more thoroughly than the <userinput +>clear</userinput +> command. After a <userinput +>reset</userinput +> command everything is like is was when you had just started &kturtle;. The turtle is positioned at the middle of the screen, the canvas color is white, and the turtle draws a black line on the canvas.</para +></listitem> + </varlistentry> + </variablelist> +</sect2> + +<sect2 id="sprites"> +<title +>The turtle is a sprite</title> +<para +>Many people do not know what sprites are, so here a short explanation: sprites are small pictures that can be moved around the screen. (for more info see the glossary on <glossterm linkend="sprites" +>sprites</glossterm +>). So the turtle is a sprite.</para> +<para +>Next you will find a full overview on all commands to work with sprites.</para> +<para +>[The current version of &kturtle; does not yet support the use of sprites other than the turtle. With future versions you will be able to change the turtle into something of your own design]</para> + <variablelist> + <anchor id="show"/> + <varlistentry> + <term +>show</term> + <listitem +><para +><screen +>show</screen> +<userinput +>show</userinput +> makes the turtle visible again after it has been hidden.<userinput +>show</userinput +> can be abbreviated to <userinput +>ss</userinput +>.</para +></listitem> + </varlistentry> + </variablelist> + <variablelist> + <anchor id="hide"/> + <varlistentry> + <term +>hide</term> + <listitem +><para +><screen +>hide</screen> +<userinput +>hide</userinput +> hides the turtle. This can be used if the turtle does not fit in your drawing.<userinput +>hide</userinput +> can be abbreviated to <userinput +>sh</userinput +>.</para +></listitem> + </varlistentry> + </variablelist> +</sect2> + +<sect2 id="writing"> +<title +>Can the turtles write text?</title> +<para +>The answer is: <quote +>yes</quote +>. The turtle can write: it writes just about everything you command it to.</para> + <variablelist> + <anchor id="print"/> + <varlistentry> + <term +>print</term> + <listitem +><para +><screen +>print X</screen> +The <userinput +>print</userinput +> command is used to command the turtle to write something on the canvas. <userinput +>print</userinput +> takes numbers and strings as input. You can <userinput +>print</userinput +> various numbers and strings using the <quote +>+</quote +> symbol. See here a small example: <screen +>year = 2004 +author = "Cies" +print "KTurtle was made in " + year + " by " + author +</screen> + </para +></listitem> + </varlistentry> + </variablelist> + <variablelist> + <anchor id="fontsize"/> + <varlistentry> + <term +>fontsize</term> + <listitem +><para +><screen +>fontsize X</screen> +<userinput +>fontsize</userinput +> sets the size of the font that is used by <userinput +>print</userinput +>. <userinput +>fontsize</userinput +> takes one input which should be a number. The size is set in <glossterm linkend="pixels" +>pixels</glossterm +>.</para +></listitem> + </varlistentry> + </variablelist> +</sect2> + +<sect2 id="dice"> +<title +>A command that rolls a dice for you</title> +<para +>There is one command that rolls a dice for you</para> + <variablelist> + <anchor id="random"/> + <varlistentry> + <term +>random</term> + <listitem +><para +><screen +>random X,Y</screen> +<userinput +>random</userinput +> is a command that takes input and gives output. As input are required two numbers, the first (X) sets the minimum output, the second (Y) sets the maximum. The output is a randomly chosen number that is equal or greater then the minimum and equal or smaller than the maximum. Here a small example: <screen> +repeat 500 [ + x = random 1,20 + forward x + turnleft 10 - x +] +</screen +> Using the <userinput +>random</userinput +> command you can add a bit of chaos to your program.</para +></listitem> + </varlistentry> + </variablelist> +</sect2> +</sect1> + +<sect1 id="containers"> +<title +>Containers</title> +<para +>Containers are letters or words that can be used by the programmer to store a number or a text. Containers that contain a number are called <link linkend="variables" +>variables</link +>, containers that can contain text are called <link linkend="strings" +>strings</link +>.</para> + +<para +>Containers that are not used yet are 0 by default. An example: <screen> +print N +</screen +> This will print a 0. </para> + +<sect2 id="variables"> +<title +>Variables: number containers</title> +<para +>Let us start with an example: <screen> +x = 3 +print x +</screen +> In the first line the letter <userinput +>x</userinput +> made into a variable (number container). As you see the value of the variable <userinput +>x</userinput +> is set to 3. On the second line the value is printed.</para> +<para +>Note that if we wanted to print an <quote +>x</quote +> that we should have written <screen +>print "x" +</screen> +</para> +<para +>That was easy, now a bit harder example: <screen> +A = 2004 +B = 25 +AB = A + B + +# the next command prints "2029" +print AB +backward 30 +# the next command prints "2004 plus 25" +print "" + A + " plus " + B +backward 30 +# the next command prints "1979" +print A - B +</screen +> In the first two lines the variables <userinput +>A</userinput +> and <userinput +>B</userinput +> are set to 2004 and 25. On the third line the variable <userinput +>AB</userinput +> is set to <userinput +>A + B</userinput +>, which is 2029. The rest of the example consists of 3 <userinput +>print</userinput +> commands with <userinput +>backward 30</userinput +> in between. The <userinput +>backward 30</userinput +> is there to make sure every output is on a new line. In this example you also see that variables can be used in <link linkend="math" +>mathematical calculations</link +>.</para> +</sect2> + +<sect2 id="strings"> +<title +>Strings: text containers</title> +<para +>Strings are a lot like variables. The biggest difference is that strings cannot be used in <link linkend="math" +>mathematical calculations</link +> and <link linkend="questions" +>questions</link +>. An example of the use of strings: <screen> +x = "Hello " +name = inputwindow "Please enter your name..." +print x + name + ", how are you?" +</screen +> On the first line the string <userinput +>x</userinput +> is set to <quote +>Hello </quote +>. On the second line the string <userinput +>name</userinput +> is set to the output of the <userinput +>inputwindow</userinput +> command. On the third line the program prints a composition of three strings on the canvas.</para> +<para +>This program ask you to enter your name. When you, for instance, enter the name <quote +>Paul</quote +>, the program prints <quote +>Hello Paul, how are you?</quote +>. Please note that the plus (+) is the only math symbol that you can use with strings.</para> +</sect2> +</sect1> + +<sect1 id="math"> +<title +>Can the Turtle do maths?</title> +<para +>Yes, &kturtle; will do your math. You can add (+), substract (-), multiply (*), and divide (/). Here is an example in which we use all of them: <screen> +a = 20 - 5 +b = 15 * 2 +c = 30 / 30 +d = 1 + 1 +print "a: "+a+", b: "+b+", c: "+c+", d: "+d +</screen +> Do you know what value a, b, c and d have?</para> +<para +>If you just want a simple calculation to be done you can do something like this: <screen +>print 2004-12 +</screen +></para> +<para +>Now an example with brackets: <screen> +print ( ( 20 - 5 ) * 2 / 30 ) + 1 +</screen +> The expressions inside brackets will be calculated first. In this example, 20-5 will be calculated, then multiplied by 2, divided by 30, and then 1 is added (giving 2).</para> +</sect1> + +<sect1 id="questions"> +<title +>Asking questions, getting answers...</title> +<para +><link linkend="if" +><userinput +>if</userinput +></link +> and <link linkend="while" +><userinput +>while</userinput +></link +> are <link linkend="controlling-execution" +>execution controllers</link +> that we will discuss in the next section. In this section we use the <userinput +>if</userinput +> command to explain questions.</para> +<para +>A simple example of questions: <screen> +x = 6 +if x > 5 [ + print "hello" +] +</screen +> In this example the question is the <userinput +>x > 5</userinput +> part. If the answer to this question is <quote +>true</quote +> the code between the brackets will be executed. Questions are an important part of programming and often used together with <link linkend="controlling-execution" +>execution controllers</link +>, like <link linkend="if" +><userinput +>if</userinput +></link +>. All numbers and <link linkend="variables" +>variables</link +> (number containers) can be compared to each other with questions.</para> +<para +>Here are all possible questions: <table> +<title +>Types of questions</title> +<tgroup cols="3"> +<tbody> +<row> +<entry +><userinput +>a == b</userinput +></entry> +<entry +>equals</entry> +<entry +>answer is <quote +>true</quote +> if <userinput +>a</userinput +> equals <userinput +>b</userinput +></entry> +</row> +<row> +<entry +><userinput +>a != b</userinput +></entry> +<entry +>not-equal</entry> +<entry +>answer is <quote +>true</quote +> if <userinput +>a</userinput +> does not equal <userinput +>b</userinput +></entry> +</row> +<row> +<entry +><userinput +>a > b</userinput +></entry> +<entry +>greater than</entry> +<entry +>answer is <quote +>true</quote +> if <userinput +>a</userinput +> is greater than <userinput +>b</userinput +></entry> +</row> +<row> +<entry +><userinput +>a < b</userinput +></entry> +<entry +>smaller than</entry> +<entry +>answer is <quote +>true</quote +> if <userinput +>a</userinput +> is smaller than <userinput +>b</userinput +></entry> +</row> +<row> +<entry +><userinput +>a >= b</userinput +></entry> +<entry +>greater than or equals</entry> +<entry +>answer is <quote +>true</quote +> if <userinput +>a</userinput +> is greater than or equals <userinput +>b</userinput +></entry> +</row> +<row> +<entry +><userinput +>a <= b</userinput +></entry> +<entry +>smaller than or equals</entry> +<entry +>answer is <quote +>true</quote +> if <userinput +>a</userinput +> is smaller than or equals <userinput +>b</userinput +></entry> +</row> +</tbody> +</tgroup> +</table> +</para> +<para +>Questions can also be glued to each other with <quote +>question glue</quote +>, this way a few questions can become one big question. <screen> +a = 1 +b = 5 +if a < 5 and b == 5 [ + print "hello" +] +</screen +> <anchor id="question-glue"/>In this example the glue-word <userinput +>and</userinput +> is used to glue 2 questions (<userinput +>a < 5</userinput +>, <userinput +>b == 5</userinput +>) together. If one side of the <userinput +>and</userinput +> would answer <quote +>false</quote +> the whole question would answer <quote +>false</quote +>, because with the glue-word <userinput +>and</userinput +> both sides need to be <quote +>true</quote +> in order to answer <quote +>true</quote +>.</para> +<para +><userinput +>and</userinput +> is not the only glue-word there are two others. They are all in the next table: <table> +<title +>Question glue-words</title> +<tgroup cols="2"> +<tbody> +<row> +<entry +><userinput +>and</userinput +></entry> +<entry +>both sides need to be <quote +>true</quote +> in order to answer <quote +>true</quote +></entry> +</row> +<row> +<entry +><userinput +>or</userinput +></entry> +<entry +>if one of the sides is <quote +>true</quote +> the answer is <quote +>true</quote +></entry> +</row> +<row> +<entry +><userinput +>not</userinput +></entry> +<entry +>only if both of the sides are <quote +>false</quote +> the answer is <quote +>false</quote +></entry> +</row> +</tbody> +</tgroup> +</table> +</para> +</sect1> + +<sect1 id="controlling-execution"> +<title +>Controlling execution</title> +<para +>The execution controllers enable you — as their name implies — to control execution.</para> + +<sect2 id="easy"> +<title +>Have the turtle wait</title> +<para +>If you have done some programming in &kturtle; you have might noticed that the turtle can be very quick at drawing. This command makes the turtle wait for a given amount of time.</para> + <variablelist> + <anchor id="wait"/> + <varlistentry> + <term +>wait</term> + <listitem +><para +><screen +>wait X</screen> +<userinput +>wait</userinput +> makes the turtle wait for X seconds. <screen> +repeat 36 [ + forward 5 + turnright 10 + wait 0.5 +] +</screen +> This code draws a circle, but the turtle will wait half a second after each step. This gives the impression of a slow-moving turtle.</para +></listitem> + </varlistentry> + </variablelist> +</sect2> + +<sect2 id="execute-if"> +<title +>Execute "if"</title> +<para +></para> + <variablelist> + <anchor id="if"/> + <varlistentry> + <term +>if</term> + <listitem +><para +><screen +>if <link linkend="questions" +>question</link +> [ ... ]</screen> +The code that is placed between the brackets will only be executed <userinput +>if</userinput +> the answer to the <link linkend="questions" +>question</link +> is <quote +>true</quote +>. Please read for more information on <link linkend="questions" +>questions</link +> in the <link linkend="questions" +>question section</link +>. <screen> +x = 6 +if x > 5 [ + print "x is greater than five!" +] +</screen +> On the first line <userinput +>x</userinput +> is set to 6. On the second line the <link linkend="questions" +>question</link +> <userinput +>x > 5</userinput +> is asked. Since the answer to this question is <quote +>true</quote +> the execution controller <userinput +>if</userinput +> will allow the code between the brackets to be executed</para +></listitem> + </varlistentry> + </variablelist> +</sect2> + +<sect2 id="execute-while"> +<title +>Execute "while"</title> +<para +></para> + <variablelist> + <anchor id="while"/> + <varlistentry> + <term +>while</term> + <listitem +><para +><screen +>while <link linkend="questions" +>question</link +> [ ... ]</screen> +The execution controller <userinput +>while</userinput +> is a lot like <link linkend="if" +><userinput +>if</userinput +></link +>. The difference is that <userinput +>while</userinput +> keeps repeating the code between the brackets till the answer to the <link linkend="questions" +>question</link +> is <quote +>false</quote +>. <screen> +x = 1 +while x < 5 [ + forward 10 + wait 1 + x = x + 1 +] +</screen +> On the first line <userinput +>x</userinput +> is set to 1. On the second line the <link linkend="questions" +>question</link +> <userinput +>x < 5</userinput +> is asked. Since the answer to this question is <quote +>true</quote +> the execution controller <userinput +>while</userinput +> starts executing the code between the brackets till the answer to the <link linkend="questions" +>question</link +> is <quote +>false</quote +>. In this case the code between the brackets will be executed 4 times, because every time the fifth line is executed <userinput +>x</userinput +> increases by 1..</para +></listitem> + </varlistentry> + </variablelist> +</sect2> + +<sect2 id="if-else"> +<title +>If not, in other words: "else"</title> +<para +></para> + <variablelist> + <anchor id="else"/> + <varlistentry> + <term +>else</term> + <listitem +><para +><screen +>if question [ ... ] else [ ... ]</screen> +<userinput +>else</userinput +> can be used in addition to the execution controller <link linkend="if" +><userinput +>if</userinput +></link +>. The code between the brackets after <userinput +>else</userinput +> is only executed if the answer to the <link linkend="questions" +>question</link +> that is asked is <quote +>false</quote +>. <screen> +x = 4 +if x > 5 [ + print "x is greater than five!" +] else [ + print "x is smaller than six!" +] +</screen +> The <link linkend="questions" +>question</link +> asks if <userinput +>x</userinput +> is greater than 5. Since <userinput +>x</userinput +> is set to 4 on the first line the answer to the question is <quote +>false</quote +>. This means the code between the brackets after <userinput +>else</userinput +> gets executed.</para +></listitem> + </varlistentry> + </variablelist> +</sect2> + +<sect2 id="for-loop"> +<title +>The "for" loop</title> +<para +></para> + <variablelist> + <anchor id="for"/> + <varlistentry> + <term +>for</term> + <listitem +><para +><screen +>for <userinput +>start point</userinput +> to <userinput +>end point</userinput +> [ ... ]</screen> +The <userinput +>for</userinput +> loop is a <quote +>counting loop</quote +>, &ie; it keeps count for you. <screen> +for x = 1 to 10 [ + print x * 7 + forward 15 +] +</screen +> Every time the code between the brackets is executed the <userinput +>x</userinput +> is increased by 1, till <userinput +>x</userinput +> reaches the value of 10. The code between the brackets prints the <userinput +>x</userinput +> multiplied by 7. After this program finishes its execution you will see the times table of 7 on the canvas.</para +></listitem> + </varlistentry> + </variablelist> +</sect2> + +</sect1> + + +<sect1 id="learn"> +<title +>Create your own commands</title> +<para +><userinput +>learn</userinput +> is a very special command, because it is used to create your own commands. The command you create can take <glossterm linkend="input-output" +>input</glossterm +> and return <glossterm linkend="input-output" +>output</glossterm +>. Let us take a look at how a new command is created: <screen> +learn circle (x) [ + repeat 36 [ + forward x + turnleft 10 + ] +] +</screen +> The new command is called <userinput +>circle</userinput +>. <userinput +>circle</userinput +> takes one <glossterm linkend="input-output" +>input</glossterm +>, a number, to set the size of the circle. <userinput +>circle</userinput +> returns no <glossterm linkend="input-output" +>output</glossterm +>. The <userinput +>circle</userinput +> command can now be used like a normal command in the rest of the code. See this example: <screen +>learn circle (x) [ + repeat 36 [ + forward x + turnleft 10 + ] + ] + + go 30,30 + circle(20) + + go 40,40 + circle(50) +</screen> +</para> +<para +>In the next example a command with a return value is created. <screen> +reset + +learn multiplyBySelf (n) [ + r = n * 1 + r = n * n + return r +] +i = inputwindow "Please enter a number and press OK" +print i + " multiplied by itself is: " + multiplyBySelf (i) +</screen +> In this example a new command called <userinput +>multiplyBySelf</userinput +> is created. The input of this command is multiplied by it self and then returned, using the <anchor id="return"/><userinput +>return</userinput +> command. The <userinput +>return</userinput +> command is the way to output a value from a function you have created. </para> +</sect1> + +</chapter> diff --git a/tde-i18n-en_GB/docs/kdeedu/kturtle/translator-guide.docbook b/tde-i18n-en_GB/docs/kdeedu/kturtle/translator-guide.docbook new file mode 100644 index 00000000000..2b6f0de1859 --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kturtle/translator-guide.docbook @@ -0,0 +1,223 @@ +<chapter id="translators"> +<title +>Translator's Guide to &kturtle;</title> +<para +>As you know, one of the great features of &logo; is that the &logo; commands can be translated in your own language. This makes it easier for a child to understand the commands. For a new language, there are 3 files to translate: first the keywords file (or commands) then the logo-highlight-style file and finally the examples. </para> +<sect1 id="make_directory"> +<title +>Creating a Directory to hold the Translated Files</title> +<para +>First, you need to create a directory to store the translated files. Create a directory called <filename class="directory" +>kde-i18n/<replaceable +>code</replaceable +>/data/kdeedu/kturtle/</filename +> in your KDE CVS directory, where <replaceable +>code</replaceable +> is your country code (the 2- or 4- letter <acronym +>ISO</acronym +> code). </para> +<para +>Copy the <filename +>Makefile.am</filename +> file from <filename class="directory" +>kdeedu/kturtle/data/</filename +> into this directory. Open it using your favorite text editor, replace all instances of <quote +>en_US</quote +> in the file with your country code (the one used above), and save the file. </para> +</sect1> +<sect1 id="commands_trans"> +<title +>How To Translate the &logo; Keywords (commands)</title> +<para> +<itemizedlist> +<listitem +><para +>Copy the <filename +>logokeywords.en_US.xml</filename +> file from <filename class="directory" +>kdeedu/kturtle/data/</filename +> to the directory you have just created, and rename it to <filename +>logokeywords.<replaceable +>code</replaceable +>.xml</filename +> where <replaceable +>code</replaceable +> is your country code (the 2- or 4- letter <acronym +>ISO</acronym +> code). </para> +</listitem> +<listitem +><para +>Translate the contents of the <sgmltag class="starttag" +>keyword</sgmltag +> tag (&ie; the information between <sgmltag class="starttag" +>keyword</sgmltag +> and <sgmltag class="endtag" +>keyword</sgmltag +>) into your own language wherever possible. Also, translate the contents of the <sgmltag class="starttag" +>alias</sgmltag +> tag, (&ie; the information between the <sgmltag class="starttag" +>alias</sgmltag +> and <sgmltag class="endtag" +>alias</sgmltag +>): these are used as shortcuts for the keyword.</para> +<para +>For example, translate <quote +>while</quote +> in: <sgmltag class="starttag" +>keyword</sgmltag +>while<sgmltag class="endtag" +>keyword</sgmltag +> </para> +<para +>Please do not translate anything else and do not translate the English words in <sgmltag class="starttag" +>command name="english_word"</sgmltag +>: these must stay in English. </para> +</listitem> +<listitem +><para +>Save your file as <acronym +>UTF-8</acronym +> (in &kate;, use <guimenuitem +>Save As...</guimenuitem +> and change to <guilabel +>utf8</guilabel +> in the box on the right of the file name). </para> +</listitem> +<listitem +><para +>Commit your file (add your filename in the <filename +>Makefile.am</filename +>) or send it to Anne-Marie. </para> +</listitem> +<listitem +><para +>In case of any doubt, please contact Anne-Marie Mahfouf <email +>annemarie.mahfouf@free.fr</email +> for more information.</para> +</listitem> +</itemizedlist> +</para> +</sect1> + +<sect1 id="examples_syntax"> +<title +>How To Translate the Syntax Highlighting Files</title> +<para> +<itemizedlist> +<listitem +><para +>Copy the <filename +>logohighlightstyle.en_US.xml</filename +> file from <filename class="directory" +>kdeedu/kturtle/data/</filename +> to the directory you created to store the translated keywords file, and rename it to <filename +>logohighlightstyle.<replaceable +>code</replaceable +>.xml</filename +> where <replaceable +>code</replaceable +> is your country code (the 2- or 4- letter <acronym +>ISO</acronym +> code). </para> +</listitem> +<listitem +><para +>In line 4 of the file, there is <sgmltag class="starttag" +>language name="en_US"</sgmltag +>...: here you change <quote +>en_US</quote +> to your language's <acronym +>ISO</acronym +> code (2 or 4 letters). </para +></listitem> +<listitem +><para +>Translate into your own language the content of the <sgmltag class="starttag" +>item</sgmltag +> tag (&ie; the information between <sgmltag class="starttag" +>item</sgmltag +> and <sgmltag class="endtag" +>item</sgmltag +>). This content must match the <filename +>logokeyword</filename +> file. For example, translate <quote +>while</quote +> in: <sgmltag class="starttag" +>item</sgmltag +> while <sgmltag class="endtag" +>item</sgmltag +> and leave the spaces as they are (one at the beginning and one at the end). Please do not translate anything else. </para +></listitem> +<listitem +><para +>Save your file as <acronym +>UTF-8</acronym +> (in &kate;, use <guimenuitem +>Save As...</guimenuitem +> and change to <guilabel +>utf8</guilabel +> in the box on the right of the file name). </para +></listitem> +<listitem +><para +>Commit your file (add your filename in the <filename +>Makefile.am</filename +>) or send it to Anne-Marie. </para +></listitem> +<listitem +><para +>In case of any doubt, please contact Anne-Marie Mahfouf <email +>annemarie.mahfouf@free.fr</email +> for more information. </para +></listitem> +</itemizedlist> +</para> +</sect1> + +<sect1 id="examples_trans"> +<title +>How To Translate the Examples</title> +<itemizedlist> +<listitem +><para +>Copy the English example files from <filename class="directory" +>kdeedu/kturtle/data/</filename +> to the directory used to store the translated keyword and hilighting files. Translate the filenames of the examples in your directory: this will allow users to easily and quickly understand what the example is about.</para> +</listitem> +<listitem +><para +>Translate the keywords in the examples, using those in the <filename +>logokeywords.xml</filename +> for your language. The keywords file file must be done, first, before translating the examples.</para> +</listitem> +<listitem +><para +>Save your file as <acronym +>UTF-8</acronym +> (in &kate;, use <guimenuitem +>Save As...</guimenuitem +> and change to <guilabel +>utf8</guilabel +> in the box on the right of the file name)</para> +</listitem> +<listitem +><para +>Commit your folder (add a <filename +>Makefile.am</filename +> inside) or send it to Anne-Marie.</para> +</listitem> +<listitem +><para +>In case of any doubt, please contact Anne-Marie Mahfouf, <email +>annemarie.mahfouf@free.fr</email +> for more information.</para> +</listitem> +<listitem +><para +>Finally, if you want, you can add your own examples in this folder.</para> +</listitem> +</itemizedlist> +</sect1> + +</chapter> diff --git a/tde-i18n-en_GB/docs/kdeedu/kturtle/using-kturtle.docbook b/tde-i18n-en_GB/docs/kdeedu/kturtle/using-kturtle.docbook new file mode 100644 index 00000000000..e250da7f1ba --- /dev/null +++ b/tde-i18n-en_GB/docs/kdeedu/kturtle/using-kturtle.docbook @@ -0,0 +1,1025 @@ +<chapter id="using-kturtle"> +<title +>Using &kturtle;</title> + +<screenshot> + <screeninfo +>Here is a screenshot of &kturtle; in action</screeninfo> + <mediaobject> + <imageobject> + <imagedata fileref="mainwindow_flower_nrs.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>&kturtle; Main Window</phrase> + </textobject> + </mediaobject> +</screenshot> + +<para +>The main window of &kturtle; has two main parts: <link linkend="the-code-editor" +>the code editor</link +> (3) on the left where you type the &logo; commands, and <link linkend="the-canvas" +>the canvas</link +> (4) on the right where the instructions are visualized. <link linkend="the-canvas" +>The canvas</link +> is the turtle's playground: it is on the canvas that the turtle actually moves and draws. The three other places on the main window are: <link linkend="the-menubar" +>the menu bar</link +> (1) from where all the actions can be reached, <link linkend="the-toolbar" +>the toolbar</link +> (4) that allows you to quickly select the most used actions, and <link linkend="the-statusbar" +>the statusbar</link +> (5) where you will find feedback on the state of &kturtle;.</para> + +<sect1 id="the-code-editor"> +<title +>The Code Editor</title> +<para +>In the code editor you type the &logo; commands. It has all of the features you would expect from a modern editor. Most of its features are found in the <link linkend="the-edit-menu" +>Edit</link +> and the <link linkend="the-tools-menu" +>Tools</link +> menus. The code editor can be docked on each border of the main window or it can be detached and placed anywhere on your desktop.</para> +<para +>You have several ways to get some code in the editor. The easiest way is to use an already-made example: choose <menuchoice +><guimenu +>File</guimenu +><guimenuitem +>Open Examples</guimenuitem +> </menuchoice +> in the <link linkend="the-file-menu" +>File menu</link +> and click on a file. The filename will tell you what the example is about (⪚ <filename +>square.logo</filename +> will draw a square). The file you choose will be opened in the <link linkend="the-code-editor" +>the code editor</link +>, you can then use <menuchoice +><guimenu +>File</guimenu +><guimenuitem +>Execute Commands</guimenuitem +> </menuchoice +> to run the code if you like.</para> +<para +>You can open &logo; files by choosing <menuchoice +><guimenu +>File</guimenu +><guimenuitem +>Open...</guimenuitem +> </menuchoice +>.</para> +<para +>The third way is to directly type your own code in the editor or to copy/paste some code from this user guide. </para> +<para +>The cursor position is indicated in <link linkend="the-statusbar" +>the statusbar</link +>, on the right with the Line number and Column number. </para> +</sect1> + +<sect1 id="the-canvas"> +<title +>The Canvas</title> +<para +>The canvas is the area where the commands are visualized, where the commands <quote +>draw</quote +> a picture. In other words, it is the turtle's playground. After getting some code in the <link linkend="the-code-editor" +>the code editor</link +>, and executing it using <menuchoice +><guimenu +>File</guimenu +><guimenuitem +>Execute Commands</guimenuitem +> </menuchoice +>, two things can happen: either the code executes fine, and will you most likely see something change on the canvas; or you have made an error in your code and there will be a message telling you what error you made.</para> +<para +>This message should help you to resolve the error.</para> +<para +>The picture that is drawn can be saved as an image (using <menuchoice +><guimenu +>File</guimenu +><guimenuitem +>Save Canvas</guimenuitem +> </menuchoice +>) or printed (using <menuchoice +><guimenu +>File</guimenu +><guimenuitem +>Print...</guimenuitem +> </menuchoice +>).</para> +</sect1> + +<sect1 id="the-menubar"> +<title +>The Menubar</title> +<para +>In the menu bar you find all the actions of &kturtle;. They are in the following groups: <guimenu +>File</guimenu +>, <guimenu +>Edit</guimenu +>, <guimenu +>View</guimenu +>, <guimenu +>Tools</guimenu +>, <guimenu +>Settings</guimenu +>, and <guimenu +>Help</guimenu +>. This section describes them all.</para> + +<sect2 id="the-file-menu"> +<title +>The <guimenu +>File</guimenu +> Menu</title> + <variablelist> + <varlistentry> + <term +><menuchoice +><shortcut +> <keycombo +>&Ctrl;<keycap +>N</keycap +></keycombo +> </shortcut +> <guimenu +>File</guimenu +> <guimenuitem +>New</guimenuitem +> </menuchoice +></term> + <listitem +><para +>Creates a new, empty &logo; file.</para +></listitem> + </varlistentry> + </variablelist> + <variablelist> + <varlistentry> + <term +><menuchoice +><shortcut +> <keycombo +>&Ctrl;<keycap +>O</keycap +></keycombo +> </shortcut +> <guimenu +>File</guimenu +> <guimenuitem +>Open...</guimenuitem +> </menuchoice +></term> + <listitem +><para +>Opens a &logo; file.</para +></listitem> + </varlistentry> + </variablelist> + <variablelist> + <varlistentry> + <term +><menuchoice +><guimenu +>File</guimenu +> <guimenuitem +>Open Recent</guimenuitem +> </menuchoice +></term> + <listitem +><para +>Opens a &logo; file that has been opened recently.</para +></listitem> + </varlistentry> + </variablelist> + <variablelist> + <varlistentry> + <term +><menuchoice +><shortcut +> <keycombo +>&Ctrl;<keycap +>E</keycap +></keycombo +> </shortcut +> <guimenu +>File</guimenu +> <guimenuitem +>Open Examples</guimenuitem +> </menuchoice +></term> + <listitem +><para +>Show the folder with examples &logo; programs. The examples should be in your favorite language that you can choose in <menuchoice +><guimenu +>Settings</guimenu +><guimenuitem +>Configure &kturtle;...</guimenuitem +> </menuchoice +>.</para +></listitem> + </varlistentry> + </variablelist> + <variablelist> + <anchor id="file-execute"/> + <varlistentry> + <term +><menuchoice +><shortcut +> <keycombo +>&Alt;<keysym +>Return</keysym +></keycombo +> </shortcut +> <guimenu +>File</guimenu +> <guimenuitem +>Execute Commands</guimenuitem +> </menuchoice +></term> + <listitem +><para +>Starts the execution of the commands in the code editor.</para +></listitem> + </varlistentry> + </variablelist> + <variablelist> + <anchor id="file-stop"/> + <varlistentry> + <term +><menuchoice +><shortcut +> <keycombo +><keysym +>Escape</keysym +></keycombo +> </shortcut +> <guimenu +>File</guimenu +> <guimenuitem +>Stop Execution</guimenuitem +> </menuchoice +></term> + <listitem +><para +>Stops the execution. This action is only enabled when the commands are actually executing.</para +></listitem> + </varlistentry> + </variablelist> + <variablelist> + <anchor id="file-save"/> + <varlistentry> + <term +><menuchoice +><shortcut +> <keycombo +>&Ctrl;<keycap +>S</keycap +></keycombo +> </shortcut +> <guimenu +>File</guimenu +> <guimenuitem +>Save</guimenuitem +> </menuchoice +></term> + <listitem +><para +>Saves the currently opened &logo; file.</para +></listitem> + </varlistentry> + </variablelist> + <variablelist> + <anchor id="file-save-as"/> + <varlistentry> + <term +><menuchoice +><guimenu +>File</guimenu +> <guimenuitem +>Save As...</guimenuitem +> </menuchoice +></term> + <listitem +><para +>Saves the currently opened &logo; file on a specified location.</para +></listitem> + </varlistentry> + </variablelist> + <variablelist> + <anchor id="file-save-canvas"/> + <varlistentry> + <term +><menuchoice +><guimenu +>File</guimenu +> <guimenuitem +>Save Canvas</guimenuitem +> </menuchoice +></term> + <listitem +><para +>Saves the current drawing on canvas into an image.</para +></listitem> + </varlistentry> + </variablelist> + <variablelist> + <anchor id="file-print"/> + <varlistentry> + <term +><menuchoice +><shortcut +> <keycombo +>&Ctrl;<keycap +>P</keycap +></keycombo +> </shortcut +> <guimenu +>File</guimenu +> <guimenuitem +>Print...</guimenuitem +> </menuchoice +></term> + <listitem +><para +>Prints either the current code in the editor or the current drawing on the canvas.</para +></listitem> + </varlistentry> + </variablelist> + <variablelist> + <anchor id="file-quit"/> + <varlistentry> + <term +><menuchoice +><shortcut +> <keycombo +>&Ctrl;<keycap +>Q</keycap +></keycombo +> </shortcut +> <guimenu +>File</guimenu +> <guimenuitem +>Quit</guimenuitem +> </menuchoice +></term> + <listitem +><para +>Quits &kturtle;.</para +></listitem> + </varlistentry> + </variablelist> +</sect2> + +<sect2 id="the-edit-menu"> + <title +>The <guimenu +>Edit</guimenu +> Menu</title> + <variablelist> + <anchor id="edit-undo"/> + <varlistentry> + <term +><menuchoice +><shortcut +> <keycombo +>&Ctrl;<keycap +>Z</keycap +></keycombo +> </shortcut +> <guimenu +>Edit</guimenu +> <guimenuitem +>Undo</guimenuitem +> </menuchoice +></term> + <listitem +><para +>Undoes the last change to code. &kturtle; has unlimited undos.</para +></listitem> + </varlistentry> + </variablelist> + <variablelist> + <anchor id="edit-redo"/> + <varlistentry> + <term +><menuchoice +><shortcut +> <keycombo +>&Ctrl;&Shift;<keycap +>Z</keycap +></keycombo +> </shortcut +> <guimenu +>Edit</guimenu +> <guimenuitem +>Redo</guimenuitem +> </menuchoice +></term> + <listitem +><para +>Redoes an undone change to the code.</para +></listitem> + </varlistentry> + </variablelist> + <variablelist> + <anchor id="edit-cut"/> + <varlistentry> + <term +><menuchoice +><shortcut +> <keycombo +>&Ctrl;<keycap +>X</keycap +></keycombo +> </shortcut +> <guimenu +>Edit</guimenu +> <guimenuitem +>Cut</guimenuitem +> </menuchoice +></term> + <listitem +><para +>Cuts the selected text from the code editor to the clipboard.</para +></listitem> + </varlistentry> + </variablelist> + <variablelist> + <anchor id="edit-copy"/> + <varlistentry> + <term +><menuchoice +><shortcut +> <keycombo +>&Ctrl;<keycap +>C</keycap +></keycombo +> </shortcut +> <guimenu +>Edit</guimenu +> <guimenuitem +>Copy</guimenuitem +> </menuchoice +></term> + <listitem +><para +>Copies the selected text from the code editor to the clipboard.</para +></listitem> + </varlistentry> + </variablelist> + <variablelist> + <anchor id="edit-paste"/> + <varlistentry> + <term +><menuchoice +><shortcut +> <keycombo +>&Ctrl;<keycap +>V</keycap +></keycombo +> </shortcut +> <guimenu +>Edit</guimenu +> <guimenuitem +>Paste</guimenuitem +> </menuchoice +></term> + <listitem +><para +>Pastes the text from the clipboard to the editor.</para +></listitem> + </varlistentry> + </variablelist> + <variablelist> + <anchor id="edit-find"/> + <varlistentry> + <term +><menuchoice +><shortcut +> <keycombo +>&Ctrl;<keycap +>F</keycap +></keycombo +> </shortcut +> <guimenu +>Edit</guimenu +> <guimenuitem +>Find...</guimenuitem +> </menuchoice +></term> + <listitem +><para +>With this action you can find phrases in the code.</para +></listitem> + </varlistentry> + </variablelist> + <variablelist> + <anchor id="edit-find-next"/> + <varlistentry> + <term +><menuchoice +><shortcut +> <keycombo +><keysym +>F3</keysym +></keycombo +> </shortcut +> <guimenu +>Edit</guimenu +> <guimenuitem +>Find Next</guimenuitem +> </menuchoice +></term> + <listitem +><para +>Use this to find the next occurrence of the phrase.</para +></listitem> + </varlistentry> + </variablelist> + <variablelist> + <anchor id="edit-replace"/> + <varlistentry> + <term +><menuchoice +><shortcut +> <keycombo +>&Ctrl;<keycap +>R</keycap +></keycombo +> </shortcut +> <guimenu +>Edit</guimenu +> <guimenuitem +>Replace...</guimenuitem +> </menuchoice +></term> + <listitem +><para +>With this action you can replace phrases in the code.</para +></listitem> + </varlistentry> + </variablelist> +</sect2> + +<sect2 id="the-view-menu"> + <title +>The <guimenu +>View</guimenu +> Menu</title> + <variablelist> + <anchor id="view-fullscreen"/> + <varlistentry> + <term +><menuchoice +><shortcut +> <keycombo +>&Ctrl;&Shift;<keycap +>F</keycap +></keycombo +> </shortcut +> <guimenu +>View</guimenu +> <guimenuitem +>Full Screen Mode</guimenuitem +> </menuchoice +></term> + <listitem +><para +>With this action you toggle the full screen mode.</para> + <para +>Note: When code is executed while in full screen mode everything but the canvas is hidden. This makes it possible to write <quote +>full screen</quote +> programs in &kturtle;.</para +></listitem> + </varlistentry> + </variablelist> + <variablelist> + <anchor id="view-linenumbers"/> + <varlistentry> + <term +><menuchoice +><shortcut +> <keycombo +><keysym +>F11</keysym +></keycombo +> </shortcut +> <guimenu +>View</guimenu +> <guimenuitem +>Show Line Numbers</guimenuitem +> </menuchoice +></term> + <listitem +><para +>With this action you can show the line numbers in the code editor. This can be handy for finding errors.</para +></listitem> + </varlistentry> + </variablelist> +</sect2> + +<sect2 id="the-tools-menu"> + <title +>The <guimenu +>Tools</guimenu +> Menu</title> + <variablelist> + <anchor id="tools-color-picker"/> + <varlistentry> + <term +><menuchoice +><shortcut +> <keycombo +>&Alt;<keycap +>C</keycap +></keycombo +> </shortcut +> <guimenu +>Tools</guimenu +> <guimenuitem +>Colour Picker</guimenuitem +> </menuchoice +></term> + <listitem +><para +>This action opens the colour picker. Using the colour picker you can easily select a <glossterm linkend="rgb" +>colour code</glossterm +> and insert it in <link linkend="the-code-editor" +>the code editor</link +>.</para +></listitem> + </varlistentry> + </variablelist> + <variablelist> + <anchor id="tools-indent"/> + <varlistentry> + <term +><menuchoice +><shortcut +> <keycombo +>&Ctrl;<keycap +>I</keycap +></keycombo +> </shortcut +> <guimenu +>Tools</guimenu +> <guimenuitem +>Indent</guimenuitem +> </menuchoice +></term> + <listitem +><para +>This action <quote +>indents</quote +> (adds white space at the beginning of) the lines that are selected. When <quote +>indentation</quote +> is used properly this can make code much easier to read. All examples use indentation, please check them out.</para +></listitem> + </varlistentry> + </variablelist> + <variablelist> + <anchor id="tools-unindent"/> + <varlistentry> + <term +><menuchoice +><shortcut +> <keycombo +>&Ctrl;&Shift;<keycap +>I</keycap +></keycombo +> </shortcut +> <guimenu +>Tools</guimenu +> <guimenuitem +>Unindent</guimenuitem +> </menuchoice +></term> + <listitem +><para +>This action <quote +>unindents</quote +> (removes the white space at the beginning of) the lines that are selected.</para +></listitem> + </varlistentry> + </variablelist> + <variablelist> + <anchor id="tools-clean-indent"/> + <varlistentry> + <term +><menuchoice +><guimenu +>Tools</guimenu +> <guimenuitem +>Clean Indentation</guimenuitem +> </menuchoice +></term> + <listitem +><para +>This action cleans <quote +>indentation</quote +> (removes all the white space at the beginning of) the lines that are selected.</para +></listitem> + </varlistentry> + </variablelist> + <variablelist> + <anchor id="tools-comment"/> + <varlistentry> + <term +><menuchoice +><shortcut +> <keycombo +>&Ctrl;<keycap +>D</keycap +></keycombo +> </shortcut +> <guimenu +>Tools</guimenu +> <guimenuitem +>Comment</guimenuitem +> </menuchoice +></term> + <listitem +><para +>This action add comment characters (#) in from of the lines that are selected. Lines that start with a comment character are ignored when the code is executed. Comments allow the programmer to explain a bit about his code or they can be used to temporarily prevent a certain piece of code from being executed.</para +></listitem> + </varlistentry> + </variablelist> + <variablelist> + <anchor id="tools-uncomment"/> + <varlistentry> + <term +><menuchoice +><shortcut +> <keycombo +>&Ctrl;&Shift;<keycap +>D</keycap +></keycombo +> </shortcut +> <guimenu +>Tools</guimenu +> <guimenuitem +>Uncomment</guimenuitem +> </menuchoice +></term> + <listitem +><para +>This action removes the comment characters from the selected lines.</para +></listitem> + </varlistentry> + </variablelist> +</sect2> + +<sect2 id="the-setting-menu"> + <title +>The <guimenu +>Settings</guimenu +> Menu</title> + <variablelist> + <anchor id="toggle-toolbar"/> + <varlistentry> +<term +><menuchoice +><guimenu +>Settings</guimenu +> <guimenuitem +>Show/Hide Toolbar</guimenuitem +> </menuchoice +></term> +<listitem +><para +><action +>Toggle</action +> the Main Toolbar</para +></listitem> +</varlistentry> + </variablelist +> + <variablelist> + <anchor id="toggle-statusbar"/> + <varlistentry> +<term +><menuchoice +><guimenu +>Settings</guimenu +> <guimenuitem +>Show/Hide Statusbar</guimenuitem +> </menuchoice +></term> +<listitem +><para +><action +>Toggle</action +> the Statusbar</para +></listitem> +</varlistentry> + </variablelist> + <variablelist> + <anchor id="tools-advanced"/> + <varlistentry> + <term +><menuchoice +><guimenu +>Settings</guimenu +> <guisubmenu +>Advanced Settings</guisubmenu +> </menuchoice +></term> + <listitem +><para +>Here you can change things you normally do not need to change. The <guisubmenu +>Advanced Settings</guisubmenu +> submenu has three items: <guimenuitem +>Configure Editor...</guimenuitem +> (the standard &kate; editor settings dialog), <guimenuitem +>Configure Shortcuts...</guimenuitem +> (the standard &kde; shortcut settings dialog), and <guimenuitem +>Configure Toolbars...</guimenuitem +> (the standard &kde; toolbars setting dialog).</para +></listitem> + </varlistentry> + </variablelist> + <variablelist> + <anchor id="settings-configure"/> + <varlistentry> + <term +><menuchoice +><guimenu +>Settings</guimenu +> <guimenuitem +>Configure &kturtle;...</guimenuitem +> </menuchoice +></term> + <listitem +><para +>This is used to configure &kturtle;. Here you can change the language of the &logo; commands or set a new initial canvas size.</para +></listitem> + </varlistentry> + </variablelist> + +</sect2> + +<sect2 id="the-help-menu"> + <title +>The <guimenu +>Help</guimenu +> Menu</title> + <variablelist> + <anchor id="help-handbook"/> + <varlistentry> + <term +><menuchoice +><guimenu +>Help</guimenu +> <guimenuitem +>&kturtle; Handbook</guimenuitem +> </menuchoice +></term> + <listitem +><para +>This action shows the handbook that you are currently reading.</para +></listitem> + </varlistentry> + </variablelist> + <variablelist> + <anchor id="help-whats-this"/> + <varlistentry> + <term +><menuchoice +><shortcut +> <keycombo +>&Shift;<keysym +>F1</keysym +></keycombo +> </shortcut +> <guimenu +>Help</guimenu +> <guimenuitem +>What's This?</guimenuitem +> </menuchoice +></term> + <listitem +><para +>After activating this action the mouse arrow will be changed into a <quote +>question mark arrow</quote +>. When this arrow is used to click on parts of &kturtle; main window, a description of the particular part pops-up.</para +></listitem> + </varlistentry> + </variablelist> + <variablelist> + <anchor id="help-context-help"/> + <varlistentry> + <term +><menuchoice +><shortcut +> <keycombo +><keysym +>F1</keysym +></keycombo +> </shortcut +> <guimenu +>Help</guimenu +> <guimenuitem +>Help on: ...</guimenuitem +> </menuchoice +></term> + <listitem +><para +>This is a very useful function: it provides help on the code where the cursor in the code editor is at. So, ⪚, you have used the <userinput +>print</userinput +> command in your code, and you want to read and to know what the handbook says on this command. You just move your cursor so it is in the <userinput +>print</userinput +> command and you press <keysym +>F1</keysym +>. The handbook will then show all info on the <userinput +>print</userinput +> command.</para> + <para +>This function is very important while learning programming.</para +></listitem> + </varlistentry> + </variablelist> + <variablelist> + <anchor id="help-report-bug"/> + <varlistentry> + <term +><menuchoice +><guimenu +>Help</guimenu +> <guimenuitem +>Report Bug...</guimenuitem +> </menuchoice +></term> + <listitem +><para +>Use this to report a problem with &kturtle; to the developers. These reports can be used to make future versions of &kturtle; even better.</para +></listitem> + </varlistentry> + </variablelist> + <variablelist> + <anchor id="help-about-kturtle"/> + <varlistentry> + <term +><menuchoice +><guimenu +>Help</guimenu +> <guimenuitem +>About &kturtle;</guimenuitem +> </menuchoice +></term> + <listitem +><para +>Here you find information on &kturtle;, like the authors and the license it comes with.</para +></listitem> + </varlistentry> + </variablelist> + <variablelist> + <anchor id="help-about-kde"/> + <varlistentry> + <term +><menuchoice +><guimenu +>Help</guimenu +> <guimenuitem +>About &kde;</guimenuitem +> </menuchoice +></term> + <listitem +><para +>Here you can find information on &kde;. If you do not know yet what &kde; is, this is a place you should not miss.</para +></listitem> + </varlistentry> + </variablelist> +</sect2> + +</sect1> + +<sect1 id="the-toolbar"> +<title +>The Toolbar</title> +<para +>Here you can quickly reach the most used actions. By default, you will find here all main useful commands ending with the <guiicon +>Execute Commands</guiicon +> and <guiicon +>Stop Execution</guiicon +> icons.</para> +<para +>You can configure the toolbar using <menuchoice +><guimenu +>Settings</guimenu +><guimenuitem +>Advanced Settings</guimenuitem +><guimenuitem +>Configure Toolbar...</guimenuitem +></menuchoice +></para> +</sect1> + +<sect1 id="the-statusbar"> +<title +>The Statusbar</title> +<para +>On the statusbar you get feedback of the state of &kturtle;. On the left side it shows the feedback on the last action. On the right side you find the current location of the cursor (line and column numbers). In the middle of the Statusbar is indicated the current language used for the commands.</para> +</sect1> + +</chapter> |