Translation FAQ

Jump to: navigation, search

Contents

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?

The month names and days are displayed in English. How can I translate them?

Names of days and months are pulled out of your operating system. The system is configured for Moodle in langconfig.php where you have the strings locale (for -nix type operating systems) and localewin (for Windows operating systems) that should point to the right locale on your server. Your server operating system should support the language (= locale should be installed) - see also Month-name translation problem for an alternative solution.

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 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 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 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 "official" language for Moodle is actually Australian English (G'day mate!) , which is almost 100% the same as UK English.
  • 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 'Talk Like a Pirate' day.
  • 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) is just used to suggest Moodle core language strings improvements and typo fixes.

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 three 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 Gradebook calculations and with the Spanish Moodle Docs.
  • Just as "America and England are two nations divided by a common language", so are Spain and Mexico. See the Mexican Spanish documentation page in Spanish.
  • The Venezuelan Spanish (es_ve) is a very small child language of the international Spanish language.
  • You can read about two (now defunct) other Spanish child languages.

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:

26 AMOS fullnamedisplay core original.png

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

26 AMOS fullnamedisplay core.png

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

26 AMOS fullnamedisplay core Japanese.png

Placeholders enclosed within % characters (%example%) must not be translated

The Moodle Cloud Signup and Portal strings local plugin is used for accessing the 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 translate and must be copied exactly:

AMOS placeholders with percentace character.png

  • Example of one string with one placeholder (highlighted) and some regular text that can be easily translated:

AMOS text with placeholders with percentace character.png

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:

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, 
  • 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 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
<a href="http://docs.moodle.org/en/

Addresses inside a Language string that have
<a href="http://docs.moodle.org/en/ 
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.

  • &nbsp
    - 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.
  • &ensp
    and
    &emsp
    - 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.
  • &amp
    - ampersand sign (&)
  • &apos
    - apostrophe sign (')
  • &copy
    - copyright sign (©)
  • &plusmn
    - "plus or minus" sign (±)
  • &times
    - multiply sign (*)
  • &divide
    - divide sign (/)
  • &gt
    - "greater than" sign ( > )
  • &lt
    - "less than" sign (<)
  • &laquo
    - quotation mark (‘)
  • &lsquo
    - left single quotation sign (‘)
  • &rsquo
    - right single quotation sign (’)
  • &ouml
    - small letter o with diaeresis (ö)

Calculation functions must not be translated

Calculation functions start with an equal sign (=). Following is an expression using operators and functions supported by the system. 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 more about problems with these variables.

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 this trick to check for integrity:
    • Load the language pack in a local instance of Moodle.
    • In order to generate a translation memory, load the language pack in the 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 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 this post and 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 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.

Two simultaneous windows in two languages

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 AMOS translation forum.

Is there a list of Moodle error messages which can be translated?

Error messages are listed in the user docs Category:Error.

Can the subtitles for Moodle HQ YouTube videos be translated?

For Moodle 3.2 onwards, yes. See Translating Moodle video subtitles.

See also this forum thread.

Can the User Tours from Moodle.net be translated?

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 these steps.
  • Windows
    • You can have several local Moodle servers in different folders in a Windows 7 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/ 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...

See also