Removing untranslated files...
This commit is contained in:
koenr
@@ -1,13 +0,0 @@
|
||||
<p align="center"><b>Cookies</b></p>
|
||||
|
||||
<p>Two cookies are used by this site.</p>
|
||||
|
||||
<p>The essential one is the session cookie, usually called <b>MoodleSession</b>. You must allow this cookie
|
||||
into your browser to provide continuity and maintain your login from page to page. When you log out or
|
||||
close the browser this cookie is destroyed (in your browser and on the server).</p>
|
||||
|
||||
<p>The other cookie is purely for convenience, usually called something like <b>MOODLEID</b>. It just remembers
|
||||
your username within the browser. This means when you return to this site the username field on the
|
||||
login page will be already filled out for you. It is safe to refuse this cookie - you will just have
|
||||
to retype your username every time you log in.</p>
|
||||
|
||||
@@ -1,11 +0,0 @@
|
||||
<p align="center"><b>Course availability</b></p>
|
||||
|
||||
<P>This option allows you to "hide" your course
|
||||
completely.</p>
|
||||
|
||||
<p>It will not appear on any course listings, except to
|
||||
teachers of the course and administrators.</p>
|
||||
|
||||
<p>Even if students try to access the course URL directly,
|
||||
they will not be allowed to enter.</p>
|
||||
|
||||
@@ -1,11 +0,0 @@
|
||||
<P ALIGN=CENTER><B>Course Categories</B></P>
|
||||
|
||||
<P>Your Moodle administrator may have set up several
|
||||
course categories.
|
||||
|
||||
<P>For example, "Science", "Humanities", "Public Health" etc
|
||||
|
||||
<P>Choose the one most applicable for your course. This
|
||||
choice will affect where your course is displayed on the
|
||||
course listing and may make it easier for students to
|
||||
find your course.
|
||||
@@ -1,24 +0,0 @@
|
||||
<P ALIGN=CENTER><B>Moodle course formats</B></P>
|
||||
|
||||
<P><B>Weekly format</B></P>
|
||||
<UL>
|
||||
The course is organised week by week, with a clear start date and a finish date.
|
||||
Each week consists of activities. Some of them, like journals, may have
|
||||
"open windows" of, say, two weeks after which they become unavailable.
|
||||
</UL>
|
||||
|
||||
<P><B>Topics format</B></P>
|
||||
<UL>
|
||||
Very similar to the weekly format, except that each "week" is called a topic.
|
||||
A "topic" is not restricted to any time limit. You don't need to specify any
|
||||
dates.
|
||||
</UL>
|
||||
|
||||
<P><B>Social format</B></P>
|
||||
<UL>
|
||||
This format is oriented around one main forum, the Social forum, which appears
|
||||
listed on the main page. It is useful for situations that are more freeform.
|
||||
They may not even be courses. For example, it could be used as a departmental
|
||||
notice board.
|
||||
</UL>
|
||||
|
||||
@@ -1,4 +0,0 @@
|
||||
<P ALIGN=CENTER><B>Course Full name</B></P>
|
||||
|
||||
<P>The full name of the course is displayed at the top of the screen and in the course listings.</P>
|
||||
|
||||
@@ -1,14 +0,0 @@
|
||||
<p align="center"><b>Grades</b></p>
|
||||
|
||||
<P>Many of the activities allow grades to be set.</p>
|
||||
|
||||
<p>By default, the results of all grades within the
|
||||
course can be seen in the Grades page, available
|
||||
from the main course page.</p>
|
||||
|
||||
<p>If a teacher is not interested in using grades in a
|
||||
course, or just wants to hide grades from students,
|
||||
then they can disable the display of grades in the
|
||||
Course Settings. This does not prevent individual
|
||||
activities from using or setting grades, it just
|
||||
disables the results being displayed to students.</p>
|
||||
@@ -1,13 +0,0 @@
|
||||
<p align="center"><b>Course hidden sections</b></p>
|
||||
|
||||
<P>This option allows you to decide how the hidden sections in your course
|
||||
are displayed to students.</p>
|
||||
|
||||
<p>By default, a small area is shown (in collapsed form, usually gray) to
|
||||
indicate where the hidden section is, though they still can not actually see
|
||||
the hidden activities and texts. This is particularly useful
|
||||
in the Weekly format, so that non-class weeks are clear.</p>
|
||||
|
||||
<p>If you choose, these can be completely hidden, so that students
|
||||
don't even know sections of the course are hidden</p>
|
||||
|
||||
@@ -1,7 +0,0 @@
|
||||
<P ALIGN=CENTER><B>Course ID Number</B></P>
|
||||
|
||||
<P>The ID number of a course is only used when matching this course against
|
||||
external systems - it is never displayed within Moodle. If you have an
|
||||
official code name for this course then use it here ... otherwise you can
|
||||
leave it blank.</p>
|
||||
|
||||
@@ -1,15 +0,0 @@
|
||||
<P ALIGN=CENTER><B>Course News Items</B></P>
|
||||
|
||||
<P>A special forum called "News" appears in the
|
||||
"weekly" and "topics" course formats. It's
|
||||
a good place to post notices for all students
|
||||
to see. (By default, all students are subscribed
|
||||
to this forum, and will receive your notices by
|
||||
email.)
|
||||
|
||||
<P>This setting determines how many recent items
|
||||
appear on your course home page, in a news box
|
||||
down the right-hand side.
|
||||
|
||||
<P>If you set it to "0 news items" then the news
|
||||
box won't even appear.
|
||||
@@ -1,14 +0,0 @@
|
||||
<P ALIGN=CENTER><B>Course Number of Weeks/Topics</B></P>
|
||||
|
||||
<P>This setting is only used by the 'weekly' and 'topics'
|
||||
course formats.
|
||||
|
||||
<P>In the 'weekly' format, it specifies the number of weeks
|
||||
that the course will run for, starting from the
|
||||
course starting date.
|
||||
|
||||
<P>In the 'topics' format, it specifies the number of topics
|
||||
in the course.
|
||||
|
||||
<P>Both of these translate to the number of "boxes" down the
|
||||
middle of the course page.
|
||||
@@ -1,16 +0,0 @@
|
||||
<P ALIGN=CENTER><B>Recent Activity</B></P>
|
||||
|
||||
<P>Moodle can display "recent activity" on the course home page.
|
||||
|
||||
<P>This shows the everything that has happened in the course since
|
||||
the last time the viewer logged in to the course, including
|
||||
new posts, new users, submitted journals etc.
|
||||
|
||||
<P>It is highly recommended you leave this feature enabled in
|
||||
your courses, as it helps give a sense of activity in the course.
|
||||
Knowing what everyone else is doing also helps to promote a
|
||||
collaborative atmosphere in the class.
|
||||
|
||||
<P>You might want to disable this feature for extremely large or
|
||||
heavily used courses, as it may slow down the display of
|
||||
the course page.
|
||||
@@ -1,21 +0,0 @@
|
||||
<p align="center"><b>Activity Reports</b></p>
|
||||
|
||||
<P>Activity reports are available for each participant
|
||||
that show their activity in the current course. As
|
||||
well as listings of their contributions, these
|
||||
reports include detailed access logs.</p>
|
||||
|
||||
<p>Teachers always have access to these reports, using
|
||||
the button visible on each persons's profile page.</p>
|
||||
|
||||
<p>Student access to their own reports is controlled by
|
||||
the teacher via a course setting. For some courses these
|
||||
reports can be a useful tool for a student to reflect
|
||||
on their involvement and appearance within the online
|
||||
environment, but for some courses this may not be
|
||||
necessary.</p>
|
||||
|
||||
<p>Another reason for turning it off is that the report
|
||||
can place a bit of load on the server while being
|
||||
generated. For large or long classes it may be more
|
||||
efficient to keep it off.<p>
|
||||
@@ -1,7 +0,0 @@
|
||||
<P ALIGN=CENTER><B>Course short name</B></P>
|
||||
|
||||
<P>Many institutions have a shorthand way of referring to a course, such as
|
||||
BP102 or COMMS. Even you don't already have such a name for your course,
|
||||
make one up here. It will be used in several places where the long name
|
||||
isn't appropriate (such us in the subject line of email).</P>
|
||||
|
||||
@@ -1,19 +0,0 @@
|
||||
<P ALIGN=CENTER><B>Course Start Date</B></P>
|
||||
|
||||
<P>This is where you specify the starting time of the
|
||||
course (in your own timezone).
|
||||
|
||||
<P>If you are using a 'weekly' course format, this will
|
||||
affect the display of the weeks. The first week will
|
||||
start on the date you set here.
|
||||
|
||||
<P>This setting will not affect courses using the
|
||||
'social' or 'topics' formats.
|
||||
|
||||
<P>However, one place this setting will be affect is
|
||||
the display of logs, which use this date as the earliest
|
||||
possible date you can display.
|
||||
|
||||
<P>In general, if your course does have a real starting date
|
||||
then it makes sense to set this date to that, no matter
|
||||
what course formats you are using.
|
||||
@@ -1,8 +0,0 @@
|
||||
<P ALIGN=CENTER><B>Course upload size</B></P>
|
||||
|
||||
<P>This setting defines the largest size of file that can be
|
||||
uploaded by students in this course, limited by the site
|
||||
wide setting created by the administrator.
|
||||
|
||||
<P>It is possible to further restrict this size through
|
||||
settings within each activity module.
|
||||
@@ -1,26 +0,0 @@
|
||||
<p align="center"><b>Directory paths</b></p>
|
||||
|
||||
<p>The full syntax of a directory path depends on your operating system:</p>
|
||||
|
||||
<blockquote>
|
||||
|
||||
<p>In <b>Windows Systems</b> use something like:
|
||||
<ul>
|
||||
<li>c:\program files\data\moodle
|
||||
<li>c:\documents and settings\moodle\temp\saved
|
||||
</ul>
|
||||
</p>
|
||||
|
||||
<p>In <b>Unix Systems</b> use something like:
|
||||
<ul>
|
||||
<li>/usr/data/moodle
|
||||
<li>/home/moodle/tmp/saved
|
||||
</ul>
|
||||
</p>
|
||||
|
||||
</blockquote>
|
||||
|
||||
<p>Note that it's usually a good idea to make sure the directory already exists.
|
||||
Sometimes Moodle can create the directory when required but this is not always possible.</p>
|
||||
|
||||
<p>Finally, make sure the case is correct (upper vs lower) and never include a trailing slash.</p>
|
||||
@@ -1,120 +0,0 @@
|
||||
<P ALIGN=CENTER><B>Using Smilies (emoticons)</B></P>
|
||||
|
||||
<table border="1" align="center">
|
||||
<tr valign="top">
|
||||
<td>
|
||||
<table border="0" align="center" cellpadding="5">
|
||||
<tr>
|
||||
<td><a href="javascript:inserttext(':-)')"><img border="0" hspace="10" src="pix/s/smiley.gif" width="15" height="15"></a></td>
|
||||
<td>smile</td>
|
||||
<td><font face="courier">:-)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><a href="javascript:inserttext(':-D')"><img alt border="0" hspace="10" src="pix/s/biggrin.gif" width="15" height="15"></a></td>
|
||||
<td>big grin</td>
|
||||
<td><font face="courier">:-D</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><a href="javascript:inserttext(';-)')"><img alt border="0" hspace="10" src="pix/s/wink.gif" width="15" height="15"></a></td>
|
||||
<td>wink</td>
|
||||
<td><font face="courier">;-)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><a href="javascript:inserttext(':-/')"><img alt border="0" hspace="10" src="pix/s/mixed.gif" width="15" height="15"></a></td>
|
||||
<td>mixed</td>
|
||||
<td><font face="courier">:-/</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><a href="javascript:inserttext('V-.')"><img alt border="0" hspace="10" src="pix/s/thoughtful.gif" width="15" height="15"></a></td>
|
||||
<td>thoughtful</td>
|
||||
<td><font face="courier">V-.</font></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><a href="javascript:inserttext(':-P')"><img alt border="0" hspace="10" src="pix/s/tongueout.gif" width="15" height="15"></a></td>
|
||||
<td>tongue out</td>
|
||||
<td><font face="courier">:-P</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><a href="javascript:inserttext('B-)')"><img alt border="0" hspace="10" src="pix/s/cool.gif" width="15" height="15"></a></td>
|
||||
<td>cool</td>
|
||||
<td><font face="courier">B-)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><a href="javascript:inserttext('^-)')"><img alt border="0" hspace="10" src="pix/s/approve.gif" width="15" height="15"></a></td>
|
||||
<td>approve</td>
|
||||
<td><font face="courier">^-)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><a href="javascript:inserttext('8-)')"><img alt border="0" hspace="10" src="pix/s/wideeyes.gif" width="15" height="15"></a></td>
|
||||
<td>wide eyes</td>
|
||||
<td><font face="courier">8-)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><a href="javascript:inserttext('8-o')"><img alt border="0" hspace="10" src="pix/s/surprise.gif" width="15" height="15"></a></td>
|
||||
<td>surprise</td>
|
||||
<td><font face="courier">8-o</td>
|
||||
</tr>
|
||||
</table>
|
||||
</td>
|
||||
<td>
|
||||
<table border="0" align="center" cellpadding="5">
|
||||
<tr>
|
||||
<td><a href="javascript:inserttext(':-(')"><img alt border="0" hspace="10" src="pix/s/sad.gif" width="15" height="15"></a></td>
|
||||
<td>sad</td>
|
||||
<td><font face="courier">:-(</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><a href="javascript:inserttext('8-.')"><img alt border="0" hspace="10" src="pix/s/shy.gif" width="15" height="15"></a></td>
|
||||
<td>shy</td>
|
||||
<td><font face="courier">8-.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><a href="javascript:inserttext(':-I')"><img alt border="0" hspace="10" src="pix/s/blush.gif" width="15" height="15"></a></td>
|
||||
<td>blush</td>
|
||||
<td><font face="courier">:-I</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><a href="javascript:inserttext(':-X')"><img alt border="0" hspace="10" src="pix/s/kiss.gif" width="15" height="15"></a></td>
|
||||
<td>kisses</td>
|
||||
<td><font face="courier">:-X</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><a href="javascript:inserttext(':o)')"><img alt border="0" hspace="10" src="pix/s/clown.gif" width="15" height="15"></a></td>
|
||||
<td>clown</td>
|
||||
<td><font face="courier">:o)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><a href="javascript:inserttext('P-|')"><img alt border="0" hspace="10" src="pix/s/blackeye.gif" width="15" height="15"></a></td>
|
||||
<td>black eye</td>
|
||||
<td><font face="courier">P-|</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><a href="javascript:inserttext('8-[')"><img alt border="0" hspace="10" src="pix/s/angry.gif" width="15" height="15"></a></td>
|
||||
<td>angry</td>
|
||||
<td><font face="courier">8-[</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><a href="javascript:inserttext('xx-P')"><img alt border="0" hspace="10" src="pix/s/dead.gif" width="15" height="15"></a></td>
|
||||
<td>dead</td>
|
||||
<td><font face="courier">xx-P</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><a href="javascript:inserttext('|-.')"><img alt border="0" hspace="10" src="pix/s/sleepy.gif" width="15" height="15"></a></td>
|
||||
<td>sleepy</td>
|
||||
<td><font face="courier">|-.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><a href="javascript:inserttext('}-]')"><img alt border="0" hspace="10" src="pix/s/evil.gif" width="15" height="15"></a></td>
|
||||
<td>evil</td>
|
||||
<td><font face="courier">}-]</td>
|
||||
</tr>
|
||||
</table>
|
||||
</table>
|
||||
|
||||
<P>When writing online, it can sometimes difficult to express emotion with plain text.
|
||||
These little icons can help.
|
||||
|
||||
<P>To insert these icons in your text: just click the icon above, or type the associated text code directly in your text.</P>
|
||||
|
||||
<P>Note that the codes themselves are like little pictures - just turn your head to the left when looking at them</P>
|
||||
|
||||
@@ -1,23 +0,0 @@
|
||||
<P ALIGN=CENTER><B>Course Enrolment Key</B></P>
|
||||
|
||||
<P>A course enrolment key is what keeps unwanted people
|
||||
out of your course.
|
||||
|
||||
<P>If you leave this blank, then anyone who has created
|
||||
a Moodle username on this site will be able to enrol
|
||||
in your course simply by going in to it.
|
||||
|
||||
<P>If you put something here, then students who are trying
|
||||
to get in for the FIRST TIME ONLY will be asked to supply
|
||||
this word or phrase.
|
||||
|
||||
<P>The idea is that you will supply the key to authorised
|
||||
people using another means like private email, snail mail,
|
||||
on the phone or even verbally in a face to face class.
|
||||
|
||||
<P>If this password "gets out" and you have unwanted people
|
||||
enrolling, you can unenrol them (see their user profile page)
|
||||
and change this key. Any legitimate students who have already
|
||||
enrolled will not be affected, but the unwanted people won't be
|
||||
able to get back in.
|
||||
|
||||
@@ -1,13 +0,0 @@
|
||||
<p align="center"><b>Enrolment period</b></b></p>
|
||||
|
||||
<p>This setting specifies the number of days a student can be
|
||||
enrolled in this course (starting from the moment they enroll).</p>
|
||||
|
||||
<p>If this is set, then students are automatically unenrolled
|
||||
after the specified time has elapsed. This is most useful
|
||||
for rolling courses without a specific start or end time.</p>
|
||||
|
||||
<p>If you don't set this then the student will remain
|
||||
in this course until they are manually unenrolled or the
|
||||
clean-up function to remove defunct students takes effect. </p>
|
||||
|
||||
@@ -1,24 +0,0 @@
|
||||
<p align="center"><b>Group Mode</b></p>
|
||||
|
||||
<p>The group mode can be one of three levels:
|
||||
<ul>
|
||||
<li>No groups - there are no sub groups, everyone is part of one big community</li>
|
||||
<li>Separate groups - each group can only see their own group, others are invisible</li>
|
||||
<li>Visible groups - each group works in their own group, but can also see other groups</li>
|
||||
</ul>
|
||||
</p>
|
||||
|
||||
<P>The group mode can be defined at two levels:</p>
|
||||
|
||||
<dl>
|
||||
<dt><b>1. Course level</b></dt>
|
||||
<dd>The group mode defined at the course level is the default mode
|
||||
for all activities defined within that course<br /><br /></dd>
|
||||
<dt><b>2. Activity level</b></dt>
|
||||
<dd>Each activity that supports groups can also define its own
|
||||
grouping mode. If the course is set to "<a href="help.php?module=moodle&file=groupmodeforce.html">force group mode</a>" then
|
||||
the setting for each activity is ignored.</dd>
|
||||
</dl>
|
||||
|
||||
<P>
|
||||
|
||||
@@ -1,10 +0,0 @@
|
||||
<p align="center"><b>Force Group Mode</b></p>
|
||||
|
||||
<P>If the group mode is "forced" at a course-level, then
|
||||
the course group mode is applied to every activity
|
||||
in that course. Individual group settings in each
|
||||
activity are then ignored. </p>
|
||||
|
||||
<p>This is useful when, for example, one wants to set up a
|
||||
course for a number of completely separate cohorts.</p>
|
||||
|
||||
@@ -1,21 +0,0 @@
|
||||
<P ALIGN=CENTER><B>Guest Access</B></P>
|
||||
|
||||
<P>You have the choice of allowing "guests" into your course.
|
||||
|
||||
<P>People can log in as guests using the "Login as a guest" button
|
||||
on the login screen.
|
||||
|
||||
<P>Guests ALWAYS have "read-only" access - meaning they can't leave
|
||||
any posts or otherwise mess up the course for real students.
|
||||
|
||||
<P>This can be handy when you want to let a colleague in to
|
||||
look around at your work, or to let students see a course before
|
||||
they have decided to enrol.
|
||||
|
||||
<P>Note that you have a choice between two types of guest access:
|
||||
with the enrolment key or without. If you choose to allow
|
||||
guests who have the key, then the guest will need to provide
|
||||
the current enrolment key EVERY TIME they log in (unlike
|
||||
students who only need to do it once). This lets you restrict
|
||||
your guests. If you choose to allow guests without a key, then
|
||||
anyone can get straight into your course.
|
||||
@@ -1,20 +0,0 @@
|
||||
<P ALIGN=CENTER><B>Help on writing html</B></P>
|
||||
|
||||
<P>When writing HTML in Moodle, you are free to use almost any HTML tags you like
|
||||
to produce the effect you want.</p>
|
||||
|
||||
<P>Note that scripting (eg Javascript or VB Script) is not allowed, and will be removed
|
||||
automatically.</P>
|
||||
|
||||
<P>Your code will normally be printed on the page within a table cell,
|
||||
so:
|
||||
|
||||
<UL>
|
||||
<LI>there is no need to use any <HEAD> or <BODY> tags
|
||||
<LI>be careful about unmatched </TABLE> tags that may mess up the display.
|
||||
</UL>
|
||||
|
||||
<p>Smilies (emoticons) will be converted into their graphical equivalent, and
|
||||
bare URLs will be converted into links.</p>
|
||||
|
||||
</p>
|
||||
@@ -1,53 +0,0 @@
|
||||
|
||||
<p><b>Index of Help files</b></p>
|
||||
|
||||
<p>General</p>
|
||||
<ul>
|
||||
<li><a href="help.php?file=cookies.html">Cookies</a>
|
||||
<li><a href="help.php?file=directorypaths.html">Directory paths</a>
|
||||
</ul>
|
||||
|
||||
<p>Administration</p>
|
||||
<ul>
|
||||
<li><a href="help.php?file=langedit.html">Language editing</a>
|
||||
<li><a href="help.php?file=uploadusers.html">Upload users</a>
|
||||
</ul>
|
||||
|
||||
<p>Setting up courses</p>
|
||||
<ul>
|
||||
<li><a href="help.php?file=mods.html">Activity Modules</a>
|
||||
<li><a href="help.php?file=coursereports.html">Activity Reports</a>
|
||||
<li><a href="help.php?file=courseavailability.html">Course availability</a>
|
||||
<li><a href="help.php?file=coursecategory.html">Course categories</a>
|
||||
<li><a href="help.php?file=courseformats.html">Course formats</a>
|
||||
<li><a href="help.php?file=coursefullname.html">Course fullname</a>
|
||||
<li><a href="help.php?file=courseidnumber.html">Course ID number</a>
|
||||
<li><a href="help.php?file=coursenewsitems.html">Course news items</a>
|
||||
<li><a href="help.php?file=coursenumsections.html">Course number of weeks/topics</a>
|
||||
<li><a href="help.php?file=courseshortname.html">Course short name</a>
|
||||
<li><a href="help.php?file=coursestartdate.html">Course start date</a>
|
||||
<li><a href="help.php?file=courseuploadsize.html">Course upload size</a>
|
||||
<li><a href="help.php?file=enrolmentkey.html">Enrollment keys</a>
|
||||
<li><a href="help.php?file=coursegrades.html">Grades</a>
|
||||
<li><a href="help.php?file=groupmode.html">Group mode</a>
|
||||
<li><a href="help.php?file=groupmodeforce.html">Group mode (forcing)</a>
|
||||
<li><a href="help.php?file=guestaccess.html">Guest access</a>
|
||||
<li><a href="help.php?file=courserecent.html">Recent Activity</a>
|
||||
<li><a href="help.php?file=scales.html">Scales</a>
|
||||
<li><a href="help.php?file=summaries.html">Section summaries</a>
|
||||
<li><a href="help.php?file=teachers.html">Teachers</a>
|
||||
<li><a href="help.php?file=picture.html">Uploading a picture</a>
|
||||
</ul>
|
||||
|
||||
<p>Reading and Writing</p>
|
||||
<ul>
|
||||
<li><a href="help.php?file=questions.html">Asking Questions</a>
|
||||
<li><a href="help.php?file=reading.html">Reading</a>
|
||||
<li><a href="help.php?file=writing.html">Writing</a>
|
||||
<li><a href="help.php?file=textformat.html">Formatting Text</a>
|
||||
<li><a href="help.php?file=html.html">Editing HTML format</a>
|
||||
<li><a href="help.php?file=text.html">Edting Text format</a>
|
||||
<li><a href="help.php?file=wiki.html">Editing Wiki format</a>
|
||||
<li><a href="help.php?file=richtext.html">Using the Richtext HTML editor</a>
|
||||
<li><a href="help.php?file=emoticons.html">Using Smilies (emoticons)</a>
|
||||
</ul>
|
||||
@@ -1,12 +0,0 @@
|
||||
<P ALIGN=CENTER><B>Language Editing</B></P>
|
||||
|
||||
<P>To edit languages on this page the files need to be writable
|
||||
by the web server process.
|
||||
|
||||
<P>Within some of the strings you will notice <B>$a</B> and <B>$a->something</B>.
|
||||
|
||||
<P>These represent variables that will be replaced by names or other words from
|
||||
within Moodle.
|
||||
|
||||
<P>When there is only one variable, the $a form is used. When there are two or
|
||||
more variables, then each one has a name.
|
||||
@@ -1,926 +0,0 @@
|
||||
<p align="center"><b>Using Markdown format to write web pages</b></p>
|
||||
|
||||
<p>(This text is a copy of <a target="_blank" href="http://daringfireball.net/projects/markdown/syntax">the original Markdown syntax page</a>)</p>
|
||||
|
||||
<hr />
|
||||
<div id="Main">
|
||||
|
||||
<div class="article">
|
||||
|
||||
<ul>
|
||||
<li><a href="#overview">Overview</a>
|
||||
<ul>
|
||||
<li><a href="#philosophy">Philosophy</a></li>
|
||||
<li><a href="#html">Inline HTML</a></li>
|
||||
<li><a href="#autoescape">Automatic Escaping for Special Characters</a></li>
|
||||
</ul></li>
|
||||
<li><a href="#block">Block Elements</a>
|
||||
<ul>
|
||||
<li><a href="#p">Paragraphs and Line Breaks</a></li>
|
||||
<li><a href="#header">Headers</a></li>
|
||||
<li><a href="#blockquote">Blockquotes</a></li>
|
||||
<li><a href="#list">Lists</a></li>
|
||||
<li><a href="#precode">Code Blocks</a></li>
|
||||
<li><a href="#hr">Horizontal Rules</a></li>
|
||||
</ul></li>
|
||||
<li><a href="#span">Span Elements</a>
|
||||
<ul>
|
||||
<li><a href="#link">Links</a></li>
|
||||
<li><a href="#em">Emphasis</a></li>
|
||||
<li><a href="#code">Code</a></li>
|
||||
<li><a href="#img">Images</a></li>
|
||||
</ul></li>
|
||||
<li><a href="#misc">Miscellaneous</a>
|
||||
<ul>
|
||||
<li><a href="#backslash">Backslash Escapes</a></li>
|
||||
<li><a href="#autolink">Automatic Links</a></li>
|
||||
</ul></li>
|
||||
</ul>
|
||||
|
||||
<hr />
|
||||
|
||||
<h2 id="overview">Overview</h2>
|
||||
|
||||
<h3 id="philosophy">Philosophy</h3>
|
||||
|
||||
<p>Markdown is intended to be as easy-to-read and easy-to-write as is feasible.</p>
|
||||
|
||||
<p>Readability, however, is emphasized above all else. A Markdown-formatted
|
||||
document should be publishable as-is, as plain text, without looking
|
||||
like it’s been marked up with tags or formatting instructions. While
|
||||
Markdown’s syntax has been influenced by several existing text-to-HTML
|
||||
filters — including <a href="http://docutils.sourceforge.net/mirror/setext.html">Setext</a>, <a href="http://www.aaronsw.com/2002/atx/">atx</a>, <a href="http://textism.com/tools/textile/">Textile</a>, <a href="http://docutils.sourceforge.net/rst.html">reStructuredText</a>,
|
||||
<a href="http://www.triptico.com/software/grutatxt.html">Grutatext</a>, and <a href="http://ettext.taint.org/doc/">EtText</a> — the single biggest source of
|
||||
inspiration for Markdown’s syntax is the format of plain text email.</p>
|
||||
|
||||
<p>To this end, Markdown’s syntax is comprised entirely of punctuation
|
||||
characters, which punctuation characters have been carefully chosen so
|
||||
as to look like what they mean. E.g., asterisks around a word actually
|
||||
look like *emphasis*. Markdown lists look like, well, lists. Even
|
||||
blockquotes look like quoted passages of text, assuming you’ve ever
|
||||
used email.</p>
|
||||
|
||||
<h3 id="html">Inline HTML</h3>
|
||||
|
||||
<p>Markdown’s syntax is intended for one purpose: to be used as a
|
||||
format for <em>writing</em> for the web.</p>
|
||||
|
||||
<p>Markdown is not a replacement for HTML, or even close to it. Its
|
||||
syntax is very small, corresponding only to a very small subset of
|
||||
HTML tags. The idea is <em>not</em> to create a syntax that makes it easier
|
||||
to insert HTML tags. In my opinion, HTML tags are already easy to
|
||||
insert. The idea for Markdown is to make it easy to read, write, and
|
||||
edit prose. HTML is a <em>publishing</em> format; Markdown is a <em>writing</em>
|
||||
format. Thus, Markdown’s formatting syntax only addresses issues that
|
||||
can be conveyed in plain text.</p>
|
||||
|
||||
<p>For any markup that is not covered by Markdown’s syntax, you simply
|
||||
use HTML itself. There’s no need to preface it or delimit it to
|
||||
indicate that you’re switching from Markdown to HTML; you just use
|
||||
the tags.</p>
|
||||
|
||||
<p>The only restrictions are that block-level HTML elements — e.g. <code><div></code>,
|
||||
<code><table></code>, <code><pre></code>, <code><p></code>, etc. — must be separated from surrounding
|
||||
content by blank lines, and the start and end tags of the block should
|
||||
not be indented with tabs or spaces. Markdown is smart enough not
|
||||
to add extra (unwanted) <code><p></code> tags around HTML block-level tags.</p>
|
||||
|
||||
<p>For example, to add an HTML table to a Markdown article:</p>
|
||||
|
||||
<pre><code>This is a regular paragraph.
|
||||
|
||||
<table>
|
||||
<tr>
|
||||
<td>Foo</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
This is another regular paragraph.
|
||||
</code></pre>
|
||||
|
||||
<p>Note that Markdown formatting syntax is not processed within block-level
|
||||
HTML tags. E.g., you can’t use Markdown-style <code>*emphasis*</code> inside an
|
||||
HTML block.</p>
|
||||
|
||||
<p>Span-level HTML tags — e.g. <code><span></code>, <code><cite></code>, or <code><del></code> — can be
|
||||
used anywhere in a Markdown paragraph, list item, or header. If you
|
||||
want, you can even use HTML tags instead of Markdown formatting; e.g. if
|
||||
you’d prefer to use HTML <code><a></code> or <code><img></code> tags instead of Markdown’s
|
||||
link or image syntax, go right ahead.</p>
|
||||
|
||||
<p>Unlike block-level HTML tags, Markdown syntax <em>is</em> processed within
|
||||
span-level tags.</p>
|
||||
|
||||
<h3 id="autoescape">Automatic Escaping for Special Characters</h3>
|
||||
|
||||
<p>In HTML, there are two characters that demand special treatment: <code><</code>
|
||||
and <code>&</code>. Left angle brackets are used to start tags; ampersands are
|
||||
used to denote HTML entities. If you want to use them as literal
|
||||
characters, you must escape them as entities, e.g. <code>&lt;</code>, and
|
||||
<code>&amp;</code>.</p>
|
||||
|
||||
<p>Ampersands in particular are bedeviling for web writers. If you want to
|
||||
write about ‘AT&T’, you need to write ‘<code>AT&amp;T</code>’. You even need to
|
||||
escape ampersands within URLs. Thus, if you want to link to:</p>
|
||||
|
||||
<pre><code>http://images.google.com/images?num=30&q=larry+bird
|
||||
</code></pre>
|
||||
|
||||
<p>you need to encode the URL as:</p>
|
||||
|
||||
<pre><code>http://images.google.com/images?num=30&amp;q=larry+bird
|
||||
</code></pre>
|
||||
|
||||
<p>in your anchor tag <code>href</code> attribute. Needless to say, this is easy to
|
||||
forget, and is probably the single most common source of HTML validation
|
||||
errors in otherwise well-marked-up web sites.</p>
|
||||
|
||||
<p>Markdown allows you to use these characters naturally, taking care of
|
||||
all the necessary escaping for you. If you use an ampersand as part of
|
||||
an HTML entity, it remains unchanged; otherwise it will be translated
|
||||
into <code>&amp;</code>.</p>
|
||||
|
||||
<p>So, if you want to include a copyright symbol in your article, you can write:</p>
|
||||
|
||||
<pre><code>&copy;
|
||||
</code></pre>
|
||||
|
||||
<p>and Markdown will leave it alone. But if you write:</p>
|
||||
|
||||
<pre><code>AT&T
|
||||
</code></pre>
|
||||
|
||||
<p>Markdown will translate it to:</p>
|
||||
|
||||
<pre><code>AT&amp;T
|
||||
</code></pre>
|
||||
|
||||
<p>Similarly, because Markdown supports <a href="#html">inline HTML</a>, if you use
|
||||
angle brackets as delimiters for HTML tags, Markdown will treat them as
|
||||
such. But if you write:</p>
|
||||
|
||||
<pre><code>4 < 5
|
||||
</code></pre>
|
||||
|
||||
<p>Markdown will translate it to:</p>
|
||||
|
||||
<pre><code>4 &lt; 5
|
||||
</code></pre>
|
||||
|
||||
<p>However, inside Markdown code spans and blocks, angle brackets and
|
||||
ampersands are <em>always</em> encoded automatically. This makes it easy to use
|
||||
Markdown to write about HTML code. (As opposed to raw HTML, which is a
|
||||
terrible format for writing about HTML syntax, because every single <code><</code>
|
||||
and <code>&</code> in your example code needs to be escaped.)</p>
|
||||
|
||||
<hr />
|
||||
|
||||
<h2 id="block">Block Elements</h2>
|
||||
|
||||
<h3 id="p">Paragraphs and Line Breaks</h3>
|
||||
|
||||
<p>A paragraph is simply one or more consecutive lines of text, separated
|
||||
by one or more blank lines. (A blank line is any line that looks like a
|
||||
blank line — a line containing nothing but spaces or tabs is considered
|
||||
blank.) Normal paragraphs should not be intended with spaces or tabs.</p>
|
||||
|
||||
<p>The implication of the “one or more consecutive lines of text” rule is
|
||||
that Markdown supports “hard-wrapped” text paragraphs. This differs
|
||||
significantly from most other text-to-HTML formatters (including Movable
|
||||
Type’s “Convert Line Breaks” option) which translate every line break
|
||||
character in a paragraph into a <code><br /></code> tag.</p>
|
||||
|
||||
<p>When you <em>do</em> want to insert a <code><br /></code> break tag using Markdown, you
|
||||
end a line with two or more spaces, then type return.</p>
|
||||
|
||||
<p>Yes, this takes a tad more effort to create a <code><br /></code>, but a simplistic
|
||||
“every line break is a <code><br /></code>” rule wouldn’t work for Markdown.
|
||||
Markdown’s email-style <a href="#blockquote">blockquoting</a> and multi-paragraph <a href="#list">list items</a>
|
||||
work best — and look better — when you format them with hard breaks.</p>
|
||||
|
||||
<h3 id="header">Headers</h3>
|
||||
|
||||
<p>Markdown supports two styles of headers, <a href="http://docutils.sourceforge.net/mirror/setext.html">Setext</a> and <a href="http://www.aaronsw.com/2002/atx/">atx</a>.</p>
|
||||
|
||||
<p>Setext-style headers are “underlined” using equal signs (for first-level
|
||||
headers) and dashes (for second-level headers). For example:</p>
|
||||
|
||||
<pre><code>This is an H1
|
||||
=============
|
||||
|
||||
This is an H2
|
||||
-------------
|
||||
</code></pre>
|
||||
|
||||
<p>Any number of underlining <code>=</code>’s or <code>-</code>’s will work.</p>
|
||||
|
||||
<p>Atx-style headers use 1-6 hash characters at the start of the line,
|
||||
corresponding to header levels 1-6. For example:</p>
|
||||
|
||||
<pre><code># This is an H1
|
||||
|
||||
## This is an H2
|
||||
|
||||
###### This is an H6
|
||||
</code></pre>
|
||||
|
||||
<p>Optionally, you may “close” atx-style headers. This is purely
|
||||
cosmetic — you can use this if you think it looks better. The
|
||||
closing hashes don’t even need to match the number of hashes
|
||||
used to open the header. (The number of opening hashes
|
||||
determines the header level.) :</p>
|
||||
|
||||
<pre><code># This is an H1 #
|
||||
|
||||
## This is an H2 ##
|
||||
|
||||
### This is an H3 ######
|
||||
</code></pre>
|
||||
|
||||
<h3 id="blockquote">Blockquotes</h3>
|
||||
|
||||
<p>Markdown uses email-style <code>></code> characters for blockquoting. If you’re
|
||||
familiar with quoting passages of text in an email message, then you
|
||||
know how to create a blockquote in Markdown. It looks best if you hard
|
||||
wrap the text and put a <code>></code> before every line:</p>
|
||||
|
||||
<pre><code>> This is a blockquote with two paragraphs. Lorem ipsum dolor sit amet,
|
||||
> consectetuer adipiscing elit. Aliquam hendrerit mi posuere lectus.
|
||||
> Vestibulum enim wisi, viverra nec, fringilla in, laoreet vitae, risus.
|
||||
>
|
||||
> Donec sit amet nisl. Aliquam semper ipsum sit amet velit. Suspendisse
|
||||
> id sem consectetuer libero luctus adipiscing.
|
||||
</code></pre>
|
||||
|
||||
<p>Markdown allows you to be lazy and only put the <code>></code> before the first
|
||||
line of a hard-wrapped paragraph:</p>
|
||||
|
||||
<pre><code>> This is a blockquote with two paragraphs. Lorem ipsum dolor sit amet,
|
||||
consectetuer adipiscing elit. Aliquam hendrerit mi posuere lectus.
|
||||
Vestibulum enim wisi, viverra nec, fringilla in, laoreet vitae, risus.
|
||||
|
||||
> Donec sit amet nisl. Aliquam semper ipsum sit amet velit. Suspendisse
|
||||
id sem consectetuer libero luctus adipiscing.
|
||||
</code></pre>
|
||||
|
||||
<p>Blockquotes can be nested (i.e. a blockquote-in-a-blockquote) by
|
||||
adding additional levels of <code>></code>:</p>
|
||||
|
||||
<pre><code>> This is the first level of quoting.
|
||||
>
|
||||
> > This is nested blockquote.
|
||||
>
|
||||
> Back to the first level.
|
||||
</code></pre>
|
||||
|
||||
<p>Blockquotes can contain other Markdown elements, including headers, lists,
|
||||
and code blocks:</p>
|
||||
|
||||
<pre><code>> ## This is a header.
|
||||
>
|
||||
> 1. This is the first list item.
|
||||
> 2. This is the second list item.
|
||||
>
|
||||
> Here's some example code:
|
||||
>
|
||||
> return shell_exec("echo $input | $markdown_script");
|
||||
</code></pre>
|
||||
|
||||
<p>Any decent text editor should make email-style quoting easy. For
|
||||
example, with BBEdit, you can make a selection and choose Increase
|
||||
Quote Level from the Text menu.</p>
|
||||
|
||||
<h3 id="list">Lists</h3>
|
||||
|
||||
<p>Markdown supports ordered (numbered) and unordered (bulleted) lists.</p>
|
||||
|
||||
<p>Unordered lists use asterisks, pluses, and hyphens — interchangably
|
||||
— as list markers:</p>
|
||||
|
||||
<pre><code>* Red
|
||||
* Green
|
||||
* Blue
|
||||
</code></pre>
|
||||
|
||||
<p>is equivalent to:</p>
|
||||
|
||||
<pre><code>+ Red
|
||||
+ Green
|
||||
+ Blue
|
||||
</code></pre>
|
||||
|
||||
<p>and:</p>
|
||||
|
||||
<pre><code>- Red
|
||||
- Green
|
||||
- Blue
|
||||
</code></pre>
|
||||
|
||||
<p>Ordered lists use numbers followed by periods:</p>
|
||||
|
||||
<pre><code>1. Bird
|
||||
2. McHale
|
||||
3. Parish
|
||||
</code></pre>
|
||||
|
||||
<p>It’s important to note that the actual numbers you use to mark the
|
||||
list have no effect on the HTML output Markdown produces. The HTML
|
||||
Markdown produces from the above list is:</p>
|
||||
|
||||
<pre><code><ol>
|
||||
<li>Bird</li>
|
||||
<li>McHale</li>
|
||||
<li>Parish</li>
|
||||
</ol>
|
||||
</code></pre>
|
||||
|
||||
<p>If you instead wrote the list in Markdown like this:</p>
|
||||
|
||||
<pre><code>1. Bird
|
||||
1. McHale
|
||||
1. Parish
|
||||
</code></pre>
|
||||
|
||||
<p>or even:</p>
|
||||
|
||||
<pre><code>3. Bird
|
||||
1. McHale
|
||||
8. Parish
|
||||
</code></pre>
|
||||
|
||||
<p>you’d get the exact same HTML output. The point is, if you want to,
|
||||
you can use ordinal numbers in your ordered Markdown lists, so that
|
||||
the numbers in your source match the numbers in your published HTML.
|
||||
But if you want to be lazy, you don’t have to.</p>
|
||||
|
||||
<p>If you do use lazy list numbering, however, you should still start the
|
||||
list with the number 1. At some point in the future, Markdown may support
|
||||
starting ordered lists at an arbitrary number.</p>
|
||||
|
||||
<p>List markers typically start at the left margin, but may be indented by
|
||||
up to three spaces. List markers must be followed by one or more spaces
|
||||
or a tab.</p>
|
||||
|
||||
<p>To make lists look nice, you can wrap items with hanging indents:</p>
|
||||
|
||||
<pre><code>* Lorem ipsum dolor sit amet, consectetuer adipiscing elit.
|
||||
Aliquam hendrerit mi posuere lectus. Vestibulum enim wisi,
|
||||
viverra nec, fringilla in, laoreet vitae, risus.
|
||||
* Donec sit amet nisl. Aliquam semper ipsum sit amet velit.
|
||||
Suspendisse id sem consectetuer libero luctus adipiscing.
|
||||
</code></pre>
|
||||
|
||||
<p>But if you want to be lazy, you don’t have to:</p>
|
||||
|
||||
<pre><code>* Lorem ipsum dolor sit amet, consectetuer adipiscing elit.
|
||||
Aliquam hendrerit mi posuere lectus. Vestibulum enim wisi,
|
||||
viverra nec, fringilla in, laoreet vitae, risus.
|
||||
* Donec sit amet nisl. Aliquam semper ipsum sit amet velit.
|
||||
Suspendisse id sem consectetuer libero luctus adipiscing.
|
||||
</code></pre>
|
||||
|
||||
<p>If list items are separated by blank lines, Markdown will wrap the
|
||||
items in <code><p></code> tags in the HTML output. For example, this input:</p>
|
||||
|
||||
<pre><code>* Bird
|
||||
* Magic
|
||||
</code></pre>
|
||||
|
||||
<p>will turn into:</p>
|
||||
|
||||
<pre><code><ul>
|
||||
<li>Bird</li>
|
||||
<li>Magic</li>
|
||||
</ul>
|
||||
</code></pre>
|
||||
|
||||
<p>But this:</p>
|
||||
|
||||
<pre><code>* Bird
|
||||
|
||||
* Magic
|
||||
</code></pre>
|
||||
|
||||
<p>will turn into:</p>
|
||||
|
||||
<pre><code><ul>
|
||||
<li><p>Bird</p></li>
|
||||
<li><p>Magic</p></li>
|
||||
</ul>
|
||||
</code></pre>
|
||||
|
||||
<p>List items may consist of multiple paragraphs. Each subsequent
|
||||
paragraph in a list item must be intended by either 4 spaces
|
||||
or one tab:</p>
|
||||
|
||||
<pre><code>1. This is a list item with two paragraphs. Lorem ipsum dolor
|
||||
sit amet, consectetuer adipiscing elit. Aliquam hendrerit
|
||||
mi posuere lectus.
|
||||
|
||||
Vestibulum enim wisi, viverra nec, fringilla in, laoreet
|
||||
vitae, risus. Donec sit amet nisl. Aliquam semper ipsum
|
||||
sit amet velit.
|
||||
|
||||
2. Suspendisse id sem consectetuer libero luctus adipiscing.
|
||||
</code></pre>
|
||||
|
||||
<p>It looks nice if you indent every line of the subsequent
|
||||
paragraphs, but here again, Markdown will allow you to be
|
||||
lazy:</p>
|
||||
|
||||
<pre><code>* This is a list item with two paragraphs.
|
||||
|
||||
This is the second paragraph in the list item. You're
|
||||
only required to indent the first line. Lorem ipsum dolor
|
||||
sit amet, consectetuer adipiscing elit.
|
||||
|
||||
* Another item in the same list.
|
||||
</code></pre>
|
||||
|
||||
<p>To put a blockquote within a list item, the blockquote’s <code>></code>
|
||||
delimiters need to be indented:</p>
|
||||
|
||||
<pre><code>* A list item with a blockquote:
|
||||
|
||||
> This is a blockquote
|
||||
> inside a list item.
|
||||
</code></pre>
|
||||
|
||||
<p>To put a code block within a list item, the code block needs
|
||||
to be indented <em>twice</em> — 8 spaces or two tabs:</p>
|
||||
|
||||
<pre><code>* A list item with a code block:
|
||||
|
||||
<code goes here>
|
||||
</code></pre>
|
||||
|
||||
<p>It’s worth noting that it’s possible to trigger an ordered list by
|
||||
accident, by writing something like this:</p>
|
||||
|
||||
<pre><code>1986. What a great season.
|
||||
</code></pre>
|
||||
|
||||
<p>In other words, a <em>number-period-space</em> sequence at the beginning of a
|
||||
line. To avoid this, you can backslash-escape the period:</p>
|
||||
|
||||
<pre><code>1986\. What a great season.
|
||||
</code></pre>
|
||||
|
||||
<h3 id="precode">Code Blocks</h3>
|
||||
|
||||
<p>Pre-formatted code blocks are used for writing about programming or
|
||||
markup source code. Rather than forming normal paragraphs, the lines
|
||||
of a code block are interpreted literally. Markdown wraps a code block
|
||||
in both <code><pre></code> and <code><code></code> tags.</p>
|
||||
|
||||
<p>To produce a code block in Markdown, simply indent every line of the
|
||||
block by at least 4 spaces or 1 tab. For example, given this input:</p>
|
||||
|
||||
<pre><code>This is a normal paragraph:
|
||||
|
||||
This is a code block.
|
||||
</code></pre>
|
||||
|
||||
<p>Markdown will generate:</p>
|
||||
|
||||
<pre><code><p>This is a normal paragraph:</p>
|
||||
|
||||
<pre><code>This is a code block.
|
||||
</code></pre>
|
||||
</code></pre>
|
||||
|
||||
<p>One level of indentation — 4 spaces or 1 tab — is removed from each
|
||||
line of the code block. For example, this:</p>
|
||||
|
||||
<pre><code>Here is an example of AppleScript:
|
||||
|
||||
tell application "Foo"
|
||||
beep
|
||||
end tell
|
||||
</code></pre>
|
||||
|
||||
<p>will turn into:</p>
|
||||
|
||||
<pre><code><p>Here is an example of AppleScript:</p>
|
||||
|
||||
<pre><code>tell application "Foo"
|
||||
beep
|
||||
end tell
|
||||
</code></pre>
|
||||
</code></pre>
|
||||
|
||||
<p>A code block continues until it reaches a line that is not indented
|
||||
(or the end of the article).</p>
|
||||
|
||||
<p>Within a code block, ampersands (<code>&</code>) and angle brackets (<code><</code> and <code>></code>)
|
||||
are automatically converted into HTML entities. This makes it very
|
||||
easy to include example HTML source code using Markdown — just paste
|
||||
it and indent it, and Markdown will handle the hassle of encoding the
|
||||
ampersands and angle brackets. For example, this:</p>
|
||||
|
||||
<pre><code> <div class="footer">
|
||||
&copy; 2004 Foo Corporation
|
||||
</div>
|
||||
</code></pre>
|
||||
|
||||
<p>will turn into:</p>
|
||||
|
||||
<pre><code><pre><code>&lt;div class="footer"&gt;
|
||||
&amp;copy; 2004 Foo Corporation
|
||||
&lt;/div&gt;
|
||||
</code></pre>
|
||||
</code></pre>
|
||||
|
||||
<p>Regular Markdown syntax is not processed within code blocks. E.g.,
|
||||
asterisks are just literal asterisks within a code block. This means
|
||||
it’s also easy to use Markdown to write about Markdown’s own syntax.</p>
|
||||
|
||||
<h3 id="hr">Horizontal Rules</h3>
|
||||
|
||||
<p>You can produce a horizontal rule tag (<code><hr /></code>) by placing three or
|
||||
more hyphens or asterisks on a line by themselves. If you wish, you
|
||||
may use spaces between the hyphens or asterisks. Each of the following
|
||||
lines will produce a horizontal rule:</p>
|
||||
|
||||
<pre><code>* * *
|
||||
|
||||
***
|
||||
|
||||
*****
|
||||
|
||||
- - -
|
||||
|
||||
---------------------------------------
|
||||
</code></pre>
|
||||
|
||||
<hr />
|
||||
|
||||
<h2 id="span">Span Elements</h2>
|
||||
|
||||
<h3 id="link">Links</h3>
|
||||
|
||||
<p>Markdown supports two style of links: <em>inline</em> and <em>reference</em>.</p>
|
||||
|
||||
<p>In both styles, the link text is delimited by [square brackets].</p>
|
||||
|
||||
<p>To create an inline link, use a set of regular parentheses immediately
|
||||
after the link text’s closing square bracket. Inside the parentheses,
|
||||
put the URL where you want the link to point, along with an <em>optional</em>
|
||||
title for the link, surrounded in quotes. For example:</p>
|
||||
|
||||
<pre><code>This is [an example](http://example.com/ "Title") inline link.
|
||||
|
||||
[This link](http://example.net/) has no title attribute.
|
||||
</code></pre>
|
||||
|
||||
<p>Will produce:</p>
|
||||
|
||||
<pre><code><p>This is <a href="http://example.com/" title="Title">
|
||||
an example</a> inline link.</p>
|
||||
|
||||
<p><a href="http://example.net/">This link</a> has no
|
||||
title attribute.</p>
|
||||
</code></pre>
|
||||
|
||||
<p>If you’re referring to a local resource on the same server, you can
|
||||
use relative paths:</p>
|
||||
|
||||
<pre><code>See my [About](/about/) page for details.
|
||||
</code></pre>
|
||||
|
||||
<p>Reference-style links use a second set of square brackets, inside
|
||||
which you place a label of your choosing to identify the link:</p>
|
||||
|
||||
<pre><code>This is [an example][id] reference-style link.
|
||||
</code></pre>
|
||||
|
||||
<p>You can optionally use a space to separate the sets of brackets:</p>
|
||||
|
||||
<pre><code>This is [an example] [id] reference-style link.
|
||||
</code></pre>
|
||||
|
||||
<p>Then, anywhere in the document, you define your link label like this,
|
||||
on a line by itself:</p>
|
||||
|
||||
<pre><code>[id]: http://example.com/ "Optional Title Here"
|
||||
</code></pre>
|
||||
|
||||
<p>That is:</p>
|
||||
|
||||
<ul>
|
||||
<li>Square brackets containing the link identifier (optionally
|
||||
indented from the left margin using spaces or tabs);</li>
|
||||
<li>followed by a colon;</li>
|
||||
<li>followed by one or more spaces (or tabs);</li>
|
||||
<li>followed by the URL for the link;</li>
|
||||
<li>optionally followed by a title attribute for the link, enclosed
|
||||
in double or single quotes.</li>
|
||||
</ul>
|
||||
|
||||
<p>The link URL may, optionally, be surrounded by angle brackets:</p>
|
||||
|
||||
<pre><code>[id]: <http://example.com/> "Optional Title Here"
|
||||
</code></pre>
|
||||
|
||||
<p>You can put the title attribute on the next line and use extra spaces
|
||||
or tabs for padding, which tends to look better with longer URLs:</p>
|
||||
|
||||
<pre><code>[id]: http://example.com/longish/path/to/resource/here
|
||||
"Optional Title Here"
|
||||
</code></pre>
|
||||
|
||||
<p>Link definitions are only used for creating links during Markdown
|
||||
processing, and are stripped from your document in the HTML output.</p>
|
||||
|
||||
<p>Link definition names may constist of letters, numbers, spaces, and punctuation — but they are <em>not</em> case sensitive. E.g. these two links:</p>
|
||||
|
||||
<pre><code>[link text][a]
|
||||
[link text][A]
|
||||
</code></pre>
|
||||
|
||||
<p>are equivalent.</p>
|
||||
|
||||
<p>The <em>implicit link name</em> shortcut allows you to omit the name of the
|
||||
link, in which case the link text itself is used as the name.
|
||||
Just use an empty set of square brackets — e.g., to link the word
|
||||
“Google” to the google.com web site, you could simply write:</p>
|
||||
|
||||
<pre><code>[Google][]
|
||||
</code></pre>
|
||||
|
||||
<p>And then define the link:</p>
|
||||
|
||||
<pre><code>[Google]: http://google.com/
|
||||
</code></pre>
|
||||
|
||||
<p>Because link names may contain spaces, this shortcut even works for
|
||||
multiple words in the link text:</p>
|
||||
|
||||
<pre><code>Visit [Daring Fireball][] for more information.
|
||||
</code></pre>
|
||||
|
||||
<p>And then define the link:</p>
|
||||
|
||||
<pre><code>[Daring Fireball]: http://daringfireball.net/
|
||||
</code></pre>
|
||||
|
||||
<p>Link definitions can be placed anywhere in your Markdown document. I
|
||||
tend to put them immediately after each paragraph in which they’re
|
||||
used, but if you want, you can put them all at the end of your
|
||||
document, sort of like footnotes.</p>
|
||||
|
||||
<p>Here’s an example of reference links in action:</p>
|
||||
|
||||
<pre><code>I get 10 times more traffic from [Google] [1] than from
|
||||
[Yahoo] [2] or [MSN] [3].
|
||||
|
||||
[1]: http://google.com/ "Google"
|
||||
[2]: http://search.yahoo.com/ "Yahoo Search"
|
||||
[3]: http://search.msn.com/ "MSN Search"
|
||||
</code></pre>
|
||||
|
||||
<p>Using the implicit link name shortcut, you could instead write:</p>
|
||||
|
||||
<pre><code>I get 10 times more traffic from [Google][] than from
|
||||
[Yahoo][] or [MSN][].
|
||||
|
||||
[google]: http://google.com/ "Google"
|
||||
[yahoo]: http://search.yahoo.com/ "Yahoo Search"
|
||||
[msn]: http://search.msn.com/ "MSN Search"
|
||||
</code></pre>
|
||||
|
||||
<p>Both of the above examples will produce the following HTML output:</p>
|
||||
|
||||
<pre><code><p>I get 10 times more traffic from <a href="http://google.com/"
|
||||
title="Google">Google</a> than from
|
||||
<a href="http://search.yahoo.com/" title="Yahoo Search">Yahoo</a>
|
||||
or <a href="http://search.msn.com/" title="MSN Search">MSN</a>.</p>
|
||||
</code></pre>
|
||||
|
||||
<p>For comparison, here is the same paragraph written using
|
||||
Markdown’s inline link style:</p>
|
||||
|
||||
<pre><code>I get 10 times more traffic from [Google](http://google.com/ "Google")
|
||||
than from [Yahoo](http://search.yahoo.com/ "Yahoo Search") or
|
||||
[MSN](http://search.msn.com/ "MSN Search").
|
||||
</code></pre>
|
||||
|
||||
<p>The point of reference-style links is not that they’re easier to
|
||||
write. The point is that with reference-style links, your document
|
||||
source is vastly more readable. Compare the above examples: using
|
||||
reference-style links, the paragraph itself is only 81 characters
|
||||
long; with inline-style links, it’s 176 characters; and as raw HTML,
|
||||
it’s 234 characters. In the raw HTML, there’s more markup than there
|
||||
is text.</p>
|
||||
|
||||
<p>With Markdown’s reference-style links, a source document much more
|
||||
closely resembles the final output, as rendered in a browser. By
|
||||
allowing you to move the markup-related metadata out of the paragraph,
|
||||
you can add links without interrupting the narrative flow of your
|
||||
prose.</p>
|
||||
|
||||
<h3 id="em">Emphasis</h3>
|
||||
|
||||
<p>Markdown treats asterisks (<code>*</code>) and underscores (<code>_</code>) as indicators of
|
||||
emphasis. Text wrapped with one <code>*</code> or <code>_</code> will be wrapped with an
|
||||
HTML <code><em></code> tag; double <code>*</code>’s or <code>_</code>’s will be wrapped with an HTML
|
||||
<code><strong></code> tag. E.g., this input:</p>
|
||||
|
||||
<pre><code>*single asterisks*
|
||||
|
||||
_single underscores_
|
||||
|
||||
**double asterisks**
|
||||
|
||||
__double underscores__
|
||||
</code></pre>
|
||||
|
||||
<p>will produce:</p>
|
||||
|
||||
<pre><code><em>single asterisks</em>
|
||||
|
||||
<em>single underscores</em>
|
||||
|
||||
<strong>double asterisks</strong>
|
||||
|
||||
<strong>double underscores</strong>
|
||||
</code></pre>
|
||||
|
||||
<p>You can use whichever style you prefer; the lone restriction is that
|
||||
the same character must be used to open and close an emphasis span.</p>
|
||||
|
||||
<p>Emphasis can be used in the middle of a word:</p>
|
||||
|
||||
<pre><code>un*fucking*believable
|
||||
</code></pre>
|
||||
|
||||
<p>But if you surround an <code>*</code> or <code>_</code> with spaces, it’ll be treated as a
|
||||
literal asterisk or underscore.</p>
|
||||
|
||||
<p>To produce a literal asterisk or underscore at a position where it
|
||||
would otherwise be used as an emphasis delimiter, you can backslash
|
||||
escape it:</p>
|
||||
|
||||
<pre><code>\*this text is surrounded by literal asterisks\*
|
||||
</code></pre>
|
||||
|
||||
<h3 id="code">Code</h3>
|
||||
|
||||
<p>To indicate a span of code, wrap it with backtick quotes (<code>`</code>).
|
||||
Unlike a pre-formatted code block, a code span indicates code within a
|
||||
normal paragraph. For example:</p>
|
||||
|
||||
<pre><code>Use the `printf()` function.
|
||||
</code></pre>
|
||||
|
||||
<p>will produce:</p>
|
||||
|
||||
<pre><code><p>Use the <code>printf()</code> function.</p>
|
||||
</code></pre>
|
||||
|
||||
<p>To include a literal backtick character within a code span, you can
|
||||
backslash escape it:</p>
|
||||
|
||||
<pre><code>`There is a literal backtick (\`) here.`
|
||||
</code></pre>
|
||||
|
||||
<p>Or, if you prefer, you can use multiple backticks as the opening and
|
||||
closing delimiters:</p>
|
||||
|
||||
<pre><code>``There is a literal backtick (`) here.``
|
||||
</code></pre>
|
||||
|
||||
<p>Both of the previous two examples will produce this:</p>
|
||||
|
||||
<pre><code><p><code>There is a literal backtick (`) here.</code></p>
|
||||
</code></pre>
|
||||
|
||||
<p>With a code span, ampersands and angle brackets are encoded as HTML
|
||||
entities automatically, which makes it easy to include example HTML
|
||||
tags. Markdown will turn this:</p>
|
||||
|
||||
<pre><code>Please don't use any `<blink>` tags.
|
||||
</code></pre>
|
||||
|
||||
<p>into:</p>
|
||||
|
||||
<pre><code><p>Please don't use any <code>&lt;blink&gt;</code> tags.</p>
|
||||
</code></pre>
|
||||
|
||||
<p>You can write this:</p>
|
||||
|
||||
<pre><code>`&#8212;` is the decimal-encoded equivalent of `&mdash;`.
|
||||
</code></pre>
|
||||
|
||||
<p>to produce:</p>
|
||||
|
||||
<pre><code><p><code>&amp;#8212;</code> is the decimal-encoded
|
||||
equivalent of <code>&amp;mdash;</code>.</p>
|
||||
</code></pre>
|
||||
|
||||
<h3 id="img">Images</h3>
|
||||
|
||||
<p>Admittedly, it’s fairly difficult to devise a “natural” syntax for
|
||||
placing images into a plain text document format.</p>
|
||||
|
||||
<p>Markdown uses an image syntax that is intended to resemble the syntax
|
||||
for links, allowing for two styles: <em>inline</em> and <em>reference</em>.</p>
|
||||
|
||||
<p>Inline image syntax looks like this:</p>
|
||||
|
||||
<pre><code>
|
||||
|
||||
|
||||
</code></pre>
|
||||
|
||||
<p>That is:</p>
|
||||
|
||||
<ul>
|
||||
<li>An exclamation mark: <code>!</code>;</li>
|
||||
<li>followed by a set of square brackets, containing the <code>alt</code>
|
||||
attribute text for the image;</li>
|
||||
<li>followed by a set of parentheses, containing the URL or path to
|
||||
the image, and an optional <code>title</code> attribute enclosed in double
|
||||
or single quotes.</li>
|
||||
</ul>
|
||||
|
||||
<p>Reference-style image syntax looks like this:</p>
|
||||
|
||||
<pre><code>![Alt text][id]
|
||||
</code></pre>
|
||||
|
||||
<p>Where “id” is the name of a defined image reference. Image references
|
||||
are defined using syntax identical to link references:</p>
|
||||
|
||||
<pre><code>[id]: url/to/image "Optional title attribute"
|
||||
</code></pre>
|
||||
|
||||
<p>As of this writing, Markdown has no syntax for specifying the
|
||||
dimensions of an image; if this is important to you, you can simply
|
||||
use regular HTML <code><img></code> tags.</p>
|
||||
|
||||
<hr />
|
||||
|
||||
<h2 id="misc">Miscellaneous</h2>
|
||||
|
||||
<h3 id="autolink">Automatic Links</h3>
|
||||
|
||||
<p>Markdown supports a shortcut style for creating “automatic” links for URLs and email addresses: simply surround the URL or email address with angle brackets. What this means is that if you want to show the actual text of a URL or email address, and also have it be a clickable link, you can do this:</p>
|
||||
|
||||
<pre><code><http://example.com/>
|
||||
</code></pre>
|
||||
|
||||
<p>Markdown will turn this into:</p>
|
||||
|
||||
<pre><code><a href="http://example.com/">http://example.com/</a>
|
||||
</code></pre>
|
||||
|
||||
<p>Automatic links for email addresses work similarly, except that
|
||||
Markdown will also perform a bit of randomized decimal and hex
|
||||
entity-encoding to help obscure your address from address-harvesting
|
||||
spambots. For example, Markdown will turn this:</p>
|
||||
|
||||
<pre><code><[email protected]>
|
||||
</code></pre>
|
||||
|
||||
<p>into something like this:</p>
|
||||
|
||||
<pre><code><a href="&#x6D;&#x61;i&#x6C;&#x74;&#x6F;:&#x61;&#x64;&#x64;&#x72;&#x65;
|
||||
&#115;&#115;&#64;&#101;&#120;&#x61;&#109;&#x70;&#x6C;e&#x2E;&#99;&#111;
|
||||
&#109;">&#x61;&#x64;&#x64;&#x72;&#x65;&#115;&#115;&#64;&#101;&#120;&#x61;
|
||||
&#109;&#x70;&#x6C;e&#x2E;&#99;&#111;&#109;</a>
|
||||
</code></pre>
|
||||
|
||||
<p>which will render in a browser as a clickable link to “[email protected]”.</p>
|
||||
|
||||
<p>(This sort of entity-encoding trick will indeed fool many, if not
|
||||
most, address-harvesting bots, but it definitely won’t fool all of
|
||||
them. It’s better than nothing, but an address published in this way
|
||||
will probably eventually start receiving spam.)</p>
|
||||
|
||||
<h3 id="backslash">Backslash Escapes</h3>
|
||||
|
||||
<p>Markdown allows you to use backslash escapes to generate literal
|
||||
characters which would otherwise have special meaning in Markdown’s
|
||||
formatting syntax. For example, if you wanted to surround a word with
|
||||
literal asterisks (instead of an HTML <code><em></code> tag), you can backslashes
|
||||
before the asterisks, like this:</p>
|
||||
|
||||
<pre><code>\*literal asterisks\*
|
||||
</code></pre>
|
||||
|
||||
<p>Markdown provides backslash escapes for the following characters:</p>
|
||||
|
||||
<pre><code>\ backslash
|
||||
` backtick
|
||||
* asterisk
|
||||
_ underscore
|
||||
{} curly braces
|
||||
[] square brackets
|
||||
() parentheses
|
||||
# hash mark
|
||||
. dot
|
||||
! exclamation mark
|
||||
</code></pre>
|
||||
|
||||
</div> <!-- article -->
|
||||
@@ -1,4 +0,0 @@
|
||||
<P ALIGN=CENTER><B>Activity Modules</B></P>
|
||||
|
||||
<P>Moodle contains a wide range of activity modules that can be used to
|
||||
build up any type of course.</P>
|
||||
@@ -1,18 +0,0 @@
|
||||
<P ALIGN=CENTER><B>Uploading a picture</B></P>
|
||||
|
||||
<P>You can upload a picture from your computer to this server, and this picture will be used in various places to represent you.
|
||||
<P>For this reason, the best images to use are a close-up of your face, but you can use any image you like.
|
||||
<P>The picture must be in JPG or PNG format (ie the names will usually end in .jpg or .png).
|
||||
<P>You can get a picture file using one of four methods:
|
||||
|
||||
<OL>
|
||||
<LI>Using a digital camera, your photos will most likely already be on your computer in the right format.
|
||||
<LI>You can use a scanner to scan a printed photograph. Make sure you save it as JPG or PNG format.
|
||||
<LI>If you're artistic, you might draw a picture using a paint program.
|
||||
<LI>Lastly, you can "steal" images from the web. <A TARGET=google HREF="http://images.google.com/">http://images.google.com</A> is a superb place to search for images. Once you find one, you can "right-click" on them with the mouse and choose "Save this image..." from the menu (different computers may vary slightly).
|
||||
</OL>
|
||||
|
||||
<P>To upload the image, click the "Browse" button on this editing page, and select the image from your hard disk.
|
||||
<P>NOTE: Make sure that the file is not larger than the maximum size listed, or it will not be uploaded.
|
||||
<P>Then click "Update my Profile" at the bottom - the image file will be cropped to a square and resized down to 100x100 pixels.
|
||||
<P>When you are taken back to your profile page, the image might not appear to have changed. If this is so, just use the "Reload" button in your browser.
|
||||
@@ -1,86 +0,0 @@
|
||||
<P ALIGN=CENTER><B>Questions</B></P>
|
||||
|
||||
<P>A good way to help other people think about a subject is to
|
||||
ask them a question about it. Being asked a good question
|
||||
can really help us put information together, evaluate our
|
||||
existing ideas and create new ideas.</P>
|
||||
|
||||
<P>Asking questions that are specifically intended to help
|
||||
others learn is known as <I>Socratic questioning</I>, named
|
||||
after Socrates in Ancient Greece.</P>
|
||||
|
||||
<P>Socratic questions require you to listen very carefully
|
||||
to the other person to help you judge and phrase your question
|
||||
in a helpful, constructive, and hopefully non-confrontational way.
|
||||
|
||||
<P>Here are some examples of such questions:</P>
|
||||
|
||||
<!--Hidden comment: Someday I will include a great example dialogue here -->
|
||||
|
||||
<h3>Questions of clarification</h3>
|
||||
<ul>
|
||||
<li>What do you mean when you say ______?</li>
|
||||
<li>What is your main point?</li>
|
||||
<li>How does _____ relate to _____?</li>
|
||||
<li>Could you put that another way?</li>
|
||||
<li>Let me see if I understand you; do you mean _____ or _____?</li>
|
||||
<li>How does this relate to our problem/discussion/issue?</li>
|
||||
<li>Jane, can you summarize in your own words what Richard said? ... Richard, is this what you meant?</li>
|
||||
<li>Could you give me an example?</li>
|
||||
<li>Would _____ be a good example of that?</li>
|
||||
</ul>
|
||||
<h3>Questions that probe assumptions</h3>
|
||||
<ul>
|
||||
<li>What are you assuming here?</li>
|
||||
<li>What is Jenny assuming?</li>
|
||||
<li>What could we assume instead?</li>
|
||||
<li>You seem to be assuming _____. Do I understand you correctly?</li>
|
||||
<li>All of your reasoning depends on the idea that _____. Why have you based your reasoning on _____ instead of _____?</li>
|
||||
<li>You seem to be assuming _____. How do you justify taking that for granted?</li>
|
||||
<li>Is that always the case? Why do you think the assumption holds here?</li>
|
||||
<li>Why would someone make that assumption? </li>
|
||||
</ul>
|
||||
<h3>Questions that probe reasons and evidence</h3>
|
||||
<ul>
|
||||
<li>Could you explain your reasons to us?</li>
|
||||
<li>How does that apply to this case?</li>
|
||||
<li>Is there a reason to doubt that evidence?</li>
|
||||
<li>Who is in a position to know that is true?</li>
|
||||
<li>What would you say to someone who said that ____?</li>
|
||||
<li>Can someone else give evidence to support that view?</li>
|
||||
<li>By what reasoning did you come to that conclusion?</li>
|
||||
<li>How could we find out if that is true? </li>
|
||||
</ul>
|
||||
<h3>Questions about viewpoints or perspectives </h3>
|
||||
<ul>
|
||||
<li>What are you implying by that?</li>
|
||||
<li>When you say _____, are you implying _____?</li>
|
||||
<li>But, if that happened, what else would happen as a result? Why?</li>
|
||||
<li>What effect would that have?</li>
|
||||
<li>Would that necessarily happen or only possibly/probably happen?</li>
|
||||
<li>What is an alternative?</li>
|
||||
<li>If _____ and _____ are the case, then what might also be true?</li>
|
||||
<li>If we say that ____ is ethical, how about _____? </li>
|
||||
</ul>
|
||||
<h3>Questions that probe implications and consequences </h3>
|
||||
<ul>
|
||||
<li>How can we find out?</li>
|
||||
<li>What does this question assume?</li>
|
||||
<li>Would _____ ask this question differently?</li>
|
||||
<li>How could someone settle this question?</li>
|
||||
<li>Can we break this question down at all?</li>
|
||||
<li>Is this question clear? Do we understand it?</li>
|
||||
<li>Is this question easy or hard to answer? Why?</li>
|
||||
<li>Do we all agree that this is the question?</li>
|
||||
<li>To answer this question, what other questions must we answer first?</li>
|
||||
<li>How would _____ state the issue?</li>
|
||||
<li>Why is this issue important?</li>
|
||||
<li>Is this the most important question, or is there an underlying question?</li>
|
||||
<li>Can you see how this might relate to ________?</li>
|
||||
</ul>
|
||||
|
||||
<HR>
|
||||
<FONT SIZE=1><I>Questions adapted from Paul, R. (1993). Critical Thinking: How To Prepare Students for a Rapidly Changing World: Foundation for Critical Thinking, Santa Rosa, CA. </I></FONT>
|
||||
|
||||
<p align=right><a href="help.php?file=writing.html">More info about writing</a></p>
|
||||
<p align=right><a href="help.php?file=reading.html">More info about reading</a></p>
|
||||
@@ -1,13 +0,0 @@
|
||||
<P ALIGN=CENTER><B>Reading</B></P>
|
||||
|
||||
<P>When reading texts quickly it is often very easy to misunderstand what the
|
||||
author was trying to say.</P>
|
||||
|
||||
<P>To avoid misunderstanding, read their words carefully and try to see things
|
||||
from the author's point of view.<P>
|
||||
|
||||
<P>It can also help to think of what the author has NOT said or left in doubt
|
||||
- this may help you form questions in your own mind.</P>
|
||||
|
||||
<p align=right><a href="help.php?file=writing.html">More info about writing</a></p>
|
||||
<p align=right><a href="help.php?file=questions.html">More info about questions</a></p>
|
||||
@@ -1,160 +0,0 @@
|
||||
<P ALIGN=CENTER><B>About the Richtext HTML editor</B></P>
|
||||
|
||||
<P>Availability: <B>
|
||||
<?php if (!$CFG->htmleditor) {
|
||||
print_string("htmleditordisabledadmin");
|
||||
} else if (!$USER->htmleditor) {
|
||||
print_string("htmleditordisabled");
|
||||
} else if (!can_use_richtext_editor()) {
|
||||
print_string("htmleditordisabledbrowser");
|
||||
} else {
|
||||
print_string("htmleditoravailable");
|
||||
}
|
||||
?>
|
||||
</B></P>
|
||||
|
||||
<P>The Richtext HTML editor provides a word-processor interface embedded in your web page to allow you to edit text in an intuitive way, and produces normal HTML code.
|
||||
|
||||
<P>In addition to formatting text, this editor provides a number of extra features you may find useful.
|
||||
|
||||
<P><B>Paste text in from other Applications</B></P>
|
||||
<UL>
|
||||
<P>You can cut and paste rich text from other Windows applications such as Microsoft Word
|
||||
straight into this editor, and your formatting will be preserved. Just use the normal cut and paste
|
||||
menus in your web browser (or Control-C and Control-V).
|
||||
</UL>
|
||||
|
||||
<P><B>Inserting images <img border="0" hspace="10" src="lib/editor/images/ed_image.gif"></B></P>
|
||||
<UL>
|
||||
<P>If you have images that are already published on a web site and accessible via a URL, you can include these images in your texts using the "Insert Image" button.
|
||||
</UL>
|
||||
|
||||
<P><B>Inserting Tables <img border="0" hspace="10" src="lib/editor/images/insert_table.gif"></B></P>
|
||||
<UL>
|
||||
<P>To add layout to your texts, you can use the "Insert Tables" button in the toolbar.
|
||||
</UL>
|
||||
|
||||
<P><B>Inserting Links <img border="0" hspace="10" src="lib/editor/images/ed_link.gif"></B></P>
|
||||
<UL>
|
||||
<P>To make a new link, first type the text that you want to be a link. Then select it and click the link button in the toolbar. Type the URL you want to link to and it's done!
|
||||
</UL>
|
||||
|
||||
|
||||
<P><B>Inserting smilies (emoticons) <img border="0" hspace="10" src="pix/s/smiley.gif" width="15" height="15"></B></P>
|
||||
<UL>
|
||||
<P>To embed these small icons in your text, click on the smiley icon in the toolbar. A dialog will pop up that allows you to select from the following smiley icons. (Alternatively, you can just type the corresponding code straight into your text and it will be converted later when your text is displayed).
|
||||
|
||||
<table border="1">
|
||||
<tr valign="top">
|
||||
<td>
|
||||
<table border="0" align="center" cellpadding="10">
|
||||
<tr>
|
||||
<td><img border="0" hspace="10" src="pix/s/smiley.gif" width="15" height="15"></td>
|
||||
<td>smile</td>
|
||||
<td NOWRAP><FONT FACE=Courier>:-)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img alt border="0" hspace="10" src="pix/s/biggrin.gif" width="15" height="15"></td>
|
||||
<td>big grin</td>
|
||||
<td NOWRAP><FONT FACE=Courier>:-D</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img alt border="0" hspace="10" src="pix/s/wink.gif" width="15" height="15"></td>
|
||||
<td>wink</td>
|
||||
<td NOWRAP><FONT FACE=Courier>;-)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img alt border="0" hspace="10" src="pix/s/mixed.gif" width="15" height="15"></td>
|
||||
<td>mixed</td>
|
||||
<td NOWRAP><FONT FACE=Courier>:-/</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img alt border="0" hspace="10" src="pix/s/thoughtful.gif" width="15" height="15"></td>
|
||||
<td>thoughtful</td>
|
||||
<td NOWRAP><FONT FACE=Courier>V-.</FONT></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img alt border="0" hspace="10" src="pix/s/tongueout.gif" width="15" height="15"></td>
|
||||
<td>tongue out</td>
|
||||
<td NOWRAP><FONT FACE=Courier>:-P</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img alt border="0" hspace="10" src="pix/s/cool.gif" width="15" height="15"></td>
|
||||
<td>cool</td>
|
||||
<td NOWRAP><FONT FACE=Courier>B-)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img alt border="0" hspace="10" src="pix/s/approve.gif" width="15" height="15"></td>
|
||||
<td>approve</td>
|
||||
<td NOWRAP><FONT FACE=Courier>^-)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img alt border="0" hspace="10" src="pix/s/wideeyes.gif" width="15" height="15"></td>
|
||||
<td>wide eyes</td>
|
||||
<td NOWRAP><FONT FACE=Courier>8-)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img alt border="0" hspace="10" src="pix/s/surprise.gif" width="15" height="15"></td>
|
||||
<td>surprise</td>
|
||||
<td NOWRAP><FONT FACE=Courier>8-o</td>
|
||||
</tr>
|
||||
</table>
|
||||
</td>
|
||||
<td>
|
||||
<table border="0" align="center" cellpadding="10">
|
||||
<tr>
|
||||
<td><img alt border="0" hspace="10" src="pix/s/sad.gif" width="15" height="15"></td>
|
||||
<td>sad</td>
|
||||
<td NOWRAP><FONT FACE=Courier>:-(</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img alt border="0" hspace="10" src="pix/s/shy.gif" width="15" height="15"></td>
|
||||
<td>shy</td>
|
||||
<td NOWRAP><FONT FACE=Courier>8-.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img alt border="0" hspace="10" src="pix/s/blush.gif" width="15" height="15"></td>
|
||||
<td>blush</td>
|
||||
<td NOWRAP><FONT FACE=Courier>:-I</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img alt border="0" hspace="10" src="pix/s/kiss.gif" width="15" height="15"></td>
|
||||
<td>kisses</td>
|
||||
<td NOWRAP><FONT FACE=Courier>:-X</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img alt border="0" hspace="10" src="pix/s/clown.gif" width="15" height="15"></td>
|
||||
<td>clown</td>
|
||||
<td NOWRAP><FONT FACE=Courier>:o)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img alt border="0" hspace="10" src="pix/s/blackeye.gif" width="15" height="15"></td>
|
||||
<td>black eye</td>
|
||||
<td NOWRAP><FONT FACE=Courier>P-|</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img alt border="0" hspace="10" src="pix/s/angry.gif" width="15" height="15"></td>
|
||||
<td>angry</td>
|
||||
<td NOWRAP><FONT FACE=Courier>8-[</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img alt border="0" hspace="10" src="pix/s/dead.gif" width="15" height="15"></td>
|
||||
<td>dead</td>
|
||||
<td NOWRAP><FONT FACE=Courier>xx-P</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img alt border="0" hspace="10" src="pix/s/sleepy.gif" width="15" height="15"></td>
|
||||
<td>sleepy</td>
|
||||
<td NOWRAP><FONT FACE=Courier>|-.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img alt border="0" hspace="10" src="pix/s/evil.gif" width="15" height="15"></td>
|
||||
<td>evil</td>
|
||||
<td NOWRAP><FONT FACE=Courier>}-]</td>
|
||||
</tr>
|
||||
</table>
|
||||
</table>
|
||||
|
||||
</UL>
|
||||
|
||||
|
||||
@@ -1,18 +0,0 @@
|
||||
<p align="center"><b>Scales</b></p>
|
||||
|
||||
<p>Teachers can create new custom scales to be used in a course for any grading activities.</p>
|
||||
|
||||
<p>The name of the scale should be a phrase that identifies it clearly: this will appear
|
||||
in scale-selection lists, as well as on context-sensitive help buttons.</p>
|
||||
|
||||
<p>The scale itself is defined by an ordered list of values, ranging from negative to positive, separated by commas. For example:</p>
|
||||
|
||||
<blockquote><i>
|
||||
Disappointing, Not good enough, Average, Good, Very good, Excellent!
|
||||
</i></blockquote>
|
||||
|
||||
<p>Scales should also include a good description of what it means and how it is
|
||||
expected to be used. This description will appear in help pages for teachers and students.</p>
|
||||
|
||||
<p>Finally, there may be one or more "Standard" scales defined on your site by the
|
||||
system administrator. These will be available in all courses.</p>
|
||||
@@ -1,10 +0,0 @@
|
||||
<p align=center><b>Topic/Week summaries</b></p>
|
||||
|
||||
<p>The idea of a topic summary is a very short text to prepare students
|
||||
for the activities within this topic (or week).</p>
|
||||
|
||||
<p>Each summary should be very short so that the course page doesn't become too long.</p>
|
||||
|
||||
<p>If you find yourself wanting to say more than a sentence or two then
|
||||
consider adding a resource to this topic instead (for example, the first activity
|
||||
might be a page called <b>About This Topic</b>).</p>
|
||||
@@ -1,99 +0,0 @@
|
||||
<P ALIGN=CENTER><B>Available surveys</B></P>
|
||||
|
||||
<P>Currently, Moodle only offers specific types of surveys (future versions
|
||||
will enable you to create your own).</P>
|
||||
|
||||
<P>The available surveys have been chosen as being particularly useful for
|
||||
evaluating online learning environments that use a constructivist pedagogy.
|
||||
They are useful to identify certain trends that may be happening among
|
||||
your participants.
|
||||
|
||||
(To see a paper where these are used in a detailed analysis, see:
|
||||
<A TARGET=paper HREF="http://dougiamas.com/writing/herdsa2002">http://dougiamas.com/writing/herdsa2002</A>)</P>
|
||||
|
||||
<HR>
|
||||
<P><B>COLLES - Constructivist On-Line Learning Environment Survey</B></P>
|
||||
<UL>
|
||||
<p>The COLLES comprises an economical 24 statements grouped into six scales,
|
||||
each of which helps us address a key question about the quality of the on-line
|
||||
learning environment: </p>
|
||||
|
||||
<table BORDER="0" CELLSPACING="10" CELLPADDING="10">
|
||||
<tr>
|
||||
<td valign=top>Relevance</td>
|
||||
<td>How relevant is on-line learning to students' professional practices?
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td valign=top>Reflection </td>
|
||||
|
||||
<td>Does on-line learning stimulate students' critical reflective thinking?
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td valign=top>Interactivity </td>
|
||||
<td>To what extent do students engage on-line in rich educative dialogue?
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td valign=top>Tutor Support</td>
|
||||
|
||||
<td>How well do tutors enable students to participate in on-line learning?
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td valign=top>Peer Support </td>
|
||||
<td>Is sensitive and encouraging support provided on-line by fellow students?
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td valign=top>Interpretation </td>
|
||||
|
||||
<td>Do students and tutors make good sense of each other's on-line communications?</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
<p>Underpinning the dynamic view of learning is a new theory of knowing: social
|
||||
constructivism, which portrays the learner as an active conceptualiser within
|
||||
a socially interactive learning environment. Social constructivism is an epistemology,
|
||||
or way of knowing, in which learners collaborate reflectively to co-construct
|
||||
new understandings, especially in the context of mutual inquiry grounded in
|
||||
their personal experience. </p>
|
||||
|
||||
<p>Central to this collaboration is the development of students' communicative
|
||||
competence, that is, the ability to engage in open and critical discourse
|
||||
with both the teacher and peers. This discourse is characterised by an empathic
|
||||
orientation to constructing reciprocal understanding, and a critical attitude
|
||||
towards examining underlying assumptions. </p>
|
||||
|
||||
<p>The COLLES has been designed to enable you
|
||||
to monitor the extent to which you are able to exploit the interactive capacity
|
||||
of the World Wide Web for engaging students in dynamic learning practices. </p>
|
||||
|
||||
<P>
|
||||
(This information has been adapted from the COLLES page. You can find out more about
|
||||
COLLES and the authors of it at:
|
||||
<A TARGET=paper HREF="http://surveylearning.com/colles/">http://surveylearning.com/colles/</A>)</P>
|
||||
</UL>
|
||||
|
||||
|
||||
<HR>
|
||||
<P><B>ATTLS - Attitudes to Thinking and Learning Survey</B></P>
|
||||
<UL>
|
||||
|
||||
<P>The theory of 'ways of knowing', originally from the field of gender research (Belenky et al., 1986) provides us with a survey tool to examine the quality of discourse within a collaborative environment.
|
||||
|
||||
<P>The Attitudes Towards Thinking and Learning Survey (ATTLS) is an instrument developed by Galotti et al. (1999) to measure the extent to which a person is a 'connected knower' (CK) or a 'separate knower' (SK).
|
||||
|
||||
<P>People with higher CK scores tend to find learning more enjoyable, and are often more cooperative, congenial and more willing to build on the ideas of others, while those with higher SK scores tend to take a more critical and argumentative stance to learning.
|
||||
|
||||
<P>Studies have shown that these two learning styles are independent of each other (Galotti et al., 1999; Galotti et al., 2001). Additionally, they are only a reflection of learning attitudes, not learning capacities or intellectual power.
|
||||
|
||||
<P><I>Belenky, M. F., Clinchy, B. M., Goldberger, N. R., & Tarule, J. M. (1986). Women's Ways of Knowing: The Development of Self, Voice, and Mind. New York: Basic Books, Inc. </I></P>
|
||||
|
||||
<P><I>Galotti, K. M., Clinchy, B. M., Ainsworth, K., Lavin, B., & Mansfield, A. F. (1999). A New Way of Assessing Ways of Knowing: The Attitudes Towards Thinking and Learning Survey (ATTLS). Sex Roles, 40(9/10), 745-766.</I></P>
|
||||
|
||||
<P><I>Galotti, K. M., Reimer, R. L., & Drebus, D. W. (2001). Ways of knowing as learning styles: Learning MAGIC with a partner. Sex Roles, 44(7/8), 419-436.</I></P>
|
||||
|
||||
|
||||
</UL>
|
||||
@@ -1,39 +0,0 @@
|
||||
<P ALIGN=CENTER><B>Teachers</B></P>
|
||||
|
||||
<P>This page shows the list of people who are assigned to be
|
||||
"teachers" in this course (by the system administrator).
|
||||
</p>
|
||||
|
||||
<P>You can use this form to assign a role (title) to each person
|
||||
such as "Professor", "Tutor", "Assistant" and so on. These
|
||||
will appear on the site's course listing and also on the
|
||||
list of participants for your course. If you leave the
|
||||
role empty then the default word for teacher will be used
|
||||
(the one you set in the Course Settings page).
|
||||
</p>
|
||||
|
||||
<P>You can also order this list (to put the main teacher at the
|
||||
top, for example). Simply select numbers from the menus
|
||||
in the "Order" column. After pressing "Save changes" you will
|
||||
see the new order.
|
||||
</p>
|
||||
|
||||
<P>A special case occurs if you use select "Hide"
|
||||
for a teacher. In this case, the teacher will
|
||||
NOT BE SHOWN on the course listings or the list of
|
||||
participants. They will be "hidden" from students
|
||||
(unless they post messages to the forums etc).
|
||||
</p>
|
||||
|
||||
<p>You can also choose whether a teacher should have editing rights
|
||||
on the course. Non-editing teachers could be thought of as course
|
||||
tutors. They are:
|
||||
<ol>
|
||||
<li>not able to change the structure of the course</li>
|
||||
<li>not able to enroll or unenroll students
|
||||
<li>able to grade</li>
|
||||
<li>able to facilitate within activities</li>
|
||||
</ol>
|
||||
When assigned to a group, they are only able to perform
|
||||
task 3 and 4 with that group.
|
||||
</p>
|
||||
@@ -1,144 +0,0 @@
|
||||
<P ALIGN=CENTER><B>Help on writing text</B></P>
|
||||
|
||||
Writing text in Moodle works pretty much the way you would expect, but you also have the ability to include "smilies", "URL addresses" and some HTML tags in your text.
|
||||
|
||||
<P><B>Smilies (emoticons)</B></P>
|
||||
<UL>
|
||||
<P>To embed these small icons in your text, just type the associated code. These codes themselves are like little pictures if you turn your head to the left when looking at them.</P>
|
||||
|
||||
<table border="1">
|
||||
<tr valign="top">
|
||||
<td>
|
||||
<table border="0" align="center" cellpadding="10">
|
||||
<tr>
|
||||
<td><img border="0" hspace="10" src="pix/s/smiley.gif" width="15" height="15"></td>
|
||||
<td>smile</td>
|
||||
<td><FONT FACE=Courier>:-)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img alt border="0" hspace="10" src="pix/s/biggrin.gif" width="15" height="15"></td>
|
||||
<td>big grin</td>
|
||||
<td><FONT FACE=Courier>:-D</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img alt border="0" hspace="10" src="pix/s/wink.gif" width="15" height="15"></td>
|
||||
<td>wink</td>
|
||||
<td><FONT FACE=Courier>;-)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img alt border="0" hspace="10" src="pix/s/mixed.gif" width="15" height="15"></td>
|
||||
<td>mixed</td>
|
||||
<td><FONT FACE=Courier>:-/</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img alt border="0" hspace="10" src="pix/s/thoughtful.gif" width="15" height="15"></td>
|
||||
<td>thoughtful</td>
|
||||
<td><FONT FACE=Courier>V-.</FONT></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img alt border="0" hspace="10" src="pix/s/tongueout.gif" width="15" height="15"></td>
|
||||
<td>tongue out</td>
|
||||
<td><FONT FACE=Courier>:-P</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img alt border="0" hspace="10" src="pix/s/cool.gif" width="15" height="15"></td>
|
||||
<td>cool</td>
|
||||
<td><FONT FACE=Courier>B-)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img alt border="0" hspace="10" src="pix/s/approve.gif" width="15" height="15"></td>
|
||||
<td>approve</td>
|
||||
<td><FONT FACE=Courier>^-)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img alt border="0" hspace="10" src="pix/s/wideeyes.gif" width="15" height="15"></td>
|
||||
<td>wide eyes</td>
|
||||
<td><FONT FACE=Courier>8-)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img alt border="0" hspace="10" src="pix/s/surprise.gif" width="15" height="15"></td>
|
||||
<td>surprise</td>
|
||||
<td><FONT FACE=Courier>8-o</td>
|
||||
</tr>
|
||||
</table>
|
||||
</td>
|
||||
<td>
|
||||
<table border="0" align="center" cellpadding="10">
|
||||
<tr>
|
||||
<td><img alt border="0" hspace="10" src="pix/s/sad.gif" width="15" height="15"></td>
|
||||
<td>sad</td>
|
||||
<td><FONT FACE=Courier>:-(</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img alt border="0" hspace="10" src="pix/s/shy.gif" width="15" height="15"></td>
|
||||
<td>shy</td>
|
||||
<td><FONT FACE=Courier>8-.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img alt border="0" hspace="10" src="pix/s/blush.gif" width="15" height="15"></td>
|
||||
<td>blush</td>
|
||||
<td><FONT FACE=Courier>:-I</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img alt border="0" hspace="10" src="pix/s/kiss.gif" width="15" height="15"></td>
|
||||
<td>kisses</td>
|
||||
<td><FONT FACE=Courier>:-X</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img alt border="0" hspace="10" src="pix/s/clown.gif" width="15" height="15"></td>
|
||||
<td>clown</td>
|
||||
<td><FONT FACE=Courier>:o)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img alt border="0" hspace="10" src="pix/s/blackeye.gif" width="15" height="15"></td>
|
||||
<td>black eye</td>
|
||||
<td><FONT FACE=Courier>P-|</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img alt border="0" hspace="10" src="pix/s/angry.gif" width="15" height="15"></td>
|
||||
<td>angry</td>
|
||||
<td><FONT FACE=Courier>8-[</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img alt border="0" hspace="10" src="pix/s/dead.gif" width="15" height="15"></td>
|
||||
<td>dead</td>
|
||||
<td><FONT FACE=Courier>xx-P</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img alt border="0" hspace="10" src="pix/s/sleepy.gif" width="15" height="15"></td>
|
||||
<td>sleepy</td>
|
||||
<td><FONT FACE=Courier>|-.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img alt border="0" hspace="10" src="pix/s/evil.gif" width="15" height="15"></td>
|
||||
<td>evil</td>
|
||||
<td><FONT FACE=Courier>}-]</td>
|
||||
</tr>
|
||||
</table>
|
||||
</table>
|
||||
|
||||
</UL>
|
||||
|
||||
<P><B>URLs</B></P>
|
||||
<UL>
|
||||
<P>Any "word" starting with <B>www.</B> or <B>http://</B> will automatically be turned into a clickable link.
|
||||
<P>For example: <A HREF="http://www.yahoo.com">www.yahoo.com</A> or <A HREF="http://curtin.edu">http://curtin.edu</A>
|
||||
</UL>
|
||||
|
||||
<P><B>HTML tags</B></P>
|
||||
<UL>
|
||||
<P>You can use a limited subset of HTML tags to add emphasis to your texts.
|
||||
<TABLE BORDER=0 CELLPADDING=5 CELLSPACING=5>
|
||||
<TR><TH>HTML tags<TH>Produces</TR>
|
||||
<TR><TD><B> bold </B> <TD> <B>bold text</B> </TR>
|
||||
<TR><TD><I> italic </I> <TD> <I>italic text</I> </TR>
|
||||
<TR><TD><U> underline </U> <TD> <U>underlined text</U> </TR>
|
||||
<TR><TD><FONT SIZE=1> small </FONT> <TD> <FONT SIZE=1>small</FONT> </TR>
|
||||
<TR><TD><FONT SIZE=4> large </FONT> <TD> <FONT SIZE=4>large</FONT> </TR>
|
||||
<TR><TD><FONT COLOR=green> example </FONT> <TD> <FONT color=green>example</FONT> </TR>
|
||||
<TR><TD valign=top><UL><LI>one <LI>two </UL> <TD valign=top> <UL><LI>one<LI>two</UL> </TR>
|
||||
<TR><TD><HR><TD> <HR> </TR>
|
||||
</TABLE>
|
||||
</UL>
|
||||
|
||||
|
||||
@@ -1,84 +0,0 @@
|
||||
<P ALIGN=CENTER><B>Formatting text</B></P>
|
||||
|
||||
<P>When writing text in Moodle there are several formats you can choose
|
||||
to produce your text, depending on your expertise and the type of browser
|
||||
you are using.
|
||||
|
||||
<P><B>Usually you can just leave this setting to the default value and things
|
||||
should work as you expect</B>.
|
||||
|
||||
<P><B>1. Moodle auto-format</B></P>
|
||||
|
||||
<UL>
|
||||
<P>This format is best for when you are using normal web forms for entry
|
||||
(instead of the Richtext HTML editor). Just type text normally, as if you
|
||||
were sending an email.
|
||||
|
||||
<P>When you save your text, Moodle will do a number of things to automatically
|
||||
format your text for you.
|
||||
<P>For example, URLs such as
|
||||
<A HREF="http://yahoo.com/">http://yahoo.com</A> or even
|
||||
<A HREF="http://www.yahoo.com/">www.yahoo.com</A> will be turned into links.
|
||||
<P>Your line breaks will be retained, and blank lines will start new paragraphs.
|
||||
<P>Smiley characters such as :-) will automatically become their graphical equivalents.
|
||||
<P>You can even embed HTML code if you want to and it will be retained.
|
||||
<p align=right><a href="help.php?file=text.html">More info about Moodle auto-formatting</a></p>
|
||||
</UL>
|
||||
|
||||
|
||||
<P><B>2. HTML format</B></P>
|
||||
|
||||
<UL>
|
||||
<P>This format assumes the text is pure HTML. If you are using the
|
||||
HTML editor to edit text then this is the default format - all
|
||||
the commands in the toolbar are producing HTML for you.
|
||||
|
||||
<P>Even if you are not using the Richtext HTML editor, you can use HTML code
|
||||
in your text and it should come out exactly as you intended.
|
||||
|
||||
<P>Unlike the Moodle auto-format, no automatic formatting is performed.
|
||||
<p align=right><a href="help.php?file=html.html">More info about HTML in Moodle</a></p>
|
||||
<p align=right><a href="help.php?file=richtext.html">More info about the Richtext HTML editor</a></p>
|
||||
</UL>
|
||||
|
||||
|
||||
<P><B>3. Plain text format</B></P>
|
||||
|
||||
<UL>
|
||||
<P>This format is useful when you need to include lots of code
|
||||
or HTML that you want to be displayed exactly as you wrote it.
|
||||
|
||||
<P>It still translates spaces and new lines, but otherwise your
|
||||
text isn't touched.
|
||||
</UL>
|
||||
|
||||
|
||||
<P><B>4. Markdown text format</B></P>
|
||||
|
||||
<UL>
|
||||
<P>Markdown format tries to make it easy as possible to type
|
||||
well-formatted XHTML pages using nothing but text written
|
||||
more or less like you would write an email.</p>
|
||||
|
||||
<p>It's very good for writing clean text pages with some headings
|
||||
and some lists but without many links or images.</p>
|
||||
|
||||
<p align=right><a href="help.php?file=markdown.html">More info about the Markdown format</a></p>
|
||||
</UL>
|
||||
|
||||
|
||||
|
||||
<P><B>5. Wiki-like text format</B></P>
|
||||
<UL>
|
||||
<P>This format uses special codes for typing text known as the
|
||||
Wiki way. If you already know the Wiki way of creating pages
|
||||
and want to use it everywhere in Moodle, then this format is
|
||||
for you.</p>
|
||||
|
||||
<P>Note that this isn't a <b>real</b> Wiki, so you can't use CamelCase
|
||||
for creating new pages. It may also be slightly different from the
|
||||
Wiki module in Moodle, so be aware.</p>
|
||||
|
||||
<p align=right><a href="help.php?file=wiki.html">More info about the Wiki format</a></p>
|
||||
</UL>
|
||||
|
||||
@@ -1,33 +0,0 @@
|
||||
<p align="center"><b>Upload users</b></p>
|
||||
|
||||
<p>Firstly, note that <strong>it is usually not necessary to import users in bulk</strong> - to keep your own maintenance work down you should first explore forms of authentication that do not require manual maintenance, such as connecting to existing external databases or letting the users create their own accounts. See the Authentication section in the admin menus.</p>
|
||||
<p>If you are sure you want to import multiple user accounts from a text file, then you need to format your text file as follows:</p>
|
||||
|
||||
<ul>
|
||||
<li>Each line of the file contains one record</li>
|
||||
<li>Each record is a series of data separated by commas</li>
|
||||
<li>The first record of the file is special, and contains a list of fieldnames. This defines the format of the rest of the file.
|
||||
<blockquote>
|
||||
<p><strong>Required fieldnames:</strong> these fields must be included in the first record, and defined for each user</p>
|
||||
<p></p>
|
||||
<font color="#990000" face="Courier New, Courier, mono">username, password, firstname, lastname, email</font></p>
|
||||
</p>
|
||||
<p><strong>Default fieldnames:</strong> these are optional - if they are not included then the values are taken from the primary admin</p>
|
||||
<p><font color="#990000" face="Courier New, Courier, mono">institution, department, city, country, lang, timezone</font> </p>
|
||||
<p><strong>Optional fieldnames: </strong>all of these are completely optional. The course names are the "shortnames" of the courses - if present then the user will be enrolled as students in those courses. Group names must be associated to the corresponding courses, i.e. group1 to course1, etc.</p>
|
||||
<p> <font color="#990000" face="Courier New, Courier, mono">idnumber, icq, phone1, phone2, address, url, description, mailformat, maildisplay, htmleditor, autosubscribe, course1, course2, course3, course4, course5, group1, group2, group3, group4, group5</font></p>
|
||||
</blockquote>
|
||||
</li>
|
||||
<li>Commas within the data should be encoded as &#44 - the script will automatically decode these back to commas. </li>
|
||||
<li>For Boolean fields, use 0 for false and 1 for true. </li>
|
||||
<li>Note: If a user is already registered in the Moodle user database, this script will return the
|
||||
userid number (database index) for that user, and will enrol the user as a student in any of the
|
||||
specified courses WITHOUT updating the other specified data.</li>
|
||||
</ul>
|
||||
|
||||
|
||||
<p>Here is an example of a valid import file:</p>
|
||||
<p><font size="-1" face="Courier New, Courier, mono">username, password, firstname, lastname, email, lang, idnumber, maildisplay, course1, group1<br>
|
||||
jonest, verysecret, Tom, Jones, [email protected], en, 3663737, 1, Intro101, Section 1<br>
|
||||
reznort, somesecret, Trent, Reznor, [email protected], en_us, 6736733, 0, Advanced202, Section 3</font></p>
|
||||
|
||||
@@ -1,155 +0,0 @@
|
||||
<p align="center"><b>Writing pages using Wiki-like formatting</b></p>
|
||||
|
||||
<p>
|
||||
Wiki formatted pages provide a facility for marking up plain text with intuitive, human readable
|
||||
formatting that will be converted to XHTML when displayed. The big advantages are that you
|
||||
do not need to learn HTML to produce quite complex results, and that the text you write
|
||||
<em>looks</em> good to the eye even <em>before</em> conversion. It is a real alternative to
|
||||
saving Word files as HTML retaining the ability to edit the resource online.
|
||||
</p>
|
||||
|
||||
<p>You should enter basically plain text. There are a number of <em>special</em> characters you
|
||||
can add to insert formatting</p>
|
||||
|
||||
<h3>Block level formatting</h3>
|
||||
|
||||
<p>
|
||||
Paragraph blocks are separated by at least one blank line. To add special formatting to a paragraph
|
||||
add one of the following special characters in the first character of the first line of the block followed
|
||||
by a space...
|
||||
</p>
|
||||
|
||||
<table>
|
||||
<tr><th>Character</th><th>Block Type</th></tr>
|
||||
<tr><td>No character</td><td>Ordinary paragraph</td></tr>
|
||||
<tr><td>></td><td>Quotation</td></tr>
|
||||
<tr><td>Space</td><td>Preformatted Text (Monospaced)</td></tr>
|
||||
<tr><td>%</td><td>Preformatted <em>and</em> Wikki formatting is ignored</td></tr>
|
||||
<tr><td>!#</td><td>Heading - where # is 1-6, the heading level (1 is biggest)</td></tr>
|
||||
<tr><td>Q.</td><td>Question - styling info added to paragraph to improve question/answer presentation (in theme)</td></tr>
|
||||
<tr><td>A.</td><td>Answer - as above but answer</td></tr>
|
||||
</table>
|
||||
|
||||
<h3>List Formatting</h3>
|
||||
|
||||
<p>Simple lists can be constructed easily by placing a special character at the start of each line in the list followed by a space.
|
||||
The list is terminated by a blank line. Lists may be freely nested - and nested lists may change list type. Definition list
|
||||
definitions and text types may be freely intermixed to obtain the desired effect. The special characters
|
||||
are as follows...</p>
|
||||
|
||||
<table>
|
||||
<tr><th>Character</th><th>List item type</th></tr>
|
||||
<tr><td>*</td><td>Unordered List (bullet points)</td></tr>
|
||||
<tr><td>#</td><td>Ordered List (1,2,3 etc)</td></tr>
|
||||
<tr><td>:</td><td>Definition list, definition</td></tr>
|
||||
<tr><td>;</td><td>Definition list, text</td></tr>
|
||||
</table>
|
||||
|
||||
<p>Nested lists example:</p>
|
||||
<p><pre>
|
||||
* First Bullet
|
||||
* Second Bullet
|
||||
## nested line 1
|
||||
## nested line 2
|
||||
* Third Bullet
|
||||
</pre></p>
|
||||
<p>Produces:
|
||||
<ul><li>First Bullet</li>
|
||||
<li>Second Bullet</li>
|
||||
<ol><li>nested line 1</li>
|
||||
<li>nested line 2</li></ol>
|
||||
<li>Third Bullet
|
||||
</ul></p>
|
||||
|
||||
<h3>Inline formatting</h3>
|
||||
|
||||
<p>Inline formmating allows part of a line to be marked as having a particular style. The special
|
||||
characters used can appear anywhere on a line, but note that the formatting cannot
|
||||
cross lines. Codes are as follows...</p>
|
||||
|
||||
<table>
|
||||
<tr><th>Example</th><th>Example</th><th>Formatting</th></tr>
|
||||
<tr><td>*hello world*</td><td><strong>hello world</strong></td><td>Strong or Bold</td></tr>
|
||||
<tr><td>/hello world/</td><td><em>hello world</em></td><td>Emphasis or Italics</td></tr>
|
||||
<tr><td>+hello world+</td><td><ins>hello world</ins></td><td>Inserted text</td></tr>
|
||||
<tr><td>-hello world-</td><td><del>hello world</del></td><td>Deleted or Strikethrough</td></tr>
|
||||
<tr><td>hello ~world~</td><td>hello <sub>world</sub></td><td>Subscript</td></tr>
|
||||
<tr><td>hello ^world^</td><td>hello <sup>world</sup></td><td>Superscript</td></tr>
|
||||
<tr><td>"hello world"</td><td>“hello world”</td><td>Quoted</td></tr>
|
||||
<tr><td>%hello world%</td><td><code>hello world</code></td><td>Code or Monospaced</td></tr>
|
||||
<tr><td>@hello world@</td><td><cite>hello world</cite></td><td>Cite</td></tr>
|
||||
</table>
|
||||
|
||||
<h3>Acronyms</h3>
|
||||
|
||||
<p>Acronym tagging is acheived by placing the acronym in capital letters followed by the description
|
||||
is parenthesis. There must be no space between the acronym and the parenthesis. Example...</p>
|
||||
|
||||
<p>HTML(Hypertext Markup Language) <br /> <acronym title="Hypertext Markup Language">HTML</acronym></p>
|
||||
|
||||
<h3>Hyper Links</h3>
|
||||
|
||||
<p>Links can be placed in the text and are followed (with no spaces) by the text to be displayed in brackets. Example: </em>http://www.google.com/(Search Now)</em> will be converted to
|
||||
<a href="http://www.google.com/">Search Now</a>.</p>
|
||||
|
||||
<p>Mail links can be acheived the same way, e.g.,</p>
|
||||
<p>[email protected](Test User) will be converted to
|
||||
<a href="mailto:[email protected]">Test User</a></p>
|
||||
|
||||
<h3>Moodle Module Links</h3>
|
||||
|
||||
<p>If you know the Moodle id number (look for ?id=nn at the end of a module address) and
|
||||
the module name, you can link directly to that resource using the syntax:</p>
|
||||
|
||||
<p>ModuleName:nn(Description Text)</p>
|
||||
<p>eg, <em>resource:36(My New Page)</em> <em>forum:10(Jump to forum)</em></p>
|
||||
|
||||
<h3>Moodle Picture Links</h3>
|
||||
|
||||
<p>Inline graphics can be placed on wiki pages. You need to upload the graphic and note its path within the file upload area. The syntax is:</p>
|
||||
|
||||
<p>/<em>..path to file..</em>(alt text)</p>
|
||||
|
||||
<p>for example, /mypics/graphic.jpg(Staff picture)</p>
|
||||
|
||||
<h3>Moodle File Links</h3>
|
||||
|
||||
<p>Very like Picture Links (above), this feature enables links to previously uploaded
|
||||
files to be placed in a wiki page. The syntax is:</p>
|
||||
|
||||
<p><b>file:</b><em>..path to file</em>(link text)</p>
|
||||
|
||||
<p>for example, file:/pdfs/moodle.pdf(Information About Moodle)</p>
|
||||
|
||||
<h3>Automatic reformating</h3>
|
||||
|
||||
<p>Many commonly used functions are converted into their XHTML equivalents automatically.. The main ones are as
|
||||
follows...</p>
|
||||
|
||||
<ul>
|
||||
<li>HTTP links are converted into active links
|
||||
<li> ..., (R), (TM), (C), 1/4, 1/2, 3/4 are all converted to the correct character
|
||||
<li> digits x digits converts to correct multiply symbol
|
||||
<li>A line starting with at least four dashes is converted into a horizontal line
|
||||
</ul>
|
||||
|
||||
<h3>Spelling Checker (Experimental)</h3>
|
||||
|
||||
<p>The wiki formatter can be switched into a spell checking mode. Place the following on
|
||||
a line by itself in the text. Everything after this will be checked...
|
||||
|
||||
<pre>
|
||||
!SPELL:language_code:language_variant
|
||||
|
||||
Examples:
|
||||
!SPELL:en:british
|
||||
!SPELL:sp
|
||||
</pre>
|
||||
|
||||
<p>"language_code" should be replaced by the appropriate code (e.g., EN, FR etc), "language_variant" (along with the colon) is optional and can be one of "american", "british", or "canadian" if the language code is EN.</p>
|
||||
|
||||
<p>When displayed any unknown words are highlighted and you can see suggestions by holding the mouse over
|
||||
the word</p>
|
||||
|
||||
<p><em>NOTE: spelling uses the <strong>pspell</strong> libraries. These and the required dictionaries must be present on your server for the spell checker to work. In particular the Windows platform is not supported.
|
||||
</em></p>
|
||||
@@ -1,22 +0,0 @@
|
||||
<P ALIGN=CENTER><B>Writing</B></P>
|
||||
|
||||
<P>When writing text for others to read, try and write directly to your audience.</P>
|
||||
|
||||
<P>Explain your ideas as clearly and simply as you can to help avoid misunderstandings.
|
||||
One thing you can do is to avoid long words when a short one will do.</P>
|
||||
|
||||
<P>In the forums it will really help to keep your whole posts short and on-topic.
|
||||
Instead of one long rambling post that makes many different points, it may be
|
||||
better to write several shorter ones (they may even belong in separate forums).
|
||||
|
||||
<P>Re-edit your text as much as necessary until you get it right.
|
||||
Even in forum posts you have <?PHP echo ($CFG->maxeditingtime/60) ?> minutes
|
||||
after you've posted it to go back and improve it if necessary.</P>
|
||||
|
||||
<P>When replying to others, try and think of interesting questions you
|
||||
can ask them. This will help both you and the other person think (and learn!)
|
||||
about the subject you are discussing.</P>
|
||||
|
||||
|
||||
<p align=right><a href="help.php?file=questions.html">More info about asking questions</a></p>
|
||||
<p align=right><a href="help.php?file=reading.html">More info about reading</a></p>
|
||||
Reference in New Issue
Block a user