MoodleDocs - User contributions [en]

Moderator guidelines

2024-02-01T17:24:50Z

Marycooch: moved page

This page has moved to [https://moodle.org/mod/page/view.php?id=8799&forceview=1 Moodle.org moderator guidelines].

Plugin contribution

2023-06-13T09:59:43Z

Marycooch: added link to https://moodle.org/plugins/registerplugin.php

{{Plugins development}}

This page describes how to contribute your code into the [[Plugins directory]] to share it with the Moodle community.

== Why ==

You are encouraged to share your plugin with the community. But firstly, to be clear and honest, you do not necessarily need to submit your plugin into the Plugins directory. Maybe it is a custom plugin that solves one particular site's needs and you do not really want to share it with others. Remember you can always simply host your plugin on your own site and let users download it manually from there.

Having your plugin registered with the Plugins directory has several benefits.

* Your plugin is easier to install. Plugins directory integrates with Moodle. Administrators can simply install your plugin from the plugins directory via the web interface.
* Your plugin is easier to update. Whenever you release a new version of your plugin, all administrators having it installed are notified about the available update. They can easily upgrade to the new version from within the Moodle administration UI.
* You reserve the component name ([[Frankenstyle|frankenstyle]]) of your plugin. Plugins directory is the official register of Moodle plugins. As with the internet domain names, there can't be two plugins having the same component name.
* The plugin can be localised. Plugins in the Plugins directory are implicitly registered with [[AMOS]] and can be localised using the same tools that are used for localising the standard Moodle UI.
* The plugin must be approved. Many institutions respect the approval review procedure and do not allow to install a plugin on their servers unless it has been approved in the plugins directory.

== Before you start ==

Before submitting your work to the Plugins directory, you should make sure you have all required and recommended resources available.

* '''Plugin type''' - Different [[Plugin types|plugin types]] are best suited for certain types of functionality. It is important to choose the appropriate plugin type to implement the desired features.
* '''Plugin name''' - See the [[Frankenstyle]] page for details.
* '''Repository''' - You are expected to have the plugin code published and shared in a way that facilitates collaboration on further development. Ideally, you have the code available in a public Git repository. Most developers found [https://github.com Github] a good place to host their code on. The [[#Repository]] section below provides more details.
* '''Tracker''' - You are expected to have a system where users can report issues, bugs and feature requests for the plugin. Again, many developers use [https://guides.github.com/features/issues/ Github issues] happily these days. You can also use the Moodle tracker if you prefer. See [[#Tracker]] section for more details.
* '''Documentation''' - The plugin should have a good documentation available. See [[Plugin documentation]] for options.
* '''Screenshots''' - Prepare good screenshots that illustrate your plugin's essential features.

== Sharing code in the Plugins directory ==

So you have written a new plugin and want to share it now in the [[Plugins directory]]? Great! Shortly, the workflow of publishing and maintaining your plugin in the Plugins directory looks like this:

<div class="container">
[[Image:plugin-contribution-workflow.png|640px]]

''Workflow of contributing a plugin into the Moodle plugins directory ([[Media:plugin-contribution-workflow.svg|SVG version]])''
</div>

# You upload the initial plugin version for approval from the [https://moodle.org/plugins/registerplugin.php Register a new plugin] link, available in the Navigation block in the blocks drawer on the right. To help the approval review go smoothly, please feel encouraged to review the [[Plugin contribution checklist]] and follow all the guidelines there.
# After you submit the plugin for approval, please brace yourself with patience. You will likely wait some weeks before you get initial review results. We generally try and provide the feedback sooner, but it is not always possible. The actual approval queue stats [https://moodle.org/plugins/queue.php are available].
# The plugin goes through the validation and approval process.
# Almost all plugins are sent back as "needing more work" as a result of the initial review, and there is no reason to feel bad about that. It is natural part of the workflow. You may find particular issues reported so you have an opportunity to demonstrate your ability to co-operate with the reporter to resolve them.
# Once the plugin is approved, its strings are registered with [[AMOS]] and can be translated. The plugin itself should ship with English strings only. The page [https://docs.moodle.org/en/Translating_plugins Translating plugins] has more details.
# We do not automatically pull from Github. You have to explicitly release new version via the Plugins directory. Still you are encouraged to use Git tags - releasing new version is easier then.

=== Repository ===

* Git is de-facto standard source code management system for Moodle plugins.
* You are supposed to publish and share your plugin code so that others can clone it easily and eventually contribute patches for it easily.
* [https://github.com/ Github] is a popular choice of many Moodle developers these days.
* The layout should be that the root of the repository is the root of the plugin folder. In other words, in the root of your repository there should be files like version.php and folders like lang or classes. That way, your plugin can be directly cloned (checked out) into existing Moodle installation without conflicting with other contributed plugins of the same type, also obtained via Git.
* It is suggested to follow the common naming convention of Moodle related repositories: moodle-{plugintype}_{pluginname}. For example, the birthday block has a repository name of moodle-block_birthday and is located at https://github.com/arborrow/moodle-block_birthday. Other developers can fork the code and work from their repositories.

=== Tracker ===

You are expected to have a system where users can report feature requests, bugs, and other code issues. Following the open source best practise, these reports should be open and public and the associated procedures should be as transparent as possible.

There are multiple options on where to host the issues tracker. Most plugin developers today prefer to have the issue tracker close to their source code management system - so they use the native issue tracker built into Github, BitBucket or some similar system. It is suggested to use a system that your users are likely to be familiar with.

==Tutorial==
There is a [[Tutorial]] to help you learn how to write plugins for Moodle from start to finish, while showing you how to navigate the most important developer documentation along the way.

==See also==

* [[Moodle icons]]
* [[Overview]] of Moodle development
* Using Moodle [http://moodle.org/mod/forum/discuss.php?d=99037 Best practices for code modification?] forum discussion
* [http://aosabook.org/en/moodle.html Moodle] in The Architecture of Open Source Applications, by Tim Hunt - an overview of all aspects of how Moodle works, it focuses on those areas where Moodle's design is particularly interesting.
* [http://www.examulator.com/er/ The Moodle 3.0 database schema] reverse engineered and [[Database schema introduction]].
* [https://moodle.org/mod/forum/discuss.php?d=322196 Preparing plugins for Moodle 3.0] excellent summary in this forum thread. Also applies for Moodle 3.1 and newer.

[[Category:Guidelines for contributors]]
[[Category:Plugins]]
[[Category:Plugin documentation]]

Contributing to Moodle

2023-02-06T05:24:00Z

Marycooch: updated link to dev docs

There are lots of ways you can contribute to the Moodle project:

==User support==

Join in with the international discussions in [http://moodle.org/course/view.php?id=5 Moodle in English] or [https://moodle.org/community/ community discussions in many other languages].

==Moodle Users Association==

The [https://moodleassociation.org/ Moodle Users Association] (MUA) is a not-for-profit incorporated association that helps drive the Moodle project. The MUA provides a strong and united voice to users, giving direction and resources for new developments. It is a separate entity from Moodle Pty Ltd and other organisations involved in the Moodle open-source project. Members of the Association decide twice a year on new development projects for Moodle core; access an exclusive peer group of Moodle users; and gain some early, deeper insights into Moodle core developments. Different member levels (for individuals and institutions) are available. Shape the future of Moodle today, join MUA!

==Documentation==

Help write and edit our [https://docs.moodle.org/overview/ user documentation in various languages] or our [https://moodledev.io/| developer docs].

==Testing==

Help test and report bugs via the [http://tracker.moodle.org/ Moodle Tracker] (see the [[Tracker introduction|introduction to the Tracker]]) and participate in [[QA testing]].

==User experience (UX)==

Participate in discussions in the [https://moodle.org/ux Moodle UX area] in and sign up to help with Moodle UX research.

==Development==

[[Process#Fixing_a_bug|Fix a bug]] in Moodle core. If you are looking for a good issue to start with, please see the [https://tracker.moodle.org/issues/?jql=project%20%3D%20MDL%20AND%20type%20in%20(bug)%20AND%20status%20%3D%20open%20AND%20Difficulty%20%3D%20Easy%20AND%20labels%20not%20in%20(patch)%20ORDER%20BY%20created%20DESC list of relatively easy Moodle bugs].

Help [http://moodle.org/development develop new code for Moodle] or share your code in the [https://moodle.org/plugins Plugins directory].

Adopt a [https://moodle.org/plugins/browse.php?list=set&id=61 plugin seeking a new maintainer] and help many users. See the [https://moodle.org/mod/forum/discuss.php?d=260354 Plugins adoption programme].

See also [[Working with the Community]].

Sign up to free self-paced courses in our [https://learn.moodle.org/ Moodle Academy Developer Learning Pathway] to help you learn and extend your Moodle development skills.

==Themes==

Share your theme in the [https://moodle.org/plugins/browse.php?list=category&id=3 Themes section of the plugins directory].

==Translation==

Assist with the [[Translation|translation]] of Moodle, including [[Contributing a translation|contributing a translation/correction]], [[Translating plugins|translating a plugin]], [[Translating Moodle video subtitles|translating Moodle screencasts subtitles]] or [[Improving English language strings|suggesting an improvement to an English language string]].

==Social media==

Help [https://moodle.org/social/ raise awareness of the Moodle project and share the latest news and happenings] in the Moodle world

==Books and video courses==

A percentage of all sales from [https://moodle.org/mod/data/view.php?id=7246 books or video courses] goes to Moodle Pty Ltd to help support Moodle development.

==Shop Official Merchandise==

Moodle receives a percentage from each item purchased from our official [https://moodle.com/shop/ Moodle Shop]

==Vote for future Moodle improvements==

See the [https://docs.moodle.org/dev/New_feature_ideas new feature ideas]. [https://tracker.moodle.org/issues/?filter=10512 Check the Moodle tracker and vote] for the issues that you think will improve Moodle the most.

==Moodle Partners==

A certified network of Moodle Partners contribute to the Moodle project. Moodle Partners offer services such as hosting, support, installation, custom coding, course development and consulting, amongst others. Find our full listing of [http://moodle.com/partners/ Moodle Partners here.]

==More ways to contribute==

Do you want to help but don't have the time? Do you want to give something back to the project to help pay the developers who make it happen? Then please make a [http://moodle.com/donations donation] to the project.

MediaWiki:Sitenotice

2023-01-30T06:40:42Z

Marycooch:

{| class="alert alert-info"
|style="padding: 0.7em 0.5em 0.5em;" | '''Note:'''
If you want to create a new page for developers, you should create it on the [https://moodledev.io Moodle Developer Resource] site.

|}

MediaWiki:Sitenotice

2023-01-30T06:38:19Z

Marycooch:

{| class="alert alert-info"
|style="padding: 0.7em 0.5em 0.5em;" | '''Note:'''
If you want to create a new page for developers, please create it on [https://moodledev.io Moodle Developer Resource] site.

|}

MediaWiki:Sitenotice

2023-01-30T06:36:01Z

Marycooch: site notice

'''Note:''' If you want to create a new page for developers, please create it on [https://moodledev.io Moodle Developer Resource] site.

Plugin contribution

2022-12-14T18:04:27Z

Marycooch:

{{Plugins development}}

This page describes how to contribute your code into the [[Plugins directory]] to share it with the Moodle community.

== Why ==

You are encouraged to share your plugin with the community. But firstly, to be clear and honest, you do not necessarily need to submit your plugin into the Plugins directory. Maybe it is a custom plugin that solves one particular site's needs and you do not really want to share it with others. Remember you can always simply host your plugin on your own site and let users download it manually from there.

Having your plugin registered with the Plugins directory has several benefits.

* Your plugin is easier to install. Plugins directory integrates with Moodle. Administrators can simply install your plugin from the plugins directory via the web interface.
* Your plugin is easier to update. Whenever you release a new version of your plugin, all administrators having it installed are notified about the available update. They can easily upgrade to the new version from within the Moodle administration UI.
* You reserve the component name ([[Frankenstyle|frankenstyle]]) of your plugin. Plugins directory is the official register of Moodle plugins. As with the internet domain names, there can't be two plugins having the same component name.
* The plugin can be localised. Plugins in the Plugins directory are implicitly registered with [[AMOS]] and can be localised using the same tools that are used for localising the standard Moodle UI.
* The plugin must be approved. Many institutions respect the approval review procedure and do not allow to install a plugin on their servers unless it has been approved in the plugins directory.

== Before you start ==

Before submitting your work to the Plugins directory, you should make sure you have all required and recommended resources available.

* '''Plugin type''' - Different [[Plugin types|plugin types]] are best suited for certain types of functionality. It is important to choose the appropriate plugin type to implement the desired features.
* '''Plugin name''' - See the [[Frankenstyle]] page for details.
* '''Repository''' - You are expected to have the plugin code published and shared in a way that facilitates collaboration on further development. Ideally, you have the code available in a public Git repository. Most developers found [https://github.com Github] a good place to host their code on. The [[#Repository]] section below provides more details.
* '''Tracker''' - You are expected to have a system where users can report issues, bugs and feature requests for the plugin. Again, many developers use [https://guides.github.com/features/issues/ Github issues] happily these days. You can also use the Moodle tracker if you prefer. See [[#Tracker]] section for more details.
* '''Documentation''' - The plugin should have a good documentation available. See [[Plugin documentation]] for options.
* '''Screenshots''' - Prepare good screenshots that illustrate your plugin's essential features.

== Sharing code in the Plugins directory ==

So you have written a new plugin and want to share it now in the [[Plugins directory]]? Great! Shortly, the workflow of publishing and maintaining your plugin in the Plugins directory looks like this:

<div class="container">
[[Image:plugin-contribution-workflow.png|640px]]

''Workflow of contributing a plugin into the Moodle plugins directory ([[Media:plugin-contribution-workflow.svg|SVG version]])''
</div>

# You upload the initial plugin version for approval. To help the approval review go smoothly, please feel encouraged to review the [[Plugin contribution checklist]] and follow all the guidelines there.
# After you submit the plugin for approval, please brace yourself with patience. You will likely wait some weeks before you get initial review results. We generally try and provide the feedback sooner, but it is not always possible. The actual approval queue stats [https://moodle.org/plugins/queue.php are available].
# The plugin goes through the validation and approval process.
# Almost all plugins are sent back as "needing more work" as a result of the initial review, and there is no reason to feel bad about that. It is natural part of the workflow. You may find particular issues reported so you have an opportunity to demonstrate your ability to co-operate with the reporter to resolve them.
# Once the plugin is approved, its strings are registered with [[AMOS]] and can be translated. The plugin itself should ship with English strings only. The page [https://docs.moodle.org/en/Translating_plugins Translating plugins] has more details.
# We do not automatically pull from Github. You have to explicitly release new version via the Plugins directory. Still you are encouraged to use Git tags - releasing new version is easier then.

=== Repository ===

* Git is de-facto standard source code management system for Moodle plugins.
* You are supposed to publish and share your plugin code so that others can clone it easily and eventually contribute patches for it easily.
* [https://github.com/ Github] is a popular choice of many Moodle developers these days.
* The layout should be that the root of the repository is the root of the plugin folder. In other words, in the root of your repository there should be files like version.php and folders like lang or classes. That way, your plugin can be directly cloned (checked out) into existing Moodle installation without conflicting with other contributed plugins of the same type, also obtained via Git.
* It is suggested to follow the common naming convention of Moodle related repositories: moodle-{plugintype}_{pluginname}. For example, the birthday block has a repository name of moodle-block_birthday and is located at https://github.com/arborrow/moodle-block_birthday. Other developers can fork the code and work from their repositories.

=== Tracker ===

You are expected to have a system where users can report feature requests, bugs, and other code issues. Following the open source best practise, these reports should be open and public and the associated procedures should be as transparent as possible.

There are multiple options on where to host the issues tracker. Most plugin developers today prefer to have the issue tracker close to their source code management system - so they use the native issue tracker built into Github, BitBucket or some similar system. It is suggested to use a system that your users are likely to be familiar with.

==Tutorial==
There is a [[Tutorial]] to help you learn how to write plugins for Moodle from start to finish, while showing you how to navigate the most important developer documentation along the way.

==See also==

* [[Moodle icons]]
* [[Overview]] of Moodle development
* Using Moodle [http://moodle.org/mod/forum/discuss.php?d=99037 Best practices for code modification?] forum discussion
* [http://aosabook.org/en/moodle.html Moodle] in The Architecture of Open Source Applications, by Tim Hunt - an overview of all aspects of how Moodle works, it focuses on those areas where Moodle's design is particularly interesting.
* [http://www.examulator.com/er/ The Moodle 3.0 database schema] reverse engineered and [[Database schema introduction]].
* [https://moodle.org/mod/forum/discuss.php?d=322196 Preparing plugins for Moodle 3.0] excellent summary in this forum thread. Also applies for Moodle 3.1 and newer.

[[Category:Guidelines for contributors]]
[[Category:Plugins]]
[[Category:Plugin documentation]]

Support forums policy

2022-10-21T00:43:45Z

Marycooch:

<p class="note">'''Note:''' This article is out of date and should not be referenced or migrated.</p>

==Community discussion courses==

Our main Moodle community site, moodle.org, includes [http://moodle.org/course/ community discussion courses in many languages].

In order to thrive, a community discussion course needs a core of committed participants and at least one facilitator.

If you would like to volunteer to help facilitate a community discussion course, please contact an existing facilitator.

Following a review and consultation, any community discussion courses which are no longer needed are closed. See [https://docs.google.com/spreadsheet/ccc?key=0AmamVlPpCnn4dFRVcHhtZG8wa2ZxdmU1UDRoM3BWZ0E#gid=0 moodle.org courses review August 2012] for details of the last review.

==Using Moodle forums==

[https://moodle.org/course/view.php?id=5 Using Moodle] is the main place for support and developer discussions between users and developers in English.

Add-on maintainers and users are welcome to discuss their add-on in an appropriate forum, for example the [https://moodle.org/mod/forum/view.php?id=2121 Blocks forum], or the [https://moodle.org/mod/forum/view.php?id=46 Themes forum], or the [https://moodle.org/mod/forum/view.php?id=44 General add-ons forum]. If an add-on maintainer thinks there is sufficient need for their add-on to have its own forum, they should create a Moodle Community Sites issue for it in the tracker.

Note: All add-ons should have an entry in the [https://moodle.org/plugins Moodle plugins directory] and provide [[Plugin documentation|plugin documentation]].

==See also==

* [https://docs.google.com/spreadsheet/ccc?key=0AmamVlPpCnn4dGtUY0ZTTkRYb2QxSS1EMnJPY3ZqbWc#gid=1 Using Moodle forums review August 2012]
* [https://docs.google.com/spreadsheet/ccc?key=0AmamVlPpCnn4dGtUY0ZTTkRYb2QxSS1EMnJPY3ZqbWc#gid=2 Using Moodle forums reorganisation - Plan A]
* [[Community credits]]

[[Category:Moodle.org]]

Improving English language strings

2022-10-10T08:18:06Z

Marycooch: redirect to user docs

This page is now located in the user docs: [[:en:Improving English language strings|Improving English language strings]]

Translation FAQ

2022-09-09T09:39:06Z

Marycooch: redirect

This page is now located in the user docs: [[:en:Translation FAQ|Translation FAQ]]

Translation FAQ

2022-09-09T09:38:33Z

Marycooch: Changed protection level for "Translation FAQ" ([Edit=Allow only autoconfirmed users] (indefinite))

{{Template:Migrated|newDocId=/general/development/process/translation/faq}}
{{Translation}}
==How can I help with translating Moodle?==
Please see the guide [[Contributing a translation]].
==I've found an error in a language pack. What do I do?==
* You are welcome to [[Contributing a translation|contribute a fix]] for the error. Alternatively you can contact the language pack maintainer as listed in the [http://lang.moodle.org/local/amos/credits.php Translation credits].
* English language string typo fixes and suggested improvements can be [[Improving English language strings|contributed to the English (fixes) (en_fix) language pack]].
==The month names and days are displayed in English. How can I translate them?==
This is neither Moodle bug nor a missing translation. Names of days and months are pulled out of your operating system. Your server, where the Moodle is running, does not seem to have the specific [https://en.wikipedia.org/wiki/Locale_(computer_software) locale] installed. You need to contact the server administrator and ask them to install the needed locale. See [[Table of locales]] for details.

The particular locale to use for the given language is configured in the langconfig.php file in strings ''locale'' (for Unix like operating systems) and ''localewin'' (for Windows operating systems).

On Ubuntu/Debian, the package <tt>locale-all</tt> can be installed to support all existing languages.

Mac OS is known to have a very limited support for locales. This can not be fixed.
==Why are log descriptions displayed in English?==
In log reports, descriptions are intended to be displayed in English only; it is not possible to translate them. For example "The user with id '2' viewed the course with id '4'."
==I'm starting a new language pack or I'm contributing to one. Can I do the user interface strings first?==
No, there is no way to know which strings will be shown for users and which not. But to help you a little bit, there are some unofficial priorities you can take into account.

First:
* make sure [[Translation_langconfig|langconfig]] is properly set up.
* take a look at [[Translation priority]]. All files have a rating according to how urgent they need translating.
* less urgent are also the contributed plugins, since they are not part of a standard Moodle distribution. There is a list of [https://moodle.org/plugins/stats.php the 20 top plugins downloads for Moodle] which might be worth considering for translation priority.
==How many words are there in the English language pack?==
See the discussion [http://lang.moodle.org/mod/forum/discuss.php?d=3651 How many words are there in the English language pack?].
==Moodle languages with several available language packs==
===Are there translations for the American (and other branches of the) English language?===
The [http://lang.moodle.org/mod/forum/discuss.php?d=2617 "official"] language for Moodle is actually Australian English (''G'day mate!'') , which is almost 100% the same as UK English. [http://english.stackexchange.com/questions/74737/what-is-the-origin-of-the-phrase-two-nations-divided-by-a-common-language Someone] once said "America and England are two nations divided by a common language".
* The English - United States (en_us)] language pack mostly contains different spellings (color ''versus'' colour, enroll ''versus'' enrol etc).
* The English - Pirate (en_ar)] language pack is used in the '[https://moodle.org/mod/forum/discuss.php?d=132888 Talk Like a Pirate]' day.
* The English - United States K12 (en_us_k12) language pack is used in the [https://en.wikipedia.org/wiki/K%E2%80%9312 K-12] (kindergarten to grade 12) primary and secondary education in the USA, Canada, and other English speaking countries. It includes spellings from the en_us language pack and the term "course" is renamed as "class".
* The English for kids (en_kids) language pack seems to be a simplified version of the most common English strings seen by Moodle users, considered easier/suitable for small children.
* The English (fixes) (en_fix) language pack is used to suggest Moodle core language strings improvements and typo fixes, as described in the guide [[Improving English language strings]].
===Why do Moodle has four different language packs for the German language?===
* In Germany we have a formal language where people are talking with „Sie“ to each other. This is the language of the formal adults. I think it’s something like using „Sir“ in english language. The normal German language pack is using this formal language. Nearly all strings in the Moodle language pack and in the translated plugins are translated in the formal language.

* You can’t use these formal words in school … there you are using an informal language with „du“. Students are talking to each other like friends. Therefor we made the language pack „German personal“ (de_du). It come with the personal words „du“, „dein“, „dir“ and so on where the formal words are „Sie“, „Ihre“, „Ihnen“ (yes, these words are written with an uppercase letter).

* For my (Ralf Krause) personal use I take „German personal" (de_du) or „German Kids“ (de_kids). „German Kids“ uses the personal words „du“, „dein“ and „dir“ but it also uses an easier to understand language.

* Some time ago we tried to make Moodle as a platform for social communication but nobody wanted to use it. Therefore we made "German community“. In a social platform, nobody would talk about teachers or students or participants or classrooms or courses … in a social platform, you would use members of a group and meetings. I don’t know if this pack will be used in future.
===Why do Moodle has several different language packs for the Spanish language?===
* Spain and many South American countries use a (comma) [[Decimal separator]] that is different from the (decimal point) used in Mexico and Central America.
** Moodle core in English uses by default a decimal point for calculations, and Moodle Docs do too.
** This caused many problems in the [https://docs.moodle.org/31/en/Grader_report Gradebook] calculations and with the [https://docs.moodle.org/all/es/P%C3%A1gina_Principal Spanish Moodle Docs].
* Just as "America and England are two nations divided by a common language", so are Spain and Mexico. See [https://docs.moodle.org/all/es/Espa%C3%B1ol_de_M%C3%A9xico the Mexican Spanish documentation page] in Spanish.
* The Venezuelan Spanish (es_ve) is a very small child language of the international Spanish language.
* The Colombian Spanish (es_co) is a very small child language of the international Spanish language.
* The Mexican Spanish (es_mx) is a very modern, comprehensive, independent, language pack, specially made for Mexican Moodlers.
* The Mexican Spanish for kids (es_mx_kids) is a simplified version of the most common Mexican Spanish strings seen by Moodle users, considered easier/suitable for small children.
* You can read about [https://docs.moodle.org/all/es/Espa%C3%B1ol_internacional#Idiomas_hijos_que_depend.C3.ADan_del_Espa.C3.B1ol_internacional two (now defunct) other Spanish child languages].
===Why do other languages have child languages?===
* Languages with ''-kids'' in their code names are all child languages with a simplified version of common language strings aimed at small children.
* If you have the time, it is probably a good idea to have one such child language for kids for your main language pack.
* Current (mid 2017) languages for kids are:
** Deutsch - Kids
** English for kids
** Español de México para niños (Mexican Spanish for kids)
** עברית בתי־ספר (hebrew for kids)
** Japanese - kids
** Deutsch - Kids

* Norwegian (Primary) language pack is aimed at primary education.

* Finnish for companies is aimed at companies.

* Languages ending in "_wp" are supplementary languages for [https://docs.moodle.org/37/en/Moodle_Workplace Moodle Workplace]. They are maintained by the companies offering [https://docs.moodle.org/37/en/Moodle_Workplace Moodle Workplace].
==Are there items which are NOT to be translated?==
===Moodle variables enclosed within {curly brackets}===
The following words, when enclosed within {curly brackets}, are placeholders for Moodle names of variables. They should not be translated, but must remain as they are within the curly brackets:
firstname, lastname, username, email, city, country, lang, timezone, mailformat, maildisplay, maildigest, htmleditor, ajax, autosubscribe , institution, department, idnumber, skype , msn, aim, yahoo, icq, phone1, phone2, address, url, description, descriptionformat, password, auth, oldusername , deleted, suspended, course1, course2, course3, course4
They must also be written exactly like this in all translations of the documentation pages (such as this page.) However, the translator might like to include a translation enclosed in brackets. For example, in the Spanish documentation pages you might find: password (''contraseña'').

The fact is: '''no placeholders can be translated in AMOS'''. There is no official list of "reserved" $a properties. Whatever xyz is put in {$a->xyz}, it must be kept as it is in AMOS.

Example:

[[File:26 AMOS fullnamedisplay_core original.png]]

'''Must''' be (in this case, when translated into Mexican Spanish):

[[File:26 AMOS fullnamedisplay_core.png]]

unless your language uses lastname before the firstname, as Japanese does, which translates to:

[[File:26 AMOS fullnamedisplay_core Japanese.png]]
===Placeholders enclosed within % characters (%example%) must not be translated===
The [https://moodle.org/plugins/local_moodlecloudsignup Moodle Cloud Signup and Portal strings] local plugin is used for accessing the [https://moodle.com/cloud/ MoodleCloud] and it includes several strings that have some words surrounded by % characters (eg, %date%). These words must not be translated, they must be copied exactly into the language pack translation, but the rest of the string might or might not be translated.
* Example of one string that can not be translated and must be copied exactly:
[[File:AMOS placeholders with percentace character.png|600px]]
* Example of one string with one placeholder (highlighted) and some regular text that can be easily translated:
[[File:AMOS text with placeholders with percentace character.png|600px]]
===Placeholders in H5P prefixed with % or : characters must not be translated===
The [http://h5p.org/ H5P editor] integrated with Moodle since 3.9 has some variables prefixed with "%" or ":" that must not be translated because they are transformed internally with the correct value. They should be treated as the Moodle curly brackets variables.
* Example of variables with "%" that can not be translated and must be copied exactly:
"Parameters contain %used while only %supported or earlier are supported."

In that case, %used and %supported must not be translated. So, for instance, the Spanish translation would be something like:
"Parámetros contiene %used mientras que sólo se soportan %supported o anterior."
* Example of variables with ":" that can not be translated and must be copied exactly:
"The :property value exceeds the maximum of :max."

In that case, :property and :max must not be translated. The Spanish translation for this string would be something like:
"El valor de :property excede el máximo de :max."
=== All fieldnames must be kept in English===
* These names are hooks that are used in the software. You should not translate them.
* See the example below for the string uploadcourses_help in the file tool_uploadcourse for Moodle 3.1:
[[File:Fieldnames are not to be translatd.png]]
* Notice that the string text indicates (red rectangle) that these words (enclosed in green rectangles) are fieldnames. Also notice that the Spanish translation clearly indicates, at the final part of the paragraph ''(así escritos, en inglés)'' that these fieldnames must be written in English as they are written here.
* Some used fieldnames in Moodle are:
category, category_id, category_idnumber, category_path, context, course, description, descriptionformat, email, enrolmentkey, firstname, fullname, groupname, hidepicture, idnumber, intro, lastname, maxgrade, maxrequest, name, password, picture, section, shortname, teachers, timeopen, timeclose, timeend, timestart, username, visible,
* Examples of strings where these fielnames appear are uploadcohorts_help | core_cohort, importgroups_help | core_group, uploadcourses_help | tool_uploadcourse and uploadusers_help | tool_uploaduser.
* Note that these fieldnames may appear as real fieldnames (must not be translated) or as regular words in another context (can and must be translated). You should exercise caution and, If possible, always check that Moodle works correctly by testing your translations with some data in a real or test server.
===Local addresses after <a href="../===
Addresses inside a Language string that have <a href="../ reference a specific URL inside your Moodle server and you must keep the address part of the expression, but you can translate the descriptive name part. See the following example:
noassignableroles | tool_cohortautoroles
There are currently no roles that can be assigned in the user context. <a href="../../roles/manage.php">Manage roles</a>
* You must keep the <a href="../../roles/manage.php"> part, as this references to the [https://docs.moodle.org/31/en/PHP PHP] code in your Moodle server that will be executed in order to manage roles
* You can/should/must translate 'Manage roles'
* Do not forget to keep the ending </a>
===Moodle Docs addresses after <syntaxhighlight lang="php"><nowiki><a href="http://docs.moodle.org/en/</nowiki></syntaxhighlight>===
Addresses inside a Language string that have <syntaxhighlight lang="php"><nowiki><a href="http://docs.moodle.org/en/ </nowiki></syntaxhighlight>reference a specific URL in the Moodle English Documentation. You must look at that address and '''only''' if your language has a valid translation for that page, you can/should replace the original English Docs address with your own language address. See the following example:
core backup | nonisowarning
Warning: this backup is from a non-Unicode version of Moodle (pre 1.6). If this backup contains any non-ISO-8859-1 texts then they may be CORRUPTED if you try to restore them to this Unicode version of Moodle. See the <a href="http://docs.moodle.org/en/Backup_FAQ">Backup FAQ</a> for more information about how to recover this backup correctly.
* There are six different language translations for that page. So, you can only replace this address if your language is one of these.
===Other internet addresses after <a href="http://===
* You must proceed as with Moodle Docs addresses:
* Example:
auth_radius | auth_radiusdescription
This method uses a <a href="http://en.wikipedia.org/wiki/RADIUS">RADIUS</a> server to check whether a given username and password is valid.
* You must check the (English language wikipedia) page about the RADIUS server, and then you can decide whether to keep this address or replace it with your own language matching wikipedia translation.
===HTML codes that must not be translated===
The following HTML codes are reserved words that must not be translated. However, it is important for the translators to understand their meaning in order to decide whether to keep them in the translation and if so, whether they can be rearranged.
* <syntaxhighlight lang="php">&nbsp</syntaxhighlight> - non-breaking space i.e. a space but there will never be a line-break inserted instead of this space at the end of a line.
* <syntaxhighlight lang="php">&ensp</syntaxhighlight> and <syntaxhighlight lang="php">&emsp</syntaxhighlight> - denote an en space and an em space respectively, where an en space is half the point size and an em space is equal to the point size of the current font. For fixed pitch fonts, the user agent can treat the en space as being equivalent to a single space character, and the em space as being equuivalent to two space characters.
* <syntaxhighlight lang="php">&amp</syntaxhighlight> - ampersand sign (&)
* <syntaxhighlight lang="php">&apos</syntaxhighlight> - apostrophe sign (')
* <syntaxhighlight lang="php">&copy</syntaxhighlight> - copyright sign (©)
* <syntaxhighlight lang="php">&plusmn</syntaxhighlight> - "plus or minus" sign (±)
* <syntaxhighlight lang="php">&times</syntaxhighlight> - multiply sign (*)
* <syntaxhighlight lang="php">&divide</syntaxhighlight> - divide sign (/)
* <syntaxhighlight lang="php">&gt</syntaxhighlight> - "greater than" sign ( > )
* <syntaxhighlight lang="php">&lt</syntaxhighlight> - "less than" sign (<)
* <syntaxhighlight lang="php">&laquo</syntaxhighlight> - quotation mark (‘)
* <syntaxhighlight lang="php">&lsquo</syntaxhighlight> - left single quotation sign (‘)
* <syntaxhighlight lang="php">&rsquo</syntaxhighlight> - right single quotation sign (’)
* <syntaxhighlight lang="php">&ouml</syntaxhighlight> - small letter o with diaeresis (ö)
* <syntaxhighlight lang="php">&mdash</syntaxhighlight> - [https://en.wikipedia.org/wiki/Dash#Em_dash em dash] sign (—)
===Calculation functions must not be translated===
[https://docs.moodle.org/32/en/Grade_calculations#Calculation_functions Calculation functions] start with an equal sign (=). Following is an expression using operators and functions supported by the system.
[[File:DO NOT translate calculation functions.png]]
===The 'thisdirection' and 'thisdirectionvertical' strings in core_langconfig should never be translated===
'''The 'thisdirection' and 'thisdirectionvertical' strings in core_langconfig should never be translated, as they are not variables meant to be translated. They are prefixing selectors used by the themes to display left-to-right or right-to-left languages. Read [https://moodle.org/mod/forum/discuss.php?d=328567#p1323101 more about problems with these variables].
===MoodleBox===
The word 'MoodleBox' must be kept in all languages.
===Safe Exam Browser===
A feedback by the Safe Exam Browser main developer:
The software is called “Safe Exam Browser” in any language, we don’t translate the name of the application. So it doesn’t make sense to translate it in any plugin, you could use it as a subtitle or in brackets, like “Safe Exam Browser (Navegador de Examen Seguro)”.
==Is there a way to check the integrity of all placeholders in a language pack?==
* Not a at the moment. See MDL-51775 .
* You can use [https://lang.moodle.org/mod/forum/discuss.php?d=4661 this trick] to check for integrity:
** Load the language pack in a [https://download.moodle.org/windows/ local instance of Moodle].
** In order to generate a [https://lang.moodle.org/mod/forum/discuss.php?d=4098 translation memory], load the language pack in the [https://docs.moodle.org/29/en/Language_customisation Language customization] tool, so that the texts are loaded in the database.
** Run the sql instance in the file (tm_generator.txt)
** Insert the result of the query in template.tmx file
** The result is a translation memory that can be analysed with [http://www.opentag.com/okapi/wiki/index.php?title=CheckMate Checkmate].
** The problem: probably you will get many errors due to some characters that are not allowed by Checkmate so you will have to remove manually some translation units. After doing it, you will get a report with some possible errors (see the attached image).
** Of course, it would be great to have an integrated quality check system in Moodle. Vote for MDL-51775 .

* The contents of the file tm_generator.txt are ('''change the language from eu to your language'''):
SELECT concat('<tu tuid="',mdl_tool_customlang_components.name,'|',mdl_tool_customlang.stringid,'">
<tuv xml:lang="en"><seg>',mdl_tool_customlang.original,'</seg></tuv>
<tuv xml:lang="',mdl_tool_customlang.lang,'"><seg>',mdl_tool_customlang.master,'</seg></tuv>
</tu>') as txt
FROM mdl_tool_customlang INNER JOIN mdl_tool_customlang_components ON mdl_tool_customlang.componentid = mdl_tool_customlang_components.id
WHERE (((mdl_tool_customlang.lang)="eu") AND ((mdl_tool_customlang.original) Is Not Null) AND ((mdl_tool_customlang.master) <>mdl_tool_customlang.original));
* the contents of the template.tmx file are:
<?xml version="1.0" encoding="UTF-8"?>
<tmx version="1.4"><header creationtool="SQLQuery" creationtoolversion="unknown" segtype="paragraph" o-tmf="unknown" adminlang="en" srclang="en" datatype="unknown"></header><body>
PLACE HERE THE RESULT OF THE SQL QUERY
</body>
</tmx>
==What is a ''translation memory'' and how can I create a translation memory out of a Moodle language pack?==
* Read the 'Is there a way to check the integrity of all placeholders in a language pack?' section above.
* See [https://lang.moodle.org/mod/forum/user.php?id=1489&page=1 this post] and [https://dl.dropboxusercontent.com/u/86242384/moodle/en/publish/moodle_tm/website_index.html this tutorial].
==How can I help with translating Moodle documentation?==
Please see the guide [[Translating Moodle Docs]].
==How can I find out the context of the strings?==
You can find where a language string is located as described in the user docs [[:en:Language_customisation#Finding_the_component_and_string_identifier|Finding the component and string identifier]] and [[:en:Language FAQ|Language FAQ]].

You may wish to use two windows (perhaps using two monitors), with one displaying the page in English and the other displaying the page in your language.

[[File:two windows translation.jpg|Two simultaneous windows in two languages|800px]]

If you think the original English language strings have more than one meaning and you can't guess which one applies, you are welcome to post in the [https://lang.moodle.org/mod/forum/view.php?id=5 AMOS translation forum].
==Is there a list of Moodle error messages which can be translated?==
Error messages are listed in the user docs [[:en:Category:Error|Category:Error]].
==Can the subtitles for Moodle HQ YouTube videos be translated?==
Unfortunately this is currently not possible. For details, see [[Translating Moodle video subtitles]].
==Can the User Tours from Moodle.net be translated?==
* Yes. See [[Translating User tours from Moodle.net]]
==How can I test my plugins translations of several (different) Moodle branches?==
*Linux
** You can have several Moodle branches in one Ubuntu (or any other Linux distro) machine by following [https://docs.moodle.org/31/en/Step-by-step_Installation_Guide_for_Ubuntu#Hosting_several_Moodle_branches_in_one_Ubuntu_server these steps].

* Windows
** You can have several [https://download.moodle.org/windows/ local Moodle servers] in different folders in a Windows (7,8,10) PC. It is very easy to start one branch server, work on it, stop it and then start a different branch.
{{Note|Some early local Moodle (versions before 3.0) server packages from [https://download.moodle.org/windows/ https://download.moodle.org/windows/] only work in Windows 7, but apparently not in Windows 8 and definitely not in Windows 10, regardless of compatibility settings. For these you would need to install XAMP separately. Moodle 3.0 and newer branches do work under Windows 10.}}
*Mac
**We need to write about this...
==Can I translate a language pack offline / can I use another language then English as source language?==
Yes you can, but it is not recommended because there is a high risk of causing problems (remember - sites update language packs automatically, so your problem spreads quickly over the world).
One problem is that you absolutely have to avoid untranslated strings or strings in the wrong language in the language pack. This should NEVER happen. Another problem is that there is no way to know which strings are already translated. There is also a higher risk for syntax errors. If you have to, you can follow the following procedure:
* download the English language pack (or another one if you want a different source language)
* translate directly in the php file, preferably using something with syntax highlighting (Geany, Gedit, Notepad++ on Windows, ...)
* IMPORTANT: delete all not-translated lines from the file, before uploading - therefore it is probably best to translate line by line and keep the original source files, so you can work with a record of processed line numbers.
* import the files in the translation portal following the manual on https://docs.moodle.org/dev/AMOS_manual#Importing_a_file (IMPORTANT: zip file cannot contain any folders)
==How can I translate H5P content types?==
Use [https://translate-h5p.tk/weblate/projects/h5p/ the Weblate H5P project translation page] or see the h5p.org guide [https://h5p.org/adding-content-type-translation-via-github Adding content type translations via GitHub] and the forum discussion [https://moodle.org/mod/forum/discuss.php?d=414325 Translate H5P items].
==See also==
* [[:en:Language customization|Language customization]] in the user docs for information on how to edit an existing language pack
* [[String Deprecation]] is introduced in Moodle 2.8 to help minimize the language files but avoid accidental lost of translations by simply removing strings.
* [https://lang.moodle.org/mod/forum/discuss.php?d=4098#p4879 Generating a translation memory and running a quality test] forum discussion
* [https://moodle.org/mod/forum/discuss.php?d=347843 translation in context] forum discussion
[[de:Übersetzung FAQ]]

Moodle App Translation

2022-09-09T09:38:01Z

Marycooch: redirect

This page is now located in the user docs: [[:en:Translating the Moodle App|Translating the Moodle App]]

Moodle App Translation

2022-09-09T09:37:35Z

Marycooch: Changed protection level for "Moodle App Translation" ([Edit=Allow only autoconfirmed users] (indefinite))

{{Template:Migrated|newDocId=/general/development/process/translation/moodleapp}}
{{Translation}}

==Moodle App translations==

The Moodle App is being translated into more and more languages! Check out [https://moodle.org/plugins/translations.php?plugin=local_moodlemobileapp the latest translation stats].

==How do I translate words and phrases used in the Moodle App?==

To help with translating, you first need to create an account on the [http://lang.moodle.org Moodle translation site].

Moodle App strings may be found using this filter: https://lang.moodle.org/local/amos/view.php?t=1&c=*app&m=1

Just select the desired language and click "Show strings" to display them.

===Advanced selection of strings===

All strings used in the app are indexed in [https://github.com/moodlehq/moodleapp/blob/master/scripts/langindex.json the langindex.json file].

They have the following format:

* <code>"{module}.{string-identifier}": "{component}"</code> — In this case the string will be translated using the <code>{string-identifier}</code> on the <code>{component}</code> file.
* <code>"{module}.{string-identifier}": "{component}/{component-string}"</code> — In this case the string will be translated using the <code>{component-string}</code> on the <code>{component}</code> file.

Some examples are:

* <code>"addon.block_recentlyaccessedcourses.nocourses": "block_recentlyaccessedcourses"</code> — This means it will use the <code>nocourses</code> translation from the <code>block_recentlyaccessedcourses</code> component in AMOS.
* <code>"addon.mod_workshop.yourassessment": "workshop/assessmentbyyourself"</code> — This means it will use the <code>assessmentbyyourself</code> string from the </code>workshop</code> component in AMOS.

The <code>local_moodlemobileapp</code> component has the specific strings of the Moodle App, but most of the strings are located in other components. To select all the Moodle App strings, click on "Moodle App" below the components selector. This action will auto-select the following:

* Last version available option (it is selected by default). The propagation to other version is done automatically.
* Components used in the App.
* Only strings that are being used in the Moodle App: This will filter only the strings used in every component on the app.

Additionally, you will see a little mobile in the strings used in the app. Hovering over this icon, you can read the string identifier in the app.

==I am not a language pack maintainer. How can I contribute a translation?==

The process is the same as for core Moodle. See [[Contributing a translation]].

Note: Please contact the maintainer of your language pack as listed in the [http://lang.moodle.org/local/amos/credits.php Translation credits] to tell them that you are translating the Moodle App. If you don't receive a reply within a reasonable time, contact our Moodle translation coordinator, Koen Roggemans, at [mailto:translation@moodle.org translation@moodle.org].

==When will the translated strings be shown in the Moodle App?==

Translations are not automatically synchronised with the app, you will have to wait to the next release to see your latest contributions.

==My language does not appear in the app==

Only some languages are available in the app, the selection is done using the following criteria:

* Over 75% of the strings used in the app are available in the language and more than 50 strings are from the <code>local_moodlemobileapp</code> component.
* Over 50% of the strings used in the app are available in the language and more than 75 strings are from the <code>local_moodlemobileapp</code> component.

This is done to ensure translations are rich enough.

==How can I translate my plugin?==

If you are developing a plugin, you'll have to indicate which strings you want to use in the <code>lang</code> configuration option. You can learn more about this in the [[Moodle App Plugins Development Guide]].

[[Category:Mobile]]

Translating Moodle Docs

2022-09-09T09:35:56Z

Marycooch: redirect

This page is now located in the user docs: [[:en:Translating Moodle Docs|Translating Moodle Docs]]

Translating Moodle Docs

2022-09-09T09:35:30Z

Marycooch: Changed protection level for "Translating Moodle Docs" ([Edit=Allow only autoconfirmed users] (indefinite))

{{Template:Migrated|newDocId=/general/development/process/translation/docs}}
{{Translation}}
==Contributing to the documentation==
Moodle Docs pages, such as the page you are reading right now, are wiki pages available in [https://docs.moodle.org/overview/ several languages]. Any registered Moodle user can contribute to Moodle Docs and improve or translate these wiki pages. Please make sure to follow the [[:en:Guidelines_for_Contributors|guidelines for contributors]].

You might find it useful to add the original English documentation pages that you have just translated to your watchlist (alt-shift-w), so that you will know when your translation might need to be re-checked for a possible update.

==Translating the screen images used in Moodle Docs==
* If you want to recreate the bright orange-coloured screen images used in the Documentation pages (eg, [https://docs.moodle.org/30/en/New_features Moodle 3.0 New features Docs page]), you can replicate the [http://school.demo.moodle.net/ Mount Orange school] theme in your local server by following the details outlined [https://docs.moodle.org/30/en/Standard_themes#Mount_Orange:_example_of_a_customised_More_theme here for Moodle 3.0] and [https://docs.moodle.org/34/en/Standard_themes#Example_of_a_customised_Boost_theme here for the Boost theme in more recent Moodle branches].

===Replicating the Mount Orange theme look in a local server with the Boost theme===
* You will need to download the cloudy background from [https://docs.moodle.org/34/en/File:bg6.png here] and the Mount Orange image from [https://docs.moodle.org/30/en/File:Mount_Orange_Front_page_image.jpg here].
* You may insert these two images in a label in a Moodle course and notice (write down) the paths that references where these images have been stored, as you will need to input these paths later.

* Go to your site home and edit the site home summary.

[[File:Edit_Site_home_01.png]]

** You need to click on the very first tool button in order to show all the tools buttons in the Atto editor.

[[File:Edit_Site_home_02.png]]

** You need to click on the </> button in order to input HTML code:

[[File:Edit_Site_home_03.png]]

** You must input the code described in 'Front page topic section' of https://docs.moodle.org/34/en/Standard_themes#Example_of_a_customised_Boost_theme. Do NOT click the 'Save' button yet:

[[File:Edit Site home 04.png]]
** Replace 'YOUR UPLOADED FRONT PAGE IMAGE.jpg' with the path to your recently uploaded front page image, that you carefully wrote down earlier.
** Now is the time when you replace the 'YOUR HEADING' text with the translated text for your Orange-coloured School ('Escuela Monte Naranja' for this Spanish language example).
** Replace the 'SMALLER HEADING' text in both places with your language text strings.
** Replace 'Paragraph of text' in both places.
** Replace 'BUTTON TEXT' in both cases-
* When you click again on the <> button, the HTML code will be interpreted and you will see the graphics displayed and the texts rendered in a nice orange-colored style:

[[File:Edit_Site_home_05.png]]
** Check the result, and correct if necessary.
** You can now save your changes.

* Go to Administration, Appearance, Themes, Boost, advanced settings
* Paste the 'Boost theme Advanced settings - Raw initial CSS:' and 'Boost theme Advanced settings - Raw SCSS:' codes from https://docs.moodle.org/34/en/Standard_themes#Example_of_a_customised_Boost_theme.
** In the 'Boost theme Advanced settings - Raw SCSS:' section, replace 'YOUR UPLOADED BACKGROUND IMAGE.jpg' with the path to your recently uploaded cloudy background image.
* Replace the original English language text with the appropiate text for your language pack.
* Check that your Mount Orange clone site looks good.
* Compare your site's front page with the image of [https://docs.moodle.org/34/en/File:MountOrangeFrontPage.png Mount Orange 3.4 front page], or better yet, compare your site with [http://school.demo.moodle.net/ the current Mount Orange] page.
** Correct if necessary.
* If all is fine, save the changes.

* You can now use your emulated translated Orange site to replicate the beautiful images Moodle HQ used to illustrate [https://docs.moodle.org/33/en/New_features Moodle 3.3 new features] (or newer branches) in Moodle Docs.

==Which documentation pages are most important or useful to translate?==

Many Moodle users will start reading the [[:en:Main Page|English docs main page]]. This might be a good page to have translated.

The [[:en:New_features|new features in the latest version]] would surely be of interest to the users of previous Moodle versions that want to catch up with the new available features.

The [[:en:Category:Quick_guide|quick guides]] are very short pages (that hopefully you can very quickly translate) that teachers can quickly check, in order to grasp how an important Moodle feature works, without having to read the standard detailed (long) Moodle full documentation pages.

The [[:en:Table_of_Contents|Table of contents]] has a very comprehensive and organized list of important Moodle topics. This might be a worthy addition to your language documentation.

If you see a post which has been rated as 'Useful' several times in a [https://moodle.org/course/ Forum in a language other than English], which links to an untranslated English documentation page, it might be a good idea to translate this page.

The English Documentation Special Page with the [https://docs.moodle.org/30/en/index.php?title=Special:MostLinkedPages&limit=100&offset=0 Most linked-to pages] shows the English pages that have the highest number of links and (except for all the User: pages) you will find there many pages highly useful for Moodlers of all languages and worth translating to your language (eg, [https://docs.moodle.org/30/en/Managing_a_Moodle_site Managing a Moodle site] & [https://docs.moodle.org/30/en/Managing_a_Moodle_course Managing a Moodle course]).

''If you are a Moodle site admin or teacher, using a language other than English, and you use the 'Moodle Docs for this page' link in your daily work, please consider translating the English pages that helped you most to do your job and solve your problems.'' See below.

==Translating the Documentation pages for 'Mooodle Docs for this page' and 'More help' links==

* When logged in as an admin or teacher, 'Moodle Docs for this page' links at the bottom of each page in Moodle take you to documentation about that page in your language, if it exists, otherwise in English.
[[File:Moodle Docs for this page.png|300px]]
* You might be tempted to start typing the documentation in your own language (if such a page exists), but please don't do it. Instead, change your language to English and then click in the 'Moodle Docs for this page' link.
* In the English documentation page that just opened, add a language link for your language (see [https://docs.moodle.org/dev/Starting_a_new_docs_wiki Interlanguage-linking]), save it and then open the given translation page.
* If the English Documentation page has only a redirect instruction, please add a translation for the redirection and then save the English page with the redirection
[[File:Redirected page.png|400px]]
[[File:Redirected page in English.png|400px]]
* Make sure that you add a translation link for the redirection, check that it works (create the page if it did not exist) and save the page.
[[File:Redirected page in English with Spanish translation link.png|400px]]
* You can now jump to the redirected page in your own language and work on it.
[[File:Redirected page in Spanish.png|400px]]
* The 'More help' links have the same icon (i) and work the same way as the 'Moodle Docs for this page' links.

==Is it important to translate English Documentation pages that only have one #Redirect instruction?==
Yes, it is very, very fast and it will make your translated wiki more efficient, because you will replicate all the automatic redirections that exist in the English Docs in your own language Docs, specially with the Docs pages related to online help for specific pages in your Moodle server (see the example above).

If you have translated Documentation pages with #Redirect instructions, it will then be a good idea to go to the TOOLS column at the bottom of the page (in your language wiki documentation) and click on 'Special pages'. There, check the 'Broken redirects' and 'Double redirects' links and fix any pages that might show up there.

==Which English documentation pages will change when there is a new Moodle version release==

* If you have a translation of [https://docs.moodle.org/dev/Releases https://docs.moodle.org/dev/Releases] you will need to update it
* The [[:en:New_features|new features in the latest version]] mentioned above must now have the new available features.
* You might need to update the version numbers in your translated documentation for these pages:
** [https://docs.moodle.org/en/Upgrading https://docs.moodle.org/en/Upgrading]
** [https://docs.moodle.org/en/Installation_Quickstart https://docs.moodle.org/en/Installation_Quickstart]
** [https://docs.moodle.org/en/Installing_Moodle https://docs.moodle.org/en/Installing_Moodle]
** [https://docs.moodle.org/en/Git_for_Administrators https://docs.moodle.org/en/Git_for_Administrators]
** [https://docs.moodle.org/en/Upgrade_overview https://docs.moodle.org/en/Upgrade_overview]
** [https://docs.moodle.org/en/Language_packs https://docs.moodle.org/en/Language_packs]

==See also==

* [[Starting a new docs wiki]]
* [[Help strings]] in the developers documentation

[[Category:Moodle Docs]]
[[Category:Translation]]

Translating plugins

2022-09-09T09:35:04Z

Marycooch: redirect

This page is now located in the user docs: [[:en:Translating plugins|Translating plugins]]

Translating plugins

2022-09-09T09:34:36Z

Marycooch: Changed protection level for "Translating plugins" ([Edit=Allow only autoconfirmed users] (indefinite))

{{Template:Migrated|newDocId=/general/development/process/translation/plugins}}
{{Translation}}
==Looking for translated plugins in the Moodle plugins database==

* Almost all contributed plugins published in Moodle Plugins directory have been imported into [http://lang.moodle.org/ AMOS] and are ready to be translated.
*Watch this video tutorial on [https://www.youtube.com/watch?v=E_20uU1ibcA&feature=youtu.be Translating a Moodle plugin]
* When a user is looking at the [https://moodle.org/plugins/ Moodle plugins database], in ' Description tab > Useful links section' there is a link to 'Contribute translation for (your preferred language)' that points to [http://lang.moodle.org/ AMOS].
* Have a look at an example for the very popular [https://moodle.org/plugins/view.php?plugin=mod_hotpot HotPot] plugin:

[[File:Link to Plugin translations in Moodle plugins database.png|300px]]

* You can click on the 'Contribute translation for (your preferred language)' link.
* '''CURRENTLY:''' If you do not have an AMOS account, you would have to 'Create a new account' by using the appropriate link.
* If you have a translator account in AMOS, you can use AMOS to contribute the translation.
* If you select all the language packs (except English fixes) and write 'pluginname' in the box for 'String identifier', AMOS will display the name of the plugin in all available translations.
* Make sure that you have selected the Moodle branch(es) that you are interested in (eg, 2.5 in the image below).

[[File:Plugins translations in AMOS.png|400px]]

* In the above example, there are a total of 123 different language packs registered in AMOS; 63 of these are missing a translation for HotPot, which means that there are 60 different language translations already available for the HotPot plugin, a fair number for this popular plugin :)
* When no translation is available for any/many language(s), the box named 'Translation' will be empty for those languages.
* If a plugin name has been translated, there is a fair chance (but no certainty) that this plugin has been (completely) translated into that language. You can change the settings in AMOS and check for yourself.

==Plugin translation priority==
* Please help Moodle users in other languages by translating your favourite plugins.
* Moodle has a continuously updated [https://moodle.org/plugins/report/index.php?report=favourites&p=0&l=50&s=favourited&d=DESC list of the most favourite plugins], which might be worth considering for translation :)
* In mid-2019, the [https://moodle.org/plugins/mod_hvp H5P plugin] is the most downloaded additional activity plugin and it is expected to [https://docs.moodle.org/dev/Roadmap#Moodle_3.8_and_beyond:_in_progress be incorporated into Moodle 3.8 core].
* You can find the plugins with the largest number of downloads in the last three months at [https://moodle.org/plugins/stats.php https://moodle.org/plugins/stats.php]. These are the plugins most likely to be most useful when translated to your language. It would probably be a good idea to translate them first.
* Moodle has a list of plugins that have received the [https://moodle.org/plugins/browse.php?list=award&id=1 Reviewers' choice award]. These are given by the plugins guardians and reviewers for particularly useful, well coded or otherwise interesting plugins. It would be very desirable/useful to have these translated.
* See the [https://moodle.org/mod/forum/discuss.php?d=325804 list of (year 2015) favorite plugins] by Gavin Henrick
* Special cases:
** All plugins with ''mobile'' in their name, and all [https://moodle.org/plugins/browse.php?list=set&id=62 server side plugins] to support the [https://docs.moodle.org/38/en/Moodle_Mobile Moodle mobile app]
** [https://moodle.org/plugins/local_moodlecloudsignup MoodleCloud strings] are used for accessing the [https://moodle.com/cloud/ MoodleCloud] free and paid hosting services.

===Elementary school teaching===
If your Moodle site will serve kids, consider [https://docs.moodle.org/38/en/Language_packs#Can_I_make_a_language_pack_for_kids.3F making a language pack for kids].

===Plugins for K-12 teaching===
For [https://en.wikipedia.org/wiki/K%E2%80%9312 K-12] teaching and learning environments, please consider translating the plugins that are included in the [https://moodle.com/cloud/school/?utm_source=Sendy&utm_medium=Email&utm_campaign=Newsletter_July2016 Moodle for School at MoodleCloud]:
* [https://moodle.org/plugins/mod_attendance Attendance]
* [http://bigbluebutton.org/ BigBlueButton]
* [https://moodle.org/plugins/mod_checklist Checklist]
* [https://moodle.org/plugins/atto_chemistry Chemistry editor]
* [https://moodle.org/plugins/mod_choicegroup Group choice]
* [https://moodle.org/plugins/block_xp Level up!]
* [https://moodle.org/plugins/mod_quizgame Quizventure]
* [https://moodle.org/plugins/tinymce_wordcount Word count]

===Plugins for University teaching===
For universities, there is a [https://docs.moodle.org/38/en/Tertiary_education#Moodle_plugins_by.2Ffor_Universities list of plugins by/for Universities], and a [https://docs.moodle.org/38/en/Tertiary_education#Discipline-specific_plugins link to discipline-specific plugins], which might be worth translating.

==H5P plugin==
===H5P translations in AMOS===
You must translate all the H5P (and hvp) related plugins in AMOS:

[[File:h5p TRANSLATIONS IN amos 1.png|400px]]

[[File:h5p TRANSLATIONS IN amos 2.png|400px]]

THEN you will ALSO have to translate the H5P module strings in the H5P site. You can do it either using weblate (preferred method) or GitHub (old method).

===H5P translation using weblate (preferred method)===
Visit [https://translate-h5p.tk/contributing/ https://translate-h5p.tk/contributing/] and register.

If there is a maintainer for your language, you can make suggestions for string translations.

Check [https://h5p.org/forum/6 https://h5p.org/forum/6] for the FAQs and your questions/doubts/problems.

If there are no maintainers for your language, you may request to become a maintainer (send an email to serettig@posteo.de).

If one (or a few) of the English source strings is blank, you can simply leave it blank in your translation, too. Weblate might complain about an untranslated string, but you can ignore that!

It is VERY IMPORTANT to make sure that all the English language strings have been translated. If that file has only been partially translated, you should use the original English language strings. If you leave an empty field, there will be a serious ERROR that will block weblate progress. See the following screeens:

[[File:H5P weblate problem with strings not translated.png|500px]]

And the weblate will CLOSE this module for translation:

[[File:H5P weblate problem with strings not translated WEBLATE blocked.png|700px]]

If weblate closes a module for translation, you can only add or change language strings vía GitHub (see below).

If you are a language maintainer, ONLY after making sure ALL the strings for one H5P module have been properly translated into your language, you should Commit your changes to wordslate ('Manage' -> Commit). THEN you should PUSH your changes ('Manage' -> Repository maintenance -> PUSH). You must then wait for the people responsible for the GitHub code to review and accept your pull requests by way of weblate.

Don't forget to always push your changes once you've finished a library so that Joubel can review and accept them.

If you notice a typo or any other error in the original English language strings, you can write an issue (or a Pull request) in the GitHub page of the original H5P module. They will be very happy to check it and fix it if necessary.

====Translation of H5P module's names using weblate====

After translating all the H5P strings using weblate, you may consider translating [https://next.lumi.education/ LUMI] using weblate, as that will allow H5P users to see the H5P modules' names and descriptions in languages other than English when they use the free [https://next.lumi.education/ LUMI] app to produce .h5p files to be used in a Moodle course.

[[File:H5P LUMI 3.png|600px]]

The description of each H5P module in other languages might make it easier for many new Moodle users of H5P:

[[File:H5P Flashcards LUMI en español.png|600px]]

===H5P translation using GitHub (old method)===
While the [https://moodle.org/plugins/mod_hvp H5P plugin for Moodle] is currently (April 2020) installed in 14333 sites, and the Moodle roadmap shows 'improved H5P integration' contemplated for Moodle 3.8 and beyond, only 30 languages (April 2020) have any translated language strings in AMOS.

[[File:H5P editor french language.png|600px]]

Even after translating the [https://moodle.org/plugins/mod_hvp H5P plugin for Moodle] in AMOS, most users of this plugin in languages other than English may see (partly or totally) untranslated strings when using it. This is because all H5P libraries ("components" / "plugins") have their own separate [https://github.com/h5p/h5p-contribution-docs/blob/master/en/translations.md translation infrastucture] which is not related to the H5P Moodle plugin and we are not sure what is the frequency of merging and distributing the contributed translation pull requests that we see on each library's repository on GitHub.

[[File:H5P editor es_mx language.png|600px]]

There is a page providing an overview of the H5P content-type translation status at [https://localization.h5p.org/ https://localization.h5p.org/ ]

[[File:H5P_translation_02.png|600px]]

When you click on a language (Spanish in this example), you will see all the H5P modules with the proportion of strings translated into that language.

[[File:H5P translation 03.png|600px]]

When you click on a module (Audio in this example) you will see a list of all the untranslated and translated strings for that language for that module

[[File:H5P translation 04.png|600px]]

At the botton of that page, there will be a link to 'Head over to the source repository'. If you click on that link, you will be taken to the GitHub page for that module, where you can fix or add the translations for your language and make a 'Pull request' to contribute this translation.

[[File:H5P translation 05.png|600px]]

See also:

* [https://translate-h5p.tk/ h5p.tk] - a user-friendliy platfform that you can use to translate H5P strings.
* the [https://h5p.org/adding-content-type-translation-via-github Guide for Adding content type translations via GitHub].

==Non-translatable strings==
While AMOS does a great job for translating the Moodle core and most Moodle plugin language strings, some English language strings are not available for translation with AMOS.

===Plugins in the [https://moodle.org/plugins/browse.php?list=category&id=38 Other] category===
The plugins classified as '[https://moodle.org/plugins/browse.php?list=category&id=38 Other] ' (Utilities, Experimental or Incubating) are not translatable by AMOS (see [http://lang.moodle.org/mod/forum/discuss.php?d=3113 this forum thread]). You can use the [[:en:Language customization|language customization]] tool within your Moodle (production or local) server to produce the .php file containing the translated language strings for your language and email this file to the particular 'other' plugin maintainer, so that it can be included in the lang folder within the downloadable Zip file for the plugin.

===Plugins with coding errors===
Some plugins (of types different from 'Other') available for download in the [https://moodle.org/plugins/ Moodle plugins directory] may not have English language strings available for translation in [https://lang.moodle.org/ AMOS] because of [https://docs.moodle.org/dev/index.php?title=Plugin_contribution_checklist&redirect=no coding errors], that must be identified and fixed by the plugin maintainer, See [https://docs.moodle.org/dev/Plugin_contribution_checklist#Strings Plugin contribution checklist:Strings]:
* The plugin code must not rely on trailing and leading whitespace in strings.
* The string file must be considered as pure data file with the syntax $string['id'] = 'value';
* No other PHP syntax such as [http://php.net/manual/en/language.operators.string.php concatenation], [http://php.net/manual/en/language.types.string.php heredoc and nowdoc] is supported by the tools that AMOS use when processing the strings (even if it may work in Moodle itself).
* Use neither string concatenation operators nor other PHP logic inside string files. Those should really be considered as plain data files with simple $string['key'] = 'value'; syntax, nothing more.

===Plugins with hard-wired English language strings===
Sometimes you might have translated 100% of the strings available in AMOS for a given plugin, and you can still view the original English (non-translated) strings.
* Please check that you have purged your browser cache and the server cache, waited for one hour (for AMOS to update the language packs), and updated your language packs.
* If the problem persists, please write the plugin maintainer by clicking at the 'Bug tracker' link shown in the given plugin's page in the [https://moodle.org/plugins/index.php Moodle plugins database].
* If the plugin author has nested additional 'Lang' folders inside any subdirectories within the plugin folder structure, the English language strings in these nested Lang folder will not be available for AMOS, and they would seem to be hard-wired. Please contact the plugin author.
* Most Moodle plugin authors have been very fast at replacing the English hard-coded strings with strings variables that can now be translated in AMOS.
* If you suspect the problem is in a core plugin, you can post an issue in the [https://lang.moodle.org/mod/forum/view.php?id=5 AMOS translation forum].

===Log descriptions can not be translated===
* See [https://docs.moodle.org/dev/Translation_FAQ#Why_are_log_descriptions_displayed_in_English.3F why log descriptions are not translated].

===Items that must NOT be translated===
* See the [https://docs.moodle.org/dev/Translation_FAQ#Are_there_items_which_are_not_to_be_translated.3F Items that are not to be translated] in the [https://docs.moodle.org/dev/Translation_FAQ Translation FAQ]

==If translations are available in AMOS for some Moodle branches but not available for other branches==
Sometimes a plugin may have its English language strings available for translations for some Moodle branches (e.g. 2.0 to 2.4), but not for other branches (e.g. 2.5 to 2.7), even though the plugin itself is indeed available for download for all branches (2.0 to 2.7) in the Moodle plugins database.

Please see an example in [http://lang.moodle.org/mod/forum/discuss.php?d=3939 this post]. The cause is very likely a programming error (see 'Plugins with coding errors' above), that must be fixed by the plugin maintainer.

==What happens if a plugin ZIP file includes translation(s) inside the lang folder==
If a site has debugging on, there will be a warning message about 'Found language file' when the user installs the plugin, but the installation may proceed.

[[File:Found language file debugging message.jpg|400px]]

The Language strings inside a properly installed downloaded plugin will overwrite the strings translations of the language pack, but they can be overwritten by the strings defined with the Language customization.

===Strings priority===
When displaying text language strings, Moodle 2.x and 3.x will have the following priority:
# Strings defined by the [[:en:Language customization|language customization]] tool
# Strings defined in an installed child language pack (eg, the es_ve language pack)
# Strings defined in an installed parent language pack (eg, the es language pack)
# Strings enclosed inside the plugin_name/lang/xx/yy.php folder (where xx is a language code other than the en folder) from a downloaded and installed plugin ZIP file (eg, inside the /server/moodle/theme/adaptable/lang/es/theme_adaptable.php file)
# Original Australian English language strings shipped with the downloaded Moodle branch.
# Original Australian English language strings inside the /lang/en folder in the downloaded/updated plugin ZIP file

Note: See the [https://moodle.org/plugins/local_string_override local String override plugin] that makes it possible for plugins to override existing translations regardless if they're bundled with Moodle or they're originated from a community plugin.

==See also==

* [http://lang.moodle.org/mod/forum/discuss.php?d=2485 Contributed plugins are now automatically imported into AMOS] announcement explaining the mechanism
* [https://docs.moodle.org/dev/Translation_FAQ#Are_there_items_which_are_not_to_be_translated.3F Items that are not to be translated] in the [https://docs.moodle.org/dev/Translation_FAQ Translation FAQ]

[[Category:Plugins]]

Starting a new language pack

2022-09-09T09:34:07Z

Marycooch: redirect

This page is now located in the user docs: [[:en:Starting a new language pack|Starting a new language pack]]

Starting a new language pack

2022-09-09T09:33:33Z

Marycooch: Changed protection level for "Starting a new language pack" ([Edit=Allow only autoconfirmed users] (indefinite))

{{Template:Migrated|newDocId=/general/development/process/translation/langpack}}
{{Translation}}
If Moodle is not yet translated into your language and you would like to help, please [http://lang.moodle.org/login/signup.php create an account on the Translation site] and contact our Moodle translation coordinator, Koen Roggemans, [mailto:translation@moodle.org translation@moodle.org].

Once your language pack has been set up, you can follow the instructions provided in [[Maintaining a language pack]].

First:
* '''Make sure [[Translation_langconfig|langconfig]] is properly set up'''. It would be a very good idea to ask for other translators to double-check your translation of this extremely important file by posting a request in the [https://lang.moodle.org/mod/forum/view.php?id=5 Translating Moodle forum].
* Take a look at [[Translation priority]]. All files have a rating according to how urgent they need translating.

If you have any questions about using AMOS, please post in the [http://lang.moodle.org/mod/forum/view.php?id=5 Using AMOS forum].

==Starting a child language of an existing language pack==
If your country uses a variation of an existing language, that has a few (or many) differences from an [https://docs.moodle.org/dev/Translation_langconfig#parentlanguage.2Ccore_langconfig existing parent language] (ie, Canadian French is a variation of French, or US English has some spelling differences from UK English), a child language might be a good solution, as only the strings that need changes have to be uploaded to AMOS.
Some examples of existing child languages and the changes from the parent language for Moodle 3.2 are:

* Català (Valencià) , 4416 changes from ca
* Dansk (kursus) , 42 changes from da
* Dansk Rum , 879 changes from da
* Davvisámegiella , 104 changes from no
* Deutsch community , 260 changes from de_du
* Deutsch - Du , 890 changes from de
* Deutsch - Kids , 234 changes from de_du
* English - Pirate , 1687 changes from en
* English for kids , 82 changes from en
* English - United States , 628 changes from en
* Español de México para niños , 142 changes from es_mx
* Español Venezuela , 40 changes from es
* Filipino , 927 changes from tl
* Finlandssvenska , 3437 changes from sv
* Français - Canada , 989 changes from fr
* Hebrew kids , 1226 changes from he
* Japanese kids , 32 changes from ja.
* Kalaallisut , 560 changes from da
* Lithuanian (university) , 14359 changes from lt
* Lulesamisk , 8 changes from no
* Norsk , 797 changes from no
* Norsk - nynorsk , 3245 changes from no
* Sørsamisk , 8 changes from no
* Suomi+ , 1165 changes from fi
* Suomi Filipino , 927 changes from tl
* Wolof , 202 changes from fr

If your local language only has a few differences from an existing language, it still qualifies as a different language for Moodle, and it can have its own language pack (if someone is willing to create and maintain it).

==Defining the language code==
For historical reasons we use the [https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes ISO-639-1] code for the representation of the language. If that doesn't exist, we use the [https://en.wikipedia.org/wiki/List_of_ISO_639-3_codes ISO639-3 code] (e.g. Moroccan Tamazight).
In some exceptional cases, like the Occitan languages, we combine the [https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes ISO 639-1] code with the [https://en.wikipedia.org/wiki/List_of_ISO_639-6_codes ISO 639-6] code, eg oc_gsc (keep in mind that the [https://en.wikipedia.org/wiki/List_of_ISO_639-6_codes ISO 639-6] standard is [http://www.iso.org/iso/catalogue_detail?csnumber=43380 withdrawn]).
Other exceptions includes the _kids addition for language packs for very young children and some other exceptions. These exceptions should be kept to a minimum.

AMOS manual

2022-09-09T09:33:08Z

Marycooch: redirect

This page is now located in the user docs: [[:en:AMOS manual|AMOS manual]]

AMOS manual

2022-09-09T09:32:28Z

Marycooch: Changed protection level for "AMOS manual" ([Edit=Allow only autoconfirmed users] (indefinite))

{{Template:Migrated|newDocId=/general/development/process/translation/amos}}
{{Translation}}
'''AMOS stands for Automated Manipulation Of Strings. AMOS is a central repository of Moodle strings and their history. It tracks the addition of English strings into Moodle code, gathers translations, handles common translation tasks and generates language packages to be deployed on Moodle servers.'''

The name was chosen in honour of [https://en.wikipedia.org/wiki/John_Amos_Comenius John Amos Comenius], the author of ''Janua linguarum reserata'' (Gate to Languages Unlocked). Sorry Tori ;-)

AMOS is hosted on our '''[https://lang.moodle.org Moodle translation site]'''.

== Basic concepts ==

AMOS consists of several tools available via the main navigation block - Translator, Stage, Stashes, Contributions and Log.

* Translator - is a tool that allows you to filter strings you want to work on and translate them.
* Stage - is a temporary working area that holds the strings you have translated during the current session. Maintainers can permanently commit the stage into the strings repository. Contributors can submit the stage for maintainers.
* Stashes - are snapshots of the stage. Imagine them as ordinary files at your computer where you can save your work. You can submit your stash to the language pack maintainers.
* Contributions - is a database tracking all submitted contributions and their current status. Records in this database are like issues in the Moodle tracker with the translated strings attached.
* Repository - a database of all Moodle strings and their history running at lang.moodle.org server.
* Log - displays the log of all modifications of Moodle strings.

== Translation workflow ==

The following data flow diagram illustrates how AMOS tools are used during the translation process.

[[image:amos-workflow.png]]

The key AMOS component is the staging area or shortly the stage. It holds translated strings temporarily during your current login session. If you log out, the stage is cleared (though there is a backup - see below). There are several ways how translations can be staged, that is how translated strings can be put into the stage:

* by using the AMOS translator
* by importing strings from an uploaded file
* by applying a previously created stash
* by applying a submitted contribution

Language pack maintainers have write access to the AMOS strings repository. Therefore they can commit their stage permanently. Once the stage is committed, staged strings are stored in the AMOS repository. Every hour, AMOS generates ZIP packages from the most recent snapshot of the repository. These ZIP packages are published on the language pack download pages https://download.moodle.org/langpack/. In addition, Moodle sites can install and update language packages automatically via ''Site administration > Language > Language packs''.

Community members do not have write access to the repository so they can't commit their stage. Instead, they can submit it to the maintainers. By submitting a stage, a new contribution record is created and language pack maintainers are notified by automatic email message. Maintainers can review the submitted contribution and, if they accept it, commit it on behalf of the contributor.

The stage can be also saved so you can interrupt your work and continue next time you come back to the site. The stage is saved into the so called 'stashing area'. The stashing area consists of stashes. A new stash is simply a snapshot copy of your current stage. AMOS automatically keeps one stash for you as a backup copy of your most recent stage. A stash can be submitted to the maintainers too.

== AMOS tools ==

=== Using the translator tool ===

[[image:amos-screenshot-translator.png|300px|thumb|right|AMOS Translator tool]]
The translator tool page has two main parts. At the top, there is a filter form (1). You use that filter to get the strings you want to translate. When the filter settings are saved (2), a table with the filtered strings is displayed below.

Every row in the table represents a single string. The table has four columns. The first column (3) describes the version (or branch) where the string is used, its identifier and its component. You can see a text like

2.0 [completiondate,coursereport_completion]

That reads: this string is used in Moodle 2.0, its identifier is 'completiondate' and it belongs to 'courserepor_completion' component.

The second column (4) contains the English original of the string. Below the text, you can see Google icon. Click that icon to get automatic translation of the string into the language being translated. The next column contains a code of the language that this string is being translated to (for example "cs" for Czech).

Finally the last column contains the translation itself. If it is empty, the string is not translated yet, otherwise it displays the current translation. '''Click in the cell to turn it into the input editor.''' Insert the translation and click outside the cell to stage the translation. Note there is no submit button, the text is sent to the stage automatically in the background. You can see that the colour of the cell turned blue. Blue colour signalizes that the translation is currently staged.

You have many options of how to use the strings filter. You can work on a single component or all missing strings at once. You can search for strings containing a given text (either in English or the translated string) etc. You can check for strings in older versions, too but those strings are read-only. They get automatically pulled into AMOS from the CVS repository of 1.x translations.

The 'permalink' below the filter's submit button can be used to keep the current filter settings. For example, you can bookmark a setting use regularly or you can copy the link URL and send it to somebody so they can set their filter just by visiting that URL.

When you finish translating, do not forget to visit the stage page. You probably want either commit it (if you are a lang pack maintainer) or submit it to maintainers so they can review your work and include it into the language pack.

Sadly, sometimes, AMOS may consider that your request-URI is too large to handle :(

[[File:Permalink request -uri too large.png|600px]]

=== Using the stage ===

[[image:amos-screenshot-stage-contrib.png|300px|thumb|right|Strings staged by a contributor]]
The translated strings are put into a temporary area called ''stage'' immediately after the cursor leaves the editor field. The stage holds your work before it is either committed into the repository (if you are language pack maintainer) or submitted to the maintainers for inclusion or stashed.

The stage is cleared when you logout. You have to explicitly commit or stash the stage so it is saved permanently. If you forget to do it, or there is a problem with the connectivity, your browser crashes or whatever, you can find your most recent snapshot of the stage in autosave stash.

If you are language pack maintainer, you can commit the stage into the repository so your work is registered and the translated strings become part of the official language package. You can also propagate the strings to other branches by selecting the branches you want the string to go to and hit the propagate button. It is a wise thing to do that, to save work and to keep consistency in the wording over the versions.

Updated language packages in ZIP format are published hourly at https://download.moodle.org/langpack/3.8/ - look at the bottom of the page to see the last update. At the same time, they become available for Moodle sites for automatic update.

The stage can also be used to import strings from files and to merge or compare versions of language packs.

=== Importing a file ===

[[image:amos-screenshot-stage-empty.png|300px|thumb|right|Empty stage allows you to import strings from a file]]
Strings can be translated offline and uploaded back to AMOS using the stage page. The only supported format at the moment is common PHP format used by Moodle where strings are defined in associative array called $string. For obvious security reasons, AMOS can not actually execute PHP files uploaded by users. Instead, it parses the uploaded file in a similar way as PHP parser, looking for patterns that are considered as valid string definition. That means that not every valid PHP code is valid string definition. AMOS parser requires following conditions are met:

* the filename is valid component name used by Moodle, for example moodle.php, enrol_manual.php or workshop.php
* the file is valid PHP code without syntax errors - that means is passes the PHP lint check
* strings are defined as elements of global array $string
* strings are single quoted constants

Example of a valid file to import into AMOS (filename countries.php, Czech translation)

<?php

$string['AE'] = 'Spojené Arabské emiráty';
$string['AF'] = 'Afghánistán';
$string['CH'] = 'Švýcarsko';
$string['HU'] = 'Maďarsko';

?>

During the import, strings found in the file are added into your stage as if they were translated via web. You can commit them into repository if you have such privilege.

You can import several .php files at once if you put them into a ZIP file (Maximum size: 2MB) and import this ZIP file.

=== Using stashes ===

At any moment, you can save a snapshot of the current stage. We call such snapshot a ''stash''. Stashed strings are kept forever until you drop them manually (please do not abuse this and keep your stashes reasonable big). To manage your stash, click on Stashes in the right menu of AMOS. You just see a list of the stashes. There are "peekaboo" buttons that appear when you mouse hoover over the stashes. The stash can be ''applied'' so that the stashed strings are copied back to the stage. What the ''pop'' does is apply and drop (delete) the stash. ''drop'' is like delete. ''submit to maintainer'' opens a form for doing just that.

There is one special stash record for every user called autosave stash. This stash keeps the most recent state of the stage. You may find it useful if you loose the current stage for any reason - your browser crashes, your internet connectivity dies or you accidentally unstage all strings. If that happens, just apply the autosave stash to get your work back. The autosave stash is updated every time you stage a string. So if your stage is empty and your autosave stash is full of strings and you go into the translator first without applying the stash, the autosave will be replaced with the new translated string. We recommend to experiment a bit with this feature first.

=== Using the log tool ===

The Log page allows even anonymous users to search in the history of commits tracked by AMOS. At the top of the page there is a filter that allows you to look for a particular information or report. It is important to realize how the filter actually works. Searching and filtering happens in two steps (this was necessary for performance reasons):

* Firstly, commit records are searched based on the criteria specified in the Commit filter form. If there are more commits found matching the filter settings, only 100 most recent commits are processed.
* Then, within the commits found, either all string modification records are returned, or you can filter these records, too. Settings in String filter form section are used in that case.

By default, the filter looks for all commits since the last time you logged in and than displays only strings at the currently translated branch modified by those commits.

===Language packs and Moodle versions===

When a new Moodle version is released, it will become the default version on your Amos - Translator page (see tick boxes at the top).

The suggested work flow is to continue your translation work for the new Moodle version and merge your work in the older versions.
Some time ago, people used to do that using the Amos - Stage page: Set the source version to the version you were working in and set the target version to the version you want the strings to be copied to. Nowadays AMOS automatically propagates (most of) the strings to all suitable branches.

==Keeping track of your 'favorite' plugins strings to translate==
You can use the ''permalink'' feature for frequently checking a finite set of additional plugins for missing or outdated string.

The permalink feature is supposed to work like this:
* You use the AMOS filter settings (that is, you define which versions, components, etc, you want to see). For example, you can select version 3.1, then all core components and some additional components.
* You press "Save filter settings" and let AMOS show you the strings.
* Then you can copy or bookmark the URL that is available via the "Permalink" link.
* Following that URL should set the filter back to the current settings.

* The problem is that AMOS does not allow you to mix strings from one component version with strings from another component version at the moment. So you can't see things like "Workshop 3.1 strings together with Essential 3.0 strings". You would have to select both 3.0 and 3.1 version fields, and both Workshop and Essential components. But that would lead to Workshop strings being displayed twice.

{{Note|It would be useful for you to have a couple of bookmarked / saved permalinks per version. So you would have one for "3.1 core and interesting additional plugins", another one for "3.0 interesting plugins", another one for "2.9 interesting plugins" etc. That way, you can regularly check these three or four links and have your areas of interested monitored well.}}

== See also ==

* [[Automated Manipulation of Strings 2.0]] for the AMOS developer spec
* [https://www.youtube.com/watch?v=JtY5zvEHnQ8 Accepting submissions] Instruction video for language pack maintainers
* [https://www.youtube.com/watch?v=XClUZOuFfWo Contributing to a language pack] Instruction video for language pack contributors
* [https://www.youtube.com/watch?v=xT2-ElTaH6M Changing the default language] Instruction video on how to change your default language

[[fr:AMOS]]
[[es:AMOS]]

Maintaining a language pack

2022-09-09T09:32:00Z

Marycooch: redirect

This page is now located in the user docs: [[:en:Maintaining a language pack|Maintaining a language pack]]

Maintaining a language pack

2022-09-09T09:31:22Z

Marycooch: Changed protection level for "Maintaining a language pack" ([Edit=Allow only autoconfirmed users] (indefinite))

{{Template:Migrated|newDocId=/general/development/process/translation/maintaining}}
{{Translation}}
==Volunteering to become a language pack maintainer==

If your language currently doesn't have a language pack maintainer, and you would like to volunteer, please [http://lang.moodle.org/login/signup.php create an account on the Translation site] and contact our Moodle translation coordinator, Koen Roggemans, [mailto:translation@moodle.org translation@moodle.org].

== The role of language pack maintainer==
A language pack maintainer for a Moodle language pack takes responsibility for that language pack. It means contributing to the translation, reviewing contributions of other contributors and approving, improving or rejecting them within a reasonable time frame. The language pack maintainer must pay special attention to the consistency of all Moodle and other terminology all over the language pack. He/She must also pay special attention to the technical correctness of what goes in the language pack since problematic strings can ultimately cause a site in that language to break.

The aim of a language pack maintainer is to get the language pack complete for a standard Moodle installation.

== Steps for the maintainer, making own contributions==

# Use AMOS translator interface to translate missing strings or amend the current translation
# Go to the Stage page
# Make a meaningful comment about your work in the 'Commit message' form
# Click on 'Commit'

== Approving contributions from others==

AMOS allows community members to help with the translation of Moodle strings.
[[image:amos-screenshot-contribution-details.png|300px|thumb|right|Contribution details page]]
# When a user submits a new contribution, you will receive an automatically generated email from AMOS containing a link to the contribution.
# Press 'Start review' button. That will assign the contribution to yourself, change the status from 'New' to 'In review', send an automatically generated email to the contributor and will copy the submitted strings into your stage. You should check that your stage is empty before you apply the submitted strings unless you want to merge several contributions into one commit.
# Review the submitted strings, eventually edit them. Commit the stage. It is nice to mention the contributor's name in the commit message and attribute the original authorship to them.
# Go back to the contribution record and change the status to Accepted or Rejected. An automatically generated email will be sent to the contributor whenever you change the status.
# Use contribution record comments for further communication with the contributor about the submitted translation.
# Accepted and Rejected contributions are not shown at the contributions page unless you click the 'Show resolved contributions' button.
# You will get a weekly reminder of contributed strings that are not processed yet.

==Translating strings offline==

You can use the [[:en:Language customization|Language customisation]] tool in your local Moodle server to enhance the translation of language strings for the Moodle core files.
If you want to translate the strings of a particular plugin, you must have that plugin installed on your server first.
Your translated files will be located inside the local language folder in your Moodle server.
You can upload these files to AMOS, one file at a time, or zip many files and upload the zip file (which will be un-zipped automatically inside AMOS).

==Uploading a file of translations==

To avoid making changes one by one, you can do your translations offline (as above) and upload them to AMOS.
# Click 'Stage' in the Navigation block.
# Choose 'Import translated strings from file'.
# Dag and drop the file.
# Click the 'Import' button.

*Note: You can import several files at once if you zip them first and upload the zip file. The zip file is not allowed to contain any folders, only files.

==See also==
* [[AMOS manual]] for further information about the AMOS translation toolkit
* [[:en:Language packs|Language packs]] user documentation

Contributing a translation

2022-09-09T09:30:48Z

Marycooch: redirect

This page is now located in the user docs: [[:en:Contributing a translation|Contributing a translation]]

Contributing a translation

2022-09-08T08:58:54Z

Marycooch: redirect

This page is now located in the user docs: [[:en:Translation|Translation]]

Contributing a translation

2022-09-08T08:57:37Z

Marycooch: Changed protection level for "Contributing a translation" ([Edit=Allow only autoconfirmed users] (indefinite))

{{Template:Migrated|newDocId=/general/development/process/translation/contributing}}
{{Translation}}
The [http://lang.moodle.org Translation site] enables translators to work collaboratively on language packs using a special Moodle translation tool called ''AMOS''. If you see an error or non-translated term in Moodle in your language, you can contribute a correction or translation via the Translation site.

When contributing, the quality of your work is more important then the quantity. Make sure spelling, grammar, capitals and punctuation are correct. Only use terminology consistent with the rest of the language pack. Don't make mistakes in technical parts of the strings, like variable placeholders, html etc. For these reasons, using automatic translation (e.g, Google Translate) is never good enough.

If you'd like to help translating more than just a few strings, please contact the maintainer of your language pack as listed in the [http://lang.moodle.org/local/amos/credits.php Translation credits]. (If you don't receive a reply within a reasonable time, contact our Moodle translation coordinator, Koen Roggemans, [mailto:translation@moodle.org translation@moodle.org].)

==Getting started with AMOS==

# [http://lang.moodle.org/login/signup.php Create an account on the Translation site] and log in.
# Click the link [http://lang.moodle.org/local/amos/view.php AMOS translator].
# In the Languages box, ''select your language''.
# In the Components box, find the language strings you wish to translate.
# Click the button 'Save filter settings'.
# Type your translation into the boxes on the right. When you click out of the box, it will turn blue and your text will be saved automatically.
# When you have finished translating, click the button at the bottom of the page 'Go to the stage'. Do no more than 30 strings at a time.
# Review your translation, then click the button 'Send strings to language pack maintainers'.
# (Optional) Add a message for the language pack maintainer explaining what you have done.

{|
|[[File:translate1.png|thumb|Add your translation]]
|[[File:translate2.png|thumb|Submit your translation]]
|}

Note: You only need to contribute translations for ONE version, as the translations are added automatically to other versions when your contribution is accepted. Simply leave 'Latest available version' ticked.

==What happens next==

The maintainer(s) of the language pack will receive notification of your contribution. It will be reviewed and then most likely added to the language pack. You will receive email notification when the status of your contribution changes i.e. when a maintainer begins their review and then when they accept or reject it. At any time you can use the contribution record comments to communicate with the maintainer about your submitted translation.

In addition, your name will then appear on the [http://lang.moodle.org Translation site] front page as a recent, valued contributor. Well done!

Once you have three contributions accepted, you are listed as a contributor in the [http://lang.moodle.org/local/amos/credits.php Translation credits].

==Tips and Tricks==
* If you are a bilingual (or multilingual) developer of a Moodle plugin, please send your strings of languages other than English to the language pack maintainer(s).
* Bear in mind that If a language pack maintainer gets a contribution with 250 strings of various modules, that is a nightmare to review :(
** It is better to send contributions of a few strings at a time.
** 30 strings of one module should really be the maximum, 10 strings from one module at a time is better :)
* Please note that '''there are some things that should never be translated''', such as Moodle placeholders and HTML variables. See [[Translation_FAQ#Are_there_items_which_are_not_to_be_translated.3F| Translation FAQ]]
* Please don't flood the language pack maintainer by sending the same strings more then once. If strings are in the contribution queue, they stay in the queue until the maintainer can review them.
* Never submit untranslated or half translated strings. Only good quality translations with checked spelling, correct punctuation, well formed sentences and consistent wording with the rest of the language pack are worth adding to the language pack.
* Never send strings that are translated already without improving them, e.g. by blindly uploading offline translated strings.
* Avoid a mix of newly translated strings and improved strings.

==See also==
* [[AMOS manual]] for further information about the AMOS translation toolkit
* [http://www.youtube.com/watch?v=XClUZOuFfWo| Video on how to contribute to a language pack]
* [[Improving English language strings]]

Translation

2022-09-05T07:11:17Z

Marycooch:

{{Note|[https://docs.moodle.org/en/Translation Translation documentation] is available in the user documentation.}}

Translation

2022-09-04T13:18:00Z

Marycooch: WIP redirects

{{Note|[https://docs.moodle.org/en/Translation Translation documentation] is available in the user docs.}}

Translation

2022-09-04T12:56:03Z

Marycooch: Removed protection from "Translation"

{{Translation}}
==So you'd like to help with translating Moodle?==

Great! :-) All translation happens on our '''[http://lang.moodle.org Moodle translation site]''', so you'll need to start by creating an account there.

Perhaps you've found some words or phrases not yet translated into your language? Or you've spotted a mistake? If so, please see the guide to [[Contributing a translation]].

Note: If you'd like to help translate more than just a few strings, please contact the maintainer of your language pack as listed in the [http://lang.moodle.org/local/amos/credits.php Translation credits] and ask where you can help.

==Wish to take on responsibility for a language pack?==

Please see [[Maintaining a language pack]] and the [[AMOS manual]] for further information about the AMOS translation toolkit.

==Is Moodle not yet translated into your language?==

Please see [[Starting a new language pack]].

==Any questions?==

Please check the [[Translation FAQ]] and join us in the [http://lang.moodle.org/mod/forum/view.php?id=5 Using AMOS forum].

==See also==

* [https://download.moodle.org/langpack/3.8/ Language packs for Moodle 3.8] for the percentage of language strings translated in each language pack for the current Moodle branch

[[fr:Traduction]]
[[de:Übersetzung]]
[[es:Traducción]]

Translating Moodle video subtitles

2022-04-22T10:36:50Z

Marycooch: removed trusted contributor details.

{{Translation}}
'''Note: In September 2020, Youtube disabled community contributed subtitles.'''

For the Moodle HQ videos on Moodle 4.0 available in https://www.youtube.com/playlist?list=PLxcO_MFWQBDcI0BezfCOW8QRfJw6FblRn the user can choose to have automatically generated closed captions being automatically translated to a user language different from English.

The user watching a YouTube video must choose the cog symbol, choose Autotranslate and choose the target language. Obviously the CC icon must be activated for the auto-translated closed captions to be shown in these YouTube videos.
[[File:CC autotranslated.png|thumb|CC auto-translated]]

Translating Moodle video subtitles

2022-04-21T12:45:16Z

Marycooch: typo

Contributing to Moodle

2022-04-01T08:31:43Z

Marycooch: updated to add Academy dev pathway

There are lots of ways you can contribute to the Moodle project:

==User support==

Join in with the international discussions in [http://moodle.org/course/view.php?id=5 Moodle in English] or [https://moodle.org/community/ community discussions in many other languages].

==Moodle Users Association==

The [https://moodleassociation.org/ Moodle Users Association] (MUA) is a not-for-profit incorporated association that helps drive the Moodle project. The MUA provides a strong and united voice to users, giving direction and resources for new developments. It is a separate entity from Moodle Pty Ltd and other organisations involved in the Moodle open-source project. Members of the Association decide twice a year on new development projects for Moodle core; access an exclusive peer group of Moodle users; and gain some early, deeper insights into Moodle core developments. Different member levels (for individuals and institutions) are available. Shape the future of Moodle today, join MUA!

==Documentation==

Help write and edit our [https://docs.moodle.org/overview/ user documentation in various languages] or our [[Main_Page|developer docs]].

==Testing==

Help test and report bugs via the [http://tracker.moodle.org/ Moodle Tracker] (see the [[Tracker introduction|introduction to the Tracker]]) and participate in [[QA testing]].

==User experience (UX)==

Participate in discussions in the [https://moodle.org/ux Moodle UX area] in and sign up to help with Moodle UX research.

==Development==

[[Process#Fixing_a_bug|Fix a bug]] in Moodle core. If you are looking for a good issue to start with, please see the [https://tracker.moodle.org/issues/?jql=project%20%3D%20MDL%20AND%20type%20in%20(bug)%20AND%20status%20%3D%20open%20AND%20Difficulty%20%3D%20Easy%20AND%20labels%20not%20in%20(patch)%20ORDER%20BY%20created%20DESC list of relatively easy Moodle bugs].

Help [http://moodle.org/development develop new code for Moodle] or share your code in the [https://moodle.org/plugins Plugins directory].

Adopt a [https://moodle.org/plugins/browse.php?list=set&id=61 plugin seeking a new maintainer] and help many users. See the [https://moodle.org/mod/forum/discuss.php?d=260354 Plugins adoption programme].

See also [[Working with the Community]].

Sign up to free self-paced courses in our [https://learn.moodle.org/ Moodle Academy Developer Learning Pathway] to help you learn and extend your Moodle development skills.

==Themes==

Share your theme in the [https://moodle.org/plugins/browse.php?list=category&id=3 Themes section of the plugins directory].

==Translation==

Assist with the [[Translation|translation]] of Moodle, including [[Contributing a translation|contributing a translation/correction]], [[Translating plugins|translating a plugin]], [[Translating Moodle video subtitles|translating Moodle screencasts subtitles]] or [[Improving English language strings|suggesting an improvement to an English language string]].

==Social media==

Help [https://moodle.org/social/ raise awareness of the Moodle project and share the latest news and happenings] in the Moodle world

==Books and video courses==

A percentage of all sales from [https://moodle.org/mod/data/view.php?id=7246 books or video courses] goes to Moodle Pty Ltd to help support Moodle development.

==Shop Official Merchandise==

Moodle receives a percentage from each item purchased from our official [https://moodle.com/shop/ Moodle Shop]

==Vote for future Moodle improvements==

See the [https://docs.moodle.org/dev/New_feature_ideas new feature ideas]. [https://tracker.moodle.org/issues/?filter=10512 Check the Moodle tracker and vote] for the issues that you think will improve Moodle the most.

==Moodle Partners==

A certified network of Moodle Partners contribute to the Moodle project. Moodle Partners offer services such as hosting, support, installation, custom coding, course development and consulting, amongst others. Find our full listing of [http://moodle.com/partners/ Moodle Partners here.]

==More ways to contribute==

Do you want to help but don't have the time? Do you want to give something back to the project to help pay the developers who make it happen? Then please make a [http://moodle.com/donations donation] to the project.

Talk:QA testing

2022-02-17T09:00:10Z

Marycooch:

When clicking the ""Moodle QA Telegram chat room" link in the page, and after choosing to open Telegram web, the message "There is no Telegram account with this username" is shown.

QA testing has not begun yet so perhaps wait until then?--[[User:Mary Cooch|Mary Cooch]] ([[User talk:Mary Cooch|talk]]) 08:59, 17 February 2022 (UTC)

Talk:QA testing

2022-02-17T08:59:53Z

Marycooch:

When clicking the ""Moodle QA Telegram chat room" link in the page, and after choosing to open Telegram web, the message "There is no Telegram account with this username" is shown.
QA testing has not begun yet so perhaps wait until then?--[[User:Mary Cooch|Mary Cooch]] ([[User talk:Mary Cooch|talk]]) 08:59, 17 February 2022 (UTC)

Translating Moodle video subtitles

2022-02-16T04:43:10Z

Marycooch: removing out of date info

Translating Moodle video subtitles

2020-11-27T07:53:41Z

Marycooch: updating info re translations

{{Translation}}
'''Note: In September 2020, Youtube disabled community contributed subtitles. Early in 2021 a [https://support.google.com/youtube/thread/73769191?hl=en "trusted contributor" scheme] is planned, whereby specific translators can access channels with limited permissions to translate subtitles. Once this is in place, Moodle HQ will arrange for subtitles to be translated again.'''

For each major release, Moodle HQ creates a number of screencasts to showcase step-by-step new features and improvements. Certain screencasts, starting with Moodle '''3.2''' have translations enabled.
This means the subtitles may be translated online, on YouTube. ''(Note not all HQ screencasts have this feature enabled.)''

You can find all Moodle HQ videos for the Learn Moodle Basics 3.x series at https://www.youtube.com/c/moodle/playlists when you scroll down to "Learn Moodle: A collection of Video Tutorials".

[[File:Learn Moodle 3.8 to 3.6 basics.jpg|t600px]]

==How to translate HQ videos==

1) From the [https://www.youtube.com/user/moodlehq Moodle HQ YouTube channel,] find the video you wish to translate. (You need to be logged in with a Google account)

* You may want to translate the videos for the most recent Moodle branch (e.g, [https://www.youtube.com/playlist?list=PLxcO_MFWQBDdJu-ct9wJQTTS3owR-lELq Moodle 3.8 videos])
* You may want to translate the videos from the Learn Moodle Basics MOOC (eg, [https://www.youtube.com/playlist?list=PLxcO_MFWQBDfMnwMzFBq0ab9wSPniXEkp Learn Moodle 3.8 Basics])
* You may want to translate the 11 videos for [https://www.youtube.com/playlist?list=PLxcO_MFWQBDdF2i_Rw4vn4G0VVNNN7P4V Learn Moodle beginner admin]

* You can watch a [https://youtu.be/iN1R6yKL6sg screencast on translating the videos here] -or read the instructions below:

2) Click the cogwheel/settings icon:
[[File:VideoTranslate01.png|thumb|500px|center]]
3) Click the subtitles/CC link:
[[File:VideoTranslate02.png|thumb|500px|center]]
4) If contributions have been enabled for this video you will see Subtitles/CC. Click there:
[[File:VideoTranslate03.png|thumb|500px|center]]
5) Select your language by typing in its first few letters:
[[File:VideoTranslate04.png|thumb|500px|center]]
6) Type the translations under the English (1) and then click (2) Submit for review:
[[File:VideoTranslate05.png|thumb|500px|center]]
7) If you want credit, tick the box:
[[File:VideoTranslate06.png|thumb|500px|center]]
8) Once you have clicked ‘submit,’ a notification will be sent to a Moodle HQ Communications staff for review

9) Once the video is reviewed and the translation published,(if desired) your name and a link to your YouTube channel will appear in the description of the video:
[[File:VideoTranslate07.png|thumb|500px|center]]
10) A Moodle Communications team member will also let you know when it is published before communicating the translated videos through social channels, news post and other tools (with a credit to you)
Questions / for further assistance, please contact mary@moodle.com

Moodle.org FAQ

2020-11-13T12:00:06Z

Marycooch: replacing support email with contact form

==I tried to make an account on moodle.org but I didn't get an email to confirm my address. Why?!==

Most likely the email ended up in the spam folder of your email account. Please check carefully; if there is no sign of it, use the [https://moodle.com/contact/support/?selection=community#form Moodle.com contact form].
==I'm getting tons of email copies of forum posts. How do I stop them?==

* '''Either''' open one of the emails, scroll to the bottom of it and click the link 'Unsubscribe from this forum' or 'Unsubscribe from all forums'
* '''Or''' log in to moodle.org then go to your user menu (top right) > Preferences > Notification preferences and click to turn off email notifications of subscribed forum posts.

If you'd still like forum post notifications, just not so many emails, in Preferences > Forum preferences you can enable an email digest i.e. one email per day containing all recent forum post notifications.

You can also receive forum post notifications via Moodle messaging or the Moodle app (see Preferences > Notification preferences) or can monitor forum activity via an RSS feed.

==What is the best way to ensure my question is answered?==

See [[Moodle.org forums help]] for advice.

==Is it OK to post my question in more than one forum?==

Please choose only the most appropriate forum to post in. Posting the same question in multiple forums is of no benefit. It only fragments the support you receive and makes it more difficult for other users to find the correct information in the future when they do a search. (Source: [https://moodle.org/mod/page/view.php?id=7080 Moodle.org site policy].)

==I have an idea for a new feature in Moodle. What do I do?==

See [[New feature ideas]].

==Where can I report any spam I come across on moodle.org?==

To report spam in forum posts or comments, please use the 'Report to moderator' link.

To report spam sent via Moodle messaging, or spam on any other Moodle community site, use the [https://moodle.com/contact/support/?selection=community#form Moodle.com contact form].
==My post has been incorrectly flagged as containing spam==

Occasionally our spam prevention system reports false positives. Please use the [https://moodle.com/contact/support/?selection=community#form Moodle.com contact form] if your forum post was blocked by mistake.

==Where can I report a problem on one of the Moodle community sites?==

Please check whether the problem has already been reported: https://tracker.moodle.org/browse/MDLSITE. If not, create an issue for it, selecting Moodle community sites as project.

==How are icons added next to certain users' forum posts?==

The icons for [http://moodle.org/user/index.php?id=5&group=1 Particularly helpful Moodlers], [http://moodle.org/user/index.php?id=5&group=172 Core Developers] etc. are pictures indicating group membership. Group pictures may be added when [[:en:Groups|creating or updating a group]].

==What advertising is allowed on moodle.org?==

See the section on advertising in the [https://moodle.org/mod/page/view.php?id=7080 Moodle.org site policy].

==How can I link automatically to a tracker issue from a forum post?==

Simply type the issue number e.g. MDL-1234.

==How can I link automatically to a page in the documentation wiki from a forum post?==

Type the title of the page in double square brackets. To use words other than the page title as the text of the link, add the pipe "|" divider followed by the alternative text.

For example, to link to the documentation on upgrading type
<nowiki>[[Upgrading]]</nowiki>
or
<nowiki>[[Upgrading|Documentation on upgrading]]</nowiki>

To link to a page in a documentation wiki in another language, add an extra pipe "|" divider followed by the language code.

For example, to link to https://docs.moodle.org/fr/Notes type
<nowiki>[[Notes||fr]]</nowiki>
or
<nowiki>[[Notes|Notes documentation in French|fr]]</nowiki>

==What filters are used on moodle.org?==

See [[:en:Filters used on the Moodle.org forums]] for the full list of standard and contributed filters.

==Where can I post a Moodle-related job advert?==

Moodle-related jobs offered may be posted in the [http://moodle.org/mod/data/view.php?id=7232 Moodle Jobs database].

==Why does Moodle Docs use MediaWiki rather than the Moodle wiki module?==

MediaWiki was chosen for our documentation wiki because it is designed to be used by thousands of people collaboratively editing a large numbers of pages. It has lots of features, such as inter-language linking, [[MoodleDocs:Templates|templates]], [[Special:Categories|categories]], namespaces and page redirects, which are put to good use in Moodle Docs.

The [[:en:Wiki module|wiki module]] is designed to be used within a Moodle course. It has far fewer tools than MediaWiki for handling large numbers of pages.

==Where can I find the Moodle logo for use in my article?==

http://moodle.org/logo

==How do I ask for my account on moodle.org to be deleted?==

Go to https://moodle.org/admin/tool/dataprivacy/createdatarequest.php?type=2 and click the button 'Save changes'.

==Why did I receive a password reset email when I didn't request it?==

If someone accidentally mistypes their username when logging into moodle.org, and doesn't notice their mistake, it's likely they will request a new password. With over 2 million registered accounts on moodle.org, there's a good chance that the mistyped username is the same as someone else's. Thus a password reset email can be generated by mistake.

If you received a password reset email when you didn't request it, please just ignore it.

==Why have I received an email saying that my account is locked?==

After several failed login attempts, a user's account is locked and they are sent an email containing a URL to unlock the account. With over a million registered accounts on moodle.org, it's possible that someone can accidentally mistype their username or password and inadvertently lock another user's account.

If you receive an email saying that your moodle.org account is locked when you haven't attempted to log in, please don't worry. Simply follow the URL to unlock your account or wait 30 minutes after which time a locked account is automatically unlocked.

For more details of the account lockout feature, see [[:en:Site policies|Site policies]].

[[Category:FAQ]]
[[Category:Moodle.org]]

MoodleDocs:About

2020-11-12T12:30:04Z

Marycooch: removed support@moodle.org and replaced with contact form link

The '''Dev docs''' are written by developers in the Moodle community.

The site is based on wiki technology and is powered by [https://www.mediawiki.org MediaWiki].

==Contact==

* For feedback and suggestions about the Dev docs, please join the discussions in the [https://moodle.org/mod/forum/view.php?id=7135 Moodle community sites forum].
* For account queries please use the [https://moodle.com/contact/support/?selection=community#form Moodle.com contact form].
[[Category:Moodle Docs]]

Translating Moodle video subtitles

2020-01-27T21:08:27Z

Marycooch: updating links

{{Translation}}
For each major release, Moodle HQ creates a number of screencasts to showcase step-by-step new features and improvements. Certain screencasts, starting with Moodle '''3.2''' have translations enabled.
This means the subtitles may be translated online, on YouTube. ''(Note not all HQ screencasts have this feature enabled.)''

==How to translate HQ videos==

1) From the [https://www.youtube.com/user/moodlehq Moodle HQ YouTube channel,] find the video you wish to translate. (You need to be logged in with a Google account)

* You may want to translate the videos for the most recent Moodle branch (e.g, [https://www.youtube.com/playlist?list=PLxcO_MFWQBDdJu-ct9wJQTTS3owR-lELq Moodle 3.8 videos])
* You may want to translate the videos from the Learn Moodle Basics MOOC (eg, [https://www.youtube.com/playlist?list=PLxcO_MFWQBDfMnwMzFBq0ab9wSPniXEkp Learn Moodle 3.8 Basics])
* You may want to translate the 11 videos for [https://www.youtube.com/playlist?list=PLxcO_MFWQBDdF2i_Rw4vn4G0VVNNN7P4V Learn Moodle beginner admin]

* You can watch a [https://youtu.be/iN1R6yKL6sg screencast on translating the videos here] -or read the instructions below:

2) Click the cogwheel/settings icon:
[[File:VideoTranslate01.png|thumb|500px|center]]
3) Click the subtitles/CC link:
[[File:VideoTranslate02.png|thumb|500px|center]]
4) If contributions have been enabled for this video you will see Subtitles/CC. Click there:
[[File:VideoTranslate03.png|thumb|500px|center]]
5) Select your language by typing in its first few letters:
[[File:VideoTranslate04.png|thumb|500px|center]]
6) Type the translations under the English (1) and then click (2) Submit for review:
[[File:VideoTranslate05.png|thumb|500px|center]]
7) If you want credit, tick the box:
[[File:VideoTranslate06.png|thumb|500px|center]]
8) Once you have clicked ‘submit,’ a notification will be sent to a Moodle HQ Communications staff for review

9) Once the video is reviewed and the translation published,(if desired) your name and a link to your YouTube channel will appear in the description of the video:
[[File:VideoTranslate07.png|thumb|500px|center]]
10) A Moodle Communications team member will also let you know when it is published before communicating the translated videos through social channels, news post and other tools (with a credit to you)
Questions / for further assistance, please contact mary@moodle.com

Translating Moodle video subtitles

2019-07-12T17:20:13Z

Marycooch: /* How to translate HQ videos */

{{Translation}}
For each major release, Moodle HQ creates a number of screencasts to showcase step-by-step new features and improvements. Certain screencasts, starting with Moodle '''3.2''' have translations enabled.
This means the subtitles may be translated online, on YouTube. ''(Note not all HQ screencasts have this feature enabled.)''

==How to translate HQ videos==

1) From the [https://www.youtube.com/user/moodlehq Moodle HQ YouTube channel,] find the video you wish to translate. (You need to be logged in with a Google account)

* You may want to translate the videos for the most recent Moodle branch (e.g, [https://www.youtube.com/playlist?list=PLxcO_MFWQBDcsZhjYKz9JIwRRFRaW8hyk Moodle 3.7 videos])
* You may want to translate the videos from the Learn Moodle Basics MOOC (eg, [https://www.youtube.com/playlist?list=PLxcO_MFWQBDdoXpGILaTAj8S6O8-I6nRR Learn Moodle 3.7 Basics])
* You may want to translate the 11 videos for [https://www.youtube.com/playlist?list=PLxcO_MFWQBDdF2i_Rw4vn4G0VVNNN7P4V Learn Moodle beginner admin]

* You can watch a [https://youtu.be/iN1R6yKL6sg screencast on translating the videos here] -or read the instructions below:

2) Click the cogwheel/settings icon:
[[File:VideoTranslate01.png|thumb|500px|center]]
3) Click the subtitles/CC link:
[[File:VideoTranslate02.png|thumb|500px|center]]
4) If contributions have been enabled for this video you will see Subtitles/CC. Click there:
[[File:VideoTranslate03.png|thumb|500px|center]]
5) Select your language by typing in its first few letters:
[[File:VideoTranslate04.png|thumb|500px|center]]
6) Type the translations under the English (1) and then click (2) Submit for review:
[[File:VideoTranslate05.png|thumb|500px|center]]
7) If you want credit, tick the box:
[[File:VideoTranslate06.png|thumb|500px|center]]
8) Once you have clicked ‘submit,’ a notification will be sent to a Moodle HQ Communications staff for review

9) Once the video is reviewed and the translation published,(if desired) your name and a link to your YouTube channel will appear in the description of the video:
[[File:VideoTranslate07.png|thumb|500px|center]]
10) A Moodle Communications team member will also let you know when it is published before communicating the translated videos through social channels, news post and other tools (with a credit to you)
Questions / for further assistance, please contact mary@moodle.com

Translating Moodle video subtitles

2019-07-12T17:19:33Z

Marycooch: /* How to translate HQ videos */

{{Translation}}
For each major release, Moodle HQ creates a number of screencasts to showcase step-by-step new features and improvements. Certain screencasts, starting with Moodle '''3.2''' have translations enabled.
This means the subtitles may be translated online, on YouTube. ''(Note not all HQ screencasts have this feature enabled.)''

==How to translate HQ videos==

1) From the [https://www.youtube.com/user/moodlehq Moodle HQ YouTube channel,] find the video you wish to translate. (You need to be logged in with a Google account)

* You may want to translate the videos for the most recent Moodle branch (e.g, [list=https://www.youtube.com/playlist?list=PLxcO_MFWQBDcsZhjYKz9JIwRRFRaW8hyk Moodle 3.7 videos])
* You may want to translate the videos from the Learn Moodle Basics MOOC (eg, [https://www.youtube.com/playlist?list=PLxcO_MFWQBDdoXpGILaTAj8S6O8-I6nRR Learn Moodle 3.7 Basics])
* You may want to translate the 11 videos for [https://www.youtube.com/playlist?list=PLxcO_MFWQBDdF2i_Rw4vn4G0VVNNN7P4V Learn Moodle beginner admin]

* You can watch a [https://youtu.be/iN1R6yKL6sg screencast on translating the videos here] -or read the instructions below:

2) Click the cogwheel/settings icon:
[[File:VideoTranslate01.png|thumb|500px|center]]
3) Click the subtitles/CC link:
[[File:VideoTranslate02.png|thumb|500px|center]]
4) If contributions have been enabled for this video you will see Subtitles/CC. Click there:
[[File:VideoTranslate03.png|thumb|500px|center]]
5) Select your language by typing in its first few letters:
[[File:VideoTranslate04.png|thumb|500px|center]]
6) Type the translations under the English (1) and then click (2) Submit for review:
[[File:VideoTranslate05.png|thumb|500px|center]]
7) If you want credit, tick the box:
[[File:VideoTranslate06.png|thumb|500px|center]]
8) Once you have clicked ‘submit,’ a notification will be sent to a Moodle HQ Communications staff for review

9) Once the video is reviewed and the translation published,(if desired) your name and a link to your YouTube channel will appear in the description of the video:
[[File:VideoTranslate07.png|thumb|500px|center]]
10) A Moodle Communications team member will also let you know when it is published before communicating the translated videos through social channels, news post and other tools (with a credit to you)
Questions / for further assistance, please contact mary@moodle.com

Translating Moodle video subtitles

2019-07-12T10:01:38Z

Marycooch: updating links

{{Translation}}
For each major release, Moodle HQ creates a number of screencasts to showcase step-by-step new features and improvements. Certain screencasts, starting with Moodle '''3.2''' have translations enabled.
This means the subtitles may be translated online, on YouTube. ''(Note not all HQ screencasts have this feature enabled.)''

==How to translate HQ videos==

1) From the [https://www.youtube.com/user/moodlehq Moodle HQ YouTube channel,] find the video you wish to translate. (You need to be logged in with a Google account)

* You may want to translate the videos for the most recent Moodle branch (e.g, [https://www.youtube.com/playlist?list=https://www.youtube.com/playlist?list=PLxcO_MFWQBDcsZhjYKz9JIwRRFRaW8hyk Moodle 3.7 videos])
* You may want to translate the videos from the Learn Moodle Basics MOOC (eg, [https://www.youtube.com/playlist?list=PLxcO_MFWQBDdoXpGILaTAj8S6O8-I6nRR Learn Moodle 3.7 Basics])
* You may want to translate the 11 videos for [https://www.youtube.com/playlist?list=PLxcO_MFWQBDdF2i_Rw4vn4G0VVNNN7P4V Learn Moodle beginner admin]

* You can watch a [https://youtu.be/iN1R6yKL6sg screencast on translating the videos here] -or read the instructions below:

2) Click the cogwheel/settings icon:
[[File:VideoTranslate01.png|thumb|500px|center]]
3) Click the subtitles/CC link:
[[File:VideoTranslate02.png|thumb|500px|center]]
4) If contributions have been enabled for this video you will see Subtitles/CC. Click there:
[[File:VideoTranslate03.png|thumb|500px|center]]
5) Select your language by typing in its first few letters:
[[File:VideoTranslate04.png|thumb|500px|center]]
6) Type the translations under the English (1) and then click (2) Submit for review:
[[File:VideoTranslate05.png|thumb|500px|center]]
7) If you want credit, tick the box:
[[File:VideoTranslate06.png|thumb|500px|center]]
8) Once you have clicked ‘submit,’ a notification will be sent to a Moodle HQ Communications staff for review

9) Once the video is reviewed and the translation published,(if desired) your name and a link to your YouTube channel will appear in the description of the video:
[[File:VideoTranslate07.png|thumb|500px|center]]
10) A Moodle Communications team member will also let you know when it is published before communicating the translated videos through social channels, news post and other tools (with a credit to you)
Questions / for further assistance, please contact mary@moodle.com

Translating plugins

2019-07-08T09:14:56Z

Marycooch: added video on translating plugin

{{Translation}}
==Looking for translated plugins in the Moodle plugins database==

* Almost all contributed plugins published in Moodle Plugins directory have been imported into [http://lang.moodle.org/ AMOS] and are ready to be translated.
*Watch this video tutorial on [https://www.youtube.com/watch?v=E_20uU1ibcA&feature=youtu.be Translating a Moodle plugin]
* When a user is looking at the [https://moodle.org/plugins/ Moodle plugins database], in ' Description tab > Useful links section' there is a link to 'Contribute translation for (your preferred language)' that points to [http://lang.moodle.org/ AMOS].
* Have a look at an example for the very popular [https://moodle.org/plugins/view.php?plugin=mod_hotpot HotPot] plugin:

[[File:Link to Plugin translations in Moodle plugins database.png|300px]]

* You can click on the 'Contribute translation for (your preferred language)' link.
* '''CURRENTLY:''' If you do not have an AMOS account, you would have to 'Create a new account' by using the appropriate link.
* If you have a translator account in AMOS, you can use AMOS to contribute the translation.
* If you select all the language packs (except English fixes) and write 'pluginname' in the box for 'String identifier', AMOS will display the name of the plugin in all available translations.
* Make sure that you have selected the Moodle branch(es) that you are interested in (eg, 2.5 in the image below).

[[File:Plugins translations in AMOS.png|400px]]

* In the above example, there are a total of 123 different language packs registered in AMOS; 63 of these are missing a translation for HotPot, which means that there are 60 different language translations already available for the HotPot plugin, a fair number for this popular plugin :)
* When no translation is available for any/many language(s), the box named 'Translation' will be empty for those languages.
* If a plugin name has been translated, there is a fair chance (but no certainty) that this plugin has been (completely) translated into that language. You can change the settings in AMOS and check for yourself.

==Plugin translation priority==
* Please help Moodle users in other languages by translating your favourite plugins.
* Moodle has a continuously updated [https://moodle.org/plugins/report/index.php?report=favourites&p=0&l=50&s=favourited&d=DESC list of the most favourite plugins], which might be worth considering for translation :)
* You can find the plugins with the largest number of downloads in the last three months at [https://moodle.org/plugins/stats.php https://moodle.org/plugins/stats.php]. These are the plugins most likely to be most useful when translated to your language. It would probably be a good idea to translate them first.
* Moodle has a list of plugins that have received the [https://moodle.org/plugins/browse.php?list=award&id=1 Reviewers' choice award]. These are given by the plugins guardians and reviewers for particularly useful, well coded or otherwise interesting plugins. It would be very desirable/useful to have these translated.
* See the [https://moodle.org/mod/forum/discuss.php?d=325804 list of (year 2015) favorite plugins] by Gavin Henrick
* Special cases:
** All plugins with ''mobile'' in their name, and all [https://moodle.org/plugins/browse.php?list=set&id=62 server side plugins] to support the [https://docs.moodle.org/31/en/Moodle_Mobile Moodle mobile app]
** [https://moodle.org/plugins/local_moodlecloudsignup MoodleCloud strings] are used for accessing the [https://moodle.com/cloud/ MoodleCloud] free and paid hosting services.

===Elementary school teaching===
If your Moodle site will serve kids, consider [https://docs.moodle.org/31/en/Language_packs#Can_I_make_a_language_pack_for_kids.3F making a language pack for kids].

===Plugins for K-12 teaching===
For [https://en.wikipedia.org/wiki/K%E2%80%9312 K-12] teaching and learning environments, please consider translating the plugins that are included in the [https://moodle.com/cloud/school/?utm_source=Sendy&utm_medium=Email&utm_campaign=Newsletter_July2016 Moodle for School at MoodleCloud]:
* [https://moodle.org/plugins/mod_attendance Attendance]
* [http://bigbluebutton.org/ BigBlueButton]
* [https://moodle.org/plugins/mod_checklist Checklist]
* [https://moodle.org/plugins/atto_chemistry Chemistry editor]
* [https://moodle.org/plugins/mod_choicegroup Group choice]
* [https://moodle.org/plugins/block_xp Level up!]
* [https://moodle.org/plugins/mod_quizgame Quizventure]
* [https://moodle.org/plugins/tinymce_wordcount Word count]

===Plugins for University teaching===
For universities, there is a [https://docs.moodle.org/31/en/Tertiary_education#Moodle_plugins_by.2Ffor_Universities list of plugins by/for Universities], and a [https://docs.moodle.org/31/en/Tertiary_education#Discipline-specific_plugins link to discipline-specific plugins], which might be worth translating.

==Non-translatable strings==
While AMOS does a great job for translating the Moodle core and most Moodle plugin language strings, some English language strings are not available for translation with AMOS.

===Plugins in the [https://moodle.org/plugins/browse.php?list=category&id=38 Other] category===
The plugins classified as '[https://moodle.org/plugins/browse.php?list=category&id=38 Other] ' (Utilities, Experimental or Incubating) are not translatable by AMOS (see [http://lang.moodle.org/mod/forum/discuss.php?d=3113 this forum thread]). You can use the [[:en:Language customization|language customization]] tool within your Moodle (production or local) server to produce the .php file containing the translated language strings for your language and email this file to the particular 'other' plugin maintainer, so that it can be included in the lang folder within the downloadable Zip file for the plugin.

===Plugins with coding errors===
Some plugins (of types different from 'Other') available for download in the [https://moodle.org/plugins/ Moodle plugins directory] may not have English language strings available for translation in [https://lang.moodle.org/ AMOS] because of [https://docs.moodle.org/dev/index.php?title=Plugin_contribution_checklist&redirect=no coding errors], that must be identified and fixed by the plugin maintainer, See [https://docs.moodle.org/dev/Plugin_contribution_checklist#Strings Plugin contribution checklist:Strings]:
* The plugin code must not rely on trailing and leading whitespace in strings.
* The string file must be considered as pure data file with the syntax $string['id'] = 'value';
* No other PHP syntax such as [http://php.net/manual/en/language.operators.string.php concatenation], [http://php.net/manual/en/language.types.string.php heredoc and nowdoc] is supported by the tools that AMOS use when processing the strings (even if it may work in Moodle itself).
* Use neither string concatenation operators nor other PHP logic inside string files. Those should really be considered as plain data files with simple $string['key'] = 'value'; syntax, nothing more.

===Plugins with hard-wired English language strings===
Sometimes you might have translated 100% of the strings available in AMOS for a given plugin, and you can still view the original English (non-translated) strings.
* Please check that you have purged your browser cache and the server cache, waited for one hour (for AMOS to update the language packs), and updated your language packs.
* If the problem persists, please write the plugin maintainer by clicking at the 'Bug tracker' link shown in the given plugin's page in the [https://moodle.org/plugins/index.php Moodle plugins database].
* If the plugin author has nested additional 'Lang' folders inside any subdirectories within the plugin folder structure, the English language strings in these nested Lang folder will not be available for AMOS, and they would seem to be hard-wired. Please contact the plugin author.
* Most Moodle plugin authors have been very fast at replacing the English hard-coded strings with strings variables that can now be translated in AMOS.
* If you suspect the problem is in a core plugin, you can post an issue in the [https://lang.moodle.org/mod/forum/view.php?id=5 AMOS translation forum].

===Log descriptions can not be translated===
* See [https://docs.moodle.org/dev/Translation_FAQ#Why_are_log_descriptions_displayed_in_English.3F why log descriptions are not translated].

===Items that must NOT be translated===
* See the [https://docs.moodle.org/dev/Translation_FAQ#Are_there_items_which_are_not_to_be_translated.3F Items that are not to be translated] in the [https://docs.moodle.org/dev/Translation_FAQ Translation FAQ]

==If translations are available in AMOS for some Moodle branches but not available for other branches==
Sometimes a plugin may have its English language strings available for translations for some Moodle branches (e.g. 2.0 to 2.4), but not for other branches (e.g. 2.5 to 2.7), even though the plugin itself is indeed available for download for all branches (2.0 to 2.7) in the Moodle plugins database.

Please see an example in [http://lang.moodle.org/mod/forum/discuss.php?d=3939 this post]. The cause is very likely a programming error (see 'Plugins with coding errors' above), that must be fixed by the plugin maintainer.

==What happens if a plugin ZIP file includes translation(s) inside the lang folder==
If a site has debugging on, there will be a warning message about 'Found language file' when the user installs the plugin, but the installation may proceed.

[[File:Found language file debugging message.jpg|400px]]

The Language strings inside a properly installed downloaded plugin will overwrite the strings translations of the language pack, but they can be overwritten by the strings defined with the Language customization.

===Strings priority===
When displaying text language strings, Moodle 2.x and 3.x will have the following priority:
# Strings defined by the [[:en:Language customization|language customization]] tool
# Strings defined in an installed child language pack (eg, the es_ve language pack)
# Strings defined in an installed parent language pack (eg, the es language pack)
# Strings enclosed inside the plugin_name/lang/xx/yy.php folder (where xx is a language code other than the en folder) from a downloaded and installed plugin ZIP file (eg, inside the /server/moodle/theme/adaptable/lang/es/theme_adaptable.php file)
# Original Australian English language strings shipped with the downloaded Moodle branch.
# Original Australian English language strings inside the /lang/en folder in the downloaded/updated plugin ZIP file

Note: See the [https://moodle.org/plugins/local_string_override local String override plugin] that makes it possible for plugins to override existing translations regardless if they're bundled with Moodle or they're originated from a community plugin.

==See also==

* [http://lang.moodle.org/mod/forum/discuss.php?d=2485 Contributed plugins are now automatically imported into AMOS] announcement explaining the mechanism
* [https://docs.moodle.org/dev/Translation_FAQ#Are_there_items_which_are_not_to_be_translated.3F Items that are not to be translated] in the [https://docs.moodle.org/dev/Translation_FAQ Translation FAQ]

[[Category:Plugins]]

LearnMoodle

2019-06-08T11:22:20Z

Marycooch: /* What is LearnMoodle? */

LearnMoodle

2019-02-06T11:39:28Z

Marycooch: updated MOOC

Moodle 3.6 release notes

2018-12-13T11:29:16Z

Marycooch: MDL - 61041

[[Releases]] > {{FULLPAGENAME}}

Release date: 3 December 2018

Here is [https://tracker.moodle.org/secure/IssueNavigator!executeAdvanced.jspa?jqlQuery=project+%3D+mdl+AND+resolution+%3D+fixed+AND+fixVersion+in+%28%223.6%22%29+ORDER+BY+priority+DESC&runQuery=true&clear=true the full list of fixed issues in 3.6].

See our [https://docs.moodle.org/36/en/New_features New features page] in the user documentation for an introduction to Moodle 3.6 with screenshots.

If you are upgrading from a previous version, please see [[:en:Upgrading|Upgrading]] in the user docs. ''In particular, for sites using a custom theme or login form, from 3.6 onwards, the login form must include a new login token field. See [[Login token]] for details.''

{{Note|You are recommended to use [[Moodle 3.6.1 release notes|Moodle 3.6.1]], as it includes a messaging regression fix.}}

==Server requirements==

These are just the minimum supported versions. We recommend keeping all of your software and operating systems up-to-date.

* Moodle upgrade: Moodle 3.1 or later
* PHP version: minimum PHP 7.0.0 ''Note: minimum PHP version has increased since Moodle 3.3''. PHP 7.1.x and 7.2.x are supported too. [[Moodle and PHP7|PHP 7.3.x support]] is being implemented (@ MDL-63420) and '''not ready for production''' with this release.
* PHP extension '''intl''' is required since Moodle 3.4 (it was recommended in 2.0 onwards)

=== Database requirements ===

Moodle supports the following database servers. Again, version numbers are just the minimum supported version. We recommend running the latest stable version of any software.

{| class="nicetable"
|-
! Database
! Minimum version
! Recommended
|-
| [http://www.postgresql.org/ PostgreSQL]
| 9.4
| Latest
|-
| [http://www.mysql.com/ MySQL]
| 5.6
| Latest
|-
| [https://mariadb.org/ MariaDB]
| 5.5.31
| Latest
|-
| [http://www.microsoft.com/en-us/server-cloud/products/sql-server/ Microsoft SQL Server]
| 2008
| Latest
|-
| [http://www.oracle.com/us/products/database/overview/index.html Oracle Database]
| 11.2
| Latest
|}

==Client requirements==

=== Browser support ===
Moodle is compatible with any standards compliant web browser. We regularly test Moodle with the following browsers:

Desktop:
* Chrome
* Firefox
* Safari
* Edge
* Internet Explorer

Mobile:
* MobileSafari
* Google Chrome

For the best experience and optimum security, we recommend that you keep your browser up to date. https://whatbrowser.org

Note: Legacy browsers with known compatibility issues with Moodle 3.6:
* Internet Explorer 10 and below
* Safari 7 and below

==Major features==

===Dashboard and Course overview===
* MDL-63044 and MDL-63337 - New [https://docs.moodle.org/36/en/Course_overview Course overview] and [https://docs.moodle.org/36/en/Timeline_block Timeline block]
* MDL-63062 - New [https://docs.moodle.org/36/en/Recently_accessed_courses_block Recently accessed courses block]
* MDL-63063 - New [https://docs.moodle.org/36/en/Recently_accessed_items_block Recently accessed items block]
* MDL-63457 - Option to hide courses in the course overview block
* MDL-63058 - Option to star/unstar courses in the course overview block
* MDL-63064 - New [https://docs.moodle.org/36/en/Starred_courses_block Starred courses block]
* MDL-63352 - Dashboard retains user preferences for view options
* MDL-63793 - Course overview block retains user preferences for the number of courses to show
* MDL-61161 - Grace period when displaying "In progress" courses in course overview block
* MDL-63040 - Removal of Dashboard page header

===GDPR and Privacy===
Note that some of these GDPR improvements have also been backported to Moodle 3.5.3, 3.4.6 and 3.3.9.

* MDL-63116 - Data requests bulk actions
* MDL-62309 - Option to make site policies required or optional
* MDL-61652 - Capabilities for controlling who can download SAR data
* MDL-62563 - Data deletion of existing deleted users
* MDL-63897 - Pre-processing stage removed from data requests process
* MDL-62558 - Data retention summary (read-only)
* MDL-63726 - Option to remove the "Data retention summary" link in the footer
* MDL-62491 - HTML data request export format
* MDL-63401 - User expiry improvements
* MDL-63619 - Data purpose and category inheritance improvements
* MDL-62560 - Different data retention strategies for different roles in a purpose
* MDL-62554 - Ability to configure data registry to use module type defaults
* MDL-63009 - Site mentioned in email notifications of data requests
* MDL-6074 - Option to hide your name in the [https://docs.moodle.org/36/en/Online_users_block online users block]

===Messaging===
* '''MDL-57272 and MDL-63280 - Group messaging'''
* MDL-63303 - New messaging UI with [https://docs.moodle.org/36/en/Messaging messaging drawer]
* MDL-63279 - Option to [https://docs.moodle.org/36/en/Messaging_settings disable site-wide messaging]
* MDL-63214 - Privacy setting for restricting who can message you
* MDL-63213 - Option to star messaging conversations
* MDL-63283 - Notifications not sent for group conversations
* MDL-63281 - Group members synchronised with messaging conversations members

===Assignment===
* MDL-27520 - Assignment feedback can include media or other files

===Quiz===
* MDL-62610 - Improved quiz statistics report usability for randomized questions
* MDL-62708 - Option to add ID numbers to questions and question categories
* MDL-63738 - Single questions can be exported from the question bank

===Workshop===
* MDL-60820 - Teachers can specify workshop submission types

===Repositories===
* MDL-58943 - Nextcloud integration, with a [https://docs.moodle.org/36/en/Nextcloud_repository Nextcloud repository] and [https://docs.moodle.org/36/en/OAuth_2_Nextcloud_service OAuth 2 Nextcloud service]

===Open Badges===
* MDL-58454 - Support for Open Badges v2.0

===Performance===
* MDL-54035 - Performance improvements to cache flags
* MDL-47962 - Glossary auto-linking filter performance improvements

===Usability improvements===
* MDL-51177 - atto_htmlplus implemented to improve Atto editor HTML indenting
* MDL-45170 - Copy and paste of images from one WYSIWYG window to another
* MDL-61388 - Forum actions announced by screen reader when completed
* MDL-62899 - Global search displays a relevant icon next to link in results
* MDL-46415 - SVG/high resolution emoticons
* MDL-58000 - Larger badge images are used

===Experimental===
* MDL-53566 - [https://docs.moodle.org/36/en/Context_freezing Context freezing] - setting read-only access for categories, courses, activities and their content

==Other highlights==

===Functional changes===
* MDL-17943 - 'Resend confirmation email' button on login page
* MDL-14274 - IF conditions in grade calculations
* MDL-37624 - Calendar entries location support
* MDL-36754 - Images are displayed in forum notification emails
* MDL-59259 - Course format options may be specified in upload courses CSV file
* MDL-41265 - Page resource option to show/hide "Last modified"
* MDL-61378 - Forum post HTML structure improvements
* MDL-59454 - Option to download the list of course participants
* MDL-60520 - Analytics models can use different machine learning backends
* MDL-61573 - User menu: customusermenuitems map Font Awesome icons for non pix/t folders
* MDL-62320 - JSON added to the default MIME types list
* MDL-63431 - Atto media plugin title global attribute support
* MDL-60435 - Shibboleth authentication identity providers
* MDL-59169 - Grader report saves after edit with multiple tabs
* MDL-62960 - Drag and drop of course events respects the course start date

===Security issues===
* [https://moodle.org/mod/forum/discuss.php?d=378731 MSA-18-0020] Login CSRF vulnerability in login form. Note that this fix has previously been disclosed following the release of Moodle 3.5.3, 3.4.6, 3.3.9 and 3.1.15.

===For administrators===
* MDL-62334 - 'Add a new course' link in Site administration
* MDL-63253 - Admin search results provide location of the found matching page
* MDL-63772 - Capability to control use of Atto Record RTC
* MDL-63708 - New blocks supported by the mobile app can be disabled
* MDL-52953 - Legacy log store deprecation
* MDL-59429 - Log changes to site administrators
* MDL-62651 - adhoc task runner
* MDL-62777 - Site upgrades via CLI display new default settings
* MDL-63603 - Indian Rupee added to [https://docs.moodle.org/36/en/PayPal_enrolment PayPal enrolment] currencies
* MDL-60514 - Set Path to PHP CLI in order to display 'Run now' for [https://docs.moodle.org/36/en/Scheduled_tasks Scheduled tasks]
* MDL-61041 - Assignment upgrade helper tool removed from core.

==For developers==
* MDL-55188 - Old Events API final deprecation
* MDL-54741 - Phase 2 of deprecation of functions in lib/deprecatedlib.php
* MDL-51803 - Reusable element for drag and drop sortable table or list
* MDL-63329 - memcache session handler removal
* MDL-63658 - New Favourites subsystem
* MDL-63729 - Badges web services return new fields and data added by the Open Badges v2.0 specification
* MDL-50812 - core_useragent::get_browser_version_classes distinguishes between different browsers

===Privacy API update===

In addition to existing requirements, any plugin which implements the plugin provider interface must also implement the <tt>\core_privacy\local\request\core_userlist_provider</tt> interface. Two new methods need to be implemented:

* [[Privacy API#Retrieving_the_users_in_a_context|get_users_in_context()]]
* [[Privacy API#Delete_personal_information_for_several_users_in_a_specific_context|delete_data_for_users()]]

However, the two above methods are not required for plugins that [[Privacy_API#Plugins_which_do_not_store_personal_data|implement the <tt>null_provider</tt>]] only (i.e. which do not store personal data).

Note that these changes are also required for latest Moodle 3.4.6 and 3.5.3 versions.

===Behat scenario files===

* MDL-57281 - The behat step <code>I navigate to "ITEM" node in "MAINNODE > PATH"</code> has been deprecated and throws an exception with details on how to replace it. The recommended replacement steps work in all recent Moodle versions. The updated Behat will pass with Moodle 3.4 too.

===Login token===

If your plugin provides an alternative login form (e.g. it is a theme replacing the default login form template / renderer), the login form must include a new login token field. For details of required changes, see [[Login token]]. Note that this also affects latest stable branches too.

===New core functions===

* <tt>userdate_htmltime()</tt>

===Component APIs upgrades===

Please refer to the upgrade.txt files in the relevant component directory for changes in this particular Moodle release.

* [https://git.in.moodle.com/moodle/moodle/blob/master/admin/tool/log/upgrade.txt admin/tool/log/upgrade.txt]
* [https://git.in.moodle.com/moodle/moodle/blob/master/admin/tool/upgrade.txt admin/tool/upgrade.txt]
* [https://git.in.moodle.com/moodle/moodle/blob/master/auth/shibboleth/upgrade.txt auth/shibboleth/upgrade.txt]
* [https://git.in.moodle.com/moodle/moodle/blob/master/auth/upgrade.txt auth/upgrade.txt]
* [https://git.in.moodle.com/moodle/moodle/blob/master/badges/upgrade.txt badges/upgrade.txt]
* [https://git.in.moodle.com/moodle/moodle/blob/master/blocks/upgrade.txt blocks/upgrade.txt]
* [https://git.in.moodle.com/moodle/moodle/blob/master/cache/upgrade.txt cache/upgrade.txt]
* [https://git.in.moodle.com/moodle/moodle/blob/master/calendar/upgrade.txt calendar/upgrade.txt]
* [https://git.in.moodle.com/moodle/moodle/blob/master/course/format/upgrade.txt course/format/upgrade.txt]
* [https://git.in.moodle.com/moodle/moodle/blob/master/course/upgrade.txt course/upgrade.txt]
* [https://git.in.moodle.com/moodle/moodle/blob/master/enrol/upgrade.txt enrol/upgrade.txt]
* [https://git.in.moodle.com/moodle/moodle/blob/master/filter/upgrade.txt filter/upgrade.txt]
* [https://git.in.moodle.com/moodle/moodle/blob/master/grade/grading/form/upgrade.txt grade/grading/form/upgrade.txt]
* [https://git.in.moodle.com/moodle/moodle/blob/master/grade/report/upgrade.txt grade/report/upgrade.txt]
* [https://git.in.moodle.com/moodle/moodle/blob/master/grade/upgrade.txt grade/upgrade.txt]
* [https://git.in.moodle.com/moodle/moodle/blob/master/lib/upgrade.txt lib/upgrade.txt]
* [https://git.in.moodle.com/moodle/moodle/blob/master/media/upgrade.txt media/upgrade.txt]
* [https://git.in.moodle.com/moodle/moodle/blob/master/message/upgrade.txt message/upgrade.txt]
* [https://git.in.moodle.com/moodle/moodle/blob/master/mod/assign/upgrade.txt mod/assign/upgrade.txt]
* [https://git.in.moodle.com/moodle/moodle/blob/master/mod/feedback/upgrade.txt mod/feedback/upgrade.txt]
* [https://git.in.moodle.com/moodle/moodle/blob/master/mod/forum/upgrade.txt mod/forum/upgrade.txt]
* [https://git.in.moodle.com/moodle/moodle/blob/master/mod/quiz/upgrade.txt mod/quiz/upgrade.txt]
* [https://git.in.moodle.com/moodle/moodle/blob/master/mod/scorm/report/basic/upgrade.txt mod/scorm/report/basic/upgrade.txt]
* [https://git.in.moodle.com/moodle/moodle/blob/master/mod/scorm/upgrade.txt mod/scorm/upgrade.txt]
* [https://git.in.moodle.com/moodle/moodle/blob/master/mod/upgrade.txt mod/upgrade.txt]
* [https://git.in.moodle.com/moodle/moodle/blob/master/mod/workshop/upgrade.txt mod/workshop/upgrade.txt]
* [https://git.in.moodle.com/moodle/moodle/blob/master/question/format/upgrade.txt question/format/upgrade.txt]
* [https://git.in.moodle.com/moodle/moodle/blob/master/report/upgrade.txt report/upgrade.txt]
* [https://git.in.moodle.com/moodle/moodle/blob/master/tag/upgrade.txt tag/upgrade.txt]
* [https://git.in.moodle.com/moodle/moodle/blob/master/theme/upgrade.txt theme/upgrade.txt]
* [https://git.in.moodle.com/moodle/moodle/blob/master/user/upgrade.txt user/upgrade.txt]

==See also==
*[[Moodle 3.5 release notes]]

[[Category:Release notes]]
[[Category:Moodle 3.6]]

[[fr:Notes de mise à jour de Moodle 3.6]]
[[es:Notas de Moodle 3.6]]

Moodle 3.6 release notes

2018-12-04T14:20:12Z

Marycooch: ref to MDL-60514

[[Releases]] > {{FULLPAGENAME}}

Release date: 3 December 2018

Here is [https://tracker.moodle.org/secure/IssueNavigator!executeAdvanced.jspa?jqlQuery=project+%3D+mdl+AND+resolution+%3D+fixed+AND+fixVersion+in+%28%223.6%22%29+ORDER+BY+priority+DESC&runQuery=true&clear=true the full list of fixed issues in 3.6].

See our [https://docs.moodle.org/36/en/New_features New Features page] for a more user-friendly introduction to Moodle 3.6 with screenshots.

{{Note|If you are upgrading from a previous version, please see [[:en:Upgrading|Upgrading]] in the user docs. ''In particular, for sites using a custom theme or login form, from 3.6 onwards, the login form must include a new login token field. See [[Login token]] for details.}}

==Server requirements==

These are just the minimum supported versions. We recommend keeping all of your software and operating systems up-to-date.

* Moodle upgrade: Moodle 3.1 or later
* PHP version: minimum PHP 7.0.0 ''Note: minimum PHP version has increased since Moodle 3.3''. PHP 7.1.x and 7.2.x are supported too. [[Moodle and PHP7|PHP 7.3.x support]] is being implemented (@ MDL-63420) and '''not ready for production''' with this release.
* PHP extension '''intl''' is required since Moodle 3.4 (it was recommended in 2.0 onwards)

=== Database requirements ===

Moodle supports the following database servers. Again, version numbers are just the minimum supported version. We recommend running the latest stable version of any software.

{| class="nicetable"
|-
! Database
! Minimum version
! Recommended
|-
| [http://www.postgresql.org/ PostgreSQL]
| 9.4
| Latest
|-
| [http://www.mysql.com/ MySQL]
| 5.6
| Latest
|-
| [https://mariadb.org/ MariaDB]
| 5.5.31
| Latest
|-
| [http://www.microsoft.com/en-us/server-cloud/products/sql-server/ Microsoft SQL Server]
| 2008
| Latest
|-
| [http://www.oracle.com/us/products/database/overview/index.html Oracle Database]
| 11.2
| Latest
|}

==Client requirements==

=== Browser support ===
Moodle is compatible with any standards compliant web browser. We regularly test Moodle with the following browsers:

Desktop:
* Chrome
* Firefox
* Safari
* Edge
* Internet Explorer

Mobile:
* MobileSafari
* Google Chrome

For the best experience and optimum security, we recommend that you keep your browser up to date. https://whatbrowser.org

Note: Legacy browsers with known compatibility issues with Moodle 3.6:
* Internet Explorer 10 and below
* Safari 7 and below

==Major features==

===Dashboard and Course overview===
* MDL-63044 and MDL-63337 - New [https://docs.moodle.org/36/en/Course_overview Course overview] and [https://docs.moodle.org/36/en/Timeline_block Timeline block]
* MDL-63062 - New [https://docs.moodle.org/36/en/Recently_accessed_courses_block Recently accessed courses block]
* MDL-63063 - New [https://docs.moodle.org/36/en/Recently_accessed_items_block Recently accessed items block]
* MDL-63457 - Option to hide courses in the course overview block
* MDL-63058 - Option to star/unstar courses in the course overview block
* MDL-63064 - New [https://docs.moodle.org/36/en/Starred_courses_block Starred courses block]
* MDL-63352 - Dashboard retains user preferences for view options
* MDL-63793 - Course overview block retains user preferences for the number of courses to show
* MDL-61161 - Grace period when displaying "In progress" courses in course overview block
* MDL-63040 - Removal of Dashboard page header

===GDPR and Privacy===
Note that some of these GDPR improvements have also been backported to Moodle 3.5.3, 3.4.6 and 3.3.9.

* MDL-63116 - Data requests bulk actions
* MDL-62309 - Option to make site policies required or optional
* MDL-61652 - Capabilities for controlling who can download SAR data
* MDL-62563 - Data deletion of existing deleted users
* MDL-63897 - Pre-processing stage removed from data requests process
* MDL-62558 - Data retention summary (read-only)
* MDL-63726 - Option to remove the "Data retention summary" link in the footer
* MDL-62491 - HTML data request export format
* MDL-63401 - User expiry improvements
* MDL-63619 - Data purpose and category inheritance improvements
* MDL-62560 - Different data retention strategies for different roles in a purpose
* MDL-62554 - Ability to configure data registry to use module type defaults
* MDL-63009 - Site mentioned in email notifications of data requests
* MDL-6074 - Option to hide your name in the [https://docs.moodle.org/36/en/Online_users_block online users block]

===Messaging===
* '''MDL-57272 and MDL-63280 - Group messaging'''
* MDL-63303 - New messaging UI with [https://docs.moodle.org/36/en/Messaging messaging drawer]
* MDL-63279 - Option to [https://docs.moodle.org/36/en/Messaging_settings disable site-wide messaging]
* MDL-63214 - Privacy setting for restricting who can message you
* MDL-63213 - Option to star messaging conversations
* MDL-63283 - Notifications not sent for group conversations
* MDL-63281 - Group members synchronised with messaging conversations members

===Assignment===
* MDL-27520 - Assignment feedback can include media or other files

===Quiz===
* MDL-62610 - Improved quiz statistics report usability for randomized questions
* MDL-62708 - Option to add ID numbers to questions and question categories
* MDL-63738 - Single questions can be exported from the question bank

===Workshop===
* MDL-60820 - Teachers can specify workshop submission types

===Repositories===
* MDL-58943 - Nextcloud integration, with a [https://docs.moodle.org/36/en/Nextcloud_repository Nextcloud repository] and [https://docs.moodle.org/36/en/OAuth_2_Nextcloud_service OAuth 2 Nextcloud service]

===Open Badges===
* MDL-58454 - Support for Open Badges v2.0

===Performance===
* MDL-54035 - Performance improvements to cache flags
* MDL-47962 - Glossary auto-linking filter performance improvements

===Usability improvements===
* MDL-51177 - atto_htmlplus implemented to improve Atto editor HTML indenting
* MDL-45170 - Copy and paste of images from one WYSIWYG window to another
* MDL-61388 - Forum actions announced by screen reader when completed
* MDL-62899 - Global search displays a relevant icon next to link in results
* MDL-46415 - SVG/high resolution emoticons
* MDL-58000 - Larger badge images are used

===Experimental===
* MDL-53566 - [https://docs.moodle.org/36/en/Context_freezing Context freezing] - setting read-only access for categories, courses, activities and their content

==Other highlights==

===Functional changes===
* MDL-17943 - 'Resend confirmation email' button on login page
* MDL-14274 - IF conditions in grade calculations
* MDL-37624 - Calendar entries location support
* MDL-36754 - Images are displayed in forum notification emails
* MDL-59259 - Course format options may be specified in upload courses CSV file
* MDL-41265 - Page resource option to show/hide "Last modified"
* MDL-61378 - Forum post HTML structure improvements
* MDL-59454 - Option to download the list of course participants
* MDL-60520 - Analytics models can use different machine learning backends
* MDL-61573 - User menu: customusermenuitems map Font Awesome icons for non pix/t folders
* MDL-62320 - JSON added to the default MIME types list
* MDL-63431 - Atto media plugin title global attribute support
* MDL-60435 - Shibboleth authentication identity providers
* MDL-59169 - Grader report saves after edit with multiple tabs
* MDL-62960 - Drag and drop of course events respects the course start date

===Security issues===
* [https://moodle.org/mod/forum/discuss.php?d=378731 MSA-18-0020] Login CSRF vulnerability in login form. Note that this fix has previously been disclosed following the release of Moodle 3.5.3, 3.4.6, 3.3.9 and 3.1.15.

===For administrators===
* MDL-62334 - 'Add a new course' link in Site administration
* MDL-63253 - Admin search results provide location of the found matching page
* MDL-63772 - Capability to control use of Atto Record RTC
* MDL-63708 - New blocks supported by the mobile app can be disabled
* MDL-52953 - Legacy log store deprecation
* MDL-59429 - Log changes to site administrators
* MDL-62651 - adhoc task runner
* MDL-62777 - Site upgrades via CLI display new default settings
* MDL-63603 - Indian Rupee added to [https://docs.moodle.org/36/en/PayPal_enrolment PayPal enrolment] currencies
* MDL-60514 - Set Path to PHP CLI in order to display 'Run now' for [[Scheduled tasks]]

==For developers==
* MDL-55188 - Old Events API final deprecation
* MDL-54741 - Phase 2 of deprecation of functions in lib/deprecatedlib.php
* MDL-51803 - Reusable element for drag and drop sortable table or list
* MDL-63329 - memcache session handler removal
* MDL-63658 - New Favourites subsystem
* MDL-63729 - Badges web services return new fields and data added by the Open Badges v2.0 specification
* MDL-50812 - core_useragent::get_browser_version_classes distinguishes between different browsers

===Privacy API update===

In addition to existing requirements, any plugin which implements the plugin provider interface must also implement the <tt>\core_privacy\local\request\core_userlist_provider</tt> interface. Two new methods need to be implemented:

* [[Privacy API#Retrieving_the_users_in_a_context|get_users_in_context()]]
* [[Privacy API#Delete_personal_information_for_several_users_in_a_specific_context|delete_data_for_users()]]

However, the two above methods are not required for plugins that [[Privacy_API#Plugins_which_do_not_store_personal_data|implement the <tt>null_provider</tt>]] only (i.e. which do not store personal data).

Note that these changes are also required for latest Moodle 3.4.6 and 3.5.3 versions.

===Behat scenario files===

* MDL-57281 - The behat step <code>I navigate to "ITEM" node in "MAINNODE > PATH"</code> has been deprecated and throws an exception with details on how to replace it. The recommended replacement steps work in all recent Moodle versions. The updated Behat will pass with Moodle 3.4 too.

===Login token===

If your plugin provides an alternative login form (e.g. it is a theme replacing the default login form template / renderer), the login form must include a new login token field. For details of required changes, see [[Login token]]. Note that this also affects latest stable branches too.

===New core functions===

* <tt>userdate_htmltime()</tt>

===Component APIs upgrades===

Please refer to the upgrade.txt files in the relevant component directory for changes in this particular Moodle release.

* [https://git.in.moodle.com/moodle/moodle/blob/master/admin/tool/log/upgrade.txt admin/tool/log/upgrade.txt]
* [https://git.in.moodle.com/moodle/moodle/blob/master/admin/tool/upgrade.txt admin/tool/upgrade.txt]
* [https://git.in.moodle.com/moodle/moodle/blob/master/auth/shibboleth/upgrade.txt auth/shibboleth/upgrade.txt]
* [https://git.in.moodle.com/moodle/moodle/blob/master/auth/upgrade.txt auth/upgrade.txt]
* [https://git.in.moodle.com/moodle/moodle/blob/master/badges/upgrade.txt badges/upgrade.txt]
* [https://git.in.moodle.com/moodle/moodle/blob/master/blocks/upgrade.txt blocks/upgrade.txt]
* [https://git.in.moodle.com/moodle/moodle/blob/master/cache/upgrade.txt cache/upgrade.txt]
* [https://git.in.moodle.com/moodle/moodle/blob/master/calendar/upgrade.txt calendar/upgrade.txt]
* [https://git.in.moodle.com/moodle/moodle/blob/master/course/format/upgrade.txt course/format/upgrade.txt]
* [https://git.in.moodle.com/moodle/moodle/blob/master/course/upgrade.txt course/upgrade.txt]
* [https://git.in.moodle.com/moodle/moodle/blob/master/enrol/upgrade.txt enrol/upgrade.txt]
* [https://git.in.moodle.com/moodle/moodle/blob/master/filter/upgrade.txt filter/upgrade.txt]
* [https://git.in.moodle.com/moodle/moodle/blob/master/grade/grading/form/upgrade.txt grade/grading/form/upgrade.txt]
* [https://git.in.moodle.com/moodle/moodle/blob/master/grade/report/upgrade.txt grade/report/upgrade.txt]
* [https://git.in.moodle.com/moodle/moodle/blob/master/grade/upgrade.txt grade/upgrade.txt]
* [https://git.in.moodle.com/moodle/moodle/blob/master/lib/upgrade.txt lib/upgrade.txt]
* [https://git.in.moodle.com/moodle/moodle/blob/master/media/upgrade.txt media/upgrade.txt]
* [https://git.in.moodle.com/moodle/moodle/blob/master/message/upgrade.txt message/upgrade.txt]
* [https://git.in.moodle.com/moodle/moodle/blob/master/mod/assign/upgrade.txt mod/assign/upgrade.txt]
* [https://git.in.moodle.com/moodle/moodle/blob/master/mod/feedback/upgrade.txt mod/feedback/upgrade.txt]
* [https://git.in.moodle.com/moodle/moodle/blob/master/mod/forum/upgrade.txt mod/forum/upgrade.txt]
* [https://git.in.moodle.com/moodle/moodle/blob/master/mod/quiz/upgrade.txt mod/quiz/upgrade.txt]
* [https://git.in.moodle.com/moodle/moodle/blob/master/mod/scorm/report/basic/upgrade.txt mod/scorm/report/basic/upgrade.txt]
* [https://git.in.moodle.com/moodle/moodle/blob/master/mod/scorm/upgrade.txt mod/scorm/upgrade.txt]
* [https://git.in.moodle.com/moodle/moodle/blob/master/mod/upgrade.txt mod/upgrade.txt]
* [https://git.in.moodle.com/moodle/moodle/blob/master/mod/workshop/upgrade.txt mod/workshop/upgrade.txt]
* [https://git.in.moodle.com/moodle/moodle/blob/master/question/format/upgrade.txt question/format/upgrade.txt]
* [https://git.in.moodle.com/moodle/moodle/blob/master/report/upgrade.txt report/upgrade.txt]
* [https://git.in.moodle.com/moodle/moodle/blob/master/tag/upgrade.txt tag/upgrade.txt]
* [https://git.in.moodle.com/moodle/moodle/blob/master/theme/upgrade.txt theme/upgrade.txt]
* [https://git.in.moodle.com/moodle/moodle/blob/master/user/upgrade.txt user/upgrade.txt]

==See also==
*[[Moodle 3.5 release notes]]

[[Category:Release notes]]
[[Category:Moodle 3.6]]

[[fr:Notes de mise à jour de Moodle 3.6]]
[[es:Notas de Moodle 3.6]]

LearnMoodle

2018-07-17T17:38:22Z

Marycooch: removed May ref

LearnMoodle

2018-07-17T13:17:41Z

Marycooch: updated dates of MOOC

==What is LearnMoodle?==
Most people are familiar with our Learn Moodle MOOC, an activity-based learning course for teachers new to Moodle. Four weeks, 3 to 4 hours a week. No fees.
The next Learn Moodle Basics course, for Moodle 3.6, will start on Monday 7 January, 2019.

==The new Moodle Educator Certification program==
In 2017-18, the Moodle HQ Education Team began to develop the Moodle Educator Certification Program. In these new training modules, educators are asked to demonstrate effectiveness with 22 digital competencies using Moodle Tools. In addition to the 22 facilitated modules, the program offers 10 self-regulated modules focused on deeper skills with Moodle activities and features.

==Philosophy of the MEC program==
The design of the modules reflects the following beliefs:

1. Educators are the focus of our attention, not features.

We honour the expertise of educators engaged in our models. We show them some Moodle teaching approaches and build in facilitated and self-regulated learning experiences. Our educators are asked to consider their own best work in the modules, as well as ways they may apply the ideas in their own teaching and learning practice using Moodle.

2. Teaching practice is informed by qualitative feedback.

We try to model specific behaviors like providing exemplars in Moodle, making room for experimentation, encouraging reflection, and requesting feedback from our participants. The reflections we ask educators to make are in the service of “what just happened” and making future decisions based on that information.

==Badges and Certifications==
The MEC Program offers six levels of possible attainment. Modules and certificates are awarded by program facilitators (Moodle Partner trainers).

Six Learn Moodle Basics MOOC (certificate)
*MEC Self-Regulated Modules (specific badges for Moodle tools)
*MEC Self-Regulated Modules (certificate for all self-regulated modules)
*MEC Facilitated Modules (specific badges for content standards)
*MEC Facilitated Modules (certificate for all facilitated modules)
*MEC Facilitated Capstone (Moodle Certified Educator)

==Areas of Learning==
Although the modules provide a path for badges and certification, the curriculum also serves as an excellent overview of applying digital skills with Moodle:

'''Professional Engagement'''

Educators’ digital competence to use Moodle not only to enhance teaching, but also for their professional interactions with learners and other educators, for their individual professional development, and for the collective good and continuous innovation in teaching practice.

'''Digital Resources'''

Educators’ digital competence to effectively identify Moodle resources that best fit their learning objectives, learner group, and teaching style, to structure the wealth of materials, establish connections, and to modify, add on to, and develop resources to support teaching practice.

'''Teaching and Learning'''

Educators’ digital competence to effectively archestrate the use of Moodle in the different phases and settings of the learning process including the designing, planning, and implementation.

'''Assessment'''

Educators’ digital competence to use Moodle to gather, analyze, and interpret student data, to monitor learner progress, to facilitate feedback, and to assess and adapt teaching strategies.

'''Empowering Learners'''

Educators’ digital competence to use Moodle to support the active involvement of learners in the learning process, to contribute to classroom differentiation and personalization, and ensuring accessibility for all learners.

'''Facilitating Competence'''

Educators’ digital competence to use Moodle to facilitate learners’ digital competence including digital communication and collaboration, digital content creation, and digital problem-solving.

Note: these key learning areas align with the European Framework for the Digital Competence of Educators.

==Frequently Asked Questions==

===How is this different from previous MCCC training?===
The MEC Program addresses educators who want to apply Moodle to solve well-identified issues within their teaching and learning practice. We discuss the software in the context of their own courses. The MCCC requires more technical proficiency skills and likely fewer teaching and learning conversations than the MEC.

===Where can we go to find out more about MEC Program and the courses?===
Stay tuned for more launch information this May from https://moodle.com

===When will I be able to do one of these modules?===
In April we will be running another small cohort for friends who are willing to engage as participants, then provide suggestions at the end of the session. Tom Murdock, Education Team Lead, has more details and can be contacted on tom@moodle.com.

===How much will they cost/what is the pricing system?===
Costs will be set by partners who facilitate the courses

===How long will each module last? Hours? Days? Weeks?===
The length of the module depends on its delivery method. A face-to-face workshop can be completed in 4-6 hours (depending on the module). Online facilitation could stretch out from 1-2 weeks.

===Do you cover mobile learning/accessibility/gamification/something else?===
We cover mobile learning and accessibility. Stay tuned for full curriculum list.

===Are they all totally online? What about face to face (like at a moot?)===
The MEC modules are designed to be taught online or blended (face-to-face with an online component).

===You say we must go via a Moodle Partner? What if we don’t have a Moodle partner?===
We can help you find a great partner who can support your needs.

===What are the “five languages” they will be translated into and when will they be ready?===
These are dependent on needs of the partners participating in the MEC Program.

===How have you done quality control on these courses/which trials have you done?===
We are following the stages outlined in the UNESCO IBE Developing and Implementing Curriculum Frameworks.

===Are these modules just for academic institutions or would they work for workplace too?===
They are appropriate for diverse sectors including education, higher education, and workplace learning.

===Will any of the courses be offered as free tasters?===
We haven’t considered this option at this early stage.

===How do badges and certificates work with these modules? Will I get a badge per module? A certificate per module?===

Our 6 levels for skill development and quality education:

*Learn Moodle Basics MOOC (certificate and badge)
*MEC Self-Regulated Modules (specific badges for Moodle tools)
*MEC Self-Regulated Modules (certificate for all self-regulated modules)
*MEC Facilitated Modules (specific badges for content standards)
*MEC Facilitated Modules (certificate for all facilitated modules)
*MEC Facilitated Capstone (Moodle Certified Educator)

===If we do all the modules and become certified, will we be official Moodle trainers? What will my certification allow me to do?===
MEC is a designation of expertise, but only Moodle Partner Trainers are certified to facilitate the MEC Program.

===What’s going to happen to the current MCCC?===
Stay tuned. We value all of the time and work that has been put into this curriculum and hope to work with its community to continue its positive impact for Moodlers.

===I want to do admin training!===
Excellent! Look for our 2019 program initiatives!

Moodle 3.5 release notes

2018-05-16T21:14:07Z

Marycooch: user docs new features page

[[Releases]] > {{FULLPAGENAME}}

Release date: 17 May 2018

'''This page will continue to be updated until Moodle 3.5 is released.'''

Here is [https://tracker.moodle.org/secure/IssueNavigator!executeAdvanced.jspa?jqlQuery=project+%3D+mdl+AND+resolution+%3D+fixed+AND+fixVersion+in+%28%223.5%22%29+ORDER+BY+priority+DESC&runQuery=true&clear=true the full list of fixed issues in 3.5].

See our [https://docs.moodle.org/35/en/New_features New Features page] for a more user-friendly introduction to Moodle 3.5 with screenshots.

If you are upgrading from previous version, make sure you read the [https://docs.moodle.org/35/en/Upgrading Upgrading] documentation.

==Server requirements==

These are just the minimum supported versions. We recommend keeping all of your software and operating systems up-to-date.

* Moodle upgrade: Moodle 3.1 or later
* PHP version: minimum PHP 7.0.0 ''Note: minimum PHP version has increased since Moodle 3.3''. PHP 7.1.x and 7.2.x are supported too. PHP 7.x could have some [https://docs.moodle.org/dev/Moodle_and_PHP7#Can_I_use_PHP7_yet.3F engine limitations].
* PHP extension '''intl''' is required since Moodle 3.4 (it was recommended in 2.0 onwards)

=== Database requirements ===

Moodle supports the following database servers. Again, version numbers are just the minimum supported version. We recommend running the latest stable version of any software.

{| class="nicetable"
|-
! Database
! Minimum version
! Recommended
|-
| [http://www.postgresql.org/ PostgreSQL]
| 9.3
| Latest
|-
| [http://www.mysql.com/ MySQL]
| 5.5.31
| Latest
|-
| [https://mariadb.org/ MariaDB]
| 5.5.31
| Latest
|-
| [http://www.microsoft.com/en-us/server-cloud/products/sql-server/ Microsoft SQL Server]
| 2008
| Latest
|-
| [http://www.oracle.com/us/products/database/overview/index.html Oracle Database]
| 10.2
| Latest
|}

==Client requirements==

=== Browser support ===
Moodle is compatible with any standards compliant web browser. We regularly test Moodle with the following browsers:

Desktop:
* Chrome
* Firefox
* Safari
* Edge
* Internet Explorer

Mobile:
* MobileSafari
* Google Chrome

For the best experience and optimum security, we recommend that you keep your browser up to date. https://whatbrowser.org

Note: Legacy browsers with known compatibility issues with Moodle 3.5:
* Internet Explorer 10 and below
* Safari 7 and below

==Major features==

===GDPR===
* '''MDL-61275 - GDPR Consenting of Minors and Managing, Versioning and Tracking Privacy Policies and User Consents'''
* MDL-61292 - A new admin tool to manage policy documents
* MDL-61423 - Add age and location verification to identify minors
* MDL-61302 - Workflow to allow users to agree to all policies
* MDL-61301 - Report of user agreed policies and their versions
* MDL-61705 - Bulk accept of policies on behalf of users
* MDL-61864 - Include policy tool in core
* MDL-62286 - Add policy link to the site footer

* '''MDL-61306 - GDPR Data Requests and Data Registry'''
* MDL-59718 - A process to send a request to the data protection officer
* MDL-59720 - Delete personal data when it is no longer required
* MDL-61307 - Create a new privacy subsystem
* MDL-61362 - Ability to create data categories and purposes
* MDL-61486 - Data registry with purpose and retention period
* MDL-61489 - Report of plugin/components implementing the Privacy API
* MDL-61499 - Ability to set default purpose and retention periods for context levels
* MDL-61785 - Ability to review and confirm which expired data can be deleted
* MDL-61899 - Include data privacy tool in core
* MDL-61935 - Ability to specify the lawful bases for the collection of personal data

===Question bank tagging improvements===
* MDL-61066 - Expanded tagging functionality for question bank
* MDL-61133 - New modal to add/edit/remove tags on questions
* MDL-61135 - Filter questions by tag
* MDL-61138 - Show the list of questions in the 'Add a random question' dialog
* MDL-61363 - Ability to add question tags at a course level in the edit question form
* MDL-61364 - Manage tags at a question and course context level
* MDL-61380 - Allow filtering/adding random questions by tag for quizzes
* MDL-61410 - Add import/export support for course level question tags
* MDL-61444 - New capabilities for tagging questions

===UX: Usability improvements===
* MDL-62021 - Boost 4.0 Migration
* MDL-56511 - Update bootstrap 4 to final release
* MDL-61657 - Add images to the course cards on the dashboard

===LTI Advantage support===
* MDL-60416 - Add support for LTI Advantage 1.1

===RecordRTC for Atto===
* MDL-60848 - Implement RecordRTC Atto plugin as core feature
* MDL-61973 - Update RecordRTC Atto plugin buttons

===Messaging database tables===
* MDL-61254 - Merge messaging database tables
* MDL-36941 - Create new tables for messaging
* MDL-61255 - Ad-hoc task to upgrade messages to merged table

==Other Highlights==

===Global search===
* MDL-58885 - Add group support
* MDL-59434 - Content aware searching / alternate results sort orders
* MDL-60981 - Reindex a single area
* MDL-61028 - Allow filtering search by user
* MDL-61256 - Search of section titles, summaries

===Functional changes===
* MDL-2051 - Inform student whether and how their selected choice will display
* MDL-32585 - SCORM: option to force new attempts
* MDL-53226 - Add Moodle DB search engine
* MDL-55491 - Use cohort as badge criteria
* MDL-56246 - Add site wide default for grade export: include feedback
* MDL-59875 - Allow badges as criteria for other badges
* MDL-60119 - Feedback - Multiple choice (rated) - remove weights from answer
* MDL-61203 - Allow uploading of profile picture to be used as badge criteria
* MDL-61601 - Allow cohort themes
* MDL-61651 - LTI: line item definition within link to return gradable LTI links
* MDL-60811 - Bulk delete self-registered enrolments on participants page
* MDL-60682 - Ability to set date/time to nearest minute
* MDL-60441 - Ability to add a link to glossary entries
* MDL-58411 - Ability to apply file type restrictions for essay question type
* MDL-56945 - Add easy return path from PDF grading screen to list of submissions
* MDL-52811 - Add force language capability to course settings
* MDL-41090 - Allow teachers to embed files when manually grading questions

===Security issues===

A number of security related issues were resolved. Details of these issues will be released after a period of approximately one week to allow system administrators to safely update to the latest version.

===For developers===

* MDL-61307 - All plugins must implement [https://docs.moodle.org/dev/Privacy_API Privacy API] to be compliant with GDPR requirements. They must implement the API to report on, export and delete stored user data
* MDL-56511 - Bootstrap is upgraded to final release of version 4
* MDL-61869 - Infer rendering of templatables with no render method
* MDL-61298 - Boost: use navigation node icon

==== Upgrading plugins ====

'''1. Check for changes in core APIs'''

Read lib/upgrade.txt to check for the deprecations and core API changes, make sure you applied them to your plugin. Note that entries there are not sorted by priority but rather by integration time. Below is the list of upgrade.txt files that contain information about upgrading from Moodle 3.4 to Moodle 3.5 (note that if you upgrade from earlier versions there may be more files):

* [https://raw.githubusercontent.com/moodle/moodle/master/lib/upgrade.txt lib/upgrade.txt] changes to various core APIs, deprecations, functions removal
* [https://raw.githubusercontent.com/moodle/moodle/master/calendar/upgrade.txt calendar/upgrade.txt] changes to Calendar API
* [https://raw.githubusercontent.com/moodle/moodle/master/search/upgrade.txt search/upgrade.txt] changes to Global search API
* [https://raw.githubusercontent.com/moodle/moodle/master/message/upgrade.txt message/upgrade.txt] changes to Messages API
* [https://raw.githubusercontent.com/moodle/moodle/master/course/upgrade.txt course/upgrade.txt] changes to Course API

'''2. Check for changes in the API of your plugin type'''

Below is the list of plugin types that had API changes between Moodle 3.4 and 3.5:

* [https://raw.githubusercontent.com/moodle/moodle/master/enrol/upgrade.txt enrol/upgrade.txt] Enrolment method plugins
* [https://raw.githubusercontent.com/moodle/moodle/master/mod/upgrade.txt mod/upgrade.txt] Activity module plugins
* [https://raw.githubusercontent.com/moodle/moodle/master/auth/upgrade.txt auth/upgrade.txt] Authentication plugins
* [https://raw.githubusercontent.com/moodle/moodle/master/course/format/upgrade.txt course/format/upgrade.txt] Course format plugins
* [https://raw.githubusercontent.com/moodle/moodle/master/question/type/upgrade.txt question/type/upgrade.txt] Question type plugins

'''3. Check for changes in the depended plugins'''

If your plugin depends on another plugin or calls methods from another plugin, read upgrade.txt in this plugin directory (if it exists). Below is the list of standard plugins that had changes between Moodle 3.4 and 3.5:

[https://raw.githubusercontent.com/moodle/moodle/master/admin/tool/mobile/upgrade.txt tool_mobile],
[https://raw.githubusercontent.com/moodle/moodle/master/admin/tool/usertours/upgrade.txt tool_usertours],
[https://raw.githubusercontent.com/moodle/moodle/master/mod/assign/upgrade.txt mod_assign],
[https://raw.githubusercontent.com/moodle/moodle/master/mod/feedback/upgrade.txt mod_feedback],
[https://raw.githubusercontent.com/moodle/moodle/master/mod/quiz/upgrade.txt mod_quiz],
[https://raw.githubusercontent.com/moodle/moodle/master/mod/scorm/upgrade.txt mod_scorm],
[https://raw.githubusercontent.com/moodle/moodle/master/theme/boost/upgrade.txt theme_boost]

'''4. Do a smoke test of your plugin with developer debugging mode'''

Make sure to check on both Boost and Clean themes. Bootstrap was upgraded in Moodle 3.5

'''5. Run all behat and phpunit tests'''

==See also==
*[[Moodle 3.4 release notes]]

[[Category:Release notes]]
[[Category:Moodle 3.5]]

[[fr:Notes de mise à jour de Moodle 3.5]]
[[es:Notas de Moodle 3.5]]