From: koenr Date: Sun, 6 Feb 2005 00:59:14 +0000 (+0000) Subject: moving to xhtml doctype X-Git-Url: http://git.mjollnir.org/gw?a=commitdiff_plain;h=9664b4ea0f158c5f89d78d69e975dc147f1159f2;p=moodle.git moving to xhtml doctype removed the
      construction and replaced it with a styl margin-left removed the body fixed white color and replaced it with a style in docstyles.css --- diff --git a/lang/en/docs/background.html b/lang/en/docs/background.html index 1e094bbddc..bbe2ef4b60 100644 --- a/lang/en/docs/background.html +++ b/lang/en/docs/background.html @@ -1,17 +1,18 @@ - - + + Moodle Docs: Background - - + + - +

      Background

      Moodle is an active and evolving work in progress. Development was started - by Martin + by Martin Dougiamas who continues to lead the project:

      I've been working on it, in some way or other, for several years. It @@ -72,8 +73,8 @@

      For more about our future plans for Moodle, see the Future roadmap.

      -

      Moodle Documentation

      -

      Version: $Id$

      +

      Moodle Documentation

      +

      Version: $Id$

      diff --git a/lang/en/docs/coding.html b/lang/en/docs/coding.html index eb9ed574d3..072c25a664 100755 --- a/lang/en/docs/coding.html +++ b/lang/en/docs/coding.html @@ -1,11 +1,12 @@ - - + + Moodle Docs: Coding Guidelines - - + + - +

      Moodle Coding Guidelines

      Any collaborative project needs consistency and stability to stay strong.

      @@ -201,7 +202,7 @@ GOOD: $assignments (for an array of objects)
    1. Most tables should have a timemodified field (INT10) which is updated with a current timestamp obtained with the PHP time() function.

    -

    Moodle Documentation

    -

    Version: $Id$

    +

    Moodle Documentation

    +

    Version: $Id$

    diff --git a/lang/en/docs/credits.html b/lang/en/docs/credits.html index 00047e267f..f1f9c69b1b 100644 --- a/lang/en/docs/credits.html +++ b/lang/en/docs/credits.html @@ -1,11 +1,12 @@ - - + + Moodle Docs: Credits - - + + - +

    Credits

    Overall guidance

    @@ -232,8 +233,8 @@ URL: http://moodle.org/download/mim

    -

    Moodle Documentation

    -

    Version: $Id$

    +

    Moodle Documentation

    +

    Version: $Id$

    diff --git a/lang/en/docs/cvs.html b/lang/en/docs/cvs.html index 9836f89eca..7f0074feb9 100644 --- a/lang/en/docs/cvs.html +++ b/lang/en/docs/cvs.html @@ -1,11 +1,13 @@ - - + + Moodle Docs: How to use CVS - - + + - +

    CVS for Moodle Developers

    CVS is the Concurrent Versioning System, a commonly-used way of managing source code for large software projects. CVS keeps all versions of all files so that nothing is ever lost, and usage by different people is tracked. It also provides ways to merge code if two or more people are working on the same file. All code and all versions are stored on a central server (in the case of Moodle, at Sourceforge).

    If you just want to download Moodle using CVS to run a site, then you probably don't need this page - just follow the simpler CVS instructions on the Moodle download page.

     

      -
    1. Joining the project as a developer
    2. -
    3. CVS Modules
    4. -
    5. Basic CVS Commands
      - 3.1. CVS on Unix
      - 3.2. CVS on Windows
    6. -
    7. Working with Branches
      - 4.1. Trunk development
      - 4.2. Stable branches for each release
      - 4.3. Feature branches for large changes
    8. +
    9. Joining the project as a developer
    10. +
    11. CVS Modules
    12. +
    13. Basic CVS Commands
      + 3.1. CVS on Unix
      + 3.2. CVS on Windows
    14. +
    15. Working with Branches
      + 4.1. Trunk development
      + 4.2. Stable branches for each release
      + 4.3. Feature branches for large changes
    -

     

    -

    1. Joining the project as a developer

    +
    +
    +

    1. Joining the project as a developer

    So, you've been offered CVS write access to help us develop and maintain Moodle! Welcome aboard!

    -

    To be able to write changes into Moodle's CVS archive, you first need to have an account at Sourceforge (registration is free and easy). For the examples on this page, let's assume your username is myusername and your password is mypassword. Take special note of the sourceforge instructions to create your CVS home directory - something you have to do with every new account to "enable" it for CVS. Basically you just have to use ssh to interactively connect to cvs.sourceforge.net.

    +

    To be able to write changes into Moodle's CVS archive, you first need to have an account at Sourceforge (registration is free and easy). For the examples on this page, let's assume your username is myusername and your password is mypassword. Take special note of the sourceforge instructions to create your CVS home directory - something you have to do with every new account to "enable" it for CVS. Basically you just have to use ssh to interactively connect to cvs.sourceforge.net.

    Once you have a working Sourceforge account, contact Martin Dougiamas so he can set up your account with write access to particular Moodle directories.

    + target="_top" href="http://moodle.org/user/view.php?id=1&course=1">Martin Dougiamas so he can set up your account with write access to particular Moodle directories.

    To avoid being prompted for mypassword every time you run a CVS command, follow the Sourceforge directions for using authorized keys. This step is optional, but it can make your CVS experience a lot nicer.

    With that done, you should have all the permissions you need, so you just need to set up your machine and download the current sources so you can start working on them.

     

    -

    2. CVS Modules

    +

    2. CVS Modules

    Within CVS, the word "modules" refers to separate collections of code. In Moodle we have the following modules within our repository:

    @@ -56,9 +59,9 @@

    Most people are working on the existing features in the moodle module, but many are also contributing new ideas in the contrib modules. Once code reaches a certain level of maturity in the contrib area, it can be migrated over into the main moodle tree.

     

    -

    3. Basic CVS Commands

    +

    3. Basic CVS Commands

    -

    3.1 CVS on Unix

    +

    3.1 CVS on Unix

    Sourceforge CVS uses ssh as a transport layer for security, so you will have to set a CVS_RSH environment variable in your Unix shell. It's best to put these commands in your .bashrc or .cshrc so you don't have to type it all the time:

    setenv CVS_RSH ssh (for csh, tcsh etc)
    @@ -86,12 +89,10 @@ update -dP

    Try 'cvs help' for more details ...

     

    -

    3.2 CVS on Windows

    +

    3.2 CVS on Windows

    First, you need to download a completely fresh copy of Moodle using your developer account.

    -
      -
        1. Get TortoiseCVS from tortoisecvs.org and install it, then reboot.
        2. Find or create a new folder somewhere where you want Moodle to be downloaded to.
        3. @@ -103,39 +104,29 @@ update -dP
        4. Press the button: "OK" and everything should be downloaded.
        -
      -

    A dialog box should show all the files being downloaded, and after a while you should have a complete copy of Moodle. After this first checkout, you can fetch the latest updated files from the CVS server:

    -
      -
        1. Right-mouse-click on your Moodle folder (or any file) and select "CVS Update".
        2. Sit back and watch the logs scroll by. Take note of conflicts that may occur if your local code has changes that conflict with the incoming versions - you will need to edit these files and resolve the conflicts manually.
        -
      -

    After modifying files (you will notice their icons change from green to red!), you can commit them back to the CVS server like this:

    -
      -
        1. Right-mouse-click on your Moodle folder (or any file) and select "CVS Commit...".
        2. In the dialog box, type a clear description of the changes you are committing.
        3. Click "OK". Your changes will be sent to the server.
        -
      -
    -

     

    +
    -

    4. Working with Branches

    +

    4. Working with Branches

    This diagram shows how the main moodle module branches into different versions over time.

    -

    +

    To see all the current tags and branches that are available, use this command on any old file (such as index.php in the top moodle directory):

    cvs status -v index.php

    Some tagging guidelines:

    @@ -144,10 +135,9 @@ update -dP
  1. Tags and branches should ALWAYS be applied to the entire module (all of Moodle). Don't tag individual files or directories.
  2. We don't allow renaming of tags because people may be relying on them, so get them right the first time!
  3. -


    -

    -

     

    -

    4.1 Trunk development

    +
    +
    +

    4.1 Trunk development

    The Trunk of CVS is the main development version of Moodle. In CVS it is also known as the HEAD, or default branch.

    Moodle developers try to keep this stable as possible, but as it usually contains new code it probably has bugs and small instabilities.

    @@ -155,7 +145,7 @@ update -dP

    A Beta package is also released at this point - it's for testers who don't use CVS but want to test the latest features and report bugs.

     

    -

    4.2 Stable branches for each release

    +

    4.2 Stable branches for each release

    As soon as the stable branch MOODLE_XX_STABLE is created, development efforts will fork into two streams for a while. Some people may continue working on new features in the trunk for the next release, but most developers should be concentrating on using the current STABLE branch and fixing bugs that are found in it.

    You can switch your local copy of Moodle to the STABLE version using the following command in Unix from the root directory:

    @@ -165,7 +155,6 @@ update -dP

    On Windows clients you should have a menu from which you can choose the branch.

    Once the new STABLE branch really stabilises, a release can be declared. Packages are created for distribution and the branch will be tagged (by Martin) with a tag named: MOODLE_XXX

    Periodically, bug fixes in the STABLE branch should be merged into the trunk so that they become available in future versions of Moodle. A floating tag called MOODLE_XX_MERGED will be maintained to keep track of the last merge. The procedure for such a merge is as follows:

    -
      1. Get out the very latest trunk version.

        @@ -186,18 +175,15 @@ update -dP
        cvs tag -RF MOODLE_13_MERGED
      -


    Finally, the values for $version in all the Moodle version.php files within the stable branch should not be updated at all if possible (except the last digit if necessary). The reason is that someone updating from a very stable version to the next very stable version could miss database upgrades that happened on the trunk.

    -

     

    -

    4.3 Feature branches for large changes

    +
    +

    4.3 Feature branches for large changes

    Occasionally, there may be a very large feature that needs to be checked in so several people can work on it, but it is too unstable to be included in the main development trunk.

    In these cases a short-term branch can be created to work on the feature, and then merged back into the main trunk as soon as possible. An example called MOODLE_14_WIDGET branch can be seen in the above diagram.

    If you need to do this for your new WIDGET feature, follow these steps:

    - -
      1. Discuss with other developers to make sure it's necessary!
      2. Make a new tag on the trunk (for all of moodle) called MOODLE_XX_WIDGET_PRE @@ -218,16 +204,13 @@ update -dP cvs commit
      -
    -
    -
    -

     

    -
    -
    + +
    +

    Good luck, be careful and have fun!

    -

     

    -

    Moodle Documentation

    -

    Version: $Id$

    +
    +

    Moodle Documentation

    +

    Version: $Id$

    diff --git a/lang/en/docs/developer.html b/lang/en/docs/developer.html index de819158ef..3331bfabeb 100644 --- a/lang/en/docs/developer.html +++ b/lang/en/docs/developer.html @@ -1,12 +1,13 @@ - - + + Moodle Docs: Developers Manual - - + + - +

    Developers Manual

    This document describes some of Moodle's design and how you can contribute.

    @@ -288,7 +289,7 @@

     

    -

    Moodle Documentation

    -

    Version: $Id$

    +

    Moodle Documentation

    +

    Version: $Id$

    diff --git a/lang/en/docs/docstyles.css b/lang/en/docs/docstyles.css index 319597299d..0af1b88cdb 100755 --- a/lang/en/docs/docstyles.css +++ b/lang/en/docs/docstyles.css @@ -1,5 +1,6 @@ body, td, th, li { font-family: "Trebuchet MS", Verdana, Arial, Helvetica, sans-serif; + background-color: #FFFFFF; } th { diff --git a/lang/en/docs/faq.html b/lang/en/docs/faq.html index a551525c73..9e7e60fb22 100644 --- a/lang/en/docs/faq.html +++ b/lang/en/docs/faq.html @@ -1,12 +1,13 @@ - - + + Moodle Docs: Frequently Asked Questions (FAQ) - - + + - +

    Frequently Asked Questions (FAQ)

    This page contains answers to some of the most frequently asked questions by people installing Moodle. If you have @@ -652,7 +653,7 @@ reduced functionality due to a mis-configuration in the firewall settings. has a firewall that is stripping referrer information from the browser. Here are - some instructions for fixing Norton firewall products.

    + some instructions for fixing Norton firewall products.

    @@ -781,11 +782,11 @@ This will be acceptable for the majority of users. -

    Moodle Documentation

    +

    Moodle Documentation

    -

    Version: $Id: faq.html,v 1.6 2003/03/30 13:54:28 +

    Version: $Id: faq.html,v 1.6 2003/03/30 13:54:28 diff --git a/lang/en/docs/features.html b/lang/en/docs/features.html index 9bd2063c01..0c0705fc2a 100644 --- a/lang/en/docs/features.html +++ b/lang/en/docs/features.html @@ -1,14 +1,15 @@ - - + + Moodle Docs: Background - + - + - +

    Features

    @@ -213,7 +214,7 @@

     

    -

    Moodle Documentation

    -

    Version: $Id$

    +

    Moodle Documentation

    +

    Version: $Id$

    diff --git a/lang/en/docs/future.html b/lang/en/docs/future.html index 967dc683ed..1a7baf9956 100644 --- a/lang/en/docs/future.html +++ b/lang/en/docs/future.html @@ -1,15 +1,16 @@ - - + + Moodle Docs: Future - + - + - +

    Future

    @@ -54,7 +55,7 @@

    This major release will contain some exciting developments in making Moodle more network-aware, with a natural evolution of Moodle's focus on collaboration. More on this here later.

    -

     

    -

    Moodle Documentation

    -

    Version: $Id$

    +

     

    +

    Moodle Documentation

    +

    Version: $Id$

    diff --git a/lang/en/docs/install.html b/lang/en/docs/install.html index 2aace410d6..2812e7cfcd 100644 --- a/lang/en/docs/install.html +++ b/lang/en/docs/install.html @@ -1,12 +1,13 @@ - - + + Moodle Docs: Basic Installation - + - + - +

    Installing Moodle

    -

    Dont panic!

    +

    Dont panic!

    This guide explains how to install Moodle for the first time. For some of these steps it goes into a lot of detail to try and cover the majority of possible web server setups, so this document may look long and complicated. Don't panic, once you know how to do it you can install Moodle in minutes!

    @@ -442,6 +443,6 @@ php_value post_max_size 2M

    If you like Moodle, please consider donating to help us cover our costs!

     

    -

    Moodle Documentation

    -

    Version: $Id$

    +

    Moodle Documentation

    +

    Version: $Id$

    diff --git a/lang/en/docs/installamp.html b/lang/en/docs/installamp.html index cabb457423..ad769e2a9c 100755 --- a/lang/en/docs/installamp.html +++ b/lang/en/docs/installamp.html @@ -1,12 +1,13 @@ - - + + Moodle Docs: Installing PHP and MySQL - - + + - +

    Installing Apache, MySQL and PHP

    Moodle is written in a scripting language called PHP, and stores most of its @@ -150,8 +151,8 @@

     

    -

    Moodle Documentation

    -

    Version: $Id$

    +

    Moodle Documentation

    +

    Version: $Id$

    \ No newline at end of file diff --git a/lang/en/docs/intro.html b/lang/en/docs/intro.html index bcc25f1763..29bb73d065 100644 --- a/lang/en/docs/intro.html +++ b/lang/en/docs/intro.html @@ -1,14 +1,15 @@ - - + + Moodle Docs: Introduction - + - + - +

    Introduction

    @@ -21,7 +22,7 @@ provided that you agree to: provide the source to others; not modify or remove the original license and copyrights, and apply this same license to any derivative work. Read the license for full - details and please contact the copyright + details and please contact the copyright holder directly if you have any questions.

    Moodle will run on any computer that can run @@ -37,7 +38,7 @@


    -

    Moodle Documentation

    -

    Version: $Id$

    +

    Moodle Documentation

    +

    Version: $Id$

    diff --git a/lang/en/docs/licence.html b/lang/en/docs/licence.html index 8aa51e21f8..db9becc65a 100644 --- a/lang/en/docs/licence.html +++ b/lang/en/docs/licence.html @@ -1,14 +1,15 @@ - - + + Moodle Docs: Copyright License - + - + - +

    Copyright License for Moodle

    @@ -26,14 +27,14 @@ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
    GNU General Public License for more details (attached below).

    -
    +

    		    GNU GENERAL PUBLIC LICENSE
    Version 2, June 1991

    Copyright (C) 1989, 1991 Free Software Foundation, Inc.
    59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
    Everyone is permitted to copy and distribute verbatim copies
    of this license document, but changing it is not allowed.

    Preamble

    The licenses for most software are designed to take away your
    freedom to share and change it. By contrast, the GNU General Public
    License is intended to guarantee your freedom to share and change free
    software--to make sure the software is free for all its users. This
    General Public License applies to most of the Free Software
    Foundation's software and to any other program whose authors commit to
    using it. (Some other Free Software Foundation software is covered by
    the GNU Library General Public License instead.) You can apply it to
    your programs, too.

    When we speak of free software, we are referring to freedom, not
    price. Our General Public Licenses are designed to make sure that you
    have the freedom to distribute copies of free software (and charge for
    this service if you wish), that you receive source code or can get it
    if you want it, that you can change the software or use pieces of it
    in new free programs; and that you know you can do these things.

    To protect your rights, we need to make restrictions that forbid
    anyone to deny you these rights or to ask you to surrender the rights.
    These restrictions translate to certain responsibilities for you if you
    distribute copies of the software, or if you modify it.

    For example, if you distribute copies of such a program, whether
    gratis or for a fee, you must give the recipients all the rights that
    you have. You must make sure that they, too, receive or can get the
    source code. And you must show them these terms so they know their
    rights.

    We protect your rights with two steps: (1) copyright the software, and
    (2) offer you this license which gives you legal permission to copy,
    distribute and/or modify the software.

    Also, for each author's protection and ours, we want to make certain
    that everyone understands that there is no warranty for this free
    software. If the software is modified by someone else and passed on, we
    want its recipients to know that what they have is not the original, so
    that any problems introduced by others will not reflect on the original
    authors' reputations.

    Finally, any free program is threatened constantly by software
    patents. We wish to avoid the danger that redistributors of a free
    program will individually obtain patent licenses, in effect making the
    program proprietary. To prevent this, we have made it clear that any
    patent must be licensed for everyone's free use or not licensed at all.

    The precise terms and conditions for copying, distribution and
    modification follow.

    GNU GENERAL PUBLIC LICENSE
    TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

    0. This License applies to any program or other work which contains
    a notice placed by the copyright holder saying it may be distributed
    under the terms of this General Public License. The "Program", below,
    refers to any such program or work, and a "work based on the Program"
    means either the Program or any derivative work under copyright law:
    that is to say, a work containing the Program or a portion of it,
    either verbatim or with modifications and/or translated into another
    language. (Hereinafter, translation is included without limitation in
    the term "modification".) Each licensee is addressed as "you".

    Activities other than copying, distribution and modification are not
    covered by this License; they are outside its scope. The act of
    running the Program is not restricted, and the output from the Program
    is covered only if its contents constitute a work based on the
    Program (independent of having been made by running the Program).
    Whether that is true depends on what the Program does.

    1. You may copy and distribute verbatim copies of the Program's
    source code as you receive it, in any medium, provided that you
    conspicuously and appropriately publish on each copy an appropriate
    copyright notice and disclaimer of warranty; keep intact all the
    notices that refer to this License and to the absence of any warranty;
    and give any other recipients of the Program a copy of this License
    along with the Program.

    You may charge a fee for the physical act of transferring a copy, and
    you may at your option offer warranty protection in exchange for a fee.

    2. You may modify your copy or copies of the Program or any portion
    of it, thus forming a work based on the Program, and copy and
    distribute such modifications or work under the terms of Section 1
    above, provided that you also meet all of these conditions:

    a) You must cause the modified files to carry prominent notices
    stating that you changed the files and the date of any change.

    b) You must cause any work that you distribute or publish, that in
    whole or in part contains or is derived from the Program or any
    part thereof, to be licensed as a whole at no charge to all third
    parties under the terms of this License.

    c) If the modified program normally reads commands interactively
    when run, you must cause it, when started running for such
    interactive use in the most ordinary way, to print or display an
    announcement including an appropriate copyright notice and a
    notice that there is no warranty (or else, saying that you provide
    a warranty) and that users may redistribute the program under
    these conditions, and telling the user how to view a copy of this
    License. (Exception: if the Program itself is interactive but
    does not normally print such an announcement, your work based on
    the Program is not required to print an announcement.)

    These requirements apply to the modified work as a whole. If
    identifiable sections of that work are not derived from the Program,
    and can be reasonably considered independent and separate works in
    themselves, then this License, and its terms, do not apply to those
    sections when you distribute them as separate works. But when you
    distribute the same sections as part of a whole which is a work based
    on the Program, the distribution of the whole must be on the terms of
    this License, whose permissions for other licensees extend to the
    entire whole, and thus to each and every part regardless of who wrote it.

    Thus, it is not the intent of this section to claim rights or contest
    your rights to work written entirely by you; rather, the intent is to
    exercise the right to control the distribution of derivative or
    collective works based on the Program.

    In addition, mere aggregation of another work not based on the Program
    with the Program (or with a work based on the Program) on a volume of
    a storage or distribution medium does not bring the other work under
    the scope of this License.

    3. You may copy and distribute the Program (or a work based on it,
    under Section 2) in object code or executable form under the terms of
    Sections 1 and 2 above provided that you also do one of the following:

    a) Accompany it with the complete corresponding machine-readable
    source code, which must be distributed under the terms of Sections
    1 and 2 above on a medium customarily used for software interchange; or,

    b) Accompany it with a written offer, valid for at least three
    years, to give any third party, for a charge no more than your
    cost of physically performing source distribution, a complete
    machine-readable copy of the corresponding source code, to be
    distributed under the terms of Sections 1 and 2 above on a medium
    customarily used for software interchange; or,

    c) Accompany it with the information you received as to the offer
    to distribute corresponding source code. (This alternative is
    allowed only for noncommercial distribution and only if you
    received the program in object code or executable form with such
    an offer, in accord with Subsection b above.)

    The source code for a work means the preferred form of the work for
    making modifications to it. For an executable work, complete source
    code means all the source code for all modules it contains, plus any
    associated interface definition files, plus the scripts used to
    control compilation and installation of the executable. However, as a
    special exception, the source code distributed need not include
    anything that is normally distributed (in either source or binary
    form) with the major components (compiler, kernel, and so on) of the
    operating system on which the executable runs, unless that component
    itself accompanies the executable.

    If distribution of executable or object code is made by offering
    access to copy from a designated place, then offering equivalent
    access to copy the source code from the same place counts as
    distribution of the source code, even though third parties are not
    compelled to copy the source along with the object code.

    4. You may not copy, modify, sublicense, or distribute the Program
    except as expressly provided under this License. Any attempt
    otherwise to copy, modify, sublicense or distribute the Program is
    void, and will automatically terminate your rights under this License.
    However, parties who have received copies, or rights, from you under
    this License will not have their licenses terminated so long as such
    parties remain in full compliance.

    5. You are not required to accept this License, since you have not
    signed it. However, nothing else grants you permission to modify or
    distribute the Program or its derivative works. These actions are
    prohibited by law if you do not accept this License. Therefore, by
    modifying or distributing the Program (or any work based on the
    Program), you indicate your acceptance of this License to do so, and
    all its terms and conditions for copying, distributing or modifying
    the Program or works based on it.

    6. Each time you redistribute the Program (or any work based on the
    Program), the recipient automatically receives a license from the
    original licensor to copy, distribute or modify the Program subject to
    these terms and conditions. You may not impose any further
    restrictions on the recipients' exercise of the rights granted herein.
    You are not responsible for enforcing compliance by third parties to
    this License.

    7. If, as a consequence of a court judgment or allegation of patent
    infringement or for any other reason (not limited to patent issues),
    conditions are imposed on you (whether by court order, agreement or
    otherwise) that contradict the conditions of this License, they do not
    excuse you from the conditions of this License. If you cannot
    distribute so as to satisfy simultaneously your obligations under this
    License and any other pertinent obligations, then as a consequence you
    may not distribute the Program at all. For example, if a patent
    license would not permit royalty-free redistribution of the Program by
    all those who receive copies directly or indirectly through you, then
    the only way you could satisfy both it and this License would be to
    refrain entirely from distribution of the Program.

    If any portion of this section is held invalid or unenforceable under
    any particular circumstance, the balance of the section is intended to
    apply and the section as a whole is intended to apply in other
    circumstances.

    It is not the purpose of this section to induce you to infringe any
    patents or other property right claims or to contest validity of any
    such claims; this section has the sole purpose of protecting the
    integrity of the free software distribution system, which is
    implemented by public license practices. Many people have made
    generous contributions to the wide range of software distributed
    through that system in reliance on consistent application of that
    system; it is up to the author/donor to decide if he or she is willing
    to distribute software through any other system and a licensee cannot
    impose that choice.

    This section is intended to make thoroughly clear what is believed to
    be a consequence of the rest of this License.

    8. If the distribution and/or use of the Program is restricted in
    certain countries either by patents or by copyrighted interfaces, the
    original copyright holder who places the Program under this License
    may add an explicit geographical distribution limitation excluding
    those countries, so that distribution is permitted only in or among
    countries not thus excluded. In such case, this License incorporates
    the limitation as if written in the body of this License.

    9. The Free Software Foundation may publish revised and/or new versions
    of the General Public License from time to time. Such new versions will
    be similar in spirit to the present version, but may differ in detail to
    address new problems or concerns.

    Each version is given a distinguishing version number. If the Program
    specifies a version number of this License which applies to it and "any
    later version", you have the option of following the terms and conditions
    either of that version or of any later version published by the Free
    Software Foundation. If the Program does not specify a version number of
    this License, you may choose any version ever published by the Free Software
    Foundation.

    10. If you wish to incorporate parts of the Program into other free
    programs whose distribution conditions are different, write to the author
    to ask for permission. For software which is copyrighted by the Free
    Software Foundation, write to the Free Software Foundation; we sometimes
    make exceptions for this. Our decision will be guided by the two goals
    of preserving the free status of all derivatives of our free software and
    of promoting the sharing and reuse of software generally.

    NO WARRANTY

    11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
    FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
    OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
    PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
    OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
    MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
    TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
    PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
    REPAIR OR CORRECTION.

    12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
    WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
    REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
    INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
    OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
    TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
    YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
    PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
    POSSIBILITY OF SUCH DAMAGES.

    END OF TERMS AND CONDITIONS
    -

    Moodle Documentation

    -

    Version: $Id$

    +

    Moodle Documentation

    +

    Version: $Id$

    diff --git a/lang/en/docs/other.html b/lang/en/docs/other.html index 064205f6f3..fb0bcebbf7 100755 --- a/lang/en/docs/other.html +++ b/lang/en/docs/other.html @@ -1,12 +1,13 @@ - - + + Moodle Docs: Frequently Asked Questions (FAQ) - - + + - +

    Other documentation

    Here are some links to other sources of Moodle documentation:

    Index of all Moodle diff --git a/lang/en/docs/philosophy.html b/lang/en/docs/philosophy.html index c1542ce9be..9ebebb4f48 100755 --- a/lang/en/docs/philosophy.html +++ b/lang/en/docs/philosophy.html @@ -1,14 +1,15 @@ - - + + Moodle Docs: Philosophy - + - + - +

    Philosophy

    @@ -46,7 +47,7 @@

    Obviously Moodle doesn't force this style of behaviour, but this is what it is best at supporting. In future, as the technical infrastructure of Moodle stabilises, further improvements in pedagogical support will be a major direction for Moodle development.


    -

    Moodle Documentation

    -

    Version: $Id$

    +

    Moodle Documentation

    +

    Version: $Id$

    diff --git a/lang/en/docs/release.html b/lang/en/docs/release.html index 6aec83a27a..c9863f5043 100644 --- a/lang/en/docs/release.html +++ b/lang/en/docs/release.html @@ -1,22 +1,25 @@ - - + + Moodle Docs: Current Release notes - + - + - +

    Latest Release notes

    Moodle 1.4.3 (17 December, 2004)

    @@ -24,7 +27,7 @@

    (Because this release contains important security fixes, we highly advise that sites using any previous version of Moodle upgrade to this version as soon as possible.)

    -
      +
      Some important security fixes
      @@ -115,7 +118,7 @@
      -
    +

     

    @@ -126,7 +129,7 @@

    (Because this release contains important security fixes, we highly advise that sites using any previous version of Moodle upgrade to this version as soon as possible.)

    -
      +
      Some important security fixes
      @@ -178,14 +181,11 @@
      -
    - -

     

    - +

    Moodle 1.4.1 (12th September, 2004)

    -
      +
      A few little new things
        @@ -222,14 +222,10 @@
      -
    - -

     

    - - +

    Moodle 1.4 (31st August, 2004)

    - - -

     

    -


    -

    +
    +
    Finally, don't forget to look at some of the many optional and innovative modules under development. +
    +
    +
    +
    If you experience any bugs in this release, please report them moodle.org/bugs so we can fix them in the next release.
    +

    Old release information

    -

     

    -

    Moodle Documentation

    -

    Version: $Id$

    +
    +

    Moodle Documentation

    +

    Version: $Id$

    diff --git a/lang/en/docs/upgrade.html b/lang/en/docs/upgrade.html index d165c03aa0..a7104e6012 100644 --- a/lang/en/docs/upgrade.html +++ b/lang/en/docs/upgrade.html @@ -7,7 +7,7 @@ - +

    Upgrading Moodle