From f7e7a923aca8be643f9ae6f7252f9fb27b3d2c3b Mon Sep 17 00:00:00 2001 From: Timothy Pearson Date: Sat, 3 Dec 2011 11:05:10 -0600 Subject: Second part of prior commit --- tde-i18n-en_GB/docs/tdeedu/kturtle/Makefile.am | 4 + tde-i18n-en_GB/docs/tdeedu/kturtle/Makefile.in | 635 ++++++++++ .../docs/tdeedu/kturtle/getting-started.docbook | 292 +++++ .../docs/tdeedu/kturtle/glossary.docbook | 406 +++++++ tde-i18n-en_GB/docs/tdeedu/kturtle/index.cache.bz2 | Bin 0 -> 18760 bytes tde-i18n-en_GB/docs/tdeedu/kturtle/index.docbook | 305 +++++ .../tdeedu/kturtle/programming-reference.docbook | 1209 ++++++++++++++++++++ .../docs/tdeedu/kturtle/translator-guide.docbook | 223 ++++ .../docs/tdeedu/kturtle/using-kturtle.docbook | 1025 +++++++++++++++++ 9 files changed, 4099 insertions(+) create mode 100644 tde-i18n-en_GB/docs/tdeedu/kturtle/Makefile.am create mode 100644 tde-i18n-en_GB/docs/tdeedu/kturtle/Makefile.in create mode 100644 tde-i18n-en_GB/docs/tdeedu/kturtle/getting-started.docbook create mode 100644 tde-i18n-en_GB/docs/tdeedu/kturtle/glossary.docbook create mode 100644 tde-i18n-en_GB/docs/tdeedu/kturtle/index.cache.bz2 create mode 100644 tde-i18n-en_GB/docs/tdeedu/kturtle/index.docbook create mode 100644 tde-i18n-en_GB/docs/tdeedu/kturtle/programming-reference.docbook create mode 100644 tde-i18n-en_GB/docs/tdeedu/kturtle/translator-guide.docbook create mode 100644 tde-i18n-en_GB/docs/tdeedu/kturtle/using-kturtle.docbook (limited to 'tde-i18n-en_GB/docs/tdeedu/kturtle') diff --git a/tde-i18n-en_GB/docs/tdeedu/kturtle/Makefile.am b/tde-i18n-en_GB/docs/tdeedu/kturtle/Makefile.am new file mode 100644 index 00000000000..f781297a70f --- /dev/null +++ b/tde-i18n-en_GB/docs/tdeedu/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/tdeedu/kturtle/Makefile.in b/tde-i18n-en_GB/docs/tdeedu/kturtle/Makefile.in new file mode 100644 index 00000000000..babf86aed97 --- /dev/null +++ b/tde-i18n-en_GB/docs/tdeedu/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/tdeedu/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@ +tdeinitdir = @tdeinitdir@ +libdir = @libdir@ +libexecdir = @libexecdir@ +localedir = @localedir@ +localstatedir = @localstatedir@ +mandir = @mandir@ +mkdir_p = @mkdir_p@ +oldincludedir = @oldincludedir@ +pdfdir = @pdfdir@ +prefix = @prefix@ +program_transform_name = @program_transform_name@ +psdir = @psdir@ +sbindir = @sbindir@ +sharedstatedir = @sharedstatedir@ +srcdir = @srcdir@ +sysconfdir = @sysconfdir@ +target_alias = @target_alias@ +top_builddir = @top_builddir@ +top_srcdir = @top_srcdir@ +xdg_appsdir = @xdg_appsdir@ +xdg_directorydir = @xdg_directorydir@ +xdg_menudir = @xdg_menudir@ +KDE_LANG = en_GB +#>- SUBDIRS = $(AUTODIRS) +#>+ 1 +SUBDIRS =. +KDE_DOCS = 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/tdeedu/kturtle/Makefile'; \ +#>- cd $(top_srcdir) && \ +#>- $(AUTOMAKE) --gnu docs/tdeedu/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/tdeedu/kturtle/Makefile'; \ + cd $(top_srcdir) && \ + $(AUTOMAKE) --gnu docs/tdeedu/kturtle/Makefile + cd $(top_srcdir) && perl ../scripts/admin/am_edit -p../scripts/admin docs/tdeedu/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/tdeedu/kturtle/Makefile'; \ + cd $(top_srcdir) && \ + $(AUTOMAKE) --gnu docs/tdeedu/kturtle/Makefile + cd $(top_srcdir) && perl ../scripts/admin/am_edit -p../scripts/admin docs/tdeedu/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/tdeedu/kturtle/getting-started.docbook b/tde-i18n-en_GB/docs/tdeedu/kturtle/getting-started.docbook new file mode 100644 index 00000000000..fb4e5045d03 --- /dev/null +++ b/tde-i18n-en_GB/docs/tdeedu/kturtle/getting-started.docbook @@ -0,0 +1,292 @@ + +Getting Started +When you start &kturtle; you will see something like this: Here is a screenshot of &kturtle; when you start it for the first time &kturtle; Main window In this Getting Started guide we assume that the language of the &logo; commands is English. You can change this language in SettingsConfigure &kturtle;... in the Language section. Be aware that the language you set here for &kturtle; is the one you use to type the &logo; commands. + + +First steps with &logo;: meet the Turtle! +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. + + +The Turtle Moves +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: + +forward 90 +turnleft 90 + +Type or copy-paste the code to the code editor and execute it (using FileExecute Commands) to see the result. + +When you typed and executed the commands like above in the code editor you might have noticed one or more of the following things: + +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 forward and the turnleft commands. + + +That the colour of the code changed while you where typing it: this feature is called intuitive highlighting — different types of commands are highlighted differently. This makes reading large blocks of code more easy. + + +That the turtle draws a thin black line. + + +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 SettingsConfigure &kturtle;..., in the Language section). + + + +You will likely understand that forward 90 commanded the turtle to move forward leaving a line, and that turnleft 90 commanded the turtle to turn 90 degrees to the left. + +Please see the following links to the reference manual for a complete explanation of the new commands: forward, backward, turnleft, and turnright. + + + +More examples +The first example was very simple, so let us go on! + + + +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 + +Again you can type or copy-paste the code to the code editor or open the arrow.logo file in the Open examples folder and execute it (using FileExecute Commands) to see the result. In the next examples you are expected to know the drill. + +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: + +canvassize 200,200 sets the canvas width and height to 200 pixels. The width and the height are equal, so the canvas will be a square. + +canvascolour 0,0,0 makes the canvas black. 0,0,0 is an RGB-combination where all values are set to 0, which results in black. + +pencolor 255,0,0 sets the color of the pen to red. 255,0,0 is an RGB-combination where only the red value is set to 255 (fully on) while the others (green and blue) are set to 0 (fully off). This results in a bright shade of red. + +penwidth 5 sets the width (the size) of the pen to 5 pixels. From now on every line the turtle draw will have a thickness of 5, until we change the penwidth to something else. + +clear clear the canvas, that is all it does. + +go 20,20 commands the turtle to go to a certain place on the canvas. Counted from the upper left corner, this place is 20 pixels across from the left, and 20 pixels down from the top of the canvas. Note that using the go command the turtle will not draw a line. + +direction 135 set the turtle's direction. The turnleft and turnright commands change the turtle's angle starting from its current direction. The direction command changes the turtle's angle from zero, and thus is not relative to the turtle previous direction. + +After the direction command a lot of forward and turnleft commands follow. These command do the actual drawing. + +At last another go command is used to move the turtle aside. + +Make sure you follow the links to the reference. The reference explains each command more thoroughly. + + + + + + + + + + \ No newline at end of file diff --git a/tde-i18n-en_GB/docs/tdeedu/kturtle/glossary.docbook b/tde-i18n-en_GB/docs/tdeedu/kturtle/glossary.docbook new file mode 100644 index 00000000000..22af4ab935a --- /dev/null +++ b/tde-i18n-en_GB/docs/tdeedu/kturtle/glossary.docbook @@ -0,0 +1,406 @@ + +Glossary + +In this chapter you will find an explanation of most of the uncommon words that are used in the handbook. + + + +degrees +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 turnleft, turnright and direction need an input in degrees. + + + +input and output of commands +Some commands take input, some commands give output, some commands take input and give output and some commands neither take input nor give output. +Some examples of commands that only take input are: +forward 50 +pencolour 255,0,0 +print "Hello!" + The forward command takes 50 as input. forward needs this input to know how many pixels it should go forward. pencolor takes a colour as input and print takes a string (a piece of text) as input. Please note that the input can also be a container. The next example illustrates this: x = 50 +print x +str = "hello!" +print str + + +Now some examples of commands that give output: +x = inputwindow "Please type something and press OK... thanks!" +r = random 1,100 + The inputwindow command takes a string as input, and outputs the number or string that is entered. As you can see, the output of inputwindow is stored in the container x. The random 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 r. Note that the containers x and r are not used in the example code above. + +There are also commands that neither need input nor give output. Here are some examples: clear +penup +wrapon +hide + + + + + +intuitive highlighting +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 the code editor. +Different types of code and their highlight colour + + + +regular commands +dark green +The regular commands are described here. + + +execution controllers +black (bold) +The special commands control execution, read more on them here. + + +comments +dark yellow +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. + + +brackets [, ] +light green (bold) +Brackets are used to group portions of code. Brackets are often used together with execution controllers. + + +the learn command +light green (bold) +The learn command is used to create new commands. + + +numbers +blue +Numbers, well not much to say about them. + + +strings +dark red +Not much to say about (text) strings either, except that they always start and end with the double quotes ("). + + +mathematical characters +grey +These are the mathematical characters: +, -, *, /, (, and ). Read more about them here. + + +questions characters +blue (bold) +Read more about questions here. + + +question glue-words +pink +Read more about the question glue-words (and, or, not) here. + + +regular text +black + + + + +
+ + + + +pixels +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. +A lot of commands need a number of pixels as input. These commands are: forward, backward, go, gox, goy, canvassize and penwidth. + + + +RGB combinations (colour codes) +RGB combinations are used to describe colours. The R stand for red, the G stands for green and the B stands for blue. An example of an RGB combination is 255,0,0: the first value (red) 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: +Often used RGB combinations + + + +0,0,0black +255,255,255white +255,0,0red +150,0,0dark red +0,255,0green +0,0,255blue +0,255,255light blue +255,0,255pink +255,255,0yellow + + +
+ +To easily find the RGB combinations of a colour you should try the colour picker! You can open the colour picker using ToolsColour Picker. +Two commands need an RGB combination as input: these commands are canvascolour and pencolour. + + + +sprite +A sprite is a small picture that can be moved around the screen. Our beloved turtle, for instance, is a sprite. +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. + + + +wrapping +Wrapping is what happens when the turtle draws something that is to big to fix in on the canvas and wrapping is set on. This is what happens when wrapping is on An example of wrapping 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. +Wrapping can be turned on and off with the wrapon and wrapoff commands. When &kturtle; starts wrapping is turned on by default. + + + + + \ No newline at end of file diff --git a/tde-i18n-en_GB/docs/tdeedu/kturtle/index.cache.bz2 b/tde-i18n-en_GB/docs/tdeedu/kturtle/index.cache.bz2 new file mode 100644 index 00000000000..966f31c3551 Binary files /dev/null and b/tde-i18n-en_GB/docs/tdeedu/kturtle/index.cache.bz2 differ diff --git a/tde-i18n-en_GB/docs/tdeedu/kturtle/index.docbook b/tde-i18n-en_GB/docs/tdeedu/kturtle/index.docbook new file mode 100644 index 00000000000..4a23baed449 --- /dev/null +++ b/tde-i18n-en_GB/docs/tdeedu/kturtle/index.docbook @@ -0,0 +1,305 @@ + + + + + + + + + + + + + +]> + + + + +The &kturtle; Handbook + + +Cies Breijs
cies # showroommama ! nl
+ + +Anne-Marie Mahfouf
annma@kde.org
+ + + + +AndrewColes
andrew_coles@yahoo.co.uk
Conversion to British English + + +2004 +Cies Breijs + + +&FDLNotice; + +2004-10-5 +0.2.1 + + +&kturtle; is an educational programming environment using the &logo; programming language. + + + +KDE +tdeedu +KTurtle +education +language +native +programming +code +Logo +instructions +turtle + + + + + +Introduction + +&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. + +&kturtle; is named after the turtle that plays a central role in the programming environment. The user programs the turtle, using the &logo; commands, to draw a picture on the canvas. + + + + +Features of &kturtle; +&kturtle; has some nice features that make starting to program a breeze. See here some of the highlights of &kturtle; feature set: +An integrated &logo; interpreter, so no need to download any other program. +A powerful editor for the &logo; commands with intuitive syntax highlighting, line numbering and more. +The canvas can be saved as an image or printed. +Context help for all &logo; commands: Just press F1. +The &logo; commands are fully translatable (currently only English, Dutch, French, German and Swedish are supported). +Full-screen mode. +Many integrated, internationalised example &logo; programs make it easy to get started. + + + + + +&using-kturtle; + +&getting-started; + +&programming-reference; + +&glossary; + +&translator-guide; + + + +Credits and Licence + +&kturtle; +Program copyright 2003-2004 Cies Breijs cies # showroommama ! nl +Contributors: +Coding help, editor part: Anne-Marie Mahfouf annma@kde.org + +Author of wsbasic (http://wsbasic.sourceforge.net) which is the base for the interpreter of &kturtle;: Walter Schreppers Walter.Schreppers@ua.ac.be + +German Data Files: Matthias Meßmer bmlmessmer@web.de + +Swedish Data Files: Stefan Asserhäll stefan.asserhal@telia.com + + + + +Documentation copyright 2004 +Cies Briej cies # showroommama ! nl +Anne-Marie Mahfouf annma@kde.org +Some proofreading changes by &Philip.Rodrigues; &Philip.Rodrigues.mail; + +Updated translation how-to and some proofreading changes by Andrew Coles andrew_coles@yahoo.co.uk + + + + +Andrew Colesandrew_coles@yahoo.co.uk +&underFDL; &underGPL; + + + + +Installation + + +How to obtain &kturtle; +&install.intro.documentation; + + +Compilation and Installation +&install.compile.documentation; + + + +&documentation.index; + + \ No newline at end of file diff --git a/tde-i18n-en_GB/docs/tdeedu/kturtle/programming-reference.docbook b/tde-i18n-en_GB/docs/tdeedu/kturtle/programming-reference.docbook new file mode 100644 index 00000000000..5e459b562f1 --- /dev/null +++ b/tde-i18n-en_GB/docs/tdeedu/kturtle/programming-reference.docbook @@ -0,0 +1,1209 @@ + +&kturtle;'s &logo; Programming Reference + + +Commands +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;. + + +Moving the turtle +There are several commands to move the turtle over the screen. + + + + + forward + forward X +forward moves the turtle forward by the amount of X pixels. When the pen is down the turtle will leave a trail. forward can be abbreviated to fw + + + + + + backward + backward X +backward moves the turtle backward by the amount of X pixels. When the pen is down the turtle will leave a trail. backward can be abbreviated to bw. + + + + + + turnleft + turnleft X +turnleft commands the turtle to turn an amount of X degrees to the left. turnleft can be abbreviated to tl. + + + + + + turnright + turnright X +turnrightthe turtle to turn an amount of X degrees to the right. turnright can be abbreviated to tr. + + + + + + direction + direction X +direction 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. direction can be abbreviated to dir. + + + + + + centre + centre +centre moves the turtle to the centre on the canvas. + + + + + + go + go X,Y +go commands the turtle to go to a certain place on the canvas. This place is X pixels from the left of the canvas, and Y pixels form the top of the canvas. Note that using the go command the turtle will not draw a line. + + + + + + gox + gox X +gox using this command the turtle will move to X pixels from the left of the canvas whilst staying at the same height. + + + + + + goy + goy Y +gox using this command the turtle will move to Y pixels from the top of the canvas whilst staying at the same distance from the left border of the canvas. + + + + + +The turtle has a pen +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. + + + + penup + penup +penup lifts the pen from the canvas. When the pen is up no line will be drawn when the turtle moves. See also pendown. penup can be abbreviated to pu. + + + + + + pendown + pendown +pendown presses the pen down on the canvas. When the pen is press down on the canvas a line will be drawn when the turtle moves. See also penup.pendown can be abbreviated to pd. + + + + + + penwidth + penwidth X +penwidth sets the width of the pen (the line width) to an amount of X pixels. penwidth can be abbreviated to pw. + + + + + + pencolour + pencolour R,G,B +pencolor sets the color of the pen. pencolor takes an RGB combination as input. pencolor can be abbreviated to pc. + + + + + +Commands to control the canvas +There are several commands to control the canvas. + + + + canvassize + canvassize X,Y +With the canvassize command you can set the size of the canvas. It takes X and Y as input, where X is the new canvas width in pixels, and Y is the new height of the canvas in pixels. canvassize can be abbreviated to cs. + + + + + + canvascolour + canvascolour R,G,B +canvascolor set the color of the canvas. canvascolor takes an RGB combination as input. canvascolor can be abbreviated to cc. + + + + + + wrapon + wrapon +With the wrapon command you can set wrapping on for the canvas. Please see the glossary if you want to know what wrapping is. + + + + + + wrapoff + wrapoff +With the wrapoff command you can set wrapping off for the canvas: this means the turtle can move off the canvas and can get lost. Please see the glossary if you want to know what wrapping is. + + + + + +Commands to clean up +There are two commands to clean up the canvas after you have made a mess. + + + + clear + clear +With clear 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. clear can be abbreviated to ccl. + + + + + + reset + reset +reset cleans much more thoroughly than the clear command. After a reset 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. + + + + + +The turtle is a sprite +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 sprites). So the turtle is a sprite. +Next you will find a full overview on all commands to work with sprites. +[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] + + + + show + show +show makes the turtle visible again after it has been hidden.show can be abbreviated to ss. + + + + + + hide + hide +hide hides the turtle. This can be used if the turtle does not fit in your drawing.hide can be abbreviated to sh. + + + + + +Can the turtles write text? +The answer is: yes. The turtle can write: it writes just about everything you command it to. + + + + print + print X +The print command is used to command the turtle to write something on the canvas. print takes numbers and strings as input. You can print various numbers and strings using the + symbol. See here a small example: year = 2004 +author = "Cies" +print "KTurtle was made in " + year + " by " + author + + + + + + + + fontsize + fontsize X +fontsize sets the size of the font that is used by print. fontsize takes one input which should be a number. The size is set in pixels. + + + + + +A command that rolls a dice for you +There is one command that rolls a dice for you + + + + random + random X,Y +random 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: +repeat 500 [ + x = random 1,20 + forward x + turnleft 10 - x +] + Using the random command you can add a bit of chaos to your program. + + + + + + +Containers +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 variables, containers that can contain text are called strings. + +Containers that are not used yet are 0 by default. An example: +print N + This will print a 0. + + +Variables: number containers +Let us start with an example: +x = 3 +print x + In the first line the letter x made into a variable (number container). As you see the value of the variable x is set to 3. On the second line the value is printed. +Note that if we wanted to print an x that we should have written print "x" + + +That was easy, now a bit harder example: +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 + In the first two lines the variables A and B are set to 2004 and 25. On the third line the variable AB is set to A + B, which is 2029. The rest of the example consists of 3 print commands with backward 30 in between. The backward 30 is there to make sure every output is on a new line. In this example you also see that variables can be used in mathematical calculations. + + + +Strings: text containers +Strings are a lot like variables. The biggest difference is that strings cannot be used in mathematical calculations and questions. An example of the use of strings: +x = "Hello " +name = inputwindow "Please enter your name..." +print x + name + ", how are you?" + On the first line the string x is set to Hello . On the second line the string name is set to the output of the inputwindow command. On the third line the program prints a composition of three strings on the canvas. +This program ask you to enter your name. When you, for instance, enter the name Paul, the program prints Hello Paul, how are you?. Please note that the plus (+) is the only math symbol that you can use with strings. + + + + +Can the Turtle do maths? +Yes, &kturtle; will do your math. You can add (+), substract (-), multiply (*), and divide (/). Here is an example in which we use all of them: +a = 20 - 5 +b = 15 * 2 +c = 30 / 30 +d = 1 + 1 +print "a: "+a+", b: "+b+", c: "+c+", d: "+d + Do you know what value a, b, c and d have? +If you just want a simple calculation to be done you can do something like this: print 2004-12 + +Now an example with brackets: +print ( ( 20 - 5 ) * 2 / 30 ) + 1 + 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). + + + +Asking questions, getting answers... +if and while are execution controllers that we will discuss in the next section. In this section we use the if command to explain questions. +A simple example of questions: +x = 6 +if x > 5 [ + print "hello" +] + In this example the question is the x > 5 part. If the answer to this question is true the code between the brackets will be executed. Questions are an important part of programming and often used together with execution controllers, like if. All numbers and variables (number containers) can be compared to each other with questions. +Here are all possible questions: +Types of questions + + + +a == b +equals +answer is true if a equals b + + +a != b +not-equal +answer is true if a does not equal b + + +a > b +greater than +answer is true if a is greater than b + + +a < b +smaller than +answer is true if a is smaller than b + + +a >= b +greater than or equals +answer is true if a is greater than or equals b + + +a <= b +smaller than or equals +answer is true if a is smaller than or equals b + + + +
+ +Questions can also be glued to each other with question glue, this way a few questions can become one big question. +a = 1 +b = 5 +if a < 5 and b == 5 [ + print "hello" +] + In this example the glue-word and is used to glue 2 questions (a < 5, b == 5) together. If one side of the and would answer false the whole question would answer false, because with the glue-word and both sides need to be true in order to answer true. +and is not the only glue-word there are two others. They are all in the next table: +Question glue-words + + + +and +both sides need to be true in order to answer true + + +or +if one of the sides is true the answer is true + + +not +only if both of the sides are false the answer is false + + + +
+ + + + +Controlling execution +The execution controllers enable you — as their name implies — to control execution. + + +Have the turtle wait +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. + + + + wait + wait X +wait makes the turtle wait for X seconds. +repeat 36 [ + forward 5 + turnright 10 + wait 0.5 +] + 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. + + + + + +Execute "if" + + + + + if + if question [ ... ] +The code that is placed between the brackets will only be executed if the answer to the question is true. Please read for more information on questions in the question section. +x = 6 +if x > 5 [ + print "x is greater than five!" +] + On the first line x is set to 6. On the second line the question x > 5 is asked. Since the answer to this question is true the execution controller if will allow the code between the brackets to be executed + + + + + +Execute "while" + + + + + while + while question [ ... ] +The execution controller while is a lot like if. The difference is that while keeps repeating the code between the brackets till the answer to the question is false. +x = 1 +while x < 5 [ + forward 10 + wait 1 + x = x + 1 +] + On the first line x is set to 1. On the second line the question x < 5 is asked. Since the answer to this question is true the execution controller while starts executing the code between the brackets till the answer to the question is false. In this case the code between the brackets will be executed 4 times, because every time the fifth line is executed x increases by 1.. + + + + + +If not, in other words: "else" + + + + + else + if question [ ... ] else [ ... ] +else can be used in addition to the execution controller if. The code between the brackets after else is only executed if the answer to the question that is asked is false. +x = 4 +if x > 5 [ + print "x is greater than five!" +] else [ + print "x is smaller than six!" +] + The question asks if x is greater than 5. Since x is set to 4 on the first line the answer to the question is false. This means the code between the brackets after else gets executed. + + + + + +The "for" loop + + + + + for + for start point to end point [ ... ] +The for loop is a counting loop, &ie; it keeps count for you. +for x = 1 to 10 [ + print x * 7 + forward 15 +] + Every time the code between the brackets is executed the x is increased by 1, till x reaches the value of 10. The code between the brackets prints the x multiplied by 7. After this program finishes its execution you will see the times table of 7 on the canvas. + + + + + + + + +Create your own commands +learn is a very special command, because it is used to create your own commands. The command you create can take input and return output. Let us take a look at how a new command is created: +learn circle (x) [ + repeat 36 [ + forward x + turnleft 10 + ] +] + The new command is called circle. circle takes one input, a number, to set the size of the circle. circle returns no output. The circle command can now be used like a normal command in the rest of the code. See this example: learn circle (x) [ + repeat 36 [ + forward x + turnleft 10 + ] + ] + + go 30,30 + circle(20) + + go 40,40 + circle(50) + + +In the next example a command with a return value is created. +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) + In this example a new command called multiplyBySelf is created. The input of this command is multiplied by it self and then returned, using the return command. The return command is the way to output a value from a function you have created. + + + diff --git a/tde-i18n-en_GB/docs/tdeedu/kturtle/translator-guide.docbook b/tde-i18n-en_GB/docs/tdeedu/kturtle/translator-guide.docbook new file mode 100644 index 00000000000..3676f91bfc3 --- /dev/null +++ b/tde-i18n-en_GB/docs/tdeedu/kturtle/translator-guide.docbook @@ -0,0 +1,223 @@ + +Translator's Guide to &kturtle; +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. + +Creating a Directory to hold the Translated Files +First, you need to create a directory to store the translated files. Create a directory called tde-i18n/code/data/tdeedu/kturtle/ in your KDE CVS directory, where code is your country code (the 2- or 4- letter ISO code). +Copy the Makefile.am file from tdeedu/kturtle/data/ into this directory. Open it using your favorite text editor, replace all instances of en_US in the file with your country code (the one used above), and save the file. + + +How To Translate the &logo; Keywords (commands) + + +Copy the logokeywords.en_US.xml file from tdeedu/kturtle/data/ to the directory you have just created, and rename it to logokeywords.code.xml where code is your country code (the 2- or 4- letter ISO code). + +Translate the contents of the keyword tag (&ie; the information between keyword and keyword) into your own language wherever possible. Also, translate the contents of the alias tag, (&ie; the information between the alias and alias): these are used as shortcuts for the keyword. +For example, translate while in: keywordwhilekeyword +Please do not translate anything else and do not translate the English words in command name="english_word": these must stay in English. + +Save your file as UTF-8 (in &kate;, use Save As... and change to utf8 in the box on the right of the file name). + +Commit your file (add your filename in the Makefile.am) or send it to Anne-Marie. + +In case of any doubt, please contact Anne-Marie Mahfouf annemarie.mahfouf@free.fr for more information. + + + + + + +How To Translate the Syntax Highlighting Files + + +Copy the logohighlightstyle.en_US.xml file from tdeedu/kturtle/data/ to the directory you created to store the translated keywords file, and rename it to logohighlightstyle.code.xml where code is your country code (the 2- or 4- letter ISO code). + +In line 4 of the file, there is language name="en_US"...: here you change en_US to your language's ISO code (2 or 4 letters). +Translate into your own language the content of the item tag (&ie; the information between item and item). This content must match the logokeyword file. For example, translate while in: item while item and leave the spaces as they are (one at the beginning and one at the end). Please do not translate anything else. +Save your file as UTF-8 (in &kate;, use Save As... and change to utf8 in the box on the right of the file name). +Commit your file (add your filename in the Makefile.am) or send it to Anne-Marie. +In case of any doubt, please contact Anne-Marie Mahfouf annemarie.mahfouf@free.fr for more information. + + + + + +How To Translate the Examples + +Copy the English example files from tdeedu/kturtle/data/ 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. + +Translate the keywords in the examples, using those in the logokeywords.xml for your language. The keywords file file must be done, first, before translating the examples. + +Save your file as UTF-8 (in &kate;, use Save As... and change to utf8 in the box on the right of the file name) + +Commit your folder (add a Makefile.am inside) or send it to Anne-Marie. + +In case of any doubt, please contact Anne-Marie Mahfouf, annemarie.mahfouf@free.fr for more information. + +Finally, if you want, you can add your own examples in this folder. + + + + + diff --git a/tde-i18n-en_GB/docs/tdeedu/kturtle/using-kturtle.docbook b/tde-i18n-en_GB/docs/tdeedu/kturtle/using-kturtle.docbook new file mode 100644 index 00000000000..e250da7f1ba --- /dev/null +++ b/tde-i18n-en_GB/docs/tdeedu/kturtle/using-kturtle.docbook @@ -0,0 +1,1025 @@ + +Using &kturtle; + + + Here is a screenshot of &kturtle; in action + + + + + + &kturtle; Main Window + + + + +The main window of &kturtle; has two main parts: the code editor (3) on the left where you type the &logo; commands, and the canvas (4) on the right where the instructions are visualized. The canvas 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: the menu bar (1) from where all the actions can be reached, the toolbar (4) that allows you to quickly select the most used actions, and the statusbar (5) where you will find feedback on the state of &kturtle;. + + +The Code Editor +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 Edit and the Tools 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. +You have several ways to get some code in the editor. The easiest way is to use an already-made example: choose FileOpen Examples in the File menu and click on a file. The filename will tell you what the example is about (⪚ square.logo will draw a square). The file you choose will be opened in the the code editor, you can then use FileExecute Commands to run the code if you like. +You can open &logo; files by choosing FileOpen... . +The third way is to directly type your own code in the editor or to copy/paste some code from this user guide. +The cursor position is indicated in the statusbar, on the right with the Line number and Column number. + + + +The Canvas +The canvas is the area where the commands are visualized, where the commands draw a picture. In other words, it is the turtle's playground. After getting some code in the the code editor, and executing it using FileExecute Commands , 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. +This message should help you to resolve the error. +The picture that is drawn can be saved as an image (using FileSave Canvas ) or printed (using FilePrint... ). + + + +The Menubar +In the menu bar you find all the actions of &kturtle;. They are in the following groups: File, Edit, View, Tools, Settings, and Help. This section describes them all. + + +The <guimenu +>File</guimenu +> Menu + + + &Ctrl;N File New + Creates a new, empty &logo; file. + + + + + &Ctrl;O File Open... + Opens a &logo; file. + + + + + File Open Recent + Opens a &logo; file that has been opened recently. + + + + + &Ctrl;E File Open Examples + Show the folder with examples &logo; programs. The examples should be in your favorite language that you can choose in SettingsConfigure &kturtle;... . + + + + + + &Alt;Return File Execute Commands + Starts the execution of the commands in the code editor. + + + + + + Escape File Stop Execution + Stops the execution. This action is only enabled when the commands are actually executing. + + + + + + &Ctrl;S File Save + Saves the currently opened &logo; file. + + + + + + File Save As... + Saves the currently opened &logo; file on a specified location. + + + + + + File Save Canvas + Saves the current drawing on canvas into an image. + + + + + + &Ctrl;P File Print... + Prints either the current code in the editor or the current drawing on the canvas. + + + + + + &Ctrl;Q File Quit + Quits &kturtle;. + + + + + + The <guimenu +>Edit</guimenu +> Menu + + + + &Ctrl;Z Edit Undo + Undoes the last change to code. &kturtle; has unlimited undos. + + + + + + &Ctrl;&Shift;Z Edit Redo + Redoes an undone change to the code. + + + + + + &Ctrl;X Edit Cut + Cuts the selected text from the code editor to the clipboard. + + + + + + &Ctrl;C Edit Copy + Copies the selected text from the code editor to the clipboard. + + + + + + &Ctrl;V Edit Paste + Pastes the text from the clipboard to the editor. + + + + + + &Ctrl;F Edit Find... + With this action you can find phrases in the code. + + + + + + F3 Edit Find Next + Use this to find the next occurrence of the phrase. + + + + + + &Ctrl;R Edit Replace... + With this action you can replace phrases in the code. + + + + + + The <guimenu +>View</guimenu +> Menu + + + + &Ctrl;&Shift;F View Full Screen Mode + With this action you toggle the full screen mode. + Note: When code is executed while in full screen mode everything but the canvas is hidden. This makes it possible to write full screen programs in &kturtle;. + + + + + + F11 View Show Line Numbers + With this action you can show the line numbers in the code editor. This can be handy for finding errors. + + + + + + The <guimenu +>Tools</guimenu +> Menu + + + + &Alt;C Tools Colour Picker + This action opens the colour picker. Using the colour picker you can easily select a colour code and insert it in the code editor. + + + + + + &Ctrl;I Tools Indent + This action indents (adds white space at the beginning of) the lines that are selected. When indentation is used properly this can make code much easier to read. All examples use indentation, please check them out. + + + + + + &Ctrl;&Shift;I Tools Unindent + This action unindents (removes the white space at the beginning of) the lines that are selected. + + + + + + Tools Clean Indentation + This action cleans indentation (removes all the white space at the beginning of) the lines that are selected. + + + + + + &Ctrl;D Tools Comment + 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. + + + + + + &Ctrl;&Shift;D Tools Uncomment + This action removes the comment characters from the selected lines. + + + + + + The <guimenu +>Settings</guimenu +> Menu + + + +Settings Show/Hide Toolbar +Toggle the Main Toolbar + + + + + +Settings Show/Hide Statusbar +Toggle the Statusbar + + + + + + Settings Advanced Settings + Here you can change things you normally do not need to change. The Advanced Settings submenu has three items: Configure Editor... (the standard &kate; editor settings dialog), Configure Shortcuts... (the standard &kde; shortcut settings dialog), and Configure Toolbars... (the standard &kde; toolbars setting dialog). + + + + + + Settings Configure &kturtle;... + This is used to configure &kturtle;. Here you can change the language of the &logo; commands or set a new initial canvas size. + + + + + + + The <guimenu +>Help</guimenu +> Menu + + + + Help &kturtle; Handbook + This action shows the handbook that you are currently reading. + + + + + + &Shift;F1 Help What's This? + After activating this action the mouse arrow will be changed into a question mark arrow. When this arrow is used to click on parts of &kturtle; main window, a description of the particular part pops-up. + + + + + + F1 Help Help on: ... + 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 print 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 print command and you press F1. The handbook will then show all info on the print command. + This function is very important while learning programming. + + + + + + Help Report Bug... + Use this to report a problem with &kturtle; to the developers. These reports can be used to make future versions of &kturtle; even better. + + + + + + Help About &kturtle; + Here you find information on &kturtle;, like the authors and the license it comes with. + + + + + + Help About &kde; + Here you can find information on &kde;. If you do not know yet what &kde; is, this is a place you should not miss. + + + + + + + +The Toolbar +Here you can quickly reach the most used actions. By default, you will find here all main useful commands ending with the Execute Commands and Stop Execution icons. +You can configure the toolbar using SettingsAdvanced SettingsConfigure Toolbar... + + + +The Statusbar +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. + + + -- cgit v1.2.1