diff --git a/lang/sv/LAESMIG.txt b/lang/sv/LAESMIG.txt index 3beb1529bdd..501213ae9fe 100644 --- a/lang/sv/LAESMIG.txt +++ b/lang/sv/LAESMIG.txt @@ -1,3 +1,9 @@ +Log för redigering och komplettering av språkpaketet för svenska i Moodle +version 4.0 2004-03-03 +Anders Berggren anders@ikt-pedagogen.se +Alla strängar i programfilerna fr o m 2004-02-27 är översatta. Några enstaka hjälpfiler är fortfarande på engelska. + + Log för redigering och komplettering av språkpaketet för svenska i Moodle version 3.0 2003-12-19 Anders Berggren anders@ikt-pedagogen.se diff --git a/lang/sv/assignment.php b/lang/sv/assignment.php index ee832749c6a..d4db3f78cb7 100644 --- a/lang/sv/assignment.php +++ b/lang/sv/assignment.php @@ -17,6 +17,7 @@ $string['description'] = "Beskrivning"; $string['duedate'] = "Stoppdatum/tid"; $string['duedateno'] = "Inget stoppdatum/tid"; $string['early'] = "\$a tidigt"; +$string['existingfiledeleted'] = "Befintlig fil har tagits bort: &a"; $string['failedupdatefeedback'] = "Uppdateringen av återkopplingen för det inskickade bidraget av användaren \$a fungerade inte"; $string['feedback'] = "Återkoppling"; $string['feedbackupdated'] = "Återkopplingen för inskickade bidrag för \$a användare har uppdaterats"; diff --git a/lang/sv/auth.php b/lang/sv/auth.php index 7b0ed8950fe..3cda6ec8d79 100644 --- a/lang/sv/auth.php +++ b/lang/sv/auth.php @@ -36,6 +36,7 @@ $string['auth_ldapextrafields'] = "Dessa f $string['auth_ldaptitle'] = "Använd en LDAP-server"; $string['auth_manualdescription'] = "Den här metoden gör det omöjligt för användare att skapa sina egna konton. Alla konton måste skapas manuellt av administratören."; $string['auth_manualtitle'] = "Endast manuellt skapade konton"; +$string['auth_multiplehosts'] = "Du kan ange flera värdar(t ex host1.com;host2.com;host3.com) "; $string['auth_nntpdescription'] = "Denna metod använder en NNTP-server för att kontrollera huruvida ett givet användarnamn och lösenord är giltiga."; $string['auth_nntphost'] = "NNTP-serverns adress. Använd IP-nummer, inte DNS-namn."; $string['auth_nntpport'] = "Serverport (119 är den vanligaste)"; diff --git a/lang/sv/chat.php b/lang/sv/chat.php index c4f7a06f471..f865e6bb160 100644 --- a/lang/sv/chat.php +++ b/lang/sv/chat.php @@ -12,6 +12,8 @@ $string['configrefreshroom'] = "Hur ofta ska direktsamtalet uppdateras? (I sekun $string['configrefreshuserlist'] = "Hur ofta ska listan på användare uppdateras? (i sekunder)"; $string['currentchats'] = "Aktiva sessioner för direktsamtal"; $string['currentusers'] = "Aktuella användare"; +$string['deletesession'] = "Ta bort denna session"; +$string['deletesessionsure'] = "Är Du säker på att Du vill ta bort denna session?"; $string['donotusechattime'] = "Visa inte några tider för direktsamtal"; $string['enterchat'] = "Klicka här för att gå in i direktsamtalet nu"; $string['errornousers'] = "Systemet hittade tinga användare"; diff --git a/lang/sv/choice.php b/lang/sv/choice.php index 43072c38696..317d37a38c1 100644 --- a/lang/sv/choice.php +++ b/lang/sv/choice.php @@ -8,6 +8,7 @@ $string['choicename'] = "Opinionsunders $string['choicetext'] = "Opinionsundersökningens text"; $string['modulename'] = "Opinionsundersökning"; $string['modulenameplural'] = "Opinionsundersökningar"; +$string['mustchooseone'] = "Du måste välja ett svar innan Du kan svara. Ingenting sparades."; $string['notanswered'] = "Inte ännu besvarad"; $string['publish'] = "Publicera resultaten"; $string['publishanonymous'] = "Publicera anonyma resultat, visa inte studenternas/elevernas/deltagarnas/de lärandes namn."; @@ -16,6 +17,7 @@ $string['publishnot'] = "Publicera inte resultaten f $string['responses'] = "Svar"; $string['responsesto'] = "Svar till \$a"; $string['savemychoice'] = "Spara min opinionsundersökning"; +$string['showunanswered'] = "Visa kolumn för icke besvarade"; $string['viewallresponses'] = "Visa \$a svar"; ?> diff --git a/lang/sv/dialogue.php b/lang/sv/dialogue.php index 006c151c07a..37cab1833b2 100644 --- a/lang/sv/dialogue.php +++ b/lang/sv/dialogue.php @@ -43,7 +43,8 @@ $string['onwrote'] = "P $string['onyouwrote'] = "På \$a skrev Du"; $string['open'] = "Öppna"; $string['openadialoguewith'] = "Öppna en dialog med "; -$string['opendialogue'] = "Öppen dialog"; +$string['opendialogue'] = "Öppna dialog"; +$string['opendialogueentries'] = "Öppna bidragen i dialogen "; $string['pane0'] = "Öppna en dialog"; $string['pane1'] = "\$a dialoger väntar på svar från Dig"; $string['pane1one'] = "1 dialog väntar på svar från Dig"; diff --git a/lang/sv/docs/background.html b/lang/sv/docs/background.html index 70865d1affb..8bb7f43444e 100644 --- a/lang/sv/docs/background.html +++ b/lang/sv/docs/background.html @@ -1,73 +1,73 @@ - - - - Moodle Docs: Background - - - - - -

Background

- -

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

-
-

I've been working on it, in some way or other, for several years. It - started in the 90's when I was webmaster at Curtin - University of Technology and a system administrator of their WebCT installation. - I encountered many frustrations with the WebCT beast and developed an itch - that needed scratching - there had to be a better way (no, not Blackboard - :-)

-

I also know a lot of people in schools and smaller institutions (and - some big ones!) who want to make better use of the Internet but don't know - where to start in the maze of technologies and pedagogies that are out there. - I've always hoped there would be a Free alternative that such people could - use to help them move their teaching skills into the online environment.

-

My strong beliefs in the unrealised possibilities of Internet-based education - led me to complete a Masters and then a PhD in Education, combining my former - career in Computer Science with newly constructed knowledge about the nature - of learning and collaboration. In particular, I am particularly influenced - by the epistemology of social constructionism - which not only treats learning - as a social activity, but focusses attention on the learning that occurs while - actively constructing artifacts (such as texts) for others to see or use. -

-

It is crucial to me that this software be easy to use - in fact it should - be as intuitive as possible.

-

I'm committed to continuing my work on Moodle and on keeping it Open - and Free. I have a deeply-held belief in the importance of unrestricted education - and empowered teaching, and Moodle is the main way I can contribute to the - realisation of these ideals.

-
-

A number of early prototypes were produced and discarded before he released - version 1.0 upon a largely unsuspecting world on August 20, 2002. This version - was targeted towards smaller, more intimate classes at University level, and - was the subject of research case studies that closely analysed the nature of - collaboration and reflection that occurred among these small groups of adult - participants. -

Since then there has been steady series of new releases adding new features, - better scalability and improved performance. -

As Moodle has spread and the community has grown, more input is being drawn - from a wider variety of people in different teaching situations. For example, - Moodle is now used not only in Universities, but in high schools, primary schools, - non-profit organisations, private companies, by independent teachers and even - homeschooling parents. A growing number of people from around the world are - contributing to Moodle in different ways - for more details see the Credits - page. -

An important feature of the Moodle project is the moodle.org - web site, which provides a central point for information, discussion and collaboration - among Moodle users, who include system administrators, teachers, researchers, - instructional designers and of course, developers. Like Moodle, this site is - always evolving to suit the needs of the community, and like Moodle it will - always be Free. -

In 2003, the company moodle.com - was launched to provide additional commercial support for those need it, as - well as managed hosting, consulting and other services. -

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

- -

Moodle Documentation

-

Version: $Id$

- - - + + + + Moodle Docs: Background + + + + + +

Background

+ +

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

+
+

I've been working on it, in some way or other, for several years. It + started in the 90's when I was webmaster at Curtin + University of Technology and a system administrator of their WebCT installation. + I encountered many frustrations with the WebCT beast and developed an itch + that needed scratching - there had to be a better way (no, not Blackboard + :-)

+

I also know a lot of people in schools and smaller institutions (and + some big ones!) who want to make better use of the Internet but don't know + where to start in the maze of technologies and pedagogies that are out there. + I've always hoped there would be a Free alternative that such people could + use to help them move their teaching skills into the online environment.

+

My strong beliefs in the unrealised possibilities of Internet-based education + led me to complete a Masters and then a PhD in Education, combining my former + career in Computer Science with newly constructed knowledge about the nature + of learning and collaboration. In particular, I am particularly influenced + by the epistemology of social constructionism - which not only treats learning + as a social activity, but focusses attention on the learning that occurs while + actively constructing artifacts (such as texts) for others to see or use. +

+

It is crucial to me that this software be easy to use - in fact it should + be as intuitive as possible.

+

I'm committed to continuing my work on Moodle and on keeping it Open + and Free. I have a deeply-held belief in the importance of unrestricted education + and empowered teaching, and Moodle is the main way I can contribute to the + realisation of these ideals.

+
+

A number of early prototypes were produced and discarded before he released + version 1.0 upon a largely unsuspecting world on August 20, 2002. This version + was targeted towards smaller, more intimate classes at University level, and + was the subject of research case studies that closely analysed the nature of + collaboration and reflection that occurred among these small groups of adult + participants. +

Since then there has been steady series of new releases adding new features, + better scalability and improved performance. +

As Moodle has spread and the community has grown, more input is being drawn + from a wider variety of people in different teaching situations. For example, + Moodle is now used not only in Universities, but in high schools, primary schools, + non-profit organisations, private companies, by independent teachers and even + homeschooling parents. A growing number of people from around the world are + contributing to Moodle in different ways - for more details see the Credits + page. +

An important feature of the Moodle project is the moodle.org + web site, which provides a central point for information, discussion and collaboration + among Moodle users, who include system administrators, teachers, researchers, + instructional designers and of course, developers. Like Moodle, this site is + always evolving to suit the needs of the community, and like Moodle it will + always be Free. +

In 2003, the company moodle.com + was launched to provide additional commercial support for those need it, as + well as managed hosting, consulting and other services. +

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

+ +

Moodle Documentation

+

Version: $Id$

+ + + diff --git a/lang/sv/docs/coding.html b/lang/sv/docs/coding.html index 8122605ba7c..6a9e3a6fd7a 100644 --- a/lang/sv/docs/coding.html +++ b/lang/sv/docs/coding.html @@ -1,165 +1,165 @@ - - - -Moodle Docs: Coding Guidelines - - - - - - - - - - - -

Moodle Coding Guidelines

- -

General Rules

- -
    -
  1. All files should use the .php extension.
    2. -
  2. All existing copyright notices must be retained. You can add your own if - necessary.
    3. -
  3. Each file should include the main config.php file.
    4. -
  4. Each file should check that the user is authenticated correctly, using require_login() - and isadmin(), isteacher(), iscreator() or isstudent().
    5. -
  5. All access to databases should use the functions in lib/datalib.php whenever - possible - this allows compatibility across a wide range of databases. You - should find that almost anything is possible using these functions. Any other - SQL statements should be: cross-platform; restricted to specific functions - within your code (usally a lib.php file); and clearly marked.
    6. -
  6. All strings should be translatable - create new texts in the "lang/en" - files and call them using get_string() or print_string().
    7. -
  7. All help files should be translatable - create new texts in the "en/help" - directory and call them using helpbutton().
    8. -
-

 

-

Coding Style

- -
    -
  1. Don't use tabs at all. Use consistent indenting with 4 spaces.
    2. -
  2. Braces must always be used for blocks of code (even if there is only one - line). Moodle uses this style: -

    if ($quiz->attempts) - {
    -     if (    $numattempts > - $quiz->attempts) - {
    -             error($strtoomanyattempts, - "view.php?id=$cm->id");
    -     }
    - }

    -
    3. -
  3. more to come here .... this document is not nearly finished yet!
    4. -
- - - -

 

- -
-

Moodle Documentation

- -

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

- - - - - - - + + + +Moodle Docs: Coding Guidelines + + + + + + + + + + + +

Moodle Coding Guidelines

+ +

General Rules

+ +
    +
  1. All files should use the .php extension.
    2. +
  2. All existing copyright notices must be retained. You can add your own if + necessary.
    3. +
  3. Each file should include the main config.php file.
    4. +
  4. Each file should check that the user is authenticated correctly, using require_login() + and isadmin(), isteacher(), iscreator() or isstudent().
    5. +
  5. All access to databases should use the functions in lib/datalib.php whenever + possible - this allows compatibility across a wide range of databases. You + should find that almost anything is possible using these functions. Any other + SQL statements should be: cross-platform; restricted to specific functions + within your code (usally a lib.php file); and clearly marked.
    6. +
  6. All strings should be translatable - create new texts in the "lang/en" + files and call them using get_string() or print_string().
    7. +
  7. All help files should be translatable - create new texts in the "en/help" + directory and call them using helpbutton().
    8. +
+

 

+

Coding Style

+ +
    +
  1. Don't use tabs at all. Use consistent indenting with 4 spaces.
    2. +
  2. Braces must always be used for blocks of code (even if there is only one + line). Moodle uses this style: +

    if ($quiz->attempts) + {
    +     if (    $numattempts > + $quiz->attempts) + {
    +             error($strtoomanyattempts, + "view.php?id=$cm->id");
    +     }
    + }

    +
    3. +
  3. more to come here .... this document is not nearly finished yet!
    4. +
+ + + +

 

+ +
+

Moodle Documentation

+ +

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

+ + + + + + + diff --git a/lang/sv/docs/credits.html b/lang/sv/docs/credits.html index b2faf25c98d..c73c9c34ae2 100644 --- a/lang/sv/docs/credits.html +++ b/lang/sv/docs/credits.html @@ -1,210 +1,210 @@ - - - - Moodle Docs: Credits - - - - - -

Credits

- -

Moodle the package is Copyright © 2001-2003, - Martin Dougiamas.  It is distributed under the - GNU Public License.

- - - -


Special thanks

- - - - -


Translations

-
-

Many thanks to every person who has contributed to translating Moodle into - different languages. Each translation takes many hours of work, as there are - over 1000 phrases to translate (plus all the help files!). Many of the languages - have more than one contributor, sometimes working together and sometimes they've - taken over the work from a previous person. -

Maintaining a list of everyone here is too difficult. For the most up-to-date - information see the Language - download page.

- -


Themes

-
-

Themes give Moodle sites some colour and life. Here are all the themes carried as part of the Moodle distribution, along with their authors: -

-
- - -


Other contributors

-
-

Thanks to all of you who have -

-

- -

Special thanks to those who have contributed substantial amounts of time to helping with Moodle code, including: -

-

- -

Also, thanks to those of you who have at some time contributed with constructive - discussions, support, testing and bits of code. This list is long and always - changing, but some names include (in the order I added them): -

-

I apologise if I've forgotten to include your name here - it's very difficult - to maintain! Mail me (Martin) and gently remind me! :-)

- -
- - -


Moodle libraries

- -
-

Some of Moodle's libraries were written by other people, and are being redistributed - as part of Moodle under their respective open source licenses that thankfully - allow us to do so. My thanks go out to the authors of all these excellent - products - without them Moodle would be missing important functionality. Copyright - information for each package is included below:

- -

ADOdb   -  lib/adodb
-

- -
-

Database abstraction library for MySQL, PostgreSQL, MSSQL, Oracle, -Interbase, Foxpro, Access, ADO, Sybase, DB2 and ODBC.

- -

Version: 3.60
- Copyright © 2000-2003 John Lim (jlim@natsoft.com.my)
- License: Dual LGPL and BSD-style
- URL:  http://php.weblogs.com/adodb
-

-
- -

Graph Class   -  lib/graphlib.php

- -
-

Class to draw line, point, bar, and area graphs, including numeric - x-axis and double y-axis.

- -

Version: 1.6.3 (with modifications)
- Copyright © 2000  Herman Veluwenkamp, hermanV@mindless.com
- License: LGPL
-

-
- - -

IP-Atlas  -   lib/ipatlas

- -
PHP scripts to show the location of an IP address on a map.
-
- Version: 1.0 (with modifications)
- Copyright © 2002   Ivan Kozik
- License: GNU GPL
- URL: http://www.xpenguin.com/ip-atlas.php
-
- - - -

PclZip  -   lib/pclzip

- -
Class to create, manage and unpack zip files.
-
- Version: 2.0 RC2
- Copyright © 2003  Vincent Blavet <vincent@phpconcept.net>
- License: GNU GPL
- URL: http://www.phpconcept.net
-
- - - -

PHP mailer   -  lib/class.phpmailer.php
-

- -
Class for sending email using either sendmail, PHP mail(), -or SMTP.  Methods are based upon the standard AspEmail(tm) classes.
-
- Version 1.71,
- Copyright © 2003 Brent R. Matzelle <bmatzelle@yahoo.com>
- License: LGPL
- URL:   http://phpmailer.sourceforge.net
-
-
- - - -

PHP Simple Excel File Generator  -   lib/psxlsgen.php

- -
Class to generate very simple MS Excel files (xls) -via PHP.
-
- Version: 0.3b
- Copyright © 2001  Erol Ozcan <eozcan@superonline.com>
- License: GNU LGPL
- URL: http://psxlsgen.sourceforge.net
-
- - - - - -

Richtext Editor  -   lib/rte

- -
HTML text editor for embedding in web pages.
-
- Version: 0.30 beta 1 (plus modifications)
- Copyright © 2001 Ramesys (Contracting Services) Limited <Austin.France@Ramesys.com> - License: GNU LGPL
- URL: http://richtext.sourceforge.net
-
- - -

SMTP class   -  lib/class.smtp.php
-

- -
Class that can be used to connect and communicate with - any SMTP server.
- It implements all the SMTP functions defined in RFC821 except TURN.
-
- Version: 03/26/2001
- Copyright © 2001  Chris Ryan <chris@greatbridge.com>
-
-
- - -

-
- -

Moodle Documentation

-

Version: $Id$

- - -
- - + + + + Moodle Docs: Credits + + + + + +

Credits

+ +

Moodle the package is Copyright © 2001-2003, + Martin Dougiamas.  It is distributed under the + GNU Public License.

+ + + +


Special thanks

+ + + + +


Translations

+
+

Many thanks to every person who has contributed to translating Moodle into + different languages. Each translation takes many hours of work, as there are + over 1000 phrases to translate (plus all the help files!). Many of the languages + have more than one contributor, sometimes working together and sometimes they've + taken over the work from a previous person. +

Maintaining a list of everyone here is too difficult. For the most up-to-date + information see the Language + download page.

+ +


Themes

+
+

Themes give Moodle sites some colour and life. Here are all the themes carried as part of the Moodle distribution, along with their authors: +

+
+ + +


Other contributors

+
+

Thanks to all of you who have +

+

+ +

Special thanks to those who have contributed substantial amounts of time to helping with Moodle code, including: +

+

+ +

Also, thanks to those of you who have at some time contributed with constructive + discussions, support, testing and bits of code. This list is long and always + changing, but some names include (in the order I added them): +

+

I apologise if I've forgotten to include your name here - it's very difficult + to maintain! Mail me (Martin) and gently remind me! :-)

+ +
+ + +


Moodle libraries

+ +
+

Some of Moodle's libraries were written by other people, and are being redistributed + as part of Moodle under their respective open source licenses that thankfully + allow us to do so. My thanks go out to the authors of all these excellent + products - without them Moodle would be missing important functionality. Copyright + information for each package is included below:

+ +

ADOdb   -  lib/adodb
+

+ +
+

Database abstraction library for MySQL, PostgreSQL, MSSQL, Oracle, +Interbase, Foxpro, Access, ADO, Sybase, DB2 and ODBC.

+ +

Version: 3.60
+ Copyright © 2000-2003 John Lim (jlim@natsoft.com.my)
+ License: Dual LGPL and BSD-style
+ URL:  http://php.weblogs.com/adodb
+

+
+ +

Graph Class   -  lib/graphlib.php

+ +
+

Class to draw line, point, bar, and area graphs, including numeric + x-axis and double y-axis.

+ +

Version: 1.6.3 (with modifications)
+ Copyright © 2000  Herman Veluwenkamp, hermanV@mindless.com
+ License: LGPL
+

+
+ + +

IP-Atlas  -   lib/ipatlas

+ +
PHP scripts to show the location of an IP address on a map.
+
+ Version: 1.0 (with modifications)
+ Copyright © 2002   Ivan Kozik
+ License: GNU GPL
+ URL: http://www.xpenguin.com/ip-atlas.php
+
+ + + +

PclZip  -   lib/pclzip

+ +
Class to create, manage and unpack zip files.
+
+ Version: 2.0 RC2
+ Copyright © 2003  Vincent Blavet <vincent@phpconcept.net>
+ License: GNU GPL
+ URL: http://www.phpconcept.net
+
+ + + +

PHP mailer   -  lib/class.phpmailer.php
+

+ +
Class for sending email using either sendmail, PHP mail(), +or SMTP.  Methods are based upon the standard AspEmail(tm) classes.
+
+ Version 1.71,
+ Copyright © 2003 Brent R. Matzelle <bmatzelle@yahoo.com>
+ License: LGPL
+ URL:   http://phpmailer.sourceforge.net
+
+
+ + + +

PHP Simple Excel File Generator  -   lib/psxlsgen.php

+ +
Class to generate very simple MS Excel files (xls) +via PHP.
+
+ Version: 0.3b
+ Copyright © 2001  Erol Ozcan <eozcan@superonline.com>
+ License: GNU LGPL
+ URL: http://psxlsgen.sourceforge.net
+
+ + + + + +

Richtext Editor  -   lib/rte

+ +
HTML text editor for embedding in web pages.
+
+ Version: 0.30 beta 1 (plus modifications)
+ Copyright © 2001 Ramesys (Contracting Services) Limited <Austin.France@Ramesys.com> + License: GNU LGPL
+ URL: http://richtext.sourceforge.net
+
+ + +

SMTP class   -  lib/class.smtp.php
+

+ +
Class that can be used to connect and communicate with + any SMTP server.
+ It implements all the SMTP functions defined in RFC821 except TURN.
+
+ Version: 03/26/2001
+ Copyright © 2001  Chris Ryan <chris@greatbridge.com>
+
+
+ + +

+
+ +

Moodle Documentation

+

Version: $Id$

+ + +
+ + diff --git a/lang/sv/docs/cvs.html b/lang/sv/docs/cvs.html index 2c07cc8d594..e9db85423c5 100644 --- a/lang/sv/docs/cvs.html +++ b/lang/sv/docs/cvs.html @@ -1,160 +1,160 @@ - - -Moodle Docs: How to use CVS - - - - - -

Using CVS to access and update Moodle source code

-
-

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

-

If you just want to access the current CVS version of Moodle with read-only access then - you don't need this page - just follow the simpler CVS instructions on the Moodle download page.

- -

To use Moodle's - CVS archive (as a developer - with write access), you first need to have an account - on Sourceforge. 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 give you 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. Below are instructions for Unix and Windows systems.

-

1. Using CVS on Unix

-
-

Sourceforge CVS uses ssh as a transport layer for security, so you will - have to set this CVS_RSH environment variable in your Unix shell:

-
- 
setenv CVS_RSH ssh (for csh, tcsh etc)
- 
export CVS_RSH=ssh (for sh, bash etc)
-
-

It's best to put this in your .bashrc or .cshrc so you don't have to type - it all the time. Then, check out Moodle using this (all one line):

-
- 
cvs -z3 -d:ext:myusername@cvs.moodle.sourceforge.net:/cvsroot/moodle co moodle
-
-

Don't try to do run this first CVS command into an existing moodle directory - - start fresh with a new directory.

-

Note that you will be prompted for mypassword - for each command unless you set up authorized - keys

-

Now, you should have a new 'moodle' directory. You can rename it and move - it around if you like. Go into it:

-
- 
cd moodle
-
-

All the latest Moodle files should be in there. You can now change files - in your copy. To compare your files against the main CVS copy on the server - use cvs diff, eg:

-
- 
cvs diff -c config-dist.php
-cvs diff -c lang
-
-

To fetch the latest updates from the server use:

-
- 
cvs update -dP
-
-

To copy your new files back to the server you would do something like: -

-
- 
cd lang/ca 
-cvs commit
-
-

You will be prompted to add some comments (depends on your default text - editor) ... add a meangingful comment and close the editor ... the files - will be sent to Sourceforge and stored. Done!

-

To save more time you can put default arguments into a file called .cvsrc - in your home directory. For example, mine contains:

-
- 
diff -c 
-update -dP
-
-

Try 'cvs help' for more details ...

-

 

-
-

2. Using 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. Right-mouse-click that folder and choose "CVS Checkout" - from the menu. You should see a dialog box.
-
- 4. Copy this text into the CVSROOT field (using your own username!):

-
- 
 :ext:myusername@cvs.moodle.sourceforge.net:/cvsroot/moodle
-
-


- 5. Press the button: "Fetch list...".
-
- 6. To the right of the button you should see a list of modules: choose - "moodle" from that list.
-
- 7. 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".
-

-
-

After modifying files (you will note they change from green top 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.
-

-
-
-

 

-

Good luck!

-

 

-
-

Moodle Documentation

-

Version: $Id$

- - + + +Moodle Docs: How to use CVS + + + + + +

Using CVS to access and update Moodle source code

+
+

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

+

If you just want to access the current CVS version of Moodle with read-only access then + you don't need this page - just follow the simpler CVS instructions on the Moodle download page.

+ +

To use Moodle's + CVS archive (as a developer + with write access), you first need to have an account + on Sourceforge. 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 give you 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. Below are instructions for Unix and Windows systems.

+

1. Using CVS on Unix

+
+

Sourceforge CVS uses ssh as a transport layer for security, so you will + have to set this CVS_RSH environment variable in your Unix shell:

+
+ 
setenv CVS_RSH ssh (for csh, tcsh etc)
+ 
export CVS_RSH=ssh (for sh, bash etc)
+
+

It's best to put this in your .bashrc or .cshrc so you don't have to type + it all the time. Then, check out Moodle using this (all one line):

+
+ 
cvs -z3 -d:ext:myusername@cvs.moodle.sourceforge.net:/cvsroot/moodle co moodle
+
+

Don't try to do run this first CVS command into an existing moodle directory + - start fresh with a new directory.

+

Note that you will be prompted for mypassword + for each command unless you set up authorized + keys

+

Now, you should have a new 'moodle' directory. You can rename it and move + it around if you like. Go into it:

+
+ 
cd moodle
+
+

All the latest Moodle files should be in there. You can now change files + in your copy. To compare your files against the main CVS copy on the server + use cvs diff, eg:

+
+ 
cvs diff -c config-dist.php
+cvs diff -c lang
+
+

To fetch the latest updates from the server use:

+
+ 
cvs update -dP
+
+

To copy your new files back to the server you would do something like: +

+
+ 
cd lang/ca 
+cvs commit
+
+

You will be prompted to add some comments (depends on your default text + editor) ... add a meangingful comment and close the editor ... the files + will be sent to Sourceforge and stored. Done!

+

To save more time you can put default arguments into a file called .cvsrc + in your home directory. For example, mine contains:

+
+ 
diff -c 
+update -dP
+
+

Try 'cvs help' for more details ...

+

 

+
+

2. Using 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. Right-mouse-click that folder and choose "CVS Checkout" + from the menu. You should see a dialog box.
+
+ 4. Copy this text into the CVSROOT field (using your own username!):

+
+ 
 :ext:myusername@cvs.moodle.sourceforge.net:/cvsroot/moodle
+
+


+ 5. Press the button: "Fetch list...".
+
+ 6. To the right of the button you should see a list of modules: choose + "moodle" from that list.
+
+ 7. 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".
+

+
+

After modifying files (you will note they change from green top 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.
+

+
+
+

 

+

Good luck!

+

 

+
+

Moodle Documentation

+

Version: $Id$

+ + diff --git a/lang/sv/docs/developer.html b/lang/sv/docs/developer.html index ffb2cc81de3..b313b60fad4 100644 --- a/lang/sv/docs/developer.html +++ b/lang/sv/docs/developer.html @@ -1,308 +1,308 @@ - - Moodle Docs: Developers Manual - - - - - - -

Developers Manual

-

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

-

It's a bit thin at the moment - better documentation will come eventually!

-

Sections in this document:

-
    -
  1. Moodle architecture
    2. -
  2. How you can contribute - -
    3. -
-

 

-

1. Moodle architecture

-
-

From a system administrator's perspective, Moodle has been designed according - to the following criteria:

-
    -
  1. Moodle should run on the widest variety of platforms
    -
    - The web application platform that runs on most platforms is PHP combined - with MySQL, and this is the environment that Moodle has been developed in - (on Linux, Windows, and Mac OS X). Moodle also uses the ADOdb library for - database abstraction, which means Moodle can use more - than ten different brands of database (unfortunately, though, it can - not yet set up tables in all these databases - - more on this later).
    -
    -
    2. -
  2. Moodle should be easy to install, learn and modify
    -
    - Early prototypes of Moodle (1999) were built using Zope - - an advanced object-oriented web application server. Unfortunately I found - that although the technology was pretty cool, it had a very steep learning - curve and was not very flexible in terms of system administration. The PHP - scripting language, on the other hand, is very easy to get into (especially - if you've done any programming using any other scripting language). Early - on I made the decision to avoid using a class-oriented design - again, to - keep it simple to understand for novices. Code reuse is instead achieved - by libraries of clearly-named functions and consistent layout of script - files. PHP is also easy to install (binaries are available for every platform) - and is widely available to the point that most web hosting services provide - it as standard.
    -
    -
    3. -
  3. It should be easy to upgrade from one version to the next
    -
    - Moodle knows what version it is (as well as the versions of all plug-in - modules) and a mechanism has been built-in so that Moodle can properly upgrade - itself to new versions (for example it can rename database tables or add - new fields). If using CVS in Unix for example, one can just do a "cvs - update -d" and then visit the site home page to complete an upgrade.
    -
    -
    4. -
  4. It should be modular to allow for growth
    -
    - Moodle has a number of features that are modular, including themes, activities, - interface languages, database schemas and course formats. This allows anyone - to add features to the main codebase or to even distribute them separately. - More on this below in the next section.
    -
    -
    5. -
  5. It should be able to be used in conjunction with other systems
    -
    - One thing Moodle does is keep all files for one course within a single, - normal directory on the server. This would allow a system administrator - to provide seamless forms of file-level access for each teacher, such as - Appletalk, SMB, NFS, FTP, WebDAV and so on. The authentication modules allow - Moodle to use LDAP, IMAP, POP3, NNTP and other databases as sources for - user information. Otherwise, there is work yet to do. Features planned for - Moodle in future versions include: import and export of Moodle data using - XML-based formats (including IMS and SCORM); and increased use of style - sheets for interface formatting (so that it can be integrated visually into - other web sites).
    6. -
-
-

 

-

2. How you can contribute

-
-

As mentioned above, Moodle has a number of features that are modular. Even - if you are not a programmer there are things you can change or help with.

-

Learning Activities

-
-

These are by far the most important modules, and reside in the 'mod' directory. - There are seven default modules: assignment, choice, forum, journal, quiz, - resource, and survey. Each module is in a separate subdirectory and consists - of the following mandatory elements (plus extra scripts unique to each module):

- -

The easiest way to start a new learning activity module is to use the template - in mod/newmodule_template.zip. - Unzip it and follow the README inside.

-

You might also like to post first in the Activities - modules forum on Using Moodle.

-

 

-
-

Themes

-
-

Themes (or skins) define the look of a site. A number of simple themes - are provided in the main distribution, but you may want to create your own - theme with your own colours, logo, styles and graphics.

-

Each theme is in a subdirectory of the "theme" directory, and - contains at least the following files:

- -

To create your own themes for current versions of Moodle:

-
    -
  1. Copy one of the existing theme folders to one with a new name. I recommend - starting with one of the standard themes.
    2. -
  2. Edit config.php and insert your own colours.
    3. -
  3. Edit styles.php and change your CSS styles.
    4. -
  4. Edit header.html and footer.html to add new logos, or change the layout. -
    5. -
-

Note that all these steps are optional - you can make a radically different - look to your site simply by editing the colours in config.php

-

Note also that Moodle upgrades may break themes slightly, so check - the release notes carefully if you are using a custom theme.

-

In particular, Moodle 2.0 will have a completely new display system, probably - based on XSL transformations of XML output from Moodle. It is likely that - the themes for this will be a completely different format, but the advantage - will be a much higher possible degree of customisation (including moving - elements around the page).

-

More discussion about this in the Themes - forum on Using Moodle. If you create a nice theme that you think others - might want to use, please post your zip file on the themes forum!
-

-
-

 

-

Languages

-
-

Moodle has been designed for internationalisation. Each 'string' or 'page' - of text that is displayed as part of the interface is drawn from a set of - language files. Each language is a subdirectory of the directory 'lang'. - The structure of the lang directory is as follows:

-

lang/en - directory containing all files for one language - (eg English)

- -

lang/en/help - contains whole help pages (for popup context-sensitive - help)

-
-

Main help pages are situated here, while help pages specific to each - module are located in subdirectories with the module's name.

-

You can insert a helpbutton in a page with the helpbutton function.

-

eg helpbutton("text", "Click here for help about text");

-

and for modules:

-

helpbutton("forumtypes", "Forum types", "forum");

-
-

Note that you can edit languages online, using the administration web tools - under "Check this language". This makes it easy to not to only - create new languages but to refine existing ones. If you are starting a - new language, please contact me, Martin - Dougiamas.

-

You might also like to post in the Languages - forum on Using Moodle.

-

If you are maintaining a language an ongoing basis, I can give you CVS - write access to the Moodle source code so that you can directly maintain - the files.

-
-


- Database Schemas

-
-

Given a working database with defined tables, the intentionally simple - SQL used in Moodle should work fine with a wide variety of database brands.

-

A problem exists with automatically creating new tables - in a database, which is what Moodle tries to do upon initial installation. - Because every database is very different, there doesn't yet exist any way - to do this in a platform-independent way. To support this automation in - each database, schemas can be created that list the required SQL to create - Moodle tables in a particular database. These are files in lib/db - and inside the db subdirectory of each module.

-

Currently, only MySQL and PostgreSQL are fully supported in this way (no-one - wrote the schemas for other brands).

-

Moodle 1.2 will use a new method of database-independent XML schemas that - will make all this unnecessary.

-
-

 

-

Course Formats

-
-

Moodle currently supports three different course formats: weekly, topics - and social.

-

These are a little more connected to the rest of the code (and hence, less - "pluggable") but it is still quite easy to add new ones.

-

If you have any ideas for different formats that you need or would like - to see, get in touch with me and I'll do my absolute best to have them available - in future releases.

-
-

 

-

Documentation and articles

-
-

If you feel like writing a tutorial, an article, an academic paper or anything - else about Moodle, please do!

-

Put it on the web and make sure you include links to http://moodle.org/

-
-

 

-

Participating in the bug tracker

-
-

Finally, I would like to invite you to register on the "bug tracker" - at http://moodle.org/bugs - so you can file any bugs that you find and perhaps participate in discussing - and fixing them.

-

"Bugs" not only includes software bugs with current versions - of Moodle, but also new ideas, feature requests and even constructive criticism - of existing features. The beauty of open source is that anyone can participate - in some way and help to create a better product for all of us to enjoy. - In this project, your input is very welcome!

-
-
-

 

-
-
-
-

Thanks for using Moodle!
-
- Martin Dougiamas, Lead - Developer

-
-
-
-

 

-

 

-
-

 

-
-

Moodle Documentation

-

Version: $Id: developer.html,v 1.2 2001/12/09 - 10:34:19 martin Exp $

- - + + Moodle Docs: Developers Manual + + + + + + +

Developers Manual

+

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

+

It's a bit thin at the moment - better documentation will come eventually!

+

Sections in this document:

+
    +
  1. Moodle architecture
    2. +
  2. How you can contribute + +
    3. +
+

 

+

1. Moodle architecture

+
+

From a system administrator's perspective, Moodle has been designed according + to the following criteria:

+
    +
  1. Moodle should run on the widest variety of platforms
    +
    + The web application platform that runs on most platforms is PHP combined + with MySQL, and this is the environment that Moodle has been developed in + (on Linux, Windows, and Mac OS X). Moodle also uses the ADOdb library for + database abstraction, which means Moodle can use more + than ten different brands of database (unfortunately, though, it can + not yet set up tables in all these databases - + more on this later).
    +
    +
    2. +
  2. Moodle should be easy to install, learn and modify
    +
    + Early prototypes of Moodle (1999) were built using Zope + - an advanced object-oriented web application server. Unfortunately I found + that although the technology was pretty cool, it had a very steep learning + curve and was not very flexible in terms of system administration. The PHP + scripting language, on the other hand, is very easy to get into (especially + if you've done any programming using any other scripting language). Early + on I made the decision to avoid using a class-oriented design - again, to + keep it simple to understand for novices. Code reuse is instead achieved + by libraries of clearly-named functions and consistent layout of script + files. PHP is also easy to install (binaries are available for every platform) + and is widely available to the point that most web hosting services provide + it as standard.
    +
    +
    3. +
  3. It should be easy to upgrade from one version to the next
    +
    + Moodle knows what version it is (as well as the versions of all plug-in + modules) and a mechanism has been built-in so that Moodle can properly upgrade + itself to new versions (for example it can rename database tables or add + new fields). If using CVS in Unix for example, one can just do a "cvs + update -d" and then visit the site home page to complete an upgrade.
    +
    +
    4. +
  4. It should be modular to allow for growth
    +
    + Moodle has a number of features that are modular, including themes, activities, + interface languages, database schemas and course formats. This allows anyone + to add features to the main codebase or to even distribute them separately. + More on this below in the next section.
    +
    +
    5. +
  5. It should be able to be used in conjunction with other systems
    +
    + One thing Moodle does is keep all files for one course within a single, + normal directory on the server. This would allow a system administrator + to provide seamless forms of file-level access for each teacher, such as + Appletalk, SMB, NFS, FTP, WebDAV and so on. The authentication modules allow + Moodle to use LDAP, IMAP, POP3, NNTP and other databases as sources for + user information. Otherwise, there is work yet to do. Features planned for + Moodle in future versions include: import and export of Moodle data using + XML-based formats (including IMS and SCORM); and increased use of style + sheets for interface formatting (so that it can be integrated visually into + other web sites).
    6. +
+
+

 

+

2. How you can contribute

+
+

As mentioned above, Moodle has a number of features that are modular. Even + if you are not a programmer there are things you can change or help with.

+

Learning Activities

+
+

These are by far the most important modules, and reside in the 'mod' directory. + There are seven default modules: assignment, choice, forum, journal, quiz, + resource, and survey. Each module is in a separate subdirectory and consists + of the following mandatory elements (plus extra scripts unique to each module):

+ +

The easiest way to start a new learning activity module is to use the template + in mod/newmodule_template.zip. + Unzip it and follow the README inside.

+

You might also like to post first in the Activities + modules forum on Using Moodle.

+

 

+
+

Themes

+
+

Themes (or skins) define the look of a site. A number of simple themes + are provided in the main distribution, but you may want to create your own + theme with your own colours, logo, styles and graphics.

+

Each theme is in a subdirectory of the "theme" directory, and + contains at least the following files:

+ +

To create your own themes for current versions of Moodle:

+
    +
  1. Copy one of the existing theme folders to one with a new name. I recommend + starting with one of the standard themes.
    2. +
  2. Edit config.php and insert your own colours.
    3. +
  3. Edit styles.php and change your CSS styles.
    4. +
  4. Edit header.html and footer.html to add new logos, or change the layout. +
    5. +
+

Note that all these steps are optional - you can make a radically different + look to your site simply by editing the colours in config.php

+

Note also that Moodle upgrades may break themes slightly, so check + the release notes carefully if you are using a custom theme.

+

In particular, Moodle 2.0 will have a completely new display system, probably + based on XSL transformations of XML output from Moodle. It is likely that + the themes for this will be a completely different format, but the advantage + will be a much higher possible degree of customisation (including moving + elements around the page).

+

More discussion about this in the Themes + forum on Using Moodle. If you create a nice theme that you think others + might want to use, please post your zip file on the themes forum!
+

+
+

 

+

Languages

+
+

Moodle has been designed for internationalisation. Each 'string' or 'page' + of text that is displayed as part of the interface is drawn from a set of + language files. Each language is a subdirectory of the directory 'lang'. + The structure of the lang directory is as follows:

+

lang/en - directory containing all files for one language + (eg English)

+ +

lang/en/help - contains whole help pages (for popup context-sensitive + help)

+
+

Main help pages are situated here, while help pages specific to each + module are located in subdirectories with the module's name.

+

You can insert a helpbutton in a page with the helpbutton function.

+

eg helpbutton("text", "Click here for help about text");

+

and for modules:

+

helpbutton("forumtypes", "Forum types", "forum");

+
+

Note that you can edit languages online, using the administration web tools + under "Check this language". This makes it easy to not to only + create new languages but to refine existing ones. If you are starting a + new language, please contact me, Martin + Dougiamas.

+

You might also like to post in the Languages + forum on Using Moodle.

+

If you are maintaining a language an ongoing basis, I can give you CVS + write access to the Moodle source code so that you can directly maintain + the files.

+
+


+ Database Schemas

+
+

Given a working database with defined tables, the intentionally simple + SQL used in Moodle should work fine with a wide variety of database brands.

+

A problem exists with automatically creating new tables + in a database, which is what Moodle tries to do upon initial installation. + Because every database is very different, there doesn't yet exist any way + to do this in a platform-independent way. To support this automation in + each database, schemas can be created that list the required SQL to create + Moodle tables in a particular database. These are files in lib/db + and inside the db subdirectory of each module.

+

Currently, only MySQL and PostgreSQL are fully supported in this way (no-one + wrote the schemas for other brands).

+

Moodle 1.2 will use a new method of database-independent XML schemas that + will make all this unnecessary.

+
+

 

+

Course Formats

+
+

Moodle currently supports three different course formats: weekly, topics + and social.

+

These are a little more connected to the rest of the code (and hence, less + "pluggable") but it is still quite easy to add new ones.

+

If you have any ideas for different formats that you need or would like + to see, get in touch with me and I'll do my absolute best to have them available + in future releases.

+
+

 

+

Documentation and articles

+
+

If you feel like writing a tutorial, an article, an academic paper or anything + else about Moodle, please do!

+

Put it on the web and make sure you include links to http://moodle.org/

+
+

 

+

Participating in the bug tracker

+
+

Finally, I would like to invite you to register on the "bug tracker" + at http://moodle.org/bugs + so you can file any bugs that you find and perhaps participate in discussing + and fixing them.

+

"Bugs" not only includes software bugs with current versions + of Moodle, but also new ideas, feature requests and even constructive criticism + of existing features. The beauty of open source is that anyone can participate + in some way and help to create a better product for all of us to enjoy. + In this project, your input is very welcome!

+
+
+

 

+
+
+
+

Thanks for using Moodle!
+
+ Martin Dougiamas, Lead + Developer

+
+
+
+

 

+

 

+
+

 

+
+

Moodle Documentation

+

Version: $Id: developer.html,v 1.2 2001/12/09 + 10:34:19 martin Exp $

+ + \ No newline at end of file diff --git a/lang/sv/docs/features.html b/lang/sv/docs/features.html index 870510db2c4..f7b96f39ce1 100644 --- a/lang/sv/docs/features.html +++ b/lang/sv/docs/features.html @@ -1,223 +1,223 @@ - - - - Moodle Docs: Background - - - - - - -

Features

-

Moodle is an active and evolving product. This page lists just some of the - many features it contains:

-

Overall design

- -

Site management

- -

User management

- -

Course management

- -

Assignment Module

- -

Chat Module

- -

Choice Module

- -

Forum Module

- -

Journal Module

- -

Quiz Module

- -

Resource Module

- -

Survey Module

- - -

Workshop Module

- -

 

- -

Moodle Documentation

-

Version: $Id: features.html,v 1.2 2001/12/09 - 10:34:19 martin Exp $

- - - + + + + Moodle Docs: Background + + + + + + +

Features

+

Moodle is an active and evolving product. This page lists just some of the + many features it contains:

+

Overall design

+ +

Site management

+ +

User management

+ +

Course management

+ +

Assignment Module

+ +

Chat Module

+ +

Choice Module

+ +

Forum Module

+ +

Journal Module

+ +

Quiz Module

+ +

Resource Module

+ +

Survey Module

+ + +

Workshop Module

+ +

 

+ +

Moodle Documentation

+

Version: $Id: features.html,v 1.2 2001/12/09 + 10:34:19 martin Exp $

+ + + diff --git a/lang/sv/docs/files.php b/lang/sv/docs/files.php index e05f87e22e3..be72f8cf2c9 100644 --- a/lang/sv/docs/files.php +++ b/lang/sv/docs/files.php @@ -1,21 +1,21 @@ - + diff --git a/lang/sv/docs/future.html b/lang/sv/docs/future.html index bac50d907f7..afb508d8465 100644 --- a/lang/sv/docs/future.html +++ b/lang/sv/docs/future.html @@ -1,59 +1,59 @@ - - Moodle Docs: Future - - - - - - - -

Future

- -

As Moodle gains in maturity, its directions are increasingly influenced by - the community of developers and users. A dynamic database of proposed features - and their status can be found at moodle.org/bugs. - Your contributions in the form of ideas, code, - feedback and promotion are all very welcome - see the Developers - manual for more details.

- -

Here is a rough map of the future (subject to change): -

- -
Version 1.2 - Late 2003
-
The major targets for this version include: - -
- -
Version 2.0 - Early 2004
-
This major release will include some major changes in internal structure - designed to add flexibility and scalability in many areas. Among the major - targets are: - -
-
- -

 

-

Moodle Documentation

-

Version: $Id$

- + + Moodle Docs: Future + + + + + + + +

Future

+ +

As Moodle gains in maturity, its directions are increasingly influenced by + the community of developers and users. A dynamic database of proposed features + and their status can be found at moodle.org/bugs. + Your contributions in the form of ideas, code, + feedback and promotion are all very welcome - see the Developers + manual for more details.

+ +

Here is a rough map of the future (subject to change): +

+ +
Version 1.2 - Late 2003
+
The major targets for this version include: + +
+ +
Version 2.0 - Early 2004
+
This major release will include some major changes in internal structure + designed to add flexibility and scalability in many areas. Among the major + targets are: + +
+
+ +

 

+

Moodle Documentation

+

Version: $Id$

+ diff --git a/lang/sv/docs/install.html b/lang/sv/docs/install.html index dc387c956e9..6aaadb71cc5 100644 --- a/lang/sv/docs/install.html +++ b/lang/sv/docs/install.html @@ -1,428 +1,428 @@ - - Moodle Docs: Installation - - - - - - -

Installing Moodle

-

This guide explains how to install Moodle for the first time. It goes into some detail - about some of the steps, in order to cover the wide variety of small differences between - web server setups, so this document may look long and complicated. Don't be put off by this - - I usually set Moodle up in a few minutes!

-

Take your time and work through this document carefully - it will save you time later on.

-

Sections in this document:

-
    -
  1. Requirements
    2. -
  2. Download
    3. -
  3. Site structure
    4. -
  4. Create a data directory
    5. -
  5. Create a database
    6. -
  6. Check web server settings
    7. -
  7. Edit config.php
    8. -
  8. Go to the admin page
    9. -
  9. Set up cron
    10. -
  10. Create a new course
    11. -
-

1. Requirements

-
-

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

-

The requirements for Moodle are as follows:

-
    -
  1. Web server software. Most people use Apache, - but Moodle should work fine under any web server that supports PHP, such - as IIS on Windows platforms.
    2. -
  2. PHP scripting language (version 4.1.0 - or later), with the following settings: -
      -
    • GD library - turned ON, with support for JPG and PNG formats
      • -
    • zlib library turned ON (if you want to use backup/restore on Windows)
      • -
    • Sessions support turned ON
      • -
    • File uploading turned ON
      • -
    • Safe Mode must be turned OFF (see the forums on moodle.org for problems - caused by Safe Mode)
      • -
    -
    3. -
  3. a working database server: MySQL - or PostgreSQL are - completely supported and recommended for use with Moodle 1.1. All other - databases will be supported fully in the next release.
    4. -
-

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.

-

If you want to run Moodle on your own computer and all this looks a bit daunting, - then please see our guide: Installing - Apache, MySQL and PHP. It provides some step-by-step instructions to install - all this on most popular platforms.

-

 

-

2. Download

-
-

There are two ways to get Moodle, as a compressed package and via CVS. These - are explained in detail on the download page: http://moodle.org/download/

-

After downloading and unpacking the archive, or checking out the files via - CVS, you will be left with a directory called "moodle", containing - a number of files and folders.

-

You can either place the whole folder in your web server documents directory, - in which case the site will be located at http://yourwebserver.com/moodle, - or you can copy all the contents straight into the main web server documents - directory, in which case the site will be simply http://yourwebserver.com.

-
-

 

-

3. Site structure

-
-

Here is a quick summary of the contents of the Moodle folder, to help get - you oriented:

-
-

config.php - the ONLY file you need to edit to get started
- version.php - defines the current version of Moodle code
- index.php - the front page of the site

- -

 

-
-
-

4. Create a data directory

-
-

Moodle will also need some space on your hard disk to store uploaded files, - such as course documents and user pictures.

- -

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: -

- 
deny from all
-
- -

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 "nobody" or "apache".

- -

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.

- -
-

 

-

5. Create a database

-
-

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. -

-

Example command lines for MySQL:

- 
-   # mysql -u root -p
-   > CREATE DATABASE moodle; 
-   > GRANT SELECT,INSERT,UPDATE,DELETE,CREATE,DROP,INDEX,ALTER ON moodle.* 
-           TO moodleuser@localhost IDENTIFIED BY 'yourpassword'; 
-   > quit 
-   # mysqladmin -p reload
-
-

Example command lines for PostgreSQL:

- 
-   # su - postgres
-   > psql -c "create user moodleuser createdb;" template1
-   > psql -c "create database moodle;" -U moodleuser template1
-   > psql -c "alter user moodleuser nocreatedb;" template1
-
-

(For MySQL I highly recommend the use of phpMyAdmin - to manage your databases - you can do all this via a web interface).

-

As of version 1.0.8, Moodle now supports table prefixes, and so can safely share - a database with tables from other applications.

-
-

 

-

6. Check your web server settings

-
-

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).

-

In Apache, this is done using a DirectoryIndex parameter in your httpd.conf - file. Mine usually looks like this:

-
- 
DirectoryIndex index.php index.html index.htm
-
-

Just make sure index.php is in the list (and preferably towards the start - of the list, for efficiency).

-

Secondly, if you are using Apache 2, then you should turn on the AcceptPathInfo - 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.

-
- 
AcceptPathInfo on
-
- -

Thirdly, Moodle requires a number of PHP settings to be active for it to - work. On most servers these will already be the default settings. - 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):

-
- -
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
-
-
-

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. -

To do this, you need to create a file called .htaccess in Moodle's - main directory that contains definitions for these settings. - This only works on Apache servers and only when Overrides have been allowed. - 

-DirectoryIndex index.php index.html index.htm
-
-<IfDefine APACHE2>
-     AcceptPathInfo on
-</IfDefine>
-
-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
-

You can also do things like define the maximum size for uploaded files: - 

-LimitRequestBody 0
-php_value upload_max_filesize 2M
-php_value post_max_size 2M
-
- -

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: -

- 
cp lib/htaccess .htaccess
-
- -
-

 

-

7. Edit config.php

-
-

Now you can edit the configuration file, config.php, using a - text editor. This file is used by all other files in Moodle.

-

To start with, make a copy of config-dist.php and name it - config.php. We do this so that your config.php won't be overwritten in case - you upgrade Moodle later on.

-

Edit config.php 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.

-

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: - http://example.com/moodle

-
-

 

-

8. Go to the admin page

-
-

The admin page should now be working at: http://example.com/moodle/admin. - 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 "shrinkwrap" agreement with which you must agree before you - can continue with the setup.

-

(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 must accept - the Moodle cookies, or Moodle won't work properly.) -

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:

-
-

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)) - TYPE=MyISAM

-

SUCCESS

-

...and so on, followed by: Main databases set up - successfully.

-
-

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 - <? phpinfo() ?> and looking at it through a browser. Check all these and - try this page again.

-

Scroll down the very bottom of the page and press the "Continue" - link.

-

Next you will see a similar page that sets up all the tables required by - each Moodle module. As before, they should all be green.

-

Scroll down the very bottom of the page and press the "Continue" - link.

-

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 "Save changes".

-

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 "secureforms" setting, then - try to continue again.

-

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 - "Save changes".

-

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 "Save changes". Not all the fields are - required, but if you miss any important fields you'll be re-prompted for them. -

-
-
-
-
-
-

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.

-
-
-
-
-
-

(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 "admin", - with password "admin".)

-

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:

- -
-

 

-

9. Set up cron

-
-

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.

-

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 "heartbeat" so that the script can perform functions at periods - defined by each module.

-

Note that the machine performing the cron does not need to be the same - machine that is running Moodle. 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.

-

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.

-

First, test that the script works by running it directly from your browser:

-
- 
http://example.com/moodle/admin/cron.php
-
-

Now, you need to set up some of way of running the script automatically and - regularly.

-

Running the script from a command line

-

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':

-
- 
wget -q -O /dev/null http://example.com/moodle/admin/cron.php
-
-

Note in this example that the output is thrown away (to /dev/null).

-

The same thing using lynx:

-
- 
lynx -dump http://example.com/moodle/admin/cron.php > /dev/null
-
-

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.

-
- 
/opt/bin/php /web/moodle/admin/cron.php
-
-
-(Windows) C:\apache\php\php.exe C:\apache\htdocs\moodle\admin\cron.php
-
-
-
-

Automatically running the script every 5 minutes

-

On Unix systems: Use cron. Edit your cron settings from the commandline - using "crontab -e" and add a line like:

-
- 
*/5 * * * * wget -q -O /dev/null http://example.com/moodle/admin/cron.php
-
-

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).

- -

On Windows systems: The simplest way is to use this little package moodle-cron-for-windows.zip - which makes this whole thing very easy. You can also explore using the built-in - Windows feature for "Scheduled Tasks".

-

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.

-

-
-

10. Create a new course

-
-

Now that Moodle is running properly, you can create a course.

-

Select "Create a new course" from the Admin page (or the admin - links on the home page).

-

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.

-

Press "Save changes", 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 "Add a new user" on the Admin page.

-

Once done, the course is ready to customise, and is accessible via the "Courses" - link on the home page.

-

See the "Teacher Manual" for more details - on course-building.

-
-

 

-

Moodle Documentation

-

Version: $Id$

- - + + Moodle Docs: Installation + + + + + + +

Installing Moodle

+

This guide explains how to install Moodle for the first time. It goes into some detail + about some of the steps, in order to cover the wide variety of small differences between + web server setups, so this document may look long and complicated. Don't be put off by this + - I usually set Moodle up in a few minutes!

+

Take your time and work through this document carefully - it will save you time later on.

+

Sections in this document:

+
    +
  1. Requirements
    2. +
  2. Download
    3. +
  3. Site structure
    4. +
  4. Create a data directory
    5. +
  5. Create a database
    6. +
  6. Check web server settings
    7. +
  7. Edit config.php
    8. +
  8. Go to the admin page
    9. +
  9. Set up cron
    10. +
  10. Create a new course
    11. +
+

1. Requirements

+
+

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

+

The requirements for Moodle are as follows:

+
    +
  1. Web server software. Most people use Apache, + but Moodle should work fine under any web server that supports PHP, such + as IIS on Windows platforms.
    2. +
  2. PHP scripting language (version 4.1.0 + or later), with the following settings: +
      +
    • GD library + turned ON, with support for JPG and PNG formats
      • +
    • zlib library turned ON (if you want to use backup/restore on Windows)
      • +
    • Sessions support turned ON
      • +
    • File uploading turned ON
      • +
    • Safe Mode must be turned OFF (see the forums on moodle.org for problems + caused by Safe Mode)
      • +
    +
    3. +
  3. a working database server: MySQL + or PostgreSQL are + completely supported and recommended for use with Moodle 1.1. All other + databases will be supported fully in the next release.
    4. +
+

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.

+

If you want to run Moodle on your own computer and all this looks a bit daunting, + then please see our guide: Installing + Apache, MySQL and PHP. It provides some step-by-step instructions to install + all this on most popular platforms.

+

 

+

2. Download

+
+

There are two ways to get Moodle, as a compressed package and via CVS. These + are explained in detail on the download page: http://moodle.org/download/

+

After downloading and unpacking the archive, or checking out the files via + CVS, you will be left with a directory called "moodle", containing + a number of files and folders.

+

You can either place the whole folder in your web server documents directory, + in which case the site will be located at http://yourwebserver.com/moodle, + or you can copy all the contents straight into the main web server documents + directory, in which case the site will be simply http://yourwebserver.com.

+
+

 

+

3. Site structure

+
+

Here is a quick summary of the contents of the Moodle folder, to help get + you oriented:

+
+

config.php - the ONLY file you need to edit to get started
+ version.php - defines the current version of Moodle code
+ index.php - the front page of the site

+ +

 

+
+
+

4. Create a data directory

+
+

Moodle will also need some space on your hard disk to store uploaded files, + such as course documents and user pictures.

+ +

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: +

+ 
deny from all
+
+ +

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 "nobody" or "apache".

+ +

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.

+ +
+

 

+

5. Create a database

+
+

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. +

+

Example command lines for MySQL:

+ 
+   # mysql -u root -p
+   > CREATE DATABASE moodle; 
+   > GRANT SELECT,INSERT,UPDATE,DELETE,CREATE,DROP,INDEX,ALTER ON moodle.* 
+           TO moodleuser@localhost IDENTIFIED BY 'yourpassword'; 
+   > quit 
+   # mysqladmin -p reload
+
+

Example command lines for PostgreSQL:

+ 
+   # su - postgres
+   > psql -c "create user moodleuser createdb;" template1
+   > psql -c "create database moodle;" -U moodleuser template1
+   > psql -c "alter user moodleuser nocreatedb;" template1
+
+

(For MySQL I highly recommend the use of phpMyAdmin + to manage your databases - you can do all this via a web interface).

+

As of version 1.0.8, Moodle now supports table prefixes, and so can safely share + a database with tables from other applications.

+
+

 

+

6. Check your web server settings

+
+

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).

+

In Apache, this is done using a DirectoryIndex parameter in your httpd.conf + file. Mine usually looks like this:

+
+ 
DirectoryIndex index.php index.html index.htm
+
+

Just make sure index.php is in the list (and preferably towards the start + of the list, for efficiency).

+

Secondly, if you are using Apache 2, then you should turn on the AcceptPathInfo + 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.

+
+ 
AcceptPathInfo on
+
+ +

Thirdly, Moodle requires a number of PHP settings to be active for it to + work. On most servers these will already be the default settings. + 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):

+
+ +
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
+
+
+

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. +

To do this, you need to create a file called .htaccess in Moodle's + main directory that contains definitions for these settings. + This only works on Apache servers and only when Overrides have been allowed. + 

+DirectoryIndex index.php index.html index.htm
+
+<IfDefine APACHE2>
+     AcceptPathInfo on
+</IfDefine>
+
+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
+

You can also do things like define the maximum size for uploaded files: + 

+LimitRequestBody 0
+php_value upload_max_filesize 2M
+php_value post_max_size 2M
+
+ +

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: +

+ 
cp lib/htaccess .htaccess
+
+ +
+

 

+

7. Edit config.php

+
+

Now you can edit the configuration file, config.php, using a + text editor. This file is used by all other files in Moodle.

+

To start with, make a copy of config-dist.php and name it + config.php. We do this so that your config.php won't be overwritten in case + you upgrade Moodle later on.

+

Edit config.php 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.

+

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: + http://example.com/moodle

+
+

 

+

8. Go to the admin page

+
+

The admin page should now be working at: http://example.com/moodle/admin. + 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 "shrinkwrap" agreement with which you must agree before you + can continue with the setup.

+

(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 must accept + the Moodle cookies, or Moodle won't work properly.) +

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:

+
+

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)) + TYPE=MyISAM

+

SUCCESS

+

...and so on, followed by: Main databases set up + successfully.

+
+

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 + <? phpinfo() ?> and looking at it through a browser. Check all these and + try this page again.

+

Scroll down the very bottom of the page and press the "Continue" + link.

+

Next you will see a similar page that sets up all the tables required by + each Moodle module. As before, they should all be green.

+

Scroll down the very bottom of the page and press the "Continue" + link.

+

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 "Save changes".

+

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 "secureforms" setting, then + try to continue again.

+

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 + "Save changes".

+

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 "Save changes". Not all the fields are + required, but if you miss any important fields you'll be re-prompted for them. +

+
+
+
+
+
+

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.

+
+
+
+
+
+

(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 "admin", + with password "admin".)

+

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:

+ +
+

 

+

9. Set up cron

+
+

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.

+

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 "heartbeat" so that the script can perform functions at periods + defined by each module.

+

Note that the machine performing the cron does not need to be the same + machine that is running Moodle. 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.

+

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.

+

First, test that the script works by running it directly from your browser:

+
+ 
http://example.com/moodle/admin/cron.php
+
+

Now, you need to set up some of way of running the script automatically and + regularly.

+

Running the script from a command line

+

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':

+
+ 
wget -q -O /dev/null http://example.com/moodle/admin/cron.php
+
+

Note in this example that the output is thrown away (to /dev/null).

+

The same thing using lynx:

+
+ 
lynx -dump http://example.com/moodle/admin/cron.php > /dev/null
+
+

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.

+
+ 
/opt/bin/php /web/moodle/admin/cron.php
+
+
+(Windows) C:\apache\php\php.exe C:\apache\htdocs\moodle\admin\cron.php
+
+
+
+

Automatically running the script every 5 minutes

+

On Unix systems: Use cron. Edit your cron settings from the commandline + using "crontab -e" and add a line like:

+
+ 
*/5 * * * * wget -q -O /dev/null http://example.com/moodle/admin/cron.php
+
+

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).

+ +

On Windows systems: The simplest way is to use this little package moodle-cron-for-windows.zip + which makes this whole thing very easy. You can also explore using the built-in + Windows feature for "Scheduled Tasks".

+

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.

+

+
+

10. Create a new course

+
+

Now that Moodle is running properly, you can create a course.

+

Select "Create a new course" from the Admin page (or the admin + links on the home page).

+

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.

+

Press "Save changes", 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 "Add a new user" on the Admin page.

+

Once done, the course is ready to customise, and is accessible via the "Courses" + link on the home page.

+

See the "Teacher Manual" for more details + on course-building.

+
+

 

+

Moodle Documentation

+

Version: $Id$

+ + diff --git a/lang/sv/docs/installamp.html b/lang/sv/docs/installamp.html index 75bb8cb3fe3..af11fa05e1a 100644 --- a/lang/sv/docs/installamp.html +++ b/lang/sv/docs/installamp.html @@ -1,168 +1,168 @@ - - 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 - data in a database. The database we recommend is MySQL. Before installing Moodle - you must have a working PHP installation and a working database to turn your - computer into a functional web server platform. These packages can be tricky - to set up for average computer users, so this page has been written to try to - make this process as simple as possible for different platforms:

- -

 

-

Hosting Service

-
-

Unfortunately hosting services vary quite a lot in the way they work. Some - will even install Moodle for you.

-

Most will offer a web-based control panel to control your site, create databases - and set up cron. Some may also offer terminal access via ssh, so that you - can use the command shell to do things.

-

You should work your way through the Installation - guide and take each step at a time. Ask your hosting provider if you get - stuck.

-

 

-
-

Mac OS X

-
-

The easiest way to do this is use the Apache server that Apple provides, - and add PHP and MySQL using Marc Liyanage's packages. Both of the pages below - come with good instructions that we won't duplicate here:

-
-

PHP: Download from here: http://www.entropy.ch/software/macosx/php/

-

MySQL: Download here: http://www.entropy.ch/software/macosx/mysql/

-
-

Once these are installed the standard Installation - guide should be fairly straightforward.

-

A more detailed walkthrough is here: http://moodle.org/wiki/index.php/InstallingMoodle

-

 

-
-

Redhat Linux

-
-

You should install all available RPM packages for Apache, PHP and MySQL. - One package that people frequently forget is the php-mysql package which is - necessary for PHP to talk to MySQL.

-

Once these are installed the standard Installation - guide should be fairly straightforward.

-

A more detailed walkthrough is here: http://moodle.org/wiki/index.php/InstallingMoodle

-
-

 

-

Windows

-
-

The easiest way to do this is use EasyPHP, - a package that bundles all the software you need into a single Windows application. - Here are the steps from start to finish:

-
    -
  1. Firstly, if you have ever installed MySQL before (even as part of another - package), uninstall it all, delete all the MySQL files and make sure you - delete c:\my.cnf and c:\windows\my.ini.You - might want to do a search and delete ANY file called my.cnf - or my.ini.
    2. -
  2. If you've ever installed PHP before delete any files called php4ts.dll - from around your Windows directory, as well as any files called php.ini.
    3. -
  3. Download EasyPHP from here: http://www.easyphp.org/telechargements/dn.php?F=easyphp1-6.php3 - (approx 10 Mb)
    4. -
  4. Run the downloaded file: easyphp1-6_setup.exe. The installation - process is in French but is otherwise much like installing any other Windows - program - I advise accepting the defaults and letting it all install. Note - that "Suivant" means Next.and "Oui" means Yes.
    5. -
  5. At the end of the install leave the checkbox selected to "Lancer - EasyPHP" (Start EasyPHP) and hit the 'Terminer" button.You might - be taken to a information web page which you can safely ignore.
    6. -
  6. If all went well - congratulations! Apache, PHP and MySQL are all installed - and running! You should see a black E in your toolbar tray. You can right - click on it to get a menu which will let you control the running programs, - but you won't be needing that for now.
    7. -
  7. The next thing you need to do is to set up a database for Moodle to use. - Using a browser, go to http://localhost/mysql/ - (note the final slash).
    8. -
  8. If asked for a username, use "root" with a blank password. You - should see a phpMyAdmin web interface that allows you to create a new databases - and user accounts.
    9. -
  9. Create a new database by typing "moodle" into the field and - hitting the "Create" button. That was easy!
    10. -
  10. You can also create a new user to access your database if you want. This - can be a bit tricky for a first-time user, so you might just want to use - the existing user "root" with no password in your Moodle config - for now, and fix this later.
    11. -
  11. You're ready to install Moodle! Download the latest release of Moodle - from http://moodle.org/download, - then unzip the archive.
    12. -
  12. Copy your moodle files into C:\Program Files\EasyPHP\www. You - can either copy the entire moodle directory (ie C:\Program Files\EasyPHP\www\moodle) - or copy all the contents of the moodle directory. If you choose - this second option then you will be able to access your Moodle home page - using http://localhost/ instead of http://localhost/moodle/.
    13. -
  13. Make a new empty folder somewhere else for Moodle to store uploaded files - in, eg: C:\moodledata
    14. -
  14. Go into your Moodle folder. Make a copy of config-dist.php, and call - it config.php
    15. -
  15. Edit config.php using a text editor (Notepad will do, just be careful - that it doesn't add unwanted spaces at the end).
    16. -
  16. Put in all your new database info:
    - $CFG->dbtype = 'mysql';
    - $CFG->dbhost = 'localhost';
    - $CFG->dbname = 'moodle';
    - $CFG->dbuser = 'root';
    - $CFG->dbpass = '';
    - $CFG->dbpersist = true;
    - $CFG->prefix = 'mdl_';
    -
    17. -
  17. And put in all your file paths:
    - $CFG->wwwroot = 'http://localhost/moodle'; // Use an external address - if you know it.
    - $CFG->dirroot = 'C:\Program Files\EasyPHP\www\moodle';
    - $CFG->dataroot = 'C:\moodledata';
    -
    18. -
  18. Save config.php - you can ignore the other settings if there are any.
    19. -
  19. You're nearly there now! The rest of the setup is all web-based. Visit - http://localhost/moodle/admin/ - with your browser to continue the setup via your browser.
    20. -
  20. To use zip files with Moodle (for example the backups use zip) you might - need to enable "zlib". You can do this by going to your EasyPHP - directory (C:\Program Files\EasyPHP), and running the program - phpini.exe in there. Put a mark in the checkbox next to "zlib.dll". - Close that window, then go to the black E in your toolbar and right-click - it to get a menu - select "Restart" from this menu.
    21. -
  21. Lastly, you need to set up some sort of cron. See the Installation - guide for more details on this.
    22. -
-

If you don't or can't use EasyPHP, here are some a few tips to make sure - your PHP is set up correctly and avoid common problems:

- -
-

 

-

Moodle Documentation

-

Version: $Id$

- - + + 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 + data in a database. The database we recommend is MySQL. Before installing Moodle + you must have a working PHP installation and a working database to turn your + computer into a functional web server platform. These packages can be tricky + to set up for average computer users, so this page has been written to try to + make this process as simple as possible for different platforms:

+ +

 

+

Hosting Service

+
+

Unfortunately hosting services vary quite a lot in the way they work. Some + will even install Moodle for you.

+

Most will offer a web-based control panel to control your site, create databases + and set up cron. Some may also offer terminal access via ssh, so that you + can use the command shell to do things.

+

You should work your way through the Installation + guide and take each step at a time. Ask your hosting provider if you get + stuck.

+

 

+
+

Mac OS X

+
+

The easiest way to do this is use the Apache server that Apple provides, + and add PHP and MySQL using Marc Liyanage's packages. Both of the pages below + come with good instructions that we won't duplicate here:

+
+

PHP: Download from here: http://www.entropy.ch/software/macosx/php/

+

MySQL: Download here: http://www.entropy.ch/software/macosx/mysql/

+
+

Once these are installed the standard Installation + guide should be fairly straightforward.

+

A more detailed walkthrough is here: http://moodle.org/wiki/index.php/InstallingMoodle

+

 

+
+

Redhat Linux

+
+

You should install all available RPM packages for Apache, PHP and MySQL. + One package that people frequently forget is the php-mysql package which is + necessary for PHP to talk to MySQL.

+

Once these are installed the standard Installation + guide should be fairly straightforward.

+

A more detailed walkthrough is here: http://moodle.org/wiki/index.php/InstallingMoodle

+
+

 

+

Windows

+
+

The easiest way to do this is use EasyPHP, + a package that bundles all the software you need into a single Windows application. + Here are the steps from start to finish:

+
    +
  1. Firstly, if you have ever installed MySQL before (even as part of another + package), uninstall it all, delete all the MySQL files and make sure you + delete c:\my.cnf and c:\windows\my.ini.You + might want to do a search and delete ANY file called my.cnf + or my.ini.
    2. +
  2. If you've ever installed PHP before delete any files called php4ts.dll + from around your Windows directory, as well as any files called php.ini.
    3. +
  3. Download EasyPHP from here: http://www.easyphp.org/telechargements/dn.php?F=easyphp1-6.php3 + (approx 10 Mb)
    4. +
  4. Run the downloaded file: easyphp1-6_setup.exe. The installation + process is in French but is otherwise much like installing any other Windows + program - I advise accepting the defaults and letting it all install. Note + that "Suivant" means Next.and "Oui" means Yes.
    5. +
  5. At the end of the install leave the checkbox selected to "Lancer + EasyPHP" (Start EasyPHP) and hit the 'Terminer" button.You might + be taken to a information web page which you can safely ignore.
    6. +
  6. If all went well - congratulations! Apache, PHP and MySQL are all installed + and running! You should see a black E in your toolbar tray. You can right + click on it to get a menu which will let you control the running programs, + but you won't be needing that for now.
    7. +
  7. The next thing you need to do is to set up a database for Moodle to use. + Using a browser, go to http://localhost/mysql/ + (note the final slash).
    8. +
  8. If asked for a username, use "root" with a blank password. You + should see a phpMyAdmin web interface that allows you to create a new databases + and user accounts.
    9. +
  9. Create a new database by typing "moodle" into the field and + hitting the "Create" button. That was easy!
    10. +
  10. You can also create a new user to access your database if you want. This + can be a bit tricky for a first-time user, so you might just want to use + the existing user "root" with no password in your Moodle config + for now, and fix this later.
    11. +
  11. You're ready to install Moodle! Download the latest release of Moodle + from http://moodle.org/download, + then unzip the archive.
    12. +
  12. Copy your moodle files into C:\Program Files\EasyPHP\www. You + can either copy the entire moodle directory (ie C:\Program Files\EasyPHP\www\moodle) + or copy all the contents of the moodle directory. If you choose + this second option then you will be able to access your Moodle home page + using http://localhost/ instead of http://localhost/moodle/.
    13. +
  13. Make a new empty folder somewhere else for Moodle to store uploaded files + in, eg: C:\moodledata
    14. +
  14. Go into your Moodle folder. Make a copy of config-dist.php, and call + it config.php
    15. +
  15. Edit config.php using a text editor (Notepad will do, just be careful + that it doesn't add unwanted spaces at the end).
    16. +
  16. Put in all your new database info:
    + $CFG->dbtype = 'mysql';
    + $CFG->dbhost = 'localhost';
    + $CFG->dbname = 'moodle';
    + $CFG->dbuser = 'root';
    + $CFG->dbpass = '';
    + $CFG->dbpersist = true;
    + $CFG->prefix = 'mdl_';
    +
    17. +
  17. And put in all your file paths:
    + $CFG->wwwroot = 'http://localhost/moodle'; // Use an external address + if you know it.
    + $CFG->dirroot = 'C:\Program Files\EasyPHP\www\moodle';
    + $CFG->dataroot = 'C:\moodledata';
    +
    18. +
  18. Save config.php - you can ignore the other settings if there are any.
    19. +
  19. You're nearly there now! The rest of the setup is all web-based. Visit + http://localhost/moodle/admin/ + with your browser to continue the setup via your browser.
    20. +
  20. To use zip files with Moodle (for example the backups use zip) you might + need to enable "zlib". You can do this by going to your EasyPHP + directory (C:\Program Files\EasyPHP), and running the program + phpini.exe in there. Put a mark in the checkbox next to "zlib.dll". + Close that window, then go to the black E in your toolbar and right-click + it to get a menu - select "Restart" from this menu.
    21. +
  21. Lastly, you need to set up some sort of cron. See the Installation + guide for more details on this.
    22. +
+

If you don't or can't use EasyPHP, here are some a few tips to make sure + your PHP is set up correctly and avoid common problems:

+ +
+

 

+

Moodle Documentation

+

Version: $Id$

+ + \ No newline at end of file diff --git a/lang/sv/docs/intro.html b/lang/sv/docs/intro.html index d35bda04920..a66caf4609c 100644 --- a/lang/sv/docs/intro.html +++ b/lang/sv/docs/intro.html @@ -1,41 +1,41 @@ - - - - Moodle Docs: Introduction - - - - - -

Introduction

- -

Moodle is a software package for producing internet-based courses and web sites. - It's an ongoing development project designed to support a social constructionist framework of education.

- -

Moodle is provided freely as - Open Source software (under the - GNU Public License). Basically this means Moodle is copyrighted, but that - you have additional freedoms. You are allowed to copy, use and modify Moodle - 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 - holder directly if you have any questions. -

Moodle will run on any computer that can run - PHP, and can support many types of database (particularly MySQL).

- -

The word Moodle was originally an acronym for Modular Object-Oriented Dynamic - Learning Environment, which is mostly useful to programmers and education theorists.  - It's also a verb that describes the process of lazily meandering through something, - doing things as it occurs to you to do them, an enjoyable tinkering that often - leads to insight and creativity. As such it applies both to the way Moodle was - developed, and to the way a student or teacher might approach studying or teaching - an online course. Anyone who uses Moodle is a Moodler.

-

Come and moodle with us!

-


-

-

Moodle Documentation

-

Version: $Id$

- - - + + + + Moodle Docs: Introduction + + + + + +

Introduction

+ +

Moodle is a software package for producing internet-based courses and web sites. + It's an ongoing development project designed to support a social constructionist framework of education.

+ +

Moodle is provided freely as + Open Source software (under the + GNU Public License). Basically this means Moodle is copyrighted, but that + you have additional freedoms. You are allowed to copy, use and modify Moodle + 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 + holder directly if you have any questions. +

Moodle will run on any computer that can run + PHP, and can support many types of database (particularly MySQL).

+ +

The word Moodle was originally an acronym for Modular Object-Oriented Dynamic + Learning Environment, which is mostly useful to programmers and education theorists.  + It's also a verb that describes the process of lazily meandering through something, + doing things as it occurs to you to do them, an enjoyable tinkering that often + leads to insight and creativity. As such it applies both to the way Moodle was + developed, and to the way a student or teacher might approach studying or teaching + an online course. Anyone who uses Moodle is a Moodler.

+

Come and moodle with us!

+


+

+

Moodle Documentation

+

Version: $Id$

+ + + diff --git a/lang/sv/docs/licence.html b/lang/sv/docs/licence.html index 10fb83ce650..366a515b015 100644 --- a/lang/sv/docs/licence.html +++ b/lang/sv/docs/licence.html @@ -1,33 +1,33 @@ - - - - Moodle Docs: Copyright License - - - - - -

Copyright License for Moodle

- -

Moodle is Copyright © 2001-2003, Martin - Dougiamas.

-

This program is free software; you can redistribute it and/or modify
- it under the terms of the GNU General Public License as published by
- the Free Software Foundation; either version 2 of the License, or
- (at your option) any later version.

-

This program is distributed in the hope that it will be useful,
- but WITHOUT ANY WARRANTY; without even the implied warranty of
- 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 Docs: Copyright License + + + + + +

Copyright License for Moodle

+ +

Moodle is Copyright © 2001-2003, Martin + Dougiamas.

+

This program is free software; you can redistribute it and/or modify
+ it under the terms of the GNU General Public License as published by
+ the Free Software Foundation; either version 2 of the License, or
+ (at your option) any later version.

+

This program is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ 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$

+ + + diff --git a/lang/sv/docs/other.html b/lang/sv/docs/other.html index 720790ede06..0dccebc57a1 100644 --- a/lang/sv/docs/other.html +++ b/lang/sv/docs/other.html @@ -1,62 +1,62 @@ - - -Moodle Docs: Frequently Asked Questions (FAQ) - - - - - - - -

Other documentation

-

Here are some links to other sources of Moodle documentation:

-

Index of all Moodle - help pages - a list of all the context-sensitive help files within Moodle

-

User-contributed documentation - - this page lists documentation contributed by Moodle users

-

 

-
- -

Moodle Documentation

-

Version: $Id$

- - - + + +Moodle Docs: Frequently Asked Questions (FAQ) + + + + + + + +

Other documentation

+

Here are some links to other sources of Moodle documentation:

+

Index of all Moodle + help pages - a list of all the context-sensitive help files within Moodle

+

User-contributed documentation + - this page lists documentation contributed by Moodle users

+

 

+
+ +

Moodle Documentation

+

Version: $Id$

+ + + diff --git a/lang/sv/docs/release.html b/lang/sv/docs/release.html index e654c2dfd77..e4c1390541d 100644 --- a/lang/sv/docs/release.html +++ b/lang/sv/docs/release.html @@ -1,378 +1,378 @@ - - Moodle Docs: Release notes - - - - - - -

Release notes

- -

New in Moodle 1.1.1 (10 September, 2003):

- - - -
- - - -

New in Moodle 1.1 (28 August, 2003):

- - -
- -

New in Moodle 1.0.9 (29th May, 2003) :

- - -
- - -

Older releases can be seen in the Moodle.org announcement forum. - - -

 

-

Moodle Documentation

-

Version: $Id$

+ + Moodle Docs: Release notes + + + + + + +

Release notes

+ +

New in Moodle 1.1.1 (10 September, 2003):

+ + + +
+ + + +

New in Moodle 1.1 (28 August, 2003):

+ + +
+ +

New in Moodle 1.0.9 (29th May, 2003) :

+ + +
+ + +

Older releases can be seen in the Moodle.org announcement forum. + + +

 

+

Moodle Documentation

+

Version: $Id$

diff --git a/lang/sv/docs/teacher.html b/lang/sv/docs/teacher.html index 913fd1ee413..2ca59aca8a3 100644 --- a/lang/sv/docs/teacher.html +++ b/lang/sv/docs/teacher.html @@ -1,256 +1,256 @@ - - Moodle Docs: Teachers Manual - - - - - - - -

Teacher Manual

-

This page is a very quick guide to creating online courses with Moodle. It - outlines the main functions that are available, as well as some of the main - decisions you'll need to make.

- -

Sections in this document:

-
    -
  1. Getting started
    2. -
  2. Course settings
    3. -
  3. Uploading files
    4. -
  4. Setting up activities
    5. -
  5. Running the course
    6. -
  6. Further information
    7. -
-

Getting started

-
-

This document assumes your site administrator has set up Moodle and given - you new, blank course to start with. It also assumes you have logged in to - your course using your teacher account.

-

Here are three general tips that will help you get started.

-
    -
  1. Don't be afraid to experiment: -
    feel free to poke around and change things. It's hard to break anything - in a Moodle course, and even if you do it's usually easy to fix it. -
    -
  2. Notice and use these little icons: -
    -

      - the edit icon - lets you edit whatever it is next to.

    -

    - the help - icon will provide you with a popup help window

    -

      - the open-eye - icon will let you hide something from students

    -

      - the closed-eye - icon will make a hidden item available

    -
    -
    3. -
  3. Use the navigation bar at the top of each page -
    this - should help remind you where you are and prevent getting lost. -
    4. -
- -

 

-

Course settings

-
-

The first thing you should do is look under the "Administration" - on your course home page and click on "Settings..." - (Note that this link, and in fact the whole Administration section is only - available to you (and the site administrator). Students will not even see - these links).

-

On the Settings page you can change a number of settings about your course, - ranging from its name to what day it starts. I won't talk here about all these, - as they all have a help icon next to them which explains them all in detail. - However, I will talk about the most important of these - the course - format.

-

The course format that you choose will decide the basic layout of your course, - like a template. Moodle version 1.0 has three formats - in future there will - probably be many more (please send new ideas to martin@moodle.org!)

-

Here are some screenshots of three sample courses in each of these three - formats (ignore the different colours, which are set for a whole site by the - site administrator):

-

Weekly format:

-

-

 

-

Topics format:

-

-

 

-

Social format:

-

-

 

-

Note that the weekly and topics formats are very similar in structure. The - main difference is that each box in the weekly format covers exactly one week, - whereas in the topic format each box can cover whatever you like. The social - format doesn't use much content at all and is based around just one forum - - this is displayed on the main page.

-

See the help buttons on the Course Settings page for more details.

- -

 

-

Uploading files

-
-

You may have existing content that you want to add to your course, such as - web pages, audio files, video files, word documents, or flash animations. - Any type of file that exists can be uploaded into your course and stored on - the server. While your files are on the server you can move, rename, edit - or delete them.

-

All of this is achieved through the Files link in your Administration - menu. The Files section looks like this:

-

-

 

-

This interface is only available to teachers - it is not accessible by students. - Individual files are made available to students later on (as "Resources" - - see the next section).

-

As you can see in the screenshot, files are listed alongside subdirectories. - You can create any number of subdirectories to organise your files and move - your files from one to the other.

-

Uploading files via the web is currently restricted to one file at a time. - If you want to upload a lot of files at once (for example a whole web site), - it can be a lot easier to use a zip program to compress them - into a single file, upload the zip file and then unzip them again on the server - (you will see an "unzip" link next to zip archives).

-

To preview any file you have uploaded just click on its name. Your web browser - will take care of either displaying it or downloading it to your computer.

-

HTML and text files can be edited in-place online. Other files will need - to be edited on your local computer and uploaded again. if you upload a file - with the same name as an existing file it will automatically be overwritten.

-

A final note: if your content resides out on the web then you don't need - to upload the files at all - you can link directly to them from inside the - course (see the Resources module and the next section).

- -

 

-

Setting up activities

-
-

Building a course involves adding course activity modules to the main page - in the order that students will be using them. You can shuffle the order any - time you like.

-

To turn on editing, click "Turn on editing" under Administration. - This toggle switch shows or hides the extra controls that allow you to manipulate - your main course page. Note in the first screenshot above (of the Weekly format - course) that the editing controls are turned on.

-

To add a new activity, simply go to the week or topic or section of the screen - where you want to add it, and select the type of activity from the popup menu. - Here is a summary of all the standard activities in Moodle 1.0:

-
-
Assignment
-
An assignment is where you set a task with a due date and a maximum grade. - Students will be able to upload one file to satisify the requirements. The - date they upload their file is recorded. Afterwards, you will have a single - page on which ou can view each file (and how late or early it is), and then - record a grade and a comment. Half an hour after you grade any particular - student, Moodle will automatically email that student a notification.
-
-
-
Choice
-
A choice activity is very simple - you ask a question and specify a choice - of responses. Students can make their choice, and you have a report screen - where you can see the results. I use it to gather research consent from - my students, but you could use it for quick polls or class votes.
-
-
-
Forum
-
This module is by far the most important - it is here that discussion - takes place. When you add a new forum, yu will presented with a choice of - different types - a simple single-topic discussion, a free-for-all general - forum, or a one-discussion-thread-per-user.
-
-
-
Journal
-
Each journal activity is an entry in the whole course journal. For each - one you can specify an open-ended question that guides what students write, - as well as a window of time in which the journal is open (weekly course - format only). A general rule of thumb is to create one journal per week. - Encourage students to write reflectively and critically in these journals, - as they are only available to them and you. Afterwards, you will be able - to grade and comment all the entries for that week or topic, and students - will receive an automatic email informing them of your feedback. Journals - are not designed to be continually added to - if you need to do that then - add more journal activities.
-
-
-
Resource
-
Resources are the content of your course. Each resource can be any file - you have uploaded or can point to using a URL. You can also maintain simple - text-based pages by typing them directly into a form.
-
-
-
Quiz
-
This module allows you to design and set quiz tests, consisting of multiple - choice, true-false, and short answer questions. These questions are kept - in a categorised database, and can be re-used within courses and even between - courses. Quizzes can allow multiple attempts. Each attempt is automatically - marked, and the teacher can choose whether to give feedback or to show correct - answers. This module includes grading facilities.
-
-
-
Survey
-
The survey module provides a number of predefined survey instruments that - are useful in evaluating and understanding your class. Currently they include - the COLLES and the ATTLS instruments. They can be given to students early - in the course as a diagnostic tool and at the end of the course as an evaluation - tool (I use one every week in my courses).
-
-
-

After adding your activities you can move them up and down in your course - layout by clicking on the little arrow icons ( - ) next to each one. You - can also delete them using the cross icon , - and re-edit them using the edit icon .

- -

 

-

Running the course

-
-

There are some big plans to extend this document into a more comprehensive - tutorial. Until then here are a few ideas:

-
    -
  1. Subscribe yourself to all the forums so you keep in touch with your class - activity.
    2. -
  2. Encourage all the students fill out their user profile (including photos) - and read them all - this will help provide some context to their later writings - and help you to respond in ways that are tailored to their own needs.
    3. -
  3. Keep notes to yourself in the private "Teacher's Forum" - (under Administration). This is especially useful when team teaching.
    4. -
  4. Use the "Logs" link (under Administration) - to get access to complete, raw logs. In there you'll see a link to a popup - window that updates every sixty seconds and shows the last hour of activity. - This is useful to keep open on your desktop all day so you can feel in touch - with what's going on in the course.
    5. -
  5. Use the "Activity Reports" (next to each name - in the list of all people, or from any user profile page). These provide - a great way to see what any particular person has been up to in the course.
    6. -
  6. Respond quickly to students. Don't leave it for later - do it right away. - Not only is it easy to become overwhelmed with the volume that can be generated, - but it's a crucial part of building and maintaining a community feel in - your course.
    7. -
- -

 

-

Further information

-
-

If you have any particular problems with your site, you should contact your - local site administrator.

-

If you have some great ideas for improvements to Moodle, or even some good - stories, come over to moodle.org - and join us in the course called "Using - Moodle". We'd love to hear from you, and you can help Moodle improve.

-

If you want to contribute to coding new modules, or writing documentation, - or papers, contact me: Martin - Dougiamas or browse the "bug tracker" site for Moodle, at moodle.org/bugs

-

Thanks for using Moodle - and good luck with your teaching!

-
-

 

-
-

Moodle Documentation

-

Version: $Id: teacher.html,v 1.4 2002/08/18 10:00:01 - martin Exp $

- - + + Moodle Docs: Teachers Manual + + + + + + + +

Teacher Manual

+

This page is a very quick guide to creating online courses with Moodle. It + outlines the main functions that are available, as well as some of the main + decisions you'll need to make.

+ +

Sections in this document:

+
    +
  1. Getting started
    2. +
  2. Course settings
    3. +
  3. Uploading files
    4. +
  4. Setting up activities
    5. +
  5. Running the course
    6. +
  6. Further information
    7. +
+

Getting started

+
+

This document assumes your site administrator has set up Moodle and given + you new, blank course to start with. It also assumes you have logged in to + your course using your teacher account.

+

Here are three general tips that will help you get started.

+
    +
  1. Don't be afraid to experiment: +
    feel free to poke around and change things. It's hard to break anything + in a Moodle course, and even if you do it's usually easy to fix it. +
    +
  2. Notice and use these little icons: +
    +

      - the edit icon + lets you edit whatever it is next to.

    +

    - the help + icon will provide you with a popup help window

    +

      - the open-eye + icon will let you hide something from students

    +

      - the closed-eye + icon will make a hidden item available

    +
    +
    3. +
  3. Use the navigation bar at the top of each page +
    this + should help remind you where you are and prevent getting lost. +
    4. +
+ +

 

+

Course settings

+
+

The first thing you should do is look under the "Administration" + on your course home page and click on "Settings..." + (Note that this link, and in fact the whole Administration section is only + available to you (and the site administrator). Students will not even see + these links).

+

On the Settings page you can change a number of settings about your course, + ranging from its name to what day it starts. I won't talk here about all these, + as they all have a help icon next to them which explains them all in detail. + However, I will talk about the most important of these - the course + format.

+

The course format that you choose will decide the basic layout of your course, + like a template. Moodle version 1.0 has three formats - in future there will + probably be many more (please send new ideas to martin@moodle.org!)

+

Here are some screenshots of three sample courses in each of these three + formats (ignore the different colours, which are set for a whole site by the + site administrator):

+

Weekly format:

+

+

 

+

Topics format:

+

+

 

+

Social format:

+

+

 

+

Note that the weekly and topics formats are very similar in structure. The + main difference is that each box in the weekly format covers exactly one week, + whereas in the topic format each box can cover whatever you like. The social + format doesn't use much content at all and is based around just one forum + - this is displayed on the main page.

+

See the help buttons on the Course Settings page for more details.

+ +

 

+

Uploading files

+
+

You may have existing content that you want to add to your course, such as + web pages, audio files, video files, word documents, or flash animations. + Any type of file that exists can be uploaded into your course and stored on + the server. While your files are on the server you can move, rename, edit + or delete them.

+

All of this is achieved through the Files link in your Administration + menu. The Files section looks like this:

+

+

 

+

This interface is only available to teachers - it is not accessible by students. + Individual files are made available to students later on (as "Resources" + - see the next section).

+

As you can see in the screenshot, files are listed alongside subdirectories. + You can create any number of subdirectories to organise your files and move + your files from one to the other.

+

Uploading files via the web is currently restricted to one file at a time. + If you want to upload a lot of files at once (for example a whole web site), + it can be a lot easier to use a zip program to compress them + into a single file, upload the zip file and then unzip them again on the server + (you will see an "unzip" link next to zip archives).

+

To preview any file you have uploaded just click on its name. Your web browser + will take care of either displaying it or downloading it to your computer.

+

HTML and text files can be edited in-place online. Other files will need + to be edited on your local computer and uploaded again. if you upload a file + with the same name as an existing file it will automatically be overwritten.

+

A final note: if your content resides out on the web then you don't need + to upload the files at all - you can link directly to them from inside the + course (see the Resources module and the next section).

+ +

 

+

Setting up activities

+
+

Building a course involves adding course activity modules to the main page + in the order that students will be using them. You can shuffle the order any + time you like.

+

To turn on editing, click "Turn on editing" under Administration. + This toggle switch shows or hides the extra controls that allow you to manipulate + your main course page. Note in the first screenshot above (of the Weekly format + course) that the editing controls are turned on.

+

To add a new activity, simply go to the week or topic or section of the screen + where you want to add it, and select the type of activity from the popup menu. + Here is a summary of all the standard activities in Moodle 1.0:

+
+
Assignment
+
An assignment is where you set a task with a due date and a maximum grade. + Students will be able to upload one file to satisify the requirements. The + date they upload their file is recorded. Afterwards, you will have a single + page on which ou can view each file (and how late or early it is), and then + record a grade and a comment. Half an hour after you grade any particular + student, Moodle will automatically email that student a notification.
+
+
+
Choice
+
A choice activity is very simple - you ask a question and specify a choice + of responses. Students can make their choice, and you have a report screen + where you can see the results. I use it to gather research consent from + my students, but you could use it for quick polls or class votes.
+
+
+
Forum
+
This module is by far the most important - it is here that discussion + takes place. When you add a new forum, yu will presented with a choice of + different types - a simple single-topic discussion, a free-for-all general + forum, or a one-discussion-thread-per-user.
+
+
+
Journal
+
Each journal activity is an entry in the whole course journal. For each + one you can specify an open-ended question that guides what students write, + as well as a window of time in which the journal is open (weekly course + format only). A general rule of thumb is to create one journal per week. + Encourage students to write reflectively and critically in these journals, + as they are only available to them and you. Afterwards, you will be able + to grade and comment all the entries for that week or topic, and students + will receive an automatic email informing them of your feedback. Journals + are not designed to be continually added to - if you need to do that then + add more journal activities.
+
+
+
Resource
+
Resources are the content of your course. Each resource can be any file + you have uploaded or can point to using a URL. You can also maintain simple + text-based pages by typing them directly into a form.
+
+
+
Quiz
+
This module allows you to design and set quiz tests, consisting of multiple + choice, true-false, and short answer questions. These questions are kept + in a categorised database, and can be re-used within courses and even between + courses. Quizzes can allow multiple attempts. Each attempt is automatically + marked, and the teacher can choose whether to give feedback or to show correct + answers. This module includes grading facilities.
+
+
+
Survey
+
The survey module provides a number of predefined survey instruments that + are useful in evaluating and understanding your class. Currently they include + the COLLES and the ATTLS instruments. They can be given to students early + in the course as a diagnostic tool and at the end of the course as an evaluation + tool (I use one every week in my courses).
+
+
+

After adding your activities you can move them up and down in your course + layout by clicking on the little arrow icons ( + ) next to each one. You + can also delete them using the cross icon , + and re-edit them using the edit icon .

+ +

 

+

Running the course

+
+

There are some big plans to extend this document into a more comprehensive + tutorial. Until then here are a few ideas:

+
    +
  1. Subscribe yourself to all the forums so you keep in touch with your class + activity.
    2. +
  2. Encourage all the students fill out their user profile (including photos) + and read them all - this will help provide some context to their later writings + and help you to respond in ways that are tailored to their own needs.
    3. +
  3. Keep notes to yourself in the private "Teacher's Forum" + (under Administration). This is especially useful when team teaching.
    4. +
  4. Use the "Logs" link (under Administration) + to get access to complete, raw logs. In there you'll see a link to a popup + window that updates every sixty seconds and shows the last hour of activity. + This is useful to keep open on your desktop all day so you can feel in touch + with what's going on in the course.
    5. +
  5. Use the "Activity Reports" (next to each name + in the list of all people, or from any user profile page). These provide + a great way to see what any particular person has been up to in the course.
    6. +
  6. Respond quickly to students. Don't leave it for later - do it right away. + Not only is it easy to become overwhelmed with the volume that can be generated, + but it's a crucial part of building and maintaining a community feel in + your course.
    7. +
+ +

 

+

Further information

+
+

If you have any particular problems with your site, you should contact your + local site administrator.

+

If you have some great ideas for improvements to Moodle, or even some good + stories, come over to moodle.org + and join us in the course called "Using + Moodle". We'd love to hear from you, and you can help Moodle improve.

+

If you want to contribute to coding new modules, or writing documentation, + or papers, contact me: Martin + Dougiamas or browse the "bug tracker" site for Moodle, at moodle.org/bugs

+

Thanks for using Moodle - and good luck with your teaching!

+
+

 

+
+

Moodle Documentation

+

Version: $Id: teacher.html,v 1.4 2002/08/18 10:00:01 + martin Exp $

+ + diff --git a/lang/sv/docs/upgrade.html b/lang/sv/docs/upgrade.html index 216a69726e9..230209f5329 100644 --- a/lang/sv/docs/upgrade.html +++ b/lang/sv/docs/upgrade.html @@ -1,125 +1,125 @@ - - Moodle Docs: Upgrading - - - - - - -

Upgrading Moodle

- -

Moodle is designed to upgrade cleanly from any earlier version to any later - version.

-

When upgrading a Moodle installation you should follow these steps:

-

1. Backup important data

-
-

Although it is not strictly necessary, it is always a good idea to make a - backup of any production system before a major upgrade, just in case you need - to revert back to the older version for some reason. In fact, it's a good - idea to automate your server to backup your Moodle installation daily, so - that you can skip this step.

-

There are three areas that need backing up:

-
-

1. The Moodle software directory itself

-
-

Make a separate copy of these files before the upgrade, so that you can - retrieve your config.php and any modules you have added like themes, languages - etc
-

-
-

2. Your data directory.

-
-

This is where uploaded content resides (such as course resources and - student assignments) so it is very important to have a backup of these - files anyway. Sometimes upgrades may move or rename directories within - your data directory.
-

-
-

3. Your database

-
-

Most Moodle upgrades will alter the database tables, adding or changing - fields. Each database has different ways to backup. One way of backing - up a MySQL database is to 'dump' it to a single SQL file. The following - example shows Unix commands to dump the database called "moodle":

-
-

mysqldump moodle > moodle-backup-2002-10-26.sql

-
-

You can also use the "Export" feature in Moodle's optional - "Database" web interface to do the same thing on all platforms.

-

 

-
-
-
- -

2. Install the new Moodle software

-
-

Using a downloaded archive

-
-

Do not overwrite an old installation unless you know what you are doing - ... sometimes old files can cause problems in new installations. The best - way it to rename the current Moodle directory to something else, then unpack - the new Moodle archive into the old location.

-
-

mv moodle moodle.backup
- tar xvzf moodle-1.1.tgz

-
-

Next, copy across your config.php and any other plugins such as custom - themes:

-
-

cp moodle.backup/config.php moodle
- cp -pr moodle.backup/theme/mytheme moodle/theme/mytheme

-
-
-

Using CVS

-
-

If you are using CVS, just go into the Moodle root directory and update - to the new files:

-
-

cvs update -dP

-
-

Make sure you use the "d" parameter to create new directories - if necessary, and the "P" parameter to prune empty directories.

-

If you have been editing Moodle files, watch the messages very closely - for possible conflicts. All your customised themes and non-standard plugins - will be untouched.

-
-

 

-
-

3. Finishing the upgrade

-
-

The last step is to trigger the upgrade processes within Moodle.

-

To do this just visit the admin page of your - installation.

-
-

http://example.com/moodle/admin

-
-

It doesn't matter if you are logged in as admin or not.

-

Moodle will automatically detect the new version and perform all the database - or filesystem upgrades that are necessary. If there is anything it can't do - itself (very rare) then you will see messages telling you what you need to - do.

-
-

 

-

Assuming all goes well (no error messages) then you can start using your new - version of Moodle and enjoy the new features!

-

If you have trouble with the upgrade, visit moodle.org - and post on the Installation - Support Forum in the Using Moodle course.

-

 

-

 

-

Moodle Documentation

-

Version: $Id$

- - + + Moodle Docs: Upgrading + + + + + + +

Upgrading Moodle

+ +

Moodle is designed to upgrade cleanly from any earlier version to any later + version.

+

When upgrading a Moodle installation you should follow these steps:

+

1. Backup important data

+
+

Although it is not strictly necessary, it is always a good idea to make a + backup of any production system before a major upgrade, just in case you need + to revert back to the older version for some reason. In fact, it's a good + idea to automate your server to backup your Moodle installation daily, so + that you can skip this step.

+

There are three areas that need backing up:

+
+

1. The Moodle software directory itself

+
+

Make a separate copy of these files before the upgrade, so that you can + retrieve your config.php and any modules you have added like themes, languages + etc
+

+
+

2. Your data directory.

+
+

This is where uploaded content resides (such as course resources and + student assignments) so it is very important to have a backup of these + files anyway. Sometimes upgrades may move or rename directories within + your data directory.
+

+
+

3. Your database

+
+

Most Moodle upgrades will alter the database tables, adding or changing + fields. Each database has different ways to backup. One way of backing + up a MySQL database is to 'dump' it to a single SQL file. The following + example shows Unix commands to dump the database called "moodle":

+
+

mysqldump moodle > moodle-backup-2002-10-26.sql

+
+

You can also use the "Export" feature in Moodle's optional + "Database" web interface to do the same thing on all platforms.

+

 

+
+
+
+ +

2. Install the new Moodle software

+
+

Using a downloaded archive

+
+

Do not overwrite an old installation unless you know what you are doing + ... sometimes old files can cause problems in new installations. The best + way it to rename the current Moodle directory to something else, then unpack + the new Moodle archive into the old location.

+
+

mv moodle moodle.backup
+ tar xvzf moodle-1.1.tgz

+
+

Next, copy across your config.php and any other plugins such as custom + themes:

+
+

cp moodle.backup/config.php moodle
+ cp -pr moodle.backup/theme/mytheme moodle/theme/mytheme

+
+
+

Using CVS

+
+

If you are using CVS, just go into the Moodle root directory and update + to the new files:

+
+

cvs update -dP

+
+

Make sure you use the "d" parameter to create new directories + if necessary, and the "P" parameter to prune empty directories.

+

If you have been editing Moodle files, watch the messages very closely + for possible conflicts. All your customised themes and non-standard plugins + will be untouched.

+
+

 

+
+

3. Finishing the upgrade

+
+

The last step is to trigger the upgrade processes within Moodle.

+

To do this just visit the admin page of your + installation.

+
+

http://example.com/moodle/admin

+
+

It doesn't matter if you are logged in as admin or not.

+

Moodle will automatically detect the new version and perform all the database + or filesystem upgrades that are necessary. If there is anything it can't do + itself (very rare) then you will see messages telling you what you need to + do.

+
+

 

+

Assuming all goes well (no error messages) then you can start using your new + version of Moodle and enjoy the new features!

+

If you have trouble with the upgrade, visit moodle.org + and post on the Installation + Support Forum in the Using Moodle course.

+

 

+

 

+

Moodle Documentation

+

Version: $Id$

+ + \ No newline at end of file diff --git a/lang/sv/editor.php b/lang/sv/editor.php index 1861bca51c4..c98804cd31e 100644 --- a/lang/sv/editor.php +++ b/lang/sv/editor.php @@ -21,20 +21,25 @@ $string['chooseicon'] = "V $string['close'] = "Stäng"; $string['cols'] = "Kolumner"; $string['copy'] = "Kopiera urvalet"; -$string['createlink'] = "Lägga in en webblänk"; +$string['createfolder'] = "Skapa en mapp "; +$string['createlink'] = "Infoga en webblänk"; $string['cut'] = "Klipp ut urvalet"; +$string['delete'] = "Ta bort"; +$string['filebrowser'] = "Filläsare"; $string['forecolor'] = "Färg på typsnittet"; $string['heading'] = "Rubrik"; +$string['height'] = "Höjd"; $string['hilitecolor'] = "Bakgrundsfärg"; $string['horizontal'] = "Horisontell"; $string['horizontalrule'] = "Horisontell linje (linjal)"; $string['htmlmode'] = "Byt till HTML-källa"; $string['imageurl'] = "URL till bild"; $string['indent'] = "Öka indrag"; -$string['insertchar'] = "Lägg in specialtecken"; -$string['insertimage'] = "Lägg in bild"; -$string['insertsmile'] = "Lägg in en 'smiley'"; -$string['inserttable'] = "Lägg in en tabell"; +$string['insertchar'] = "Infoga specialtecken"; +$string['insertimage'] = "Infoga bild"; +$string['insertlink'] = "Infoga länk"; +$string['insertsmile'] = "Infoga en 'smiley'"; +$string['inserttable'] = "Infoga en tabell"; $string['italic'] = "Kursiv"; $string['justifycenter'] = "Centrera"; $string['justifyfull'] = "Ställ in helrad"; @@ -42,8 +47,19 @@ $string['justifyleft'] = "Justera $string['justifyright'] = "Justera åt höger"; $string['layout'] = "Layout"; $string['left'] = "Vänster"; +$string['linkproperties'] = "Egenskaper för länk"; +$string['linktarget'] = "target"; +$string['linktargetblank'] = "Nytt fönster"; +$string['linktargetnone'] = "Ingen"; +$string['linktargetother'] = "Annan (ur funktion)"; +$string['linktargetself'] = "Samma ram"; +$string['linktargettop'] = "Samma fönster"; +$string['linktitle'] = "Titel"; +$string['linkurl'] = "URL"; $string['middle'] = "Mitten"; +$string['move'] = "Flytta "; $string['normal'] = "Normal"; +$string['notimage'] = "Vald fil är inte en bild. Var snäll och välj en bild!"; $string['notset'] = "Ej angivet"; $string['ok'] = "OK"; $string['orderedlist'] = "Ordnad lista"; @@ -55,10 +71,14 @@ $string['pixels'] = "Pixlar"; $string['popupeditor'] = "Förstora redigeraren"; $string['preformatted'] = "Förformatterad"; $string['preview'] = "Förhandsgranska"; +$string['properties'] = "Egenskaper"; $string['redo'] = "Gör om Din senast aktivitet"; +$string['rename'] = "Byt namn"; $string['right'] = "Höger"; $string['rows'] = "Rader"; +$string['selection'] = "Urval"; $string['showhelp'] = "Hjälp med att använda redigeraren"; +$string['size'] = "Storlek"; $string['spacing'] = "Radavstånd"; $string['strikethrough'] = "Genomstruken"; $string['subscript'] = "Nedsänkt skrift"; @@ -67,10 +87,13 @@ $string['textindicator'] = "Aktuell stil "; $string['textmode'] = "Du är i 'TEXT MODE'. Använd [<>] knappen för att gå tillbaka till 'WYSIWYG MODE'."; $string['texttop'] = "Längst upp på sidan"; $string['top'] = "Upp"; +$string['type'] = "Skriv in"; $string['underline'] = "Understrykning"; $string['undo'] = "Ångra senaste aktivitet"; $string['unorderedlist'] = "Lista med 'ringar'"; +$string['upload'] = "Ladda upp"; $string['vertical'] = "Vertikal"; $string['width'] = "Vidd"; +$string['zip'] = "Zip"; ?> diff --git a/lang/sv/exercise.php b/lang/sv/exercise.php index 411d0052b3a..e6f7b860cbb 100644 --- a/lang/sv/exercise.php +++ b/lang/sv/exercise.php @@ -7,7 +7,8 @@ $string['accumulative'] = "Sammanr $string['action'] = "Åtgärd"; $string['ago'] = "för \$a sedan"; $string['allgradeshaveamaximumof'] = "Alla bedömningar/värderingar/betyg har ett maximum av: \$a"; -$string['amendassessmentelements'] = "Lägg till komponenter för bedömning/värdering/betygssättning"; +$string['amend'] = "Rätta/ändra/utveckla"; +$string['amendassessmentelements'] = "Rätta/ändra/utveckla komponenter för bedömning/värdering/betygssättning"; $string['amendtitle'] = "Rätta/ändra/utveckla titel"; $string['assess'] = "Bedöm/värdera/betygssätt"; $string['assessed'] = "Bedömd/värderad/betygssatt"; @@ -20,6 +21,7 @@ $string['assessments'] = "Bed $string['atthisstageyou'] = "Vid det här laget har Du fullgjort en bedömning/värdering/betygssättning
Du kanske vill ompröva Din eget arbete mot bakgrund av den.
Om Du väljer att göra det så glöm inte att även ompröva Din bedömning/värdering/betygssättning
Du kan göra det genom att klicka på länken för Förnyad bedömning/värdering/betygssättning här nedan."; $string['awaitingassessmentbythe'] = "Väntar på bedömning/värdering/betygssättning av \$a "; $string['awaitingfeedbackfromthe'] = "Väntar på återkoppling från \$a"; +$string['clearlateflag'] = "Ta bort Sen flagga"; $string['comment'] = "Kommentar"; $string['confirmdeletionofthisitem'] = "Bekräfta borttagande av den här \$a"; $string['correct'] = "Rätt"; @@ -91,8 +93,6 @@ $string['phase2'] = "Till $string['phase2short'] = "Öppna"; $string['phase3'] = "Ta inte emot fler bedömningar/värderingar/betygssättningar och inskickade bidrag från \$a "; $string['phase3short'] = "Stängd"; -$string['phase4'] = "Visa sammanfattande/övergripande betyg/omdömen och tabell för rangordning"; -$string['phase4short'] = "Visa"; $string['pleasegradetheassessment'] = "Var snäll och bedöm/värdera/betygssätt bedömningen/värderingen/betygssättningen av det arbete som \$a har bidragit med"; $string['pleasesubmityourwork'] = "Var snäll och använd det här formuläret för att skicka in Ditt arbete"; $string['pleaseusethisform'] = "Var snäll och fyll i hela detta formulär när Du har
har gjort allt som ingår i instruktionen för den övning som visas här nedan ."; @@ -134,7 +134,8 @@ $string['suggestedgrade'] = "F $string['teacherassessment'] = "\$a Bedömning/värdering/betygssättning"; $string['teacherassessmenttable'] = "\$a tabell för bedöming/värdering/betygssättning"; $string['teacherscomment'] = "Distanslärarens kommentar"; -$string['theexerciseandthesubmissionby'] = "Övning och inskickat bidrag av \$a"; +$string['theexercise'] = "Övningsuppgiften"; +$string['theexerciseandthesubmissionby'] = "Övningsuppgift och inskickat bidrag av \$a"; $string['thegradeis'] = "Betyget/omdömet är \$a"; $string['thereisfeedbackfromthe'] = "Det finns återkoppling från \$a"; $string['thisisaresubmission'] = "Det här är ett återinskickat bidrag från \$a
Din bedömning/värdering/betygssättning av deras tidigare inskickade bidrag visas.
När Du har tittat på de senast inskickade bidragen var då snäll och rätta/ändra/komplettera den här bedömningen/värderingen/betygssättningen och klicka på någon av knapparna i sidfoten. "; diff --git a/lang/sv/forum.php b/lang/sv/forum.php index 59640fc5cff..d72a7240a04 100644 --- a/lang/sv/forum.php +++ b/lang/sv/forum.php @@ -73,6 +73,7 @@ $string['nonews'] = "Inga nya inl $string['noposts'] = "Inga inlägg"; $string['nopostscontaining'] = "Det gick inte att hitta några inlägg som innehåller '\$a' "; $string['nosubscribers'] = "Det finns ännu inga prenumeranter på detta forum"; +$string['notingroup'] = "Du måste tyvärr vara med i en grupp för att se detta forum."; $string['nownotsubscribed'] = "\$a->name kommmer INTE få kopior av '\$a->forum' med e-post."; $string['nowsubscribed'] = "\$a->name kommer få kopior av '\$a->forum' med e-post."; $string['numposts'] = "\$a inlägg"; @@ -97,6 +98,8 @@ $string['rating'] = "Bed $string['ratingeveryone'] = "Alla kan bedöma/värdera ett inlägg"; $string['ratingno'] = "Ingen bedömning/värdering"; $string['ratingonlyteachers'] = "Endast \$a kan bedöma/värdera inlägg"; +$string['ratingpublic'] = "\$a kan se allas bedömningar/värderingar"; +$string['ratingpublicnot'] = "\$a kan bara se sina egna bedömningar/värderingar"; $string['ratings'] = "Bedömning/värdering"; $string['ratingssaved'] = "bedömningarna/värderingarna har blivit sparade"; $string['ratingsuse'] = "Använd bedömningar/värderingar "; @@ -106,7 +109,8 @@ $string['readtherest'] = "L $string['replies'] = "Svar:"; $string['repliesmany'] = "\$a svar så långt"; $string['repliesone'] = "\$a svar så långt"; -$string['reply'] = "Besvara"; +$string['reply'] = "Svar"; +$string['replyforum'] = "Svar till forum"; $string['search'] = "Sök"; $string['searchforums'] = "Sök forum"; $string['searcholderposts'] = "Sök äldre inlägg..."; diff --git a/lang/sv/glossary.php b/lang/sv/glossary.php index c64c5680006..9ed518444fd 100644 --- a/lang/sv/glossary.php +++ b/lang/sv/glossary.php @@ -95,6 +95,7 @@ $string['exportglossary'] = "Exportera ord- och begreppslista"; $string['exporttomainglossary'] = "Exportera till den övergripande (förklarande) ord- och begreppslistan"; $string['filetoimport'] = "Fil att importera"; $string['fillfields'] = "'Begrepp' och definition' är obligatoriska fält"; +$string['filtername'] = "Länka ord- och begreppslista automatiskt "; $string['fullmatch'] = "Matcha hela ord bara
när de är automatiskt länkade"; $string['glossarytype'] = "Typ av ord- och begreppslista"; $string['glosssaryexported'] = "Ord- och begreppslistan har exporterats"; diff --git a/lang/sv/help/quiz/multianswer.html b/lang/sv/help/quiz/multianswer.html index ea850c7f7bc..5cc7aeab4d3 100644 --- a/lang/sv/help/quiz/multianswer.html +++ b/lang/sv/help/quiz/multianswer.html @@ -40,7 +40,7 @@ Det här exemplet kommer att visas för studenterna/eleverna/deltagarna/

3

8 Betyg


Den här frågan består av lite text med ett svar är inbäddat precis här och omedelbart efter det så måste Du ta itu med det här kortsvaret och slutligen har vi ett flyttal .

-Lägg märke till att adresser som www.moodle.org och smilies fungerar som vanligt:
+Lägg märke till att adresser som www.moodle.org och smilies :-) fungerar som vanligt:
a) Hur bra är det här?
b) Vilket betyg/omdöme skulle Du ge det?

diff --git a/lang/sv/moodle.php b/lang/sv/moodle.php index af8ef0cf679..6a226e7d9a4 100644 --- a/lang/sv/moodle.php +++ b/lang/sv/moodle.php @@ -3,6 +3,7 @@ $string['action'] = "Åtgärd"; +$string['active'] = "Aktiv"; $string['activities'] = "Aktiviteter"; $string['activity'] = "Aktivitet"; $string['activityclipboard'] = "Flyttar denna aktivitet \$a"; @@ -40,18 +41,23 @@ redigera valfritt konto."; $string['adminhelplanguage'] = "För att kontrollera och redigera det aktuella språkpaketet."; $string['adminhelplogs'] = "Gå igenom dokumentationen (loggarna)för alla aktiviteter på webbplatsen."; $string['adminhelpmanagedatabase'] = "Direkt åtkomst till databasen. Var försiktig!"; +$string['adminhelpmanagefilters'] = "Välj textfilter och därmed sammanhängande inställningar"; $string['adminhelpmanagemodules'] = "Administrera de installerade modulerna och deras inställningar."; $string['adminhelpsitefiles'] = "För att publicera allmänna filer eller ladda upp externa backuper."; $string['adminhelpsitesettings'] = "Definiera hur den första sidan på webbplatsen ska se ut."; $string['adminhelpthemes'] = "Välj hur webbplatsen ska se ut (färger, typsnitt osv)"; +$string['adminhelpuploadusers'] = "Importera nya användarkonton från en textfil"; $string['adminhelpusers'] = "Definiera Dina användare och sätt upp autenticering."; $string['administration'] = "Administration"; $string['administrator'] = "Administratör"; $string['administrators'] = "Administratörer"; +$string['advancedfilter'] = "Avancerade filter"; $string['again'] = "Igen"; $string['all'] = "Alla"; +$string['allactivities'] = "Alla aktiviteter"; $string['alldays'] = "Alla dagar"; $string['allfieldsrequired'] = "Alla fält krävs"; +$string['allgroups'] = "Alla grupper"; $string['alllogs'] = "Alla loggar"; $string['allow'] = "Tillåt"; $string['allowguests'] = "Denna kurs tillåter gäster"; @@ -77,13 +83,21 @@ $string['autosubscribeyes'] = "Ja. Registrera mig som prenumerant n $string['availability'] = "Tillgänglighet"; $string['availablecourses'] = "Tillgängliga kurser"; $string['backup'] = "Backup"; +$string['backupcoursefileshelp'] = "För att välja om Du vill ta med kursfiler i backupen"; $string['backupdate'] = "Datum för backup"; $string['backupdetails'] = "Detaljerad info om backup"; $string['backupfilename'] = "backup"; $string['backupfinished'] = "Backup framgångsrikt avslutad"; +$string['backupincludemoduleshelp'] = "För att välja om Du vill ta med kursmoduler med eller utan användardata i backupen"; +$string['backupkeephelp'] = "För att välja hur många backup-filer för varje kurs som Du vill ha kvar på hårddisken. (de äldsta tas automatiskt bort)"; +$string['backuplogshelp'] = "För att välja om Du vill ta med loggarna till kursen i backupen"; $string['backupnameformat'] = "%%Y%%m%%d-%%H%%M"; $string['backuporiginalname'] = "Namn på backup-kopian"; +$string['backupsavetohelp'] = "Hela sökvägen till katalogen där Du vill spara backup-filerna
Om Du vill spara dem i standardkatalogen så behöver Du inte fylla i något här."; +$string['backupuserfileshelp'] = "För att välja om Du vill ta med användarfiler (avatarer) i backupen"; +$string['backupusershelp'] = "För att välja om Du vill ta med alla användare på servern eller bara användarna av den aktuella kursen i backupen"; $string['backupversion'] = "Backup-kopians version"; +$string['bycourseorder'] = "Ordna enligt kurser"; $string['cancel'] = "Återställ"; $string['categories'] = "Kurskategorier"; $string['category'] = "Kategori"; @@ -102,17 +116,21 @@ $string['choose'] = "V $string['choosecourse'] = "Välj en kurs"; $string['chooselivelogs'] = "Eller se på nuvarande aktivitet"; $string['chooselogs'] = "Välj vilka loggar Du vill se"; +$string['choosereportfilter'] = "Välj ett filter för rapporten"; $string['choosetheme'] = "Välj layouttema"; $string['chooseuser'] = "Välj en användare"; -$string['city'] = "Stad"; +$string['city'] = "Stad/ort"; $string['cleaningtempdata'] = "Tömmer tillfälliga data"; +$string['clicktochange'] = "Klicka för att ändra"; $string['closewindow'] = "Stäng detta fönster"; $string['comparelanguage'] = "Jämför och redigera det aktuella språket"; $string['complete'] = "Komplett"; $string['configallowunenroll'] = "Om detta är inställt till 'Ja' då kan studenterna/eleverna/deltagarna/de lärande avregistrera sig när de vill. Annars får de inte göra det och denna process kontrolleras istället av (distans)lärare och administratörer."; +$string['configcachetext'] = "Den här inställningen kan verkligen snabba på saker och ting på stora webbplatser eller platser som använder textfilter. Kopior av texter kommer att bli kvar i sin processade form under den tid som Du anger här. Om Du ställer in ett för lågt värde så kan det faktiskt gå lite långsammare men om Du ställer in ett alltför högt värde så kommer det att ta för lång tid att uppdatera texterna (med nya länkar t ex)."; $string['configcountry'] = "Om Du har valt ett land här så kommer detta land att vara förvalt när nya användarkonton skapas. Om Du vill att användarna själva ska välja land så får Du avstå från att markera ett förval."; $string['configdebug'] = "Om Du aktiverar det här så utökar Du PHP:s felrapportering. Systemet ger då ifrån sig fler varningar. Detta är av värde bara för utvecklare."; $string['configerrorlevel'] = "Välj det antal PHP-varningar som Du vill låta visas. 'Normalt' är vanligtvis det bästa valet."; +$string['configforcelogin'] = "I normalfallet så kan folk, utan att logga in, se webbplatsens första sida och listan över kurser (men inte kurserna). Om Du vill tvinga dem att logga in innan de kan se någonting alls på webbplatsen så ska Du aktivera den här inställningen."; $string['configframename'] = "Om Du lägger in Moodle i en ram så skriver Du in namnet på denna ram här. Annars bör Du låta värdet '_top' stå kvar."; $string['configfullnamedisplay'] = "Detta definierar hur fullständiga namn visas. För de flesta enspråkiga webbplatser är standardinställningen 'För- och efternamn' den bästa, men Du kan välja att dölja efternamnet helt och hållet eller låta det aktuella språkpaketet avgöra (en del språk har olika konventioner)."; $string['configgdversion'] = "Detta indikerar vilken version av GD som är installerad. Versionen som visas som standard är den som har blivit automatiskt upptäckt. Ändra inte på detta, såvida Du inte verkligen vet vad Du gör."; @@ -130,6 +148,7 @@ $string['configloglifetime'] = "Detta specificerar hur l $string['configlongtimenosee'] = "Om studenter/elever/deltagare/lärande inte har loggat in på mycket lång tid, så kommer de automatiskt att tas bort från kurser. Denna parameter specificerar den tidsbegränsningen."; $string['configmaxbytes'] = "Detta specificerar den övergipande maximala storleken på bifogade filer på hela webbsajten. Den här inställningen begränsas av inställningen i PHP-funktionen upload_max_filesize och inställningen i Apache-funktionen LimiRequestBody. Därutöver så begränsar 'maxbytes' vilken skala som kan väljas på kurs- eller modulnivå. "; $string['configmaxeditingtime'] = "Detta specificerar tiden folk har på sig att redigera om sina foruminlägg, journalåterkopplingar etc. Vanligtvis är 30 minuter tillräcklig tid."; +$string['configopentogoogle'] = "Om Du aktiverar den här inställningen så tillåter Du att Google går in på Din webbplats som gäst(Guest). Dessutom kommer till Din webbplats via en Googlesökning att automatiskt loggas in som gäst. Lägg märke till att detta ger tillträde till kurser som redan tillåter åtkomst för gäster."; $string['configproxyhost'] = "Om denna server behöver en proxy (t.ex. en brandvägg) för att nå Internet, ange då proxyns namn (hostname) och port här. Låt det annars vara tomt."; $string['configsecureforms'] = "Moodle kan använda ytterligare en säkerhetsnivå när systemet tar emot data från ett formulär. Om detta är aktiverat så jämförs webbläsarens variabel HTTP_REFERER med det aktuella formulärets adress. I några enstaka fall kan det ge upphov till problem om användaren utnyttjar en brandvägg (t ex Zonealarm) som är inställd på att ta bort HTTP_REFERER från sin webbtrafik,. Symptom på detta är att man \\\"fastnar\\\" på ett formulär. Om Dina användare har problem med loginsidan så kanske Du vill avaktivera den här inställningen även om det öppnar Din sajt för lösenordsattacker. Om Du är tveksam så är det bäst att låta inställningen 'Ja' vara kvar."; $string['configsessioncookie'] = "Med den här inställningen kan Du ändra namnet på den 'cookie' som används för sessioner i Moodle. Detta är valfritt och behövs egentligen bara när Du kör fler än en instans (kopia) av Moodle på samma webbplats."; @@ -138,6 +157,7 @@ $string['configslasharguments'] = "Filer (bilder, uppladdade filer etc) tillhand $string['configsmtphosts'] = "Ange fullständigt namn på en eller flera lokala SMTP-servrar som Moodle skall använda för att sända e-post (t.ex. 'mail.a.com' eller 'mail.a.com;mail.b.com'). Om Du lämnar det tomt, kommer Moodle att använda standardmetoden för PHP att skicka e-post."; $string['configsmtpuser'] = "Om Du har angivit en SMTP-server ovan, och servern kräver autenticering, så ska Du skriva in användarnamn och lösenord här."; $string['configteacherassignteachers'] = "Ska \\\"vanliga\\\" distanslärare/handledare/coacher tillåtas utse andra distanslärare/handledare/coacher inom de kurser som de leder? Om svaret är 'Nej' så kan bara kursutvecklare och administratörer utse distanslärare/handledare/coacher etc. "; +$string['configtimezone'] = "Du kan ställa in standardvärdet för tidzon här. Det här är det enda standardvärdet för tidzon som visar datum - varje användare kan ändra denna inställning i sin egen Profil. \\\"Servertid\\\" här ställer in Moodles standardvärde i förhållande till serverns operativsystem. men \\\"Servertid\\\" i användarens Profil kommer att ställa användarens standardvärde till detta värde."; $string['configunzip'] = "Ange var Ditt unzip-program finns.(endast Unix). Detta behövs när Du packar upp ziparkiv på servern."; $string['configuration'] = "Konfiguration"; $string['configvariables'] = "Konfigurera variabler"; @@ -175,6 +195,8 @@ $string['createuserandpass'] = "Skapa ett nytt anv $string['createziparchive'] = "Skapa ziparkiv"; $string['creatingcategoriesandquestions'] = "Skapar kategorier och frågor..."; $string['creatingcoursemodules'] = "Skapar kursmoduler..."; +$string['creatingevents'] = "Skapar händelser"; +$string['creatinggroups'] = "Skapar grupper"; $string['creatinglogentries'] = "Skapar log 'entries'..."; $string['creatingnewcourse'] = "Skapar en ny kurs..."; $string['creatingscales'] = "Skapar skalor..."; @@ -194,6 +216,8 @@ $string['databasesetup'] = "S $string['databasesuccess'] = "Databasen har uppgraderats"; $string['databaseupgradebackups'] = "Backup-versionen är nu \$a"; $string['databaseupgrades'] = "Uppgraderar databas..."; +$string['datemostrecentfirst'] = "Datum - det senast först"; +$string['datemostrecentlast'] = "Datum - det senast sist"; $string['day'] = "dag"; $string['days'] = "dagar"; $string['defaultcoursefullname'] = "Det kompletta namnet på kursen"; @@ -204,6 +228,7 @@ $string['defaultcoursesummary'] = "H $string['defaultcourseteacher'] = "Distanslärare/handledare/coach etc"; $string['defaultcourseteachers'] = "Distanslärare/handledare/coacher etc"; $string['delete'] = "Ta bort"; +$string['deleteall'] = "Ta bort alla"; $string['deletecheck'] = "Ta bort \$a ?"; $string['deletecheckfiles'] = "Är Du säker på att Du vill ta bort de här filerna?"; $string['deletecheckfull'] = "Är Du säker på att Du vill ta bort hela \$a ? "; @@ -215,21 +240,25 @@ $string['deleted'] = "Borttaget"; $string['deletedactivity'] = "Tog bort \$a"; $string['deletedcourse'] = "\$a har tagits bort helt"; $string['deletednot'] = "Kunde inte ta bort \$a !"; +$string['deleteselected'] = "Du har valt \\\"Ta bort\\\""; $string['deletingcourse'] = "Tar bort \$a"; $string['deletingexistingcoursedata'] = "Tar bort befintliga kursdata"; $string['deletingolddata'] = "Tar bort gamla data"; $string['department'] = "Avdelning"; $string['description'] = "Beskrivning"; +$string['disable'] = "Avaktivera"; $string['displayingfirst'] = "Bara de första \$a->count \$a->things visas."; $string['displayingrecords'] = "Visar \$a poster"; $string['displayingusers'] = "Visar användare \$a->start till \$a->end"; $string['documentation'] = "Dokumentation av Moodle"; $string['donotask'] = "Fråga inte"; +$string['down'] = "Ner"; $string['downloadexcel'] = "Ladda ner i Excelformat"; $string['downloadtext'] = "Ladda ner i textformat"; $string['doyouagree'] = "Har Du läst dessa villkor och förstått dem?"; $string['edit'] = "Redigera \$a"; $string['editcoursesettings'] = "Redigera kursinställningar"; +$string['editgroupprofile'] = "Redigera grupp-profil"; $string['editinga'] = "Redigera \$a"; $string['editmyprofile'] = "Redigera profil"; $string['editsummary'] = "Redigera summeringen"; @@ -237,6 +266,7 @@ $string['editthisactivity'] = "Redigera denna aktivitet"; $string['editthiscategory'] = "Redigera denna kategori"; $string['edituser'] = "Redigera användarkonton"; $string['email'] = "E-postadress"; +$string['emailagain'] = "E-post (igen)"; $string['emailconfirm'] = "Bekräfta Ditt konto"; $string['emailconfirmation'] = "Hej \$a->firstname!

@@ -254,10 +284,12 @@ $string['emailconfirmationsubject'] = "\$a: bekr $string['emailconfirmsent'] = "

Vi har skickat ett e-postbrev till Din adress på \$a

Det innehåller enkla instruktioner som hjälper Dig att fullfölja Din registrering.

Om Du stöter på problem, är Du välkommen att kontakta den som ansvarar för webbplatsen, \$a->admin.

"; +$string['emaildisable'] = "Den här e-postadressen är avaktiverad"; $string['emaildisplay'] = "Visning av e-post"; $string['emaildisplaycourse'] = "Tillåt endast andra kursdeltagare att se min e-postadress"; $string['emaildisplayno'] = "Göm min riktiga e-postadress för alla"; $string['emaildisplayyes'] = "Tillåt alla att se min e-postadress"; +$string['emailenable'] = "Den här e-postadressen är redan registrerad"; $string['emailexists'] = "Din e-postadress är redan registrerad."; $string['emailformat'] = "E-post format"; $string['emailmustbereal'] = "Obs: Din e-postadress måste vara giltig"; @@ -279,6 +311,9 @@ $string['emailpasswordconfirmsent'] = "

Vi har skickat ett e-postbrev till Din "; $string['emailpasswordsent'] = "Tack för att Du bekräftade bytet av lösenord.

Vi har skickat ett e-postbrev som innehåller lösenordet till Din adress på \$a->email

Det nya lösenordet har skapats automatiskt - Du kanske vill link>byta Ditt lösenord till något som är lättare att komma ihåg"; +$string['enable'] = "Aktivera"; +$string['enrolledincourse'] = "Registerad på kurs \\\"\$a\\\""; +$string['enrolledincoursenot'] = "Inte registerad på kurs \\\"\$a\\\""; $string['enrolmentconfirmation'] = "Du håller på att registrera Dig som student/elev/deltagare/lärande på denna kurs.
Är Du säker på att Du vill fullfölja detta?"; $string['enrolmentkey'] = "Kursnyckel"; $string['enrolmentkeyfrom'] = "Denna kurs kräver en 'kursnyckel' -
@@ -291,6 +326,7 @@ l $string['error'] = "Fel"; $string['errortoomanylogins'] = "Du har tyvärr försökt logga in för många gånger. Starta om Din webbläsare och försök igen."; $string['errorwhenconfirming'] = "Du är inte bekräftad ännu eftersom det uppstod ett fel. Om Du klickade på en länk i ett e-postmeddelande för att komma hit så får Du kolla att raden med länken inte var uppdelad på två rader. Du kanske måste \\\"klippa och klistra\\\" för att forma länken på rätt sätt."; +$string['executeat'] = "Genomför vid"; $string['existing'] = "Finns"; $string['existingadmins'] = "Befintliga administratörer"; $string['existingcourse'] = "Befintlig kurs"; @@ -309,6 +345,10 @@ $string['firstname'] = "F $string['firsttime'] = "Är det första gången Du är här?"; $string['followingoptional'] = "Följande punkter är valfria"; $string['followingrequired'] = "Följande punkter krävs"; +$string['force'] = "Tvinga"; +$string['forcedmode'] = "Tvingande \\\"mode\\\""; +$string['forcelanguage'] = "Tvingande språkval"; +$string['forceno'] = "Tvinga inte"; $string['forgotten'] = "Har Du glömt Ditt användarnamn och lösenord?"; $string['format'] = "Format"; $string['formathtml'] = "HTML-format"; @@ -349,6 +389,25 @@ UTAN VARJE FORM AV GARANTI http://www.gnu.org/copyleft/gpl.html"; $string['grade'] = "Betyg"; $string['grades'] = "Betyg"; +$string['group'] = "Grupp"; +$string['groupadd'] = "Lägg till en ny grupp"; +$string['groupaddusers'] = "Lägg till det valda till grupp"; +$string['groupinfo'] = "Info om vald grupp"; +$string['groupinfomembers'] = "Info om valda medlemmar"; +$string['groupinfopeople'] = "Info om valda personer"; +$string['groupmemberssee'] = "Visa gruppmedlemmar"; +$string['groupmembersselected'] = "Medlemmar i vald grupp"; +$string['groupmode'] = "Grupp mode"; +$string['groupmodeforce'] = "grupp mode"; +$string['groupmy'] = "Min grupp"; +$string['groupnonmembers'] = "Personer som inte är med i någon grupp"; +$string['grouprandomassign'] = "Dela slumpmässigt in alla i grupper"; +$string['groupremove'] = "Ta bor vald grupp"; +$string['groupremovemembers'] = "Ta bort valda medlemmar"; +$string['groups'] = "Grupper"; +$string['groupsnone'] = "Inga grupper"; +$string['groupsseparate'] = "Olika grupper"; +$string['groupsvisible'] = "Synliga grupper"; $string['guestskey'] = "Tillåt gäster som har nyckeln"; $string['guestsno'] = "Tillåt inte gäster "; $string['guestsnotallowed'] = "Tyvärr, '\$a' tillåter inte gäster."; @@ -369,6 +428,7 @@ $string['helptext'] = "Hur Du skriver text"; $string['helpwiki'] = "Hur Du skriver Wiki-text"; $string['helpwriting'] = "Skriv noggrant"; $string['hide'] = "Dölj"; +$string['hidepicture'] = "Dölj bild"; $string['hits'] = "Besök"; $string['hitsoncourse'] = "Besök på \$a->coursename av \$a->username"; $string['hitsoncoursetoday'] = "Dagens besök på \$a->coursename av \$a->username"; @@ -384,17 +444,21 @@ $string['htmleditordisabledbrowser'] = "Richtext editor $string['htmlformat'] = "Snyggt HTML- format"; $string['icqnumber'] = "ICQ nummer"; $string['idnumber'] = "ID nummer"; +$string['inactive'] = "Inaktiv"; $string['include'] = "Ta med"; $string['includeallusers'] = "Ta med alla användare"; $string['includecoursefiles'] = "Ta med all kursfiler"; $string['includecourseusers'] = "Ta med alla lärande"; $string['included'] = "Ingår"; $string['includelogentries'] = "Ta med logbidrag"; +$string['includemodules'] = "Ta med Moduler"; $string['includeneededusers'] = "Ta med 'behövda' användare"; $string['includeuserfiles'] = "Ta med användarfiler"; +$string['institution'] = "Institution"; $string['invalidemail'] = "Ogiltig e-postadress"; $string['invalidlogin'] = "Ogiltig login, var vänlig försök igen"; $string['jumpto'] = "Hoppa till..."; +$string['keep'] = "Behåll"; $string['langltr'] = "Språkriktning vänster-till-höger"; $string['langrtl'] = "Språkriktning höger-till-vänster"; $string['language'] = "Språk"; @@ -470,6 +534,7 @@ $string['mainmenu'] = "Huvudmeny"; $string['makeafolder'] = "Skapa en mapp"; $string['makeeditable'] = "Om Du gör '\$a' redigerbar via webbservern (t.ex. apache) så kan Du redigera denna fil direkt från denna sida."; $string['managedatabase'] = "Databas"; +$string['managefilters'] = "Filter"; $string['managemodules'] = "Moduler"; $string['markedthistopic'] = "Det här ämnet är markerat som det just nu aktuella ämnet."; $string['markthistopic'] = "Markera detta ämne som aktuellt ämne"; @@ -489,6 +554,7 @@ $string['missingemail'] = "E-postadress saknas"; $string['missingfirstname'] = "Förnamn saknas"; $string['missingfullname'] = "Hela namnet saknas"; $string['missinglastname'] = "Efternamn saknas"; +$string['missingname'] = "Ett namn saknas"; $string['missingnewpassword'] = "Nytt lösenord saknas"; $string['missingpassword'] = "Lösenord saknas"; $string['missingshortname'] = "Kort namn saknas"; @@ -579,6 +645,7 @@ $string['nopotentialcreators'] = "Inga m $string['nopotentialstudents'] = "Inga möjliga studenter/elever/deltagare/lärande "; $string['nopotentialteachers'] = "Inga möjliga distanslärare/handledare/coacher"; $string['normal'] = "Normal"; +$string['normalfilter'] = "Normalt filter"; $string['nostudentsfound'] = "Hittade ingen/inga \$a"; $string['nostudentsyet'] = "Inga studenter/elever/deltagare/lärande har antagits till denna kurs ännu"; $string['nosuchemail'] = "Ingen sådan e-postadress"; @@ -595,6 +662,7 @@ $string['numberweeks'] = "Antalet veckor/teman"; $string['numdays'] = "\$a dagar"; $string['numhours'] = "\$a timmar"; $string['numminutes'] = "\$a minuter"; +$string['numseconds'] = "\$a sekunder"; $string['numviews'] = "\$a besök"; $string['numweeks'] = "\$a veckor"; $string['numwords'] = "\$a ord"; @@ -629,6 +697,7 @@ $string['potentialteachers'] = "M $string['preferredlanguage'] = "Föredraget språk"; $string['preview'] = "Förhandsgranska"; $string['previeworchoose'] = "Förhandsgranska eller välj ett tema"; +$string['previous'] = "Tidigare"; $string['publicdirectory'] = "Offenligt bibliotek"; $string['publicdirectory0'] = "Var snäll och publicera inte den här webbplatsen"; $string['publicdirectory1'] = "Publicera bara webbplatsens namn"; @@ -667,6 +736,7 @@ $string['returningtosite'] = " $string['revert'] = "Återgå"; $string['role'] = "Roll"; $string['savechanges'] = "Spara ändringar"; +$string['saveto'] = "Spara i"; $string['scale'] = "Skala"; $string['scales'] = "Skalor"; $string['scalescustom'] = "Egendefinierade skalor"; @@ -674,6 +744,8 @@ $string['scalescustomcreate'] = "L $string['scalescustomno'] = "Inga egendefinierade skalor har ännu lagts till"; $string['scalesstandard'] = "Standardskalor"; $string['scalestip'] = "För att skapa egendefinierade skalor så får Du använda länken 'Skalor' på menyn för administration av Din kurs."; +$string['schedule'] = "Schema"; +$string['scheduledbackupstatus'] = "Status för schemalagd backup"; $string['search'] = "Sök"; $string['searchagain'] = "Sök igen"; $string['searchcourses'] = "Sök kurser"; @@ -721,6 +793,7 @@ $string['sizemb'] = "Mb"; $string['socialheadline'] = "Gemenskapsforum - senaste tema"; $string['someallowguest'] = "Några kurser kan tillåta gäster"; $string['someerrorswerefound'] = "Några uppgifter saknades eller var felaktiga. Se nedan för detaljer."; +$string['sortby'] = "Sortera enligt"; $string['startdate'] = "Kursens startdatum"; $string['startsignup'] = "Starta nu genom att skapa ett nytt konto!"; $string['state'] = "Stat/region"; @@ -778,6 +851,7 @@ $string['unsafepassword'] = "Os $string['unusedaccounts'] = "Konton som inte har använts på mer än \$a dagar tas automatiskt bort"; $string['unzip'] = "Packa upp"; $string['unzippingbackup'] = "Packar upp backup"; +$string['up'] = "Upp"; $string['update'] = "Uppdatera"; $string['updated'] = "Uppdaterat \$a"; $string['updatemyprofile'] = "Uppdatera profil"; @@ -792,6 +866,7 @@ $string['uploadedfileto'] = "Laddade upp \$a->file till \$a->directory"; $string['uploadnofilefound'] = "Hittade ingen fil - är Du säker på att Du valde en att ladda upp?"; $string['uploadproblem'] = "Ett okänt fel inträffade under uppladdning av filen \$a (kanske var den för stor?)"; $string['uploadthisfile'] = "Ladda upp denna fil"; +$string['uploadusers'] = "Ladda upp användare"; $string['user'] = "Användare"; $string['userdeleted'] = "Ditt användarkonto har tagits bort"; $string['userdescription'] = "Beskrivning"; @@ -800,6 +875,7 @@ $string['username'] = "Anv $string['usernameexists'] = "Detta användarnamn existerar redan, välj ett annat"; $string['userprofilefor'] = "Användarprofil för \$a"; $string['users'] = "Användare"; +$string['usersnew'] = "Nya användare"; $string['userzones'] = "Användar-zoner"; $string['usingexistingcourse'] = "Använder befintlig kurs"; $string['version'] = "Version"; @@ -830,7 +906,9 @@ $string['wordforteachers'] = "Ditt ord f $string['wordforteacherseg'] = "t ex (distans)lärare, ledare, koordinatörer, utbildare, handledare, coacher etc"; $string['writingcategoriesandquestions'] = "Skriver kategorier och frågor"; $string['writingcoursedata'] = "Skriver kursdata"; +$string['writingeventsinfo'] = "Skriver info om händelser"; $string['writinggeneralinfo'] = "Skriver allmän information"; +$string['writinggroupsinfo'] = "Skriver info om grupper"; $string['writingheader'] = "Skriver huvudrubrik"; $string['writingloginfo'] = "Skriver info om loggar"; $string['writingmoduleinfo'] = "Skriver info om moduler"; diff --git a/lang/sv/quiz.php b/lang/sv/quiz.php index 8c0d12486e7..21fca07a855 100644 --- a/lang/sv/quiz.php +++ b/lang/sv/quiz.php @@ -17,9 +17,11 @@ $string['answerhowmany'] = "Ett eller flera svar?"; $string['answersingleno'] = "Flera svar tillåtna"; $string['answersingleyes'] = "Endast ett svar "; $string['answerswithacceptederrormarginmustbenumeric'] = "Bara numeriska svar kan ha felmarginal"; +$string['answertoolong'] = "Svaret är för långt efter rad \$a (max 255 tecken)"; $string['aon'] = "AON-format"; $string['attempt'] = "Försök \$a"; $string['attemptfirst'] = "Första försök"; +$string['attemptincomplete'] = "Det här försöket (av \$a) är ännu inte avslutat"; $string['attemptlast'] = "Senaste försök"; $string['attemptquiznow'] = "Påbörja försök av testet nu"; $string['attempts'] = "Försök"; @@ -28,6 +30,7 @@ $string['attemptsunlimited'] = "Obegr $string['backtoquiz'] = "Tillbaka till redigering av test"; $string['bestgrade'] = "Bästa betyget"; $string['blackboard'] = "Svarta tavlan"; +$string['calculatedquestion'] = "Beräknad fråga stödjs inte på rad \$a. Hänsyn kommer inte att tas till frågan."; $string['caseno'] = "Nej, stor eller liten bokstav spelar ingen roll"; $string['casesensitive'] = "Stor eller liten bokstav gör skillnad"; $string['caseyes'] = "Ja, stor /liten bokstav måste matcha exakt"; @@ -52,6 +55,7 @@ $string['daysavailable'] = "Dagar tillg $string['default'] = "Standard"; $string['defaultgrade'] = "Normalpoäng"; $string['defaultinfo'] = "Standardkategori för frågor."; +$string['deleteattemptcheck'] = "Är Du helt säker på att Du vill ta bort de här försöken för gott?"; $string['deletequestioncheck'] = "Är Du helt säker på att Du vill ta bort '\$a'?"; $string['description'] = "Beskrivning"; $string['discrimination'] = "Diskrim. Index"; @@ -69,6 +73,7 @@ $string['editingrandomsamatch'] = "Redigera en para_ihop-fr $string['editingshortanswer'] = "Redigera en kortsvars-fråga"; $string['editingtruefalse'] = "Redigera en sant/falskt-fråga"; $string['editquestions'] = "Redigera frågor"; +$string['errorsdetected'] = "\$a fel har upptäckts"; $string['false'] = "Falskt"; $string['feedback'] = "Återkoppling"; $string['fileformat'] = "Filformat"; @@ -87,6 +92,7 @@ $string['gradehighest'] = "H $string['grademethod'] = "Betygsättningsmetod"; $string['guestsno'] = "Tyvärr, gäster kan inte se eller göra test"; $string['imagedisplay'] = "Bild att visa"; +$string['imagemissing'] = "Ingen bild tillgänglig på rad \$a. Hänsyn kommer inte att tas till filnamnet. "; $string['importquestions'] = "Importera frågor från fil"; $string['indivresp'] = "Individers svarsreaktioner på varje del"; $string['introduction'] = "Introduktion"; @@ -95,8 +101,10 @@ $string['listitems'] = "Lista p $string['marks'] = "Poäng"; $string['match'] = "Para_ihop"; $string['matchanswer'] = "Svara på para_ihop-fråga"; +$string['missinganswer'] = "För få : SVAR,´:Lx, :Rx satser för frågerad \$a. Du måste definiera minst 2 möjliga svar."; $string['missingcorrectanswer'] = "Du måste ange rätt svar "; $string['missingname'] = "Frågan saknar namn "; +$string['missingquestion'] = "Det saknas en frågeetikett efter rad \$a"; $string['missingquestiontext'] = "Du har inte angivit själva frågan"; $string['missingword'] = "Lucktext"; $string['modulename'] = "Test"; @@ -114,12 +122,14 @@ $string['noreviewuntil'] = "Du f $string['notenoughsubquestions'] = "Otillräckligt antal delfrågor!
Vill Du gå tillbaka och rätta till den här frågan?"; $string['numerical'] = "Numerisk"; +$string['paragraphquestion'] = "Stycke-fråga stödjs inte på rad \$a. Hänsyn kommer inte att tas till frågan "; $string['percentcorrect'] = "Rätt procent"; $string['publish'] = "Publicera"; $string['qti'] = "IMS QTI format"; $string['question'] = "Fråga"; $string['questioninuse'] = "För närvarande används frågan '\$a' :"; $string['questionname'] = "Frågans namn"; +$string['questionnametoolong'] = "Frågans namn är för långt på rad \$a (max 255 tecken). Namnet har trunkerats."; $string['questions'] = "Frågor"; $string['quizavailable'] = "Detta test är tillgängligt till: \$a"; $string['quizclose'] = "Stäng testet"; @@ -169,10 +179,13 @@ $string['toomanyrandom'] = "Antalet fr $string['true'] = "Sant"; $string['truefalse'] = "Sant/Falskt"; $string['type'] = "Typ"; +$string['unknowntype'] = "Frågetypen stödjs inte på rad \$a. Hänsyn kommer inte att tas till frågan."; $string['viewallanswers'] = "Visa \$a genomförda test"; $string['viewallreports'] = "Visa rapporter för \$a försök"; +$string['warningsdetected'] = "\$a varningar har upptäckts"; $string['webct'] = "WebCT format"; $string['withsummary'] = "med sammanfattande statistik"; +$string['wronggrade'] = "Fel betyg (efter rad \$a)"; $string['yourfinalgradeis'] = "Ditt slutgiltiga betyg för detta test är \$a"; ?> diff --git a/lang/sv/resource.php b/lang/sv/resource.php index 785fe45b52b..8bec1e01ba3 100644 --- a/lang/sv/resource.php +++ b/lang/sv/resource.php @@ -18,6 +18,7 @@ $string['configpopupstatus'] = "Ska det f $string['configpopuptoolbar'] = "Ska det förinställda standardvalet vara att nya 'popup'-fönster visar verktygsraden?"; $string['configpopupwidth'] = "Vilket ska det förinställda standardvalet för bredden på nya 'popup'-fönster vara? "; $string['configwebsearch'] = "När Du lägger till en URL som en webbsida eller en webblänk så erbjuds användaren denna plats som en webbsajt. Detta för att hjälpa användaren att hitta det denne söker. "; +$string['directlink'] = "Direktlänk till den här filen"; $string['editingaresource'] = "Redigera en resurs"; $string['example'] = "Exempel"; $string['examplereference'] = "Tobin, K. & Tippins, D (1993) Constructivism as a Referent for Teaching and Learning. In: K. Tobin (Ed) The Practice of Constructivism in Science Education, pp 3-21, Lawrence-Erlbaum, Hillsdale, NJ."; @@ -46,6 +47,8 @@ $string['newwindowopen'] = "Visa den h $string['note'] = "OBS"; $string['notefile'] = "För att ladda upp fler filer till kursen (så att de uppträder i denna lista) använd Filhanteraren."; $string['notypechosen'] = "Du måste välja typ. Använd tillbakaknappen för att gå tillbaka och försöka igen."; +$string['popupresource'] = "Den här resursen bör dyka upp i ett snabbfönster."; +$string['popupresourcelink'] = "Om den inte gjorde det, klicka här: \$a"; $string['resourcetype'] = "Typ av resurs"; $string['resourcetype1'] = "Referens"; $string['resourcetype2'] = "Webbsida"; diff --git a/lang/sv/survey.php b/lang/sv/survey.php index 14c2fbe8df8..4c6a9c96e98 100644 --- a/lang/sv/survey.php +++ b/lang/sv/survey.php @@ -1,5 +1,5 @@