Skip to content
Browse files

New translated files

  • Loading branch information...
1 parent 0881130 commit 3c99a66aa90127a6171e20d724f9dbb903cc961c martignoni committed
Showing with 523 additions and 0 deletions.
  1. +48 −0 lang/fr/docs/README.txt
  2. +32 −0 lang/fr/docs/files.php
  3. +425 −0 lang/fr/docs/install.html
  4. +18 −0 lang/fr/docs/module_files.txt
48 lang/fr/docs/README.txt
@@ -0,0 +1,48 @@
+Moodle documentation
+If you want to translate this documentation into another language,
+I would suggest that you:
+ 1) don't include English versions of the files in this directory
+ because they will be used automatically anyway if it is missing
+ from your language pack.
+ 2) translate them in this order (starting with the important ones):
+ |-------------------
+ |
+ | - files.php
+ | - install.html
+ | - installamp.html
+ | - upgrade.html
+ | - faq.html
+ |
+ | -----------------
+ |
+ | - teacher.html
+ | - module_files.txt
+ |
+ | -----------------
+ |
+ | - intro.html
+ | - features.html
+ | - release.html
+ |
+ | -----------------
+ |
+ | - developer.html
+ | - cvs.html
+ | - future.html
+ |
+ | -----------------
+ |
+ | - license.html
+ |
+ |-------------------
+ 3) Please don't translate credits.html at all - it changes too much.
32 lang/fr/docs/files.php
@@ -0,0 +1,32 @@
+<?php // $Id$
+ // Names of the documentation files
+ // Files with a definition "-" are treated as spacers
+ // French translation 2003/10/08 13:22 Mina
+$string['-about'] = "Ë propos de Moodle";
+$string['intro.html'] = "Introduction";
+$string['background.html'] = "Contexte";
+$string['philosophy.html'] = "Philosophie";
+$string['licence.html'] = "Licence";
+$string['features.html'] = "FonctionnalitŽs";
+$string['release.html'] = "NouveautŽs";
+$string['future.html'] = "Futur";
+$string['credits.html'] = "Remerciements";
+$string['-installation'] = "Administration";
+$string['install.html'] = "Installation";
+$string['faq.html'] = "FAQ d'installation";
+$string['installamp.html'] = "Apache, MySQL, PHP";
+$string['upgrade.html'] = "Mise ˆ jour";
+$string['-usage'] = "Utilisation de Moodle";
+$string['teacher.html'] = "Manuel de l'enseignant";
+$string['other.html'] = "Autre documentation";
+$string['-development'] = "DŽveloppement";
+$string['developer.html'] = "Manuel du dŽveloppeur";
+$string['coding.html'] = "Guide se programmation";
+$string['cvs.html'] = "Utilisation de CVS";
425 lang/fr/docs/install.html
@@ -0,0 +1,425 @@
+<!-- Ce fichier est en cours de traduction. Il sera mis ý jour petit ý petit -->
+<title>Documentation Moodle : Installation</title>
+<link rel="stylesheet" href="docstyles.css" type="TEXT/CSS">
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+<body bgcolor="#FFFFFF">
+<h1>Installation de Moodle</h1>
+ <p>Ce document explique comment installer Moodle pour la premiËre fois. Certaines Ètapes sont
+ dÈcrites en dÈtails, afin de couvrir la grande variÈtÈ des petites diffÈrences entre les
+ diffÈrent serveurs web. C'est pourquoi ce document vous semblera peut-Ítre long et compliquÈ.
+ Ne vous laissez pas dÈcourager pour autant - la mise en place de Moodle est d'habitude
+ une affaire de minutes !</p>
+ <p>Prenez le temps d'Ètudier attentivement ces instruction - cela vous fera gagner du temps
+ pour plus tard.</p>
+ <p>Voici les diffÈrentes sections de ce document :</p>
+ <ol>
+ <li><a href="#requirements">Logiciels et rÈglages nÈcessaires</a></li>
+ <li><a href="#downloading">TÈlÈchargement</a></li>
+ <li><a href="#site">Structure du site</a></li>
+ <li><a href="#data">CrÈer un rÈpertoire de donnÈes</a></li>
+ <li><a href="#database">CrÈer une base de donnÈes</a></li>
+ <li><a href="#webserver">VÈrifier les rÈglages de votre serveur web</a></li>
+ <li><a href="#config">Modifier config.php</a></li>
+ <li><a href="#admin">Visiter la page d'administration</a></li>
+ <li><a href="#cron">Mettre en place un cron</a></li>
+ <li><a href="#course">CrÈer un nouveau cours</a></li>
+ </ol>
+ <p>&nbsp;</p>
+<h3 class="sectionheading"><a name="requirements"></a>1. Logiciels et rÈglages nÈcessaires</h3>
+<!-- Le reste doit encore Ítre traduit -->
+ <p>Moodle is primarily developed in Linux using Apache, MySQL and PHP (also
+ sometimes known as the LAMP platform), but is also regularly tested with PostgreSQL
+ and on Windows XP, Mac OS X and Netware 6 operating systems</p>
+ <p>The requirements for Moodle are as follows:</p>
+ <ol>
+ <li>Web server software. Most people use <a href="" target="_blank">Apache</a>,
+ but Moodle should work fine under any web server that supports PHP, such
+ as IIS on Windows platforms.</li>
+ <li><a href="" target="_blank">PHP</a> scripting language (version 4.1.0
+ or later), with the following settings:
+ <ul>
+ <li><a href="" target="_blank">GD library</a>
+ turned ON, with support for JPG and PNG formats</li>
+ <li>zlib library turned ON (if you want to use backup/restore on Windows)</li>
+ <li>Sessions support turned ON</li>
+ <li>File uploading turned ON</li>
+ <li>Safe Mode must be turned OFF (see the forums on for problems
+ caused by Safe Mode)</li>
+ </ul>
+ </li>
+ <li>a working database server: <a href="" target="_blank">MySQL</a>
+ or <a href="" target="_blank">PostgreSQL</a> are
+ completely supported and recommended for use with Moodle 1.1. All other
+ databases will be supported fully in the next release.</li>
+ </ol>
+ <p>Most web hosts support all of this by default. If you are signed up with
+ one of the few webhosts that does not support these features ask them why,
+ and consider taking your business elsewhere.</p>
+ <p>If you want to run Moodle on your own computer and all this looks a bit daunting,
+ then please see our guide: <a href="">Installing
+ Apache, MySQL and PHP</a>. It provides some step-by-step instructions to install
+ all this on most popular platforms.</p>
+ <p>&nbsp;</p>
+<h3 class="sectionheading"><a name="downloading"></a>2. TÈlÈchargement</h3>
+ <p>There are two ways to get Moodle, as a compressed package and via CVS. These
+ are explained in detail on the download page: <a href="" target="_blank"></a></p>
+ <p>After downloading and unpacking the archive, or checking out the files via
+ CVS, you will be left with a directory called &quot;moodle&quot;, containing
+ a number of files and folders. </p>
+ <p>You can either place the whole folder in your web server documents directory,
+ in which case the site will be located at <b></b>,
+ or you can copy all the contents straight into the main web server documents
+ directory, in which case the site will be simply <b></b>.</p>
+<h3 class="sectionheading"><a name="site"></a>3. Structure du site</h3>
+ <p>Here is a quick summary of the contents of the Moodle folder, to help get
+ you oriented:</p>
+ <blockquote>
+ <p>config.php - the ONLY file you need to edit to get started<br>
+ version.php - defines the current version of Moodle code<br>
+ index.php - the front page of the site</p>
+ <ul>
+ <li>admin/ - code to administrate the whole server </li>
+ <li>auth/ - plugin modules to authenticate users </li>
+ <li>course/ - code to display and manage courses </li>
+ <li>doc/ - help documentation for Moodle (eg this page)</li>
+ <li>files/ - code to display and manage uploaded files</li>
+ <li>lang/ - texts in different languages, one directory per language </li>
+ <li>lib/ - libraries of core Moodle code </li>
+ <li>login/ - code to handle login and account creation </li>
+ <li>mod/ - all Moodle course modules</li>
+ <li>pix/ - generic site graphics</li>
+ <li>theme/ - theme packs/skins to change the look of the site.</li>
+ <li>user/ - code to display and manage users</li>
+ </ul>
+ <p>&nbsp;</p>
+ </blockquote>
+<h3 class="sectionheading"><a name="data"></a>4. CrÈer un rÈpertoire de donnÈes</h3>
+ <p>Moodle will also need some space on your hard disk to store uploaded files,
+ such as course documents and user pictures.</p>
+ <p>Create a directory for this purpose somewhere. For security, it's best that
+ this directory is NOT accessible directly via the web. The easiest way to do this
+ is to simply locate it OUTSIDE the web directory, otherwise protect it
+ by creating a file in the data directory called .htaccess, containing this line:
+ <blockquote>
+ <pre>deny from all</pre>
+ </blockquote>
+ <p>To make sure that Moodle can save uploaded files in this directory, check that
+ the web server software (eg Apache) has permission to write
+ to this directory. On Unix machines, this means setting the owner of the directory
+ to be something like &quot;nobody&quot; or &quot;apache&quot;.</p>
+ <p>On many shared hosting servers, you will probably need to restrict all file access
+ to your "group" (to prevent other webhost customers from looking at or changing your files),
+ but provide full read/write access to everyone else (which will allow the web server
+ to access your files). Speak to your server administrator if you are having
+ trouble setting this up securely.</p>
+<h3 class="sectionheading"><a name="database"></a>5. CrÈer une base de donnÈes</h3>
+ <p>You need to create an empty database (eg "moodle") in your database system
+ along with a special user (eg "moodleuser") that has access to that database
+ (and that database only). You could use the "root" user if you wanted to, but
+ this is not recommended for a production system: if hackers manage to discover
+ the password then your whole database system would be at risk, rather than
+ just one database.
+ <p>Example command lines for MySQL: </p>
+ <pre>
+ # mysql -u root -p
+ TO moodleuser@localhost IDENTIFIED BY 'yourpassword';
+ > quit
+ # mysqladmin -p reload
+ <p>Example command lines for PostgreSQL: </p>
+ <pre>
+ # su - postgres
+ > psql -c "create user moodleuser createdb;" template1
+ > psql -c "create database moodle;" -U moodleuser template1
+ > psql -c "alter user moodleuser nocreatedb;" template1
+ <p>(For MySQL I highly recommend the use of <a href="">phpMyAdmin</a>
+ to manage your databases - you can do all this via a web interface).</p>
+ <p>As of version 1.0.8, Moodle now supports table prefixes, and so can safely share
+ a database with tables from other applications.</p>
+<h3 class="sectionheading"><a name="webserver" id="webserver"></a>6. VÈrifier les rÈglages de votre serveur web</h3>
+ <p>Firstly, make sure that your web server is set up to use index.php as a default
+ page (perhaps in addition to index.html, default.htm and so on).</p>
+ <p>In Apache, this is done using a DirectoryIndex parameter in your httpd.conf
+ file. Mine usually looks like this:</p>
+ <blockquote>
+ <pre><strong>DirectoryIndex</strong> index.php index.html index.htm </pre>
+ </blockquote>
+ <p>Just make sure index.php is in the list (and preferably towards the start
+ of the list, for efficiency).</p>
+ <p>Secondly, <b>if you are using Apache 2</b>, then you should turn on the <i>AcceptPathInfo</i>
+ variable, which allows scripts to be passed arguments like http://server/file.php/arg1/arg2.
+ This is essential to allow relative links between your resources, and also
+ provides a performance boost for people using your Moodle web site. You can
+ turn this on by adding these lines to your httpd.conf file.</p>
+ <blockquote>
+ <pre><strong>AcceptPathInfo</strong> on </pre>
+ </blockquote>
+ <p>Thirdly, Moodle requires a number of PHP settings to be active for it to
+ work. <b>On most servers these will already be the default settings.</b>
+ However, some PHP servers (and some of the more recent PHP versions) may
+ have things set differently. These are defined in PHP's configuration
+ file (usually called php.ini):</p>
+ <blockquote>
+ <pre>magic_quotes_gpc = 1 (preferred but not necessary)
+magic_quotes_runtime = 0 (necessary)
+file_uploads = 1
+session.auto_start = 0
+session.bug_compat_warn = 0
+ </blockquote>
+ <p>If you don't have access to httpd.conf or php.ini on your server, or you
+ have Moodle on a server with other applications that require different settings,
+ then don't worry, you can still OVERRIDE all of the default settings.
+ <p>To do this, you need to create a file called <b>.htaccess</b> in Moodle's
+ main directory that contains definitions for these settings.
+ This only works on Apache servers and only when Overrides have been allowed.
+ <blockquote>
+ <pre>
+DirectoryIndex index.php index.html index.htm
+&lt;IfDefine APACHE2>
+ <b>AcceptPathInfo</b> on
+php_flag magic_quotes_gpc 1
+php_flag magic_quotes_runtime 0
+php_flag file_uploads 1
+php_flag session.auto_start 0
+php_flag session.bug_compat_warn 0</pre>
+ </blockquote>
+ <p>You can also do things like define the maximum size for uploaded files:
+ <blockquote>
+ <pre>
+LimitRequestBody 0
+php_value upload_max_filesize 2M
+php_value post_max_size 2M
+ </pre>
+ </blockquote>
+ <p>The easiest thing to do is just copy the sample file from lib/htaccess
+ and edit it to suit your needs. It contains further instructions. For
+ example, in a Unix shell:
+ <blockquote>
+ <pre>cp lib/htaccess .htaccess</pre>
+ </blockquote>
+<h3 class="sectionheading"><a name="config"></a>7. Modifier config.php</h3>
+ <p>Now you can edit the configuration file, <strong>config.php</strong>, using a
+ text editor. This file is used by all other files in Moodle.</p>
+ <p>To start with, make a copy of <strong>config-dist.php</strong> and name it
+ config.php. We do this so that your config.php won't be overwritten in case
+ you upgrade Moodle later on. </p>
+ <p>Edit <strong>config.php</strong> to specify the database details that you
+ just defined (including a table prefix - notice that this is REQUIRED for
+ PostgreSQL), as well as the site address, file system directory and data directory.
+ The config file itself has detailed directions and examples.</p>
+ <p>Once you have done this the rest of the installation is via a web interface.
+ For the rest of this installation document we will assume your site is at:
+ <u></u></p>
+<h3 class="sectionheading"><a name="admin"></a>8. Visiter la page d'administration</h3>
+ <p>The admin page should now be working at: <u></u>.
+ If you try and access the front page of your site you'll be taken there automatically
+ anyway. The first time you access this admin page, you will be presented with
+ a GPL &quot;shrinkwrap&quot; agreement with which you must agree before you
+ can continue with the setup.</p>
+ <p>(Moodle will also try to set some cookies in your browser. If you have your
+ browser set up to let you choose to accept cookies, then you <b>must</b> accept
+ the Moodle cookies, or Moodle won't work properly.)
+ <p>Now Moodle will start setting up your database and creating tables to store
+ data. Firstly, the main database tables are created. You should see a number
+ of SQL statements followed by status messages (in green or red) that look
+ like this:</p>
+ <blockquote>
+ <p>CREATE TABLE course ( id int(10) unsigned NOT NULL auto_increment, category
+ int(10) unsigned NOT NULL default '0', password varchar(50) NOT NULL default
+ '', fullname varchar(254) NOT NULL default '', shortname varchar(15) NOT
+ NULL default '', summary text NOT NULL, format tinyint(4) NOT NULL default
+ '1', teacher varchar(100) NOT NULL default 'Teacher', startdate int(10)
+ unsigned NOT NULL default '0', enddate int(10) unsigned NOT NULL default
+ '0', timemodified int(10) unsigned NOT NULL default '0', PRIMARY KEY (id))
+ <p><font color="#006600">SUCCESS</font></p>
+ <p>...and so on, followed by: <font color="#006600">Main databases set up
+ successfully.</font> </p>
+ </blockquote>
+ <p>If you don't see these, then there must have been some problem with the database
+ or the configuration settings you defined in config.php. Check that PHP isn't
+ in a restricted "Safe Mode" (commercial web hosts sometimes have safe mode
+ turned on). You can check PHP variables by creating a little file containing
+ &lt? phpinfo() ?&gt and looking at it through a browser. Check all these and
+ try this page again.</p>
+ <p>Scroll down the very bottom of the page and press the &quot;Continue&quot;
+ link.</p>
+ <p>Next you will see a similar page that sets up all the tables required by
+ each Moodle module. As before, they should all be <font color="#006600">green</font>.</p>
+ <p>Scroll down the very bottom of the page and press the &quot;Continue&quot;
+ link.</p>
+ <p>You should now see a form where you can define more configuration variables
+ for your installation, such as the default language, SMTP hosts and so on.
+ Don't worry too much about getting everything right just now - you can always
+ come back and edit these later on using the admin interface. Scroll down to
+ the bottom and click &quot;Save changes&quot;.</p>
+ <p>If (and only if) you find yourself getting stuck on this page, unable to
+ continue, then your server probably has what I call the "buggy referrer" problem.
+ This is easy to fix: just turn off the &quot;secureforms&quot; setting, then
+ try to continue again.</p>
+ <p>The next page is a form where you can define parameters for your Moodle site
+ and the front page, such as the name, format, description and so on. Fill
+ this out (you can always come back and change these later) and then press
+ &quot;Save changes&quot;.</p>
+ <p>Finally, you will then be asked to create a top-level administration user
+ for future access to the admin pages. Fill out the details with your own name,
+ email etc and then click &quot;Save changes&quot;. Not all the fields are
+ required, but if you miss any important fields you'll be re-prompted for them.
+ </p>
+ <blockquote>
+ <blockquote>
+ <blockquote>
+ <blockquote>
+ <blockquote>
+ <p><strong>Make sure you remember the username and password you chose
+ for the administration user account, as they will be necessary to
+ access the administration page in future.</strong></p>
+ </blockquote>
+ </blockquote>
+ </blockquote>
+ </blockquote>
+ </blockquote>
+ <p>(If for any reason your install is interrupted, or there is a system error
+ of some kind that prevents you from logging in using the admin account, you
+ can usually log in using the default username of &quot;<strong>admin</strong>&quot;,
+ with password &quot;<strong>admin</strong>&quot;.)</p>
+ <p>Once successful, you will be returned to home page of your site. Note the
+ administration links that appear down the left hand side of the page (these
+ items also appear on a separate Admin page) - these items are only visible
+ to you because you are logged in as the admin user. All your further administration
+ of Moodle can now be done using this menu, such as:</p>
+ <ul>
+ <li>creating and deleting courses</li>
+ <li>creating and editing user accounts</li>
+ <li>administering teacher accounts</li>
+ <li>changing site-wide settings like themes etc</li>
+ </ul>
+<h3 class="sectionheading"><a name="cron"></a>9. Mettre en place un cron</h3>
+ <p>Some of Moodle's modules require continual checks to perform tasks. For example,
+ Moodle needs to check the discussion forums so it can mail out copies of posts
+ to people who have subscribed.</p>
+ <p>The script that does all this is located in the admin directory, and is called
+ cron.php. However, it can not run itself, so you need to set up a mechanism
+ where this script is run regularly (eg every five or ten minutes). This provides
+ a &quot;heartbeat&quot; so that the script can perform functions at periods
+ defined by each module.</p>
+ <p>Note that the machine performing the cron <b>does not need to be the same
+ machine that is running Moodle</b>. For example, if you have a limited web
+ hosting service that does not have cron, then you can might choose to run
+ cron on another server or on your home computer. All that matters is that
+ the cron.php file is called regularly. </p>
+ <p>The load of this script is not very high, so 5 minutes is usually reasonable,
+ but if you're worried about it you can reduce the time period to something
+ like 15 minutes or even 30 minutes. It's best not to make the time period
+ too long, as delaying mail-outs can slow down activity within the course.</p>
+ <p>First, test that the script works by running it directly from your browser:</p>
+ <blockquote>
+ <pre></pre>
+ </blockquote>
+ <p>Now, you need to set up some of way of running the script automatically and
+ regularly. </p>
+ <h4> Running the script from a command line</h4>
+ <p>You can call the page from the command line just as you did in the example
+ above. For example, you can use a Unix utility like 'wget':</p>
+ <blockquote>
+ <pre>wget -q -O /dev/null</pre>
+ </blockquote>
+ <p>Note in this example that the output is thrown away (to /dev/null).</p>
+ <p>The same thing using lynx:</p>
+ <blockquote>
+ <pre>lynx -dump &gt; /dev/null</pre>
+ </blockquote>
+ <p>Alternatively you could use a standalone version of PHP, compiled to be run
+ on the command line. The advantage with doing this is that your web server
+ logs aren't filled with constant requests to cron.php. The disadvantage is
+ that you need to have access to a command-line version of php.</p>
+ <blockquote>
+ <pre>/opt/bin/php /web/moodle/admin/cron.php
+(Windows) C:\apache\php\php.exe C:\apache\htdocs\moodle\admin\cron.php
+ </blockquote>
+ <h4>Automatically running the script every 5 minutes</h4>
+ <p><b>On Unix systems</b>: Use <b>cron</b>. Edit your cron settings from the commandline
+ using &quot;crontab -e&quot; and add a line like:</p>
+ <blockquote>
+ <pre>*/5 * * * * wget -q -O /dev/null</pre>
+ </blockquote>
+ <p>Usually, the "crontab" command will put you into the 'vi' editor. You enter
+ "insert mode" by pressing "i", then type in the line as above, then exit insert mode by
+ pressing ESC. You save and exit by typing ":wq", or quit with saving using ":q!" (without the quotes).</p>
+ <p><b>On Windows systems</b>: The simplest way is to use this little package <a href="" title="Click to download this package (150k)" target="_blank"></a>
+ which makes this whole thing very easy. You can also explore using the built-in
+ Windows feature for "Scheduled Tasks".</p>
+ <p>On web hosts: Your web-based control panel may have a web page that allows
+ you to set up this cron process. Ask your administrator for details on how
+ it works.</p>
+ <p></p>
+<h3 class="sectionheading"><a name="course"></a>10. CrÈer un nouveau cours</h3>
+ <p>Now that Moodle is running properly, you can create a course. </p>
+ <p>Select &quot;Create a new course&quot; from the Admin page (or the admin
+ links on the home page).</p>
+ <p>Fill out the form, paying special attention to the course format. You don't
+ have to worry about the details too much at this stage, as everything can
+ be changed later by the teacher.</p>
+ <p>Press &quot;Save changes&quot;, and you will be taken to a new form where
+ you can assign teachers to the course. You can only add existing user accounts
+ from this form - if you want to create a new teacher account then either ask
+ the teacher to create one for themselves (see the login page), or create one
+ for them using the &quot;Add a new user&quot; on the Admin page.</p>
+ <p>Once done, the course is ready to customise, and is accessible via the &quot;Courses&quot;
+ link on the home page.</p>
+ <p>See the &quot;<a href="./?file=teacher.html">Teacher Manual</a>&quot; for more details
+ on course-building.</p>
+<p align="CENTER"><font size="1"><a href="." target="_top">Moodle Documentation</a></font></p>
+<p align="CENTER"><font size="1">Version: $Id$</font></p>
18 lang/fr/docs/module_files.txt
@@ -0,0 +1,18 @@
+LES FICHIERS DE CE DOSSIER � moins que vous ne sachiez
+VRAIMENT ce que vous faites.
+La modification de ces fichiers pourrait rendre
+vos cours inutilisables.
+Ce dossier contient les fichiers d�pos� dans votre
+cours (dans les diff�rents modules), notamment par
+les �tudiants. Ce sont par exemple les devoirs
+rendus ou les annexes des messages des forums.
+Les noms des dossiers et des fichiers contenus dans
+ce dossier sont sp�cifiques. Ils sont automatiquement
+g�r�s par Moodle.

0 comments on commit 3c99a66

Please sign in to comment.
Something went wrong with that request. Please try again.