MoodleDocs - User contributions [en]

Using variables in localization strings

2008-07-14T10:37:49Z

Cowen:

Language strings are defined as follows:

<pre>$string['stringname'] = 'This is a string';</pre>

and are called via:

<pre>get_string("stringname","wherefrom")</pre>

If you wish to use a variable from the calling page in the string then you will need to use the following variation to call it:

<pre>get_string("stringname","wherefrom","passedvariable")</pre>

The variable can then be used in your string as follows:

<pre>$string['stringname'] = 'This is a string with a variable called $a';</pre>

[[Category:Developer|Localization strings and variables]]
[[Category:Language]]

Using variables in localization strings

2008-07-14T10:37:03Z

Cowen:

Using variables in localization strings

2008-07-14T10:35:38Z

Cowen:

Using variables in localization strings

2008-07-14T10:31:08Z

Cowen: New page: Language strings are defined as follows: <pre>$string['stringname'] = 'This is a string';</pre> and are called via: <pre>get_string("stringname","wherefrom")</pre> If you wish to use a...

Translation

2008-07-14T10:22:37Z

Cowen: /* See also */

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.

== Structure of a Moodle language pack ==

All Moodle language packs may be found in the ''lang'' folder, with each language in a unique folder named the same as the language short name e.g. ''es'', ''nl''. From Moodle 1.6 upwards, the ''lang'' folder may be found in ''moodledata'', with pack names indicating they are UTF-8 language packs e.g. ''es_utf8'', ''nl_utf8''. The default English language pack, ''en_utf8'', remains in ''moodle/lang'', along with a tiny non-UTF-8 version (''en'') for use in the 1.5 to 1.6 upgrade, prior to the database migration process.

All the main files are in the ''lang/xx_utf8'' folder, with .php extensions (eg ''moodle.php'', ''resource.php'' etc). These files contains short phrases, often called "strings". Each string supports variable substitution, to support variable ordering in different languages.

:e.g. <code>$strdueby = get_string("assignmentdueby", "assignment", userdate($date));</code>

:If a string doesn't exist in a particular language, then the equivalent in English will automatically be used instead.

:There is also a ''help'' folder containing HTML pages for pop-up context-sensitive help.

Installation language packs may be found in the ''install/lang'' folder. These language packs contain only the strings needed for the installation process. The files are generated automatically every night by the download.moodle.org server and '''must not be changed manually'''. For translators this is a unusual experience, since changes you add to the strings used in the installation script will not be visible until 24 hours later in a new download of your 1.6 and onwards installation.

==Creating a new language pack==

If your language is not yet supported by Moodle, you may want to start a new translation. If you are starting a new language, please contact [[User:koen roggemans|Koen Roggemans]] our Translation Coordinator (''translation@moodle.org''). You may also like to post in the Using Moodle [http://moodle.org/mod/forum/view.php?id=43 Languages Forum].

All you need to do is create a new folder in the lang directory using the 2-letter code for your language. You can find these standard codes in ''lib/languages.php''. If you are making a local variation of another language, use the code of that language with an underscore and a meaningful two letter extension (e.g. pt for Portuguese and pt_br for Brasilian variation of the Portuguese language pack). If you are making a Unicode version add _utf8 at the end (eg sr_utf8). Language packs created with a new Moodle 1.6 and onwards or with a Moodle 1.6 in Unicode mode are always in Unicode and should get the _utf8 suffix.

Next, copy the ''langconfig.php'' from the "moodle/lang/en_utf8" folder to that newly created folder. Modify langconfig.php in a way that the settings match your language. Ask for help if necessary.

You are now ready to start inserting new strings by editing your language... see below for details on this.

Note that your new language pack may not show up immediately on the dropdown list if under your site configuration you have langcache set to "Yes."

Since Moodle 1.6, only UTF-8 is used as characterset. This setting is located in a string named "thischarset" in ''langconfig.php'' and should not be changed. All other settings for your language pack, as the notation of dates, the locale string, the direction etc. are in this file and can be changed there. Just be careful! ;-)

===Creating a new language pack or maintaining a language pack in Moodle 1.9 onwards===
{{Moodle 1.9}}In Moodle 1.9 onwards, by default, an administrator can only edit a local language pack, not the master language pack. If you are not involved in translation work, you should only edit your local language pack to ensure that your changes are not overwritten by every update/upgrade of Moodle or the Moodle language packs.

In Moodle 1.9 onwards, if you are a translator, you need to give yourself the right to maintain the master language pack. To do so, log in as an administrator, go to ''Site administration > Users > Define roles'', then edit the Administrator role and set the capability "Edit master language packages" to allow.

==Editing an existing language pack==

===Making small customisations===

If you just want to change a few things in the interface to suit your own site better, don't start editing one of the standard language packs. If you do then your changes will be overwritten next time you upgrade to a new Moodle.

Instead, use the instructions above for making a brand new language pack, add a string 'parentlanguage' (in '''''langconfig.php''''') with the code of the language that is most similar to yours. That language will be checked by Moodle for anything missing from yours. Here's an example of such a line:

$string['parentlanguage'] = 'en_utf8';

A good name for a local English variant could be "en_utf8_local", and the parent language would be defined as "en_utf8" or "en_us_utf8". ''(For Moodle 1.5 and earlier, omit the "_utf8" from the names, since older versions of Moodle don't use UTF8.)''

Note that you also have to create a string 'thislanguage' in '''''moodle.php''''' for your "en_utf8_local" language pack:

$string['thislanguage'] = 'English at OCU';

In Moodle 1.5.x and earlier you would have to then make sure everyone chooses your new language pack. They can change it in their profiles or you can issue an SQL command to change everyone, and prevent them changing it by restricting the available languages on ''Administration > Configuration > Variables''.

Starting in Moodle 1.6, the very best method is just to create a new language directory called "xxxx_local" where xxxx is the name of the language pack you want to modify (eg es_utf8_local or ja_utf8_local). This new local language pack will automatically be checked before the main one. The local pack only needs to contain the local changes (you don't need a complete copy of the language you are modifying). It will not appear in the language menus for selection and your users do not need to change their settings.

The 'parentlanguage' method described above for 1.5 still works, just in case you want to create more than one variant of one language. In this case, you still have to add the 'thislanguage' string, except in 1.6 you add it to the ''langconfig.php'' and not to ''moodle.php''.

{{Moodle 1.9}}In Moodle 1.9 onwards, it is not possible any more to change the master language pack by mistake. By default, all changes you make to a language pack will go in the xxxx_local.

===Translating the Moodle interface language files (the "string" files)===

# Log on to your Moodle server as an administrator.
# Go to Site Administration >> Language >> Language editing, which is the build in Moodle language editor page.
# On this page you can choose for "Local string custumisation" or "Language pack maintaining". Only choose "Language pack maintaining" if you are maintainer of a language pack. You might need to change the setting in the administrator role to get this screen.
# Choose your language from the menu, then choose "Edit words or phrases".
# You should see forms you can edit for each file. If you do not, then you may have to make sure that the files are writeable - you may have to change file permissions in your web folder.
# The forms consist of two columns, the first is that string in English and the name of each string, the second is the translation in the current language.
# Edit missing strings in each files (highlighted in colour), remembering to hit the "Save changes" button at the end of each form.
# You'll notice expressions in bold like '''$a->something'''. These are variables, used by moodle and should NEVER be translated! Note that there is nowhere in the expression a space allowed.
# It's OK to leave strings empty - Moodle will simply use the parent language for that string instead. You can define the parent language in langconfig.php, otherwise English is always used by default.
# A quick way to see all the missing strings is by using the link to "Check untranslated words or phrases". Leave the untranslated strings completely empty or this handy tool won't work.

===Translating the help files===

There is a built-in editor in Moodle to translate the help files. It uses the en_utf8 language pack as a reference language. You are strongly advised to use this editor: it cleans out some possible problems, it warns you for old translations and it marks (with stars in the drop down list) which files are out of date and takes care of Unicode.
If you want another language than English as a reference (which is not a good idea), you copy a help file from the reference language pack and paste it on the same location in your own language pack. Then use a plain text editor with Unicode support to translate the file, making sure not to modify any code in the file (there usually is no code, just HTML-tags). (DON'T USE A WORDPROCESSOR to write the help-files because these programs add too much rubbish to the files).
Don't leave untranslated help files or empty files in your language pack.

Take care to write the helpfiles XHTML-compliant. This means in short:

* All tags should be closed: <pre>lalala</pre>
* All elements should be nested: <pre> lalala lalala </pre>
* All elements and attributes must be lower case
* All atributes should be written in full and with quotes : <pre> lalala </pre>
* Empty elements must end with />: <pre> <hr /></pre>. You should add an extra space before the "/" symbol.
* An <img should have an alt="" (it can be empty) en must be closed like other empty elements with a space and /> like <pre><img alt="" src="picture.gif" /></pre>
* <?= and <? should be <pre><?php</pre>
* There should not be ANY font tags at all. <pre> <h1> <h2></pre> etc should be enough for the language files ...

None of the files in the help folder need a doc type, html, body, head opening and closing tags - these files are included with ''help.php''. The script will take care of welforming the pages. This means also there is not much room for HTML creativity! Please stick to the English example.

The files in the docs folder must be completely XHTML compliant, including doc type, header etc. From Moodle 1.6 they will be moved to this wiki.

Clicking on "Check for missing strings" in the language administration screen will also show you what files you are missing. If you have missing files then Moodle will use the parent language instead, so don't leave copies of untranslated help files in your language pack or this handy tool won't work.

==Submitting your language pack to the Moodle project==

Sharing your translation with Moodle will ensure that you help other people who speak your language. Your interface language will be available in future versions of Moodle. Note that a translation doesn't need to be complete before submitting - any improvement or start of a new translation is welcome.

Simply archive your whole new language directory as a zip file and email it to ''translation@moodle.org''.

We will get back to you with further details.

Check list you can use before committing:

* No empty files?
* No untranslated files or strings (English) used in the submitted files?
* Help files not edited with a word processor?
* README file contains language, name and email address of the translator?
* Folder name is the right language code (check ''moodle\lib\languages.php'')?
* Does the language pack run error free on a test site?
* Are the strings and files XHTML compliant?
* Does ''langconfig.php'' exists and is it correct?
* No Byte Order Marks in your files (is always OK if you used the build in Moodle language editor)
* Nowhere $a->something translated? No spaces in those expressions?

==Maintenance of a standard language pack==

If you are committed to maintaining a language in Moodle, it's best to use [[CVS for Developers|Moodle CVS]] so that you have an up-to-date version of Moodle, and can easily "check in" your changes directly into the Moodle project.

You should always use HEAD to do translation. Instead of modifying the lang pack within your main code tree as it was until Moodle 1.6, you will now be modifying the one within your dataroot/lang directory.

* Always check out the very latest Moodle code
* Upgrade your site. Of course you use a NON-PRODUCTION server for this.
* Go to your dataroot directory and check out the new lang directory from CVS there like this on Unix/Linux

cd moodledata (for example)
cvs -z3 -d:ext:me@cvs.moodle.org:/cvsroot/moodle co lang

or to checkout just a single language pack (Czech in the following example)

cd moodledata (for example)
cvs -z3 -d:ext:me@cvs.moodle.org:/cvsroot/moodle co lang/cs_utf8

* Do not forget to set the correct file system permission so the process of your web server can modify checked-out files.

To do a checkout with Tortoise on Windows,

right click on your dataroot folder, choose "CVS Checkout",
CVSROOT field: :ext:me@cvs.moodle.org:/cvsroot/moodle
Module: lang

* Continue editing languages from within the Moodle GUI as you did before Moodle 1.6.

To check them into CVS, just go into the dataroot/lang directory and commit your changes.

If you really want to continue updating the language packs for 1.5.x or earlier, then you should zip the folder of your langpack and mail it to ''translation@moodle.org''. CVS write access on moodle/lang/xx will be moved to lang/xx_utf8.

Please contact ''translation@moodle.org'' if you need help setting this up.

==Translation of contributed code==

The language files of contributed [http://moodle.org/mod/data/view.php?id=6009 modules and plugins] (including blocks, filters, authentication plugins, assignment types, data fields, data presets, enrolment plugins, course formats, question types, course reports, quiz reports and resource types) reside in the lang folder within the module or plugin folder e.g. ''moodle/mod/modulename/lang/ln_utf8''. When you wish to translate such a module, you can find the English language file in the lang/en_utf8 folder of the module or plugin. Translate this file, using a UTF-8 aware text editor, and save it in an appropriate new language folder ''/lang/XX_utf8/filname.php'' in the module or plugin folder. Please don't forget to send the translated file to the maintainer of the component, whose address may be found in the readme file in the module or plugin folder. This will ensure that your work doesn't get lost in an upgrade and is available for use by other Moodlers.

These translations should never go in your main Moodle language pack.

==See also==

*Using Moodle [http://moodle.org/mod/forum/view.php?id=43 Languages Forum] - news and discussion about issues that affect translations
*[[Translation credits]]
*To keep in touch with changes in the project on a day-to-day basis it is recommended that you subscribe to the [http://lists.moodle.org CVS (commits) mailing list]. This helps to keep your translation as close to the English text as possible.
*Using Moodle [http://moodle.org/mod/forum/discuss.php?d=75088 Automatic update of language package while updating in 1.9] forum discussion
*[[Using variables in localization strings]]

[[Category:Developer]]
[[Category:Language]]

[[es:Traducciones]]
[[fr:Traduction]]
[[ja:翻訳]]
[[nl:Vertalen]]

Translation

2008-07-14T10:21:40Z

Cowen: /* See also */

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.

== Structure of a Moodle language pack ==

All Moodle language packs may be found in the ''lang'' folder, with each language in a unique folder named the same as the language short name e.g. ''es'', ''nl''. From Moodle 1.6 upwards, the ''lang'' folder may be found in ''moodledata'', with pack names indicating they are UTF-8 language packs e.g. ''es_utf8'', ''nl_utf8''. The default English language pack, ''en_utf8'', remains in ''moodle/lang'', along with a tiny non-UTF-8 version (''en'') for use in the 1.5 to 1.6 upgrade, prior to the database migration process.

All the main files are in the ''lang/xx_utf8'' folder, with .php extensions (eg ''moodle.php'', ''resource.php'' etc). These files contains short phrases, often called "strings". Each string supports variable substitution, to support variable ordering in different languages.

:e.g. <code>$strdueby = get_string("assignmentdueby", "assignment", userdate($date));</code>

:If a string doesn't exist in a particular language, then the equivalent in English will automatically be used instead.

:There is also a ''help'' folder containing HTML pages for pop-up context-sensitive help.

Installation language packs may be found in the ''install/lang'' folder. These language packs contain only the strings needed for the installation process. The files are generated automatically every night by the download.moodle.org server and '''must not be changed manually'''. For translators this is a unusual experience, since changes you add to the strings used in the installation script will not be visible until 24 hours later in a new download of your 1.6 and onwards installation.

==Creating a new language pack==

If your language is not yet supported by Moodle, you may want to start a new translation. If you are starting a new language, please contact [[User:koen roggemans|Koen Roggemans]] our Translation Coordinator (''translation@moodle.org''). You may also like to post in the Using Moodle [http://moodle.org/mod/forum/view.php?id=43 Languages Forum].

All you need to do is create a new folder in the lang directory using the 2-letter code for your language. You can find these standard codes in ''lib/languages.php''. If you are making a local variation of another language, use the code of that language with an underscore and a meaningful two letter extension (e.g. pt for Portuguese and pt_br for Brasilian variation of the Portuguese language pack). If you are making a Unicode version add _utf8 at the end (eg sr_utf8). Language packs created with a new Moodle 1.6 and onwards or with a Moodle 1.6 in Unicode mode are always in Unicode and should get the _utf8 suffix.

Next, copy the ''langconfig.php'' from the "moodle/lang/en_utf8" folder to that newly created folder. Modify langconfig.php in a way that the settings match your language. Ask for help if necessary.

You are now ready to start inserting new strings by editing your language... see below for details on this.

Note that your new language pack may not show up immediately on the dropdown list if under your site configuration you have langcache set to "Yes."

Since Moodle 1.6, only UTF-8 is used as characterset. This setting is located in a string named "thischarset" in ''langconfig.php'' and should not be changed. All other settings for your language pack, as the notation of dates, the locale string, the direction etc. are in this file and can be changed there. Just be careful! ;-)

===Creating a new language pack or maintaining a language pack in Moodle 1.9 onwards===
{{Moodle 1.9}}In Moodle 1.9 onwards, by default, an administrator can only edit a local language pack, not the master language pack. If you are not involved in translation work, you should only edit your local language pack to ensure that your changes are not overwritten by every update/upgrade of Moodle or the Moodle language packs.

In Moodle 1.9 onwards, if you are a translator, you need to give yourself the right to maintain the master language pack. To do so, log in as an administrator, go to ''Site administration > Users > Define roles'', then edit the Administrator role and set the capability "Edit master language packages" to allow.

==Editing an existing language pack==

===Making small customisations===

If you just want to change a few things in the interface to suit your own site better, don't start editing one of the standard language packs. If you do then your changes will be overwritten next time you upgrade to a new Moodle.

Instead, use the instructions above for making a brand new language pack, add a string 'parentlanguage' (in '''''langconfig.php''''') with the code of the language that is most similar to yours. That language will be checked by Moodle for anything missing from yours. Here's an example of such a line:

$string['parentlanguage'] = 'en_utf8';

A good name for a local English variant could be "en_utf8_local", and the parent language would be defined as "en_utf8" or "en_us_utf8". ''(For Moodle 1.5 and earlier, omit the "_utf8" from the names, since older versions of Moodle don't use UTF8.)''

Note that you also have to create a string 'thislanguage' in '''''moodle.php''''' for your "en_utf8_local" language pack:

$string['thislanguage'] = 'English at OCU';

In Moodle 1.5.x and earlier you would have to then make sure everyone chooses your new language pack. They can change it in their profiles or you can issue an SQL command to change everyone, and prevent them changing it by restricting the available languages on ''Administration > Configuration > Variables''.

Starting in Moodle 1.6, the very best method is just to create a new language directory called "xxxx_local" where xxxx is the name of the language pack you want to modify (eg es_utf8_local or ja_utf8_local). This new local language pack will automatically be checked before the main one. The local pack only needs to contain the local changes (you don't need a complete copy of the language you are modifying). It will not appear in the language menus for selection and your users do not need to change their settings.

The 'parentlanguage' method described above for 1.5 still works, just in case you want to create more than one variant of one language. In this case, you still have to add the 'thislanguage' string, except in 1.6 you add it to the ''langconfig.php'' and not to ''moodle.php''.

{{Moodle 1.9}}In Moodle 1.9 onwards, it is not possible any more to change the master language pack by mistake. By default, all changes you make to a language pack will go in the xxxx_local.

===Translating the Moodle interface language files (the "string" files)===

# Log on to your Moodle server as an administrator.
# Go to Site Administration >> Language >> Language editing, which is the build in Moodle language editor page.
# On this page you can choose for "Local string custumisation" or "Language pack maintaining". Only choose "Language pack maintaining" if you are maintainer of a language pack. You might need to change the setting in the administrator role to get this screen.
# Choose your language from the menu, then choose "Edit words or phrases".
# You should see forms you can edit for each file. If you do not, then you may have to make sure that the files are writeable - you may have to change file permissions in your web folder.
# The forms consist of two columns, the first is that string in English and the name of each string, the second is the translation in the current language.
# Edit missing strings in each files (highlighted in colour), remembering to hit the "Save changes" button at the end of each form.
# You'll notice expressions in bold like '''$a->something'''. These are variables, used by moodle and should NEVER be translated! Note that there is nowhere in the expression a space allowed.
# It's OK to leave strings empty - Moodle will simply use the parent language for that string instead. You can define the parent language in langconfig.php, otherwise English is always used by default.
# A quick way to see all the missing strings is by using the link to "Check untranslated words or phrases". Leave the untranslated strings completely empty or this handy tool won't work.

===Translating the help files===

There is a built-in editor in Moodle to translate the help files. It uses the en_utf8 language pack as a reference language. You are strongly advised to use this editor: it cleans out some possible problems, it warns you for old translations and it marks (with stars in the drop down list) which files are out of date and takes care of Unicode.
If you want another language than English as a reference (which is not a good idea), you copy a help file from the reference language pack and paste it on the same location in your own language pack. Then use a plain text editor with Unicode support to translate the file, making sure not to modify any code in the file (there usually is no code, just HTML-tags). (DON'T USE A WORDPROCESSOR to write the help-files because these programs add too much rubbish to the files).
Don't leave untranslated help files or empty files in your language pack.

Take care to write the helpfiles XHTML-compliant. This means in short:

* All tags should be closed: <pre>lalala</pre>
* All elements should be nested: <pre> lalala lalala </pre>
* All elements and attributes must be lower case
* All atributes should be written in full and with quotes : <pre> lalala </pre>
* Empty elements must end with />: <pre> <hr /></pre>. You should add an extra space before the "/" symbol.
* An <img should have an alt="" (it can be empty) en must be closed like other empty elements with a space and /> like <pre><img alt="" src="picture.gif" /></pre>
* <?= and <? should be <pre><?php</pre>
* There should not be ANY font tags at all. <pre> <h1> <h2></pre> etc should be enough for the language files ...

None of the files in the help folder need a doc type, html, body, head opening and closing tags - these files are included with ''help.php''. The script will take care of welforming the pages. This means also there is not much room for HTML creativity! Please stick to the English example.

The files in the docs folder must be completely XHTML compliant, including doc type, header etc. From Moodle 1.6 they will be moved to this wiki.

Clicking on "Check for missing strings" in the language administration screen will also show you what files you are missing. If you have missing files then Moodle will use the parent language instead, so don't leave copies of untranslated help files in your language pack or this handy tool won't work.

==Submitting your language pack to the Moodle project==

Sharing your translation with Moodle will ensure that you help other people who speak your language. Your interface language will be available in future versions of Moodle. Note that a translation doesn't need to be complete before submitting - any improvement or start of a new translation is welcome.

Simply archive your whole new language directory as a zip file and email it to ''translation@moodle.org''.

We will get back to you with further details.

Check list you can use before committing:

* No empty files?
* No untranslated files or strings (English) used in the submitted files?
* Help files not edited with a word processor?
* README file contains language, name and email address of the translator?
* Folder name is the right language code (check ''moodle\lib\languages.php'')?
* Does the language pack run error free on a test site?
* Are the strings and files XHTML compliant?
* Does ''langconfig.php'' exists and is it correct?
* No Byte Order Marks in your files (is always OK if you used the build in Moodle language editor)
* Nowhere $a->something translated? No spaces in those expressions?

==Maintenance of a standard language pack==

If you are committed to maintaining a language in Moodle, it's best to use [[CVS for Developers|Moodle CVS]] so that you have an up-to-date version of Moodle, and can easily "check in" your changes directly into the Moodle project.

You should always use HEAD to do translation. Instead of modifying the lang pack within your main code tree as it was until Moodle 1.6, you will now be modifying the one within your dataroot/lang directory.

* Always check out the very latest Moodle code
* Upgrade your site. Of course you use a NON-PRODUCTION server for this.
* Go to your dataroot directory and check out the new lang directory from CVS there like this on Unix/Linux

cd moodledata (for example)
cvs -z3 -d:ext:me@cvs.moodle.org:/cvsroot/moodle co lang

or to checkout just a single language pack (Czech in the following example)

cd moodledata (for example)
cvs -z3 -d:ext:me@cvs.moodle.org:/cvsroot/moodle co lang/cs_utf8

* Do not forget to set the correct file system permission so the process of your web server can modify checked-out files.

To do a checkout with Tortoise on Windows,

right click on your dataroot folder, choose "CVS Checkout",
CVSROOT field: :ext:me@cvs.moodle.org:/cvsroot/moodle
Module: lang

* Continue editing languages from within the Moodle GUI as you did before Moodle 1.6.

To check them into CVS, just go into the dataroot/lang directory and commit your changes.

If you really want to continue updating the language packs for 1.5.x or earlier, then you should zip the folder of your langpack and mail it to ''translation@moodle.org''. CVS write access on moodle/lang/xx will be moved to lang/xx_utf8.

Please contact ''translation@moodle.org'' if you need help setting this up.

==Translation of contributed code==

The language files of contributed [http://moodle.org/mod/data/view.php?id=6009 modules and plugins] (including blocks, filters, authentication plugins, assignment types, data fields, data presets, enrolment plugins, course formats, question types, course reports, quiz reports and resource types) reside in the lang folder within the module or plugin folder e.g. ''moodle/mod/modulename/lang/ln_utf8''. When you wish to translate such a module, you can find the English language file in the lang/en_utf8 folder of the module or plugin. Translate this file, using a UTF-8 aware text editor, and save it in an appropriate new language folder ''/lang/XX_utf8/filname.php'' in the module or plugin folder. Please don't forget to send the translated file to the maintainer of the component, whose address may be found in the readme file in the module or plugin folder. This will ensure that your work doesn't get lost in an upgrade and is available for use by other Moodlers.

These translations should never go in your main Moodle language pack.

==See also==

*Using Moodle [http://moodle.org/mod/forum/view.php?id=43 Languages Forum] - news and discussion about issues that affect translations
*[[Translation credits]]
*To keep in touch with changes in the project on a day-to-day basis it is recommended that you subscribe to the [http://lists.moodle.org CVS (commits) mailing list]. This helps to keep your translation as close to the English text as possible.
*Using Moodle [http://moodle.org/mod/forum/discuss.php?d=75088 Automatic update of language package while updating in 1.9] forum discussion
*Using variables in localization strings

[[Category:Developer]]
[[Category:Language]]

[[es:Traducciones]]
[[fr:Traduction]]
[[ja:翻訳]]
[[nl:Vertalen]]

Moodle version history

2007-02-19T15:47:55Z

Cowen: /* Moodle 1.8 */

==Release History==

See [[Release_Notes|Release Notes]] for more details.

==Moodle 1.0==
*Moodle 1.0 - 20 August 2002
*Moodle 1.0.1 - 26 August 2002
*Moodle 1.0.2 - 2 September 2002
*Moodle 1.0.3 - 5 September 2002
*Moodle 1.0.4 - 10 September 2002
*Moodle 1.0.5 - 27 September 2002
*Moodle 1.0.6 - 26 October 2002
:: 1.0.6.1 - 6 Nov
:: 1.0.6.2 - 11 Nov
:: 1.0.6.3 - 14 Nov
:: 1.0.6.4 - 25 Nov
*Moodle 1.0.7 - 9 December 2002
*Moodle 1.0.8 - 7 January 2003
*Moodle 1.0.9 - 30 May 2003

==Moodle 1.1==
*Moodle 1.1 - 29 August 2003
*Moodle 1.1.1 - 11 September 2003

==Moodle 1.2==
*Moodle 1.2 - 20 March 2004
*Moodle 1.2.1 - 25 March 2004

==Moodle 1.3==
*Moodle 1.3 - 25 May 2004
*Moodle 1.3.1 - 4 June 2004
*Moodle 1.3.2 - 9 July 2004
*Moodle 1.3.3 - 16 July 2004
*Moodle 1.3.4 - 11 August 2004

==Moodle 1.4==
*Moodle 1.4 - 31 August 2004
*Moodle 1.4.1 - 12 September 2004
*Moodle 1.4.2 - 5 November 2004
*Moodle 1.4.3 - 21 December 2004
*Moodle 1.4.4 - 7 March 2005
*Moodle 1.4.5 - 7 May 2005

==Moodle 1.5==
*Moodle 1.5 - 5 June 2005
*Moodle 1.5.1 - 8 July 2005
*Moodle 1.5.2 - 16 July 2005
*Moodle 1.5.3 - 11 November 2005
*Moodle 1.5.4 - 21 May 2006

==Moodle 1.6==
*Moodle 1.6 - 20 June 2006
*Moodle 1.6.1 - 20 July 2006
*Moodle 1.6.2 - 12 September 2006
*Moodle 1.6.3 - 10 October 2006
*Moodle 1.6.4 - 17 January 2007

==Moodle 1.7==
*Moodle 1.7 - 7 November 2006
*Moodle 1.7.1 - 17 January 2007

==Moodle 1.8==
*Moodle 1.8 (Currently in beta - expected release late Feb 2007)

[[Category:Administrator]]
[[Category:Developer]]

[[fr:Historique des versions]]
[[es:Historia de las versiones]]

Talk:Dfwiki module

2006-10-20T13:18:48Z

Cowen:

we have newwiki and dfwiki and the older versions of wiki. This page could be updated. As I recall dfwiki is good for 1.6 but newwiki is the "head" or less stable. Help!

A simple, brief compairson would be nice. Trying to find this in a forum is great for those who know but hard for the less familiar. Moodle Docs is a great place to summarize. Thanks for efforts --[[User:chris collman 2|chris collman 2]] 09:28, 3 August 2006 (WST)

I agree, some comparison of ewiki and Dfwiki would be nice. Also, is moodle going to adopt dfwiki as the "official" bundled wiki starting from 1.7?

I was going to edit this page myself but then reading through all the relevant forum, wiki and blog posts I found myself more confused than before. Could someone in a position to know (Ludo?) update this entry and set the record straight? It's quite a confusing situation at the moment. --[[User:Charlotte Owen|Charlotte Owen]] 08:18, 20 October 2006 (CDT)

error/moodle/guestnoeditprofileother

2006-08-30T15:25:34Z

Cowen:

This error appears if you attempt to edit the profile of the [[Guest_access|Guest User]]. As this user is a special system user it cannot be edited via the Moodle interface.

error/moodle/guestnoeditprofileother

2006-08-30T15:25:21Z

Cowen:

This error appears if you attempt to edit the profile of the [[Guest User|Guest_access]]. As this user is a special system user it cannot be edited via the Moodle interface.

error/moodle/guestnoeditprofileother

2006-08-30T15:24:47Z

Cowen:

This error appears if you attempt to edit the profile of the [[Guest User]]. As this user is a special system user it cannot be edited via the Moodle interface.

error/moodle/guestnoeditprofileother

2006-08-30T15:24:39Z

Cowen:

This error appears if you attempt to edit the profile of the [Guest User]. As this user is a special system user it cannot be edited via the Moodle interface.