Skip to content
Browse files

xhtml checked

  • Loading branch information...
1 parent 70347a3 commit ded18780b5ed6d2b8a74cc64f2cf4e66aa29795b ralf-bonn committed Jan 9, 2005
View
102 lang/de/docs/background.html
@@ -1,45 +1,59 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<HTML>
-<HEAD>
- <TITLE>Moodle Docs: Background</TITLE>
- <LINK REL="stylesheet" HREF="../theme/standard/styles.php" TYPE="TEXT/CSS">
- <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<H2>Hintergrund</H2>
-
-<P>Moodle ist eine aktive sich weiterentwickelnde Lernplattform im Enstehungsprozess.</P>
-<P>Seit einigen Jahren arbeite ich schon auf die eine oder andere Art daran. Es begann,
- als ich in den 90er Jahren als Webmaster bei <a target=_top href="http://www.curtin.edu.au/">Curtin University
- of Technology</a> arbeitete und als Systemadministrator deren WebCT-Installation betreute.
- Ich erlebte viele frustrierende Momente mit dem Biest WebCT und entwickelte ein Jucken,
- dass schließlich ein Kratzen nach sich zog – es muss einen besseren Weg geben (nein, nicht
- Blackboard :-)).</P>
-<P>Auch weiss ich von vielen Leuten in Schulen und kleineren Institutionen (und einigen
- Großen!), dass sie das Internet besser nutzen möchten, aber nicht wissen, wie sie anfangen
- sollen in dem Irrgarten da draußen aus Technologien und pädagogischen Stilrichtungen.
- Ich habe immer gehofft es würde eine kostenlose Alternative geben, dass solche
- Menschen Hilfe finden, ihre Lehrfähigkeiten in eine Onlineumgebung einbringen zu können.</P>
-<P>Mein fester Glaube an die nichtrealisierten Möglichkeiten von internetbasiertem
- Unterricht ließ mich einen Masterabschluss in Erziehungswissenschaften absolvieren und
- promovieren, um so meine frühere Informatikerlaufbahn mit neuentwickelten Kenntnissen
- über die Art des Lernens und die Zusammenarbeit zu kombinieren.</P>
-<P>Seither durchlief Moodle etliche sehr verschiedene Prototypstadien bis zur Freigabe der
- Version 1.0 am 20. August 2002, an eine in hohem Maße ahnungslose Welt. Von da ab
- erfuhr Moodle eine stetige Serie konstant verbesserter Versionen.
-<P>Heute arbeite ich damit in etlichen Kursen und finde es ein äußerst brauchbares und bewährtes
- Mittel, um Onlinekurse hoher Qualität zu erstellen – andere berichten das Gleiche.
- Angesichts des Kontextes in dem Moodle entwickelt wurde, funktioniert es besonders
- gut für kleinere Institutionen oder für kleinere, intimere Klassen.</P>
-<P>Verglichen mit den großen Werkzeugen wie WebCT oder Blackboard denke ich, dass es
- nach wie vor den Ansprüchen in manchen Bereichen nicht genügt (wie z. B. Skalierbarkeit und
- Standardunterstützung), aber es geht in vielen anderen Bereichen als Sieger hervor (<a href="index.php?file=features.html">Funktionen</a>).
-</P>
-<P>&nbsp;</P>
-
-<P ALIGN="CENTER"><FONT SIZE="1"><A HREF="." TARGET="_top">Moodle Documentation</A></FONT></P>
-<P ALIGN="CENTER"><FONT SIZE="1">Version: $Id$</FONT></P>
-
-</BODY>
-</HTML>
+<html>
+<head>
+<title>Moodle Docs: Background</title>
+<link rel="stylesheet" href="docstyles.css" type=
+"TEXT/CSS">
+<meta http-equiv="Content-Type" content=
+"text/html; charset=us-ascii">
+</head>
+<body bgcolor="#FFFFFF">
+<h1>Hintergrund</h1>
+<p>Moodle ist eine aktive sich weiterentwickelnde Lernplattform
+im Enstehungsprozess.</p>
+<p>Seit einigen Jahren arbeite ich schon auf die eine oder andere
+Art daran. Es begann, als ich in den 90er Jahren als Webmaster
+bei <a target="_top" href="http://www.curtin.edu.au/">Curtin
+University of Technology</a> arbeitete und als
+Systemadministrator deren WebCT-Installation betreute. Ich
+erlebte viele frustrierende Momente mit dem Biest WebCT und
+entwickelte ein Jucken, dass schlie&szlig;lich ein Kratzen nach
+sich zog &ndash; es muss einen besseren Weg geben (nein, nicht
+Blackboard :-)).</p>
+<p>Auch weiss ich von vielen Leuten in Schulen und kleineren
+Institutionen (und einigen Gro&szlig;en!), dass sie das Internet
+besser nutzen m&ouml;chten, aber nicht wissen, wie sie anfangen
+sollen in dem Irrgarten da drau&szlig;en aus Technologien und
+p&auml;dagogischen Stilrichtungen. Ich habe immer gehofft es
+w&uuml;rde eine kostenlose Alternative geben, dass solche
+Menschen Hilfe finden, ihre Lehrf&auml;higkeiten in eine
+Onlineumgebung einbringen zu k&ouml;nnen.</p>
+<p>Mein fester Glaube an die nichtrealisierten M&ouml;glichkeiten
+von internetbasiertem Unterricht lie&szlig; mich einen
+Masterabschluss in Erziehungswissenschaften absolvieren und
+promovieren, um so meine fr&uuml;here Informatikerlaufbahn mit
+neuentwickelten Kenntnissen &uuml;ber die Art des Lernens und die
+Zusammenarbeit zu kombinieren.</p>
+<p>Seither durchlief Moodle etliche sehr verschiedene
+Prototypstadien bis zur Freigabe der Version 1.0 am 20. August
+2002, an eine in hohem Ma&szlig;e ahnungslose Welt. Von da ab
+erfuhr Moodle eine stetige Serie konstant verbesserter
+Versionen.</p>
+<p>Heute arbeite ich damit in etlichen Kursen und finde es ein
+&auml;u&szlig;erst brauchbares und bew&auml;hrtes Mittel, um
+Onlinekurse hoher Qualit&auml;t zu erstellen &ndash; andere
+berichten das Gleiche. Angesichts des Kontextes in dem Moodle
+entwickelt wurde, funktioniert es besonders gut f&uuml;r kleinere
+Institutionen oder f&uuml;r kleinere, intimere Klassen.</p>
+<p>Verglichen mit den gro&szlig;en Werkzeugen wie WebCT oder
+Blackboard denke ich, dass es nach wie vor den Anspr&uuml;chen in
+manchen Bereichen nicht gen&uuml;gt (wie z. B. Skalierbarkeit und
+Standardunterst&uuml;tzung), aber es geht in vielen anderen
+Bereichen als Sieger hervor (<a href=
+"index.php?file=features.html">Funktionen</a>).</p>
+<p> </p>
+<p align="center"><a href="." target="_top"><font size="1">Moodle
+Documentation</font></a></p>
+<p align="center"><font size="1">Version: $Id$</font></p>
+</body>
+</html>
View
420 lang/de/docs/coding.html
@@ -1,187 +1,269 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title>Moodle Dokumentation: Coding Guidelines</title>
<link rel="stylesheet" href="docstyles.css" type="TEXT/CSS">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+<meta http-equiv="Content-Type" content=
+"text/html; charset=us-ascii">
</head>
<body bgcolor="#FFFFFF">
<h1>Moodle Coding Guidelines</h1>
-<p class="normaltext">Die Stabilit&auml;t eines Programms wie Moodle h&auml;ngt weesentlich davon ab, dass alle Entwickler des Programmcodes bestimmte Grundregeln einheitlich anwenden. Diese sind hier definert.</p>
-<p class="normaltext">Dieser Text wird vorl&auml;ufig nicht ins Deustche &uuml;bersetzt. Wir gehen davon aus, dass alle Anwender, dier selber Programmteile f&uuml;r Moodle bearbeiten wollen so viel Englisch lesen und verstehen k&ouml;nnen dass sie diesen Text im Original verstehen. </p>
-<p class="normaltext">Any collaborative project needs consistency and stability
- to stay strong.</p>
-<p class="normaltext">These guidelines are to provide a goal for all Moodle code
- to strive to. It's true that some of the older existing code falls short in
- a few areas, but it will all be fixed eventually. All new code definitely must
- adhere to these standards as closely as possible.</p>
+<p class="normaltext">Die Stabilit&auml;t eines Programms wie
+Moodle h&auml;ngt weesentlich davon ab, dass alle Entwickler des
+Programmcodes bestimmte Grundregeln einheitlich anwenden. Diese
+sind hier definert.</p>
+<p class="normaltext">Dieser Text wird vorl&auml;ufig nicht ins
+Deustche &uuml;bersetzt. Wir gehen davon aus, dass alle Anwender,
+dier selber Programmteile f&uuml;r Moodle bearbeiten wollen so
+viel Englisch lesen und verstehen k&ouml;nnen dass sie diesen
+Text im Original verstehen.</p>
+<p class="normaltext">Any collaborative project needs consistency
+and stability to stay strong.</p>
+<p class="normaltext">These guidelines are to provide a goal for
+all Moodle code to strive to. It's true that some of the older
+existing code falls short in a few areas, but it will all be
+fixed eventually. All new code definitely must adhere to these
+standards as closely as possible.</p>
<h2>General Rules</h2>
<ol class="normaltext">
- <li class="spaced">All code files should use the .php extension.</li>
- <li class="spaced">All template files should use the .html extension.</li>
- <li class="spaced">All text files should use Unix-style text format (most text
- editors have this as an option).</li>
- <li class="spaced">All php tags must be 'full' tags like <font color="#339900">&lt;?php
- ?&gt;</font> ... not 'short' tags like <font color="#339900">&lt;? ?&gt;</font>.
- </li>
- <li class="spaced">All existing copyright notices must be retained. You can
- add your own if necessary.</li>
- <li class="spaced">Each file should include the main config.php file.</li>
- <li class="spaced">Each file should check that the user is authenticated correctly,
- using require_login() and isadmin(), isteacher(), iscreator() or isstudent().</li>
- <li class="spaced">All access to databases should use the functions in lib/datalib.php
- whenever possible - this allows compatibility across a wide range of databases.
- You should find that almost anything is possible using these functions. If you must write SQL code then make sure it is: cross-platform; restricted to specific functions
- within your code (usually a lib.php file); and clearly marked.</li>
- <li class="spaced">Don't create or use global variables except for the standard
- $CFG, $SESSION, $THEME and $USER.</li>
- <li class="spaced">All variables should be initialised or at least tested for
- existence using isset() or empty() before they are used.</li>
- <li class="spaced">All strings should be translatable - create new texts in
- the &quot;lang/en&quot; files and call them using get_string() or print_string().</li>
- <li class="spaced">All help files should be translatable - create new texts
- in the &quot;en/help&quot; directory and call them using helpbutton().</li>
+<li class="spaced">All code files should use the .php
+extension.</li>
+<li class="spaced">All template files should use the .html
+extension.</li>
+<li class="spaced">All text files should use Unix-style text
+format (most text editors have this as an option).</li>
+<li class="spaced">All php tags must be 'full' tags like
+<font color="#339900">&lt;?php ?&gt;</font> ... not 'short' tags
+like <font color="#339900">&lt;? ?&gt;</font>.</li>
+<li class="spaced">All existing copyright notices must be
+retained. You can add your own if necessary.</li>
+<li class="spaced">Each file should include the main config.php
+file.</li>
+<li class="spaced">Each file should check that the user is
+authenticated correctly, using require_login() and isadmin(),
+isteacher(), iscreator() or isstudent().</li>
+<li class="spaced">All access to databases should use the
+functions in lib/datalib.php whenever possible - this allows
+compatibility across a wide range of databases. You should find
+that almost anything is possible using these functions. If you
+must write SQL code then make sure it is: cross-platform;
+restricted to specific functions within your code (usually a
+lib.php file); and clearly marked.</li>
+<li class="spaced">Don't create or use global variables except
+for the standard $CFG, $SESSION, $THEME and $USER.</li>
+<li class="spaced">All variables should be initialised or at
+least tested for existence using isset() or empty() before they
+are used.</li>
+<li class="spaced">All strings should be translatable - create
+new texts in the "lang/en" files and call them using get_string()
+or print_string().</li>
+<li class="spaced">All help files should be translatable - create
+new texts in the "en/help" directory and call them using
+helpbutton().</li>
</ol>
-<p>&nbsp;</p>
+<p> </p>
<h2>Coding Style</h2>
-<p class="normaltext">I know it can be a little annoying to change your style
- if you're used to something else, but balance that annoyance against the annoyance
- of all the people trying later on to make sense of Moodle code with mixed styles.
- There are obviously many good points for and against any style that people use,
- but the current style just <strong>is</strong>, so please stick to it. </p>
+<p class="normaltext">I know it can be a little annoying to
+change your style if you're used to something else, but balance
+that annoyance against the annoyance of all the people trying
+later on to make sense of Moodle code with mixed styles. There
+are obviously many good points for and against any style that
+people use, but the current style just <strong>is</strong>, so
+please stick to it.</p>
<ol class="normaltext">
- <li class="spaced"><strong>Indenting</strong> should be consistently 4 spaces.
- Don't use tabs AT ALL. </li>
- <li class="spaced"><strong>Variable names</strong> should always be easy-to-read,
- meaningful lowercase English words. If you really need more than one word
- then run them together, but keep them short as possible. Use
-plural names for arrays of objects.
- <p class="examplecode"><font color="#006600">GOOD: $quiz<br />
- GOOD: $errorstring<br />
-GOOD: $assignments (for an array of objects)<br />
- GOOD: $i (but only in little loops)<br />
- <br />
- BAD: $Quiz <br />
- BAD: $aReallyLongVariableNameWithoutAGoodReason<br />
- BAD: $error_string</font></p>
- </li>
- <li class="spaced"><strong>Constants</strong> should always be in upper case,
- and always start with the name of the module. They should have words separated
- by underscores.
- <p class="examplecode"><font color="#006600">define(&quot;FORUM_MODE_FLATOLDEST&quot;,
- 1);</font></p>
- </li>
- <li class="spaced"><strong>Function names</strong> should be simple English
- words, and start with the name of the module to avoid conflicts between modules.
- Words should be separated by underscores. Parameters should always have sensible
- defaults if possible. Note there is no space between the function name and
- the following (brackets). <br />
- <p class="examplecode"> <font color="#007700">function </font><font color="#0000BB">forum_set_display_mode</font><font color="#007700">(</font><font color="#0000BB">$mode</font><font color="#007700">=</font><font color="#0000BB">0</font><font color="#007700">)
- {<br />
- &nbsp;&nbsp;&nbsp;&nbsp;global </font><font color="#0000BB">$USER</font><font color="#007700">,
- </font><font color="#0000BB">$CFG</font><font color="#007700">;<br />
- <br />
- &nbsp;&nbsp;&nbsp;&nbsp;if (</font><font color="#0000BB">$mode</font><font color="#007700">)
- {<br />
- &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</font><font color="#0000BB">$USER</font><font color="#007700">-&gt;</font><font color="#0000BB">mode
- </font><font color="#007700">= </font><font color="#0000BB">$mode</font><font color="#007700">;<br />
- &nbsp;&nbsp;&nbsp;&nbsp;} else if (empty(</font><font color="#0000BB">$USER</font><font color="#007700">-&gt;</font><font color="#0000BB">mode</font><font color="#007700">))
- {<br />
- &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</font><font color="#0000BB">$USER</font><font color="#007700">-&gt;</font><font color="#0000BB">mode
- </font><font color="#007700">= </font><font color="#0000BB">$CFG</font><font color="#007700">-&gt;</font><font color="#0000BB">forum_displaymode</font><font color="#007700">;<br />
- &nbsp;&nbsp;&nbsp;&nbsp;}<br />
- }</font></p>
- </li>
- <li class="spaced"><strong>Blocks</strong> must always be enclosed in curly
- braces (even if there is only one line). Moodle uses this style:
- <p class="examplecode"> <font color="#006600">if (</font><font color="#0000CC">$quiz</font><font color="#006600">-&gt;</font><font color="#0000CC">attempts</font><font color="#006600">)
- {<br />
- &nbsp;&nbsp;&nbsp;&nbsp;if (</font><font color="#0000CC">$numattempts </font><font color="#006600">&gt;
- </font><font color="#0000CC">$quiz</font><font color="#006600">-&gt;</font><font color="#0000CC">attempts</font><font color="#006600">)
- {<br />
- &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</font><font color="#0000CC">error</font><font color="#006600">(</font><font color="#0000BB">$strtoomanyattempts</font><font color="#006600">,
- </font><font color="#CC0000">"view.php?id=$cm</font><font color="#006600">-&gt;</font><font color="#CC0000">id"</font><font color="#006600">);<br />
- &nbsp;&nbsp;&nbsp;&nbsp;}<br />
- }</font></p>
- </li>
- <li class="spaced"><strong>Strings</strong> should be defined using single quotes
- where possible, for increased speed.<br />
- <p class="examplecode"> <font color="#006600">$var = 'some text without any
- variables';<br />
- $var = &quot;with special characters like a new line \n&quot;;<br />
- $var = 'a very, very long string with a '.$single.' variable in it';<br />
- $var = &quot;some $text with $many variables $within it&quot;; </font></p>
- </li>
- <li class="spaced"><strong>Comments</strong> should use two or three slashes
- and line up nicely with the code.
- <p class="examplecode"><font color="#006600">function </font><font color="#0000BB">forum_get_ratings_mean</font><font color="#007700">(</font><font color="#0000BB">$postid</font><font color="#007700">,
- </font><font color="#0000BB">$scale</font><font color="#007700">, </font><font color="#0000BB">$ratings</font><font color="#007700">=</font><font color="#0000BB">NULL</font><font color="#007700">)
- {<br />
- </font><font color="#FF8000">/// Return the mean rating of a post given
- to the current user by others.<br />
- /// Scale is an array of possible ratings in the scale<br />
- /// Ratings is an optional simple array of actual ratings (just integers)<br />
- <br />
- &nbsp;&nbsp;&nbsp;&nbsp;</font><font color="#007700">if (!</font><font color="#0000BB">$ratings</font><font color="#007700">)
- {<br />
- &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</font><font color="#0000BB">$ratings
- </font><font color="#007700">= array(); &nbsp;&nbsp;&nbsp;&nbsp;</font><font color="#FF8000">//
- Initialize the empty array</font><font color="#007700"><br />
- &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;if (</font><font color="#0000BB">$rates
- </font><font color="#007700">= </font><font color="#0000BB">get_records</font><font color="#007700">(</font><font color="#DD0000">"forum_ratings"</font><font color="#007700">,
- </font><font color="#DD0000">"post"</font><font color="#007700">, </font><font color="#0000BB">$postid</font><font color="#007700">))
- {<br />
- &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</font><font color="#FF8000">//
- Process each rating in turn</font><font color="#007700"><br />
- &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;foreach
- (</font><font color="#0000BB">$rates </font><font color="#007700">as </font><font color="#0000BB">$rate</font><font color="#007700">)
- {</font> <br />
- ....etc </p>
- </li>
- <li class="spaced"><strong>Space</strong> should be used liberally - don't be
- afraid to spread things out a little to gain some clarity. Generally, there
- should be one space between brackets and normal statements, but no space between
- brackets and variables or functions:<br />
- <p class="examplecode"> <font color="#007700">foreach (</font><font color="#0000BB">$objects
- </font><font color="#007700">as </font><font color="#0000BB">$key </font><font color="#007700">=&gt;</font><font color="#0000BB">
- $thing</font><font color="#007700">)</font><font color="#006600"> {<br />
- </font><font color="#007700">&nbsp;&nbsp;&nbsp;&nbsp;</font><font color="#0000BB">process($thing);</font><font color="#006600">
- <br />
- } <br />
- <br />
- </font><font color="#007700">if (</font><font color="#0000BB">$x </font><font color="#007700">==
- </font><font color="#0000BB">$y</font><font color="#007700">)</font><font color="#006600">
- {<br />
- </font><font color="#007700">&nbsp;&nbsp;&nbsp;&nbsp;</font><font color="#0000BB">$a
- </font><font color="#007700">= </font><font color="#0000BB">$b</font><font color="#007700">;</font><font color="#006600"><br />
- } else if (</font><font color="#0000BB">$x </font><font color="#007700">==
- </font><font color="#0000BB">$z</font><font color="#006600">) {<br />
- </font><font color="#007700">&nbsp;&nbsp;&nbsp;&nbsp;</font><font color="#0000BB">$a
- </font><font color="#007700">= </font><font color="#0000BB">$c</font><font color="#007700">;</font><font color="#006600"><br />
- } else {<br />
- </font><font color="#007700">&nbsp;&nbsp;&nbsp;&nbsp;</font><font color="#0000BB">$a
- </font><font color="#007700">= </font><font color="#0000BB">$d</font><font color="#007700">;</font><font color="#006600"><br />
- } </font></p>
- </li>
+<li class="spaced"><strong>Indenting</strong> should be
+consistently 4 spaces. Don't use tabs AT ALL.</li>
+<li class="spaced"><strong>Variable names</strong> should always
+be easy-to-read, meaningful lowercase English words. If you
+really need more than one word then run them together, but keep
+them short as possible. Use plural names for arrays of objects.
+<p class="examplecode"><font color="#006600">GOOD: $quiz<br>
+GOOD: $errorstring<br>
+GOOD: $assignments (for an array of objects)<br>
+GOOD: $i (but only in little loops)<br>
+<br>
+BAD: $Quiz<br>
+BAD: $aReallyLongVariableNameWithoutAGoodReason<br>
+BAD: $error_string</font></p>
+</li>
+<li class="spaced"><strong>Constants</strong> should always be in
+upper case, and always start with the name of the module. They
+should have words separated by underscores.
+<p class="examplecode"><font color=
+"#006600">define("FORUM_MODE_FLATOLDEST", 1);</font></p>
+</li>
+<li class="spaced"><strong>Function names</strong> should be
+simple English words, and start with the name of the module to
+avoid conflicts between modules. Words should be separated by
+underscores. Parameters should always have sensible defaults if
+possible. Note there is no space between the function name and
+the following (brackets).<br>
+<p class="examplecode"><font color="#007700">function</font>
+<font color="#0000BB">forum_set_display_mode</font><font color=
+"#007700">(</font><font color="#0000BB">$mode</font><font color=
+"#007700">=</font><font color="#0000BB">0</font><font color=
+"#007700">) {<br>
+    global</font> <font color="#0000BB">$USER</font><font color=
+"#007700">,</font> <font color="#0000BB">$CFG</font><font color=
+"#007700">;<br>
+<br>
+    if (</font><font color="#0000BB">$mode</font><font color=
+"#007700">) {<br>
+        </font><font color="#0000BB">$USER</font><font color=
+"#007700">-&gt;</font><font color="#0000BB">mode</font>
+<font color="#007700">=</font> <font color=
+"#0000BB">$mode</font><font color="#007700">;<br>
+    } else if (empty(</font><font color=
+"#0000BB">$USER</font><font color=
+"#007700">-&gt;</font><font color=
+"#0000BB">mode</font><font color="#007700">)) {<br>
+        </font><font color="#0000BB">$USER</font><font color=
+"#007700">-&gt;</font><font color="#0000BB">mode</font>
+<font color="#007700">=</font> <font color=
+"#0000BB">$CFG</font><font color=
+"#007700">-&gt;</font><font color=
+"#0000BB">forum_displaymode</font><font color="#007700">;<br>
+    }<br>
+}</font></p>
+</li>
+<li class="spaced"><strong>Blocks</strong> must always be
+enclosed in curly braces (even if there is only one line). Moodle
+uses this style:
+<p class="examplecode"><font color="#006600">if
+(</font><font color="#0000CC">$quiz</font><font color=
+"#006600">-&gt;</font><font color=
+"#0000CC">attempts</font><font color="#006600">) {<br>
+    if (</font><font color="#0000CC">$numattempts</font>
+<font color="#006600">&gt;</font> <font color=
+"#0000CC">$quiz</font><font color=
+"#006600">-&gt;</font><font color=
+"#0000CC">attempts</font><font color="#006600">) {<br>
+        </font><font color="#0000CC">error</font><font color=
+"#006600">(</font><font color=
+"#0000BB">$strtoomanyattempts</font><font color=
+"#006600">,</font> <font color=
+"#CC0000">"view.php?id=$cm</font><font color=
+"#006600">-&gt;</font><font color=
+"#CC0000">id"</font><font color="#006600">);<br>
+    }<br>
+}</font></p>
+</li>
+<li class="spaced"><strong>Strings</strong> should be defined
+using single quotes where possible, for increased speed.<br>
+<p class="examplecode"><font color="#006600">$var = 'some text
+without any variables';<br>
+$var = "with special characters like a new line \n";<br>
+$var = 'a very, very long string with a '.$single.' variable in
+it';<br>
+$var = "some $text with $many variables $within it";</font></p>
+</li>
+<li class="spaced"><strong>Comments</strong> should use two or
+three slashes and line up nicely with the code.
+<p class="examplecode"><font color="#006600">function</font>
+<font color="#0000BB">forum_get_ratings_mean</font><font color=
+"#007700">(</font><font color=
+"#0000BB">$postid</font><font color="#007700">,</font>
+<font color="#0000BB">$scale</font><font color="#007700">,</font>
+<font color="#0000BB">$ratings</font><font color=
+"#007700">=</font><font color="#0000BB">NULL</font><font color=
+"#007700">) {<br></font> <font color="#FF8000">/// Return the
+mean rating of a post given to the current user by others.<br>
+/// Scale is an array of possible ratings in the scale<br>
+/// Ratings is an optional simple array of actual ratings (just
+integers)<br>
+<br>
+    </font><font color="#007700">if (!</font><font color=
+"#0000BB">$ratings</font><font color="#007700">) {<br>
+        </font><font color="#0000BB">$ratings</font> <font color=
+"#007700">= array();     </font><font color="#FF8000">//
+Initialize the empty array</font><font color="#007700"><br>
+        if (</font><font color="#0000BB">$rates</font>
+<font color="#007700">=</font> <font color=
+"#0000BB">get_records</font><font color=
+"#007700">(</font><font color=
+"#DD0000">"forum_ratings"</font><font color="#007700">,</font>
+<font color="#DD0000">"post"</font><font color="#007700">,</font>
+<font color="#0000BB">$postid</font><font color="#007700">))
+{<br>
+            </font><font color="#FF8000">// Process each rating
+in turn</font><font color="#007700"><br>
+            foreach (</font><font color="#0000BB">$rates</font>
+<font color="#007700">as</font> <font color=
+"#0000BB">$rate</font><font color="#007700">) {</font><br>
+....etc</p>
+</li>
+<li class="spaced"><strong>Space</strong> should be used
+liberally - don't be afraid to spread things out a little to gain
+some clarity. Generally, there should be one space between
+brackets and normal statements, but no space between brackets and
+variables or functions:<br>
+<p class="examplecode"><font color="#007700">foreach
+(</font><font color="#0000BB">$objects</font> <font color=
+"#007700">as</font> <font color="#0000BB">$key</font>
+<font color="#007700">=&gt;</font> <font color=
+"#0000BB">$thing</font><font color="#007700">)</font>
+<font color="#006600">{<br></font> <font color=
+"#007700">    </font><font color=
+"#0000BB">process($thing);</font> <font color="#006600"><br>
+}<br>
+<br></font> <font color="#007700">if (</font><font color=
+"#0000BB">$x</font> <font color="#007700">==</font> <font color=
+"#0000BB">$y</font><font color="#007700">)</font> <font color=
+"#006600">{<br></font> <font color=
+"#007700">    </font><font color="#0000BB">$a</font> <font color=
+"#007700">=</font> <font color="#0000BB">$b</font><font color=
+"#007700">;</font><font color="#006600"><br>
+} else if (</font><font color="#0000BB">$x</font> <font color=
+"#007700">==</font> <font color="#0000BB">$z</font><font color=
+"#006600">) {<br></font> <font color=
+"#007700">    </font><font color="#0000BB">$a</font> <font color=
+"#007700">=</font> <font color="#0000BB">$c</font><font color=
+"#007700">;</font><font color="#006600"><br>
+} else {<br></font> <font color="#007700">    </font><font color=
+"#0000BB">$a</font> <font color="#007700">=</font> <font color=
+"#0000BB">$d</font><font color="#007700">;</font><font color=
+"#006600"><br>
+}</font></p>
+</li>
</ol>
-<p>&nbsp;</p>
+<p> </p>
<h2>Database structures</h2>
<ol class="normaltext">
- <li class="spaced">Every table must have an auto-incrementing <strong>id</strong> field (INT10) as primary index.</li>
- <li class="spaced">The main table containing instances of each module must have the same name as the module (eg <strong>widget</strong>) and contain the following minimum fields:
- <ul>
- <li><strong>id</strong> - as described above</li>
- <li><strong>course</strong> - the id of the course that each instance belongs to</li>
- <li><strong>name</strong> - the full name of each instance of the module</li>
- </ul>
- </li>
- <li class="spaced">Other tables associated with a module that contain information about 'things' should be named <strong>widget_things</strong> (note the plural).</li>
- <li class="spaced">Column names should be simple and short, following the same rules as for variable names.</li>
- <li class="spaced">Where possible, columns that contain a reference to the id field of another table (eg <strong>widget</strong>) should be called <strong>widgetid</strong>. (Note that this convention is newish and not followed in some older tables)</li>
- <li class="spaced">Boolean fields should be implemented as small integer fields (eg INT4) containing 0 or 1, to allow for later expansion of values if necessary.</li>
- <li class="spaced">Most tables should have a <strong>timemodified</strong> field (INT10) which is updated with a current timestamp obtained with the PHP <strong>time</strong>() function.</li>
+<li class="spaced">Every table must have an auto-incrementing
+<strong>id</strong> field (INT10) as primary index.</li>
+<li class="spaced">The main table containing instances of each
+module must have the same name as the module (eg
+<strong>widget</strong>) and contain the following minimum
+fields:
+<ul>
+<li><strong>id</strong> - as described above</li>
+<li><strong>course</strong> - the id of the course that each
+instance belongs to</li>
+<li><strong>name</strong> - the full name of each instance of the
+module</li>
+</ul>
+</li>
+<li class="spaced">Other tables associated with a module that
+contain information about 'things' should be named
+<strong>widget_things</strong> (note the plural).</li>
+<li class="spaced">Column names should be simple and short,
+following the same rules as for variable names.</li>
+<li class="spaced">Where possible, columns that contain a
+reference to the id field of another table (eg
+<strong>widget</strong>) should be called
+<strong>widgetid</strong>. (Note that this convention is newish
+and not followed in some older tables)</li>
+<li class="spaced">Boolean fields should be implemented as small
+integer fields (eg INT4) containing 0 or 1, to allow for later
+expansion of values if necessary.</li>
+<li class="spaced">Most tables should have a
+<strong>timemodified</strong> field (INT10) which is updated with
+a current timestamp obtained with the PHP <strong>time</strong>()
+function.</li>
</ol>
<hr>
-<p align="CENTER"><font size="1"><a href="." target="_top">Moodle Documentation</a></font></p>
-<p align="CENTER"><font size="1">Version: $Id$</font></p>
+<p align="center"><a href="." target="_top"><font size="1">Moodle
+Documentation</font></a></p>
+<p align="center"><font size="1">Version: $Id$</font></p>
</body>
-</html>
+</html>
View
410 lang/de/docs/credits.html
@@ -1,206 +1,204 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<HTML>
-<HEAD>
- <TITLE>Moodle Dokumentation: Danke sch&ouml;n</TITLE>
- <LINK REL="stylesheet" HREF="../theme/standard/styles.php" TYPE="TEXT/CSS">
- <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<H2>Credits</H2>
-
-<P><B>Moodle </B>seinerseits unterliegt dem Copyright &copy; 2001-2002, <A TARGET=_top HREF="http://dougiamas.com/">
- Martin Dougiamas</A>. &nbsp;Es wird verbreitet unter der <A HREF="?file=licence.html">
- GNU Public License</A>.</P>
-
-
-
-<H3><br />Ein besonderer Dank gilt:</H3>
-<UL>
- <B><A TARGET=_top HREF="http://pctaylor.com">Dr Peter C. Taylor</A></B>,
- von der Curtin University of Technology in Perth, Australia, f&uuml;r seine Mitwirkung an den ersten Prototypen und f&uuml;r viele n&uuml;tzliche Anregungen auf dem Weg von Moodle.</LI>
-</UL>
-
-
-
-<H3><br />&Uuml;bersetzungen</H3>
-<BLOCKQUOTE>
-<P>Vielen Dank an all diese Leute - jede &Uuml;bersetzung erfordert viele Stunden Arbeitk, es sind jeweils &uuml;ber 900 Begriffe und viele Hilfedateien zu &uuml;bersetzen. Sie sind in der Reihenfolge aufgelistet, in der sie zum Projekt hinzugestossen sind.
-<UL>
- <LI><B>en - Englisch</B>, von Martin Dougiamas
- <LI><B>fr - Franz&ouml;sisch</B>, von S&eacute;bastien Nam&egrave;che, seb@gaia.anet.fr, <A HREF="http://gaia.anet.fr/">http://gaia.anet.fr/</A>
- <LI><B>fi - Finnisch</B>, von Petri Asikainen (paca@sci.fi), Jaana Tolvanen (jaanat@cedunet.com)
- <LI><B>it - Italienisch</B>, von Davide Suraci, icarused@tiscalinet.it
- <LI><B>pt_br - Portugisich (Brasilen)</B>, von Fabricio Valadares, webdesigner@unincor.br
- <LI><B>de - Deutschn</B>, von Holger Schadeck, Holger.Schadeck@webdesign-forum.de und vielen anderen mehr
- <LI><B>es_mx - Spanisch (Mexico)</B>, von Claudio Tavares, <A HREF="http://enlaceacademico.com">enlaceacademico.com</A>
- <LI><B>es_es - Spanisch </B>, von Antonio J. Navarro Vergara, anavarro@sextaisla.com, <A HREF="http://www.sextaisla.com">www.sextaisla.com</A>
- <LI><B>ca - Catalanisch</B>, von Carles Bellver with the help of Merc&egrave; Renau,
- Clara Andr&eacute;s and Jordi Adell, cent@uji.es, <A HREF="http://cent.uji.es">Centre d'Educaci&oacute; i Noves Tecnologies</A>
- <LI><B>no - Norwegisch</B>, von Jøran Sørbø, joran.sorbo@teleweb.no
- <LI><B>id - Indonesisch</B>, von Arfan Hidayat, ivanh@telkom.net, <A HREF="http://www.kursusmaya.com">http://www.kursusmaya.com</A>
- <LI><B>ja - Japanisch</B>, von Mitsuhiro Yoshida, mits@mitstek.com, <A HREF="http://mitstek.com">http://mitstek.com</A>
- <LI><B>tr - T&uuml;rkisch</B>, von M. C&uuml;neyt Birk&ouml;k, cuneyt@birkok.net, <A HREF="http://birkok.net">http://birkok.net</A>
- <LI><B>zh_cn - Chinesisch</B>, von Zhang Dexuan, cncoolbit@hotmail.com
- <LI><B>ar - Arabisch</B>, von Ahmed Nabil, ana@harf.com
- <LI><B>sv - Schwedisch</B>, von Set Lonnert, set@setlonnert.com, <A HREF="http://setlonnert.com">http://setlonnert.com</A>
- <LI><B>th - Thail&auml;ndisch</B>, von Wim Singhanart, minkowski@ntlworld.com, <A HREF="http://www.suthira.net">www.suthira.net</A>
- <LI><B>nl - Niederl&auml;ndisch</B>, von Hans Zwart (hans@hansdezwart.info) and Jacob Romeyn (jromeyn@thekingsschool.net)
- <LI><B>es_ar - Spanisch (Argentinien)</B>, von Rodrigo Vigil (rmvigil@frre.utn.edu.ar)
-
-</UL>
-</BLOCKQUOTE>
-
-<H3><br />Themes</H3>
-<BLOCKQUOTE>
-<P>Themes machen Moodle Farbig und lebendig. Hier sind alle Themes f&uuml;r Moodle und ihre Entwickler:
-<UL>
- <LI><B>standard* und cordoroyblue</B>, von Martin Dougiamas
- <LI><B>oceanblue</B>, von Mitsuhiro Yoshida, <A HREF="http://mitstek.com">http://mitstek.com</A>
- <LI><B>brightretro</B>, von Thomas Murdock, <A HREF="http://sand-paper.org/">http://sand-paper.org</A>
- <LI><B>garden</B>, von Spiggy, <A HREF="http://phpgirl.com">http://phpgirl.com</A>
-</UL>
-</BLOCKQUOTE>
-
-
-<H3><br />Andere Unterst&uuml;tzer</H3>
-<BLOCKQUOTE>
-<P>Dank an all die anderen
-<UL>
- <LI>die uns beschenkt haben &uuml;ber die <A TARGET=_top HREF="http://moodle.com/donations">Donations page</A>,
- <LI>Unterst&uuml;tzer auf der <A TARGET=_top HREF="http://bugs.moodle.com">Fehlermeldeseite</A>, und <LI>all die, die beteilugt waren bei den "<A TARGET=_top HREF="http://moodle.com/course/">Using Moodle</A>" course at moodle.com</A>
-</UL>
-</P>
-
-<P>Ein besonderer Dank gilt all denen, die uns mit konstruktiven Diskussionen und der Entwicklung von Codes unterst&uuml;ptzt haben. Die Litse ist lang und ver&auml;ndert sich andauernd:
- <UL>
- Art Lader,
- Matt Hope,
- Tom Murdock,
- S&eacute;bastien Nam&egrave;che,
- Petri Asikainen,
- James Miller,
- Dustin Rue,
- Holger Schadeck,
- Giovanni Tummarello,
- John Windmueller,
- Sean Keogh,
- Mitsuhiro Yoshida,
- Mark Kimes,
- Greg Barnett,
- Mary Hunter
- </UL>
-</P>
-
-<P>Es haben so viele dieses Projekt bisher unterst&uuml;tzt, dass ich vielleicht manchen vergessen habe. Es ist nicht einfach, sich an alle zu erinnern. Wenn ich Dich vergessen haben sollte, schick mir eine Mail und erinnere mich. :-)
-</P>
-
-</BLOCKQUOTE>
-
-
-<H3><br />Moodle Bibliotheken</H3>
-
-<BLOCKQUOTE>
- <P>Einige, der in Moodle verwandten Bibliotheken, wurden von anderren Leuten geschrieben und wurden LGPL in Moodle verwandt. Mein Dank geht an die Autoren all dieser phantastischen Produkte ohne die Moodle viele Funktionen fehlen w&uuml;rde. Copyright Informationen f&uuml;r jedes Pakte finden Sie hier:</P>
-
- <P><B>ADOdb &nbsp; </B>- &nbsp;lib/adodb<br />
- </P>
-
- <BLOCKQUOTE>
- <P>Database abstraction library for MySQL, PostgreSQL, MSSQL, Oracle,
-Interbase, Foxpro, Access, ADO, Sybase, DB2 and ODBC.</P>
-
- <P>Version: 2.00 14 May 2002&nbsp;<br />
- Copyright &copy; 2000, 2001 John Lim (jlim@natsoft.com.my)<br />
- License: Dual LGPL and BSD-style<br />
- URL: &nbsp;<A HREF="http://php.weblogs.com/adodb" TARGET="newpage">http://php.weblogs.com/adodb</A><br />
- </P>
- </BLOCKQUOTE>
-
- <P><B>Graph Class</B> &nbsp; - &nbsp;lib/graphlib.php </P>
-
- <BLOCKQUOTE>
- <P>Class to draw line, point, bar, and area graphs, including numeric
- x-axis and double y-axis.</P>
-
- <P> Version: 1.6.3 (with modifications)<br />
- Copyright &copy;&nbsp;2000&nbsp; Herman Veluwenkamp,&nbsp;hermanV@mindless.com<br />
- License: LGPL<br />
- </P>
- </BLOCKQUOTE>
-
-
- <P><B>IP-Atlas</B>&nbsp; - &nbsp; lib/ipatlas</P>
-
- <BLOCKQUOTE>PHP scripts to show the location of an IP address on a map.<br />
- <br />
- Version: 1.0 (with modifications)<br />
- Copyright &copy; 2002 &nbsp; Ivan Kozik<br />
- License: GNU GPL<br />
- URL: <A HREF="http://www.xpenguin.com/ip-atlas.php" TARGET="newpage">http://www.xpenguin.com/ip-atlas.php</A><br />
- </BLOCKQUOTE>
-
-
- <P><B>PHP mailer</B> &nbsp; - &nbsp;lib/class.phpmailer.php<br />
- </P>
-
- <BLOCKQUOTE>Class for sending email using either sendmail, PHP mail(),
-or SMTP.&nbsp; Methods are based upon the standard AspEmail(tm) classes.<br />
- <br />
- Version 1.60, Created 03/30/2002<br />
- Copyright &copy; 2001 Brent R. Matzelle &lt;bmatzelle@yahoo.com&gt;<br />
- License: LGPL<br />
- URL: &nbsp; <A HREF="http://phpmailer.sourceforge.net" TARGET="newpage">http://phpmailer.sourceforge.net</A><br />
- <br />
- </BLOCKQUOTE>
-
-
-
- <P><B>PHP Simple Excel File Generator</B>&nbsp; - &nbsp; lib/psxlsgen.php</P>
-
- <BLOCKQUOTE>Class to generate very simple MS Excel files (xls)
-via PHP.<br />
- <br />
- Version: 0.3b<br />
- Copyright &copy; 2001 &nbsp;Erol Ozcan &lt;eozcan@superonline.com&gt;<br />
- License: GNU LGPL<br />
- URL: <A HREF="http://psxlsgen.sourceforge.net" TARGET="newpage">http://psxlsgen.sourceforge.net</A><br />
- </BLOCKQUOTE>
-
-
-
-
-
- <P><B>Richtext Editor</B>&nbsp; - &nbsp; lib/rte</P>
-
- <BLOCKQUOTE>HTML text editor for embedding in web pages.<br />
- <br />
- Version: 0.30 beta 1 (plus modifications)<br />
- Copyright &copy; 2001 Ramesys (Contracting Services) Limited &lt;Austin.France@Ramesys.com&gt;
- License: GNU LGPL<br />
- URL: <A HREF="http://richtext.sourceforge.net" TARGET="newpage">http://richtext.sourceforge.net</A><br />
- </BLOCKQUOTE>
-
-
- <P><B>SMTP class &nbsp; </B>- &nbsp;lib/class.smtp.php<br />
- </P>
-
- <BLOCKQUOTE>Class that can be used to connect and communicate with
- any SMTP server. <br />
- It implements all the SMTP functions defined in RFC821 except TURN.<br />
- <br />
- Version: 03/26/2001 <br />
- Copyright &copy; 2001 &nbsp;Chris Ryan &lt;chris@greatbridge.com&gt;<br />
- <br />
- </BLOCKQUOTE>
-
-
- <BLOCKQUOTE><br />
- </BLOCKQUOTE>
-
- <P ALIGN="CENTER"><FONT SIZE="1"><A HREF="." TARGET="_top">Moodle Documentation</A></FONT></P>
- <P ALIGN="CENTER"><FONT SIZE="1">Version: $Id$</FONT></P>
-
-
- </BODY>
- </HTML>
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+<title>Moodle Dokumentation: Danke sch&ouml;n</title>
+<link rel="stylesheet" href="docstyles.css" type=
+"TEXT/CSS">
+<meta http-equiv="Content-Type" content=
+"text/html; charset=us-ascii">
+</head>
+<body bgcolor="#FFFFFF">
+<h1>Credits</h1>
+<p><b>Moodle</b> seinerseits unterliegt dem Copyright &copy;
+2001-2002, <a target="_top" href="http://dougiamas.com/">Martin
+Dougiamas</a>.  Es wird verbreitet unter der <a href=
+"?file=licence.html">GNU Public License</a>.</p>
+<h3><br>
+Ein besonderer Dank gilt:</h3>
+<div style="margin-left: 2em"><b><a target="_top" href=
+"http://pctaylor.com">Dr Peter C. Taylor</a></b>, von der Curtin
+University of Technology in Perth, Australia, f&uuml;r seine
+Mitwirkung an den ersten Prototypen und f&uuml;r viele
+n&uuml;tzliche Anregungen auf dem Weg von Moodle.</div>
+<h3><br>
+&Uuml;bersetzungen</h3>
+<blockquote>
+<p>Vielen Dank an all diese Leute - jede &Uuml;bersetzung
+erfordert viele Stunden Arbeitk, es sind jeweils &uuml;ber 900
+Begriffe und viele Hilfedateien zu &uuml;bersetzen. Sie sind in
+der Reihenfolge aufgelistet, in der sie zum Projekt
+hinzugestossen sind.</p>
+<ul>
+<li><b>en - Englisch</b>, von Martin Dougiamas</li>
+<li><b>fr - Franz&ouml;sisch</b>, von S&eacute;bastien
+Nam&egrave;che, seb@gaia.anet.fr, <a href=
+"http://gaia.anet.fr/">http://gaia.anet.fr/</a></li>
+<li><b>de - Deutsch</b>, von Ralf Hilgenstock, info@moodle.de, <a href=
+"http://moodle.de/">http://www.moodle.de/</a>, <a href=
+"http://dialoge.net/">http://www.dialoge.net/</a></li>
+<li><b>fi - Finnisch</b>, von Petri Asikainen (paca@sci.fi),
+Jaana Tolvanen (jaanat@cedunet.com)</li>
+<li><b>it - Italienisch</b>, von Davide Suraci,
+icarused@tiscalinet.it</li>
+<li><b>pt_br - Portugisich (Brasilen)</b>, von Fabricio
+Valadares, webdesigner@unincor.br</li>
+<li><b>es_mx - Spanisch (Mexico)</b>, von Claudio Tavares,
+<a href="http://enlaceacademico.com">enlaceacademico.com</a></li>
+<li><b>es_es - Spanisch</b> , von Antonio J. Navarro Vergara,
+anavarro@sextaisla.com, <a href=
+"http://www.sextaisla.com">www.sextaisla.com</a></li>
+<li><b>ca - Catalanisch</b>, von Carles Bellver with the help of
+Merc&egrave; Renau, Clara Andr&eacute;s and Jordi Adell,
+cent@uji.es, <a href="http://cent.uji.es">Centre
+d'Educaci&oacute; i Noves Tecnologies</a></li>
+<li><b>no - Norwegisch</b>, von J&oslash;ran S&oslash;rb&oslash;,
+joran.sorbo@teleweb.no</li>
+<li><b>id - Indonesisch</b>, von Arfan Hidayat, ivanh@telkom.net,
+<a href=
+"http://www.kursusmaya.com">http://www.kursusmaya.com</a></li>
+<li><b>ja - Japanisch</b>, von Mitsuhiro Yoshida,
+mits@mitstek.com, <a href=
+"http://mitstek.com">http://mitstek.com</a></li>
+<li><b>tr - T&uuml;rkisch</b>, von M. C&uuml;neyt Birk&ouml;k,
+cuneyt@birkok.net, <a href=
+"http://birkok.net">http://birkok.net</a></li>
+<li><b>zh_cn - Chinesisch</b>, von Zhang Dexuan,
+cncoolbit@hotmail.com</li>
+<li><b>ar - Arabisch</b>, von Ahmed Nabil, ana@harf.com</li>
+<li><b>sv - Schwedisch</b>, von Set Lonnert, set@setlonnert.com,
+<a href="http://setlonnert.com">http://setlonnert.com</a></li>
+<li><b>th - Thail&auml;ndisch</b>, von Wim Singhanart,
+minkowski@ntlworld.com, <a href=
+"http://www.suthira.net">www.suthira.net</a></li>
+<li><b>nl - Niederl&auml;ndisch</b>, von Hans Zwart
+(hans@hansdezwart.info) and Jacob Romeyn
+(jromeyn@thekingsschool.net)</li>
+<li><b>es_ar - Spanisch (Argentinien)</b>, von Rodrigo Vigil
+(rmvigil@frre.utn.edu.ar)</li>
+</ul>
+</blockquote>
+<h3><br>
+Themes</h3>
+<blockquote>
+<p>Themes machen Moodle Farbig und lebendig. Hier sind alle
+Themes f&uuml;r Moodle und ihre Entwickler:</p>
+<ul>
+<li><b>standard* und cordoroyblue</b>, von Martin Dougiamas</li>
+<li><b>oceanblue</b>, von Mitsuhiro Yoshida, <a href=
+"http://mitstek.com">http://mitstek.com</a></li>
+<li><b>brightretro</b>, von Thomas Murdock, <a href=
+"http://sand-paper.org/">http://sand-paper.org</a></li>
+<li><b>garden</b>, von Spiggy, <a href=
+"http://phpgirl.com">http://phpgirl.com</a></li>
+</ul>
+</blockquote>
+<h3><br>
+Andere Unterst&uuml;tzer</h3>
+<blockquote>
+<p>Dank an all die anderen</p>
+<ul>
+<li>die uns beschenkt haben &uuml;ber die <a target="_top" href=
+"http://moodle.com/donations">Donations page</a>,</li>
+<li>Unterst&uuml;tzer auf der <a target="_top" href=
+"http://bugs.moodle.com">Fehlermeldeseite</a>, und</li>
+<li>all die, die beteilugt waren bei den "<a target="_top" href=
+"http://moodle.com/course/">Using Moodle</a>" course at
+moodle.com</li>
+</ul>
+<p>Ein besonderer Dank gilt all denen, die uns mit konstruktiven
+Diskussionen und der Entwicklung von Codes unterst&uuml;ptzt
+haben. Die Litse ist lang und ver&auml;ndert sich andauernd:</p>
+<div style="margin-left: 2em">Art Lader, Matt Hope, Tom Murdock,
+S&eacute;bastien Nam&egrave;che, Petri Asikainen, James Miller,
+Dustin Rue, Holger Schadeck, Giovanni Tummarello, John
+Windmueller, Sean Keogh, Mitsuhiro Yoshida, Mark Kimes, Greg
+Barnett, Mary Hunter</div>
+<p>Es haben so viele dieses Projekt bisher unterst&uuml;tzt, dass
+ich vielleicht manchen vergessen habe. Es ist nicht einfach, sich
+an alle zu erinnern. Wenn ich Dich vergessen haben sollte, schick
+mir eine Mail und erinnere mich. :-)</p>
+</blockquote>
+<h3><br>
+Moodle Bibliotheken</h3>
+<blockquote>
+<p>Einige, der in Moodle verwandten Bibliotheken, wurden von
+anderren Leuten geschrieben und wurden LGPL in Moodle verwandt.
+Mein Dank geht an die Autoren all dieser phantastischen Produkte
+ohne die Moodle viele Funktionen fehlen w&uuml;rde. Copyright
+Informationen f&uuml;r jedes Pakte finden Sie hier:</p>
+<p><b>ADOdb  </b> -  lib/adodb<br></p>
+<blockquote>
+<p>Database abstraction library for MySQL, PostgreSQL, MSSQL,
+Oracle, Interbase, Foxpro, Access, ADO, Sybase, DB2 and ODBC.</p>
+<p>Version: 2.00 14 May 2002 <br>
+Copyright &copy; 2000, 2001 John Lim (jlim@natsoft.com.my)<br>
+License: Dual LGPL and BSD-style<br>
+URL:  <a href="http://php.weblogs.com/adodb" target=
+"newpage">http://php.weblogs.com/adodb</a><br></p>
+</blockquote>
+<p><b>Graph Class</b>   -  lib/graphlib.php</p>
+<blockquote>
+<p>Class to draw line, point, bar, and area graphs, including
+numeric x-axis and double y-axis.</p>
+<p>Version: 1.6.3 (with modifications)<br>
+Copyright &copy; 2000  Herman
+Veluwenkamp, hermanV@mindless.com<br>
+License: LGPL<br></p>
+</blockquote>
+<p><b>IP-Atlas</b>  -   lib/ipatlas</p>
+<blockquote>PHP scripts to show the location of an IP address on
+a map.<br>
+<br>
+Version: 1.0 (with modifications)<br>
+Copyright &copy; 2002   Ivan Kozik<br>
+License: GNU GPL<br>
+URL: <a href="http://www.xpenguin.com/ip-atlas.php" target=
+"newpage">http://www.xpenguin.com/ip-atlas.php</a><br></blockquote>
+<p><b>PHP mailer</b>   -  lib/class.phpmailer.php<br></p>
+<blockquote>Class for sending email using either sendmail, PHP
+mail(), or SMTP.  Methods are based upon the standard
+AspEmail(tm) classes.<br>
+<br>
+Version 1.60, Created 03/30/2002<br>
+Copyright &copy; 2001 Brent R. Matzelle
+&lt;bmatzelle@yahoo.com&gt;<br>
+License: LGPL<br>
+URL:   <a href="http://phpmailer.sourceforge.net" target=
+"newpage">http://phpmailer.sourceforge.net</a><br>
+<br></blockquote>
+<p><b>PHP Simple Excel File Generator</b>  -  
+lib/psxlsgen.php</p>
+<blockquote>Class to generate very simple MS Excel files (xls)
+via PHP.<br>
+<br>
+Version: 0.3b<br>
+Copyright &copy; 2001  Erol Ozcan
+&lt;eozcan@superonline.com&gt;<br>
+License: GNU LGPL<br>
+URL: <a href="http://psxlsgen.sourceforge.net" target=
+"newpage">http://psxlsgen.sourceforge.net</a><br></blockquote>
+<p><b>Richtext Editor</b>  -   lib/rte</p>
+<blockquote>HTML text editor for embedding in web pages.<br>
+<br>
+Version: 0.30 beta 1 (plus modifications)<br>
+Copyright &copy; 2001 Ramesys (Contracting Services) Limited
+&lt;Austin.France@Ramesys.com&gt; License: GNU LGPL<br>
+URL: <a href="http://richtext.sourceforge.net" target=
+"newpage">http://richtext.sourceforge.net</a><br></blockquote>
+<p><b>SMTP class  </b> -  lib/class.smtp.php<br></p>
+<blockquote>Class that can be used to connect and communicate
+with any SMTP server.<br>
+It implements all the SMTP functions defined in RFC821 except
+TURN.<br>
+<br>
+Version: 03/26/2001<br>
+Copyright &copy; 2001  Chris Ryan
+&lt;chris@greatbridge.com&gt;<br>
+<br></blockquote>
+<blockquote><br></blockquote>
+<p align="center"><a href="." target="_top"><font size="1">Moodle
+Documentation</font></a></p>
+<p align="center"><font size="1">Version: $Id$</font></p>
+</blockquote>
+</body>
+</html>
View
342 lang/de/docs/cvs.html
@@ -1,157 +1,201 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
-<title>Moodle Dokumentation: Wie Sie das CVS benutzen k&ouml;nnen</title>
- <link rel="stylesheet" href="../theme/standard/styles.php" type="TEXT/CSS">
- <meta HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<title>Moodle Dokumentation: Wie Sie das CVS benutzen
+k&ouml;nnen</title>
+<link rel="stylesheet" href="docstyles.css" type=
+"TEXT/CSS">
+<meta http-equiv="Content-Type" content=
+"text/html; charset=us-ascii">
</head>
-<body bgcolor="#ffffff">
-<br /><h2>Zugang und Nutzung des CVS</h2><br />
-
-<blockquote><p>Das CVS bietet den Zugang zu den aktuellen Entwicklerversionen von Moodle. Die Anleitung zur Nutzung des CVS wird nicht ins Deutsche &uuml;bersetzt.</p></blockquote><br /> <br />
-<br />
-
+<body bgcolor="#FFFFFF">
+<br>
+<h1>Zugang und Nutzung des CVS</h1>
+<br>
+<blockquote>
+<p>Das CVS bietet den Zugang zu den aktuellen Entwicklerversionen
+von Moodle. Die Anleitung zur Nutzung des CVS wird nicht ins
+Deutsche &uuml;bersetzt.</p>
+</blockquote>
+<br>
+<br>
+<br>
<h2>Using CVS to access and update Moodle source code</h2>
<blockquote>
- <p>CVS is the Concurrent Versioning System. It's a commonly used way of storing
- source code because it keeps versions of all files so that nothing is ever
- lost, and usage by different people is tracked. It also provides ways to merge
- code if two or more people are working on the same file. All code and all
- versions are stored on a central server (in this case, at <a href="http://www.sf.net/">Sourceforge</a>).
- </p>
- <p>To use <a href="http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/moodle/moodle/">Moodle's
- CVS archive</a> (as a <a href="http://sourceforge.net/project/memberlist.php?group_id=30935">developer
- with write access</a>), you first need to have an <a href="http://sourceforge.net/account/register.php">account
- on Sourceforge</a>. For the examples on this page, let's assume your username
- is <strong><font color="#990000">myusername</font></strong> and your password
- is <strong><font color="#990000">mypassword</font></strong>. Once you have
- a Sourceforge account, contact me (<a
- href="http://dougiamas.com/">Martin Dougiamas</a>) so I can give you write access
- to particular directories.</p>
- <p>To avoid being prompted for <strong><font color="#990000">mypassword</font></strong>
- every time you run a CVS command, follow the <a href="http://sourceforge.net/account/editsshkeys.php">Sourceforge
- directions for using authorized keys</a>. This step is optional, but it can
- make your CVS experience a lot nicer.</p>
- <p>With that done, you should have all the permissions you need, so you just
- need to set up your machine and download the current sources so you can start
- working on them. Below are instructions for Unix and Windows systems.</p>
- <h3>1. Using CVS on Unix</h3>
- <blockquote>
- <p>Sourceforge CVS uses ssh as a transport layer for security, so you will
- have to set this CVS_RSH environment variable in your Unix shell:</p>
- <blockquote>
- <pre><strong>setenv CVS_RSH ssh</strong> (for csh, tcsh etc)</pre>
- <pre><strong>export CVS_RSH=ssh</strong> (for sh, bash etc)</pre>
- </blockquote>
- <p>It's best to put this in your .bashrc or .cshrc so you don't have to type
- it all the time. Then, check out Moodle using this (all one line): </p>
- <blockquote>
- <pre><strong>cvs -z3 -d:ext:myusername@cvs.sourceforge.net:/cvsroot/moodle co moodle</strong></pre>
- </blockquote>
- <p>Don't try to do run this first CVS command into an existing moodle directory
- - start fresh with a new directory.</p>
- <p>Note that you will be prompted for <strong><font color="#990000">mypassword</font></strong>
- for each command unless you set up <a href="http://sourceforge.net/account/editsshkeys.php">authorized
- keys</a></p>
- <p>Now, you should have a new 'moodle' directory. You can rename it and move
- it around if you like. Go into it: </p>
- <blockquote>
- <pre><strong>cd moodle </strong></pre>
- </blockquote>
- <p>All the latest Moodle files should be in there. You can now change files
- in your copy. To compare your files against the main CVS copy on the server
- use cvs diff, eg: </p>
- <blockquote>
- <pre><strong>cvs diff -c config-dist.php
-cvs diff -c lang</strong></pre>
- </blockquote>
- <p>To fetch the latest updates from the server use: </p>
- <blockquote>
- <pre><strong>cvs update -dP</strong> </pre>
- </blockquote>
- <p>To copy your new files back to the server you would do something like:
- </p>
- <blockquote>
- <pre><strong>cd lang/ca
-cvs commit</strong> </pre>
- </blockquote>
- <p>You will be prompted to add some comments (depends on your default text
- editor) ... add a meangingful comment and close the editor ... the files
- will be sent to Sourceforge and stored. Done! </p>
- <p>To save more time you can put default arguments into a file called .cvsrc
- in your home directory. For example, mine contains: </p>
- <blockquote>
- <pre><strong>diff -c
-update -dP</strong> </pre>
- </blockquote>
- <p>Try 'cvs help' for more details ... </p>
- <p>&nbsp;</p>
- </blockquote>
- <h3>2. Using CVS on Windows</h3>
- <blockquote>
- <p>These instructions are based on notes provided by Mitsuhiro Yoshida &lt;mits@mitstek.com&gt;.</p>
- <p>Firstly, download and install WinCVS.</p>
- <blockquote>
- <p><a href="https://sourceforge.net/project/showfiles.php?group_id=10072">https://sourceforge.net/project/showfiles.php?group_id=10072</a></p>
- </blockquote>
- <p>Secondly, download sfsetup for SourceForge ssh access, install it and reboot
- Windows.</p>
- <blockquote>
- <p><a href="http://sourceforge.net/projects/sfsetup/">http://sourceforge.net/projects/sfsetup/</a></p>
- </blockquote>
- <p>Next, configure WinCVS. Launch it, and select Admin -&gt; Preferences.
- Then change them as follows:</p>
- <blockquote>
- <p> [General]<br />
- <strong>CVSROOT data</strong>:<br />
- <strong>Authentication</strong>: ssh<br />
- <strong>Path</strong>: /cvsroot/moodle<br />
- <strong>Host address</strong>: cvs.sourceforge.net<br />
- <strong>User name</strong>: <font color="#990000">myusername</font><br />
- <strong>CVSROOT</strong>: <font color="#990000">myusername</font>@cvs.sourceforge.net:/cvsroot/moodle</p>
- <p>[Globals]<br />
- <strong>Checkout read-only</strong>: uncheck<br />
- <strong>Supply control when adding files</strong>: check<br />
- <strong>Quiet mode</strong>: uncheck<br />
- <strong>TCP/IP compression</strong>: check and select 9<br />
- <strong>Dirty files support</strong>: check<br />
- <strong>Prune(remove) empty directories</strong>: check<br />
- <strong>Disable splash screen</strong>: uncheck</p>
- </blockquote>
- <p>Congratulations, WinCVS is set up. Now, you should check out a complete
- working copy of the Moodle course code:</p>
- <ol>
- <li>Select 'Create -&gt; checkout'</li>
- <li>For the setting 'Module name and path on the server&quot;, type &quot;moodle&quot;,
- then click OK.</li>
- <li>Type in <strong><font color="#990000">mypassword</font></strong> and
- press Enter in the DOS window.</li>
- </ol>
- <p>After this first checkout, you can fetch updated files from the CVS server
- like this:</p>
- <ol>
- <li> Select folders or files you want to update</li>
- <li>Press right mouse button and select '<strong>Update selection</strong>'</li>
- <li>Press OK button</li>
- <li>Type in <strong><font color="#990000">mypassword</font></strong> and
- press Enter in the DOS window.</li>
- </ol>
- <p>After modifying files, you can commit them back to the CVS server like
- this:</p>
- <ol>
- <li>Select folders or files you want to commit</li>
- <li>Press right button and select '<strong>Commit selection</strong>'</li>
- <li>Press OK button</li>
- <li>Type in a meaningful comment and press OK button.</li>
- <li>Type in <strong><font color="#990000">mypassword</font></strong> and
- press Enter in the DOS window.</li>
- </ol>
- </blockquote>
- <p>&nbsp;</p>
- <p align="center">Good luck!</p>
- <p>&nbsp;</p>
+<p>CVS is the Concurrent Versioning System. It's a commonly used
+way of storing source code because it keeps versions of all files
+so that nothing is ever lost, and usage by different people is
+tracked. It also provides ways to merge code if two or more
+people are working on the same file. All code and all versions
+are stored on a central server (in this case, at <a href=
+"http://www.sf.net/">Sourceforge</a>).</p>
+<p>To use <a href=
+"http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/moodle/moodle/">Moodle's
+CVS archive</a> (as a <a href=
+"http://sourceforge.net/project/memberlist.php?group_id=30935">developer
+with write access</a>), you first need to have an <a href=
+"http://sourceforge.net/account/register.php">account on
+Sourceforge</a>. For the examples on this page, let's assume your
+username is <strong><font color=
+"#990000">myusername</font></strong> and your password is
+<strong><font color="#990000">mypassword</font></strong>. Once
+you have a Sourceforge account, contact me (<a href=
+"http://dougiamas.com/">Martin Dougiamas</a>) so I can give you
+write access to particular directories.</p>
+<p>To avoid being prompted for <strong><font color=
+"#990000">mypassword</font></strong> every time you run a CVS
+command, follow the <a href=
+"http://sourceforge.net/account/editsshkeys.php">Sourceforge
+directions for using authorized keys</a>. This step is optional,
+but it can make your CVS experience a lot nicer.</p>
+<p>With that done, you should have all the permissions you need,
+so you just need to set up your machine and download the current
+sources so you can start working on them. Below are instructions
+for Unix and Windows systems.</p>
+<h3>1. Using CVS on Unix</h3>
+<blockquote>
+<p>Sourceforge CVS uses ssh as a transport layer for security, so
+you will have to set this CVS_RSH environment variable in your
+Unix shell:</p>
+<blockquote>
+<pre>
+<strong>setenv CVS_RSH ssh</strong> (for csh, tcsh etc)
+</pre>
+<pre>
+<strong>export CVS_RSH=ssh</strong> (for sh, bash etc)
+</pre></blockquote>
+<p>It's best to put this in your .bashrc or .cshrc so you don't
+have to type it all the time. Then, check out Moodle using this
+(all one line):</p>
+<blockquote>
+<pre>
+<strong>cvs -z3 -d:ext:myusername@cvs.sourceforge.net:/cvsroot/moodle co moodle</strong>
+</pre></blockquote>
+<p>Don't try to do run this first CVS command into an existing
+moodle directory - start fresh with a new directory.</p>
+<p>Note that you will be prompted for <strong><font color=
+"#990000">mypassword</font></strong> for each command unless you
+set up <a href=
+"http://sourceforge.net/account/editsshkeys.php">authorized
+keys</a></p>
+<p>Now, you should have a new 'moodle' directory. You can rename
+it and move it around if you like. Go into it:</p>
+<blockquote>
+<pre>
+<strong>cd moodle </strong>
+</pre></blockquote>
+<p>All the latest Moodle files should be in there. You can now
+change files in your copy. To compare your files against the main
+CVS copy on the server use cvs diff, eg:</p>
+<blockquote>
+<pre>
+<strong>cvs diff -c config-dist.php
+cvs diff -c lang</strong>
+</pre></blockquote>
+<p>To fetch the latest updates from the server use:</p>
+<blockquote>
+<pre>
+<strong>cvs update -dP</strong>
+</pre></blockquote>
+<p>To copy your new files back to the server you would do
+something like:</p>
+<blockquote>
+<pre>
+<strong>cd lang/ca
+cvs commit</strong>
+</pre></blockquote>
+<p>You will be prompted to add some comments (depends on your
+default text editor) ... add a meangingful comment and close the
+editor ... the files will be sent to Sourceforge and stored.
+Done!</p>
+<p>To save more time you can put default arguments into a file
+called .cvsrc in your home directory. For example, mine
+contains:</p>
+<blockquote>
+<pre>
+<strong>diff -c
+update -dP</strong>
+</pre></blockquote>
+<p>Try 'cvs help' for more details ...</p>
+<p> </p>
+</blockquote>
+<h3>2. Using CVS on Windows</h3>
+<blockquote>
+<p>These instructions are based on notes provided by Mitsuhiro
+Yoshida &lt;mits@mitstek.com&gt;.</p>
+<p>Firstly, download and install WinCVS.</p>
+<blockquote>
+<p><a href=
+"https://sourceforge.net/project/showfiles.php?group_id=10072">https://sourceforge.net/project/showfiles.php?group_id=10072</a></p>
+</blockquote>
+<p>Secondly, download sfsetup for SourceForge ssh access, install
+it and reboot Windows.</p>
+<blockquote>
+<p><a href=
+"http://sourceforge.net/projects/sfsetup/">http://sourceforge.net/projects/sfsetup/</a></p>
+</blockquote>
+<p>Next, configure WinCVS. Launch it, and select Admin -&gt;
+Preferences. Then change them as follows:</p>
+<blockquote>
+<p>[General]<br>
+<strong>CVSROOT data</strong>:<br>
+<strong>Authentication</strong>: ssh<br>
+<strong>Path</strong>: /cvsroot/moodle<br>
+<strong>Host address</strong>: cvs.sourceforge.net<br>
+<strong>User name</strong>: <font color=
+"#990000">myusername</font><br>
+<strong>CVSROOT</strong>: <font color=
+"#990000">myusername</font>@cvs.sourceforge.net:/cvsroot/moodle</p>
+<p>[Globals]<br>
+<strong>Checkout read-only</strong>: uncheck<br>
+<strong>Supply control when adding files</strong>: check<br>
+<strong>Quiet mode</strong>: uncheck<br>
+<strong>TCP/IP compression</strong>: check and select 9<br>
+<strong>Dirty files support</strong>: check<br>
+<strong>Prune(remove) empty directories</strong>: check<br>
+<strong>Disable splash screen</strong>: uncheck</p>
+</blockquote>
+<p>Congratulations, WinCVS is set up. Now, you should check out a
+complete working copy of the Moodle course code:</p>
+<ol>
+<li>Select 'Create -&gt; checkout'</li>
+<li>For the setting 'Module name and path on the server", type
+"moodle", then click OK.</li>
+<li>Type in <strong><font color=
+"#990000">mypassword</font></strong> and press Enter in the DOS
+window.</li>
+</ol>
+<p>After this first checkout, you can fetch updated files from
+the CVS server like this:</p>
+<ol>
+<li>Select folders or files you want to update</li>
+<li>Press right mouse button and select '<strong>Update
+selection</strong>'</li>
+<li>Press OK button</li>
+<li>Type in <strong><font color=
+"#990000">mypassword</font></strong> and press Enter in the DOS
+window.</li>
+</ol>
+<p>After modifying files, you can commit them back to the CVS
+server like this:</p>
+<ol>
+<li>Select folders or files you want to commit</li>
+<li>Press right button and select '<strong>Commit
+selection</strong>'</li>
+<li>Press OK button</li>
+<li>Type in a meaningful comment and press OK button.</li>
+<li>Type in <strong><font color=
+"#990000">mypassword</font></strong> and press Enter in the DOS
+window.</li>
+</ol>
+</blockquote>
+<p> </p>
+<p align="center">Good luck!</p>
+<p> </p>
</blockquote>
-<p align="CENTER"><font size="1"><a href="." target="_top">Moodle Documentation</a></font></p>
-<p align="CENTER"><font size="1">Version: $Id: features.html,v 1.2 2001/12/09
- 10:34:19 martin Exp $</font></p>
+<p align="center"><a href="." target="_top"><font size="1">Moodle
+Documentation</font></a></p>
+<p align="center"><font size="1">Version: $Id: features.html,v
+1.2 2001/12/09 10:34:19 martin Exp $</font></p>
</body>
</html>
View
589 lang/de/docs/developer.html
@@ -1,290 +1,349 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
<head>
- <title>Moodle Dokumentation: Entwicklerhandbuch</title>
- <link rel="stylesheet" href="../theme/standard/styles.php" type="TEXT/CSS">
- <meta HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<title>Moodle Dokumentation: Entwicklerhandbuch</title>
+<link rel="stylesheet" href="docstyles.css" type=
+"TEXT/CSS">
+<meta http-equiv="Content-Type" content=
+"text/html; charset=us-ascii">
</head>
-
<body bgcolor="#FFFFFF">
-<h2>Entwicklerhandbuch</h2>
-<p>Dieses Dokument beschreibt die Grundlagen des Designs von Moodle und wie Sie daran mitwirken k&ouml;nnen.</p>
+<h1>Entwicklerhandbuch</h1>
+<p>Dieses Dokument beschreibt die Grundlagen des Designs von
+Moodle und wie Sie daran mitwirken k&ouml;nnen.</p>
<p>Abschnitte dieses Dokuments:</p>
<ol>
- <li><a href="#architecture">Moodle Architektur</a></li>
- <li><a href="#contribute">Wie Sie mitarbeiten k&ouml;nnen</a>
- <ul>
- <li><a href="#activities">Lernmodule Aktivit&auml;ten)</a></li>
- <li><a href="#themes">Themes</a></li>
- <li><a href="#languages">Sprachen</a></li>
- <li><a href="#database">Datenbankschema</a></li>
- <li><a href="#courseformats">Kursformate</a></li>
- <li><a href="#doc">Dokumentation und Artikel</a></li>
- <li><a href="#bugs">Fehlerbeseitigung</a></li>
- </ul>
- </li>
+<li><a href="#architecture">Moodle Architektur</a></li>
+<li><a href="#contribute">Wie Sie mitarbeiten k&ouml;nnen</a>
+<ul>
+<li><a href="#activities">Lernmodule Aktivit&auml;ten)</a></li>
+<li><a href="#themes">Themes</a></li>
+<li><a href="#languages">Sprachen</a></li>
+<li><a href="#database">Datenbankschema</a></li>
+<li><a href="#courseformats">Kursformate</a></li>
+<li><a href="#doc">Dokumentation und Artikel</a></li>
+<li><a href="#bugs">Fehlerbeseitigung</a></li>
+</ul>
+</li>
</ol>
-<br />
-<p>Vorbemerkung: Dieser Text wird nicht weiter ins Deutsche &uuml;bertragen. Die Entwicklung dieses Programms erfolgt in einer internationalen Gemeinschaft. Die Umgangssprache in Englisch. Wir gehen davon aus, dass alle an der Entwicklung interessierten Personen in der Lage sind, den Oroginaltext zu verstehen. </p><br />
-
-<p>&nbsp;</p>
-<h3><a name="architecture"></a>1. Moodle architecture</h3>
-<p>From a system administrator's perspective, Moodle has been designed according
- to the following criteria:</p>
+<br>
+<p>Vorbemerkung: Dieser Text wird nicht weiter ins Deutsche
+&uuml;bertragen. Die Entwicklung dieses Programms erfolgt in
+einer internationalen Gemeinschaft. Die Umgangssprache in
+Englisch. Wir gehen davon aus, dass alle an der Entwicklung
+interessierten Personen in der Lage sind, den Originaltext zu
+verstehen.</p>
+<br>
+<p> </p>
+<h3><a name="architecture" id="architecture"></a>1. Moodle
+architecture</h3>
+<p>From a system administrator's perspective, Moodle has been
+designed according to the following criteria:</p>
<ol>
- <li><strong>Moodle should run on the widest variety of platforms</strong><br />
- <br />
- The web application platform that runs on most platforms is PHP combined with
- MySQL, and this is the environment that Moodle has been developed in (on Linux,
- Windows, and Mac OS X). Moodle also uses the ADOdb library for database abstraction,
- which means Moodle can use <a href="http://php.weblogs.com/ADOdb_manual#drivers">more
- than ten different brands of database</a> (unfortunately, though, it can not
- yet <em><strong>set up tables</strong></em> in all these databases - more
- on this later). <br /><br />
- </li>
- <li><strong>Moodle should be easy to install, learn and modify</strong><br />
- <br />
- Early prototypes of Moodle (1999) were built using <a target=_top href="http://www.zope.org/">Zope</a>
- - an advanced object-oriented web application server. Unfortunately I found
- that although the technology was pretty cool, it had a very steep learning
- curve and was not very flexible in terms of system administration. The PHP
- scripting language, on the other hand, is very easy to get into (especially
- if you've done any programming using any other scripting language). Early
- on I made the decision to avoid using a class-oriented design - again, to
- keep it simple to understand for novices. Code reuse is instead achieved by
- libraries of clearly-named functions and consistent layout of script files.
- PHP is also easy to install (binaries are available for every platform) and
- is widely available to the point that most web hosting services provide it
- as standard.<br /><br />
- </li>
- <li><strong>It should be easy to upgrade from one version to the next</strong><br />
- <br />
- Moodle knows what version it is (as well as the versions of all plug-in modules)
- and a mechanism has been built-in so that Moodle can properly upgrade itself
- to new versions (for example it can rename database tables or add new fields).
- If using CVS in Unix for example, one can just do a &quot;cvs update -d&quot;
- and then visit the site home page to complete an upgrade.<br /><br />
- </li>
- <li><strong>It should be modular to allow for growth</strong><br />
- <br />
- Moodle has a number of features that are modular, including themes, activities,
- interface languages, database schemas and course formats. This allows anyone
- to add features to the main codebase or to even distribute them separately.
- More on this below in the next section.<br /><br />
- </li>
- <li><strong>It should be able to be used in conjunction with other systems</strong><br />
- <br />
- One thing Moodle does is keep all files for one course within a single, normal
- directory on the server. This would allow a system administrator to provide
- seamless forms of file-level access for each teacher, such as Appletalk, SMB,
- NFS, FTP, WebDAV and so on. The authentication modules allow Moodle to use
- LDAP, IMAP, POP3, NNTP and other databases as sources for user information.
- Otherwise, there is work yet to do. Features planned
- for Moodle in future versions include: import and export of Moodle data using XML-based
- formats (including IMS and SCORM); and increased use of style sheets for
- interface formatting (so that it can be integrated visually into other web sites).</li>
+<li><strong>Moodle should run on the widest variety of
+platforms</strong><br>
+<br>
+The web application platform that runs on most platforms is PHP
+combined with MySQL, and this is the environment that Moodle has
+been developed in (on Linux, Windows, and Mac OS X). Moodle also
+uses the ADOdb library for database abstraction, which means
+Moodle can use <a href=
+"http://php.weblogs.com/ADOdb_manual#drivers">more than ten
+different brands of database</a> (unfortunately, though, it can
+not yet <em><strong>set up tables</strong></em> in all these
+databases - more on this later).<br>
+<br></li>
+<li><strong>Moodle should be easy to install, learn and
+modify</strong><br>
+<br>
+Early prototypes of Moodle (1999) were built using <a target=
+"_top" href="http://www.zope.org/">Zope</a> - an advanced
+object-oriented web application server. Unfortunately I found
+that although the technology was pretty cool, it had a very steep
+learning curve and was not very flexible in terms of system
+administration. The PHP scripting language, on the other hand, is
+very easy to get into (especially if you've done any programming
+using any other scripting language). Early on I made the decision
+to avoid using a class-oriented design - again, to keep it simple
+to understand for novices. Code reuse is instead achieved by
+libraries of clearly-named functions and consistent layout of
+script files. PHP is also easy to install (binaries are available
+for every platform) and is widely available to the point that
+most web hosting services provide it as standard.<br>
+<br></li>
+<li><strong>It should be easy to upgrade from one version to the
+next</strong><br>
+<br>
+Moodle knows what version it is (as well as the versions of all
+plug-in modules) and a mechanism has been built-in so that Moodle
+can properly upgrade itself to new versions (for example it can
+rename database tables or add new fields). If using CVS in Unix
+for example, one can just do a "cvs update -d" and then visit the
+site home page to complete an upgrade.<br>
+<br></li>
+<li><strong>It should be modular to allow for growth</strong><br>
+<br>
+Moodle has a number of features that are modular, including
+themes, activities, interface languages, database schemas and
+course formats. This allows anyone to add features to the main
+codebase or to even distribute them separately. More on this
+below in the next section.<br>
+<br></li>
+<li><strong>It should be able to be used in conjunction with
+other systems</strong><br>
+<br>
+One thing Moodle does is keep all files for one course within a
+single, normal directory on the server. This would allow a system
+administrator to provide seamless forms of file-level access for
+each teacher, such as Appletalk, SMB, NFS, FTP, WebDAV and so on.
+The authentication modules allow Moodle to use LDAP, IMAP, POP3,
+NNTP and other databases as sources for user information.
+Otherwise, there is work yet to do. Features planned for Moodle
+in future versions include: import and export of Moodle data
+using XML-based formats (including IMS and SCORM); and increased
+use of style sheets for interface formatting (so that it can be
+integrated visually into other web sites).</li>
</ol>
-<p>&nbsp;</p>
-<h3><a name="contribute" id="contribute"></a>2. How you can contribute</h3>
-<p>As mentioned above, Moodle has a number of features that are modular. Even
- if you are not a programmer there are things you can change or help with.</p>
-<p><strong><a name="activities" id="activities"></a>Learning Activities</strong></p>
+<p> </p>
+<h3><a name="contribute" id="contribute"></a>2. How you can
+contribute</h3>
+<p>As mentioned above, Moodle has a number of features that are
+modular. Even if you are not a programmer there are things you
+can change or help with.</p>
+<p><strong><a name="activities" id="activities"></a>Learning
+Activities</strong></p>
<blockquote>
- <p>These are by far the most important modules, and reside in the 'mod' directory.
- There are seven default modules: assignment, choice, forum, journal, quiz,
- resource, and survey. Each module is in a separate subdirectory and consists
- of the following mandatory elements (plus extra scripts unique to each module):</p>
- <ul>
- <li>mod.html: a form to set up or update an instance of this module</li>
- <li>version.php: defines some meta-info and provides upgrading code</li>
- <li>icon.gif: a 16x16 icon for the module</li>
- <li>db/: SQL dumps of all the required db tables and data (for each database
- type) </li>
- <li>index.php: a page to list all instances in a course</li>
- <li>view.php: a page to view a particular instance</li>
- <li>lib.php: any/all functions defined by the module should be in here. If
- the modulename if called widget, then the required functions include:
- <ul>
- <li>widget_add_instance() - code to add a new instance of widget</li>
- <li>widget_update_instance() - code to update an existing instance</li>
- <li>widget_delete_instance() - code to delete an instance</li>
- <li>widget_user_outline() - given an instance, return a summary of a user's
- contribution</li>
- <li>widget_user_complete() - given an instance, print details of a user's
- contribution<br />
- </li>
- <li>To avoid possible conflict, any module functions should be named starting
- with widget_ and any constants you define should start with WIDGET_
- </li>
- </ul>
- </li>
- <li>Lastly, each module will have some language files that contain strings
- for that module. See below.</li>
- </ul>
- <p>The easiest way to start a new learning activity module is to use the template
- in <strong><a href="http://moodle.com/mod/newmodule_template.zip">mod/newmodule_template.zip</a>.</strong>
- Unzip it and follow the README inside. </p>
- <p>You might also like to post first in the <a href="http://moodle.com/mod/forum/view.php?id=44" target="_top">Activities
- modules forum on Using Moodle</a>.</p>
- <p>&nbsp;</p>
+<p>These are by far the most important modules, and reside in the
+'mod' directory. There are seven default modules: assignment,
+choice, forum, journal, quiz, resource, and survey. Each module
+is in a separate subdirectory and consists of the following
+mandatory elements (plus extra scripts unique to each
+module):</p>
+<ul>
+<li>mod.html: a form to set up or update an instance of this
+module</li>
+<li>version.php: defines some meta-info and provides upgrading
+code</li>
+<li>icon.gif: a 16x16 icon for the module</li>
+<li>db/: SQL dumps of all the required db tables and data (for
+each database type)</li>
+<li>index.php: a page to list all instances in a course</li>
+<li>view.php: a page to view a particular instance</li>
+<li>lib.php: any/all functions defined by the module should be in
+here. If the modulename if called widget, then the required
+functions include:
+<ul>
+<li>widget_add_instance() - code to add a new instance of
+widget</li>
+<li>widget_update_instance() - code to update an existing
+instance</li>
+<li>widget_delete_instance() - code to delete an instance</li>
+<li>widget_user_outline() - given an instance, return a summary
+of a user's contribution</li>
+<li>widget_user_complete() - given an instance, print details of
+a user's contribution<br></li>
+<li>To avoid possible conflict, any module functions should be
+named starting with widget_ and any constants you define should
+start with WIDGET_</li>
+</ul>
+</li>
+<li>Lastly, each module will have some language files that
+contain strings for that module. See below.</li>
+</ul>
+<p>The easiest way to start a new learning activity module is to
+use the template in <strong><a href=
+"http://moodle.com/mod/newmodule_template.zip">mod/newmodule_template.zip</a>.</strong>
+Unzip it and follow the README inside.</p>
+<p>You might also like to post first in the <a href=
+"http://moodle.com/mod/forum/view.php?id=44" target=
+"_top">Activities modules forum on Using Moodle</a>.</p>
+<p> </p>
</blockquote>
-<p> <strong><a name="themes" id="themes"></a>Themes</strong></p>
+<p><strong><a name="themes" id="themes"></a>Themes</strong></p>
<blockquote>
- <p>Themes (or skins) define the look of a site. A number of simple themes are
- provided in the main distribution, but you may want to create your own theme
- with your own colours, logo, styles and graphics.
-
- <p>Each theme is in a subdirectory of the &quot;theme&quot; directory, and contains
- at least the following files:</p>
- <ul>
- <li><strong>config.php</strong>: defines the theme colours used throughout
- the site</li>
- <li><strong>styles.php</strong>: the style sheet, containing CSS definitions
- for standard HTML elements as well as many Moodle elements.</li>
- <li><strong>header.html</strong>: Included at the top of each page. This is
- what you need to edit to add a logo at the top of pages, for example.</li>
- <li><strong>footer.html</strong>: Included at the bottom of each page.</li>
- </ul>
- <p>To create your own themes for current versions of Moodle:</p>
- <ol>
- <li>Copy one of the existing theme folders to one with a new name. I recommend
- starting with one of the standard themes.
- <li>Edit config.php and insert your own colours.
- <li>Edit styles.php and change your CSS styles.
- <li>Edit header.html and footer.html to add new logos, or change the layout.
- </ol>
- <p>Note that all these steps are optional - you can make a radically different
- look to your site simply by editing the colours in config.php</p>
- <p>Note also that Moodle upgrades <em>may</em> break themes slightly, so check the
- release notes carefully if you are using a custom theme.</p>
- <p>In particular, Moodle 2.0 will have a completely new display system, probably based on
- XSL transformations of XML output from Moodle. It is likely that the
- themes for this will be a completely different format, but the advantage will
- be a much higher possible degree of customisation (including moving elements
- around the page).</p>
- <p>More discussion about this in the <a target=_top href="http://moodle.com/mod/forum/view.php?id=46">Themes
- forum on Using Moodle</a>. If you create a nice theme that you think others
- might want to use, please post your zip file on the themes forum!<br />
- </p>
+<p>Themes (or skins) define the look of a site. A number of
+simple themes are provided in the main distribution, but you may
+want to create your own theme with your own colours, logo, styles
+and graphics.</p>
+<p>Each theme is in a subdirectory of the "theme" directory, and
+contains at least the following files:</p>
+<ul>
+<li><strong>config.php</strong>: defines the theme colours used
+throughout the site</li>
+<li><strong>styles.php</strong>: the style sheet, containing CSS
+definitions for standard HTML elements as well as many Moodle
+elements.</li>
+<li><strong>header.html</strong>: Included at the top of each
+page. This is what you need to edit to add a logo at the top of
+pages, for example.</li>
+<li><strong>footer.html</strong>: Included at the bottom of each
+page.</li>
+</ul>
+<p>To create your own themes for current versions of Moodle:</p>
+<ol>
+<li>Copy one of the existing theme folders to one with a new
+name. I recommend starting with one of the standard themes.</li>
+<li>Edit config.php and insert your own colours.</li>
+<li>Edit styles.php and change your CSS styles.</li>
+<li>Edit header.html and footer.html to add new logos, or change
+the layout.</li>
+</ol>
+<p>Note that all these steps are optional - you can make a
+radically different look to your site simply by editing the
+colours in config.php</p>
+<p>Note also that Moodle upgrades <em>may</em> break themes
+slightly, so check the release notes carefully if you are using a
+custom theme.</p>
+<p>In particular, Moodle 2.0 will have a completely new display
+system, probably based on XSL transformations of XML output from
+Moodle. It is likely that the themes for this will be a
+completely different format, but the advantage will be a much
+higher possible degree of customisation (including moving
+elements around the page).</p>
+<p>More discussion about this in the <a target="_top" href=
+"http://moodle.com/mod/forum/view.php?id=46">Themes forum on
+Using Moodle</a>. If you create a nice theme that you think
+others might want to use, please post your zip file on the themes
+forum!<br></p>
</blockquote>
-
- <p>&nbsp;</p>
-
-<p><strong><a name="languages" id="languages"></a>Languages</strong></p>
+<p> </p>
+<p><strong><a name="languages" id=
+"languages"></a>Languages</strong></p>
+<blockquote>
+<p>Moodle has been designed for internationalisation. Each
+'string' or 'page' of text that is displayed as part of the
+interface is drawn from a set of language files. Each language is
+a subdirectory of the directory 'lang'. The structure of the lang
+directory is as follows:</p>
+<p><strong>lang/en</strong> - directory containing all files for
+one language (eg English)</p>
+<ul>
+<li>moodle.php - strings for main interface</li>
+<li>assignment.php - strings for assignment module</li>
+<li>choice.php - strings for choice module</li>
+<li>forum.php - strings for forum module</li>
+<li>journal.php - strings for journal module</li>
+<li>quiz.php - strings for quiz module</li>
+<li>resource.php - strings for resource module</li>
+<li>survey.php - strings for survey module</li>
+<li>.... plus other modules if any.<br>
+<br>
+A string is called from these files using the
+<strong><em>get_string()</em></strong> or
+<em><strong>print_string()</strong></em> functions. Each string
+supports variable substitution, to support variable ordering in
+different languages.<em><br>
+<br></em> eg $strdueby = get_string("assignmentdueby",
+"assignment", userdate($date));<br>
+<br>
+If a string doesn't exist in a particular language, then the
+equivalent in English will automatically be used instead.</li>
+</ul>
+<p><strong>lang/en/help</strong> - contains whole help pages (for
+popup context-sensitive help)</p>
<blockquote>
- <p>Moodle has been designed for internationalisation. Each 'string' or 'page'
- of text that is displayed as part of the interface is drawn from a set of
- language files. Each language is a subdirectory of the directory 'lang'. The
- structure of the lang directory is as follows:</p>
- <p><strong>lang/en</strong> - directory containing all files for one language
- (eg English)</p>
- <ul>
- <li>moodle.php - strings for main interface</li>
- <li>assignment.php - strings for assignment module</li>
- <li>choice.php - strings for choice module</li>
- <li>forum.php - strings for forum module</li>
- <li>journal.php - strings for journal module </li>
- <li>quiz.php - strings for quiz module</li>
- <li>resource.php - strings for resource module</li>
- <li>survey.php - strings for survey module</li>
- <li>.... plus other modules if any.<br />
- <br />
- A string is called from these files using the <strong><em>get_string()</em></strong><em>
- </em>or<em> <strong>print_string()</strong> </em>functions. Each string
- supports variable substitution, to support variable ordering in different
- languages.<em><br />
- <br />
- </em>eg $strdueby = get_string(&quot;assignmentdueby&quot;, &quot;assignment&quot;,
- userdate($date)); <br />
- <br />
- If a string doesn't exist in a particular language, then the equivalent
- in English will automatically be used instead.</li>
- </ul>
- <p><strong>lang/en/help</strong> - contains whole help pages (for popup context-sensitive
- help)</p>
- <blockquote>
- <p>Main help pages are situated here, while help pages specific to each module
- are located in subdirectories with the module's name.</p>
- <p>You can insert a helpbutton in a page with the helpbutton function.</p>
- <p>eg helpbutton(&quot;text&quot;, &quot;Click here for help about text&quot;);</p>
- <p>and for modules:</p>
- <p>helpbutton(&quot;forumtypes&quot;, &quot;Forum types&quot;, &quot;forum&quot;);</p>
- </blockquote>
- <p>Note that you can edit languages online, using the administration web tools
- under &quot;Check this language&quot;. This makes it easy to not to only create
- new languages but to refine existing ones. If you are starting a new language,
- please contact me, <a target=_top href="http://dougiamas.com/">Martin Dougiamas</a>. </p>
- <p>You might also like to post in the <a target=_top href="http://moodle.com/mod/forum/view.php?id=43" target="_top">Languages
- forum on Using Moodle</a>. </p>
- <p>If you are maintaining a language an ongoing basis, I can give you <a href="?file=cvs.html">CVS
- write access to the Moodle source code</a> so that you can directly maintain
- the files.</p>
+<p>Main help pages are situated here, while help pages specific
+to each module are located in subdirectories with the module's
+name.</p>
+<p>You can insert a helpbutton in a page with the helpbutton
+function.</p>
+<p>eg helpbutton("text", "Click here for help about text");</p>
+<p>and for modules:</p>
+<p>helpbutton("forumtypes", "Forum types", "forum");</p>
</blockquote>
-<p><br />
- <strong><a name="database" id="database"></a>Database Schemas</strong></p>
+<p>Note that you can edit languages online, using the
+administration web tools under "Check this language". This makes
+it easy to not to only create new languages but to refine
+existing ones. If you are starting a new language, please contact
+me, <a target="_top" href="http://dougiamas.com/">Martin
+Dougiamas</a>.</p>
+<p>You might also like to post in the <a href=
+"http://moodle.com/mod/forum/view.php?id=43" target=
+"_top">Languages forum on Using Moodle</a>.</p>
+<p>If you are maintaining a language an ongoing basis, I can give
+you <a href="?file=cvs.html">CVS write access to the Moodle
+source code</a> so that you can directly maintain the files.</p>
+</blockquote>
+<p><br>
+<strong><a name="database" id="database"></a>Database
+Schemas</strong></p>
<blockquote>
- <p>Given a working database with defined tables, the intentionally simple SQL
- used in Moodle should work fine with a wide variety of database brands.</p>
-
- <p>A problem exists with <strong>automatically creating</strong> new tables
- in a database, which is what Moodle tries to do upon initial installation.
- Because every database is very different, there doesn't yet exist any way
- to do this in a platform-independent way. To support this automation in each
- database, schemas can be created that list the required SQL to create Moodle
- tables in a particular database. These are files in <strong>lib/db</strong>
- and inside the <strong>db</strong> subdirectory of each module.</p>
-
- <p>Currently, only MySQL and PostgreSQL are fully supported in this way. If you are
- familiar with another database (especially open source databases) and are
- willing to help port the existing schema, please get in contact with me (<a target=_top href="http://dougiamas.com/">Martin
- Dougiamas</a>).</p>
+<p>Given a working database with defined tables, the
+intentionally simple SQL used in Moodle should work fine with a
+wide variety of database brands.</p>
+<p>A problem exists with <strong>automatically creating</strong>
+new tables in a database, which is what Moodle tries to do upon
+initial installation. Because every database is very different,
+there doesn't yet exist any way to do this in a
+platform-independent way. To support this automation in each
+database, schemas can be created that list the required SQL to
+create Moodle tables in a particular database. These are files in
+<strong>lib/db</strong> and inside the <strong>db</strong>
+subdirectory of each module.</p>
+<p>Currently, only MySQL and PostgreSQL are fully supported in
+this way. If you are familiar with another database (especially
+open source databases) and are willing to help port the existing
+schema, please get in contact with me (<a target="_top" href=
+"http://dougiamas.com/">Martin Dougiamas</a>).</p>
</blockquote>
-<p>&nbsp;</p>
-<p><strong><a name="courseformats" id="courseformats"></a>Course Formats</strong></p>
+<p> </p>
+<p><strong><a name="courseformats" id="courseformats"></a>Course
+Formats</strong></p>
<blockquote>
- <p>Moodle currently supports three different course formats: weekly, topics and social.
- </p>
- <p>These are a little more connected to the rest of the code (and hence, less
- &quot;pluggable&quot;) but it is still quite easy to add new ones.</p>
- <p>If you have any ideas for different formats that you need or would like to
- see, get in touch with me and I'll do my absolute best to have them available
- in future releases.</p>
+<p>Moodle currently supports three different course formats:
+weekly, topics and social.</p>
+<p>These are a little more connected to the rest of the code (and
+hence, less "pluggable") but it is still quite easy to add new
+ones.</p>
+<p>If you have any ideas for different formats that you need or
+would like to see, get in touch with me and I'll do my absolute
+best to have them available in future releases.</p>
</blockquote>
-<p>&nbsp;</p>
-<p><strong><a name="doc" id="doc"></a>Documentation and articles</strong></p>
+<p> </p>
+<p><strong><a name="doc" id="doc"></a>Documentation and
+articles</strong></p>
<blockquote>
- <p>If you feel like writing a tutorial, an article, an academic paper or anything
- else about Moodle, please do! </p>
- <p>Put it on the web and make sure you include links to <a target=_top href="http://moodle.com/">http://moodle.com/</a></p>
- </blockquote>
-<p>&nbsp;</p>
-<p><strong><a name="bugs" id="bugs"></a>Participating in the bug tracker</strong></p>
+<p>If you feel like writing a tutorial, an article, an academic
+paper or anything else about Moodle, please do!</p>
+<p>Put it on the web and make sure you include links to
+<a target="_top" href=
+"http://moodle.com/">http://moodle.com/</a></p>
+</blockquote>
+<p> </p>
+<p><strong><a name="bugs" id="bugs"></a>Participating in the bug
+tracker</strong></p>
<blockquote>
- <p>Finally, I would like to invite you to register on the &quot;bug tracker&quot;
- at <a target=_top href="http://bugs.moodle.org">bugs.moodle.org</a> so you can file any
- bugs that you find and perhaps participate in discussing and fixing them.
- </p>
- <p>&quot;Bugs&quot; not only includes software bugs with current versions of
- Moodle, but also new ideas, feature requests and even constructive criticism
- of existing features. The beauty of open source is that anyone can participate
- in some way and help to create a better product for all of us to enjoy. In
- this project, your input is very welcome!</p>
+<p>Finally, I would like to invite you to register on the "bug
+tracker" at <a target="_top" href=
+"http://bugs.moodle.org">bugs.moodle.org</a> so you can file any
+bugs that you find and perhaps participate in discussing and
+fixing them.</p>
+<p>"Bugs" not only includes software bugs with current versions
+of Moodle, but also new ideas, feature requests and even
+constructive criticism of existing features. The beauty of open
+source is that anyone can participate in some way and help to
+create a better product for all of us to enjoy. In this project,
+your input is very welcome!</p>
</blockquote>
-<p>&nbsp;</p>
+<p> </p>
<blockquote>
- <blockquote>
- <blockquote>
- <p align="center">Thanks for using Moodle!</p>
- <p align="center">Cheers,<br />
- <a target=_top href="http://dougiamas.com/" target="_top">Martin Dougiamas</a></p>
- </blockquote>
- </blockquote>
+<blockquote>
+<blockquote>
+<p align="center">Thanks for using Moodle!</p>
+<p align="center">Cheers,<br>
+<a href="http://dougiamas.com/" target="_top">Martin
+Dougiamas</a></p>
+</blockquote>
+</blockquote>
</blockquote>
-<p>&nbsp;</p>
-<p>&nbsp;</p>
+<p> </p>
+<p> </p>
<blockquote>
- <p>&nbsp;</p>
+<p> </p>
</blockquote>
-<p align="CENTER"><font size="1"><a href="." target="_top">Moodle Documentation</a></font></p>
-<p align="CENTER"><font size="1">Version: $Id: developer.html,v 1.2 2001/12/09
- 10:34:19 martin Exp $</font></p>
-
-</body>
+<p align="center"><a href="." target="_top"><font size="1">Moodle
+Documentation</font></a></p>
+<p align="center"><font size="1">Version: $Id: developer.html,v
+1.2 2001/12/09 10:34:19 martin Exp $</font></p>
+</body>
+</html>
View
689 lang/de/docs/faq.html
@@ -1,283 +1,406 @@
-<HTML><HEAD><TITLE>Moodle Dokumentation: Frequently Asked Questions (FAQ)</TITLE>
-
-
-<H1>Frequently Asked Questions (FAQ)</H1>
-<P class=normaltext>Auf dieser Seite finden Sie einige der am h&auml;ufigsten
-gestellten Fragen von Menschen, die Moodle installieren. Wenn Sie der <A
-href="http://moodle.org/file.php/18/moddata/forum/166/17102/?file=install.html">Installationsanleitung</A>
-gefolgt sind und trotzdem ein Problem haben, dann sind Sie genau hier an der
-richtigen Stelle. </P>
-<P class=normaltext>Falls Sie hier keine Antworten auf Ihre Frage finden,
-versuchen Sie es auf der Seite moodle.org mit dem Kurs <A
-href="http://moodle.org/mod/forum/index.php?id=5" target=_top>Using Moodle</A>.
-Durchsuchen Sie zuerst die Foren mit einigen Schl&uuml;sselw&ouml;rtern, denn Ihr Problem
-k&ouml;nnte dort bereits diskutiert worden sein. Besteht keine solche Diskussion,
-versuchen Sie selbst eine im passenden Forum zu beginnen – normalerweise wird
-irgendjemand Ihnen helfen k&ouml;nnen.</P>
-<P class=normaltext>M&ouml;glicherweise f&uuml;hren Ihre verschiedenen L&ouml;sungsversuche zu
-keinem Ergebnis und Sie benutzen eine Firewall, so kann es sein, dass diese
-notwendige Funktionen oder eine ben&ouml;tigte Kommunikation verhindert. Zur
-Sicherheit empfiehlt es sich eine erneute Konfiguration durchzuf&uuml;hren. Sehr
-selten haben Firewalls Probleme mit Moodle, aber gelegentlich sind sie
-verantwortlich f&uuml;r eine reduzierte Funktionalit&auml;t aufgrund einer
-Fehlkonfiguration derer Einstellungen.
-<P class=normaltext>Benutzen Sie diese Liste, um zu den gew&uuml;nschten Antworten zu
-springen:</P>
-<P class=questionlink><A
-href="http://moodle.org/file.php/18/moddata/forum/166/17102/faq.html#filenotfound">Immer
-wenn ich versuche auf eine hochgeladene Datei zuzugreifen oder anzeigen zu
-lassen, erhalte ich eine Fehlermeldung "Datei nicht gefunden".</A></P>
-<P class=questionlink><A
-href="http://moodle.org/file.php/18/moddata/forum/166/17102/faq.html#php">Ist
-PHP auf meinem System installiert und welche Version habe ich?</A></P>
-<P class=questionlink><A
-href="http://moodle.org/file.php/18/moddata/forum/166/17102/faq.html#blankpages">Warum
-sind meine ganzen Seiten leer?</A></P>
-<P class=questionlink><A
-href="http://moodle.org/file.php/18/moddata/forum/166/17102/faq.html#errorgetstring">Meine
-Seite zeigt 'fatal error' an wie z. B.: call to undefined function:
-get_string()</A></P>
-<P class=questionlink><A
-href="http://moodle.org/file.php/18/moddata/forum/166/17102/faq.html#headerssent">Warum
-erhalte ich dauernd Fehlermeldungen &uuml;ber "headers already sent"?</A></P>
-<P class=questionlink><A
-href="http://moodle.org/file.php/18/moddata/forum/166/17102/faq.html#failedopen">Ich
-erhalte st&auml;ndig den Fehler: Failed opening required
-'/web/moodle/lib/setup.php'</A></P>
-<P class=questionlink><A
-href="http://moodle.org/file.php/18/moddata/forum/166/17102/faq.html#quotes">Jeder
-Versuch einen Text, ein Apostroph (') oder ein Anf&uuml;hrungszeichen (") hinzu zu
-f&uuml;gen, endet mit einer Fehlermeldung oder er wird mit einem Slash
-gezeigt.</A></P>
-<P class=questionlink><A
-href="http://moodle.org/file.php/18/moddata/forum/166/17102/faq.html#sessiontmp">Ich
-erhalte dauernd Fehlermeldungen &uuml;ber session_start.</A></P>
-<P class=questionlink><A
-href="http://moodle.org/file.php/18/moddata/forum/166/17102/faq.html#fixdirroot">Wenn
-ich auf die Adminseite gehen m&ouml;chte, bekomme ich eine Nachricht, dirroot leer zu
-machen!</A></P>
-<P class=questionlink><A
-href="http://moodle.org/file.php/18/moddata/forum/166/17102/faq.html#loginsetting">Ich
-melde mich an, aber die Anmeldeseite &auml;ndert sich nicht. Ich bin angemldet und
-kann frei navigieren. </A></P>
-<P class=questionlink><A
-href="http://moodle.org/file.php/18/moddata/forum/166/17102/faq.html#resource1">Wenn
-ich versuche eine Literatur oder Quelle ein zu f&uuml;gen, erhalte ich
-Fehlermeldungen.</A></P>
-<P class=questionlink><A
-href="http://moodle.org/file.php/18/moddata/forum/166/17102/faq.html#noadmin">W&auml;hrend
-dem anf&auml;nglichen Setup wurde ich nicht aufgefordert einen Adminaccount ein zu
-richten!</A></P>
-<P class=questionlink><A
-href="http://moodle.org/file.php/18/moddata/forum/166/17102/faq.html#nologin">Ich
-kann mich nicht anmelden – ich bleibe einfach auf der Anmeldeseite
-stecken.</A></P>
-<P class=questionlink><A
-href="http://moodle.org/file.php/18/moddata/forum/166/17102/faq.html#backup">Wie
-kann ich meine Moodleseite sichern? </A></P>
-<P class=questionlink><A
-href="http://moodle.org/file.php/18/moddata/forum/166/17102/faq.html#locale">Warum
-zeigt meine Moodleseite die Zeit und das Datum nicht richtig an?</A></P>
-<P class=questionlink><A
-href="http://moodle.org/file.php/18/moddata/forum/166/17102/faq.html#cron">Von
-den Foren werden keine Kopien per email versendet.</A></P>
-<P class=questionlink>&nbsp;</P>
-<H3><A name=filenotfound></A>Immer wenn ich versuche auf eine hochgeladene Datei
-zu zu greifen oder anzeigen zu lassen, erhalte ich eine Fehlermeldung "Datei
-nicht gefunden".</H3>
-<P class=answer>Bsp.: Not Found: The requested URL /moodle/file.php/2/myfile.jpg
-was not found on this server. </P>
-<P class=answer>Die Konfiguration Ihres Webservers muss den Teil nach dem
-Skriptnamen einer URL erlauben, um direkt zu dem Skript &uuml;bergeben zu werden.
-&Uuml;blicherweise ist dies in der Apache 1 Version bereits aktiviert, aber in der
-Apache 2 Version standardm&auml;&szlig;ig inaktiv. Um dies zu aktivieren, f&uuml;gen Sie diese
-Zeile zu httpd.conf oder zu .htaccess in Ihrem lokalen Verzeichnis ein (mehr
-Infos finden sie in der <A
-href="http://moodle.org/file.php/18/moddata/forum/166/17102/?file=install.html#webserver">Installationsanleitung</A>
-): </P>
-<P class=answercode><B>AcceptPathInfo</B> on</P>
-<P class=answer>Achtung, funktioniert ausschlie&szlig;lich f&uuml;r die Apache Version
-2.x.</P>
-<P class=answer>Falls Sie Apache 2 nicht benutzen und trotzdem ungewollt dieses
-Problem haben, k&ouml;nnen Sie Moodle so ver&auml;ndern, dass es eine alternative Methode
-benutzt. Nachteil dessen sind, leichte Verluste in der Ausf&uuml;hrung f&uuml;r Ihre
-Benutzer und es k&ouml;nnen keine Linkverbindungen mit HTML-Inhalten benutzt werden.
-</P>
-<P class=answer>Um diese Methode zu benutzen, m&uuml;ssen Sie als Admin angemeldet
-sein. Gehen Sie zur Seite "Konfigurationsvariablen" und &auml;ndern Sie die
-Einstellung f&uuml;r die "<B>slasharguments</B>".Nun sollten Sie in der Lage sein auf
-Ihre hochgeladenen Dateien zugreifen zu k&ouml;nnen.</P>
-<P class=answer>&nbsp;</P>
-<H3><A name=php></A>Ist PHP auf meinem System installiert und welche Version
-habe ich?</H3>
-<P class=answer>Erstellen Sie eine neue Webseite mit dem Namen info.php mit dem
-folgenden Textinhalt und &ouml;ffnen es mit Ihrem Browser:</P>
-<P class=answercode>&lt;?PHP phpinfo() ?&gt;</P>
-<P class=answer>Wenn nichts passiert, dann haben Sie kein PHP installiert. In
-der Installationsanleitung finden Sie einige Informationen dar&uuml;ber, wo Sie PHP
-f&uuml;r Ihr System herunterladen k&ouml;nnen. </P>
-<P class=answer>&nbsp;</P>
-<H3><A name=blankpages></A>Warum sind meine ganzen Seiten leer? </H3>
-<P class=answer>Pr&uuml;fen Sie die dirroot Variablen in der config.php. Sie m&uuml;ssen vollst&auml;ndige absolute Pfade eintragen, z.B.:</P>
-<P class=answercode>$CFG-&gt;dirroot =
-"d:\inetpub\sites\www.yoursite.com\web\moodle";</P>
-<P></P>
-<P class=answer>F&uuml;r Nutzer von Redhat Linux sehen Sie bitte hier nach: <A
-href="http://moodle.org/doc/?file=installamp.html">Redhat Linux</A></P>
-<P></P>
-<H3><A name=errorgetstring></A>Meine
-Seite zeigt 'fatal error' an wie z. B.: call to undefined function:
-get_string()</H3>
-<P class=answer>Wenn Sie folgende Fehler sehen:</P>
-<P class=answercode>Parse error: parse error, unexpected T_VARIABLE in
-c:\program files\easyphp\www\moodle\config.php on line 94 <br />Fatal error: Call
-to undefined function: get_string() in c:\program
-files\easyphp\www\moodle\mod\resource\lib.php on line 11</P>
-<P class=answer>dann haben Sie vermutlich ein Semicolon am Ende oder ein abschlie&szlig;endes " in config.php (in Zeile 94) vergessen.</P>
-<P class=answer>Andere Gr&uuml;nde k&ouml;nnen darin liegen, wenn Sie die Datei config.php in Word bearbeitet haben und sie als HTML-Seite gespeichert haben, statt als reine Textdatei. Dadurch werden zus&auml;tzliche Informationen in der Datei gespeichert, die die Ausf&uuml;hrung st&ouml;ren.</P>
-<P>&nbsp;</P>
-<H3><A name=headerssent></A>Warum
-erhalte ich dauernd Fehlermeldungen &uuml;ber "headers already sent"?</H3>
-<P class=answer>Wenn Sie folgende Fehler sehen:</P>
-<P class=answercode>Warning: Cannot add header information - headers already
-sent by (output started at /webs/moodle/config.php:87) in
-/webs/moodle/lib/moodlelib.php on line 1322 </P>
-<P class=answercode>Warning: Cannot add header information - headers already
-sent by (output started at /webs/moodle/config.php:87) in
-/webs/moodle/lib/moodlelib.php on line 1323 </P>
-<P class=answercode>Warning: Cannot add header information - headers already
-sent by (output started at /webs/moodle/config.php:87) in
-/webs/moodle/login/index.php on line 54 </P>
-<P class=answer>Sie haben leere Zeilen oder Leerzeichen nach dem abschlie&szlig;enden ?&gt; in Ihrer
-config.php Datei. Einige Texteditoren wie z.B. Notepad (Windows) f&uuml;gen diese ein. Sie m&uuml;ssen nun mit einem andernen Editor diese Zeichen vollst&auml;ndig l&ouml;schen. </P>
-<P class=answer>&nbsp;</P>
-<H3><A name=failedopen></A>Ich erhalte st&auml;ndig den Fehler: Failed opening required
-'/web/moodle/lib/setup.php'</H3>
-<P class=answer>In Ihrer config.php mu&szlig; die Angabe f&uuml;r dirroot
-ein <STRONG>vollst&auml;ndiger Pfad auf dem Server sein.</STRONG>.</P>
-<P class=answer>Manchmal werden nur die Pfade vom Home-Verzeichnis oder relative Pfade eingetragen.</P>
-<P class=answer>&nbsp;</P>
-<H3><A id=quotes name=quotes></A>Jeder
-Versuch einen Text, ein Apostroph (') oder ein Anf&uuml;hrungszeichen (") hinzu zu
-f&uuml;gen, endet mit einer Fehlermeldung oder er wird mit einem Slash
-gezeigt.</H3>
-<P class=answer>Probleme mit ' liegen in falschen "magic
-quotes" Einstellungen. Moodle ben&ouml;tigt die folgenden Einstellungen (dies sind normalerweise die Standardeinstellungen):</P>
-<P class=answercode>magic_quotes_gpc = On<br />magic_quotes_runtime = Off</P>
-<P class=answer>Beachten Sie auch den folgenden Hinweis zur <A
-href="http://moodle.org/file.php/18/moddata/forum/166/17102/?file=install.html#webserver">Webserver
-Konfiguration</A> in den Installationsdokumenten.</P>
-<P class=answer>&nbsp;</P>
-<H3><A name=sessiontmp></A>Ich
-erhalte dauernd Fehlermeldungen &uuml;ber session_start.</H3>
-<P class=answer>Wenn Sie folgende Fehler sehen:</P>
-<P class=answercode>Warning: session_start() [function.session-start]:
-open(/tmp\sess_d40f380d37d431fc1516e9a895ad9ce0, O_RDWR) failed: No such file or
-directory (2) in G:\web\moodle\lib\setup.php on line 123</P>
-<P class=answercode>Warning: session_start() [function.session-start]:
-open(/tmp\sess_d40f380d37d431fc1516e9a895ad9ce0, O_RDWR) failed: No such file or
-directory (2) in G:\web\moodle\lib\setup.php on line 123</P>
-<P class=answercode>Warning: session_start() [function.session-start]: Cannot
-send session cache limiter - headers already sent (outp