Create your own awesome maps

Even on the go

with our free apps for iPhone, iPad and Android

Get Started

Already have an account?
Log In

Proposed changes for Moodle 2.x languages machinery by Mind Map: Proposed changes for Moodle 2.x
languages machinery
0.0 stars - reviews range from 0 to 5

Proposed changes for Moodle 2.x languages machinery

translators use single translation interface at http://lang.moodle.org

the only way at the beginning of Moodle 2.0 beta period

adding a support for locally installed tools later

local strings customization possible later during 2.0 beta

translated strings are stored in a database

language packs are generated from the latest snapshot of the database for each branch

generated packs can be downloaded as ZIPs or via internal component downloading mechanism

commiting strings from the master database into a git repository possible in the future if there is a demand for it

get_string() implementation improvement

language packs merging and compiling into run-time format

support for plural forms and other grammar issues

language pack may contain a library of functions or methods that are called instead of plain getting the value from array

not a trivial job - for advanced translators only

the format is not specified yet - we will start some experiments and will choose the solution as the standard one

HTML help files replaced with ordinary strings

makes the translation easier as we do not need to have other tools to translate help files

help consists of a paragraph or two of a static HTML only

no links

no images

just strong, em, p, br

the rest goes to wiki, linked via Documentation for this page

backward compatibility issues

dropping help files indices in favour of wiki

dropping some automatically generated helps (scales etc.)

dropping some helps that were actually a concatenation of several help files (like Add an activity)

location

$string['intro'] = 'Workshop intro'; $string['intro_help'] = 'This is the ...';

migration process

map the current $helppage to the new string to pair it with the text displayed next the field

move language files to the plugin space

as we have in contributed plugins

just to make things easier to understand

downloaded packs goes into $CFG->langpacks and there the structure of Moodle is copied

drop _utf8 suffix from language codes

everywhere, languages are reffered to as "en", "cs", "en_us" or "fr_local" only

just to make things easier

in-place local customization

known as "I want to click at any text in Moodle interface and translate it in-place"

form in the footer that shows the list of all strings that were displayed on the current page

strings cleanup and alchemy

all plugin types must define "pluginname" and "pluginnameplural"

replaces current "modname" and other sort of strings

consistent way across all module types

moving strings from central components (like "enrol") into plugins

done automatically at AMOS database level, re-using current translations

general strings and help review

by Helen